Date: Mon, 26 Mar 2001 12:15:40 -0500 From: Coleman Kane <cokane@FreeBSD.ORG> To: "Karsten W. Rohrbach" <karsten@rohrbach.de> Cc: bv@wjv.com, freebsd-fs@FreeBSD.ORG Subject: Re: Design a journalled file system Message-ID: <20010326121540.B83061@cokane.yi.org> In-Reply-To: <20010325060752.A28058@rohrbach.de>; from karsten@rohrbach.de on Sun, Mar 25, 2001 at 06:07:52AM %2B0200 References: <20010226221132.C20550@prism.flugsvamp.com> <200102270620.XAA13824@usr05.primenet.com> <20010227084658.D20550@prism.flugsvamp.com> <20010227101911.A88501@wjv.com> <20010325060752.A28058@rohrbach.de>
next in thread | previous in thread | raw e-mail | index | archive | help
--DBIVS5p969aUjpLe Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable All those things that intel systems are expected to conform to are just BIOS restrictions. The nice thing about IBMs, Suns, and many other non-PC workstations is that they have a nice BIOS system designed to handle such things as the ipldevice, etc. Intel systems, without BIOS, simply just start executing whatever is at 0xffff0 (i think that's it, towards the end of memory anyway), which typically is where the BIOS chip is mapped/wired. If PC BIOSes weren't so brain-dead we could have all sorts of useful features (e.g.: 386 and 486 hardware does have the ability to boot from ATA CD, but the BIOS doesn't know how to find it). Anyway, many linux-based distro's use a seperate small partition to boot the kernel, typically if the driver for the boot device is not compiled in the kernel. The loading mechanism is pretty different though, and I don't really see the advantage in the BSD's. At least, not until we run into the problem where our loader can't get the kernel off the boot device. That's what all the _ROOT macros in config are for. Karsten W. Rohrbach had the audacity to say: >=20 > Bill Vermillion(bill@bilver.wjv.com)@Tue, Feb 27, 2001 at 10:19:11AM -050= 0: > > 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. =20 > yeah afaik there is a separate partition/slice/whatsoever that holds the > boot files. >=20 > >=20 > > 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=20 > cd /bootstage && find .|cpio -o /dev/bootdevice > now the loader has to grok cpio or tar format. > </asbestos suit> >=20 > 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. >=20 > cheers, > /k >=20 > --=20 > > LET Jesus be YOUR anchor! When Satan rocks your boat, THROW Jesus overb= oard! > KR433/KR11-RIPE -- http://www.webmonster.de -- ftp://ftp.webmonster.de >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-fs" in the body of the message >=20 --DBIVS5p969aUjpLe Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6v3k7ERViMObJ880RAfjZAJ4qHdEfPdfEeY013NZC9mu2yuSPtACg3/Rl 8c70H3Tv27BSXaLM/XgPw7o= =4YlC -----END PGP SIGNATURE----- --DBIVS5p969aUjpLe-- 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?20010326121540.B83061>