On Sun, 2005-08-14 at 04:00 +0200, Marco d'Itri wrote:
> On Jul 28, Mourad De Clerck <email address hidden> wrote:
> > Let me know how I can help you chase down this bug.
> Please check if you can still reproduce this bug with udev 066 and a
> 2.6.12 kernel.
Unfortunately, using linux-image-2.6.12-1-k7 2.6.12-2 and udev 0.066-1 I
can still reproduce this bug. After boot certain devices don't show up,
but after running udevstart they seem to be there. Compared to the
previous udev version I checked where only /dev/input/mice was affected,
now my cdrw/dvd devices seem to be affected too:
On Sun, 2005-08-14 at 04:00 +0200, Marco d'Itri wrote:
> On Jul 28, Mourad De Clerck <email address hidden> wrote:
> > Let me know how I can help you chase down this bug.
> Please check if you can still reproduce this bug with udev 066 and a
> 2.6.12 kernel.
Unfortunately, using linux-image- 2.6.12- 1-k7 2.6.12-2 and udev 0.066-1 I
can still reproduce this bug. After boot certain devices don't show up,
but after running udevstart they seem to be there. Compared to the
previous udev version I checked where only /dev/input/mice was affected,
now my cdrw/dvd devices seem to be affected too:
--- dev_after_boot.txt 2005-08-14 14:33:44.000000000 +0200 udevstart. txt 2005-08-14 14:34:06.000000000 +0200 udevdb/ class@input@ mice udevdb/ block@hdc udevdb/ class@input@ event5
+++ dev_after_
@@ -1,2 +1,5 @@
/dev/
+/dev/dvd
+/dev/cdrw
+/dev/cdrom
/dev/vcsa5
@@ -20,2 +23,3 @@
/dev/input
+/dev/input/mice
/dev/input/event5
@@ -745,2 +749,4 @@
/dev/.udevdb
+/dev/.
+/dev/.
/dev/.
-- Mourad