On Aug 25, 2008, at 6:04 AM, Steffen Maier wrote:Hi David, Jeremy, John, do you have any new comments on our discussion? On 08/11/2008 10:45 AM, Steffen Maier wrote: any news or new opinions from your side concerning Mark's work on supporting automatic reboot after the 1st install phase by integrating the s390 reipl feature into anaconda? Is Reipl.py a new command for the distribution? It contains option parsing and other things that you'd find in a command line tool. If it is, where is it to live? If it's not a command and the functionality is to be added to anaconda, is there anyway it can be significantly reduced? All of the sanity checking code and sysfs finding code....is any of that really necessary? In anaconda we can assume sysfs is mounted to /sys, for example. But, if Reipl.py is a new system command, I can see how you'd want it to hunt around for sysfs. I mean, what needs to happen in anaconda for reipl to work? We need to transform the boot device (which we know in anaconda) to the special format to write to the sysfs files, right? Going back to what Jeremy was saying a while back, this should be a simple task for anaconda. Try to write the reipl device, nothing more. If it fails, it fails. As he noted, we don't do anything special for grub failures because we can't really. On s390 we do gain a little more, but to keep the installer in line with other platforms, let's keep the failure handling to logging a message in anaconda and continuing anyway. -- David Cantrell <dcantrell@xxxxxxxxxx> Red Hat / Honolulu, HI |
_______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
