All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: +rule: query device inode by Major and Minor - am i inventing brand new bycicle ?
Date: Tue, 16 Aug 2005 21:28:56 +0000	[thread overview]
Message-ID: <20050816212856.GA27757@kroah.com> (raw)
In-Reply-To: <4300318B.8040505@nm.ru>

On Tue, Aug 16, 2005 at 09:13:42PM +0400, Arioch wrote:
> 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!

Of course they can.  For further examples, see Documentation/devices.txt
for all of the reserved major/minor numbers for character and block
devices.  Remember, character and block devices are totally separate
"namespaces".  The major/minor number is only unique within a character,
or a block "namespace".

thanks,

greg k-h


-------------------------------------------------------
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

  parent reply	other threads:[~2005-08-16 21:28 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
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 ` Greg KH [this message]
2005-08-17  8:07 ` 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=20050816212856.GA27757@kroah.com \
    --to=greg@kroah.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 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.