Maybe it would be helpful to know or get some idea of what will not work anymore? I mean, for the most part, my servers are pretty stock RH8. I use PHP, Apache 1.3.27, mySQL (but the newer RPMS from mysql.com since RH is pure failure in their update departement here). And honestly not a lot more than that. Will I still have a working system? Can I still use Apache 1.3.27 since PHP and Apache 2.0 isn't suggested for real servers? Will RH9 have everything that RH8 did at least? What NEW stuff is there (aside from version updates). What is this "linux threads" thing? Is it part of the kernel? What is it responsible for and where will I see improvement by using it? F.e. I know that the 2.6 kernel has some awesome scheduler where people are reporting improved response in everthing from download times to loading times; will this linux threads thing be something noticeable too, or is it just a necessary evil to migrate to something bigger and better down the line (like when Linux switched to ELF was it?) > -----Original Message----- > From: psyche-list-admin@xxxxxxxxxx > [mailto:psyche-list-admin@xxxxxxxxxx] On Behalf Of Jesse Keating > Sent: Friday, March 28, 2003 5:59 PM > To: psyche-list@xxxxxxxxxx > Subject: Re: RH 9 - new glibc > > > On Friday 28 March 2003 17:37, Daevid Vincent wrote: > > Yeah, this baffles me too. It's not like they were close to > a 9.0 release > > anyways, as if they were on like RH 8.7 or something and > just took a small > > leap. They went from 8.0 to 9.0 with no intermediate steps. > If this is such > > a huge jump and so much is going to break, then it seems > mighty foolish to > > me... I know I won't be upgrading my RH 8.0 boxes until > well into RH 9.x > > (assuming there is one and RH doesn't $hit on us again and > jump to 10.0 > > after this release). RH is notorious for blundering their > .0 releases, and > > for them to use a brang new glibc known to break things > already, seems > > extremely dangerous to me. Am I not understanding > something? Do any other > > distros use this new/broken glibc yet? Is there that much > with this glibc > > that is soooo unbelievably awesome that we just *had* to > have it in this RH > > version and it couldn't wait till after 8.1, 8.2, 8.5 or > whatever...? > > Ugh. Glibc doesn't "break" things, just old things aren't > compatible with the > new glibc. It happens all the time. IT's not broken, just > too new. Most > the reason for the 8.0 -> 9 is the Linux threads, which are > supposedly very > cool, and very worth it. > > You just can't win, either you're too old for the people that > want new stuff, > or your too new for the people that want old stuff, or you > don't include 8x > alternatives for every app, or you include way too many > alternatives for each > app... *sigh* > > I guess it's like a judge, they know they're doing their job > if _both_ sides > are pissed off at the end. > > -- > Jesse Keating RHCE MCSE > http://geek.j2solutions.net > Mondo DevTeam (http://www.microwerks.net/~hugo/) > > Was I helpful? Let others know: > http://svcs.affero.net/rm.php?r=jkeating > > > > -- > Psyche-list mailing list > Psyche-list@xxxxxxxxxx > https://listman.redhat.com/mailman/listinfo/psyche-list > -- Psyche-list mailing list Psyche-list@xxxxxxxxxx https://listman.redhat.com/mailman/listinfo/psyche-list
