Date: Sun, 7 Jan 1996 18:55:00 +0100 From: se@zpr.uni-koeln.de (Stefan Esser) To: -Vince- <vince@apollo.cosc.gov> Cc: freebsd-current@freebsd.org Subject: Re: -current kernel problems Message-ID: <199601071755.AA11179@Sysiphos> In-Reply-To: -Vince- <vince@apollo.COSC.GOV> "Re: -current kernel problems" (Jan 6, 9:01)
next in thread | previous in thread | raw e-mail | index | archive | help
On Jan 6, 9:01, -Vince- wrote: } Subject: Re: -current kernel problems } On Sat, 6 Jan 1996, J Wunsch wrote: } } > Btw., if nobody is answering a particular question, while everyone } > seems to be happy with -current, chances are good that you should look } > into your environment again. } } I did and Stefan Esser seemed to say sysctl is having some } problems on some machines... It isn't the environment since we have the } same hardware as freefall does. Hmm, well, I remember saying that sysctl has problems on /your/ machine ... I also said, that there are ongoing changes in that area ... In general, it seems to work just fine. And I get more and more the impression, that you have rebuilt a kernel from incompatible parts ... But the "sysctl -w kern.bootfile=/kernel.old" which fails on your system is unneccesary anyway, if you are going to reboot immediately. And you just should rebuild /usr/sbin/config, configure your kernel using the new binary, and then build a kernel in a clean compile directory. Regards, STefan -- Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 ============================================================================== http://www.zpr.uni-koeln.de/~se <se@ZPR.Uni-Koeln.DE>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199601071755.AA11179>