The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Dan Cross <crossd@gmail.com>
To: ca6c@bitmessage.ch
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] The origin of /home
Date: Thu, 27 Sep 2018 17:07:30 -0400	[thread overview]
Message-ID: <CAEoi9W5Ex3RzCzTMDZOUZCG81YZZTqyWfWhuLxeadQfT1JKUcw@mail.gmail.com> (raw)
In-Reply-To: <20180927204237.h3kQJ%ca6c@bitmessage.ch>

[-- Attachment #1: Type: text/plain, Size: 1958 bytes --]

On Thu, Sep 27, 2018 at 4:43 PM Cág <ca6c@bitmessage.ch> wrote:

>
> Thanks for such an interesting and informative answer, Mr. Cross.
>

I'm happy to write it!

Dan Cross wrote:
>
> > 4.4BSD had a convention of placing user home directories in /a, /b,
> > etc.
>
> Do I understand it correctly: they were in just "slash a/b/etc" in
> root? Not /home/a or /usr/a but just /a?
>

Correct. I believe the idea was to program the automounter to make these
appear in some directory like /home, but the directories themselves lived
in /a, /b, etc. Presumably these were mount points for separate
disk-resident filesystems.

> 4.4BSD-Lite also had /var/users.
>
> Was it /var/users/$(user) or /var/$(user)?
>

/var/users/$user. For example, 4.4BSD-Lite1 contains entries for Ken and
Dennis in /etc/master.passwd:

dmr:*:10:31::0:0:Dennis Ritchie:/var/users/guest/dmr:
ken:*:11:31::0:0:& Thompson:/var/users/guest/ken:

To everyone: thanks for all the answers, it's always interesting to read
> such things. I try not to miss a single mail after signing up for the
> list.
>
> This question actually came up long ago when I first tried Plan 9,
> which, as you know, has the directory in /usr, and it was released in
> 90s, after 4.4BSD. Of course, Plan 9 is(not) (Research) Unix, and
> doesn't have a root user, and apparently has a different rationale
> behind it -- if I'm not mistaken, it has bin, lib and something else
> there, none of which are usually present in /home these days, even bin
> is usually in /usr/local.
>

Plan 9 represented an opportunity to do things over. Many of us rather
liked it and thought it was a worthy successor to Unix, but it never caught
on in the larger world and now, in the bathed in the cold light of history,
some of its faults are evident.

The issue with bin/ is that it's in several places. In plan9, these are all
bound onto /bin, which is nice.

        - Dan C.

[-- Attachment #2: Type: text/html, Size: 2944 bytes --]

  reply	other threads:[~2018-09-27 21:08 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
2018-09-27 14:31 Noel Chiappa
2018-09-27 15:33 Noel Chiappa
2018-09-27 20:15 ` Dan Cross
2018-09-27 23:14 Noel Chiappa
2018-09-28  5:27 ` Lars Brinkhoff
2018-09-28  2:39 Doug McIlroy
2018-10-10 14:43 Norman Wilson
2018-10-10 16:26 ` arnold
2018-10-11 19:10   ` Lyndon Nerenberg
2018-10-10 17:08 ` Grant Taylor via TUHS
2018-10-11  0:22   ` Steve Nickolas
2018-10-11  2:33     ` David Arnold
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

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=CAEoi9W5Ex3RzCzTMDZOUZCG81YZZTqyWfWhuLxeadQfT1JKUcw@mail.gmail.com \
    --to=crossd@gmail.com \
    --cc=ca6c@bitmessage.ch \
    --cc=tuhs@minnie.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).