From: Helge Hafting <helge.hafting@aitel.hist.no>
To: Hans Reiser <reiser@namesys.com>
Cc: Theodore Ts'o <tytso@mit.edu>,
Kenichi Okuyama <okuyamak@dd.iij4u.or.jp>,
Andreas Dilger <adilger@clusterfs.com>,
fs <fs@ercist.iscas.ac.cn>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
zhiming@admin.iscas.ac.cn, qufuping@ercist.iscas.ac.cn,
madsys@ercist.iscas.ac.cn, xuh@nttdata.com.cn,
koichi@intellilink.co.jp, kuroiwaj@intellilink.co.jp,
okuyama@intellilink.co.jp, matsui_v@valinux.co.jp,
kikuchi_v@valinux.co.jp, fernando@intellilink.co.jp,
kskmori@intellilink.co.jp, takenakak@intellilink.co.jp,
yamaguchi@intellilink.co.jp, ext2-devel@lists.sourceforge.net,
shaggy@austin.ibm.com, xfs-masters@oss.sgi.com,
Reiserfs developers mail-list <Reiserfs-Dev@namesys.com>
Subject: Re: [Ext2-devel] Re: [RFD] FS behavior (I/O failure) in kernel summit
Date: Thu, 16 Jun 2005 13:52:59 +0200 [thread overview]
Message-ID: <42B1681B.6000703@aitel.hist.no> (raw)
In-Reply-To: <42B091E3.3010908@namesys.com>
Hans Reiser wrote:
>What users need is for a window to pop up saying "the usb drive is
>turned off" or "we are getting checksum errors from XXX, this may
>indicate hardware problems that require your attention".
>
>
Nice. And the way to do this right is to have the kernel merely
log the error as usual. The user can have some daemon listening
to the log, this program may then pop up error messages with
nifty detailed explanations, start up diagnostic software
for various subsystems and so on.
The kernel can't do GUI stuff - a GUI may or may not be present,
and the kernel cannot know. The server may not run X at all
but I still run graphical SW on it using a workstation or X-terminal.
Or the pc may have three video cards, each running a different xserver
with different users for each. Who to report to?
An error-reporting daemon have an easier job, it can look up the
correct (possibly remote) display in its config file for all those
cases when there isn't just _one_ display.
Helge Hafting
next prev parent reply other threads:[~2005-06-16 11:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-13 19:53 [RFD] FS behavior (I/O failure) in kernel summit fs
2005-06-13 17:59 ` Hans Reiser
2005-06-13 20:13 ` [Ext2-devel] " Andreas Dilger
2005-06-13 23:56 ` Hans Reiser
2005-06-14 2:46 ` Kenichi Okuyama
2005-06-15 14:01 ` [Ext2-devel] " Theodore Ts'o
2005-06-15 19:40 ` Kenichi Okuyama
2005-06-15 20:37 ` [Ext2-devel] " Theodore Ts'o
2005-06-15 20:38 ` Hans Reiser
2005-06-15 22:53 ` Theodore Ts'o
2005-06-16 19:08 ` [Ext2-devel] " Hans Reiser
2005-06-16 11:52 ` Helge Hafting [this message]
2005-06-16 19:52 ` Hans Reiser
2005-06-16 21:27 ` Pavel Machek
2005-06-16 11:38 ` Matthew Wilcox
2005-06-14 12:51 ` Erik Mouw
2005-06-14 13:48 ` Denis Vlasenko
2005-06-14 17:16 ` Kenichi Okuyama
2005-06-14 20:17 ` Szakacsits Szabolcs
2005-06-14 3:46 ` Valdis.Kletnieks
2005-06-14 17:41 ` [Ext2-devel] " fs
2005-06-13 21:51 ` Jeff Mahoney
2005-06-14 0:03 ` Hans Reiser
2005-06-15 17:39 ` Jeff Mahoney
2005-06-16 2:18 ` Dave Chinner
2005-06-16 15:21 ` Jeff Mahoney
2005-06-16 18:52 ` Hans Reiser
2005-06-14 13:22 ` Dave Kleikamp
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=42B1681B.6000703@aitel.hist.no \
--to=helge.hafting@aitel.hist.no \
--cc=Reiserfs-Dev@namesys.com \
--cc=adilger@clusterfs.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=fernando@intellilink.co.jp \
--cc=fs@ercist.iscas.ac.cn \
--cc=kikuchi_v@valinux.co.jp \
--cc=koichi@intellilink.co.jp \
--cc=kskmori@intellilink.co.jp \
--cc=kuroiwaj@intellilink.co.jp \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=madsys@ercist.iscas.ac.cn \
--cc=matsui_v@valinux.co.jp \
--cc=okuyama@intellilink.co.jp \
--cc=okuyamak@dd.iij4u.or.jp \
--cc=qufuping@ercist.iscas.ac.cn \
--cc=reiser@namesys.com \
--cc=shaggy@austin.ibm.com \
--cc=takenakak@intellilink.co.jp \
--cc=tytso@mit.edu \
--cc=xfs-masters@oss.sgi.com \
--cc=xuh@nttdata.com.cn \
--cc=yamaguchi@intellilink.co.jp \
--cc=zhiming@admin.iscas.ac.cn \
/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;
as well as URLs for NNTP newsgroup(s).