Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 20 Nov 1995 14:37:31 -0800 (PST)
From:      "Rodney W. Grimes" <rgrimes@GndRsh.aac.dev.com>
To:        davidg@Root.COM
Cc:        guido@gvr.win.tue.nl, CVS-commiters@freefall.freebsd.org, cvs-usrsbin@freefall.freebsd.org
Subject:   Re: cvs commit: src/usr.sbin/syslogd syslogd.c
Message-ID:  <199511202237.OAA23395@GndRsh.aac.dev.com>
In-Reply-To: <199511202143.NAA00149@corbin.Root.COM> from "David Greenman" at Nov 20, 95 01:43:57 pm

next in thread | previous in thread | raw e-mail | index | archive | help
> 
> >>    The sysctl crap in the Makefile is bogus and should be removed. My kernel
> >> is often not called "/kernel" and pretending that it was is wrong. The bootfile
> >> name should be read-only and the Makefile should not be messing with it.
> >> 
> >
> >I still dont like the fact that installing a new kernel with make install
> >can make all kinds of programs useless. Perhaps a better way of
> >doing things is first check if /kernel is the kernel being used. If so, and
> >if it is moved to kernel.old, sysctl should be called according to me.
> 
>    And if I do 2 make installs before rebooting?

Enhance my last patch to test if sysctl kern.bootfile==/kernel.old and if
it does output a warning and probably set kern.bootfile to null since you
don't have a valid copy of the current kernel anyplace but in memory.

[Hummmm.. would /dev/kmem work???.  I think not since the a.out header is
missing :-(]

Or perhaps enhance the rename to use /kernel.N, N being a number, simply
move it to one higher than the highest existing file.

Anyway, this is not rocket science, it can be fixed to do the right things
rather trivially.

-- 
Rod Grimes                                      rgrimes@gndrsh.aac.dev.com
Accurate Automation Company                 Reliable computers for FreeBSD



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199511202237.OAA23395>