I tried to boot by editting the grub entry with 'init=/bin/bash', but it did not work
The error message was 'exec of init ('/bin/bash') failed!!!! No such file or directory.
With the resuce disc, it's complaining about the same sort of thing. When I run
'chroot /mnt/sysimage' is complains it can not find /bin/sh. The rescue disc
does find all the drives and the proper files links are in mnt. But can't mount
it to make it writable.
Any other suggestions. I don't get it. Especially when there are a few people
that reverted back fine.
Dwaine
----- Original Message ----
From: Michal Jaegermann <michal@xxxxxxxxxxxx>
To: For testers of Fedora Core development releases <fedora-test-list@xxxxxxxxxx>
Sent: Saturday, October 28, 2006 11:33:30 PM
Subject: Re: new problem with graphical login
From: Michal Jaegermann <michal@xxxxxxxxxxxx>
To: For testers of Fedora Core development releases <fedora-test-list@xxxxxxxxxx>
Sent: Saturday, October 28, 2006 11:33:30 PM
Subject: Re: new problem with graphical login
On Sat, Oct 28, 2006 at 07:17:13PM -0400, Dwaine Garden wrote:
> I reverted back, I did have a copy of the rpms. rpm
> did update the box, but failed on "Script errors" for
> glibc 2.5.90.
There is an option '--noscripts' which allows you to skip
scripts in case of errors. Installing glibc does
re-execute init.
> Now the box will not boot with an init error.
How about booting with 'init=/bin/bash'?
> Any help.. Please... I tried the rescue disk, but
> not help.
Could you be more specific what "not help" means (and stop
top-posting)? Rescue disk should use its own libraries.
At least this is the case if you will boot from an installation
disk with 'linux rescue'. Mount your disks writable, i.e.
"Continue" when asked. rpm has an option '--root' which
allows you to change a tree which will be affected by operations
so you can fix things if you really have a mess on your hands.
If you cannot boot "rescue" then you likely have a hardware
problem.
Michal
--
fedora-test-list mailing list
fedora-test-list@xxxxxxxxxx
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-test-list
> I reverted back, I did have a copy of the rpms. rpm
> did update the box, but failed on "Script errors" for
> glibc 2.5.90.
There is an option '--noscripts' which allows you to skip
scripts in case of errors. Installing glibc does
re-execute init.
> Now the box will not boot with an init error.
How about booting with 'init=/bin/bash'?
> Any help.. Please... I tried the rescue disk, but
> not help.
Could you be more specific what "not help" means (and stop
top-posting)? Rescue disk should use its own libraries.
At least this is the case if you will boot from an installation
disk with 'linux rescue'. Mount your disks writable, i.e.
"Continue" when asked. rpm has an option '--root' which
allows you to change a tree which will be affected by operations
so you can fix things if you really have a mess on your hands.
If you cannot boot "rescue" then you likely have a hardware
problem.
Michal
--
fedora-test-list mailing list
fedora-test-list@xxxxxxxxxx
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-test-list
-- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list