Linked by Thom Holwerda on Wed 21st Apr 2010 23:01 UTC
Permalink for comment 420368
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
Linked by Thom Holwerda on 04/16/13 9:29 UTC
More Features »
Sponsored Links



Member since:
2005-07-11
Some things, it makes sense to split into separate files. Like Apache virtual hosts. But does everything else under /etc/apache2 have to be in separate files? Really?
Same with all the apt.sources.d directories. Is it really easier to manage all those files, then just firing up a text editor and adding/removing a simple # in the first column?
What's even worse, though, is when using separate config files actually breaks features ... like the mess that is logrotate (at least in Debian/Ubuntu). /etc/logrotate.conf is supposed to be the global config file that all the other files under /etc/logrotate.d/ pick up ... yet it doesn't actually work that way, and you still have to duplicate all your monthly/compress options in all the files. Which means you now have to edit dozens of files to change the rotation policy ... instead of just one.
There's a time and a place to separate config files and use includes. Grub configuration is not one of them.