linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike <mis@ipunwired.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev
Date: Thu, 11 Aug 2005 19:21:15 +0000	[thread overview]
Message-ID: <42FBA52B.1020501@ipunwired.com> (raw)
In-Reply-To: <20050811182850.GD15803@kroah.com>

running udev on each disk gave me

[root@localhost udev-065]# udevtest /sys/block/sdb
version 039
looking at '/block/sdb'
configured rule in '/etc/udev/rules.d/10-udev.rules' at line 2 applied, 
added
symlink 'raid11'
configured rule in '/etc/udev/rules.d/10-udev.rules' at line 2 applied, 
'sdb'
becomes '%k'
creating device node '/dev/sdb', major = '8', minor = '16', mode = 
'060660', uid
= '0', gid = '6'

for all the disk that were present. I removed sda before running the 
test. The sda drive returns looking at /block/sda and dosn't go any further.

thanks
    Mike

Greg KH wrote:
> On Thu, Aug 11, 2005 at 02:29:35PM -0400, Mike wrote:
> 
>>hey;
>>
>>I've setup Raid1 on two SATA drives on my FC3 system. as well there are 
>>several other SATA drives in the system that are not in the raid. I 
>>wanted to make static mappings to the /dev devices. I've created a rules 
>>file and according to the logs its reading the rules files I created.
>>
>>...
>>Aug 09 21:34:42 localhost udev[10536]: configured rule in 
>>'/etc/udev/rules.d/10-udev.rules' at line 4 applied, 'sdd' becomes '%k'
>>Aug 09 21:34:42 localhost udev[10536]: creating device node '/dev/sdd'
>>...
>>
>>but if I remove on of the drives from the system. It will read the rules 
>>file only up to where the non present drive is then switch to the 
>>defaults which removes the satic maps and breaks the raid.
> 
> 
> What does running udevtest show for that situation?
> 
> 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-11 19:21 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-11 18:28 udev Greg KH
2005-08-11 18:29 ` udev Mike
2005-08-11 19:16 ` udev Greg KH
2005-08-11 19:21 ` Mike [this message]
2005-08-11 19:36 ` udev Kay Sievers
2005-08-12 15:33 ` udev Mike
2005-08-12 18:03 ` udev Greg KH
2009-11-02 11:10 ` udev Oleg Puchinin
2009-11-02 11:50 ` udev Oleg Puchinin
2009-11-02 14:35 ` udev Andrey Borzenkov
2009-11-02 16:57 ` udev Alan Jenkins
2011-03-22 19:48 ` Udev Paulo Eliseu Weber
2011-03-22 19:58 ` Udev Kay Sievers
  -- strict thread matches above, loose matches on Subject: below --
2010-08-18  9:51 UDEV Тима
2010-08-18 12:49 ` UDEV Greg KH
2010-08-19 15:27 ` UDEV Greg KH
2010-08-24 12:50 ` UDEV Greg KH
2004-08-08 22:47 udev Luke Kenneth Casson Leighton
2004-08-09 12:36 ` udev Luke Kenneth Casson Leighton
2004-08-09 12:40 ` udev Marco d'Itri

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=42FBA52B.1020501@ipunwired.com \
    --to=mis@ipunwired.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).