From: "Bruce Ellis" <brucee@chunder.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] FS question
Date: Tue, 11 Nov 2003 21:26:24 +1100 [thread overview]
Message-ID: <00b201c3a83e$4cc58e40$8201a8c0@cc77109e> (raw)
In-Reply-To: <200311110230.hAB2UJg18931@cpu1.cs.usyd.edu.au>
that's not me. just in case you guys thought i'd gone into IT.
brucee
----- Original Message -----
From: <bruce@it.usyd.edu.au>
To: <9fans@cse.psu.edu>
Sent: Tuesday, November 11, 2003 1:30 PM
Subject: Re: [9fans] FS question
> If a file could be removed but still remain accessible
> (via an open file descriptor) then that might suggest an implementation
> where the file was distinct from its name. Once that separation
> existed then it might have been thought interesting to allow
> multiple names for the same file.
>
> What did Multics do?
> ken?
next prev parent reply other threads:[~2003-11-11 10:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-11 2:30 bruce
2003-11-11 10:26 ` Bruce Ellis [this message]
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 0:34 ` [9fans] Bruce Michael Baldwin
2003-11-13 9:32 ` [9fans] FS question Skip Tavakkolian
2003-11-13 16:47 ` Dan Cross
-- strict thread matches above, loose matches on Subject: below --
2003-11-14 6:49 Andrew Simmons
2003-11-10 14:01 Brantley Coile
2003-11-10 15:07 ` Russ Cox
2003-11-10 17:14 ` Brantley Coile
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
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='00b201c3a83e$4cc58e40$8201a8c0@cc77109e' \
--to=brucee@chunder.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).