Quoting Jacques Gelinas ([EMAIL PROTECTED]):
> > Ok, I browsed a bit though the linuxconf source (there are comments *gasp*).
> > What I finally came up with is this: If linuxconf prints a "*" (asterix)
> > before a line, this line was written to stderr and the internal error
> > counter is increased for each such line. Why is this ? Shouldn't
> > linuxconf solely rely on the return code ?
> >
> > The offending command in my setup is /bin/loadkeys which prints the
> > name of the keymap to stderr. What should I do ?
>
> Linuxconf monitors the error channel of the command it launch.
> Unfortunatly, no tool before linuxconf tried to log and make some sens out
> of the message produced by the boot sequence.
>
> the error channel is meant to report errors. Unfortunatly, there are still
> commands out there that think it is cool to present greating on the error
> channel (loadkeys, dhcpd server). Other send error message, but do not
> return any error code.
>
> My goal is to create some awareness and those things will be fixed.
Ok. I downloaded the SRPM and patched it. Now it works. What should I
do with the patch ?
--
Aaron "Optimizer" Digulla Team AMIGA AROS Head of Development
Author of XDME, ResTrackLib, CInt. <http://www.aros.org/>
"(to) optimize: Make a program faster by improving the algorithms rather than
by buying a faster machine."
---
You are currently subscribed to linuxconf as: [[email protected]]
To unsubscribe, forward this message to [EMAIL PROTECTED]
