What you did was bypass devfs, and cause create_dev to mknod a file
with the device number of your root instead of creating a symlink
to the normal devfs node.
Is your booter translating the device name into a number? You can
check this by looking at the printed comand line in the dmesg, or
by cat /proc/cmdline .
If you see root=0304 then your booter is translating the device number
and therefore find_in_devfs is failing (possibly because of the previously
metioned patch to read_dir).
I notice that there are lots of hardcoded maxdepth of 64 characters for
the devfs path, but yours seems to be 39 and therefore should be ok.
milton
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Nov 30 2002 - 22:00:11 EST