From owner-freebsd-questions Thu Jan 4 09:30:06 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA18266 for questions-outgoing; Thu, 4 Jan 1996 09:30:06 -0800 (PST) Received: from albion.loach.org (root@loach.org [199.233.190.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA18254 for ; Thu, 4 Jan 1996 09:30:01 -0800 (PST) Received: (from alexei@localhost) by albion.loach.org (8.6.12/8.6.9) id JAA07117; Thu, 4 Jan 1996 09:31:23 GMT From: Alexei Nikolaevich Romanov Message-Id: <199601040931.JAA07117@albion.loach.org> Subject: Re: Small, tiny question. To: chuckr@glue.umd.edu (Chuck Robey) Date: Thu, 4 Jan 1996 09:31:21 +0000 () Cc: freebsd-questions@freebsd.org In-Reply-To: from "Chuck Robey" at Jan 4, 96 11:54:48 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-questions@freebsd.org Precedence: bulk > > On Thu, 4 Jan 1996, Alexei Nikolaevich Romanov wrote: > > > Is there a quick guide to completely rebuilding the OS using the make world > > mechanism of the source tree? Any caveats that need to be known? Anyone? > > Anyone? Bueller? :) Any advice is appreciated! > > Take a look at the handbook, it's got a section on making your kernel > config file that's pretty useable. Beware, if you have an older copy of > the handbook, it had a mistake in it that made many think it was ok to > drop the npx0 device. It's a mandatory device, so don't disable it or > you just won't get a good compile (you'll get linking error messages). > > After you are happy with the config file, use the config utility to make > a build directory for it. You MUST do it that way, because config does > many other things for you too. Then cd into the directory that config > tells you it has created, do a make depend, then a make. If you don't > see any error messages, you can install this new kernel in your system > with a make install. If you then get a error rebooting and want to go > back to your old kernel, it's still there, just respond to the boot > prompt with the filename "kernel.old" and you'll be back where you were. > You might want to save that kernel.old then, to make room, because a > second make install (of a fixed kernel) will write the bad kernel into > kernel.old. I usually keep an 'emerg'ency file in my root, to which I > always copy my last good kernel, as a safety line. > > > > > -Alexei > > > > ============================================================================ > Chuck Robey chuckr@eng.umd.edu -- I run FreeBSD on n3lxx and Journey2 > --------------------------------------------------------------------------- > The Dilbert Zone is Dilbert's new WWW home! The area > features never-before-seen original sketches of Dilbert, a photo tour > of Scott Adams' studio, Dilbert Trivia and memorabilia, high > school photos and much more!: > > > My english isn't so good; I meant to ask: How do you go about building the entire _OS_; i.e., the shared libraries, and the utilities. THe kernel build is no problem whatsoever. I meant to specify that I meant about the source tree for everything else. (As I'm interested in recompiling them all, and practising, before bringing a system up to date with sup, for experimentation) Apologies for the confusion-- Alexei