-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Jeremy Katz wrote: | | Either a new directive or just doing the sane default (r/w) if we're in | kickstart mode. Arguably, we should have a 'rescue' directive that acts | like upgrade and others and kicks us into rescue mode so that you can | have everything for rescue mode specified in the ks.cfg. Then you'd | have | rescue | rescue --nomount | rescue --romount | |> What partition contains the root fs? | | The easy answer is that we just do the first. And then if we think that | caring about multiple roots[1] is important, then we should do it in a | way that generalizes and also helps the upgrade case | What I lean towards is the following: 1) Add a 'rescue' directive in kickstart for the sake of completeness (see above), but without any options. 2) Add a new directive in kickstart so it describes what partitions and where to mount them (as described in previous e-mail). 3) In rescue mode based on 2) try to mount the partitions. 4) If 2) is not present in kickstart then try some defaults if they fail, don't try anything else. 5) Execute the %post scripts after everything is done. Upgrade mode can also be modified to use 2) if present. It's a bigger change than the proposed one but I'd prefer adding all the bits now instead of doing the defaults (or --nomount, --romount) for rescue mode and later (not known when) adding the support for multiple roots. Thanks, Alexander. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Red Hat - http://enigmail.mozdev.org iD8DBQFIiC/ehmd3WOiFct4RCgajAJ9WHuXO01T6R04LiflZQoUNdbpKdwCfdpyI xwgEInIyLlhTFxoW+4heSfI= =+vF+ -----END PGP SIGNATURE----- _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
