public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "K. Mike Bradley" <kmb@mikienet.com>
To: <gentoo-user@lists.gentoo.org>
Subject: RE: [gentoo-user] Newbie question re: /usr
Date: Tue, 25 Apr 2006 13:12:06 -0400	[thread overview]
Message-ID: <001f01c6688b$614b1050$0300a8c0@samantha> (raw)
In-Reply-To: <7573e9640604250914w5688d024n64b0d6002c693120@mail.gmail.com>

Thank you Richard.
That answers my question very well.




-----Original Message-----
From: richard.j.fish@gmail.com [mailto:richard.j.fish@gmail.com] On Behalf
Of Richard Fish
Sent: Tuesday, April 25, 2006 12:14 PM
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Newbie question re: /usr

On 4/25/06, K. Mike Bradley <kmb@mikienet.com> wrote:
> I wonder if anyone can explain why /usr was created?

The idea is that / can be a very small partition and contains
everything necessary to boot and administer the system, and /usr can
be a separate partition or logical volume.  Some advantages to this
setup are:

1. If the partition containing /usr is corrupted, the system will
still boot, and you have enough tools (fdisk, mkfs, tar, cpio, etc) to
repair and restore it.

2. /usr can be on a network server.

3. On the network server, exporting /usr presents no risk to /.  Even
if /usr is filled up, the server will continue to function and can
still be administered.

This is why:

- command interpreters like bash, ash, etc go in /bin
- network clients and remote shells (ssh, telnet, etc) go in /usr/bin
- network, filesystem, and disk utilities go in /bin
- large text editors (emacs, etc) go in /usr/bin
- small text editors (vi, vim) go in /bin
- X, KDE, Gnome, et al are in /usr
- and so on...

That said, you wll find a lot of desktop systems (mine included) that
have / and /usr on the same filesystem.  It's a matter of taste and
what you will be using the system for whether you should make /usr a
separate filesystem or not.

-Richard

-- 
gentoo-user@gentoo.org mailing list


-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-04-25 17:17 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-23  6:06 [gentoo-user] GnuPG Trouble - Found Problem, Need Solution lordsauronthegreat
2006-04-23 21:17 ` Mick
2006-04-25  4:17   ` lordsauronthegreat
2006-04-25  4:25     ` Justin Findlay
2006-04-25  4:47       ` Jeremy Olexa
2006-04-25  6:32   ` lordsauronthegreat
2006-04-25  8:07     ` Alexander Skwar
2006-04-25 15:13       ` [gentoo-user] Newbie question re: /usr K. Mike Bradley
2006-04-25 15:32         ` [gentoo-user] Initramfs question K. Mike Bradley
2006-04-25 15:42           ` Hans-Werner Hilse
2006-04-25 15:36         ` [gentoo-user] Newbie question re: /usr Justin Findlay
2006-04-25 16:00           ` K. Mike Bradley
2006-04-25 16:07             ` Justin Findlay
2006-04-25 18:11             ` Herman Grootaers
2006-04-26  6:12               ` Dirk Heinrichs
2006-04-26  6:04             ` Dirk Heinrichs
2006-04-25 16:14         ` Richard Fish
2006-04-25 17:12           ` K. Mike Bradley [this message]
2006-04-25 19:38             ` Richard Fish
2006-04-25 20:21               ` znx
2006-04-26  0:39               ` K. Mike Bradley
2006-04-26  6:16                 ` Dirk Heinrichs
2006-04-26  8:03                 ` Neil Bothwick
2006-04-25 10:51     ` [gentoo-user] GnuPG Trouble - Found Problem, Need Solution Mick
2006-04-25 11:33       ` Bo Andresen
2006-04-25 15:16     ` Daniel da Veiga
2006-04-25 23:51       ` lordsauronthegreat
2006-04-24  5:39 ` Alexander Skwar
2006-04-24 23:18   ` lordsauronthegreat
2006-04-24 21:42 ` Abhay Kedia
2006-04-24 23:23   ` lordsauronthegreat

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='001f01c6688b$614b1050$0300a8c0@samantha' \
    --to=kmb@mikienet.com \
    --cc=gentoo-user@lists.gentoo.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