From: Bryan Simmons <bsimmo1@gl.umbc.edu>
To: Jude DaShiell <jdashiel@shellworld.net>
Cc: jbradford@dial.pipex.com, pa3gcu@zeelandnet.nl,
linux-newbie <linux-newbie@vger.kernel.org>
Subject: Re: CD-ROM settings and hardware resources...
Date: 25 Oct 2002 06:00:45 -0400 [thread overview]
Message-ID: <1035540045.18011.0.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.BSF.4.44.0210250441590.3791-100000@server1.shellworld.net>
Actually, yes. I believe that JFS, XFS and ReiserFS all use B+ trees to
manage files in a directory.
On Fri, 2002-10-25 at 04:42, Jude DaShiell wrote:
> Do any of the Linux file systems use a tree rather than linked lists?
>
>
>
> On 24 Oct 2002, Bryan Simmons wrote:
>
> > Shows how much I know about basic system design...
> >
> > In fact, I was shocked to learn last night that ext2 uses linked lists
> > to keep track of files in a directory. Why is this? Did the guys who
> > wrote the file system specs go to school for computer science? I can't
> > tell you how many times my cmsc professors have told us that the linked
> > list is totally inferior to the tree. At least, it is when it comes to
> > large sets of data. Perhaps the ext2 guys never saw the need for
> > extremely large sets of files in a single directory, but still, even
> > when hashing, it is suggested that you not handle collisions with linked
> > lists...
> > Stacks and queues are one thing (when used for temporary operations,
> > like iterators and memory management). But persistent data is another.
> > I would never want to store stuff in a list if it is always going to be
> > accessed, growing and shrinking...
> >
> > On Thu, 2002-10-24 at 07:11, jbradford@dial.pipex.com wrote:
> > > > > Does anyone know a way around this? I can't hardly believe that all the
> > > > > millions of Linux users have been, and still are, stuck with CD-RWs that
> > > > > have to masquerade as SCSI devices.
> > > >
> > > > There is no way around it, simply read the proper documentation, in this case
> > > > the CD-Writing HOWTO.
> > > > IDE-ATAPI CD-RW devices only work with SCSI emulation as they only do in
> > > > widows as well.
> > > > If you find a better way you can tell us millions how you did it then.
> > >
> > > There will soon be a better way - Linus himself mentioned using the
> > > standard IDE devices for cd recording, last Tuesday.
> > >
> > > Expect to see cd recording with native IDE devices once the 2.6 kernel
> > > is ready.
> > >
> > > Incidently, IDE devices masquerading as SCSI is not as unusual as it
> > > might first appear - ATAPI is basically a way to send SCSI commands
> > > over the IDE bus.
> > >
> > > John.
> > > -
> > > To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
> > > the body of a message to majordomo@vger.kernel.org
> > > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > > Please read the FAQ at http://www.linux-learn.org/faqs
> > --
> > Regards,
> >
> > Bryan Simmons
> > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> >
> > On Integrity:
> >
> > "I'm going to be as good as they let me and
> > as mean as they make me, and they all know
> > that. I don't ever lie. If I tell you a
> > rooster can fly, get the harness."
> >
> > --Burl Cain, Louisiana State Pen Warden
> > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.linux-learn.org/faqs
> >
--
Bryan Simmons <bsimmo1@gl.umbc.edu>
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2002-10-25 10:00 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <MSGID_110=3a10=2f1.2_8d16c3d8@linuxnet>
2002-10-22 13:25 ` CD-ROM settings and hardware resources Robert Couture
2002-10-22 19:45 ` Bryan Simmons
2002-10-23 15:49 ` pa3gcu
2002-10-23 19:20 ` Bryan Simmons
2002-10-23 19:34 ` Ray Olszewski
2002-10-23 20:36 ` pa3gcu
2002-10-23 21:51 ` Bryan Simmons
2002-10-24 6:40 ` pa3gcu
2002-10-24 10:35 ` Bryan Simmons
2002-10-24 14:04 ` pa3gcu
2002-10-24 7:01 ` Ray Olszewski
2002-10-24 10:40 ` Bryan Simmons
[not found] ` <1035409609.31016.29.camel@localhost.localdomain>
2002-10-24 6:35 ` pa3gcu
2002-10-24 16:04 ` jbradford
2002-10-24 16:10 ` Ray Olszewski
2002-10-24 11:11 ` jbradford
2002-10-24 13:24 ` Bryan Simmons
2002-10-25 8:42 ` Jude DaShiell
2002-10-25 10:00 ` Bryan Simmons [this message]
2002-10-25 10:06 ` Bryan Simmons
2002-10-25 13:04 ` Linux Mount Partitions Abhijit Vijay
2002-10-25 13:32 ` Paul Furness
2002-10-25 14:12 ` Steven Smith
2002-11-07 8:28 CD-ROM settings and hardware resources Calin Szonyi
-- strict thread matches above, loose matches on Subject: below --
2002-10-18 19:23 CD-ROM settings and bash resources Bryan Simmons
2002-10-19 23:09 ` Ray Olszewski
2002-10-20 5:46 ` CD-ROM settings and hardware resources Bryan Simmons
2002-10-20 5:58 ` Bryan Simmons
2002-10-20 6:29 ` Ray Olszewski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1035540045.18011.0.camel@localhost.localdomain \
--to=bsimmo1@gl.umbc.edu \
--cc=jbradford@dial.pipex.com \
--cc=jdashiel@shellworld.net \
--cc=linux-newbie@vger.kernel.org \
--cc=pa3gcu@zeelandnet.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox