public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Canek Peláez Valdés" <caneko@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] where did lvm installation guide go?
Date: Fri, 30 Aug 2013 09:28:26 -0500	[thread overview]
Message-ID: <CADPrc83CcOS221CXt=ZrSNJhWR16VcYkdbMOuv6N0Rw3SPr9Eg@mail.gmail.com> (raw)
In-Reply-To: <5220A68D.1080407@libertytrek.org>

On Fri, Aug 30, 2013 at 9:05 AM, Tanstaafl <tanstaafl@libertytrek.org> wrote:
> On 2013-08-30 3:16 AM, Dale <rdalek1967@gmail.com> wrote:
>>
>> Example, don't want a init thingy, put / on a regular partition and
>> normal file system, just make sure you won't fill it up for a very
>> long time. Of course /boot has to be on a regular file system too.
>
>
> Well, apparently this now includes /usr, as from what I gleaned from the
> earlier thread, there is no guarantee even eudev will continue to support
> separate /usr partition in future (since gentoo council has formally voted
> to NOT support it without an initramfs)...

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.

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.

And for a good reason: is braindead.

Regards.
-- 
Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México


  reply	other threads:[~2013-08-30 14:28 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 [this message]
2013-08-30 14:37                     ` Tanstaafl
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='CADPrc83CcOS221CXt=ZrSNJhWR16VcYkdbMOuv6N0Rw3SPr9Eg@mail.gmail.com' \
    --to=caneko@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