On Thu, Oct 30, 2008 at 01:42:58PM -0400, Chris Lumens wrote: > > Maybe we should have our own newtWinMessage that calls startNewt first. > > But that's probably a post-F10 sort of thing. > > I like this idea. I as well. > > So for F10, our best > > choices are probably go through and try to add some startNewt() calls or > > just do it early and deal with the blue screen people will get. I don't > > really have a strong leaning either way > > Yeah, I don't either. If we put off thinking about it for another hour > or two, David will show up and then he can look and tell us if the > startNewt calls are going to be pretty straightforward to add. Nothing is straightforward about newt. I would prefer our own wrapper function that calls startNewt() and takes in to account whether or not it should, what to do on the various bastard architectures, and so on. Less intrusive to the main code. As for the blue screen appearing early, I don't care about that. But we should make sure that we don't try to do that on systems that will crash and burn if we try to start up. -- David Cantrell <dcantrell@xxxxxxxxxx> Red Hat / Honolulu, HI
Attachment:
pgpAnia93Hafv.pgp
Description: PGP signature
_______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
