From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] news item for udev 197-r3 upgrade (yes, I know, it's late)
Date: Sun, 27 Jan 2013 22:45:09 -0600 [thread overview]
Message-ID: <20130128044509.GA26718@linux1> (raw)
In-Reply-To: <510034C8.9050704@desaster-games.com>
[-- Attachment #1: Type: text/plain, Size: 1255 bytes --]
On Wed, Jan 23, 2013 at 08:06:48PM +0100, Felix Kuperjans wrote:
> Mike Gilbert:
> > On Wed, Jan 23, 2013 at 1:29 PM, Felix Kuperjans
> > <felix@desaster-games.com> wrote:
> >> Samuli Suominen wrote:
> >>> please review this news item, seems we need one after all
> >> Hello Samuli,
> >>
> >> /dev/root is no longer available in this udev version, so people who put
> >> this in their /etc/fstab might end up with an unbootable system.
> >>
> >> I suggest including in the news item, that /dev/root must be replaced
> >> with the actual root device or LABEL=..., UUID=... and the like in
> >> /etc/fstab.
> >>
> > fstab is not consulted for mounting the root filesystem, so it doesn't
> > really matter what you have in there. Either the kernel mounts it
> > based on the kernel command line, or your initramfs mounts it based on
> > whatever your /init programs does.
> Well, *if* a line with /dev/root is present in /etc/fstab, the system
> does not boot up properly (tested it right now).
> I always though such a line in /etc/fstab is needed so that fsck is run
> on the root filesystem...
That was an example in the fstab in the stages, but the handbook always
told you to replace /dev/root with the reference to the specific root
device.
William
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-01-28 4:45 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
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 ` William Hubbs [this message]
2013-01-24 10:02 ` [gentoo-dev] " 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=20130128044509.GA26718@linux1 \
--to=williamh@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