Re: Reipl support (John Summerfield)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Mark Hamzy wrote:
It's not clear to me _when_ this program is used. If you package it as
an rpm and installed on the target system, then Anaconda can run it from
there, but should chroot() to do so.

Reipl is called after anaconda has finished installing the target system
but before a reboot is performed.

If it might be used during the ordinary use of a Linux guest (as it
might be, if you have a recovery disk to IPL, repair something, then IPL
that something in the same  VM), then packaging it and installing to
/usr/sbin or /usr/bin is sensible. If it's only to be used at install
time, then you need to consider how it gets into the install image.
Someone else might address that, I'm not very good with that snake
either.

Reipl can be used duing install and it can be run at any time by a system
adminstrator.  It doesn't cause a reboot itself.  It only tells VM where
to reboot from if it ever were to reboot.

That's close to what LILO can do: I can't check the syntax (I don't have it installed), but when run with the proper operands, it says "next time, use _that_ menu entry." It can be used, for example, to run OS/2 on the next reboot, and after that it reverts to the default.

/sbin and /bin should be used for executables required before /usr gets
mounted. See www.pathname.com where the FHS might be found.

Ah, thanks.  I did not consider that possibility.  But it shouldn't
affect this patch as Reipl lives in the stage 2 image and not on the
target's system for the installation case.
If "it can be run at any time by a system adminstrator," then it needs to be installed on the target system. OTOH, I think that in the stage2 image all the *bin directories are the same, by use of symlinks.


I could not see where reipl executes any external program (but my python
is strictly  limited). If it's not executing other programs, PATH is
unimportant.

I didn't look for that (did I say I don't handle these snakes well?), but if it's not importing anything not already available to python, the point stands. And *bin directories aren't appropriate for python modules.




--

Cheers
John

-- spambait
1aaaaaaa@xxxxxxxxxxxxxxxx  Z1aaaaaaa@xxxxxxxxxxxxxxxx
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375

You cannot reply off-list:-)

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list

[Index of Archives]     [Kickstart]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]
  Powered by Linux