From: "T. A." <tkhoadfdsaf@hotmail.com>
To: "J Sloan" <jjs@pobox.com>, "linux-kernel" <linux-kernel@vger.kernel.org>
Subject: Re: [OT] Re: Which kernel (Linus or ac)?
Date: Fri, 12 Oct 2001 05:14:33 -0400 [thread overview]
Message-ID: <OE394qrvAsp4XgWZGbR0000e29d@hotmail.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>
> That's odd, my Red Hat servers have been
> almost like appliances. Not perfect, but all
> the problems I've seen could be dealt with.
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 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. And once I have to replace the system experimental C
library and compiler it just get even more ridicules.
> I've seen worse problems in commercial
> unices, e.g. unixware - yuk - and hpux.
I know. Please don't remind me of UnixWare. I buried that at my
clients' and companies' sites in the Linux 1.2.x days.
> x.0 release: New stuff, interesting, buggy
> x.1 release: A passable cleanup of the bugs in .0
> x.2 release: A smooth, polished, evolution of .1
Well here's hoping that 7.2 is smooth and polished. Especially since
Redhat has become the defacto standard and I'll probably be trying it out
again.
> (shrug) I had no idea it was alpha - it works
> well for me, and I'm a vi man.
I never keep it around for long after I saw it crash a couple of times
on my first 7.0 or 7.1 box so I can't say much about its stability. Besides
it was more the principal of the thing. Why in the world use the alpha
version of a text editor when a perfectly good released version exists with
pretty much the same functionality. One thing I did notice, if I remember
correctly. Seamed that either the installed vim was crippled or had a bug
in reading my customized .vimrc file. My custom options didn't get loaded
until I downloaded the latest 5.[89] source and recompiled myself a new
version.
next prev parent reply other threads:[~2001-10-12 9:16 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-11 14:45 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. [this message]
2001-10-12 9:59 ` Luigi Genoni
2001-10-12 17:35 ` J Sloan
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=OE394qrvAsp4XgWZGbR0000e29d@hotmail.com \
--to=tkhoadfdsaf@hotmail.com \
--cc=jjs@pobox.com \
--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
all inboxes | Powered by JetHome®