9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Keith Nash <kjn9@citizenearth.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] File server for NT
Date: Fri, 16 May 2003 09:22:58 +0000	[thread overview]
Message-ID: <20030516092258.8907.qmail@mail.dirac.net> (raw)

> it never was on lunix, but on plan 9 your path had to be:
>
>    .
>    /bin
>
> to preserve some sort of semantic sanity, given 'everyone is a mortal' on
> plan 9.

Putting "." at the head of the path means that a system tool will be overridden by anything in the current directory that happens to have the same name.  This practice is not advised in Lunix; I have often wondered why it was adopted in Plan 9.

Telling Plan 9 to execute dir/tool causes it to look for $path/dir/tool, not ./dir/tool - a consistent and elegant choice of design.

I'm not sure whether by 'semantic sanity' you mean preserving an aspect of Lunix' inconsistency in order to provide users with a familiar environment.  This isn't the choice that Plan 9's designers usually made.

Does anything break if path is set to just "/bin", or to "/bin ."?  For example, in
cd foo
mk
developers are free to place their own substitutes for system commands along with their source files in directory foo.  Does the official Plan 9 software ever do this?  Even if it doesn't, 3rd-party software might, which suggests that we are stuck with using the ". /bin" default for ever.



             reply	other threads:[~2003-05-16  9:22 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-16  9:22 Keith Nash [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-16  3:53 Andrew Simmons
2003-05-16  5:00 ` William K. Josephson
2003-05-16  6:03   ` William K. Josephson
2003-05-16 11:38   ` Andrew Simmons
2003-05-16 12:55     ` Russ Cox
2003-05-19  9:45       ` Andrew Simmons
2003-05-16 13:43     ` rog
     [not found] <andrew.simmons@monitorbm.co.nz>
2003-05-16  0:28 ` Andrew Simmons
2003-05-16  0:28   ` Scott Schwartz
2003-05-16  1:04   ` William Josephson
2003-05-16  2:06     ` Dan Cross
2003-05-16  6:25       ` boyd, rounin
2003-05-16 13:46         ` rog
2003-05-16 13:20           ` Sam
2003-05-16 14:26       ` ron minnich
2003-05-16 15:23         ` andrey mirtchovski
2003-05-16 16:02           ` Dan Cross
2003-05-19  9:46             ` boyd, rounin
2003-05-16 16:08           ` Russ Cox
2003-05-16 16:17           ` ron minnich
2003-05-16 22:07             ` Geoff Collyer
2003-05-16 23:32               ` northern snowfall
2003-05-16 22:37                 ` Geoff Collyer

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=20030516092258.8907.qmail@mail.dirac.net \
    --to=kjn9@citizenearth.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).