-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Jeremy Katz wrote:
|
| I'm not entirely convinced on this front -- this then requires a lot of
| manual work to find and mount the rootfs and thus avoids testing one of
| the biggest parts of rescue mode (finding and mounting the root). We're
| probably better off doing the mount through the normal paths if you're
| doing kickstart rescue mode
|
Leaving aside the mount of the root fs we can test other stuff: FirstAidKit
(although you can test it by other means also), if the rescue environment is
sane (e.g. bash is there), if we can chroot into the system (given we've mounted
that by hand), network setup, anything else people will do if they boot with
nomount and start poking around in the shell.
I agree with doing the mount through the current code but how do we cleanly
avoid the places where the user is asked to make a decision:
Mount: Read/Write, Read only, Skip ?
What partition contains the root fs?
Any assumption to answers of these questions will be generally wrong and will
break on different systems. The only possible way I see is to add additional
command{s} to kickstart which answer them. E.g.
In the case of a single command:
parttomount --dev /dev/sda1 --mode r --fstype ext3 --path /mnt/sysimage
I'm OK with adding this to kickstart but wanted to see what others think.
Thanks,
Alexander.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Red Hat - http://enigmail.mozdev.org
iD8DBQFIhzJfhmd3WOiFct4RCk7yAJ9CM9RbPlvTk8dSlCPALFcDcMZeNgCfT6TM
pwbH+SWiwiewaAmXAl0BfHk=
=6Ggg
-----END PGP SIGNATURE-----
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
