Date: Wed, 15 Nov 1995 12:39:22 -0800 (PST) From: "Rodney W. Grimes" <rgrimes@GndRsh.aac.dev.com> To: wollman@lcs.mit.edu (Garrett A. Wollman) Cc: davidg@Root.COM, current@freebsd.org Subject: Re: cvs commit: src/usr.sbin/syslogd syslogd.c Message-ID: <199511152039.MAA19557@GndRsh.aac.dev.com> In-Reply-To: <9511151653.AA26197@halloran-eldar.lcs.mit.edu> from "Garrett A. Wollman" at Nov 15, 95 11:53:34 am
next in thread | previous in thread | raw e-mail | index | archive | help
>
> <<On Wed, 15 Nov 1995 05:54:22 -0800, David Greenman <davidg@Root.COM> said:
>
> > 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.
>
> No, the bootfile name should not be read-only; I knew what I was doing
> when I wrote that code.
Agree.
> Yes, the Makefile should not be messing with
> it.
Disagree, but it should be very carefull about messing with it:
mv /kernel /kernel.old
kernel=`sysctl kern.bootfile`
if [ "X${kernel}" = "X/kernel" ]; then
sysctl -w kern.bootfile=/kernel.old
fi
> The reason for making the bootfile name not be read-only is to allow
> LKMs to leave their symbol-files in some convenient place and set
> kern.bootfile to point there, so that other programs like `modload'
> and `netstat' are able to find it.
Likewise if make install does overwrite the running kernel but saves a
copy of it first kern.bootfile should point to this saved copy, otherwise
strange things can and _DO_ happen. A lot of code now gets the running
kernel name from sysctl, and to screw this over due to lack of dilligenance
in the kernel install: target is just silly.
--
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?199511152039.MAA19557>