From: Mark David Dumlao <madumlao@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] systemd installation location
Date: Mon, 30 Sep 2013 13:08:44 +0800 [thread overview]
Message-ID: <CAG2nJkP_fwMam7NCuUuJjOKbP08oSLGGwwE6r5GK0d_V4xVbdw@mail.gmail.com> (raw)
In-Reply-To: <CAA2qdGV9TOjjV9CTOYoqW_GOHN7gfY95S1AyC_SRbtCQ6ej2Vw@mail.gmail.com>
On Mon, Sep 30, 2013 at 12:13 PM, Pandu Poluan <pandu@poluan.info> wrote:
>
> On Sep 30, 2013 9:31 AM, "Daniel Campbell" <lists@sporkbox.us> wrote:
>>
>
> --- le snip ---
>
>> If the proposed solution is all binaries and libraries in the same
>> root/prefix directory, then why call it /usr?
>
> My question exactly.
>
> Why install to /usr at all, leaving /bin and /sbin a practically empty
> directory containing symlinks only?
>
> I mean, I have no quarrel with / and /usr separation, having had them in the
> same partition for ages... but why not do it the other way around, i.e., put
> everything in / and have /usr be a container for symlinks?
>
If the binaries and libraries are kept together, /usr can actually be made
reliably sharable, independent of local settings in /etc. It can also be made
properly readonly, or otherwise use different mount options than /.
Most of the things in /usr have the same read-write characteristics.
They're mostly chunks of 1-20mb in size that are read very often and
written very rarely. You can pick a filesystem with options that
optimized for that. They're also non-data, so the root of that tree
has an entirely different backup priority than /etc or /home.
And then there are directories in /usr that don't exist in /. Are you
gonna link them too? So we have /share now? Or /src?
Seems to me that it makes less mess to move / to /usr than vice versa.
--
This email is: [ ] actionable [x] fyi [ ] social
Response needed: [ ] yes [ ] up to you [x] no
Time-sensitive: [ ] immediate [ ] soon [x] none
next prev parent reply other threads:[~2013-09-30 5:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-29 19:52 [gentoo-user] systemd installation location William Hubbs
2013-09-30 0:54 ` Daniel Campbell
2013-09-30 1:17 ` Mark David Dumlao
2013-09-30 1:22 ` Daniel Campbell
2013-09-30 1:51 ` Mark David Dumlao
2013-09-30 2:01 ` Daniel Campbell
2013-09-30 2:25 ` Mark David Dumlao
2013-09-30 2:31 ` Daniel Campbell
2013-09-30 4:13 ` Pandu Poluan
2013-09-30 5:08 ` Mark David Dumlao [this message]
2013-09-30 1:40 ` Mark David Dumlao
2013-09-30 1:50 ` Daniel Campbell
2013-09-30 2:05 ` Mark David Dumlao
2013-09-30 2:15 ` Daniel Campbell
2013-09-30 2:42 ` Mark David Dumlao
2013-09-30 8:07 ` Neil Bothwick
2013-09-30 6:24 ` pk
2013-09-30 6:45 ` Alan McKinnon
2013-09-30 22:14 ` pk
2013-09-30 22:43 ` Neil Bothwick
2013-10-01 6:16 ` Alan McKinnon
2013-10-01 19:59 ` pk
2013-09-30 16:06 ` [gentoo-user] " Martin Vaeth
2013-09-30 17:47 ` [gentoo-user] " Mark David Dumlao
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=CAG2nJkP_fwMam7NCuUuJjOKbP08oSLGGwwE6r5GK0d_V4xVbdw@mail.gmail.com \
--to=madumlao@gmail.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