From: Felix von Leitner <leitner@convergence.de>
To: linux-kernel@vger.kernel.org
Subject: Re: [reiserfs-list] ReiserFS Oops (2.4.1, deterministic, symlink related)
Date: Sun, 4 Feb 2001 00:26:27 +0100 [thread overview]
Message-ID: <20010204002627.A9527@convergence.de> (raw)
In-Reply-To: <E14OoD8-0007GI-00@the-village.bc.nu> <3A7BC808.E9BF5B44@linux.com> <20010203110053.C1766@werewolf.able.es>
In-Reply-To: <20010203110053.C1766@werewolf.able.es>; from jamagallon@able.es on Sat, Feb 03, 2001 at 11:00:53AM +0100
Thus spake J . A . Magallon (jamagallon@able.es):
> > How about a simple patch to the top level makefile that checks the gcc
> > version then prints a distinct message ..'this compiler hasn't been approved
> > for compiling the kernel', sleeping for one second, then continuing on. This
> > solution doesn't stop compiling and makes a visible indicator without forcing
> > anything.
> Or a config option like CONFIG_TRUSTED_COMPILER, and everyone that wants
> can bracket his code in 'if [ $TRUSTED = "y" ] ... fi', so if some driver-fs
> fails with untrusted compilers it is just not selectable.
What kind of crap is this?
It is not the kernel's job to work around RedHat bugs.
If RedHat ships a broken compiler, it is their responsibility to tell
their customers and provide a working one.
This kind of compatibility crap has caused commercial Unices to
suffocate in their own bloat. We don't need this. And we don't want
this.
Felix
-
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/
next prev parent reply other threads:[~2001-02-03 23:27 UTC|newest]
Thread overview: 38+ 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
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 [this message]
2001-02-04 11:04 ` Alan Cox
2001-02-04 3:24 ` John Alvord
2001-02-02 11:28 Jan Kasprzak
2001-02-02 11:04 ` [reiserfs-list] " Hans Reiser
2001-02-02 12:16 ` Jan Kasprzak
2001-02-02 12:34 ` Alan Cox
2001-02-02 13:09 ` Jan Kasprzak
2001-02-02 16:36 ` Jan Kasprzak
2001-02-02 16:46 ` Alan Cox
2001-02-02 12:15 ` John Morrison
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=20010204002627.A9527@convergence.de \
--to=leitner@convergence.de \
--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