On 2012-07-28 15:57, Bruno Wolff III wrote:
On Sat, Jul 28, 2012 at 15:39:17 +0200,
Hello,*
I still cannot boot directly on the damage installation
What is bizard is that the installer of fedora 16 can see the
installation
but not fedora 17.
How can I force fedora 17 to update the installation?
Thank.
I made a /dev/urandom and a /dev/null after a chroot and it seems
fine.
Which command create the /dev/* at boot?
Is there anyway to repair the installation now that I run (after a
chroot)?
If you are trying to do rescue in a change route, then what you want
to do is a bind mount. You'll probably also want /sys, /proc and
maybe
/run.
So for example if you were running a system from an initramfs or
other kind of rescue environment and the rootfs was on /dev/sda1,
/boot was on /dev/sda2 and /home was on /dev/sda3 you might do the
following:
mkdir /sysimage
mount /dev/sda1 /sysimage
mount -o bind /dev /sysimage/dev
mount -o bind /sys /sysimage/sys
mount -o bind /proc /sysimage/proc
mount -o bind /run /sysimage/run
mount /dev/sda2 /sysimage/boot
mount /dev/sda3 /sysimage/home
chroot /sysimage
At that point you should be able to run things like yum to repair the
system.
You'll eventually want to relabel the system (once you have it
working again). You can touch /.autorelabel (in the chroot) to flag
this to happen at the next boot.
--
======================================================================
Patrick DUPRÉ | | email: pdupre@xxxxxxxxxx
======================================================================
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
