git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: walt <wa1ter@myrealbox.com>
Cc: git@vger.kernel.org
Subject: Re: Does git belong in root's $PATH?
Date: Sat, 07 Jan 2006 19:00:23 -0800	[thread overview]
Message-ID: <43C08047.6090701@zytor.com> (raw)
In-Reply-To: <dpppg4$qkd$1@sea.gmane.org>

walt wrote:
> H. Peter Anvin wrote:
> 
>>/usr used to be what is now called /home.  What you're describing above
>>is the current usage.
> 
> History lessons are valuable for us youngsters ;o)  Can you give us a
> brief description of what motivated such a change?  (Just as important,
> of course, is whether the original motives have changed or disappeared.)
> 

This is the history as far as I understand it.  Keep in mind I was only 
8 years old in 1980, and I think I first learned about how Unix worked 
in 1985 or 1986, so not all of this is first-hand.

/usr was initially used for home directories (user directories.)  Both 
fore reasons as have been previously discussed (remember, most easy 
multi-user systems were a lot friendlier than one would expect today), 
and because the root disk often filled up, it became common for users to 
put binaries in /usr/bin, and often the sysadmin, too.

As the need for system security tightened, by the 80's this was a pretty 
unusable configuration.  Since home directories were specified in 
/etc/passwd, those could, and often were, located elsewhere -- much 
easier than trying to change the now-established conventions of /usr/bin 
et al.  A lot of systems in the 80's were massively multiuser anyway 
(workstations were coming in but were rare), and so you'd frequently see 
paths like /u2/h/hpa for example (my actual home directory location on 
our college server.)

The convention of using /home for home directories seems to have evolved 
out of necessity when networking came in use on a large scale (NFS, 
automounter, etc), probably in the late 80's-early 90's.  By the time 
Linux emerged in 1991 it was pretty well-established on smaller systems; 
larger systems still tended to use local conventions inherited from 
previous generation systems.

	-hpa

  reply	other threads:[~2006-01-08  3:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-07 17:21 Does git belong in root's $PATH? walt
2006-01-07 18:03 ` Andreas Ericsson
2006-01-07 20:40   ` H. Peter Anvin
2006-01-08  0:37     ` Andreas Ericsson
2006-01-08  0:39       ` H. Peter Anvin
2006-01-08  1:22         ` walt
2006-01-08  3:00           ` H. Peter Anvin [this message]
2006-01-07 18:31 ` Linus Torvalds
2006-01-07 20:49   ` H. Peter Anvin
2006-01-07 23:01   ` Sam Ravnborg

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=43C08047.6090701@zytor.com \
    --to=hpa@zytor.com \
    --cc=git@vger.kernel.org \
    --cc=wa1ter@myrealbox.com \
    /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).