From: Rob Pike <robpike@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] chdir to mode 000 directory
Date: Sun, 6 Jun 2004 00:33:31 -0700 [thread overview]
Message-ID: <7359f04904060600333d3bca7d@mail.gmail.com> (raw)
In-Reply-To: <d0059d98907ffa0e47b0cb9e86948ab9@orthanc.cc.titech.ac.jp>
> Having understood this semantic, there ocurred a question
> to me. This is yet another departure from UNIX semantics
> isn't it? Why is this so?
plan 9 was not designed by going down a list of unix features
and choosing which ones to change. it was started from
scratch, so many details are different just because they ended
up different, given the overall design. the permission model
was designed from scratch, for instance.
-rob
next prev parent reply other threads:[~2004-06-06 7:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-03 6:01 YAMANASHI Takeshi
2004-06-03 6:19 ` lucio
2004-06-06 7:10 ` YAMANASHI Takeshi
2004-06-06 7:33 ` Rob Pike [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-03 1:58 YAMANASHI Takeshi
2004-06-03 5:49 ` lucio
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=7359f04904060600333d3bca7d@mail.gmail.com \
--to=robpike@gmail.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).