maier@xxxxxxxxxxxxxxxxxx@redhat.com wrote on 12/11/2009 08:13:51 AM:
> > diff --git a/gui.py b/gui.py
> > index 4379bec..e1753e3 100755
> > --- a/gui.py
> > +++ b/gui.py
> > @@ -1324,6 +1324,7 @@ class InstallControlWindow:
> > takeScreenShot()
> >
> > def _doExit (self, *args):
> > + iutil.dumpReIPLFiles ()
> > gtk.main_quit()
> > os._exit(0)
> >
>
> Can anyone please confirm that those two places are really the only ones
> where anaconda may exit for a (successful) installation?
> If there will be a global exit handler with Chris' reboot rework, then
> we could trigger an lsreipl there.
Ditto. Can anyone please confirm that those two places are really the only ones
where anaconda may exit for a (successful) installation?
> Instead of letting anaconda interpret the current reipl settings, I now
> realized that we have lsreipl from s390utils in stage2 (and even stage1
> since dae98456cac25415bb05464138a52b583aaebb2b). This tool gets
> maintained and will be adapted should the reipl interface change.
> Calling this existing tool might make life easier, if it provides all
> the output you intended to get.
That is a good idea. Unfortunately, lsreipl is NOT on the root image
when anaconda is run. I do see that it is in scripts/upd-instroot and
scripts/mk-images. But it is not in initrd.img or install.img. So what
am I missing?
--
Mark
You must be the change you wish to see in the world. -- Mahatma Gandhi
Worrying is praying for that you do not wish to happen.
_______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
