4 ms·
This answer totally sucks, I agree. And I have run into this annoyance myself (I've been using systemd for almost three years). But just so everyone knows, and
by chimeracoder 12y ago
This answer totally sucks, I agree. And I have run into this annoyance myself (I've been using systemd for almost three years).
But just so everyone knows, and so nobody finds themselves in this position, there is an easier way. By default, I believe systemd will skip the fsck if running on battery power (this is the case on Arch, at least). So if you know you are in a hurry but haven't added this to your GRUB config, the easiest thing to do is just boot the laptop and wait about ten seconds before plugging in the power cord (the fsck check happens early enough, so it'll have been skipped by that point). This doesn't help kill it if it's already in progress, but it has saved me many times.
Brian's response is laughably rude and unhelpful, but hopefully this will be a bit easier and more helpful than telling people to edit their GRUB config before-the-fact.
- fsniper 12y agoWell, this answer is a workaround. And I'm sorry it's a ridiculous one. What if I'm not on a laptop? What if this is a server system?
- chimeracoder 12y ago> this answer is a workaround. And I'm sorry it's a ridiculous one. If you're trying to have an argument, you've picked the wrong person. I'm not defending Brian; I'm simply pointing out a relevant trick that I thought people reading this thread may find helpful.
- fsniper 12y agoYou make it clear that you are not backing Brian. I'm just trying to tell the shortcomings of your trick. Also in this case it also involves back in time travel or being prepared. If you want to be prepared tune2fs would be a better choice.
- mst 12y agoIt was incredibly obvious that he already understands those are shortcomings. You're just stating the obvious in a condescending fashion. Reddit is over there.