Return to BSD News archive
Newsgroups: comp.os.linux.development.system,comp.unix.bsd.freebsd.misc Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!newshost.telstra.net!act.news.telstra.net!psgrain!newsfeed.internetmci.com!in2.uu.net!mail2news.alias.net!myriad!mylinuxbox!suck!netcom.com!kalessin From: Adam Megacz <kalessin@netcom.com> Subject: Re: Ideal filesystem Content-Type: text/plain; charset=us-ascii Message-ID: <31547526.7B5995A0@netcom.com> Sender: kalessin@netcom17.netcom.com Content-Transfer-Encoding: 7bit Organization: NETCOM On-line Communication Services (408 261-4700 guest) References: <4gejrb$ogj@floyd.sw.oz.au> <4gilab$97u@park.uvsc.edu> <4giqu8$aqk@park.uvsc.edu> <4gira2$a9d@park.uvsc.edu> <hpa.31321eee.I.use.Linux@freya.yggdrasil.com> <4h7t5i$qoh@park.uvsc.edu> <DnoqB4.2sy@pe1chl.ampr.org> <glDH59i00YUvFFjspX@andrew.cmu. <4hptj4$cf4@cville-srv.wam.umd.edu> <3140C968.20699696@netcom.com> <4ia7im$i4m@usenet.srv.cis.pitt.edu> <314A470D.CCE53F0@netcom.com> <4ijs72$cim@josie.abo.fi> <314E0DB7.624ACB10@netcom.com> <4irqph$n9d@josie.abo.fi> Mime-Version: 1.0 Date: Sat, 23 Mar 1996 22:03:18 GMT X-Mailer: Mozilla 2.0 (X11; I; Linux 1.2.13 i486) Lines: 34 Xref: euryale.cc.adfa.oz.au comp.os.linux.development.system:19888 comp.unix.bsd.freebsd.misc:15887 > conceptual cleanliness. when you hear about old traditions, wanting to > overthrow them is well and good, but stopping to wonder how they came > to be old traditions can be good too; the simple byte stream, while > perhaps unpractical for some things, has a few things going for it - > ease of implementation being just one. Yes, but new features are always hard to implement :-) > >> >They reside in the inode, > >> not if you want a fixed-size inode they don't. (i'm under the > >> impression that at least ext2, and probably FFS, use fixed-size > >> one-block inodes; do correct me if i'm mistaken.) > > >HPFS has fixed inode sizes, stores EA's in the inode, and it is the best > >implementation of EA's to date. > > then HPFS surely must have limits on EA size and number? and probably > decently low limits, to avoid wasting ridiculous amounts of disk space > on inodes alone? (i've long wanted to find a good technical paper on > the structure of HPFS; does anybody happen to know of one?) 1) The limit is 64k, which is very generous. EA's can spill over into extra Inodes, but conceptually, they are still part of the origional Inode. Rumor has it that HPFSII (codename Merlin) will eliminate the 64k limit. 2) Check Microsoft (sadly, it was they who invented HPFS). They have a great paper that discusses the power of HPFS, but doesn't give enough information to implement an FS driver. -- Adam Megacz <kalessin@netcom.com> Website ftp://ftp.netcom.com/pub/ka/kalessin/adam.html Linux - OS/2