Re: Skipping fsck during boot with systemd?
On 12/12/2014 12:07 PM, Brian wrote:
> On Fri 12 Dec 2014 at 09:36:33 -0500, Jerry Stuckle wrote:
>> On 12/12/2014 6:02 AM, Gian Uberto Lauri wrote:
>>> Jerry Stuckle writes:
>>> > This means fsck will never run because I don't use
>>> > the laptop outside of those times.
>>> Plan to use it outside of these times as a maintenance call. Or check
>>> the discussion for a nice suggestion to make the "fsck on max mount or
>>> time exceeded" work to do what you want and not what it wants.
>> No, I work enough hours as it is. I have a life outside of Debian.
>> However, the max mount is an interesting idea. I'll look at it - but
>> right now plans are to stick with Wheezy as long as it is supported. If
>> the next version of Debian after Jessie (not sure what the name is)
>> still has systemd, I'll be changing distros.
> The ^C method only postpones the fsck to another time. The issue of when
> to run one remains.
Which is fine. I can run it during the day when I'm not under a
deadline. The problem is only when it runs at an inconvenient time.
(Note: for some reason I didn't receive your last email to me on the
list - don't know why). And I want to thank you for the idea of
changing the max mount. I think that will work for me just fine. Just
set it up to run when I'm going to a meeting or doing something else
when I don't need the system for a few minutes.
At some point I'm probably going to have to go to Jessie. But right now
none of my clients are. They're either staying on Wheezy or looking at
other distros, so I don't really have to go there yet.
Which is going to be a problem for me - until now I've been able to just
stay with the stable version of Debian for development/testing. Now I'm
going to have to keep up with other versions, also. Maybe it's a good
time to raise my rates :)