We're dealing some pre- and postinstall scripts and we've just tried to redirect the outputs of a script inside the %pre section of ks. This wasn't successful, all the debug and info messages appeared on tty1, so I removed this redirection from kickstart file. But after building a new iso we see the same redirections during installation. I've double- and triplechecked the ks.cfg file, there are no redirections anywhere, despite of this anaconda shows everything on the first console.
What/where could be the problem?
Laszlo BERES wrote:
We're dealing some pre- and postinstall scripts and we've just tried to redirect the outputs of a script inside the %pre section of ks. This wasn't successful, all the debug and info messages appeared on tty1, so I removed this redirection from kickstart file. But after building a new iso we see the same redirections during installation. I've double- and triplechecked the ks.cfg file, there are no redirections anywhere, despite of this anaconda shows everything on the first console.
What/where could be the problem?
Does /tmp/ks.cfg (during the installation procedure) show the redirection? /tmp/ks.cfg is where anaconda writes out the kickstart file it is using.
If it does, anaconda may not be using the same ks.cfg you intend it to. Do you have or did you have any other kickstart files laying around for anaconda to pick up?
Kind regards,
Jeroen van Meeuwen -kanarip
Jeroen van Meeuwen wrote:
Do you have or did you have any other kickstart files laying around for anaconda to pick up?
Thanks for your reply, the solution was somewhere else :) For curiosity I've enabled the updates repo in the configfile, and one of the PackageKit updates was broken so this blocked some DBUS mechanism in Anaconda.
After removing the updates repo, the messages has disappeared.
revisor-users@lists.fedorahosted.org
-
Jeroen van Meeuwen -
Laszlo BERES