Hi Brian, >> Brian <a...@cityscape.co.uk> wrote: >> >> > But remember our current slogan "Linux is all about choice". One can >> > choose to boot with or without "fsck.mode=skip". >> >> What about the choice to stop fsck it if it has started at an inconvenient >> moment ? > > Remedial action is not needed because the right choice was made from the grub > menu. If it wasn't, you get to live with the consequences and don't do it > again.
I guess you never were in a hurry to get a system up and running again during production hours where a fschk takes a looong time. As normally a reboot takes place at night and I DO want a fschk to be performed at that time if needed this is the default boot option. So in your opinion everyone with a production system needs a third grub line apart from the 2 default lines. If that many people NEED it then why is it not a default 3rd line in all installations? Also, just about "never" will that fschk start when I do a manual reboot so why would I remember to choose option 3 at the reboot. Also... a server nowadays takes minutes for the hardware check to complete a reboot, after that I have only 5 seconds to select the proper boot option in your scenario. Or do you want me to lengthen ALL reboots by lengthening the Grub boot screen? All of this was never necessary as we could cancel an unneeded fschk that was merely performed because a certain number of days had passed. That was the proper way, to take action when it is needed. Not to allways take action in preemptive way in a short (seconds) windows when it is almost never needed. I hope this clarifies things a bit, I hope we get the option back to stop a scheduled fschk that is performed at an inconvenient moment. Met vriendelijke groet, Bonno Bloksma -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/89d1798a7351d040b4e74e0a043c69d7a83c9...@einexch-01.tio.nl
