-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, 21 Jan 2010, Ales Kozumplik wrote:
On 01/21/2010 05:23 PM, Steffen Maier wrote:
On 01/21/2010 04:33 PM, Ales Kozumplik wrote:
On 01/21/2010 04:26 PM, Ales Kozumplik wrote:
dcantrell's recent change to the shutdown mechanism exposed a
situation when
shutdown is correctly handled but the init's exit handler still gets
called and
dumps its callstack, that's not desirable because (in case of an
exception in
python code for example) part of the useful information on the screen is
scrolled out of view.
---
Note that there still will be kernel panic displayed and the machine
won't react on ctrl-alt-del (VMWare). An endless sleepy loop could be a
way out perhaps?
Right, the loop is what used to be there. I kind of liked it but it
requires a separation of the two cases: loader returning with error vs.
s390 needing init to halt. If nobody has any real need for waiting at
this point any longer, we could alternatively call performReboot for all
cases of rebootAction, even for HALT.
(See also
https://www.redhat.com/archives/anaconda-devel-list/2010-January/msg00317.html)
Hi Steffen,
I'm not an shutdown expert, but we don't want to call performReboot in the
HALT case, that would make it the same as POWEROFF: not good because we
wouldn't be able to see the final output (in the frequent case of loader
SIGSEGV for example), as you mentioned in the second thread. The loop could
be one option, possibly with conditional code for S390 -- what do you think
David?
BTW Steffen, how does one halt the Linux kernel?
No opposition here.
- --
David Cantrell <dcantrell@xxxxxxxxxx>
Red Hat / Honolulu, HI
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
iEYEARECAAYFAktYofAACgkQ5hsjjIy1VkkHNACghRqC5SzabUXvyOPZAsi4Rynj
TG8Anilcj+GdscMT8whLtrLts4msofYf
=OqNi
-----END PGP SIGNATURE-----
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
