Subject: Re: It's still PST in the Pacific time zone ... / 1st time "sup"
To: None <current-users@sun-lamp.cs.berkeley.edu>
From: - Greg Earle <earle@isolar.Tujunga.CA.US>
List: current-users
Date: 04/03/1994 12:05:28
>Re: comment that NetBSD didn't notice crossing into DST, posted with example
>dates at 1AM and change:
>
>I thought that DST started at 2AM?  I'm pretty sure that that's when you're
>supposed to change your clocks.

It did.  That's when I posted it.  Right after the 2AM -> 3AM change.

As I posted last weekend, my clock was already an hour behind, even for GMT. 
So it was saying 1 AM when it was really already 2 AM, and after 2 AM when it
should have said "3 AM PDT", it was still saying "1 AM PST".  It did not thus
recognize that PST -> PDT until an hour after it "really" did; my system now
says

netbsd4me:83 # uname -a ; date
NetBSD netbsd4me.jpl.nasa.gov 0.9a NETBSD4ME#0 sparc
Sun Apr  3 10:39:15 PDT 1994

whereas it's really

isolar:2:240 % uname -a ; date
SunOS isolar 4.1.3 2 sun4c
Sun Apr  3 11:38:34 PDT 1994

So I'm back to being only 1 hour behind, at least :-)

Because my GMT is also one hour wrong, but you say yours are OK, I have to then
wonder if perhaps gettimeofday() has been changed recently?

Are other people still seeing their clocks as being 1 hour behind?

>All of my clocks show the correct time now; I was baking brownies at 1 and 2
>AM (and therefore 3AM 8-), so I can't say exactly what it looked like then ...

Any special ingredients in those brownies?	:-)

-------------------------------------------------------------------------------

On another note, I built & installed "sup" (nothing from my source tree build
mkdir'd "/usr/lib/supfiles", so I had to suss that out).  Decided to try it
out in test mode:

netbsd4me:295 # sup -fNvs
SUP 8.26 (4.3 BSD) for system software at Apr  3 10:41:35
SUP Upgrade of current-allsrc at Sun Apr  3 10:41:36 1994
SUP Fileserver 7.13 (4.3 BSD) 9622 on sun-lamp.cs.berkeley.edu at 10:41:36
SUP Requesting changes since Dec 31 16:00:00 1969
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

I already made the whole build from last weekend's tar babies.  I'd like to
avoid having "sup" suck the whole universe down upon first "real" invocation;
is there any way to do that, manually or otherwise?  My guess is that I'd have
to either run it with the "-k" option, or else manually create

/usr/lib/supfiles/<collection name>/when.<rel-suffix>

(what values of "rel-suffix" would be used?) and put timestamps in each of them
(what format are the timestamps in?  sup(1) doesn't say; is it just in the
 tv_sec long returned from gettimeofday(2)?)

Also, I noticed this in the "test" run output:

SUP Would create file README.export-control
SUP Would receive old file src/Makefile
SUP Would update file src/bin/Makefile
...
SUP Would update file src/bin/cp/Makefile
SUP Would update file src/bin/cp/cp.1
SUP Would receive new file src/bin/cp/cp.c
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Curious to know why it said "receive new file src/bin/cp/cp.c" here.  I already
have a /usr/src/bin/cp/cp.c, thus my curiosity ...

	- Greg

------------------------------------------------------------------------------