From: Jesse Pollard <pollard@tomcat.admin.navo.hpc.mil>
To: mwood@IUPUI.Edu, unlisted-recipients:; (no To-header on input)
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Alright, I give up. What does the "i" in "inode" stand for?
Date: Tue, 30 Jul 2002 15:58:40 -0500 (CDT) [thread overview]
Message-ID: <200207302058.PAA92524@tomcat.admin.navo.hpc.mil> (raw)
--------- Received message begins Here ---------
>
> On Fri, 19 Jul 2002, Jesse Pollard wrote:
> [snip]
> > In even earlier OSs (DEC RSX, TOPS 10) the file index table was actually a file
> > in the filesystem (usually named index.idx (or was it file.idx...).
>
> INDEXF.SYS, on TOPS-10.
>
> > I don't
> > know what it was called in MULTICs where the UNIX varient would have
> > started.
> >
> > Most of these filesystems were based on contigeuous allocation, or allocations
> > of contigeous segments.
>
> "Extents". "Segments" were contiguous hunks of real memory that the MMU
> knew about, then as now.
I'll accept extents - the "segment" reference was wrong.
> [snip]
> > Note - the version number had nothing to do with the file version -
> > it was used to aid file recovery and was only a reuse count of the index
> > node. The index node contents had to have the same version number as the
> > directory entry, or the directory entry was considered invalid. The
> > file name was a rad50, or sixbit (packed) characters, and sometimes was
> > stored in both inode and directory - again, for rebuilding the file system.
>
> No, RAD50 and SIXBIT are different. You can (de)compose SIXBIT words with
> simple shift-and-mask operations, but RAD50 requires arithmetic. (Hmmm,
> on TOPS-10 we called it RADIX50, so maybe it's different.)
Definitely different. RAD50 was used in FILES-11 and RT-11 disks. It was used
to store 3 characters in a 16 bit word. SIXBIT was used on TOPS-10 36bit
systems to store 6 characters in a word. It also allowed for a fast file
name search since the names were all on word boundaries (full filename
compair took 2 compair, and 1 mask operation 6+3 file names).
> --
> Mark H. Wood, Lead System Programmer mwood@IUPUI.Edu
> Who just last weekend rediscovered an MF10 core-plane hiding in the filing
> cabinet.
Still got the manuals ? :-)
-------------------------------------------------------------------------
Jesse I Pollard, II
Email: pollard@navo.hpc.mil
Any opinions expressed are solely my own.
next reply other threads:[~2002-07-30 20:55 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-30 20:58 Jesse Pollard [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-25 13:54 Jesse Pollard
2002-07-20 2:51 Kevin Puetz
[not found] <fa.m2aun2v.khulp2@ifi.uio.no>
2002-07-20 2:20 ` Kevin Buhr
2002-07-19 13:32 Jesse Pollard
2002-07-30 20:07 ` Mark H. Wood
2002-07-19 13:21 Nicholas Berry
2002-07-19 5:08 Mohamed Ghouse , Gurgaon
2002-07-18 22:33 Rob Landley
2002-07-19 4:38 ` Kelledin
2002-07-19 4:38 ` Larry McVoy
2002-07-19 4:45 ` CaT
2002-07-18 23:34 ` Rob Landley
2002-07-19 5:40 ` Thunder from the hill
2002-07-19 0:21 ` Rob Landley
2002-07-19 12:38 ` Kelledin
2002-07-19 13:09 ` Ryan Cumming
2002-07-19 7:00 ` dalecki
2002-07-19 19:58 ` Måns Rullgård
2002-07-19 20:17 ` Cort Dougan
2002-07-20 1:06 ` Kelsey Hudson
2002-07-19 14:20 ` yodaiken
2002-07-20 14:22 ` Georg Nikodym
2002-07-20 14:31 ` yodaiken
2002-07-22 13:10 ` Jesse Pollard
2002-07-20 6:01 ` John Kacur
2002-07-19 4:52 ` Albert D. Cahalan
2002-07-22 22:23 ` Joe DiMartino
2002-07-22 22:49 ` Hiten Pandya
2002-07-25 0:24 ` Daniel Mose
2002-07-25 1:16 ` Andrew Rodland
2002-07-25 2:43 ` jw schultz
2002-07-25 3:18 ` Christian Lavoie
2002-07-25 5:30 ` Ross Vandegrift
2002-07-25 11:08 ` Alan Cox
2002-07-25 6:03 ` Thunder from the hill
2002-07-26 8:24 ` jbradford
2002-07-28 9:01 ` Thunder from the hill
2002-08-04 15:11 ` Gert Menke
2002-07-26 12:54 ` Rob Landley
2002-07-25 18:06 ` Kevin Buhr
2002-07-26 23:39 ` Daniel Mose
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=200207302058.PAA92524@tomcat.admin.navo.hpc.mil \
--to=pollard@tomcat.admin.navo.hpc.mil \
--cc=linux-kernel@vger.kernel.org \
--cc=mwood@IUPUI.Edu \
/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
Powered by JetHome