The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Ronald Natalie <ron@ronnatalie.com>
To: "John P. Linderman" <jpl.jpl@gmail.com>
Cc: The Unix Heritage Society <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] The origin of /home
Date: Thu, 27 Sep 2018 10:09:13 -0400	[thread overview]
Message-ID: <2F919C1F-3C91-4083-9B46-B5A6D28A1D54@ronnatalie.com> (raw)
In-Reply-To: <CAC0cEp_CCi5Tjkm4zq1xiWA4mCduphw_N_kae99ZF7rwfk-bgQ@mail.gmail.com>

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

 Symlinks?   Surely  you jest.   Not in Version 7 or System V.

The idea was to keep root small for convenience in various stages of setup.   /usr was indeed intended to be a separate disk.   If you look at the early distributions like V7, you’ll find the /usr image was a separate tape file.

> On Sep 27, 2018, at 9:54 AM, John P. Linderman <jpl.jpl@gmail.com> wrote:
> 
> More opinion, unencumbered by facts. /usr contained many sudirectories, like /usr/bin and /usr/lib, that were essential to an operational OS. Home directories, on the other hand, persisted unchanged when new releases of an OS were installed. Some of us had symlinks from /usr into a separate file system to make the distinction easier to maintain across releases.
> 
> On Thu, Sep 27, 2018 at 8:58 AM, Donald ODona <mutiny.mutiny@india.com <mailto:mutiny.mutiny@india.com>> wrote:
> At 27 Sep 2018 12:11:15 +0000 (+00:00) from "Cág" <ca6c@bitmessage.ch <mailto:ca6c@bitmessage.ch>>:
> > Hi,
> >
> Also, what was the
> > rationale of moving the directory to /home?
> originally /usr, placed on a separate disk, was what became /home much later. Then disk space of / was running out and more an more applications and libs were moved to the /usr device.
> Much later in the 80ths much more disk space was available and a separate /home was created. Exacly when I don't know, but there was no /home in Ed. 7 but System V release 3 had it already.
> 


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

  reply	other threads:[~2018-09-27 14:15 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 [this message]
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=2F919C1F-3C91-4083-9B46-B5A6D28A1D54@ronnatalie.com \
    --to=ron@ronnatalie.com \
    --cc=jpl.jpl@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).