From owner-freebsd-arch Thu Apr 27 0:17:36 2000 Delivered-To: freebsd-arch@freebsd.org Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (Postfix) with ESMTP id 465B337BE52 for ; Thu, 27 Apr 2000 00:17:30 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.3/8.9.3) with ESMTP id JAA23330 for ; Thu, 27 Apr 2000 09:17:21 +0200 (CEST) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id JAA00207 for freebsd-arch@freebsd.org; Thu, 27 Apr 2000 09:17:16 +0200 (CEST) Received: from mass.cdrom.com (adsl-63-202-176-132.dsl.snfc21.pacbell.net [63.202.176.132]) by hub.freebsd.org (Postfix) with ESMTP id 25ED037B5A0 for ; Wed, 26 Apr 2000 23:21:31 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id XAA00679; Wed, 26 Apr 2000 23:29:10 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200004270629.XAA00679@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Terry Lambert Cc: rkw@dataplex.net (Richard Wackerbarth), doconnor@gsoft.com.au (Daniel O'Connor), freebsd-arch@freebsd.org Subject: Re: How about building modules along with the kernel? In-reply-to: Your message of "Wed, 26 Apr 2000 18:40:13 -0000." <200004261840.LAA06879@usr09.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 26 Apr 2000 23:29:10 -0700 From: Mike Smith Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > The loader can (and does) already read UFS.. > > > > > > It can read files in and load them into arbitarily named sections in the > > > kernel, and other good things :) > > > > But what about JFS, E2FS, KFS, etc. ? > > Historical UNIX implementations have handled this with a > flat filesystem, usually called "stand", where the kernel and > any modules needed to access the locally instantiated filesystem > implementations are installed. > > NT's boot loader approaches this the same way, though their > "stand" is actually a FAT partition. We have this already; it's called /, and the format is UFS. If you want to get really anal, change the module search path to include somewhere under /boot, and make that a FAT filesystem (we support those as well). The reason that these other systems use a separate filesystem of a simpler type is that their bootloaders are _lame_. Ours isn't, and it doesn't need a new filesystem type just to cater to its' braindeath. Either use FAT or UFS, or teach the loader (libstand) about your new filesystem types. If you're going to implement a filesystem for FreeBSD, writing loader support for it is just about the most trivial part - probably on par with the manpage. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message