udevinfo messages

While trying to get 2.6.11 running on my Suse 9.1 system I encountered some problems with mkinitrd and the udev package Suse uses (seems to be a patched udev-052 version). I noticed a few funny synlinks within /dev:

lrwxrwxrwx  1 root root 4 2005-03-21 15:33:54.196950896 +0100 device2 -> hda2
lrwxrwxrwx  1 root root 4 2005-03-21 15:33:54.196950896 +0100 not2 -> hda2
lrwxrwxrwx  1 root root 4 2005-03-21 15:33:54.196950896 +0100 found2 -> hda2
lrwxrwxrwx  1 root root 4 2005-03-21 15:33:54.196950896 +0100 in2 -> hda2
lrwxrwxrwx  1 root root 4 2005-03-21 15:33:54.196950896 +0100 database2 -> hda2
lrwxrwxrwx  1 root root 4 2005-03-21 15:33:54.471909096 +0100 device1 -> hdc1
lrwxrwxrwx  1 root root 4 2005-03-21 15:33:54.471909096 +0100 not1 -> hdc1
lrwxrwxrwx  1 root root 4 2005-03-21 15:33:54.471909096 +0100 found1 -> hdc1
lrwxrwxrwx  1 root root 4 2005-03-21 15:33:54.471909096 +0100 in1 -> hdc1
lrwxrwxrwx  1 root root 4 2005-03-21 15:33:54.471909096 +0100 database1 -> hdc1
lrwxrwxrwx  1 root root 3 2005-03-21 15:33:54.785861368 +0100 mknod: -> hda
lrwxrwxrwx  1 root root 3 2005-03-21 15:33:54.785861368 +0100 No -> hda
lrwxrwxrwx  1 root root 3 2005-03-21 15:33:54.785861368 +0100 such -> hda
lrwxrwxrwx  1 root root 3 2005-03-21 15:33:54.785861368 +0100 file -> hda
lrwxrwxrwx  1 root root 3 2005-03-21 15:33:54.785861368 +0100 or -> hda
lrwxrwxrwx  1 root root 3 2005-03-21 15:33:54.785861368 +0100 directory\nata_identify: -> hda
lrwxrwxrwx  1 root root 4 2005-03-21 15:33:54.844852400 +0100 mknod:1 -> hdg1
lrwxrwxrwx  1 root root 4 2005-03-21 15:33:54.844852400 +0100 No1 -> hdg1
lrwxrwxrwx  1 root root 4 2005-03-21 15:33:54.844852400 +0100 such1 -> hdg1
lrwxrwxrwx  1 root root 4 2005-03-21 15:33:54.844852400 +0100 file1 -> hdg1
lrwxrwxrwx  1 root root 4 2005-03-21 15:33:54.844852400 +0100 or1 -> hdg1
lrwxrwxrwx  1 root root 4 2005-03-21 15:33:54.844852400 +0100 directory1 -> hdg1

I don't know exactly, what caused this in depth. But I found udevinfo prints all error messages to stdout instead of using stderr, like:

if (retval != 0) {
     printf("device not found in database\n");
     goto exit;
}

seems this is taken as a list of symliks to create.

Seems there is some "ata_identify" utility involved, but I could not find how this is used. It does not apear within the official udev-056 release. Seems to be some SuSE/Redhad addition.

Can some one give me a hint, how to debug this? During boot there are some messages scrolling by, but finally the console-font gets switched which clips off my console history :-(

Dieter.

Dieter Stüken, con terra GmbH, Münster
     [email protected]
     http://www.conterra.de/
     (0)251-7474-501


-------------------------------------------------------
This SF.net email is sponsored by: 2005 Windows Mobile Application Contest
Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones
for the chance to win $25,000 and application distribution. Enter today at
http://ads.osdn.com/?ad_idh82&alloc_id148&opÌk
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Ah, ok. I will change this. Thanks!

This looks pretty funny. :)

You may search for PROGRAM= keys in all files in:
/etc/udev/rules.d/

This is the only way to call external stuff from udev. One of these rules should match for ide-block-devices and seems to call udevinfo.

Good luck,
Kay

-------------------------------------------------------
This SF.net email is sponsored by Microsoft Mobile & Embedded DevCon 2005 Attend MEDC 2005 May 9-12 in Vegas. Learn more about the latest Windows Embedded(r) & Windows Mobile(tm) platforms, applications & content. Register by 3/29 & save $300 http://ads.osdn.com/?ad_idh83&alloc_id149&opÌk
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

got it; it was hidden within a couple of additional scripts. Udevinfo correctly returns an exit code, to flag the message as an error. This was not tested by the scripts. But writing to stderr would make sense anyway.

Dieter.

Dieter Stüken, con terra GmbH, Münster
     [email protected]
     http://www.conterra.de/
     (0)251-7474-501


-------------------------------------------------------
This SF.net email is sponsored by Microsoft Mobile & Embedded DevCon 2005
Attend MEDC 2005 May 9-12 in Vegas. Learn more about the latest Windows
Embedded(r) & Windows Mobile(tm) platforms, applications & content.  Register
by 3/29 & save $300 http://ads.osdn.com/?ad_idh83&alloc_id149&op�k
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel