Date: Sun, 21 Oct 2001 00:17:54 -0700 From: Peter Wemm <peter@wemm.org> To: Brian Somers <brian@FreeBSD.org> Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/conf Makefile.i386 Message-ID: <20011021071754.CF876380A@overcee.netplex.com.au> In-Reply-To: <200110171357.f9HDvX610060@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Brian Somers wrote: > brian 2001/10/17 06:57:32 PDT > > Modified files: > sys/conf Makefile.i386 > Log: > Change kern.bootfile when mv'ing the kernel This backs out part of rev 1.169, which was an intentional change.. This is incomplete.. what if it is the second 'make install'? What if sysctl isn't in $PATH? What if it is an old sysctl that needs the -w switch? There isn't an error trap to eat the error code, will this cause 'make installkernel' to fail? Hmm, it seems it does: peter@overcee[12:15am]/home/src/sys/i386/compile/OVERCEE-111# make install rm -rf /boot/kernel.old mv /boot/kernel /boot/kernel.old [ "`sysctl -n kern.bootfile`" != "/boot/kernel/kernel" ] || sysctl kern.bootfile=/boot/kernel.old/kernel sysctl: must use -w to modify variables *** Error code 1 Stop in /home/src/sys/i386/compile/OVERCEE. Nothing is supposed to be using this sysctl, it's purely informational these days, and even then it has only part of the story. The booted kernel may not even be reachable (eg: on an EFI filesystem or pulled in via tftp). Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011021071754.CF876380A>