From: "Canek Peláez Valdés" <caneko@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Another issue/questions updating udev from 164-r2 to 171-r5
Date: Sun, 5 Feb 2012 15:58:34 -0600 [thread overview]
Message-ID: <CADPrc81psX94+z78yt7qaaCFgYMNVXenYfo6swe39qvFw0DLSQ@mail.gmail.com> (raw)
In-Reply-To: <4F2EC8A1.40202@libertytrek.org>
On Sun, Feb 5, 2012 at 12:21 PM, Tanstaafl <tanstaafl@libertytrek.org> wrote:
[snip]
> Ok, I apparently don't, but... are you saying that all of the stuff that
> follows the initramfs warning *all* pertains to using an initramfs?
No, you're right; this:
mount options for directory /dev are no longer
set in /etc/udev/udev.conf, but in /etc/fstab
as for other directories.
You only have to worry if you set mount options using udev; almost
nobody did that. If you did (I think you'll remember) you only need to
set the mount options in fstab (which is what the Gentoo Handbook
describes). This line:
If you use /dev/md/*, /dev/loop/* or /dev/rd/*,
then please migrate over to using the device names
/dev/md*, /dev/loop* and /dev/ram*.
The devfs-compat rules have been removed.
For reference see Bug #269359.
Again, I think you'll remember if you used any of those devices, so
you are probably fine. And lastly:
Rules for /dev/hd* devices have been removed
Please migrate to libata.
If you don't have IDE devices, nothing to worry about.
Regards.
--
Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México
prev parent reply other threads:[~2012-02-05 21:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-05 17:34 [gentoo-user] Another issue/questions updating udev from 164-r2 to 171-r5 Tanstaafl
2012-02-05 17:45 ` Volker Armin Hemmann
2012-02-05 17:57 ` Tanstaafl
2012-02-05 17:47 ` Canek Peláez Valdés
2012-02-05 18:21 ` Tanstaafl
2012-02-05 21:58 ` Canek Peláez Valdés [this message]
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=CADPrc81psX94+z78yt7qaaCFgYMNVXenYfo6swe39qvFw0DLSQ@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