Date: Sun, 25 Mar 2001 06:07:52 +0200 From: "Karsten W. Rohrbach" <karsten@rohrbach.de> To: bv@bilver.wjv.com Cc: freebsd-fs@freebsd.org Subject: Re: Design a journalled file system Message-ID: <20010325060752.A28058@rohrbach.de> In-Reply-To: <20010227101911.A88501@wjv.com>; from bill@bilver.wjv.com on Tue, Feb 27, 2001 at 10:19:11AM -0500 References: <20010226221132.C20550@prism.flugsvamp.com> <200102270620.XAA13824@usr05.primenet.com> <20010227084658.D20550@prism.flugsvamp.com> <20010227101911.A88501@wjv.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Bill Vermillion(bill@bilver.wjv.com)@Tue, Feb 27, 2001 at 10:19:11AM -0500: > On Tue, Feb 27, 2001 at 08:46:58AM -0600, Jonathan Lemon thus spoke: > Is my mind playing tricks on me? I seem to recall that on an SGI > there is a separte boot file system then the XFS. It's been a > couple of years now - but I convertned several from the 5.x to the > 6.x Irix with the new XFS. yeah afaik there is a separate partition/slice/whatsoever that holds the boot files. > > Why does the boot file system have to be the same as a running > file-system. I know that in some of the Sys V.x Intel variants, > there is a separate booting file system conforming to the old > s51 file system because the newer file systems they use wont > boot in an iNTEL environment. i know some people will ignite their flamethrowers now but <asbestos suit> i like the idea behind /dev/ipldevice on ibm aix. its just container for some very simple structure that holds the files needed to boot as far as devices and other drivers are loaded to get into the next stage and kinda kldload(8) the other drivers and stuff before commencing the real rc stuff. this means -- in the simplest implementation -- having a partition, lets say /dev/da0e with approx. 10 mb size and symlinking it to /dev/bootdevice. then some administration model like linux' lilo has to be run where the image of the boot file system gets assembled somehow. dirty hack: having a directory /bootstage where all the files (loader, rcfiles, kernel, modules) are copied in and cd /bootstage && find .|cpio -o /dev/bootdevice now the loader has to grok cpio or tar format. </asbestos suit> very stable and convenient way. to be suitable for production use there has to be some kind of selection mechanism for the old setup but that's not a big point in discussion i guess. cheers, /k -- > LET Jesus be YOUR anchor! When Satan rocks your boat, THROW Jesus overboard! KR433/KR11-RIPE -- http://www.webmonster.de -- ftp://ftp.webmonster.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010325060752.A28058>