cvs commit: src/sbin/adjkerntz adjkerntz.c

Giorgos Keramidas keramida at
Mon May 15 08:17:08 PDT 2006

On 2006-05-15 19:00, Maxim Konovalov <maxim at> wrote:
>On Mon, 15 May 2006, 17:27+0300, Giorgos Keramidas wrote:
>> On 2006-05-11 17:25, Poul-Henning Kamp <phk at> wrote:
>> >   1.30      +14 -25    src/sbin/adjkerntz/adjkerntz.c
>> On 2006-05-13 11:58, Pawel Jakub Dawidek <pjd at> wrote:
>> >   1.31      +4 -4      src/sbin/adjkerntz/adjkerntz.c
>> These changes make it impossible to run a new `adjkerntz' with
>> an old kernel.  Since adjkerntz is one of the first things
>> that need to be run before `make installworld' in single-user
>> mode, do you think we should add an UPDATING entry that after
>> this change people should install a new adjkerntz before
>> booting into single-user mode?
>> Otherwise, running `make installworld' may install files with
>> timestamps that are several hours in the future, depending on
>> the local timezone settings.
> Huh.  Saw this today 4am when reboot with new kernel and
> thought that was hallucination.

Heh!  This is what you get for running installworlds at 4am or
so, I guess.  I get that too often lately, so don't worry :-)

How about adding this to UPDATING then, everyone?

--- UPDATING    (revision 75)
+++ UPDATING    (working copy)
@@ -21,6 +21,21 @@
        developers choose to disable these features on build machines
        to maximize performance.
+       The machdep.* sysctls and the adjkerntz utility have been
+       modified bit bit.  The new adjkerntz utility uses the new
+       sysctl names and sysctlbyname() calls, so it may be impossible
+       to run an old /sbin/adjkerntz utility in single-user mode
+       with a new kernel.  Replace the `adjkerntz -i' step before
+       `make installworld' with:
+           /usr/obj/usr/src/sbin/adjkerntz/adjkerntz -i
+       and proceed as usual with the rest of the installworld-stage
+       steps.  Otherwise, you risk installing binaries with their
+       timestamp set several hours in the future, especially if
+       you are running with local time set to GMT+X hours.
        The ip6fw utility has been removed.  The behavior provided by
        ip6fw has been in ipfw2 for a good while and the rc.d scripts

More information about the cvs-src mailing list