From owner-freebsd-current Wed Nov 15 12:39:54 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id MAA22610 for current-outgoing; Wed, 15 Nov 1995 12:39:54 -0800 Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id MAA22581 for ; Wed, 15 Nov 1995 12:39:49 -0800 Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id MAA19557; Wed, 15 Nov 1995 12:39:22 -0800 From: "Rodney W. Grimes" Message-Id: <199511152039.MAA19557@GndRsh.aac.dev.com> Subject: Re: cvs commit: src/usr.sbin/syslogd syslogd.c To: wollman@lcs.mit.edu (Garrett A. Wollman) Date: Wed, 15 Nov 1995 12:39:22 -0800 (PST) Cc: davidg@Root.COM, current@freebsd.org In-Reply-To: <9511151653.AA26197@halloran-eldar.lcs.mit.edu> from "Garrett A. Wollman" at Nov 15, 95 11:53:34 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1479 Sender: owner-current@freebsd.org Precedence: bulk > > < 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