Mike Macgirvin
Diary and Other Rantings
Beyond Silicon Valley
   
Wednesday, Jul 09 2008, 12:49 pm
Oct 27, 2007
Daylight Savings

Tomorrow is Daylight Savings. Remember 'Spring forward, fall back'? That's right - tomorrow we move it forward, no matter how odd that may seem. It's October, but it's spring.

At least the Australian government hasn't been mucking with and tweaking DST as it did before the 2000 Olympics. The software engineers need time to code in the changes - I think that a lot of the world now has Sydney time right.

Well that would be anybody using the Olsen timezone databases. I know personally about thirty web services which just give you a choice of 'GMT+10' - and these are all going to be wrong tomorrow. On the bright side, I really don't care if they get it wrong. I'm not using any of them for anything globally time sensitive. It always makes my head hurt trying to figure out how many hours I'm going to be away from GMT with all the conversions and tweaks in effect. I suppose it'll probably be GMT+11. One hour forward. But wait, we'll then be one hour closer to Greenwhich, England as the earth spins. Not further from it. So maybe it's GMT+9. Silicon Valley will be... Uh, I give up. It's in negative GMT and the time is going back. So is it forward or backward? I'll have to figure it out on paper to work out the difference between LA (where this server is) and Sydney (close enough to where I am).  

But this will also give a good test of my own daylight savings and timezone functions (which use Olsen tables). The U.S. is going one hour back and we're going one hour forward. I might be poring over the code tomorrow if something gets askew.  

Comments:

Joe (Derek Joe Tennant)
October 28, 2007 04:08
Joe
Mike....already you've been away from the US too long! The new law has the time change thethird weekend in March and the first Sunday in November. So don't change anything tomorrow (today, since you're already Sunday while I write this Saturday morning in the states....)

mike (Mike Macgirvin)
October 28, 2007 08:22
[*TOP MEMBER*] mike

In fact the time changed here - I was just a bit premature on when it changes there. They used to try and change the whole world on the same day, but you're right. Last year's energy act messed up that part of it.

No worries. Everything seems to be working. It just means I'll have to go through all of this again when you folks change over. I won't bother calculating the delta right now, since it's in a temporary state. It's nice to know the delta before I make a phone call overseas. Nothing worse than 'Hello? Who is this? It's 3 in the morning!'


peonyden (Denis Wilson)
October 28, 2007 09:45
peonyden
Hi Mike Thanks for posting about Daylight Saving Changes. We have now changed, but on the Sunday morning, so you might have been early to all events on Saturday, if you changed on 27 October. But that's better than being completely out. It is one thing to be unaware. You end up 1 hour late on the first day of the change. I went the wrong way, once, (the "autumn" change) and put my clocks forward, at the end of the season. I was two hours early for everything, and thought I had missed a series of important events. but they had not yet happened. I was in a panic - unnecessarily. The little adage "Spring Forward, Fall Back" which you quoted is now permanently engraved in my brain as a result of the scare I had on that occasion. Denis

peonyden (Denis Wilson)
October 28, 2007 09:49
peonyden

Mike

Now that I am properly awake, I see that your comment: "that the time had changed here" was written on Sunday morning - sorry if I implied you were a day ahead.

That's the other problem with Daylight Saving changeover. Body awake, but brain not yet awake.

Denis 

 


Comments? | More Actions Open/Close menu
Oct 15, 2007
Disable Linux screen blanking

I'm a bit tired of searching the web for this every time I install a new Linux box; which is every few weeks these days - but apparently not often enough to get it stuck in my brain. 

To disable the annoying 10 minute Linux automatic screen blanking, use:

/usr/sbin/setterm -blank 0

Stick it in /etc/rc.local on Debian, or in /etc/init.d/rc.local if that doesn't exist.

 

Comments:

mike (Mike Macgirvin)
November 10, 2007 08:38
[*TOP MEMBER*] mike
Actually in Debian 4.x, all of this stuff has been moved and generalized. Instead of rc.local, you should be able to edit the settings directly in /etc/console-tools/config - which should be read/processed by /etc/init.d/console-screen.sh during startup.

Comments? | More Actions Open/Close menu
Oct 13, 2007
goodbye /dev/fd0

I've got both a 5.25 and 3.5 floppy drive on my Linux box at home. I bought the 5.25 drive in the mid-80s as part of my first 'clone kit' (cheap IBM-style PC built completely from components made in Asia). Today I finally unplugged it, even though it still works just fine. I can't even recall the last time I actually used it. I believe I made a Linux emergency boot disk back in 2002, but that was on the 3.5 drive.

I tossed all my old 5.25 disks prior to moving overseas. After much more than ten years in non-controlled temp/humidity environments, there wasn't any 'critical data' left to speak of. Ditto for the 3.5's.

So I've got no disks left to read, and 720kbytes is pathetic and slow storage in 2007.  If you need a copy of something, just flash it to a USB stick.

It certainly wasn't my first floppy drive (that distinction would go to an old 8 inch CP/M drive which I never used because it was obsolete before I ever finished writing the assembly language driver code); - but it's the longest surviving piece of computer hardware I've got at the moment.  Seems a shame to let it go, however what's the point of keeping it running?

This data too shall pass. 

Comments? | More Actions Open/Close menu
Some circumstantial evidence is very strong, as when you find a trout in
the milk.
-- Thoreau