From owner-freebsd-stable Sat Nov 6 4:10:38 1999 Delivered-To: freebsd-stable@freebsd.org Received: from blaubaer.kn-bremen.de (blaubaer.kn-bremen.de [195.37.179.254]) by hub.freebsd.org (Postfix) with ESMTP id 6961414D75 for ; Sat, 6 Nov 1999 04:10:34 -0800 (PST) (envelope-from nox@saturn.kn-bremen.de) Received: from saturn.kn-bremen.de (uucp@localhost) by blaubaer.kn-bremen.de (8.9.1/8.9.1) with UUCP id NAA04119; Sat, 6 Nov 1999 13:09:16 +0100 Received: (from nox@localhost) by saturn.kn-bremen.de (8.9.3/8.8.5) id MAA35365; Sat, 6 Nov 1999 12:43:40 +0100 (MET) Date: Sat, 6 Nov 1999 12:43:40 +0100 (MET) From: Juergen Lock Message-Id: <199911061143.MAA35365@saturn.kn-bremen.de> To: zzhang@cs.binghamton.edu Subject: Re: easyboot far into disk X-Newsgroups: local.list.freebsd.stable In-Reply-To: References: <199911051534.HAA02236@dingo.cdrom.com> Organization: home Cc: freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: >Also, Linux can boot from a floppy. Can FreeBSD does similar things (boot >from a floppy and then use data on the hard drive)? Seems so, use a modified kern.flp with your kernel and change its loader.rc: remove the loading of the mfsroot image and add a line that sets currdev to point to your root fs (you can use lsdev in the loader to find it), and you should be ready to go. (I first tried setting rootdev instead but that seems to be getting ignored completely at least when booting from a floppy.) Btw i remember reading in a commitlog that the concept of a `current device' in loader is about to go, so maybe now this no longer works in -current... (Maybe this should be added to the FAQ as a method of last resort when the BIOS boot code can't see above cyl 1024?) Regards, -- Juergen Lock (remove dot foo from address to reply) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message