public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: J Sloan <jjs@lexus.com>
To: "T. A." <tkhoadfdsaf@hotmail.com>,
	Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: [OT] Re: Which kernel (Linus or ac)?
Date: Fri, 12 Oct 2001 10:35:30 -0700	[thread overview]
Message-ID: <3BC729E2.E93A416E@lexus.com> (raw)
In-Reply-To: <XFMail.20011011094548.jkp@riker.nailed.org> <3BC5E152.3D81631@bigfoot.com> <3BC5E3AF.588D0A55@lexus.com> <3BC5EB56.21B4EF88@bigfoot.com> <3BC5FA12.F8E5C91E@lexus.com> <OE64cxtniFKULPEhGD100007fff@hotmail.com> <3BC688A2.4C7640B7@pobox.com> <OE394qrvAsp4XgWZGbR0000e29d@hotmail.com>

After this post we should take it offline and
let the s/n ratio on lkml settle back down to
a dull roar - apologies for the noise, this is
the last post on this dead horse.

"T. A." wrote:

>     Oh I could deal with all of the problems as well.  But after a good bit
> of recompiling, patching, upgrading, backtracking the things done in the
> "Redhat" way

You may have a point with 7.0, but 7.1 was not
that bad - and in any case, just applying the RH
updates fixed the problems.

> which many times don't match the man pages, as well as undoing
> the "Redhat" way annoyances I just end up with a variation of my own hand
> built distribution.

To each his own - choice is a wonderful thing, isn't it?

> And once I have to replace the system experimental C
> library and compiler it just get even more ridicules.

Experimental? What you call experimental, I call (and
my customers call) fully functional and fully supported.

Using gcc-2.96 on the 40+ RH boxes I have scattered
around the southwest has shown no problems, despite
all the outrage from anti gcc-2.96 activists.

Here is a heads-up for the benefit of those wondering
about gcc-2.96:

http://www.bero.org/gcc296.html

cu

jjs


  parent reply	other threads:[~2001-10-12 17:37 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-11 14:45 Which kernel (Linus or ac)? jkp
2001-10-11 17:42 ` Robert Love
2001-10-11 17:52 ` Tim Connors
2001-10-11 18:11 ` Tim Moore
2001-10-12  2:01   ` Horst von Brand
     [not found]     ` <001901c152ca$0b42c080$0600000a@petersohn.net>
2001-10-12 18:32       ` Tim Moore
2001-10-11 18:13 ` Tim Moore
2001-10-11 18:23   ` J Sloan
2001-10-11 18:56     ` Tim Moore
2001-10-11 19:59       ` [OT] " J Sloan
2001-10-12  4:42         ` T. A.
2001-10-12  6:07           ` J Sloan
2001-10-12  9:14             ` T. A.
2001-10-12  9:59               ` Luigi Genoni
2001-10-12 17:35               ` J Sloan [this message]
2001-10-12 22:59                 ` J . A . Magallon
2001-10-11 23:50       ` Oden Eriksson
2001-10-11 23:56         ` Arnaldo Carvalho de Melo
2001-10-12  0:09         ` J Sloan
2001-10-12  4:37     ` T. A.
2001-10-12  6:56       ` Ville Herva
2001-10-12  9:25         ` T. A.
2001-10-12 10:02           ` Ville Herva
2001-10-12 11:35         ` Andrea Arcangeli
2001-10-11 19:43   ` M. R. Brown
2001-10-11 22:05 ` Luigi Genoni

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=3BC729E2.E93A416E@lexus.com \
    --to=jjs@lexus.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tkhoadfdsaf@hotmail.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