Date: Fri, 10 Jul 1998 18:43:49 +1000 (EST) From: John Birrell <jb@cimlogic.com.au> To: patton@sysnet.net (Matthew Patton) Cc: tcole@nihilist.org, freebsd-current@FreeBSD.ORG Subject: Re: SOLUTION! 2.2.6-Release to -current Message-ID: <199807100843.SAA27370@cimlogic.com.au> In-Reply-To: <l03110703b1c876232419@[192.168.1.10]> from Matthew Patton at "Jul 8, 98 08:02:49 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Matthew Patton wrote: > To think I went through all this pain just to get a SMP kernel so I can > crack rc5des faster. My word of advice: if you want SMP, save yourself the > hassle and start with a -current snapshot. *whew* *Grumble*. Today I went though the exercise of installing 2.2.6-RELEASE from the CD that WC ships. I booted from the install CD, used the visual thingy to deselect all the hardware I don't have (leaving just ide/fd controllers, par/ser ports, ed0) and did a novice install. I gave it the whole disk (wd0), let it use the default partitions, and selected just the user binaries. I created one group and one user, set the timezone and root password, rebooted, logged in as root, NFS mounted /usr/src from another machine. Then I did exactly as I have been advising people to do: cd /usr/src make -m /usr/src/share/mk world I sat and watched it do the complete build without error. No need to set BINFORMAT or MACHINE_ARCH. No editing /etc/make.conf. No specially installing mk files. No rebuilding just libc. No secret handshake. No rocket science. Just a simple make. Next I built the kernel: cd /usr/src/sys/i386/conf /usr/sbin/config GENERIC cd ../../compile/GENERIC make depend && make all && make install This barfed on vnode_if. The solution to that is to simply repeat the command: make depend && make all && make install The kernel built and installed just like it does on current. I edited /etc/rc to change /usr/lib to /usr/lib/aout, sync; sync; sync'd the disk because all the binaries are now incompatible with the booted kernel (so shutdown etc don't work) and power cycled the machine. It booted, fsck'd the disk and let me log in as root. And now the machine is running 3.0-CURRENT. I'm prepared to concede that people _are_ having problems doing this, but I ask you to consider the possibility that the build process _does_ work as advertised on a clean installation. If you're having difficulty, then it makes more sense to address the issue of what is different between _your_ machine and a clean installation before you go to all lengths to hack a build, only getting into more trouble in the process, and then sending misleading messages to this list yelling that you have the solution. If anyone has a 2.2.6-RELEASE installation (unhacked) that can't build current in this manner, please send me private mail containing the error output you are getting. As I've said before, posting messages stating that "it doesn't work" is not helpful. Let's try to find out what breaks the build in some cases. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 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?199807100843.SAA27370>