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

"Didier 'OdyX' Raboud" <[email protected]>
Newsgroups gmane.linux.debian.devel.lsb
Organization Debian, the Universal OS
Message-ID <4FBA40D5.6040702__13410.0100993694$1337606500$gmane$org@debian.org>
tags 673207 +pending
thanks

Le 21.05.2012 14:07, Didier 'OdyX' Raboud a écrit :
> 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.

Based on that idea, I have implemented a sourcing of /etc/default/rcS
for FANCYTTY that keeps the rest of the environment untouched (as
proposed by Stanislav):

http://anonscm.debian.org/gitweb/?p=users/odyx-guest/lsb.git;a=commit;h=ce9dcce

The reason to not alter the environment is that /lib/lsb/init-functions
is sourced by all sorts of init scripts and I don't want to risk
uncontrolled breakage.

So this bug is now "pending". Roger: do you need more input from my side
to allow FANCYTTY in /etc/default/rcS in initscripts ?

Cheers,

OdyX
signature.asc (application/pgp-signature, 663 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)

iQGcBAEBAgAGBQJPukDVAAoJEIvPpx7KFjRVK14L/2I/qd72mtB8vtxylwCjxQ49
d+DJGR5a/BEE1PitwxGSGCCSvSlTGUhhfTCHwHg4w1DyRN4HCCEv3lIK99qkv6vw
7nAd6GtlMvfpg6sPsIvWGCcPiGnRzpffsFpWVsSt6EJPdS71YOXJn1XjKPWwZ91b
fzlpPr2SsP/3o0/A5/jkVg19HFDOhTenr9k7nA9PZZT4zAcoK4STCpC00ZgQnKF+
4ifdsILTZxoINLGAX08N0ckcBj7u9VDelw+WwkM11i6nmfN6bpxVOjagUIUgLI0B
mUFX49d3kpd9YNBO1DA6F4GyfrpVSAwaQ5QvNNRfS963egeLAO8CJGhqWDjdex/E
WWVCqZ2GQaJ5ocdn+ZFD+AXjEY3oN3fgdQ82M3XISRsEtmd9GdwrCnNLVEz4wwIf
na7e30pIha+7bJM0HGvscgtjXagXrZfKV3n4upeDfGGeEiRixPRSV/Mv6AOA9CFb
QaU+f27dHhx1P55DzzU5qnJYIgkRM73937cmlUvJkg==
=AiB0
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.