Syslinux - Nov 2010 - New 'quiet' behavior - optional?

Syslinux version 3.74 introduced the following change (I know, old news really)

-> Suppress the Loading ... message if "quiet" is specified on the
kernel command line.

Unfortunately, for our PXELinux environment this was a very unwanted
change.  The linux command line parameter 'quiet' is included and
passed to linux because we want (and in cases absolutely require) that
the kernel be booted in quiet mode.  However, since 3.74 this also
means that PXELinux runs quietly, making it impossible to see if the
image is properly loading, or if it is stalled, or slow.   We appear
to be left with no way to specify (that I can find) the quietness of
the two independently.  (In my view, it was undesirable to piggyback
off of an already existing commonly used parameter - making it
impossible to separate the two).  This means we are left with two
undesirable choices, to either run completely silent (making network
or server or pxe firmware problems very difficult to detect), or run
without quiet completely, which causes us problems on the linux side.

Any workable suggestions with the current code (running 4.03 now)?  Or
do I need to work on a environment where I can custom build my own
pxelinux.0 or gpxelinux.0?

(I'm assuming there's near zero chance of me convincing you to change
the existing behavior. As I recognize it's a beneficial behavior in
probably 99% of cases).

Thanks,

-Ken

On 11/22/2010 03:24 PM, Kenneth Morse wrote:
> Syslinux version 3.74 introduced the following change (I know, old news
really)
> 
> -> Suppress the Loading ... message if "quiet" is specified on
the
> kernel command line.
> 
> Unfortunately, for our PXELinux environment this was a very unwanted
> change.  The linux command line parameter 'quiet' is included and
> passed to linux because we want (and in cases absolutely require) that
> the kernel be booted in quiet mode.  However, since 3.74 this also
> means that PXELinux runs quietly, making it impossible to see if the
> image is properly loading, or if it is stalled, or slow.   We appear
> to be left with no way to specify (that I can find) the quietness of
> the two independently.  (In my view, it was undesirable to piggyback
> off of an already existing commonly used parameter - making it
> impossible to separate the two).  This means we are left with two
> undesirable choices, to either run completely silent (making network
> or server or pxe firmware problems very difficult to detect), or run
> without quiet completely, which causes us problems on the linux side.
> 
> Any workable suggestions with the current code (running 4.03 now)?  Or
> do I need to work on a environment where I can custom build my own
> pxelinux.0 or gpxelinux.0?
> 
> (I'm assuming there's near zero chance of me convincing you to
change
> the existing behavior. As I recognize it's a beneficial behavior in
> probably 99% of cases).
> 
Use "loglevel=4" instead of "quiet".

	-hpa

On Mon, Nov 22, 2010 at 9:24 PM, Kenneth Morse <kdmorse at gmail.com>
wrote:
> Syslinux version 3.74 introduced the following change (I know, old news
really)
>
> -> Suppress the Loading ... message if "quiet" is specified on
the
> kernel command line.
>
> Unfortunately, for our PXELinux environment this was a very unwanted
> change. ?The linux command line parameter 'quiet' is included and
> passed to linux because we want (and in cases absolutely require) that
> the kernel be booted in quiet mode. ?However, since 3.74 this also
> means that PXELinux runs quietly, making it impossible to see if the
> image is properly loading, or if it is stalled, or slow. ? We appear
> to be left with no way to specify (that I can find) the quietness of
> the two independently. ?(In my view, it was undesirable to piggyback
> off of an already existing commonly used parameter - making it
> impossible to separate the two). ?This means we are left with two
> undesirable choices, to either run completely silent (making network
> or server or pxe firmware problems very difficult to detect), or run
> without quiet completely, which causes us problems on the linux side.
>
> Any workable suggestions with the current code (running 4.03 now)? ?Or
> do I need to work on a environment where I can custom build my own
> pxelinux.0 or gpxelinux.0?
>
> (I'm assuming there's near zero chance of me convincing you to
change
> the existing behavior. As I recognize it's a beneficial behavior in
> probably 99% of cases).
I think it'd be great if we could separate the 'quiet' command for
Linux and for syslinux. Moreover, if we have a 'quiet' command for
syslinux, would it be possible to turn off the Copyright message?


regards,

Lucas De Marchi