[arch-dev-public] rc.conf cleanup why?

Tom Gundersen teg at jklm.no
Thu Jul 19 05:56:29 EDT 2012

I should add: the reason I prefer manages rather than comments is that they
can be more verbose and updated more frequently.
On Jul 19, 2012 11:55 AM, "Tom Gundersen" <teg at jklm.no> wrote:

> Tobias,
> I'd like to nudge people into thinking twice before using these options.
> In addition to documenting what options exist, the man page also explains
> why you should not use them.
> As of the next release initscripts will do the right thing when rc.conf is
> empty.
> I also started adding warnings whenever people have
> contradictory/nonsensical options specified (usually solved by deleting the
> options).
> Tom
> On Jul 19, 2012 7:58 AM, "Tobias Powalowski" <
> tobias.powalowski at googlemail.com> wrote:
>> Hi
>> http://projects.archlinux.org/initscripts.git/commit/?id=5b062674869c97018871b1f91c0b22d27ae900f7
>> I don't think this is a good idea, I liked the described options in
>> rc.conf. Now you have to switch to an other terminal to read what
>> options are possible.
>> pacman.conf and makepackage.conf also have comments on important
>> options, so why remove parameters from the most important config file?
>> greetings
>> tpowa

More information about the arch-dev-public mailing list