From: Michael Mol <mikemol@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] udevd boot messages
Date: Thu, 24 May 2012 19:24:57 -0400 [thread overview]
Message-ID: <CA+czFiBZECFDCjDq1G=65kBAw91XSURxrenVgvxeRmY6ymUMzQ@mail.gmail.com> (raw)
In-Reply-To: <4FBAAD05.8040201@gentoo.org>
On Mon, May 21, 2012 at 5:00 PM, Markos Chandras <hwoarang@gentoo.org> wrote:
> On 05/21/2012 03:27 PM, Michael Hampicke wrote:
>>> I updated udev from 171-r5 to 171-r6 and now i get several udevd
>>> boot message as : udevd[1389]: can not find
>>> '/lib/udev/rules.d/90-network.rules': No such file or directory
>>> udevd[1389]: can not find '/lib/udev/rules.d/95-keymap.rules': No
>>> such file or directory ...................... and so on.
>>>
>>> /lib is a symlink pointing to /lib64. /lib64/udev/rules.d is ok
>>> with all the rules that udevd does not find at boot.
>>
>> No I would guess it was because of the upgrade of
>> sys-apps/baselayout to 2.1-r1. Things got crazy here with that
>> upgrade. I had to re-merge every package with files under /lib/ In
>> your case re-merging udev should to the trick.
>>
> The package clearly informed you that you need to reboot for things to
> work properly
>
> "You should reboot the system now to get /run mounted with tmpfs!"
>
> Have a look on pkg_postinst() function in that ebuild. You chose to
> ignore it and this is why you had these problems after the update.
Ok, now I'm coming up on a bind. I've spent the last few days trying
to get my laptop back up to snuff, cycling emerge updates,
revdep-rebuilds and eix-syncs. That particular warning, for me, was
buried in a mountain of ruby and libicu build failures.
I just now started going through /var/log/portage/messages, and was
reminded of this thread.
I just wanted to note that deleting the rules.d directory, and then
only re-emerging udev, strikes me as setting oneself up for more
problems in the future. Turns out, there are a lot of packages on my
system I might want to look at re-emerging. A lot of it belongs to
udev, but a lot of it...doesn't. I'm going to try Jacques's method of
removing the old rules.d folder, and re-emerging the packages equery
identified. Hopefully, I won't see the same boot messages that hit
other people.
saffron rules.d # for pkg in $(ls); do equery b $pkg; done
* Searching for 10-dm.rules ...
sys-fs/lvm2-2.02.88 (/lib/udev/rules.d/10-dm.rules)
* Searching for 11-dm-lvm.rules ...
sys-fs/lvm2-2.02.88 (/lib/udev/rules.d/11-dm-lvm.rules)
* Searching for 13-dm-disk.rules ...
sys-fs/lvm2-2.02.88 (/lib/udev/rules.d/13-dm-disk.rules)
* Searching for 30-kernel-compat.rules ...
sys-fs/udev-171-r6 (/lib/udev/rules.d/30-kernel-compat.rules)
* Searching for 40-gentoo.rules ...
sys-fs/udev-171-r6 (/lib/udev/rules.d/40-gentoo.rules)
* Searching for 42-qemu-usb.rules ...
sys-fs/udev-171-r6 (/lib/udev/rules.d/42-qemu-usb.rules)
* Searching for 50-firmware.rules ...
sys-fs/udev-171-r6 (/lib/udev/rules.d/50-firmware.rules)
* Searching for 50-udev-default.rules ...
sys-fs/udev-171-r6 (/lib/udev/rules.d/50-udev-default.rules)
* Searching for 60-cdrom_id.rules ...
sys-fs/udev-171-r6 (/lib/udev/rules.d/60-cdrom_id.rules)
* Searching for 60-persistent-alsa.rules ...
sys-fs/udev-171-r6 (/lib/udev/rules.d/60-persistent-alsa.rules)
* Searching for 60-persistent-input.rules ...
sys-fs/udev-171-r6 (/lib/udev/rules.d/60-persistent-input.rules)
* Searching for 60-persistent-serial.rules ...
sys-fs/udev-171-r6 (/lib/udev/rules.d/60-persistent-serial.rules)
* Searching for 60-persistent-storage.rules ...
sys-fs/udev-171-r6 (/lib/udev/rules.d/60-persistent-storage.rules)
* Searching for 60-persistent-storage-tape.rules ...
sys-fs/udev-171-r6 (/lib/udev/rules.d/60-persistent-storage-tape.rules)
* Searching for 60-persistent-v4l.rules ...
sys-fs/udev-171-r6 (/lib/udev/rules.d/60-persistent-v4l.rules)
* Searching for 70-libgphoto2.rules ...
media-libs/libgphoto2-2.4.12 (/lib/udev/rules.d/70-libgphoto2.rules)
* Searching for 70-udev-acl.rules ...
sys-auth/consolekit-0.4.5_p20120320 (/lib/udev/rules.d/70-udev-acl.rules)
* Searching for 75-cd-aliases-generator.rules ...
sys-fs/udev-171-r6 (/lib/udev/rules.d/75-cd-aliases-generator.rules)
* Searching for 75-persistent-net-generator.rules ...
sys-fs/udev-171-r6 (/lib/udev/rules.d/75-persistent-net-generator.rules)
* Searching for 75-probe_mtd.rules ...
sys-fs/udev-171-r6 (/lib/udev/rules.d/75-probe_mtd.rules)
* Searching for 77-nm-olpc-mesh.rules ...
net-misc/networkmanager-0.8.4.0-r2 (/lib/udev/rules.d/77-nm-olpc-mesh.rules)
* Searching for 80-drivers.rules ...
sys-fs/udev-171-r6 (/lib/udev/rules.d/80-drivers.rules)
* Searching for 80-udisks.rules ...
sys-fs/udisks-1.0.4-r1 (/lib/udev/rules.d/80-udisks.rules)
* Searching for 90-alsa-restore.rules ...
media-sound/alsa-utils-1.0.25-r1 (/lib/udev/rules.d/90-alsa-restore.rules)
* Searching for 90-network.rules ...
sys-fs/udev-171-r6 (/lib/udev/rules.d/90-network.rules)
* Searching for 95-dm-notify.rules ...
sys-fs/lvm2-2.02.88 (/lib/udev/rules.d/95-dm-notify.rules)
* Searching for 95-udev-late.rules ...
sys-fs/udev-171-r6 (/lib/udev/rules.d/95-udev-late.rules)
* Searching for 95-upower-battery-recall-dell.rules ...
sys-power/upower-0.9.16 (/lib/udev/rules.d/95-upower-battery-recall-dell.rules)
* Searching for 95-upower-battery-recall-fujitsu.rules ...
sys-power/upower-0.9.16
(/lib/udev/rules.d/95-upower-battery-recall-fujitsu.rules)
* Searching for 95-upower-battery-recall-gateway.rules ...
sys-power/upower-0.9.16
(/lib/udev/rules.d/95-upower-battery-recall-gateway.rules)
* Searching for 95-upower-battery-recall-ibm.rules ...
sys-power/upower-0.9.16 (/lib/udev/rules.d/95-upower-battery-recall-ibm.rules)
* Searching for 95-upower-battery-recall-lenovo.rules ...
sys-power/upower-0.9.16
(/lib/udev/rules.d/95-upower-battery-recall-lenovo.rules)
* Searching for 95-upower-battery-recall-toshiba.rules ...
sys-power/upower-0.9.16
(/lib/udev/rules.d/95-upower-battery-recall-toshiba.rules)
* Searching for 95-upower-csr.rules ...
sys-power/upower-0.9.16 (/lib/udev/rules.d/95-upower-csr.rules)
* Searching for 95-upower-hid.rules ...
sys-power/upower-0.9.16 (/lib/udev/rules.d/95-upower-hid.rules)
* Searching for 95-upower-wup.rules ...
sys-power/upower-0.9.16 (/lib/udev/rules.d/95-upower-wup.rules)
* Searching for 99-fuse.rules ...
sys-fs/fuse-2.8.6 (/lib/udev/rules.d/99-fuse.rules)
* Searching for 99-laptop-mode.rules ...
app-laptop/laptop-mode-tools-1.60-r1 (/lib/udev/rules.d/99-laptop-mode.rules)
--
:wq
next prev parent reply other threads:[~2012-05-24 23:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 9:15 [gentoo-user] udevd boot messages Jacques Montier
2012-05-21 14:27 ` Michael Hampicke
2012-05-21 15:41 ` [solved] " Jacques Montier
2012-05-21 21:00 ` Markos Chandras
2012-05-23 16:24 ` Tanstaafl
2012-05-23 16:49 ` Alex Schuster
2012-05-23 17:18 ` Tanstaafl
2012-05-23 21:25 ` Markos Chandras
2012-05-23 21:47 ` Alan McKinnon
2012-05-23 21:54 ` Markos Chandras
2012-05-23 22:11 ` Alan McKinnon
2012-05-24 0:55 ` Pandu Poluan
2012-05-24 9:45 ` Tanstaafl
2012-05-24 9:35 ` Tanstaafl
2012-05-24 23:24 ` Michael Mol [this message]
2012-05-25 11:17 ` Tanstaafl
2012-05-25 20:13 ` pk
2012-05-25 23:52 ` Peter Humphrey
2012-05-26 8:36 ` pk
2012-05-26 9:34 ` Peter Humphrey
2012-05-26 9:37 ` Markos Chandras
2012-05-26 12:48 ` Peter Humphrey
2012-05-26 2:10 ` Michael Mol
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='CA+czFiBZECFDCjDq1G=65kBAw91XSURxrenVgvxeRmY6ymUMzQ@mail.gmail.com' \
--to=mikemol@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