On 12/08/2014 06:41 AM, Christian Groessler wrote:
On 12/08/14 12:04, Mart van de Wege wrote:Christian Groessler <chris@groessler.org> writes:On 12/08/14 09:44, Curt wrote:On 2014-12-08, Stefan Monnier <monnier@iro.umontreal.ca> wrote:Actually, it's *always* a surprise. These fsck happen at long enough intervals, that I can never know if it was "4 months ago" or "7 months ago", and neither can I remember which laptop/desktop has the delay set to 172 days vs 194 days vs 98 days vs ...Can't you write a small script to obviate the limitations of your human memory, like this little hacker here did? http://nwalsh.com/hacks/mountinfo/ http://nwalsh.com/hacks/mountinfo/mountinfoWhy don't the systemd proponents understand that someone might want to interrupt a running fsck? Don't scrutinize the reasons, just accept the fact.I understand it just fine. I just don't understand why this is a big deal, as it could have been easily avoided. This is a case of "Doctor, it hurts when I do this". "Well, don't do that then".What shouldn't I do? Boot my system?
use a journaling file system like ext4 ?? Of course that would require a major backup and restore, but that would get you the closest to where you want to be. How big is that harddrive any way?? It must be a monster drive for fsck to be an major issue. like for this guy:
http://grokbase.com/t/centos/centos/119dg0by5y/how-to-stop-an-in-progress-fsck-that-runs-at-boot...it is suggested there to use tune2fs (man tune2fs) before you shut down to go do your public display and reset the fsck counter. So, you can be in charge of your computer if you do it the way it likes you to be in charge. I've been married 3 1/2 times and I can tell you from my vast experience that a computer is little different from an ex-wife. :) Ric
-- My father, Victor Moore (Vic) used to say: "There are two Great Sins in the world... ..the Sin of Ignorance, and the Sin of Stupidity. Only the former may be overcome." R.I.P. Dad. Linux user# 44256