public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: [OT] A little help for non-native English speakers
Date: Thu, 1 Feb 2018 14:25:42 -0500	[thread overview]
Message-ID: <CAGfcS_mDj5TYPjSo59GOmKJ66Z_nRX7n1NPEBKYXW76CoSbf+A@mail.gmail.com> (raw)
In-Reply-To: <a71152d3-e49b-4a35-199b-3fbf2813c1d3@tnetconsulting.net>

On Thu, Feb 1, 2018 at 2:09 PM, Grant Taylor <gtaylor@tnetconsulting.net> wrote:
>
> IMHO that makes the name of the "/etc" directory all that much more
> entertaining.  As in Dennis R. and Ken T. couldn't be bothered to come up
> with more directory names than they had, e.g. /bin /lib /boot /var … (I
> can't be bothered to think of or look for more.)
>

Along those lines the original reason for the / vs /usr split was that
the original developers were accommodating a machine that had two hard
drives and needed to split things up.

There may very well be good reasons to preserve the distinction today,
but those aren't actually historical.  And of course there are two
modern approaches:

1.  The more traditional FHS approach of / for boot-essential and /usr
mounted later during bootstrapping.

2.  The Fedora /usr merge approach of sticking all read-only
distro-supplied files in /usr with the goal that they be contained and
read-only (think squashfs/signatures/etc), with bootstrapping covered
by the initramfs.

-- 
Rich


  reply	other threads:[~2018-02-01 19:25 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-01 17:03 [gentoo-user] [OT] A little help for non-native English speakers Peter Humphrey
2018-02-01 18:12 ` Rich Freeman
2018-02-01 18:27   ` [gentoo-user] " Grant Edwards
2018-02-01 18:47     ` Philip Webb
2018-02-01 18:50       ` Neil Bothwick
2018-02-01 19:09         ` Grant Taylor
2018-02-01 19:25           ` Rich Freeman [this message]
2018-02-01 21:17         ` Philip Webb
2018-02-01 22:24           ` Neil Bothwick
2018-02-01 23:39             ` Peter Humphrey
2018-02-02  0:04               ` Neil Bothwick
2018-02-02  0:36                 ` Peter Humphrey
2018-02-02  1:30                   ` Neil Bothwick
2018-02-02  4:48                   ` allan gottlieb
2018-02-02  5:31                     ` Floyd Anderson
2018-02-01 23:36       ` Peter Humphrey
2018-02-01 18:55   ` [gentoo-user] " Neil Bothwick
2018-02-01 22:45     ` [gentoo-user] " Ian Zimmerman
2018-02-01 23:03       ` Neil Bothwick
2018-02-01 22:52     ` [gentoo-user] [OT] " Frank Steinmetzger
2018-02-01 23:05       ` Jack
2018-02-01 23:34         ` [gentoo-user] " Grant Edwards
2018-02-02  0:05           ` Neil Bothwick
2018-02-02  0:08           ` Jack
2018-02-03  0:19             ` Wol's lists
2018-02-03  8:43               ` Peter Humphrey
2018-02-03 17:24                 ` Wols Lists
2018-02-03 18:32                   ` Philip Webb
2018-02-01 23:42         ` [gentoo-user] " Frank Steinmetzger
2018-02-01 23:43       ` Peter Humphrey
2018-02-02  7:34       ` Alan McKinnon
2018-02-02  7:47         ` Frank Steinmetzger
2018-02-02  7:46           ` Alan McKinnon
2018-02-02  8:10         ` Neil Bothwick
2018-02-02 10:06           ` Alan McKinnon
2018-02-02 17:28           ` Grant Taylor
2018-02-03  0:21             ` Wol's lists
2018-02-02  4:06     ` Grant Taylor
2018-02-02  8:03       ` Neil Bothwick
2018-02-02 20:05         ` Grant Taylor
2018-02-02 20:34           ` Peter Humphrey
2018-02-02 23:44             ` Neil Bothwick
2018-02-03  8:44               ` Peter Humphrey
2018-02-02 20:37           ` allan gottlieb
2018-02-01 23:45   ` Peter Humphrey
2018-02-02  0:25 ` R0b0t1
2018-02-02  0:41   ` Peter Humphrey
2018-02-02  1:31     ` Neil Bothwick
2018-02-02  1:58       ` Rich Freeman
2018-02-03 13:46   ` Frank Steinmetzger

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=CAGfcS_mDj5TYPjSo59GOmKJ66Z_nRX7n1NPEBKYXW76CoSbf+A@mail.gmail.com \
    --to=rich0@gentoo.org \
    --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