there are good reasons for not having an "all in one" config file. different applications and libraries use different config files, which is as it should be. with the source available, the question of "where do I configure nameserver?" is pretty easily answered. the resources are there, use them.
I would rather get hired for my (lack of) tits than not at all, and then get the chance to prove my own merit. I suppose you are against affirmative action as well.
Slashdot Mirror
there are good reasons for not having an "all in one" config file. different applications and libraries use different config files, which is as it should be. with the source available, the question of "where do I configure nameserver?" is pretty easily answered. the resources are there, use them.
I would rather get hired for my (lack of) tits than not at all, and then get the chance to prove my own merit. I suppose you are against affirmative action as well.