From: Pandu Poluan <pandu@poluan.info>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] systemd installation location
Date: Mon, 30 Sep 2013 11:13:31 +0700 [thread overview]
Message-ID: <CAA2qdGV9TOjjV9CTOYoqW_GOHN7gfY95S1AyC_SRbtCQ6ej2Vw@mail.gmail.com> (raw)
In-Reply-To: <5248E26D.7090601@sporkbox.us>
[-- Attachment #1: Type: text/plain, Size: 1577 bytes --]
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?
> It has little to do with
> users if it's nothing but binaries, libraries, etc. In addition, would a
> local directory still be under this, for user-compiled programs not
> maintained by the PM? Or does that deserve a different top level
directory?
>
> Then there's /opt, whose purpose I'm still not sure of. This is
> strengthening the idea that something new should be thought up and
> drafted.
IIRC, it was supposed to contain third-party binaries, i.e., things not
available in a distro's package repo. Thus, when one's tired of a
third-party binary package, he/she can just delete the relevant directory
under /opt, because the third-party package might not be uninstallable
using the distro's package management system (if any).
Of course, he/she might have to clean up the leftover crud in /etc, but
those are usually small and can safely be ignored. Except perhaps startup
initscripts.
> Not necessarily by us at Gentoo, but *somebody*. If I was crazy
> and knowledgeable enough I'd volunteer myself.
>
Rgds,
--
[-- Attachment #2: Type: text/html, Size: 1966 bytes --]
next prev parent reply other threads:[~2013-09-30 4:13 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 [this message]
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
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=CAA2qdGV9TOjjV9CTOYoqW_GOHN7gfY95S1AyC_SRbtCQ6ej2Vw@mail.gmail.com \
--to=pandu@poluan.info \
--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