think it just shows there isn't one right way. I like that every piece of software I configure or write I can go to one of two places -- ~/doc/[apache,ssh,mutt,etc..etc]/.. or ~/src/[c,sh,bash,python,perl]/... -- a structure that can include revisions and updates and follow the flow. It doesn't preclude me from having comments in the conf's, but after all these years in the field of computers like the idea that I can rsync one dir/subtrees and move on to another job or scp it to my home setup and use the info...i love it, guess thats a sign that you like your methodology. Is it best? is there such a thing? best is relative...my 2 cents.
On Thu, Aug 23, 2012 at 5:37 PM, Tim <ignored_mail...@yahoo.com.au> wrote: > On Thu, 2012-08-23 at 14:32 -0700, Joe Zeff wrote: > > I've always been a great believer in putting documentation of this > > type directly into the config file concerned. > > I used to do that until I found that certain things, like Apache, took > an age to start up as they had to parse through huge config file. > > On a 1.x GHz CPU, it's annoyingly noticeable how much longer it takes to > start up with the default config file, versus a stripped down one. > > -- > [tim@localhost ~]$ uname -r > 2.6.27.25-78.2.56.fc9.i686 > > Don't send private replies to my address, the mailbox is ignored. I > read messages from the public lists. > > > > -- > users mailing list > users@lists.fedoraproject.org > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > Have a question? Ask away: http://ask.fedoraproject.org >
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
