From: Xavier Bestel <xavier.bestel@free.fr>
To: venom@sns.it
Cc: louie miranda <louie@chikka.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Hi is this critical??
Date: 16 Sep 2002 15:47:20 +0200 [thread overview]
Message-ID: <1032184041.7199.14.camel@bip> (raw)
In-Reply-To: <Pine.LNX.4.43.0209161537200.5180-100000@cibs9.sns.it>
Le lun 16/09/2002 à 15:37, venom@sns.it a écrit :
>
> yes, this is critical.
> It means that your HD is going to break soon.
>
Maybe these error messages should be a bit less cryptic for the
uninitiated. Or is there a userspace utility to convert theses to
luser-understandable messages ?
next prev parent reply other threads:[~2002-09-16 13:42 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-16 20:05 2.4.19 - not a real problem raptor
2002-09-16 13:31 ` Hi is this critical?? louie miranda
2002-09-16 13:34 ` DevilKin
2002-09-16 13:37 ` venom
2002-09-16 13:47 ` Xavier Bestel [this message]
2002-09-16 14:16 ` Mark Veltzer
2002-09-16 14:14 ` Xavier Bestel
2002-09-16 15:57 ` venom
2002-09-16 23:23 ` Nuitari
2002-09-16 18:27 ` jbradford
2002-09-16 22:46 ` venom
2002-09-17 5:18 ` Nuitari
2002-09-17 8:02 ` jbradford
2002-09-17 8:20 ` Andre Hedrick
2002-09-17 10:41 ` Alan Cox
2002-09-17 11:09 ` Russell King
2002-09-17 11:17 ` Alan Cox
2002-09-17 12:02 ` Russell King
2002-09-17 12:17 ` jbradford
2002-09-17 12:02 ` jbradford
2002-09-17 18:39 ` Bill Davidsen
2002-09-18 6:00 ` Daniel Berlin
2002-09-17 17:34 ` Andre Hedrick
2002-09-17 17:54 ` Russell King
2002-09-17 19:30 ` jbradford
2002-09-17 18:34 ` Bill Davidsen
2002-09-18 5:56 ` Daniel Berlin
2002-09-17 18:23 ` Bill Davidsen
2002-09-16 14:43 ` Russell King
2002-09-17 8:40 ` Rogier Wolff
2002-09-17 9:03 ` jbradford
2002-09-16 14:53 ` Alan Cox
2002-10-05 12:58 ` 2.4.19 - not a real problem Adrian Bunk
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=1032184041.7199.14.camel@bip \
--to=xavier.bestel@free.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=louie@chikka.com \
--cc=venom@sns.it \
/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).