Re: [PATCH] kickstart.py: Fix stdoutLog not being defined

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

 



On 01/14/2010 03:31 PM, Chris Lumens wrote:
Note we are using "print" in various places in kickstart.py, these
messages won't get logged, maybe we should convert those places to
use stdoutLog ?

The things we print in kickstart are parse errors that can't be
displayed in a graphical window because there's no intf yet.  We could
probably do logging on them, but we need to make sure they go to
tty1/console/wherever to make sure they show up on serial installs as
well.  Didn't we used to have a stderrLog in anaconda?


stderrLog: not that I remember, but it will be easy for me to add it. I guess this is a thing for me to look at.

Ales

_______________________________________________
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