All of lore.kernel.org
 help / color / mirror / Atom feed
From: claude <claude@snscrew.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: Udev and Mylex Dac960
Date: Mon, 16 Feb 2004 07:35:12 +0000	[thread overview]
Message-ID: <403072B0.5010903@snscrew.net> (raw)
In-Reply-To: <4022CB7D.4010505@snscrew.net>

Greg KH wrote:
> On Mon, Feb 16, 2004 at 06:46:16AM +0100, claude wrote:
> 
>>Also a bad news :(. I've downloaded udev-017.tar.gz, compiled and installed 
>>it,
>>but my Mylex logical device are always created as /dev/rd!c0d0. Is there 
>>anything
>>I can do ?
> 
> 
> Ick.  Can you build udev by doing the following:
> 	make clean
> 	make DEBUG=true USE_LOG=true
> 
> And then run the udevtest binary in that directory that gets built for
> your block device:
> 	./udevtest block/rd!c0d0
> (you might have to do this as:
> 	./udevtest block/rd\!c0d0
> depending on your shell)
Yeah, that's why '!' bother me ! ;)
> 
> and then send the output that this program creates to us?
Yes output follow (i have to type :
	udevtest /block/rd\!c0d0 )


main: version 017
udev_hotplug: looking at '/block/rd!c0d0'
get_dirs: sysfs_path='/sys'
parse_config_file: reading '/etc/udev/udev.conf' as config file
namedev_init_rules: reading '/etc/udev/udev.rules' as rules file
namedev_init_permissions: reading '/etc/udev/udev.permissions' as permissions file
sleep_for_dev: looking for '/sys/block/rd!c0d0/dev'
get_class_dev: looking at '/sys/block/rd!c0d0'
get_class_dev: class_dev->name='rd!c0d0'
get_major_minor: dev='48:0
'
get_major_minor: found majorH, minor=0
get_blockdev_parent: rd!c0d0 not a partition
sysfs_path_is_link: stat() failed
sysfs_path_is_link: stat() failed
sysfs_path_is_link: stat() failed
sysfs_path_is_link: stat() failed
sysfs_path_is_link: stat() failed
sysfs_path_is_link: stat() failed
sysfs_path_is_link: stat() failed
sysfs_path_is_link: stat() failed
sysfs_path_is_link: stat() failed
sysfs_path_is_link: stat() failed
get_sysfs_device: timed out waiting for device symlink, continuing on anyway...
namedev_name_device: class_dev->name = 'rd!c0d0'
namedev_name_device: udev->kernel_name = 'rd/c0d0'
namedev_name_device: kernel_number='0'
namedev_name_device: name, 'rd!c0d0' is going to have owner='root', group='root', mode = 0600
udev_add_device: name='rd!c0d0'
creating device node '/dev/rd!c0d0'
create_node: mknod(/dev/rd!c0d0, 020600, 48, 0)
create_node: chmod(/dev/rd!c0d0, 020600)

> 
> thanks,
> 
> greg k-h

thanks,
claude -


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&op=click
_______________________________________________
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:[~2004-02-16  7:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-05 23:02 Udev and Mylex Dac960 claude
2004-02-06  0:07 ` Greg KH
2004-02-06 14:40 ` claude
2004-02-07 19:04 ` claude
2004-02-11 23:49 ` Greg KH
2004-02-12  1:41 ` Greg KH
2004-02-12  2:02 ` claude
2004-02-13 21:05 ` Greg KH
2004-02-16  5:46 ` claude
2004-02-16  5:52 ` Greg KH
2004-02-16  7:35 ` claude [this message]
2004-02-16 18:22 ` Greg KH
2004-02-16 20:10 ` claude

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=403072B0.5010903@snscrew.net \
    --to=claude@snscrew.net \
    --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.