Date: Tue, 12 Jan 1999 21:57:05 -0500 From: "Norman C. Rice" <nrice@emu.sourcee.com> To: Eddie Lawhead <eddie@silk.net> Cc: freebsd-current@FreeBSD.ORG Subject: Re: 3.0R--> -current. Message-ID: <19990112215705.A25754@emu.sourcee.com> In-Reply-To: <Pine.BSF.4.05.9901111923260.21568-100000@eddie.silk.net>; from Eddie Lawhead on Mon, Jan 11, 1999 at 07:30:32PM -0800 References: <Pine.BSF.4.05.9901111923260.21568-100000@eddie.silk.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jan 11, 1999 at 07:30:32PM -0800, Eddie Lawhead wrote: > > Hello All! > > I am just about to make the move from 3.0 Release to -Current. What > sort of things can I expect? Does anyone have some good ideas on > preparations I should make? I have read and printed out the "Making the > World" tutorial....I am just looking for -current specific information. In addition to the information contained in /usr/src/UPDATING and the sources that it references, I encountered the following problems during recent updates (1/9/99 and 1/10/99). 1. A ``make -j4 world'' failed with a kzip loader kzip: not found This was remedied by changing ``kzip'' to ``/usr/bin/kzip'' in /usr/src/sys/boot/i386/loader/Makefile. 2. A ``make -j4 world'' failed because some directories did not exist under /usr/share/examples/kld. This was remedied by cd /usr/share/examples/kld mkdir syscall mkdir syscall/module mkdir syscall/test 3. Building a new kernel failed with several ``gensetdefs:'' errors complaining about aout object files. This was remedied by make clean make depend && make && make -DFORCE install 4. One system panic'd when it tried to change the root device to da1s1a. With an aout kernel it used /boot.config to specify 0:da(1,a)kernel and I tried to move this file to /boot/boot.conf without success. This was remedied by booting from a fixit floppy and restoring the /boot.config file. I assume there is a way to do this with the new loader, but I didn't have the time to research it. 5. On a multi-boot system it was necessary to copy the new boot sector after the disklabel -B process required by the new loader. These issues may already be resolved. I highly recommend using mergemaster (referenced in the UPDATING document). -- Regards, Norman C. Rice, Jr. > > Thanks in advance, > > Eddie > > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Eddie H. Lawhead FreeBSD: The Power To Serve > Kelowna, BC, Canada http://www.FreeBSD.org > eddie@silk.net http://www.Silk.net > ---------------------------------------------------- > | Silk Internet: Your Smooth Connection To The Net | > ----------------------------------------------------- > =-=-=-=-=-=-= Enriched, V-Card, HTML Messages > /dev/null =-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990112215705.A25754>