From: arnold@skeeve.com
To: crossd@gmail.com, ca6c@bitmessage.ch
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] The origin of /home
Date: Thu, 27 Sep 2018 11:20:11 -0600 [thread overview]
Message-ID: <201809271720.w8RHKBNh031105@freefriends.org> (raw)
In-Reply-To: <CAEoi9W5mnNCUFWWUVs++=adNP7FfB1=iqH6sv5nRF=DxWRHLXA@mail.gmail.com>
Dan Cross <crossd@gmail.com> wrote:
> 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.
It most definitely was common usage before /home came along.
As I recall it, in the System V Release 4 time frame, AT&T, Sun, DEC and
UCB agreed on the division of things into /home, /usr, and /var, with
the impetus being that /usr could be mounted read-only from a single file
server (saving many copies of the same files), /home mounted read-write
(or automounted) and /var holding things that were peculiar to each
system but read-write, such as log files and temporary files.
Diskless workstations, or workstations with very small disks for
holding the root filesystem only, were very popular at the time.
Arnold
next prev parent reply other threads:[~2018-09-27 17:20 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 [this message]
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=201809271720.w8RHKBNh031105@freefriends.org \
--to=arnold@skeeve.com \
--cc=ca6c@bitmessage.ch \
--cc=crossd@gmail.com \
--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).