From owner-freebsd-hackers Sun Sep 21 05:00:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA27697 for hackers-outgoing; Sun, 21 Sep 1997 05:00:44 -0700 (PDT) Received: from smoke.marlboro.vt.us (smoke.marlboro.vt.us [198.206.215.91]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA27683 for ; Sun, 21 Sep 1997 05:00:37 -0700 (PDT) Received: (from cgull@localhost) by smoke.marlboro.vt.us (8.8.7/8.8.7/cgull) id IAA21345; Sun, 21 Sep 1997 08:00:15 -0400 (EDT) Date: Sun, 21 Sep 1997 08:00:15 -0400 (EDT) Message-Id: <199709211200.IAA21345@smoke.marlboro.vt.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: cgull+usenet-876052587@smoke.marlboro.vt.us (john hood) To: Mike Smith Cc: nik@iii.co.uk, hackers@FreeBSD.ORG Subject: Re: Different kernels for the bindist and boot.flp? In-Reply-To: <199709181124.UAA00465@word.smith.net.au> References: <19970918121246.52480@strand.iii.co.uk> <199709181124.UAA00465@word.smith.net.au> X-Mailer: VM 6.31 under Emacs 19.34.2 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Mike Smith writes: > No, it's actually quite hard. Due to the way the boot floppy works, > you have to build a custom image with your new kernel, and then hack > sysinstall to splat a new kernel image down after it's extracted the > bindist. You could alternatively specify a different kernel to go in > the bindist, which is relatively straightforward but slow (you have to > build a release to do it). As I've said before, a way around this is to copy the contents of that MFS onto a floppy, put your custom keeno kernel on another floppy, and swap them at the prompt. Perhaps this could be documented or made more accessible? --jh -- Mr. Belliveau said, "the difference was the wise, John Hood, cgull intelligent look on the face of the cow." He was @ *so* right. --Ofer Inbar smoke.marlboro.vt.us