Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site watcgl.UUCP
Path: utzoo!watmath!watcgl!dmmartindale
From: dmmartindale@watcgl.UUCP (Dave Martindale)
Newsgroups: net.unix-wizards
Subject: Re: /lib, /usr/lib, /usr/local/lib
Message-ID: <2460@watcgl.UUCP>
Date: Sun, 22-Apr-84 03:42:41 EST
Article-I.D.: watcgl.2460
Posted: Sun Apr 22 03:42:41 1984
Date-Received: Sun, 22-Apr-84 09:18:53 EST
References: <362@cyb-eng.UUCP>
Organization: U of Waterloo, Ontario
Lines: 21

I've always treated the root filesystem, including /bin and /lib,
as the places you store things that are absolutely necessary for
a bare system (with no other filesystems) to boot and run, and some
tools to let you fix things.  This keeps the root small, and you can
keep emergency copies of it on another disk or on tape easily.

/usr, on the other hand, gets the bulk of the system software.
System stuff mostly goes there - most binaries live in /usr/bin and
most libraries (and other "utility" things) live in /usr/lib.

/usr/local is a nice place to put stuff which belongs on "this" machine
only, or "this group of machines", when it is useful to distinguish it
from things which "everyone" has.

For example, at Waterloo /lib and /usr/lib are identical across all
of the VAXes running UNIX.  /usr/local/lib contains the graphics libraries
which exist only on watcgl.

Does this explanation make sense to you?

	Dave Martindale