![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Working Sundays
Jun. 13th, 2004 01:49 pmI'm in work at the moment.
And I've been here since 10:30 am.
Working Sundays really sucks.
I mean, being in work, when it's quiet, getting paid time and a half is rather pleasant. It's just the losing a day from the weekend that's bad.
Whilst I'll probably only end up doing 4-6 hours work today, it's meant that I had to crash relatively early last night, and had to think about my hangover for the next day.
Oh, and the real drawback, is not being able to forget about work for two days. That's important IMO.
Oh, and it's taking a little longer than I thought, because some Evil Git decided to use 15Gb disk images rather than our standard 4Gb. Which obviously takes 4 times as long to copy, and means I have to twiddle my thumbs for a bit whilst they do. (ok, so it's only an hour for 15Gb to copy, but there's 3 of them, and about 5 4Gb disk images too).
That said, I suppose if one has to work Sunday, then a few more hours don't really hurt. Well, 'cept if those buggers back 'ome start a roleplay game without me...
I'm in today, doing VMWare migrations. Now I'm sure I've mentioned it before, but VMWare is 'virtual machine' technology. 1 server, 10 'virtual' servers.
I'm moving the 10 onto a new machine. Now most of these are Windows boxes - we don't have many *nix machines on VMWare because Unix applications tend to be much better behaved about sharing resources, and not mutually crashing each other.
Whilst Windows 2000 is notably better from a general management point of view, I've noticed that the NT machines I've been moving have been a lot more tolerant of their hardware 'magically' changing underneath them. W2k seems to get most upset.
It may be a bad sign, but I find the idea of 'upsetting' operating systems most entertaining. Especially when their Win2000 and therefore NMFP.
Good eh?
And I've been here since 10:30 am.
Working Sundays really sucks.
I mean, being in work, when it's quiet, getting paid time and a half is rather pleasant. It's just the losing a day from the weekend that's bad.
Whilst I'll probably only end up doing 4-6 hours work today, it's meant that I had to crash relatively early last night, and had to think about my hangover for the next day.
Oh, and the real drawback, is not being able to forget about work for two days. That's important IMO.
Oh, and it's taking a little longer than I thought, because some Evil Git decided to use 15Gb disk images rather than our standard 4Gb. Which obviously takes 4 times as long to copy, and means I have to twiddle my thumbs for a bit whilst they do. (ok, so it's only an hour for 15Gb to copy, but there's 3 of them, and about 5 4Gb disk images too).
That said, I suppose if one has to work Sunday, then a few more hours don't really hurt. Well, 'cept if those buggers back 'ome start a roleplay game without me...
I'm in today, doing VMWare migrations. Now I'm sure I've mentioned it before, but VMWare is 'virtual machine' technology. 1 server, 10 'virtual' servers.
I'm moving the 10 onto a new machine. Now most of these are Windows boxes - we don't have many *nix machines on VMWare because Unix applications tend to be much better behaved about sharing resources, and not mutually crashing each other.
Whilst Windows 2000 is notably better from a general management point of view, I've noticed that the NT machines I've been moving have been a lot more tolerant of their hardware 'magically' changing underneath them. W2k seems to get most upset.
It may be a bad sign, but I find the idea of 'upsetting' operating systems most entertaining. Especially when their Win2000 and therefore NMFP.
Good eh?
