public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jos Hulzink <josh@stack.nl>
To: linux-kernel@vger.kernel.org
Subject: 2.7 (future kernel) wish
Date: Tue, 23 Dec 2003 23:42:17 +0100	[thread overview]
Message-ID: <200312232342.17532.josh@stack.nl> (raw)

Hi,

First of all... Compliments about 2.6.0. It is a superb kernel, with very few 
serious bugs, and for me it runs stable like a rock from the very first 
moment.

As an end user, Linux doesn't give me a good feeling on one particular item 
yet: Error handling. 

What do I mean ? Well... for example: Pull out your USB stick with a mounted 
fs on it. Linux doesn't really seem to like it, got weird problems etc. It 
will survive, sure, but the user got no clue and data are lost for sure. Bad 
sectors on a disk... Linux will pass, but even 2.6.0 went very slow, 
unresponsive when a floppy with bad sectors went into the drive. Many other 
non-critical or solvable problems that are dealt with in a way that makes 
linux survive (most of the times), but not in a way that is neat from the 
user point of view.

It all just doesn't feel like Linux is doing the best it can to "rescue the 
user" when something is going wrong. Technically speaking, it's not only the 
task of the kernel to do so, but for an end user it makes the difference 
between an OS that does its job, and an OS that does its job nicely.

I think it's hard to describe what I mean exactly, but I hope you get the 
feeling. I too know that some of this is not within scope of the kernel (it's 
not the kernels task to tell the user "put back the USB drive or data is 
lost"), but after dealing with broken floppies again, I thought it was time 
to write my feelings to the list.

Best regards, and thanks for the wonderful world of Linux,

Jos


             reply	other threads:[~2003-12-23 22:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-23 22:42 Jos Hulzink [this message]
2003-12-26 23:38 ` 2.7 (future kernel) wish Helge Hafting
2003-12-26 23:57   ` David B. Stevens
2003-12-27  6:51     ` Joshua Schmidlkofer
2003-12-28  3:03       ` Jim Crilly
2003-12-28  3:08         ` Kevin P. Fleming
2003-12-28  3:13           ` Rob Love
2003-12-28 11:17           ` Kevin Krieser
2003-12-28 11:23             ` Gaël Le Mignot
2003-12-28  3:11         ` Rob Love
2003-12-28  3:19           ` Jim Crilly
2004-01-04 21:05             ` Pat Erley
2003-12-28  3:57         ` Joshua Schmidlkofer
2003-12-28  4:33         ` Elladan
2003-12-30 14:20         ` Helge Hafting
2003-12-31  0:18           ` Jim Crilly
  -- strict thread matches above, loose matches on Subject: below --
2003-12-30 15:41 Pacheco Jason NPRI
2003-12-30 16:18 ` mjt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200312232342.17532.josh@stack.nl \
    --to=josh@stack.nl \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox