From owner-freebsd-current Fri May 21 9: 7:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles521.castles.com [208.214.165.85]) by hub.freebsd.org (Postfix) with ESMTP id 9AA6F14F5F for ; Fri, 21 May 1999 09:07:45 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id UAA00358; Thu, 20 May 1999 20:27:09 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199905210327.UAA00358@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: W Gerald Hicks Cc: Mike Smith , current@FreeBSD.ORG, wghicks@wghicks.bellsouth.net Subject: Re: FBSDBOOT.EXE In-reply-to: Your message of "Sun, 16 May 1999 23:09:21 EDT." <199905170309.XAA16468@bellsouth.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 20 May 1999 20:27:09 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > The loader won't help you because you are booting from under DOS, but > > the loader will boot the kernel just fine off a DOS filesystem. > > I'd like to understand this aspect of the loader better. This mode > might be useful for booting from (for example) a DOS flash filesystem? Typically a bootable volume on the PC has a helper BIOS that makes it look like a floppy disk. > Um... off to the source code. Thanks for the tip. The loader's multiple filesystem support is pretty simple and consequently a bit stupid; it will simply apply every filesystem module to the current device until one works (yay!) or they all fail. It's so stupid that you can even call it recursively (this is how transparent gunzipping works, and why the files have to have different names). -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message