From: Tanstaafl <tanstaafl@libertytrek.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] where did lvm installation guide go?
Date: Fri, 30 Aug 2013 10:37:19 -0400 [thread overview]
Message-ID: <5220AE1F.20601@libertytrek.org> (raw)
In-Reply-To: <CADPrc83CcOS221CXt=ZrSNJhWR16VcYkdbMOuv6N0Rw3SPr9Eg@mail.gmail.com>
On 2013-08-30 10:28 AM, Canek Peláez Valdés <caneko@gmail.com> wrote:
> udev/eudev has nothing to do with it. It's the init systems (as in
> both systemd and OpenRC) the ones that are pushing/have pushed for
> dropping support for it. In Gentoo, the move is being championed by
> William Hubs:
>
> http://thread.gmane.org/gmane.linux.gentoo.project/2946
>
> He's the OpenRC maintainer. NOBODY who has actually worked on the
> problem wants to support a separate /usr without an initramfs, because
> it makes no sense.
Please stop making such false statements.
It only makes no sense because of *other* decisions being made that want
to force files critical to booting to be placed into /usr.
There is no *philosophical* reason that it 'makes no sense.
> So it doesn't matter if you use udev, eudev, mdev or even a static
> /dev directory; no init system wants to support a separate /usr
> without an initramfs.
Just fyi... the *only* problem that I have with this is that I have an
*existing* system that has a separate /usr, and it only has that
separate /usr because when I followed the original gentoo installation
handbook back in 2003 or so, it actually had a separate /usr in the
example directory structure layout, so I thought it was the official
gentoo *recommendation* to do it that way.
If I wasn't in this predicament, I'd just make a mental note to never
install /usr to a separate partition and be done with it.
> And for a good reason: is braindead.
Again - it is only braindead if you accept the basic premise that it
'makes sense' to put files critical to the boot process into /usr.
Personally, I think it only 'makes sense' to put files critical to the
boot process into <gasp!> /boot.
next prev parent reply other threads:[~2013-08-30 14:38 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 15:47 [gentoo-user] where did lvm installation guide go? gottlieb
2013-08-29 16:56 ` [gentoo-user] " James
2013-08-29 21:02 ` gottlieb
2013-08-29 17:29 ` [gentoo-user] " Canek Peláez Valdés
2013-08-29 21:19 ` gottlieb
2013-08-30 0:30 ` Canek Peláez Valdés
2013-08-30 1:45 ` gottlieb
2013-08-30 2:29 ` Canek Peláez Valdés
2013-08-30 5:21 ` J. Roeleveld
2013-08-30 5:36 ` Canek Peláez Valdés
2013-08-30 6:10 ` Alan McKinnon
2013-08-30 7:16 ` Dale
2013-08-30 14:05 ` Tanstaafl
2013-08-30 14:28 ` Canek Peláez Valdés
2013-08-30 14:37 ` Tanstaafl [this message]
2013-08-30 14:38 ` Alan McKinnon
2013-08-30 14:59 ` Tanstaafl
2013-08-30 14:56 ` Canek Peláez Valdés
2013-08-31 11:31 ` [gentoo-user] " Nicolas Sebrecht
2013-08-30 14:13 ` [gentoo-user] " Canek Peláez Valdés
2013-08-30 5:47 ` Alan McKinnon
2013-08-30 7:17 ` Dale
2013-08-30 5:21 ` J. Roeleveld
2013-08-30 6:13 ` Alan McKinnon
2013-08-30 5:21 ` J. Roeleveld
2013-08-30 5:20 ` J. Roeleveld
2013-08-30 15:18 ` gottlieb
2013-08-30 16:48 ` joost
2013-08-30 19:18 ` Alan McKinnon
2013-08-31 14:18 ` gottlieb
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=5220AE1F.20601@libertytrek.org \
--to=tanstaafl@libertytrek.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