Shaul Karl <[EMAIL PROTECTED]> writes: > With linux 2.6.4 and Debian, in the boot process, I get: > > INIT: version 2.85 > umount /initrd: device busy > > Those lines are taken from memory but I hope they will resemble the > original ones. Putting it otherwise, immediately after starting init, > there is an attempt to umount /initrd. And it fails. Is this failure a > bug (with Debian's mkinitrd)?
/sbin/mkinitrd is normally a shell script, so you can look at it. Another place to look is the initrd itself, especially the file called /initrd/linuxrc, which is the main result of mkinitrd. I don't have a Debian system to look at, so I cannot help you directly. If /initrd is not mounted, then do sth like the following (YMMV): # gunzip -c /boot/initrd.img > /tmp/initrd # mount /tmp/initrd /mnt/initrd -o loop There should be a script called /mnt/initrd/linuxrc - look at it, if you are still puzzled - post it, it should be small enough. Reverse the operations above: # umount /mnt/initrd # gzip -c -9 /tmp/initrd > /boot/initrd.img I am assuming that Debian is similar enough to Red Hat, so the above is applicable in your parallel universe. Hope it helps, -- Oleg Goldshmidt | [EMAIL PROTECTED] ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
