Bug 124096

Summary:	udev-start.sh looks for block devices even if they don't exist
Product:	Gentoo Linux	Reporter:	Michael Hordijk <hoffbrinkle>
Component:	[OLD] Core system	Assignee:	Greg Kroah-Hartman (RETIRED) <gregkh>
Status:	RESOLVED WONTFIX
Severity:	trivial
Priority:	High
Version:	2005.1
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Michael Hordijk 2006-02-25 12:08:05 UTC

udev-start.sh, line 25:

   list="$list $(echo /sys/block/*/uevent /sys/block/*/*/uevent)"

My system:

   $ ls -a /sys/block/
   .  ..

Results in messages like this on start up:

   /lib/rcscripts/addons/udev-start.sh: line 46: /sys/block/*/uevent: No such file or directory

This is with udev-079-r1

Comment 1 Greg Kroah-Hartman (RETIRED) gentoo-dev

2006-02-25 21:24:01 UTC

How can you not have any block devices in your system?  How do you boot?

Comment 2 Michael Hordijk 2006-02-26 08:01:48 UTC

(In reply to comment #1)
> How can you not have any block devices in your system?  How do you boot?

Why net boot, of course.  :)

I've found that Gentoo and it's genkernel combined with unionfs make for really easy to maintain netboot environment.  We do a lot of hardware development on heterogeneous platforms and some custom kernel modules, and udev is pretty handy.

Another minor note is that you may want to update the comment in udev.conf regarding logging.  I believe the choices for udev_log are now "err," "debug," or "info."

Comment 3 Greg Kroah-Hartman (RETIRED) gentoo-dev

2006-03-01 16:26:57 UTC

Heh, ok.  I'm not going to change this, unless you can come up with 
a patch that works, as it's quite rare :)