udevd is called from /scripts/init-premount/udev (line 17)
udevd is definitely present in the root of the temporary file system.
But it is called without leading '/'
Not sure whether that is the error.
Continue to search...
jlinkels
On Monday 22 September 2008 01:25:11 Graham wrote:
> Hi again,
>
> If I'm not mistaken, the "/dev/disk/by-uuid" stuff is generated by
> udev, so check whether you have that installed.
>
> I believe that udev is optional, but on any normal system, it's
> probably desirable.
>
> -- graham
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
09-22-2008, 03:30 PM
Graham
Bug#499575: Do you have udev installed?
> I unpacked the initrd.img file and checked the existence of udev in the initrd
> file, and this is what find gives me:
> ./etc/udev
> ./etc/udev/rules.d/50-udev.rules
> ./etc/udev/udev.conf
> ./lib/udev
> ./scripts/init-bottom/udev
> ./scripts/init-premount/udev
> ./scripts/local-top/udev_helper
> ./udevd
> ./udevadm
> ./udevsettle
That matches what I see on my Etch system, which is still running
Linux 2.6.18. I find it somewhat odd that the udev binaries are in the
root of the initramfs, because I would not expect "/" or "." to be in
the PATH.
It may be interesting to note that my Lenny/Sid system is different.
Which is shipped in the udev package. In Etch (udev 0.105-4), I see this:
copy_exec /sbin/udevd /sbin/
In Lenny (udev 0.125-6), it is similar except that the trailing
slashes are missing. AFAICT this makes no difference.
The copy_exec function is defined in:
/usr/share/initramfs-tools/hook-functions
Without reading into it too much, there seems to be significant
differences between Etch (initramfs-tools 0.85i) and Lenny
(initramfs-tools 0.92l).
I don't see anything in the initramfs that defines the PATH, so I
would guess that it just uses the shell's default PATH -- and maybe
that has changed between Etch and Lenny? (seems unlikely, but not
impossible)
I'm not sure where to go from here, and I don't know why your system
is broken. But I might be able to try to reproduce this on my firewall
PC later, which is still mostly running Etch.
-- graham
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
09-22-2008, 03:42 PM
Graham
Bug#499575: Do you have udev installed?
> In Lenny (udev 0.125-6), it is similar
Correction: I was looking at udev 0.125-7.
Bug 498686 may be of interest here.
-- graham
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
09-22-2008, 07:51 PM
Johannes Linkels
Bug#499575: Do you have udev installed?
Hi Graham,
I had seen that bug before, but it did not make any sense to me. Now knowing
that various executables of udev could not be found, it does make much more
sense!
If I look at the date, this discussion is very, very recent, so recent that it
is likely that I have not apt-get updated since then.
I made some progress yesterday night. After manually poking '/' in front of
the programs, udev did run.
My /dev was filled now with hda1, hdc1, hdc3 etc., but NOT
with /dev/disk/by-uuid and all that stuff. Which probably means that if I
change my boot parameter back to root=/dev/hdc1 the think might actually
boot.
It is an interesting experiment which I could try tonight. Nevertheless, if I
can get it just right I am happier. After all, I am wondering why udev does't
create the disk/by-uuid nodes. It does so when I boot kernel 2.6.22, and
that is Lenny as well. But I did not generate a initrd myself for this
kernel. The initrd might be older and not suffering from bug 498686.
I will also try and see if I can download the new version of udev. And take a
careful look at your directory listings.
Thanks
Hans
On Monday 22 September 2008 11:42, Graham wrote:
> > In Lenny (udev 0.125-6), it is similar
>
> Correction: I was looking at udev 0.125-7.
>
> Bug 498686 may be of interest here.
>
> -- graham
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org