I posted a few months ago about my boot process
stopping at:
mounting proc at /proc
I finally realized what was wrong when I chrooted in
and mount produced an error like "GLIBC no good". So
I emerge -C glibc, with intentions of reemerging. Obviosly, as I realized seconds later, this was a very
bad decision by Ben. Does anyone know if I can
recover from this? I think I'll just start gentoo
over again. But seriously, why did Gentoo screw up my
boot process (glibc) in the first place. Perhaps I'll
try Debain.
Thanks,
Ben
I never had such problem, but I would try to repair it using this scenario:
1. boot from gentoo live cd
2. make mountpoint for broken gentoo
3. mount broken gentoo
4. copy glibc library from live CD to broken gentoo
(list of needed files is in /var/db/pkg/sys-libs/glibc*/CONTENTS
it's plenty of files, but lot of them is not needed yet)
5. chroot to broken gentoo
6. source /etc/profile
7. emerge glibc (in chroot)HTH noro
-- [EMAIL PROTECTED] mailing list
