From: "Victor Tsaran" <vtsaran@nimbus.ocis.temple.edu>
To: <speakup@speech.braille.uwo.ca>
Subject: Fw: difference of redhat 6.2 and 7.0
Date: Mon, 30 Oct 2000 13:16:28 -0500 [thread overview]
Message-ID: <000e01c0429d$85eeeae0$beeef79b@default> (raw)
----- Original Message -----
From: "xander" <xwiggen@students.cs.uu.nl>
To: <blinux-list@redhat.com>
Sent: Monday, October 30, 2000 6:50 AM
Subject: Re: difference of redhat 6.2 and 7.0
| >
| > Hi,
| > In addition to the kernel headers issue you mention, RedHat also
| > APPEARS to have shipped gcc 2.96 with Redhat 7.0. The 2.96 version of
GCC
| > was NOT meant for public consumption, and was supposed to be some kind
of
| > beta which was only to be used/tested by Redhat themselves. As a result
| > of RedHat releasing 2.96, GNU decided that there new version of GCC
(when
| > it is ready to be released) will be called 2.97. I have not
specifically
| > asked RedHat nor GNU about this first hand, so if anyone would like to
| > correct me please feel free... The bottom line is that some things with
| > GCC seem to be broken. I am not sure whether there is a patch yet or
some
| > other meccanism to role back to GCC 2.96.
| >
| > There is also some bug in Redhat 7.0 which causes a crash every two
| > weeks or so - some kind of memory leak. I am not sure exactly where the
| > memory leak is - I think there is already an RPM update for it though.
|
| RedHat 7.0 is a bit flaky indeed. 2.2.x kernel sources don't compile
| properly. Better wait till 7.1 is out and run 6.2 in the meantime.
|
| Regards,
| xander van wiggen
|
|
|
|
| _______________________________________________
| Blinux-list mailing list
| Blinux-list@redhat.com
| https://listman.redhat.com/mailman/listinfo/blinux-list
reply other threads:[~ UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='000e01c0429d$85eeeae0$beeef79b@default' \
--to=vtsaran@nimbus.ocis.temple.edu \
--cc=speakup@speech.braille.uwo.ca \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).