public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Albert D. Cahalan" <acahalan@cs.uml.edu>,
	Brian Wolfe <ahzz@terrabox.com>,
	Ion Badulescu <ionut@moisil.cs.columbia.edu>,
	linux-kernel@vger.kernel.org, reiserfs-list@namesys.com,
	Jan Kasprzak <kas@informatics.muni.cz>
Subject: Re: [reiserfs-list] ReiserFS Oops (2.4.1, deterministic, symlink
Date: Mon, 05 Feb 2001 15:33:20 +0300	[thread overview]
Message-ID: <3A7E9D90.3E694A7A@namesys.com> (raw)
In-Reply-To: <E14Pl8Z-0003Hj-00@the-village.bc.nu>

Alan Cox wrote:
> 
> > > I was thinking boot time.
> > and if reiserfs is the root partition?  You really want to make them reboot to
> > the old kernel and recompile rather than making them just recompile?
> 
> I want to make sure they get a sane clear message telling them where to
> find the correct compiler and that they didnt read the docs
> 
> > Stop trying to blame something other than the compiler, it is ridiculous.
> 
> WTF does it have to dow with blaming something other than the compiler ?
> 
> Its going to print something like
> 
> Linux 2.4.2-ac3 blah blah
> Error: This kernel was built with a buggy gcc. Please go to
>         http://.... and upgrade

Sorry, thought you were going to make it only reiserfs disabling, ok, if we do
both this and make the compile fail, that is pretty thorough, effective, useful,
etc.

Hans
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-02-05 13:05 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cs.lists.linux-kernel/E14OjME-0006nU-00@the-village.bc.nu>
2001-02-02 21:22 ` [reiserfs-list] ReiserFS Oops (2.4.1, deterministic, symlink related) Ion Badulescu
2001-02-02 21:57   ` Alan Cox
2001-02-02 22:06     ` Arthur Erhardt
2001-02-02 22:06     ` Hans Reiser
2001-02-02 22:57       ` Ion Badulescu
2001-02-05  2:50       ` Brian Wolfe
2001-02-05  4:08         ` Albert D. Cahalan
2001-02-05 11:58           ` Alan Cox
2001-02-05 11:36             ` Hans Reiser
2001-02-05 12:44               ` [reiserfs-list] ReiserFS Oops (2.4.1, deterministic, symlink Alan Cox
2001-02-05 12:16                 ` Hans Reiser
2001-02-05 12:52                   ` Alan Cox
2001-02-05 12:33                     ` Hans Reiser [this message]
2001-02-05 12:57                   ` Dr. David Gilbert
2001-02-05 16:57               ` [reiserfs-list] ReiserFS Oops (2.4.1, deterministic, symlink related) James Sutherland
2001-02-12  3:41               ` [reiserfs-list] ReiserFS Oops (2.4.1, deterministic, symlink Albert D. Cahalan
2001-02-12  9:45                 ` Hans Reiser
2001-02-05 12:16             ` [reiserfs-list] ReiserFS Oops (2.4.1, deterministic, symlink related) Dr. David Gilbert
2001-02-05  5:21         ` Gregory Maxwell
2001-02-05 12:02           ` Alan Cox
2001-02-05 11:38             ` Hans Reiser
2001-02-05 11:55         ` Alan Cox
2001-02-05 11:35           ` Hans Reiser
2001-02-05 20:19           ` Brian Wolfe
2001-02-02 22:42     ` Ion Badulescu
2001-02-03  3:43       ` Johan Kullstam
2001-02-03  8:57     ` [reiserfs-list] " David Ford
2001-02-03 10:00       ` J . A . Magallon
2001-02-03 23:26         ` Felix von Leitner
2001-02-04 11:04           ` Alan Cox
2001-02-04  3:24       ` John Alvord
2001-02-02 11:04 Hans Reiser
2001-02-02 12:26 ` [reiserfs-list] ReiserFS Oops (2.4.1, deterministic, symlink Alan Cox

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=3A7E9D90.3E694A7A@namesys.com \
    --to=reiser@namesys.com \
    --cc=acahalan@cs.uml.edu \
    --cc=ahzz@terrabox.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=ionut@moisil.cs.columbia.edu \
    --cc=kas@informatics.muni.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiserfs-list@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox