From: Arioch <the_Arioch@nm.ru>
To: linux-hotplug@vger.kernel.org
Subject: Re: +rule: query device inode by Major and Minor - am i inventing
Date: Tue, 16 Aug 2005 17:13:42 +0000 [thread overview]
Message-ID: <ddt6re$3vg$1@sea.gmane.org> (raw)
In-Reply-To: <4300318B.8040505@nm.ru>
Kay Sievers пишет:
> What nodes exactly have the same major/minor? That setup may need to be
> fixed.
Now i think that %M and %m macros are expanded somehow strangely:
$ pwd
/dev/.lookup_by_numbers
$for i in DUP/* ; do j=${i#*/}; h=${j%_*}; ls -l $h $i ; echo; done
[... list skipped - there is longer and more detailed one below ...]
I was intrigued by duplicating of /dev/null.
Was this device created twice ???
$ls -l ../ram3 ../nu*
crw-rw-rw- 1 root root 1, 3 Авг 16 19:47 ../null
brw-rw---- 1 root disk 1, 3 Авг 16 19:47 ../ram3
You see, it seems character and block devices with same major|minor can
easily co-exist!
$for i in {1,2,3,4,5}; do ls ../hda$i ../pty/s$i -l ; done
brw-rw---- 1 root root 3, 1 Авг 16 19:47 ../hda1
crw-rw---- 1 root tty 3, 161 Авг 16 19:47 ../pty/s1
brw-rw---- 1 root root 3, 2 Авг 16 19:47 ../hda2
crw-rw---- 1 root tty 3, 162 Авг 16 19:47 ../pty/s2
brw-rw---- 1 root root 3, 3 Авг 16 19:47 ../hda3
crw-rw---- 1 root tty 3, 163 Авг 16 19:47 ../pty/s3
brw-rw---- 1 root root 3, 4 Авг 16 19:47 ../hda4
crw-rw---- 1 root tty 3, 164 Авг 16 19:47 ../pty/s4
brw-rw---- 1 root root 3, 5 Авг 16 19:47 ../hda5
You see, on one hand we again see mixing block and char devices.
On the othe hands, it seems that when %m was expanded - it subtrcted 160
from it's value. 160=32*5 - so was minor masked with 2:00011111 ?
Or can major|minor be silently changed later, after symlink already
created ?
To be more generic, and more longer
$for i in DUP/* ; do j=${i#*/}; h=${j%_*}; ls -l $i ;ls -l
`readlink -e $i`; ls -l $h; ls -l `readlink -e $h`; echo; done
lrwxrwxrwx 1 root root 10 Авг 16 19:47 DUP/major1@minor11_DUP -> ../../kmsg
crw-rw---- 1 root root 1, 11 Авг 16 19:47 /dev/kmsg
lrwxrwxrwx 1 root root 8 Авг 16 19:47 major1@minor11 -> ../ram11
brw-rw---- 1 root disk 1, 11 Авг 16 19:47 /dev/ram11
lrwxrwxrwx 1 root root 9 Авг 16 19:47 DUP/major1@minor1_DUP -> ../../mem
crw-r----- 1 root root 1, 1 Авг 16 19:47 /dev/mem
lrwxrwxrwx 1 root root 7 Авг 16 19:47 major1@minor1 -> ../ram1
brw-rw---- 1 root disk 1, 1 Авг 16 19:47 /dev/ram1
lrwxrwxrwx 1 root root 10 Авг 16 19:47 DUP/major1@minor2_DUP -> ../../kmem
crw-r----- 1 root root 1, 2 Авг 16 19:47 /dev/kmem
lrwxrwxrwx 1 root root 7 Авг 16 19:47 major1@minor2 -> ../ram2
brw-rw---- 1 root disk 1, 2 Авг 16 19:47 /dev/ram2
lrwxrwxrwx 1 root root 10 Авг 16 19:47 DUP/major1@minor3_DUP -> ../../ram3
brw-rw---- 1 root disk 1, 3 Авг 16 19:47 /dev/ram3
lrwxrwxrwx 1 root root 7 Авг 16 19:47 major1@minor3 -> ../null
crw-rw-rw- 1 root root 1, 3 Авг 16 19:47 /dev/null
lrwxrwxrwx 1 root root 10 Авг 16 19:47 DUP/major1@minor3_DUP1 -> ../../null
crw-rw-rw- 1 root root 1, 3 Авг 16 19:47 /dev/null
lrwxrwxrwx 1 root root 7 Авг 16 19:47 major1@minor3 -> ../null
crw-rw-rw- 1 root root 1, 3 Авг 16 19:47 /dev/null
lrwxrwxrwx 1 root root 10 Авг 16 19:47 DUP/major1@minor4_DUP -> ../../port
crw-r----- 1 root root 1, 4 Авг 16 19:47 /dev/port
lrwxrwxrwx 1 root root 7 Авг 16 19:47 major1@minor4 -> ../ram4
brw-rw---- 1 root disk 1, 4 Авг 16 19:47 /dev/ram4
lrwxrwxrwx 1 root root 10 Авг 16 19:47 DUP/major1@minor5_DUP -> ../../zero
crw-rw-rw- 1 root root 1, 5 Авг 16 19:47 /dev/zero
lrwxrwxrwx 1 root root 7 Авг 16 19:47 major1@minor5 -> ../ram5
brw-rw---- 1 root disk 1, 5 Авг 16 19:47 /dev/ram5
lrwxrwxrwx 1 root root 10 Авг 16 19:47 DUP/major1@minor7_DUP -> ../../full
crw-rw-rw- 1 root root 1, 7 Авг 16 19:47 /dev/full
lrwxrwxrwx 1 root root 7 Авг 16 19:47 major1@minor7 -> ../ram7
brw-rw---- 1 root disk 1, 7 Авг 16 19:47 /dev/ram7
lrwxrwxrwx 1 root root 12 Авг 16 19:47 DUP/major1@minor8_DUP ->
../../random
crw-rw-rw- 1 root root 1, 8 Авг 16 19:47 /dev/random
lrwxrwxrwx 1 root root 7 Авг 16 19:47 major1@minor8 -> ../ram8
brw-rw---- 1 root disk 1, 8 Авг 16 19:47 /dev/ram8
lrwxrwxrwx 1 root root 13 Авг 16 19:47 DUP/major1@minor9_DUP ->
../../urandom
cr--r--r-- 1 root root 1, 9 Авг 16 19:47 /dev/urandom
lrwxrwxrwx 1 root root 7 Авг 16 19:47 major1@minor9 -> ../ram9
brw-rw---- 1 root disk 1, 9 Авг 16 19:47 /dev/ram9
lrwxrwxrwx 1 root root 12 Авг 16 19:47 DUP/major3@minor0_DUP ->
../../pty/s0
crw-rw---- 1 root tty 3, 160 Авг 16 19:47 /dev/pty/s0
lrwxrwxrwx 1 root root 6 Авг 16 19:47 major3@minor0 -> ../hda
brw-rw---- 1 root root 3, 0 Авг 16 19:47 /dev/hda
lrwxrwxrwx 1 root root 12 Авг 16 19:47 DUP/major3@minor1_DUP ->
../../pty/s1
crw-rw---- 1 root tty 3, 161 Авг 16 19:47 /dev/pty/s1
lrwxrwxrwx 1 root root 7 Авг 16 19:47 major3@minor1 -> ../hda1
brw-rw---- 1 root root 3, 1 Авг 16 19:47 /dev/hda1
lrwxrwxrwx 1 root root 12 Авг 16 19:47 DUP/major3@minor2_DUP ->
../../pty/s2
crw-rw---- 1 root tty 3, 162 Авг 16 19:47 /dev/pty/s2
lrwxrwxrwx 1 root root 7 Авг 16 19:47 major3@minor2 -> ../hda2
brw-rw---- 1 root root 3, 2 Авг 16 19:47 /dev/hda2
lrwxrwxrwx 1 root root 12 Авг 16 19:47 DUP/major3@minor3_DUP ->
../../pty/s3
crw-rw---- 1 root tty 3, 163 Авг 16 19:47 /dev/pty/s3
lrwxrwxrwx 1 root root 7 Авг 16 19:47 major3@minor3 -> ../hda3
brw-rw---- 1 root root 3, 3 Авг 16 19:47 /dev/hda3
lrwxrwxrwx 1 root root 12 Авг 16 19:47 DUP/major3@minor4_DUP ->
../../pty/s4
crw-rw---- 1 root tty 3, 164 Авг 16 19:47 /dev/pty/s4
lrwxrwxrwx 1 root root 7 Авг 16 19:47 major3@minor4 -> ../hda4
brw-rw---- 1 root root 3, 4 Авг 16 19:47 /dev/hda4
lrwxrwxrwx 1 root root 12 Авг 16 19:47 DUP/major3@minor5_DUP ->
../../pty/s5
crw-rw---- 1 root tty 3, 165 Авг 16 19:47 /dev/pty/s5
lrwxrwxrwx 1 root root 7 Авг 16 19:47 major3@minor5 -> ../hda5
brw-rw---- 1 root root 3, 5 Авг 16 19:47 /dev/hda5
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2005-08-16 17:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-15 6:09 +rule: query device inode by Major and Minor - am i inventing brand Arioch
2005-08-15 13:40 ` +rule: query device inode by Major and Minor - am i inventing brand new bycicle ? Kay Sievers
2005-08-16 10:52 ` +rule: query device inode by Major and Minor - am i inventing Arioch
2005-08-16 17:13 ` Arioch [this message]
2005-08-16 18:18 ` Arioch
2005-08-16 18:29 ` +rule: query device inode by Major and Minor - am i inventing brand new bycicle ? Kay Sievers
2005-08-16 18:50 ` +rule: query device inode by Major and Minor - am i inventing Arioch
2005-08-16 21:28 ` +rule: query device inode by Major and Minor - am i inventing brand new bycicle ? Greg KH
2005-08-17 8:07 ` +rule: query device inode by Major and Minor - am i inventing Arioch
2005-08-18 17:59 ` +rule: query device inode by Major and Minor - am i inventing brand new bycicle ? Greg KH
2005-08-18 21:04 ` +rule: query device inode by Major and Minor - am i inventing Arioch
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='ddt6re$3vg$1@sea.gmane.org' \
--to=the_arioch@nm.ru \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.