yaubu
July 25th, 2010, 05:16 PM
I just recently installed 10.04 from 9.04. I like it all in all.
*DISCLAIMER* what follows is an utter 'poor me _whine fest_' continue only if you aren't on the edge from constant whining... (I don't do it very often)
I have one issue I'd like to voice about grub2 (grub). I know grub is _not_ ubuntu or Linux.
It seems when very competent developers work on a complicated project for some time, they lose scope of what's intuitive and easy for the user.
I am fairly linux savvy and have used and configured multiple boots regularly.
In terms of grub, it's been fun keeping up with ' grub.conf , menu.lst, or grub.cfg'
I am older and forget things, and rely on linux's legacy of somewhat uniform architecture and configuration structure, and based on 'linux common sense'.
The new grub config, I _do not_ like!
1. if you want to have a dynamic file, why use the one that's in the user's face (grub.cfg), and close to the one we've edited for over a decade?
2. Why bury the user configurable one, outside the boot direcory, into an obscure file called '40_config' (what the hell is that?)
What bugs me, in a month when I got to tweak by grub.cfg it won't stick, then I'll remember this and I'll go look for the file after not finding it, I'll have to search online again, and relive this experience...
A big universal concept of Linux/associated OS systems (I know grub Is Not linux, but has been closely coupled), is keeping the configurations and output and logs human readable, and let the backend infrastructure handle any complexities.
Am I just whining about 'change'?
Am I on the wrong forum?
Does anybody else care?
*DISCLAIMER* what follows is an utter 'poor me _whine fest_' continue only if you aren't on the edge from constant whining... (I don't do it very often)
I have one issue I'd like to voice about grub2 (grub). I know grub is _not_ ubuntu or Linux.
It seems when very competent developers work on a complicated project for some time, they lose scope of what's intuitive and easy for the user.
I am fairly linux savvy and have used and configured multiple boots regularly.
In terms of grub, it's been fun keeping up with ' grub.conf , menu.lst, or grub.cfg'
I am older and forget things, and rely on linux's legacy of somewhat uniform architecture and configuration structure, and based on 'linux common sense'.
The new grub config, I _do not_ like!
1. if you want to have a dynamic file, why use the one that's in the user's face (grub.cfg), and close to the one we've edited for over a decade?
2. Why bury the user configurable one, outside the boot direcory, into an obscure file called '40_config' (what the hell is that?)
What bugs me, in a month when I got to tweak by grub.cfg it won't stick, then I'll remember this and I'll go look for the file after not finding it, I'll have to search online again, and relive this experience...
A big universal concept of Linux/associated OS systems (I know grub Is Not linux, but has been closely coupled), is keeping the configurations and output and logs human readable, and let the backend infrastructure handle any complexities.
Am I just whining about 'change'?
Am I on the wrong forum?
Does anybody else care?