From: Alec Muffett <alec.muffett@gmail.com>
To: Cág <ca6c@bitmessage.ch>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] The origin of /home
Date: Thu, 27 Sep 2018 13:30:15 +0100 [thread overview]
Message-ID: <CAFWeb9+C5+=rXopr_No8MSSsPNU3-DJuSwM1NfyETLF7cfK=6w@mail.gmail.com> (raw)
In-Reply-To: <20180927120854.u8rei%ca6c@bitmessage.ch>
[-- Attachment #1: Type: text/plain, Size: 752 bytes --]
Opinion, predating that era: I believe that the driver for /home was
automounter, because of the complexity of referencing local and remote
/export/foo/whatever/username paths consistently across a large NFS-enabled
university deployment with many different platforms and individual systems.
On Thu, 27 Sep 2018, 13:11 Cág, <ca6c@bitmessage.ch> wrote:
> Hi,
>
> 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?
>
> Thanks!
>
> --
> caóc
>
>
[-- Attachment #2: Type: text/html, Size: 1049 bytes --]
next prev parent reply other threads:[~2018-09-27 12:30 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 [this message]
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
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='CAFWeb9+C5+=rXopr_No8MSSsPNU3-DJuSwM1NfyETLF7cfK=6w@mail.gmail.com' \
--to=alec.muffett@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).