Le Mercredi 2 Avril 2003 12:21, Neil Bothwick a �crit : > Guillaume Cottenceau said, > > >> I tried the following but to no avail (maybe because of using the > >> freshly installed system by means of a chroot on /mnt) : > >> > >> boot rescue cd1 > >> mount all FS on /mnt > >> go to console > >> chroot /mnt > >> > >> First I was to mount /proc because mkinitrd _does not check_ that /proc > >> is available and thus we end in a loop at the step it scans for > >> /proc/mounts FS. > > > > I don't consider that to be a bug. Many (all?) of our system > > tools rely very much on /proc being available. I'm not even sure > > the system will boot without a /proc filesystem mounted. > > Isn't the problem that /proc disappears when you chroot to /mnt? Could > you solve this doing "mount --bind /proc /mnt/proc" when mounting > filesystems on /mnt, then /proc is still available after chrooting. > > > Cheers > > Neil
If this is true, then that was my problem on rescue mode. And that is why, Guillaume, an new rescue menu entry to rebuild a kernel initrd would be a plus in case someone has destroyed or corrupted it. (nothing to do with mdk installation here, just a new recovery tool) -- Pascal Cavy - VMF __________________________________________________________________ Running 22:40, 4 users, load average: 3.38, 3.20, 3.19 (gcc version 3.2.2 (Mandrake Linux 9.1 3.2.2-3mdk)) Kernel Linux version 2.4.21-0.13mdkenterprise
