From owner-freebsd-questions Tue Apr 7 13:08:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA00824 for freebsd-questions-outgoing; Tue, 7 Apr 1998 13:08:19 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA00257 for ; Tue, 7 Apr 1998 13:07:03 -0700 (PDT) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.7/8.8.8) with SMTP id NAA26879; Tue, 7 Apr 1998 13:06:49 -0700 (PDT) (envelope-from dwhite@gdi.uoregon.edu) Date: Tue, 7 Apr 1998 13:06:49 -0700 (PDT) From: Doug White Reply-To: Doug White To: Karl Pielorz cc: questions@FreeBSD.ORG Subject: Re: Changing the kernel on a 2.2.6 Install/Boot Disk... In-Reply-To: <352A0833.B367413A@tdx.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 7 Apr 1998, Karl Pielorz wrote: > How easy (if at all possible) is it to 'change' the kernel on a > 2.2.6-RELEASE boot/install disk? Not easy. If you want to build a new install disk you have to build all the tools on it. A mechanism exists to do this (dubbed `make release' for the command you run) but it does take time and resources to use. > I wanted to make an install disk with a different kernel on it, but I gather > because of the MFS / file system embedded in the kernel etc. - this could be > quite tricky? > > I have a 'donor' machine - which I don't mind installing all the source on > it and building it there - if that's what it takes... Okay, then. Install the full system source (I don't think you need xfree) then look in /usr/src/release. **READ THE MAKEFILE BEFORE YOU DO ANYTHING** Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message