From: Oleg Drokin <green@namesys.com>
To: Ookhoi <ookhoi@humilis.net>
Cc: Hans Reiser <reiser@namesys.com>, Niek <Art@chello.nl>,
reiserfs-list@namesys.com, Vitaly Fertman <vitaly@namesys.com>,
mason <mason@namesys.com>
Subject: Re: Hard disk crash and solution
Date: Thu, 23 Jan 2003 09:52:01 +0300 [thread overview]
Message-ID: <20030123095201.A12043@namesys.com> (raw)
In-Reply-To: <20030123074357.A2442@humilis>
Hello!
On Thu, Jan 23, 2003 at 07:43:57AM +0100, Ookhoi wrote:
> > I think we should have fsck ask the user to check and see if they are
> > using the latest fsck.
> > "You really want to be using the very latest stable version of fsck
> > when you run it. Please go to www.namesys.com, click on the download
> > button, and see if you have the latest version before you continue."
> If XFree86 crashes, it says something like,
> "This is release foo, date bar. If it is more than six months old, or if
> your video card is newer than this release, please see if a newer
> release fixes it before you report a bug"
I think it does already. Along with suggesting on where to send bugreports
if this is the latest release.
> Maybe fsck should say the same. It could very well be that you don't
> have access to the internet when you have to perform a fsck :-) And
> then you still would like to know how old your tools are. If you release
> new tools at least every two months, you can say two months. You can
> also point to the -pre releases (with the usual warning).
main.c: ** If you are using the latest reiserfsprogs and it fails **\n\
main.c- ** please email bug reports to reiserfs-list@namesys.com, **\n\
main.c- ** providing as much information as possible -- your **\n\
Though this warning is printed at the beginning.
Bye,
Oleg
next prev parent reply other threads:[~2003-01-23 6:52 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-22 21:35 Hard disk crash and solution Niek
2003-01-22 21:57 ` Hans Reiser
2003-01-23 6:43 ` Ookhoi
2003-01-23 6:52 ` Oleg Drokin [this message]
2003-01-23 7:00 ` Ookhoi
2003-01-22 22:01 ` Dieter Nützel
2003-01-22 22:02 ` Hans Reiser
2003-01-23 0:16 ` Rudy L. Zijlstra
2003-01-23 6:47 ` Ookhoi
2003-01-23 8:02 ` Rudy L. Zijlstra
2003-01-23 13:14 ` Dieter Nützel
2003-01-23 7:45 ` Todd Lyons
2003-01-23 9:40 ` Hans Reiser
2003-01-26 19:42 ` Zygo Blaxell
2003-01-27 4:53 ` Ookhoi
2003-01-27 7:03 ` Oleg Drokin
2003-01-27 23:34 ` Zygo Blaxell
2003-02-02 21:11 ` tim fairchild
2003-02-03 4:49 ` Ookhoi
2003-02-04 1:31 ` tim fairchild
2003-02-04 3:05 ` Manuel Krause
2003-02-04 3:08 ` Todd Lyons
2003-01-29 11:24 ` Hans Reiser
2003-02-06 3:04 ` Zygo Blaxell
2003-02-06 9:56 ` Hans Reiser
2003-02-06 10:21 ` Oleg Drokin
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=20030123095201.A12043@namesys.com \
--to=green@namesys.com \
--cc=Art@chello.nl \
--cc=mason@namesys.com \
--cc=ookhoi@humilis.net \
--cc=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=vitaly@namesys.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.