The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Lyndon Nerenberg <lyndon@orthanc.ca>
To: arnold@skeeve.com
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] The origin of /home
Date: Thu, 11 Oct 2018 12:10:43 -0700	[thread overview]
Message-ID: <7aa20b6d9fcbce7d@orthanc.ca> (raw)
In-Reply-To: <201810101626.w9AGQ1Wt028098@freefriends.org>

arnold@skeeve.com writes:
> Norman Wilson <norman@oclsc.org> wrote:

> > a.  It no longer matters a whit whether the (real) root file
> > system can fit into a 5MB slice of the disk or the like, so
> > just merge everything that spilled into /usr in the tiny-disk
> > days back into the root where it belongs.

> Plan 9 did exactly that, no?

Yes, but no.  With namespaces, There Is No Root.  You can pretzel up
the filesystem to your heart's content, and nobody else will ever know.

But on the filserver, there are some required conventions.

* /usr is for home directories

* /bin is an empty mountpoint

* /sys contains "the system" in the form of reference files, configs,
  source code, etc.

* /lib is a semi-sparse directory tree that non-system programs can use
  to store data/configs/etc.

* every CPU architecture gets its own top level directory (e.g.
  /386,  /sparc, ...)

But the fileserver conventions are only there because the cpu/terminal
diskless boot scripts need a basically consistent fileserver
environment to do their initial bootstrap from.  After that, the
namespace is your to pervert at your pleasure.  And such perversion
is actively encouraged :-)

http://doc.cat-v.org/plan_9/4th_edition/papers/9 (e.g. "Implementation of Name Spaces")

http://doc.cat-v.org/plan_9/4th_edition/papers/names

--lyndon

  reply	other threads:[~2018-10-11 19:11 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-10 14:43 Norman Wilson
2018-10-10 16:26 ` arnold
2018-10-11 19:10   ` Lyndon Nerenberg [this message]
2018-10-10 17:08 ` Grant Taylor via TUHS
2018-10-11  0:22   ` Steve Nickolas
2018-10-11  2:33     ` David Arnold
  -- strict thread matches above, loose matches on Subject: below --
2018-10-10 15:26 Noel Chiappa
2018-10-10 15:45 ` Clem Cole
2018-10-10 15:48   ` David
2018-10-13  6:58   ` Michael Kjörling
2018-10-12  0:15 ` Dave Horsfall
2018-09-28  2:39 Doug McIlroy
2018-09-27 23:14 Noel Chiappa
2018-09-28  5:27 ` Lars Brinkhoff
2018-09-27 15:33 Noel Chiappa
2018-09-27 20:15 ` Dan Cross
2018-09-27 14:31 Noel Chiappa
2018-09-27 12:08 Cág
2018-09-27 12:30 ` Alec Muffett
2018-09-27 12:58 ` Donald ODona
2018-09-27 13:54   ` John P. Linderman
2018-09-27 14:09     ` Ronald Natalie
2018-09-27 14:18     ` Jon Forrest
2018-09-27 14:28       ` Arrigo Triulzi
2018-09-27 15:36         ` Jon Forrest
2018-09-27 15:54           ` Arrigo Triulzi
2018-09-27 18:49             ` Jon Forrest
2018-09-28  0:50               ` Theodore Y. Ts'o
2018-10-01  1:52                 ` Lyndon Nerenberg
2018-10-10  2:38               ` Dave Horsfall
2018-10-10  3:07                 ` Grant Taylor via TUHS
2018-09-27 17:33   ` Donald ODona
2018-09-27 14:47 ` Dan Cross
2018-09-27 17:20   ` arnold
2018-09-27 20:42   ` Cág
2018-09-27 21:07     ` Dan Cross
2018-09-27 22:04       ` Clem Cole
2018-09-27 22:18         ` Henry Bent
2018-09-28  8:33   ` Tony Finch
2018-09-28 18:23     ` Jeremy C. Reed
2018-09-28 16:02 ` Nemo
2018-09-28 16:15   ` Grant Taylor via TUHS
2018-09-28 17:28     ` Arthur Krewat
2018-09-28 19:38       ` Grant Taylor via TUHS
2018-09-28 19:47       ` Grant Taylor via TUHS
2018-09-28 20:30         ` Arthur Krewat
2018-09-28 20:00     ` Nemo
2018-09-28 21:07       ` Grant Taylor via TUHS

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=7aa20b6d9fcbce7d@orthanc.ca \
    --to=lyndon@orthanc.ca \
    --cc=arnold@skeeve.com \
    --cc=tuhs@tuhs.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;
as well as URLs for NNTP newsgroup(s).