From: »Q« <boxcars@gmx.net>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: some of the stuff in /usr that's become a problem
Date: Sun, 29 Sep 2013 21:51:35 -0500 [thread overview]
Message-ID: <20130929215135.76ac0cf1@fuchsia.remarqs.net> (raw)
In-Reply-To: 5248DBDF.2070902@gmail.com
On Sun, 29 Sep 2013 22:03:11 -0400
Greg Woodbury <redwolfe@gmail.com> wrote:
> One of the most obvious things that broke booting with a
> seperate /usr is not GNOMEs fault, but GRUB 2's fault.
>
> the move of /bin to /usr/bin (for things like cp,mv,ln,ls) came after
> the breakage of /usr, but is symptomatic of some distros cavalier
> attitudes to the problem.
>
> /usr/lib/udev.....
> /usr/lib/systemd.....
>
> were both placed in /usr despite objections from a number of folks.
>
> So claims that udev and systemd are not responsible are not true.
>
> /usr/lib/e2initrd-helper was placed in /usr despite objections.
> /usr/lib/libdevmapper* was moved despite objections...
> /usr/lib/liblvm2* helpers were placed in /usr despite objections...
>
> There were deliberate placements of "new" or updated libraries
> in /usr that were known ahead of time that would break the use of a
> separate /usr filesystem.
>
> It was pointed out quite plainly at the time, and the placements were
> made anyway, dismissing the concerns are "mere historical artifacts"
> or "clinging to ancient and outmoded traditions."
What were the reasons given for those changes at the time?
next prev parent reply other threads:[~2013-09-30 2:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-30 2:03 [gentoo-user] some of the stuff in /usr that's become a problem Greg Woodbury
2013-09-30 2:21 ` Daniel Campbell
2013-09-30 3:13 ` William Hubbs
2013-09-30 3:40 ` Daniel Campbell
2013-10-01 8:36 ` Greg Woodbury
2013-10-01 8:30 ` Greg Woodbury
2013-10-01 8:45 ` Alan McKinnon
2013-09-30 2:51 ` »Q« [this message]
2013-09-30 8:10 ` Neil Bothwick
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=20130929215135.76ac0cf1@fuchsia.remarqs.net \
--to=boxcars@gmx.net \
--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