OK, the complete hack but would probably get what you wanted is to
background a script with nohup (I don't know if it is in the install
envronment, but
it could be put there pretty easily) that searches for anaconda processes
and
kills them, and then it does what you want. This again is a hack and is
violent,
but I think you could make it work reliably...james
"Bodle, Donald E"
<donald_bodle@reyrey To: "'kickstart-list@xxxxxxxxxx'" <kickstart-list@xxxxxxxxxx>
.com> cc:
Sent by: Subject: RE: Terminate a CDROM install from %pre
kickstart-list-admin
@redhat.com
04/03/03 08:12 AM
Please respond to
kickstart-list
Well, I appreciate all the discussion, and I realize my wants may have
broader implications.
We are trying to do as few distribution source modifications as possible,
so
I will probably do a little more experimentation.
I know I can halt the install with a simple "read dummy <
/dev/tty<whichever>" after echoing out something like "Critical
preinstallation step has failed, press system reset button and eject CDROM"
> /dev/tty<whichever>. I was just hoping for a little less manual
intervention. I imagine that an eject command would fail because the
device
is busy. Otherwise, I'd do a reboot from the %pre.
I presume there is yet hope. I believe if there is a python exception
(like
a malformed comps file), the install will halt. (although, as I recall,
the
system does not automatically reboot because it wants you to look at the
debug output) Not being a python programmer (yet, anyway), perhaps there
is
a way to invoke whatever python error-handler gets called from my %pre
script?
Thanks for all the suggestions.
Donald E. Bodle, Jr.
Sr. Systems Integration Engineer
Platform Development
The Reynolds and Reynolds Co.
(937) 485-1954
-----Original Message-----
From: John [mailto:red@xxxxxxxxxxxxxxxxxxxxxxx]
Sent: Wednesday, April 02, 2003 8:07 PM
To: kickstart-list@xxxxxxxxxx
Subject: RE: Terminate a CDROM install from %pre
On Wed, 2 Apr 2003 james.oden@xxxxxxxxxxx wrote:
> an error to whatever called it, to get the thing to stop properly. At
> anyrate its easy to see that there was no
> intention of even caring about return codes from %pre scripts (or %post
> scripts for that matter), which I
> thinks is the wrong thing to do, or at least there should be an option to
> request it to do this, but in most
> cases if the %pre goes bad, I don't want the install to continue. In our
> case when %pre goes bad
> usually shortly there after anaconda goes completley off the rails and we
> get a python exception.
Clearly, change that behaviour now is going to upset folks.
What happens if you remove the ks file in your %pre script?
I think this could be made an acceptable way to stop a ks install at
that point. Jeremy may accept a patch to that effect.
--
Please, reply only to the list.
_______________________________________________
Kickstart-list mailing list
Kickstart-list@xxxxxxxxxx
https://listman.redhat.com/mailman/listinfo/kickstart-list
_______________________________________________
Kickstart-list mailing list
Kickstart-list@xxxxxxxxxx
https://listman.redhat.com/mailman/listinfo/kickstart-list
