On Monday 08 December 2014 13:31:57 The Wanderer wrote: > On 12/08/2014 at 06:41 AM, Martin Read wrote: > > On 08/12/14 08:44, Curt wrote: > >> On 2014-12-08, Stefan Monnier <monn...@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? > > > > There is *no legitimate basis* for arguing with the OP's complaint. > > The systemd transition has caused a user interface regression, which > > should be fixed. > > > > I like systemd, but I do wish certain of its non-coding proponents > > would stop indulging in incendiary defence of it against legitimate > > complaints. > > Exactly. It's at least as bad as the people who blame systemd for > everything that they see go wrong after the changeover.
I just wish that the subject were able to be rationally discussed, and that people could have problems in Jessie and ask for help without starting a systemd flame war, whether systemd in fact has anything to do with it or not. Anyhow, I've gained something from this thread. I didn't know that I could get rid of fsck by the simple expedient of C^c. Yes, I know that it is obvious, and I can't believe that I didn't even try it, but I clearly didn't. Lisi -- 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/201412081409.19826.lisi.re...@gmail.com
