Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!math.ohio-state.edu!caen!usenet.coe.montana.edu!bsd.coe.montana.edu!nate From: nate@bsd.coe.montana.edu (Nate Williams) Newsgroups: comp.os.386bsd.development Subject: Re: Going from FreeBSD 1.0.2 to FreeBSD-current Date: 19 Feb 1994 19:11:32 GMT Organization: Montana State University, Bozeman MT Lines: 86 Message-ID: <2k5o94$i7a@pdq.coe.montana.edu> References: <JKH.94Feb17055727@whisker.hubbard.ie> NNTP-Posting-Host: bsd.coe.montana.edu In article <JKH.94Feb17055727@whisker.hubbard.ie>, Jordan K. Hubbard <jkh@whisker.hubbard.ie> wrote: }I've had a lot of folks ask what the best way of going about this }is, so here's a short synopsis that Terry L. and I have put together. } }This still assumes that you know a bit about what you are doing and }all my earlier comments about who should and who should not run }-current still apply! } }This also assumes that /usr/src/ contains a _FULL_ FreeBSD-current }source tree and ftp'd or sup'd from freebsd.cdrom.com (or one of our }mirror sites): } }BUILD SEQUENCE: } }cd /usr/src/share/mk }make install }cd /usr/src/include }make install }cd /usr/src/usr.sbin/config }make all install }cd /usr/src/sbin/mount_procfs }make all install } }Now add the following to your /etc/fstab file: } }proc /proc procfs rw 0 0 } }And continue with the kernel: } }cd /usr/src/sys/i386/conf }# If a recent update, you will have to edit the config to change the fd }* controller from fd0 to fdc0... You will also have to modify the wd lines to look similar to the lines in the GENERICAH kernel as well if you are using a custom kernel. For both fd and wd configuration lines use the GENERIC files as reference. To be really safe, I'd start with one of the GENERIC files and add/delete options to it to be safe. }config <configname> # ie: "config GENERICAH" }cd ../../compiler/<configname> }vi Makefile }<add -D__FreeBSD__ to the CFLAGS line - this is transitional only> }<change the -Z in the Makefile SYSTEM_LD line to a -z - transitional only> } }make depend }make }# Assuming it works... }mv /386bsd /386bsd.old }mv 386bsd /386bsd }sync }sync }sync }reboot } }...THEN you can make your "bootstrapld" target, followed by a make world. } }Before rebooting again (after the make world completes successfully) }remake your password database by doing a `vipw' and just touching the }file so that it gets rebuild (delete a character and add it back }again, or something). The database format has changed slightly and it }is necessary to remake the database so that all the tools see the new }format (or you won't be able to log in again when you reboot! :-). }Now reboot to get all the new system binaries running. Congrats, }you're running freebsd-current (~1.1 BETA)! } }You should now be able to configure/build kernels or sources in pretty }much any order and without editing. The steps marked "transitional" }above were truly that, transitional. Note, because building custom kernels is still a process that can't be automated easily, if you decide to upgrade from 1.0.2 to 1.1 you will still need to do this sort of process then. However, if you decide to go the GENERIC route, most of this will be automated in the upgrade process for those who are weak of heart. Nate -- nate@bsd.coe.montana.edu | FreeBSD core member and all around tech. nate@cs.montana.edu | weenie. work #: (406) 994-4836 | Graduating May '94 with a BS in EE home #: (406) 586-0579 | - looking for work in CS/EE field.