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

Bug#673207: /etc/default/rcS is perhaps a better place for FANCYTTY variable



Le 21.05.2012 15:07, Roger Leigh a écrit :
> On Mon, May 21, 2012 at 02:07:40PM +0200, Didier 'OdyX' Raboud wrote:
>> Hmm; now that I think of it, it would be possible to simply have
>> /etc/default/rcS ship an empty (or even commented) FANCYTTY= definition
>> and let /etc/lsb-base-logging.sh untouched: if an admin added a FANCYTTY
>> definition to his /e/lsb-base-logging.sh, then it would simply continue
>> to work; if he hasn't too and future users would be pointed at /e/d/rcS.
>> Nice.
> 
> Sounds ideal.  And by default all values in /e/d/rcS are commented, at
> least in current (experimental) versions.
> 
> So as discussed on #debian-devel, I'll do the following in initscripts:
> - make /etc/default/rcS a conffile
> - add FANCYTTY
> - add FANCYTTY to rcS(5)

Cool, thanks.

> For the latter two, a paragraph describing what the setting does and
> what its default value and possible other values are is needed; if
> this could be provided, that would be great.

Let's try:

In Debian, most init.d scripts use the logging functions defined in
/lib/lsb/init-functions to provide Policy-compliant status messages.
When FANCYTTY is either unset or set to anything in 1|Y|yes|true, then
the "Fancy output" (with informational blocks such as [ ok ] on the left
of the screen) will be used if the terminal capabilities permit; setting
FANCYTTY to 0 will forcibly disable this "Fancy output".

^ How does that sound?

Cheers,

OdyX



Attachment: signature.asc
Description: OpenPGP digital signature


Reply to: