[ale] RedHat 7.0

[Michael Smith]

	I think someone earlier posted something like this and I quote
"Anything that comes out .0, I consider beta,  I wait until the .2 version
comes out before I actually upgrade."  I think these are good words to live
by as far as Redhat goes.  I am running 6.2 at home as my gateway / firewall
/ db machine and couldn't be happier.  I did install 7.0 on my laptop to see
if it would work and I must say that the install was flawless.  I obviously
haven't done any kernel stuff but I expect issues.  I am still trying to
figure out where everything is and what has changed.  It looks like they
really stuffed alot of changes into this release.  You know things can slip
through the cracks when this happens.  It was nice to have ssh installed by
default, though....

-----Original Message-----
From: Jeff Hubbs [mailto:Jhubbs at niit.com]
To: ale at ale.org
Sent: Friday, October 20, 2000 9:30 AM
To: Armsby John-G16665; 'ale at ale.org'
Subject: RE: [ale] RedHat 7.0


> On Fri, Oct 20, 2000 at 03:10:50AM -0400, Eric Z. Ayers wrote:
> > You can compile a kernel with RH 7.0, but you have to use an older
> > version of gcc. Look for something like: kgcc or kcc or read the RH
> > 7.0 release notes.

I'm kind of pushing away from the whole Red Hat strand because of things
like this.  Any Linux distro ought to have everything - and I mean
EVERYTHING - required to compile all the source code.  I mean, this is such
a basic part of working with Linux; how can someone just ship a distro with
something like this broken??  I know a Linux distro is a very complex thing,
but doesn't anyone at Red Hat actually take a preproduction CD and do basic
stuff like recompile the supplied kernel from the supplied source?  

I'm no huge fan of Mandrake, but I hate to think that part of Mandrake's
role is to put out a more QAed version of Red Hat.



- Jeff

> -----Original Message-----
> From: Armsby John-G16665 [mailto:John.Armsby at motorola.com]
> Sent: Friday, October 20, 2000 8:12 AM
> To: 'ale at ale.org'
> Subject: RE: [ale] RedHat 7.0
> 
> 
> From what I am reading, why would the average non power user 
> want 7.0?  Sounds like a head ache to me.
> 
> John
> 
> 
> -----Original Message-----
> From: Fulton Green [mailto:ale at FultonGreen.com]
> Sent: Friday, October 20, 2000 5:13 AM
> To: Eric Z. Ayers
> Cc: Steve Nicholas; ale at ale.org
> Subject: Re: [ale] RedHat 7.0
> 
> 
> Actually, you CAN use the RH7 default compiler to sucessfully 
> build (and
> run!) the 2.4.0-test kernel. But you've gotta make sure everything is
> properly upgraded in the toolchain (e.g., make sure the 
> binutils RPM is at
> 2.10.0.18-1 or higher).
> 
> FWIW, your compiler is bombing on an assembler source, specifically on
> multi-line #define macros. I don't know if GCC invokes the 
> GNU assembler (as)
> at that point, but just in case, heed the binutils advice 
> above. It also
> wouldn't hurt to make sure the C preprocessor package is at 
> 2.96-54, even
> though I could have sworn I heard one of the GCC project 
> members at the
> recent ALS say that the preproc was now integrated into GCC.
> 
> Regarding the dwindling Diamond color depth: RH7 may have upgraded you
> to XFree 4.0.1, in which case you may have to play around with the new
> XF86Config file format to make sure that XFree has the right 
> knowledge about
> your video RAM and such. And don't forget to read the support docs for
> Diamond chipsets, located on the XFree website 
> (www.XFree.org). FWIW, I have
> a similar problem, going from XGA 24-bit color to XGA 16-bit 
> color between
> Red Hat 6.2 and 7.0.
> 
> On Fri, Oct 20, 2000 at 03:10:50AM -0400, Eric Z. Ayers wrote:
> > You can compile a kernel with RH 7.0, but you have to use an older
> > version of gcc. Look for something like: kgcc or kcc or read the RH
> > 7.0 release notes.
> > 
> > -ERic.
> > 
> > Stephen F Nicholas writes:
> >  > Ok, Ok,
> >  > I know the general consensus is NOT to load RH 7.0.  I 
> went to ALS and
> >  > purchased 7.0.  gnome is getting REALLY memory hungry 
> video wise.  fvwm
> >  > worked in 32 bit mode just fine with my Diamond 4 mb 
> card under 5.2.  6.1
> >  > went down to 24 bit color, and 7.0 went down to 16 bit color.
> >  > 
> >  > I can't compile kernel 2.2.16 from RH's cd.  It bombs 
> real fast.  Since I
> >  > d/l'd 2.2.17 I don't have the error messages from 
> 2.2.16.  HOWEVER, I DO
> >  > have the error messages from kernel 2.2.17 downloaded 
> from kernel.org.  I
> >  > did a make dep, make clean ok.  make bzImage blew with 
> the following error
> >  > message:
> >  > 
> >  > cc -D__KERNEL__ -I/usr/src/linux-2.2.17/include -D__ASSEMBLY__
> >  > -traditional -c checksum.S -o checksum.o
> >  > checksum.S:231: badly punctuated parameter list in #define
> >  > checksum.S:237: badly punctuated parameter list in #define
> >  > make[2]: *** [checksum.o] Error 1
> >  > make[2]: Leaving directory `/usr/src/linux-2.2.17/arch/i386/lib'
> >  > make[1]: *** [first_rule] Error 2
> >  > make[1]: Leaving directory `/usr/src/linux-2.2.17/arch/i386/lib'
> >  > make: *** [_dir_arch/i386/lib] Error 2
> >  > 
> >  > 
> >  > I saw a previous message saying to use kgcc instead of 
> gcc.  I tried both,
> >  > to no avail.  Suggestions??  I'm not a programmer, but I 
> try and do my
> >  > research.
> --
> To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" 
> in message body.
> --
> To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" 
> in message body.
> 
--
To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in message
body.
--
To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in message body.