The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: ron@ronnatalie.com (Ronald Natalie)
Subject: [TUHS] Understanding the /bin, /sbin, /usr/bin, /usr/sbin Split
Date: Fri, 3 Feb 2012 11:06:13 -0500	[thread overview]
Message-ID: <E1C1F408-6892-4D9E-9739-5104A4E2C48C@ronnatalie.com> (raw)
In-Reply-To: <20120203162216.504c4bb7@cnb.csic.es>


On Feb 3, 2012, at 10:22 AM, Jose R. Valverde wrote:
> 
> 	There was a reason to separate user data from system data to avoid
> the system disk from becoming unusable by a misbehaving user.

But this wasn't practically done in the early UNIX.   Even much that was in /usr was required for normal system operation and there was stuff that got left on the root that was within the user's ability to hose up.    I was system administrator of a V6 UNIX that was used in a University setting in the late 70's.   People banging on the disks was the least of my issues.    There were far more fun ways to crash UNIX (and even PDP-11's in general), break security, etc... that I ran around trying to forestall.

In fact our /usr was on the root disk.   We had two "user" home directory drives /sys1 and /sys2 on two more RK05's. My first quota as a student was 8 blocks (4K).   I supplemented that at first with a dectape (half a megabyte) and then with my own RK05 pack (we reserved two drives for user mounted volumes).    

We swapped to an RF11 fixed head disk of about a megabyte.

The fun one was people trying to ascribe meanings to the "acronyms" on the kernel disk (KEN and DMR).





  reply	other threads:[~2012-02-03 16:06 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-31 19:16 A. P. Garcia
2012-01-31 19:27 ` Warner Losh
2012-02-01 11:12 ` Jose R. Valverde
2012-02-01 17:35   ` Warner Losh
2012-02-02 13:32   ` Random832
2012-02-02 17:24     ` Warner Losh
2012-02-02 17:36       ` John Cowan
2012-02-02 18:10         ` Warner Losh
2012-02-02 21:14         ` Dave Horsfall
2012-02-02 21:49           ` Warner Losh
2012-02-02 22:29             ` Tim Newsham
2012-02-02 22:47               ` Warner Losh
2012-02-02 22:59                 ` Lyndon Nerenberg
2012-02-02 23:33                   ` Warner Losh
2012-03-13 16:09                 ` [TUHS] ASR 37 teletype desired by LCM / Vulcan.com John Foust
2012-02-02 22:53             ` [TUHS] Understanding the /bin, /sbin, /usr/bin, /usr/sbin Split Lyndon Nerenberg
2012-02-02 23:35               ` Warner Losh
2012-02-03 11:10               ` Tim Bradshaw
2012-02-03 15:22                 ` Jose R. Valverde
2012-02-03 16:06                   ` Ronald Natalie [this message]
2012-02-03 16:09                   ` Steve Nickolas
2012-02-02 17:40       ` Warner Losh
2012-02-02 18:02     ` Tim Newsham
2012-02-02 13:45   ` Tim Bradshaw
2012-02-01  9:26 arnold
2012-02-02 13:35 ` Tim Bradshaw
2012-02-02 13:49   ` Larry McVoy
2012-02-02 23:16 Norman Wilson
2012-02-02 23:37 ` Carl Lowenstein
2012-02-02 23:58 ` John Cowan
2012-02-04 19:34 Pepe
2012-02-04 21:05 ` Lyndon Nerenberg
2012-02-05  8:38 Hendrik Jan Thomassen
2012-02-05 10:13 ` Jaap Akkerhuis
2012-02-05 17:15 ` Warner Losh

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=E1C1F408-6892-4D9E-9739-5104A4E2C48C@ronnatalie.com \
    --to=ron@ronnatalie.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).