On Monday 08 December 2014 19:00:36 Brian wrote:
On Mon 08 Dec 2014 at 17:14:58 +, Lisi Reisz wrote:
On Monday 08 December 2014 16:25:51 Brian wrote:
On Mon 08 Dec 2014 at 09:40:03 -0500, The Wanderer wrote:
Several people in this thread (including, I think, you?) are
responding
2014/12/08 20:24 Brian a...@cityscape.co.uk:
On Mon 08 Dec 2014 at 10:12:55 +0100, Christian Groessler wrote:
On 12/08/14 09: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,
On 08/12/2014 22:00, Brian wrote:
On Mon 08 Dec 2014 at 17:14:58 +, Lisi Reisz wrote:
On Monday 08 December 2014 16:25:51 Brian wrote:
On Mon 08 Dec 2014 at 09:40:03 -0500, The Wanderer wrote:
Several people in this thread (including, I think, you?) are responding
to those complaints by
On 2014-12-07, seeker5528 seeker5...@comcast.net wrote:
On 12/6/2014 5:58 AM, Mart van de Wege wrote:
Well, it is not as if fscks happen out of the blue. Either you weren't
paying attention and you were hit with the periodic fsck, or you make
a habit of doing dirty shutdowns, and you know
seeker5528 seeker5...@comcast.net writes:
On 12/6/2014 5:58 AM, Mart van de Wege wrote:
Well, it is not as if fscks happen out of the blue. Either you
weren't paying attention and you were hit with the periodic fsck, or
you make a habit of doing dirty shutdowns, and you know the fsck is
On 12/07/2014 at 06:37 PM, Mart van de Wege wrote:
seeker5528 seeker5...@comcast.net writes:
On 12/6/2014 5:58 AM, Mart van de Wege wrote:
Well, it is not as if fscks happen out of the blue. Either you
weren't paying attention and you were hit with the periodic fsck,
or you make a habit
Look, if you reboot a laptop instead of suspending/hibernating it,
sooner or later you're going to have to think Hmm, it hasn't fscked for
a while. It shouldn't be a surprise when it does.
Actually, it's *always* a surprise. These fsck happen at long enough
intervals, that I can never know
On 12/07/2014 at 06:37 PM, Mart van de Wege wrote:
Look, if you reboot a laptop instead of suspending/hibernating it,
sooner or later you're going to have to think Hmm, it hasn't fscked
for a while. It shouldn't be a surprise when it does.
That brings up a whole different question about
On Sat 06 Dec 2014 at 06:42:50 +, Lisi Reisz wrote:
On Friday 05 December 2014 23:16:47 Brian wrote:
On Fri 05 Dec 2014 at 19:06:50 -0300, Renaud OLGIATI wrote:
On Fri, 5 Dec 2014 20:59:25 +
Brian a...@cityscape.co.uk wrote:
But remember our current slogan Linux is all
On Saturday 06 December 2014 09:44:38 Brian wrote:
On Sat 06 Dec 2014 at 06:42:50 +, Lisi Reisz wrote:
On Friday 05 December 2014 23:16:47 Brian wrote:
On Fri 05 Dec 2014 at 19:06:50 -0300, Renaud OLGIATI wrote:
On Fri, 5 Dec 2014 20:59:25 +
Brian a...@cityscape.co.uk
On 2014-12-06, Jarle Aase j...@jgaa.com wrote:
This is exactly the kind of arrogance that have made Windows 8 a total
disaster for Microsoft. I once convinced Windows 8 to stop a forced,
non-interruptible upgrade, by slamming the laptop in the table until the
hard-disk died.
This is a clear
On Sat 06 Dec 2014 at 10:10:05 +, Lisi Reisz wrote:
On Saturday 06 December 2014 09:44:38 Brian wrote:
On Sat 06 Dec 2014 at 06:42:50 +, Lisi Reisz wrote:
On Friday 05 December 2014 23:16:47 Brian wrote:
On Fri 05 Dec 2014 at 19:06:50 -0300, Renaud OLGIATI wrote:
On Fri, 5
(Quoting reordered slightly to make more what-replies-to-what sense.)
On 12/06/2014 at 06:27 AM, Brian wrote:
On Sat 06 Dec 2014 at 10:10:05 +, Lisi Reisz wrote:
On Saturday 06 December 2014 09:44:38 Brian wrote:
His lateness and the scheduled fsck do not appear to be
correlated. A
On 12/06/2014 at 12:27 AM, Ric Moore wrote:
On 12/05/2014 05:06 PM, Renaud (Ron) OLGIATI wrote:
On Fri, 5 Dec 2014 20:59:25 + Brian a...@cityscape.co.uk
wrote:
But remember our current slogan Linux is all about choice. One
can choose to boot with or without fsck.mode=skip.
What
On Sat, 6 Dec 2014 11:27:24 +
Brian a...@cityscape.co.uk wrote:
A third suggestion is to use grub's scripting to present the user with
a choice of a fsck or not.
Another thing to consider: lets say that the system runs fsck once every 50
reboots (figure grabbed out of thin air), and that
The Wanderer wande...@fastmail.fm writes:
On 12/06/2014 at 12:27 AM, Ric Moore wrote:
On 12/05/2014 05:06 PM, Renaud (Ron) OLGIATI wrote:
On Fri, 5 Dec 2014 20:59:25 + Brian a...@cityscape.co.uk
wrote:
But remember our current slogan Linux is all about choice. One
can choose to
Le 06/12/2014 06:27, Ric Moore a écrit :
On 12/05/2014 05:06 PM, Renaud (Ron) OLGIATI wrote:
On Fri, 5 Dec 2014 20:59:25 +
Brian a...@cityscape.co.uk wrote:
But remember our current slogan Linux is all about choice. One can
choose to boot with or without fsck.mode=skip.
What about the
On 12/06/2014 02:21 PM, Erwan David wrote:
Le 06/12/2014 06:27, Ric Moore a écrit :
On 12/05/2014 05:06 PM, Renaud (Ron) OLGIATI wrote:
On Fri, 5 Dec 2014 20:59:25 +
Brian a...@cityscape.co.uk wrote:
But remember our current slogan Linux is all about choice. One can
choose to boot with
On Sat 06 Dec 2014 at 07:21:30 -0500, The Wanderer wrote:
(Quoting reordered slightly to make more what-replies-to-what sense.)
On 12/06/2014 at 06:27 AM, Brian wrote:
On Sat 06 Dec 2014 at 10:10:05 +, Lisi Reisz wrote:
On Saturday 06 December 2014 09:44:38 Brian wrote:
His
On 12/6/2014 5:58 AM, Mart van de Wege wrote:
Well, it is not as if fscks happen out of the blue. Either you weren't
paying attention and you were hit with the periodic fsck, or you make
a habit of doing dirty shutdowns, and you know the fsck is going to
happen anyway.
Assuming your
With init, skipping a scheduled fsck during boot was easy, you just pressed
Ctrl+c, it was obvious! Today I was late for an online conference. I got
home, turned on my computer, and systemd decided it was time to run fsck on my
1TB hard drive. Ok, I just skip it, right? Well, Ctrl+c does not work,
On Fri 05 Dec 2014 at 09:04:14 -0800, Eduardo Nogueira wrote:
With init, skipping a scheduled fsck during boot was easy, you just pressed
Ctrl+c, it was obvious! Today I was late for an online conference. I got
home, turned on my computer, and systemd decided it was time to run fsck on my
1TB
On 12/05/2014 at 01:05 PM, Brian wrote:
On Fri 05 Dec 2014 at 09:04:14 -0800, Eduardo Nogueira wrote:
With init, skipping a scheduled fsck during boot was easy, you just
pressed Ctrl+c, it was obvious! Today I was late for an online
conference. I got home, turned on my computer, and systemd
With init, skipping a scheduled fsck during boot was easy, you just
pressed Ctrl+c, it was obvious! Today I was late for an online
conference. I got home, turned on my computer, and systemd decided
it was time to run fsck on my 1TB hard drive. Ok, I just skip it,
right? Well, Ctrl+c does
On 12/05/2014 07:43 PM, The Wanderer wrote:
On 12/05/2014 at 01:05 PM, Brian wrote:
On Fri 05 Dec 2014 at 09:04:14 -0800, Eduardo Nogueira wrote:
With init, skipping a scheduled fsck during boot was easy, you just
pressed Ctrl+c, it was obvious! Today I was late for an online
conference. I
On Fri 05 Dec 2014 at 14:00:40 -0500, Stefan Monnier wrote:
With init, skipping a scheduled fsck during boot was easy, you just
pressed Ctrl+c, it was obvious! Today I was late for an online
conference. I got home, turned on my computer, and systemd decided
it was time to run fsck on my
On Fri 05 Dec 2014 at 13:43:32 -0500, The Wanderer wrote:
On 12/05/2014 at 01:05 PM, Brian wrote:
On Fri 05 Dec 2014 at 09:04:14 -0800, Eduardo Nogueira wrote:
With init, skipping a scheduled fsck during boot was easy, you just
pressed Ctrl+c, it was obvious! Today I was late for an
On Fri, 5 Dec 2014 20:59:25 +
Brian a...@cityscape.co.uk wrote:
But remember our current slogan Linux is all about choice. One can
choose to boot with or without fsck.mode=skip.
What about the choice to stop fsck it if it has started at an inconvenient
moment ?
Cheers,
Ron.
--
On Fri 05 Dec 2014 at 19:06:50 -0300, Renaud OLGIATI wrote:
On Fri, 5 Dec 2014 20:59:25 +
Brian a...@cityscape.co.uk wrote:
But remember our current slogan Linux is all about choice. One can
choose to boot with or without fsck.mode=skip.
What about the choice to stop fsck it if it
On 12/05/2014 05:06 PM, Renaud (Ron) OLGIATI wrote:
On Fri, 5 Dec 2014 20:59:25 +
Brian a...@cityscape.co.uk wrote:
But remember our current slogan Linux is all about choice. One can
choose to boot with or without fsck.mode=skip.
What about the choice to stop fsck it if it has started at
On Friday 05 December 2014 23:16:47 Brian wrote:
On Fri 05 Dec 2014 at 19:06:50 -0300, Renaud OLGIATI wrote:
On Fri, 5 Dec 2014 20:59:25 +
Brian a...@cityscape.co.uk wrote:
But remember our current slogan Linux is all about choice. One can
choose to boot with or without
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/06/2014 01:16 AM, Brian wrote:
On Fri 05 Dec 2014 at 19:06:50 -0300, Renaud OLGIATI wrote:
On Fri, 5 Dec 2014 20:59:25 +
Brian a...@cityscape.co.uk wrote:
But remember our current slogan Linux is all about choice. One can
choose to
201 - 232 of 232 matches
Mail list logo
