From: Piotr Karbowski <piotr.karbowski@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: udev and existing /dev (devtmpfs)
Date: Tue, 17 Jan 2012 19:25:07 +0000 [thread overview]
Message-ID: <4F15CB13.1000703@gmail.com> (raw)
Hi,
After starting udev on the /dev which is devtmpfs the udev does not
'take over' already created nodes unless I add in the udev's init script
'udevadm trigger --typeÞvices --action=change'
right after
'udevadm trigger --typeÞvices --actiond'
If there is no action=change, the /dev device mapper nodes looks like
(all are nodes, different permissions):
brw-rw---- 1 root disk 253, 0 Jan 17 19:51 /dev/dm-0
brw-rw---- 1 root disk 253, 1 Jan 17 19:51 /dev/dm-1
brw-rw---- 1 root disk 253, 2 Jan 17 19:51 /dev/dm-2
brw-rw---- 1 root disk 253, 3 Jan 17 19:51 /dev/dm-3
brw-rw---- 1 root disk 253, 4 Jan 17 19:51 /dev/dm-4
brw-rw---- 1 root disk 253, 5 Jan 17 19:51 /dev/dm-5
crw------- 1 root root 10, 236 Jan 17 19:51 /dev/mapper/control
brw------- 1 root root 253, 0 Jan 17 19:51 /dev/mapper/enc_root
brw------- 1 root root 253, 5 Jan 17 19:51 /dev/mapper/vg-dropzone
brw------- 1 root root 253, 4 Jan 17 19:51 /dev/mapper/vg-home
brw------- 1 root root 253, 3 Jan 17 19:51 /dev/mapper/vg-rootfs
brw------- 1 root root 253, 1 Jan 17 19:51 /dev/mapper/vg-swap
brw------- 1 root root 253, 2 Jan 17 19:51 /dev/mapper/vg-tmp
but after action=change it does look like:
brw-rw---- 1 root disk 253, 0 Jan 17 19:50 /dev/dm-0
brw-rw---- 1 root disk 253, 1 Jan 17 19:50 /dev/dm-1
brw-rw---- 1 root disk 253, 2 Jan 17 19:50 /dev/dm-2
brw-rw---- 1 root disk 253, 3 Jan 17 19:50 /dev/dm-3
brw-rw---- 1 root disk 253, 4 Jan 17 19:50 /dev/dm-4
brw-rw---- 1 root disk 253, 5 Jan 17 19:50 /dev/dm-5
crw------- 1 root root 10, 236 Jan 17 19:50 /dev/mapper/control
lrwxrwxrwx 1 root root 7 Jan 17 19:50 /dev/mapper/enc_root -> ../dm-0
lrwxrwxrwx 1 root root 7 Jan 17 19:50 /dev/mapper/vg-dropzone ->
../dm-5
lrwxrwxrwx 1 root root 7 Jan 17 19:50 /dev/mapper/vg-home -> ../dm-4
lrwxrwxrwx 1 root root 7 Jan 17 19:50 /dev/mapper/vg-rootfs ->
../dm-3
lrwxrwxrwx 1 root root 7 Jan 17 19:50 /dev/mapper/vg-swap -> ../dm-1
lrwxrwxrwx 1 root root 7 Jan 17 19:50 /dev/mapper/vg-tmp -> ../dm-2
The /dev/mapper/* become symlinks to /dev/dm-* (following udev rules).
The question is: in such scenario, where udev use already-created /dev
(whatever it is devtmpfs or maybe mdev-created), should we add the
action=change to the init script? If no, then what should we do to
udevize /dev?
Distro gentoo, udev-171, I have such issue on every box I use.
-- Piotr.
next reply other threads:[~2012-01-17 19:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-17 19:25 Piotr Karbowski [this message]
2012-01-21 22:44 ` udev and existing /dev (devtmpfs) William Hubbs
2012-01-22 20:42 ` Kay Sievers
2012-01-23 16:41 ` Gabor Z. Papp
2012-01-23 17:00 ` Kay Sievers
2012-03-02 0:46 ` Piotr Karbowski
2012-03-02 2:38 ` Kay Sievers
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=4F15CB13.1000703@gmail.com \
--to=piotr.karbowski@gmail.com \
--cc=linux-hotplug@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).