RE: Skipping fsck during boot with systemd?
>> > fsck may take time. Relax, it needs that time.
>> What if I do not have that time,
> Find it (this includes planning - of infrastructure and procedures if required).
Ok, so that means anyone with a nice laptop who wants to do some work "just before" boarding a plane is now "at risk".
Just had to help someone this morning who had Windows 7 doing updates when he shut down his laptop to board a plane. He had no time to wait, he had not planned on there being an interruption in the "normal baviour". This morning his laptop would not boot.
The same can happen with "normal users" if we give them the new Debian Jessie on a laptop and they run into a similar situation where fsck will start when it "is not a good time to do so". For whatever reason. There needs to be a non corrupting way to something that can last that long.
> No other choices.
In the near future with Jessie, maybe no, but "soon" after that we really need it.
> Let fsck run and pray it does not halts claiming it can't fix the problem.
When it is started due to an unclean shutdown or something like it, we can plan. When it simply runs "because it does that sometimes", no thank you, I would like a cancel option.