> > 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? Yes, I *think* those are the only places a successful installation will exit. Everywhere else we call sys.exit is from an exception handler, or you pressed "Reboot"/"Exit", or something like that. You can't just tell from the return codes, though. > > 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? Looks like scripts/upd-instroot refers to sbin/lsreipl, whereas it's in /usr/sbin/lsreipl in the package. Basically, all these commands should be audited to make sure we're referring to the right locations. - Chris _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
