| 1 |
On Thursday, August 27, 2015 9:25:01 PM Michel Catudal wrote: |
| 2 |
> This is nonsense. I have never had a case where it would not boot when I |
| 3 |
have grub correctly installed on the partition. |
| 4 |
|
| 5 |
Install grub to a partition and do something like this: |
| 6 |
|
| 7 |
su |
| 8 |
cd |
| 9 |
mv /boot/grub grub |
| 10 |
cp -r grub /boot |
| 11 |
rm -r grub |
| 12 |
|
| 13 |
At this point your system is broken, but it will still boot. A few days to a |
| 14 |
few years from now your system stops booting, what do YOU do now? You go off |
| 15 |
ranting and name calling the devs. |
| 16 |
|
| 17 |
Now, assume that the developers took your advise and let it install without |
| 18 |
warning, what does a sane person do? I would probably reinstall grub and |
| 19 |
forever wonder wtf went wrong. |
| 20 |
|
| 21 |
Thankfully the developers looked out for me and showed me a warning and forced |
| 22 |
me to pay attention to it by requiring the --force option, so when my system |
| 23 |
breaks I'll remember that and know what went wrong (I'll probably forget but |
| 24 |
at least they tried). |
| 25 |
|
| 26 |
There are other ways to break it, like resizing partitions and I believe this |
| 27 |
is also a problem with grub1. If you modify it to install to a partition |
| 28 |
cleanly without blocklists (which is definitely possible) I doubt that they'll |
| 29 |
reject your changes. Plenty of people are willing to complain but nobody's |
| 30 |
willing to do the work. |
| 31 |
|
| 32 |
-- |
| 33 |
Fernando Rodriguez |
Archives