Follow-up Comment #4, bug #40530 (project grub):
1. How likely is a hibernated file system, which is not on the default boot
partition, on an unattended-starting server?
2. The virgin first start of an unattended system would be for sure
non-unattended, and the operator would become aware of the rarely-occurring
situation, so then could remedy the cause or set the option.
3. If you still think, I'm wrong, then here 2 other suggestions for the
problematic case:
- Interrupt the boot with a loooong time-out, e.g. 3 minutes, which only could
be decreased optionally, so standard user has enough time to prevent the
system from dangerously booting the wrong partition.
- If I can't convince you, then please introduce a non-default option for
hibernation-detection at least.
To me:
Negligently corrupting a file system and destroying data is "not an option".
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?40530>
_______________________________________________
Nachricht gesendet von/durch Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-grub mailing list
Bug-grub@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-grub
