Linked by Thom Holwerda on Wed 21st Apr 2010 23:01 UTC
Thread beginning with comment 420421
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 06/13/13 14:35 UTC
Linked by Thom Holwerda on 06/11/13 17:07 UTC
Linked by Thom Holwerda on 06/10/13 23:13 UTC
Linked by Thom Holwerda on 06/08/13 14:57 UTC
Linked by Thom Holwerda on 06/07/13 11:40 UTC
Linked by Thom Holwerda on 06/04/13 12:45 UTC
Linked by nfeske on 05/31/13 10:12 UTC
Linked by Thom Holwerda on 05/29/13 16:59 UTC
Linked by Thom Holwerda on 05/24/13 17:26 UTC
Linked by Thom Holwerda on 05/21/13 21:38 UTC
More Features »
Sponsored Links



Member since:
2008-07-15
Simple answer: automation. Most Linux systems these days focus on automation and scripting with GUI frontends. Separate files are much easier to deal with in automation and scripting tasks at least if done well.
That being said, there's a place for this and I don't believe the entire grub configuration is the best place for it. I could see splitting out each section, i.e. default config parameters and then each os entry being separate files, but the way they do it now is just overkill especially when it flies apart as it too often does.