Date: Mon, 8 Dec 2003 17:50:03 -0500 From: Damian Gerow <damian@sentex.net> To: freebsd-hackers@freebsd.org Subject: Re: FBSD 5-CURRENT: Kernel Makefile.inc1 Error Message-ID: <20031208225003.GZ82104@sentex.net> In-Reply-To: <20031208222742.GA60526@wombat.localnet> References: <20031206074503.GA73696@siue.dnsalias.net> <p0600202fbbf743682da1@[128.113.24.47]> <20031208174126.GJ82104@sentex.net> <20031208222742.GA60526@wombat.localnet>
next in thread | previous in thread | raw e-mail | index | archive | help
Thus spake Michael Edenfield (kutulu@kutulu.org) [08/12/03 17:28]: > with a 5.2 /usr/src: > * make buildworld > * make buildkernel > * make installkernel > * reboot to single-user > * make installkernel > * mergemaster > * reboot I think you want that second 'installkernel' to actually be an 'installkernel'. > The issue is, your kernel will continue handing out old file system > structures until you reboot with a new one. Rather early in the > installworld process, you will stop being able to use fundamental system > commands like ls and cp, which expect the new structures. According to the posts by Mr. McKusick, the new kernel should be able to understand both the old and the new structures -- so cp should *not* break. So long as you follow his instructions, and reboot with the new kernel before doing the installworld. > Also, a small number of ports break as well. Between the mergemaster > and reboot steps you may wish to rebuild any critical ports. postfix, > for example, refuses to start it's smtpd until you rebuild it. Any > other ports which behave oddly, particularly those which die with a > signal 11, probably need a rebuild. Yes, I ran into that as well. I gave up on guessing which ports needed to be re-compiled, and just did a portupgrade -fa, and went to bed.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031208225003.GZ82104>