From: Joe DiMartino <joe@osdl.org>
To: Rob Landley <landley@trommello.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Alright, I give up. What does the "i" in "inode" stand for?
Date: 22 Jul 2002 15:23:12 -0700 [thread overview]
Message-ID: <1027376592.15134.52.camel@joe2.pdx.osdl.net> (raw)
In-Reply-To: <200207190432.g6J4WD2366706@pimout5-int.prodigy.net>
On Thu, 2002-07-18 at 15:33, Rob Landley wrote:
> I've been sitting on this question for years, hoping I'd come across the
> answer, and I STILL don't know what the "i" is short for. Somebody here has
> got to know this. :)
>
Two plausible definitions:
The Magic Garden Explained calls them "information nodes".
A really old (1983) Byte Book called Introducing the Unix System has
this to say:
A file in the UNIX system is described by an object called an
"i-node". We think that the name means "interior node", since
the UNIX file-system is (in principle at least) a directed
graph. For every file there is a single i-node that describes
that file, and contains pointers to blocks that comprise that
file.
So, what do you _want_ it to mean? :-)
- Joe DiMartino
next prev parent reply other threads:[~2002-07-22 22:20 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
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-26 14:15 ` [OT] Why Stallman says GNU/Linux (was Re: Alright, I give up. What does the "i" in "inode" stand for?) Rob Landley
2002-07-19 14:20 ` Alright, I give up. What does the "i" in "inode" stand for? 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 [this message]
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
2002-07-19 5:08 Mohamed Ghouse , Gurgaon
2002-07-19 13:21 Nicholas Berry
2002-07-19 13:32 Jesse Pollard
2002-07-30 20:07 ` Mark H. Wood
[not found] <fa.m2aun2v.khulp2@ifi.uio.no>
2002-07-20 2:20 ` Kevin Buhr
2002-07-20 2:51 Kevin Puetz
2002-07-25 13:54 Jesse Pollard
2002-07-30 20:58 Jesse Pollard
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=1027376592.15134.52.camel@joe2.pdx.osdl.net \
--to=joe@osdl.org \
--cc=landley@trommello.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®