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 10:05:38 +0800 [thread overview]
Message-ID: <CAG2nJkOZvHT5TxMYd+W5GOn-PTD-Y4z+gZQR+VF_jm2UWjmeHQ@mail.gmail.com> (raw)
In-Reply-To: <5248D8D6.8040901@sporkbox.us>
On Mon, Sep 30, 2013 at 9:50 AM, Daniel Campbell <lists@sporkbox.us> wrote:
> Anyway, I'm not in favor of FHS _per se_, but it sounds pretty
> reasonable to have some semblance of order among where different parts
> of a system go. Shoving everything into /usr and symlinking everything
> else seems like a stop-gap or good-enough solution that came about due
> to ignoring the existing standard (FHS) and refusing to try to change
> it. I could be wrong, though. My point is I'm not dogmatic about it; I
> just think that if the FOSS community were willing, a better solution
> could be crafted.
It's true that it's nice to have a semblance of order where different parts go.
But "all libraries and binaries in /usr" is also a semblance of order. You don't
separate stuff for the sake of separating stuff. You separate them because you
have a good reason to separate them. It turns out that there isn't a good reason
to separate them, and that there's no way to predictably separate them.
Mushing them together isn't just a stop-gap or good-enough solution. The
idea of keeping system-critical separate from non-critical was not maintainable
in the long run to begin with.
>> If you were in the shoes of the ebuild packagers, you would be hard-pressed to
>> predict which packages belong in the / PREFIX and which ones in /usr PREFIX,
>> 100 times out of 100. But you need 100 times out of 100 or you'll get
>> people whining
>> that they can't boot or whining that they need to do some migration. That's
>> why / and /usr separation is broken.
>>
> I agree, but perhaps the / and /usr separation is a symptom of a greater
> problem instead of being the problem in and of itself. Like Inception,
> maybe we need to go further. :P
The greater problem is what I'm pointing out already. Even in principle, you
just can't predict which files belong in /. It's always been a case-by-case,
system-by-system thing, and it just so happens that 99.9xxx% of the cases
are the same. Distro packagers, however, have to decide for 100% of the cases.
So they're going to end up making weird decisions that are easy for you to
second-guess but are actually tough.
If you want to solve the "hard problem", you want to create a tool that
will automate / and /usr migrations. Portage has to be aware of the tool
and maybe 100% of ebuilds will have to be rewritten to take advantage of the
dynamic prefixes set by the tool. That solves it for good, and you can have
your / and /usr separate. But only for gentoo.
Every package manager needs to have a similar tool and similar intelligence
for that to work.
--
This email is: [ ] actionable [x] fyi [x] social
Response needed: [ ] yes [x] up to you [ ] no
Time-sensitive: [ ] immediate [ ] soon [x] none
next prev parent reply other threads:[~2013-09-30 2:05 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
2013-09-30 1:40 ` Mark David Dumlao
2013-09-30 1:50 ` Daniel Campbell
2013-09-30 2:05 ` Mark David Dumlao [this message]
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=CAG2nJkOZvHT5TxMYd+W5GOn-PTD-Y4z+gZQR+VF_jm2UWjmeHQ@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