From: Brantley Coile <brantley@prepaynt.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] FS question
Date: Mon, 10 Nov 2003 12:14:04 -0500 [thread overview]
Message-ID: <opryfl5qnarveh1e@smtp.borf.com> (raw)
In-Reply-To: <E1AJDe3-000OTx-KE@t40.swtch.com>
On Mon, 10 Nov 2003 10:07:47 -0500, Russ Cox <rsc@swtch.com> wrote:
>> I was just curious to the reasoning behind dropping links.
>> Did, for example, Ken's FS not do links because Plan 9 had
>> bind or did Plan 9 use bind because, possibly among other reasons,
>> FS didn't do any links. Or was it just an accident of
>> design, a side affect of putting the file name in the meta data?
>
> I have no idea (I wasn't there), but I have a question for you.
>
> If you were designing a file system today, from scratch,
> and you weren't worried about backwards compatibility,
> would you actually structure it the same way as the UNIX
> file system, with inodes and links? What a mess.
>
>
Since I learned from UNIX, there is a very real chance that
I would structure it that way. It's what I grew up with.
Why was putting the name in the metat good in 1987 but bad
in 1969?
Brantley
next prev parent reply other threads:[~2003-11-10 17:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-10 14:01 Brantley Coile
2003-11-10 15:07 ` Russ Cox
2003-11-10 17:14 ` Brantley Coile [this message]
2003-11-10 17:43 ` Russ Cox
2003-11-10 17:49 ` Sape Mullender
2003-11-11 1:47 ` Dennis Ritchie
2003-11-11 0:01 ` Geoff Collyer
2003-11-13 0:10 ` Charles Forsyth
2003-11-10 16:40 ` Rob Pike
2003-11-10 17:09 ` Brantley Coile
2003-11-10 17:39 ` ron minnich
2003-11-11 2:30 bruce
2003-11-11 10:26 ` Bruce Ellis
2003-11-11 12:28 ` Lucio De Re
2003-11-12 11:13 ` Boyd Roberts
2003-11-12 19:55 ` Andrew Simmons
2003-11-12 20:17 ` Brantley Coile
2003-11-12 21:18 ` boyd, rounin
2003-11-12 21:16 ` boyd, rounin
2003-11-13 9:32 ` Skip Tavakkolian
2003-11-13 16:47 ` Dan Cross
2003-11-14 6:49 Andrew Simmons
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=opryfl5qnarveh1e@smtp.borf.com \
--to=brantley@prepaynt.com \
--cc=9fans@cse.psu.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;
as well as URLs for NNTP newsgroup(s).