Date: Sun, 30 Nov 2003 21:02:11 -0800 (PST) From: Sean Welch <welchsm@earthlink.net> To: dgilbert@dclg.ca Cc: freebsd-mobile@freebsd.org Subject: Re: Latitude D800 Message-ID: <10005482.1070254931933.JavaMail.root@bigbird.psp.pas.earthlink.net>
next in thread | raw e-mail | index | archive | help
Actually, Dave, you can specify a timestamp. Add a line of this format
to your supfile to do just that:
*default date=2002.03.16.12.12.00
The timestamp in the above line corresponds to 12:12 on the 16th of
March 2002.
Please note that you must include all digits -- no shortcuts. There is
more info in the manpage.
Sean
__________________________________________________________
>>>>> "Randy" == Randy Bush <randy@psg.com> writes:
>> -CURRENT on your workstation says "I use this shit" ... :)
Randy> after throwing three days into -current to get athelon support
Randy> for my t40, i found it did not really work. so, imiho, current
Randy> says you have too much free time on your hands. isn't that why
Randy> it's called freebsd?
I dunno. I've had a relatively sane trip on -CURRENT for some time.
There have been rockier periods... but the amount of time that I'm
out-of-commission due to -CURRENT has been very small... and usually
fixed by an overnight rebuild or somesuch.
... but -CURRENT is, as they say, for the developers. I'm not sure of
the benifit for non-developers to be at -CURRENT.
I do maintain a few other peoples machines at varying stages of
-CURRENT. I find it helpful to have a machine to test an update on
first. One small flaw in cvsup is that you can't specify a timestamp
to sync the files to. That would make things more sane.
Dave.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?10005482.1070254931933.JavaMail.root>