public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] news item for udev 197-r3 upgrade (yes, I know, it's late)
Date: Wed, 23 Jan 2013 14:09:20 -0500	[thread overview]
Message-ID: <CAGfcS_=MJNO5bfjvES-=RLGPTx9znMUSxx6Dx8KAQvJm2NKkMQ@mail.gmail.com> (raw)
In-Reply-To: <CAJ0EP42CLXKVY-6-2Zg_6Ds9KokshLMpWc7D+B0Vff3NzsFJ=Q@mail.gmail.com>

On Wed, Jan 23, 2013 at 1:56 PM, Mike Gilbert <floppym@gentoo.org> wrote:
>
> Ah, good to know. I'm used to dealing with my little homegrown
> initramfs, where I parse root from the kernel command line in /init.
> genkernel does the same thing.

Yeah, dracut generally "does the right thing" but that generally
assumes that things like fstab are correct.  It still uses the root=
option (I'm not sure if it can work without it - I believe it does
snapshot the fstab at time of creation).  My understanding is that
dracut actually remounts root a few times as it moves along, starting
with the kernel command line, then after setting up mounts in
fstab.sys (which is how you handle a separate /usr), and finally based
on the contents of fstab (which it can't read until it actually has
root mounted).  When it is done the root filesystem is mounted using
all options in /etc/fstab, which is probably a good thing.

That said, it hasn't been without bugs.  I think they're mostly fixed
at this point, but I haven't tried removing all of my workarounds
(mainly around the fact that it wasn't auto-assembling my raid unless
I hardcoded an mdadm -As in a script).

The best thing about dracut though is that it is pretty powerful, with
modules/hooks/etc.  When it wasn't quite working right for me I just
added my own module to it.  It also has the side-benefit of working
well even when mdadm decides to renumber all my md minor device
numbers (tends to happen when booting for CD or whatever - probably
because I'm using older metadata for some of the arrays).

Rich


  reply	other threads:[~2013-01-23 19:09 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-23 13:14 [gentoo-dev] news item for udev 197-r3 upgrade (yes, I know, it's late) Samuli Suominen
2013-01-23 13:32 ` Dirkjan Ochtman
2013-01-23 13:34   ` Markos Chandras
2013-01-23 13:41     ` Samuli Suominen
2013-01-23 13:44       ` Rich Freeman
2013-01-23 14:26         ` Samuli Suominen
2013-01-23 14:02 ` Philip Webb
2013-01-23 14:05   ` Diego Elio Pettenò
2013-01-23 15:04     ` Rich Freeman
2013-01-23 15:06       ` Diego Elio Pettenò
2013-01-23 16:03       ` Michael Weber
2013-01-23 21:49         ` Christopher Head
2013-01-24  1:45           ` [gentoo-dev] " »Q«
2013-01-24 14:52             ` Michael Weber
2013-01-23 18:29 ` [gentoo-dev] " Felix Kuperjans
2013-01-23 18:42   ` Mike Gilbert
2013-01-23 18:52     ` Rich Freeman
2013-01-23 18:56       ` Mike Gilbert
2013-01-23 19:09         ` Rich Freeman [this message]
2013-01-23 19:06     ` Felix Kuperjans
2013-01-24  2:04       ` Samuli Suominen
2013-01-24  3:11         ` [gentoo-dev] " Duncan
2013-01-24  4:28           ` Dale
2013-01-28  4:45       ` [gentoo-dev] " William Hubbs
2013-01-24 10:02   ` Michael Haubenwallner
2013-01-24 11:40     ` Rich Freeman
2013-01-24 15:49     ` Michael Orlitzky
2013-01-24 19:19       ` Michael Haubenwallner
2013-01-24 20:10         ` Diego Elio Pettenò
2013-01-23 21:21 ` Pacho Ramos
2013-01-23 21:45   ` Samuli Suominen
2013-01-23 22:21     ` Pacho Ramos
2013-01-23 23:07       ` Francesco Riosa
2013-01-24 15:40       ` Ian Stakenvicius
2013-01-25  9:19 ` Dirkjan Ochtman
2013-01-25 11:59   ` Rich Freeman
2013-01-25 13:43     ` Dirkjan Ochtman
2013-01-25 14:17   ` Ian Stakenvicius
2013-01-25 14:23     ` Dirkjan Ochtman
2013-01-25 14:26       ` Diego Elio Pettenò

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='CAGfcS_=MJNO5bfjvES-=RLGPTx9znMUSxx6Dx8KAQvJm2NKkMQ@mail.gmail.com' \
    --to=rich0@gentoo.org \
    --cc=gentoo-dev@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