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 10:47:21 -0400	[thread overview]
Message-ID: <CAEoi9W5mnNCUFWWUVs++=adNP7FfB1=iqH6sv5nRF=DxWRHLXA@mail.gmail.com> (raw)
In-Reply-To: <20180927120854.u8rei%ca6c@bitmessage.ch>

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

On Thu, Sep 27, 2018 at 8:11 AM Cág <ca6c@bitmessage.ch> wrote:

> The earliest I've found to be in the FHS from '94. Are there any earlier
> examples of a home directory being at /home instead of /usr/$(user)? Are
> there any current Unix systems that don't use /home by default (except
> OSX)? Does anybody here do it intentionally? Also, what was the
> rationale of moving the directory to /home?
>

Naming on Unix (and derived systems) is one of those things that has always
had different schools of thought applied to it.

As has been pointed out, the original place for what we now refer to as
"home" directories was /usr, though this may not be entirely accurate: it's
my belief that PDP-7 Unix had separate directories for each user, but I
don't think these were nested under a common 'usr' directory. Someone
please correct me if I'm wrong. The original impetus for moving things
around was surely space considerations on early disk devices: Not only was
space limited, but filesystems couldn't span devices (in the /dev sense)
and often *partition* sizes on a single volume were fixed by the driver for
the underlying storage device. In such a rigidly defined world, varying
conventions would necessary evolve to work around the inevitable
limitations, particular in sites with lots of users like universities and
production-focused corporate groups, including the degeneration of `/usr`
as purely holding user directories. One can easily imagine the
conversation: "we're out of room on the root filesystem and I can't install
this new program in /bin..." "Hmm. Well, we've got space in /usr: create
/usr/bin and we'll fix up the difference in the shell by incorporating some
notion of a search path for binaries." Similarly with lib, man, and all the
rest of it. It's interesting that now /usr is most often devoid of user
data; the intent behind the name seems to be justified after the fact by
asserting that it contains programs, libraries and other data of interest
to users (as opposed to administrators).

That explains why other things starting encroaching and eventually took
over on /usr, but I think the provenance of "/home" specifically relates to
an etymological question. At some point, the "user's directory" as  denoted
in /etc/passwd became known as the "home directory." If that was common
vernacular by the time that `/home` came around as a convention, then it
seems a logical name stemming from that usage. The more intriguing
possibility from the antiquarian point of view is whether someone coined
"/home" and then THAT led to the rise of the "home directory" nomenclature.
man(5) on 7th Edition calls that field the user's "initial working
directory." The first time I see it called "home directory" in my cursory
search is in 4.3 Reno.

I intentionally eschew /home on a few systems. 4.4BSD had a convention of
placing user home directories in /a, /b, etc. 4.4BSD-Lite also had
/var/users. Both of which I occasionally use.

        - Dan C.

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

  parent reply	other threads:[~2018-09-27 14:48 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 [this message]
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
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='CAEoi9W5mnNCUFWWUVs++=adNP7FfB1=iqH6sv5nRF=DxWRHLXA@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).