Posted by
CmdrTaco
on from the snag-the-isos-while-they're-hot dept.
weeble writes "Red Hat 7 is now out. The updates to the Red Hat web site have been made; however the ftp site has not yet been updated." Remember to use mirrors folks. Its gonna be a bit before they all catch up so be patient.
There is still no prediction of when 2.4.0 will be released, and probably we'll have to wait at least for 2.4.2 to get a kernel that is as stable as 2.2.18.
We can't delay the 7.0 release forever (see the KDE thread).
Red Hat Linux 7 is ready for Kernel 2.4 though - just install the kernel and everything will work (we're even including a prerelease rpm).
I'm running Red Hat Linux 7 with 2.4.0 kernels on a couple of machines - no problems so far [on pretty much standard low-end hardware].
-- This message is provided under the terms outlined at http://www.bero.org/terms.html
How long do you think (proper) QA takes? We didn't want to release "yet another buggy.0."
Then, pressing the CDs takes some time, getting them packaged takes some time...
We've gone gold a while before bind 9 has been released, and even if we hadn't, there's no chance anything this different from prior versions could have got in that late in the cycle.
On a different note, I've built 9.0 in the 7.1 tree the day it was released.
While it does its core functionality perfectly, there are still a couple of problems left that wouldn't be tolerated in a Red Hat Linux release.
Especially when running on 2.2 kernels, bind 9 isn't 100% ready yet.
-- This message is provided under the terms outlined at http://www.bero.org/terms.html
I'm very pleased that they've changed the default window manager (when running GNOME, anyway) from Enlightenment to Sawfish. I think that a lot of people who thought they hated GNOME, actually just hated Enlightenment.
Sawfish is nice and lean, it makes the GNOME experience snappy and responsive. Thankfully, with Rasterman now off the payroll, Red Hat was able to make this switch, and I think it makes their product that much better. --
-- Tired of FB/Google censorship? Visit UNCENSORED!
We're using a new glibc (2.2), a new and binary incompatible libstdc++ (gcc 2.96; some ABI changes were required to support more C++ features) as well as a new package format (rpm v4).
If you want to use rawhide packages on older versions of Red Hat Linux or other distributions using rpm, get rpm 3.0.5 or higher (3.0.5 is the first 3.x version that supports rpm v4 packages), get the source rpm and use rpm --rebuild.
That should work in most cases.
-- This message is provided under the terms outlined at http://www.bero.org/terms.html
The European version contains some additional CDs.
Since net access is still very expensive in many countries in Europe, we decided we should include more packages (that can be simply downloaded in the rest of the world) in Europe.
The additions (including, of course, Parsec) will be available on ftp.redhat.de (unless licenses don't permit it) - parts of them, such as our new, credit card sized Rescue CD, are available already.
-- This message is provided under the terms outlined at http://www.bero.org/terms.html
xinetd is more secure (it has tcp wrappers functionality implemented), and it supports having a different config file for each service, making it much more easily maintainable by config tools.
Because of this change, we could finally get all the inet services into ntsysv - along with the ones running as daemons.
This sort of stuff is MUCH harder to achieve with the traditional inetd.
-- This message is provided under the terms outlined at http://www.bero.org/terms.html
From my perspective, upgrading to 7.0 is definitely worth it. The 7.0 distro has much more software than 6.2, and includes many packages that I have been manually installing since the 6.0 days. 7.0 will save me a lot of time: I no longer have to constantly maintain and upgrade the packages that ship with the base 7.0 distro. Folks who have been installing certain popular add-on software will be pleasantly surprised and relieved that they will no longer have to do that.
As far as the RPM 4.0 issue goes, changes in 4.0 are mostly on the database back-end. The database back-end is more reliable, and 4.0 packages are also a bit smaller due to some internal reorganization.
I really like the new default desktop in 7.0. 7.0 looks and feels much, much better than 6.2.
As far as upgrading goes, just make sure to run Xconfigurator after the upgrade, to make sure that you get the correct X server. Run sndconfig too, if you have a sound card. Also, go through/tmp/upgrade.log to see what configuration files have been reset, so that you can add back any site-specific configurations. This is really no different than previous RH upgrades, actually. Same thing.
As we all know, Red Hat ties the name of one version to the next. Fitting "Guinness" is a little difficult.
Version - Name - Tie-together
3.0.3 - Picasso
3.0.4 - Rembrandt - Painters
4.0 - Colgate - Toothpastes
4.1 - Vanderbilt - Universities
4.2 - Biltmore - The Vanderbilts lived in Biltmore Estate
4.8 - Thunderbird - Hotels near the San Jose airport
4.9 - Mustang - Ford automobiles
5.0 - Hurricane - WWII fighters
5.1 - Manhattan - Mixed drinks
5.2 - Apollo - Theaters
5.9 - Starbuck - Battlestar Galactica characters
6.0 - Hedwig - Starbuck MN & St Hedwig TX are small towns
beta - Lorax - Hedwig Godiva & the Lorax are Dr Seuss characters
6.1 - Cartmann - MS Word macro-viruses (or cartoon characters)
beta - Piglet - Cartoon characters
6.2 - Zoot - Dr Piglet & Sir Zoot are occupants of Castle Anthrax
beta - Pinstripe - Types of suits
Linux Planet had an article in which they claimed the version after "Pinstripe" would be called "Winston".
At first, I had difficulty finding a tie-together between "Pinstripe" and "Guinness", but with "Winston" as an in-between, we have the Winston Fabrics which has a pinstripe product, and Winston's Restaurant in Colorado which serves Guinness, or Winston Agaba, who is a brand manager for Guinness, or Winston Churchill and Alec Guinness were both knighted.
Upon further examination, however, I discovered there is a red ale called "SKA Pinstripe", which seems to be a much cleaner tie-together with Guinness.
I'm still wondering about that "Winston" that Linux Planet mentioned.
Christopher A. Bohn
-- cb
Oooh! What does this button do!?
Liking GNOME is NOT disliking KDE.
by
bero-rh
·
· Score: 3
The fact that most of us like GNOME doesn't mean we don't like KDE.
We don't like the Qt 1.x license. That's all.
By now, GNOME has progressed far beyond a point where we would want to drop it as soon as there's a stable release of KDE running on Qt 2.x, so that's not going to happen.
Red Hat will continue to support both desktops.
-- This message is provided under the terms outlined at http://www.bero.org/terms.html
Integrated with the Red Hat Network.
Since it's already slashdotted, care to enlighten us as to what this is all about? I'm wary of the name already -- it's way too close MSN...
It's a way of administering and monitoring your systems - the base service is for it to notify you when any of the rpms on your systems has been updates, and install that. Later on, we're planning to add enterprise features. The basic service is intended to be free, while we will sell higher level services including support.
(on rpm 4) Which gives us what benefits over 3.x?
It has some code in it to handle multiple architectures on the same system (IA64 can use IA32 binaries, same situation for SPARC/UltraSPARC), it is based on db3 and has transaction support, it has new standard macros and build policies and many internal changes. Probably more I don't know of (i.e. not highly visible)
Re:Redhat x.0 or x.1 -- wait and research...
by
dew
·
· Score: 4
Those who merely install Linux and expect it to be secure deserve to get rooted.
Technosnobbery in general is abhorrent, but to see someone like you refusing to even acknowledge that perhaps a distribution could be shipped secure out-of-the-box additionally reflects ignorance.
Distributions should be friendly, easy-to-use, and informative. They should instruct where necessary (i.e., 'Turning on this option will let anyone remotely read the directories you've specified. Are you sure you want to do this?') and be as secure as possible.
Why hasn't anyone done an OpenBSD-style audit on the Linux source base? There, at least, they know a thing or two about shipping a secure distribution. Instead of making fun of their users they simply provide them with the world's most secure operating system out-of-the box, no questions asked.
The short of it? Distros can and should be secure out-of-the box and any potentially insecure operations should be accompanied by links to the latest literature. Users should be informed about security updates instead of having to actively discover patches, with an option for one-click upgrades (e.g., 'The FTP server you're running has just been updated. Your version contains a serious security hole. Would you like to update it now?'). These things are possible.
Don't make fun of users for wanting a good product.
Re:A nonexistent compiler... excellent.
by
teg
·
· Score: 3
That's odd. I've been a minor (very minor, mind you) GCC contributor for a while, and I could have sworn that 2.96 doesn't actually exist.
The actual release is marked gcc version 2.96 20000731 (Red Hat Linux 7.0) .
It is tagged in the trees, and will be supported by the former cygnus(which is now part of Red Hat, including the gcc engineers). We've put a lot of work into making this a stable, high-performance compiler and so far it looks like one.
A nonexistent compiler... excellent.
by
devphil
·
· Score: 5
a new and binary incompatible libstdc++ (gcc 2.96; some ABI changes were required to support more C++ features)
That's odd. I've been a minor (very minor, mind you) GCC contributor for a while, and I could have sworn that 2.96 doesn't actually exist.
In fact, I believe that "2.96" is the name given to the current series of snapshots, which are known to be incomplete and not fully working and missing documentation, because if you're using a snapshot, it is assumed that you don't need all the documentation, you know what's working and what isn't, etc, etc.
Why did RH choose to use an unstable compiler as the default for a major distro? I can't wait to see all the crap on the gcc-bugs mailing list, from people using an incomplete compiler.
-- You cannot apply a technological solution to a sociological problem. (Edwards' Law)
Re:A nonexistent compiler... excellent.
by
devphil
·
· Score: 3
gcc version 2.96 20000731
Yah, exactly. The YYYYMMDD designation is given to snapshots, not releases. The GCC folks are very careful to distinguish between the two. This marks a compiler as being incomplete...
...which still doesn't answer my question of why RH chose to use a snapshot instead of the latest release? (Note the terms, please.) The current goal is to have 3.0 out around year's end, two months from now; why not just wait until then?
-- You cannot apply a technological solution to a sociological problem. (Edwards' Law)
Re:Large File support (2GB)
by
bero-rh
·
· Score: 3
You don't even need kernel 2.4 - we're also including the kernel for the Enterprise Edition (kernel-enterprise-*rpm) which has the LFS patch.
-- This message is provided under the terms outlined at http://www.bero.org/terms.html
you can also make a beetle travel at the speed of light... though it does require that you strap three or four warp drives to the top of it... not to mention the procedure requires a ton of duct tape.
-- Ignore the "p2p is theft" trolls, they're just uninformed
Red Hat Linux 7.0 is far more uptodate than Slackware 7, Mandrake 7.1 etc - our version number is there to say what is and what isn't binary compatible. Some of the others just play the number game (Mandrake, Slackware), SuSE seems to have their own versioning instead of just upping their number(I'm not sure what it is yet...) and Debian also has their own versioning.
new 2.2ish glibc
new gcc compiler, with performance enhancements
openssl, openssh
Integrated with the Red Hat Network. The base service is free.
optimized for PentiumPro or higher, while maintaining backwards compatibility
XFree 4, with accelerated 3D support for some cards. Many XFree 3.x servers used for stability reasons, but they also work with GLX.
RPM 4
USB support for mice and keyboard (the rest is included as is)
Gnome 1.2 (seems to have less bugs than helix)
preview of KDE 2 and 2.4 kernel
FHS layout
QT 2.2
And probably more features I'm just taking for granted now...
I've been dying to get RH7.0 for one reason: Parsec.
According to this page the european RH7.0 version will include a playable demo (lan party beta release as they call it) with 50 MB of mp3 music aswell. Now what I want to know is will parsec be included in the iso(s) that are free for download? If anybody with insight could give some input on this I'd love to hear it.
And yes, I *HAVE* checked parsec for downloads. And no, there are none.
Hope this isn't too offtopic, but I'm dying to try parsec. Also wouldn't mind trying RH7.0, but that is not the main reason for me to upgrade;>
We're setting up a test drive of RedHat 7.0 in the Compaq Test Drive program today. It should be available this afternoon - we'll post an announcement on our main page when it is. Once it's ready, you'll be able to get a free shell account on it by going to our web site and registering. You'll be able to explore what the new release is like and try compiling your code against it without having to download and install it on your own system.
Actually, we think KDE 2.0 is very important.
The reason why we've ever had problems with KDE was the non-free nature of the Qt 1.x license - with Qt 2.0 (which is used by KDE 2.0 and can't be used with KDE 1.x), these problems are gone.
Qt 2.2.0 is even GPL (we'd still prefer LGPL, but given Trolltech's business model, it's perfectly clear that it won't happen, and that's ok).
If you've checked the beta, you've probably noticed we had a CVS snapshot of KDE 2 in there - both because of the great features of KDE 2 and because we'd like to get rid of Qt 1.x's license problems.
Unfortunately, it wasn't stable enough for prime time when we had to go gold, so we had to go back to KDE_1_1_BRANCH CVS - and packaged up the current beta for the preview directory.
Moving release dates (especially without knowing for sure when the stuff will finally be ready) would have been a big pain for the business side (I'm not part of that, so I can't give you the exact details, but the basics are obvious).
It'll be in 7.1 (which is already being heavily worked on) unless the planned KDE 2.0 release date is moved by months. (Actually the internal 7.1 build already has a CVS snapshot of KDE 2).
-- This message is provided under the terms outlined at http://www.bero.org/terms.html
After downloading and upgrading to RH7.0 from 6.2, I can tell you this:
Unless you know how to recompile your kernel to get your USB devices working, upgrade to 7.0 - it's definitely worth it. My USB mouse now works, and USB keyboards supposedly work too, but I don't have one to test it with..
The updated Glib and GTK+ libraries make for a serious pain in the ass for recompiling your favorite apps. Make sure that they're compatible before upgrading.
Sawfish rules! Even though you can download it and install it, it's just nice to see it as the standard WM. (BTW - Anyone know why it changed its name from Sawmill?)
Basically, you can make the upgrade yourself by upgrading a few things and installing a new kernel. It's not a huge release like 6.0 was, but it might be worth the money if you're not willing to wrestle with stuff like Glib, GTK, or Qt. If you want the new Gnome look without installing 7.0, your best bet is to install Helix Gnome.
Note: If you're running Pinstripe (the RH7 beta), the upgrade is a bit rocky. I would recommend either reinstalling Red Hat completely, or doing a manual upgrade.
Redhat x dot zero releases
by
MarNuke
·
· Score: 3
Ever since redhat was started, dot zero releases are like the front bumper of car that was driven 1300 miles in south Georgia and Florida in the summer.
Slashdot Mirror
There is still no prediction of when 2.4.0 will be released, and probably we'll have to wait at least for 2.4.2 to get a kernel that is as stable as 2.2.18.
We can't delay the 7.0 release forever (see the KDE thread).
Red Hat Linux 7 is ready for Kernel 2.4 though - just install the kernel and everything will work (we're even including a prerelease rpm).
I'm running Red Hat Linux 7 with 2.4.0 kernels on a couple of machines - no problems so far [on pretty much standard low-end hardware].
This message is provided under the terms outlined at http://www.bero.org/terms.html
How long do you think (proper) QA takes? We didn't want to release "yet another buggy .0."
Then, pressing the CDs takes some time, getting them packaged takes some time...
We've gone gold a while before bind 9 has been released, and even if we hadn't, there's no chance anything this different from prior versions could have got in that late in the cycle.
On a different note, I've built 9.0 in the 7.1 tree the day it was released.
While it does its core functionality perfectly, there are still a couple of problems left that wouldn't be tolerated in a Red Hat Linux release.
Especially when running on 2.2 kernels, bind 9 isn't 100% ready yet.
This message is provided under the terms outlined at http://www.bero.org/terms.html
I'm very pleased that they've changed the default window manager (when running GNOME, anyway) from Enlightenment to Sawfish. I think that a lot of people who thought they hated GNOME, actually just hated Enlightenment.
Sawfish is nice and lean, it makes the GNOME experience snappy and responsive. Thankfully, with Rasterman now off the payroll, Red Hat was able to make this switch, and I think it makes their product that much better.
--
Tired of FB/Google censorship? Visit UNCENSORED!
We're using a new glibc (2.2), a new and binary incompatible libstdc++ (gcc 2.96; some ABI changes were required to support more C++ features) as well as a new package format (rpm v4).
If you want to use rawhide packages on older versions of Red Hat Linux or other distributions using rpm, get rpm 3.0.5 or higher (3.0.5 is the first 3.x version that supports rpm v4 packages), get the source rpm and use rpm --rebuild.
That should work in most cases.
This message is provided under the terms outlined at http://www.bero.org/terms.html
The European version contains some additional CDs.
Since net access is still very expensive in many countries in Europe, we decided we should include more packages (that can be simply downloaded in the rest of the world) in Europe.
The additions (including, of course, Parsec) will be available on ftp.redhat.de (unless licenses don't permit it) - parts of them, such as our new, credit card sized Rescue CD, are available already.
This message is provided under the terms outlined at http://www.bero.org/terms.html
xinetd is more secure (it has tcp wrappers functionality implemented), and it supports having a different config file for each service, making it much more easily maintainable by config tools.
Because of this change, we could finally get all the inet services into ntsysv - along with the ones running as daemons.
This sort of stuff is MUCH harder to achieve with the traditional inetd.
This message is provided under the terms outlined at http://www.bero.org/terms.html
Disclaimer: I've been beta-testing 7.0
From my perspective, upgrading to 7.0 is definitely worth it. The 7.0 distro has much more software than 6.2, and includes many packages that I have been manually installing since the 6.0 days. 7.0 will save me a lot of time: I no longer have to constantly maintain and upgrade the packages that ship with the base 7.0 distro. Folks who have been installing certain popular add-on software will be pleasantly surprised and relieved that they will no longer have to do that.
As far as the RPM 4.0 issue goes, changes in 4.0 are mostly on the database back-end. The database back-end is more reliable, and 4.0 packages are also a bit smaller due to some internal reorganization.
I really like the new default desktop in 7.0. 7.0 looks and feels much, much better than 6.2.
As far as upgrading goes, just make sure to run Xconfigurator after the upgrade, to make sure that you get the correct X server. Run sndconfig too, if you have a sound card. Also, go through /tmp/upgrade.log to see what configuration files have been reset, so that you can add back any site-specific configurations. This is really no different than previous RH upgrades, actually. Same thing.
---
As we all know, Red Hat ties the name of one version to the next. Fitting "Guinness" is a little difficult.
Version - Name - Tie-together3.0.3 - Picasso
3.0.4 - Rembrandt - Painters
4.0 - Colgate - Toothpastes
4.1 - Vanderbilt - Universities
4.2 - Biltmore - The Vanderbilts lived in Biltmore Estate
4.8 - Thunderbird - Hotels near the San Jose airport
4.9 - Mustang - Ford automobiles
5.0 - Hurricane - WWII fighters
5.1 - Manhattan - Mixed drinks
5.2 - Apollo - Theaters
5.9 - Starbuck - Battlestar Galactica characters
6.0 - Hedwig - Starbuck MN & St Hedwig TX are small towns
beta - Lorax - Hedwig Godiva & the Lorax are Dr Seuss characters
6.1 - Cartmann - MS Word macro-viruses (or cartoon characters)
beta - Piglet - Cartoon characters
6.2 - Zoot - Dr Piglet & Sir Zoot are occupants of Castle Anthrax
beta - Pinstripe - Types of suits
Linux Planet had an article in which they claimed the version after "Pinstripe" would be called "Winston".
At first, I had difficulty finding a tie-together between "Pinstripe" and "Guinness", but with "Winston" as an in-between, we have the Winston Fabrics which has a pinstripe product, and Winston's Restaurant in Colorado which serves Guinness, or Winston Agaba, who is a brand manager for Guinness, or Winston Churchill and Alec Guinness were both knighted.
Upon further examination, however, I discovered there is a red ale called "SKA Pinstripe", which seems to be a much cleaner tie-together with Guinness.
I'm still wondering about that "Winston" that Linux Planet mentioned.
Christopher A. Bohn
cb
Oooh! What does this button do!?
The fact that most of us like GNOME doesn't mean we don't like KDE.
We don't like the Qt 1.x license. That's all.
By now, GNOME has progressed far beyond a point where we would want to drop it as soon as there's a stable release of KDE running on Qt 2.x, so that's not going to happen.
Red Hat will continue to support both desktops.
This message is provided under the terms outlined at http://www.bero.org/terms.html
Integrated with the Red Hat Network. Since it's already slashdotted, care to enlighten us as to what this is all about? I'm wary of the name already -- it's way too close MSN...
It's a way of administering and monitoring your systems - the base service is for it to notify you when any of the rpms on your systems has been updates, and install that. Later on, we're planning to add enterprise features. The basic service is intended to be free, while we will sell higher level services including support.
(on rpm 4) Which gives us what benefits over 3.x?
It has some code in it to handle multiple architectures on the same system (IA64 can use IA32 binaries, same situation for SPARC/UltraSPARC), it is based on db3 and has transaction support, it has new standard macros and build policies and many internal changes. Probably more I don't know of (i.e. not highly visible)
Technosnobbery in general is abhorrent, but to see someone like you refusing to even acknowledge that perhaps a distribution could be shipped secure out-of-the-box additionally reflects ignorance.
Distributions should be friendly, easy-to-use, and informative. They should instruct where necessary (i.e., 'Turning on this option will let anyone remotely read the directories you've specified. Are you sure you want to do this?') and be as secure as possible.
Why hasn't anyone done an OpenBSD-style audit on the Linux source base? There, at least, they know a thing or two about shipping a secure distribution. Instead of making fun of their users they simply provide them with the world's most secure operating system out-of-the box, no questions asked.
The short of it? Distros can and should be secure out-of-the box and any potentially insecure operations should be accompanied by links to the latest literature. Users should be informed about security updates instead of having to actively discover patches, with an option for one-click upgrades (e.g., 'The FTP server you're running has just been updated. Your version contains a serious security hole. Would you like to update it now?'). These things are possible.
Don't make fun of users for wanting a good product.
David E. Weekly
David E. Weekly
Code / Think / Teach / Learn
h4x0r for
That's odd. I've been a minor (very minor, mind you) GCC contributor for a while, and I could have sworn that 2.96 doesn't actually exist.
The actual release is marked
gcc version 2.96 20000731 (Red Hat Linux 7.0)
. It is tagged in the trees, and will be supported by the former cygnus(which is now part of Red Hat, including the gcc engineers). We've put a lot of work into making this a stable, high-performance compiler and so far it looks like one.
a new and binary incompatible libstdc++ (gcc 2.96; some ABI changes were required to support more C++ features)
That's odd. I've been a minor (very minor, mind you) GCC contributor for a while, and I could have sworn that 2.96 doesn't actually exist.
In fact, I believe that "2.96" is the name given to the current series of snapshots, which are known to be incomplete and not fully working and missing documentation, because if you're using a snapshot, it is assumed that you don't need all the documentation, you know what's working and what isn't, etc, etc.
Why did RH choose to use an unstable compiler as the default for a major distro? I can't wait to see all the crap on the gcc-bugs mailing list, from people using an incomplete compiler.
You cannot apply a technological solution to a sociological problem. (Edwards' Law)
You don't even need kernel 2.4 - we're also including the kernel for the Enterprise Edition (kernel-enterprise-*rpm) which has the LFS patch.
This message is provided under the terms outlined at http://www.bero.org/terms.html
Mandrake goes to 7.1 ... That's 0.1 louder isn't it?
You can never equivocate too much.
you can also make a beetle travel at the speed of light ... though it does require that you strap three or four warp drives to the top of it ... not to mention the procedure requires a ton of duct tape.
Ignore the "p2p is theft" trolls, they're just uninformed
Red Hat Linux 7.0 is far more uptodate than Slackware 7, Mandrake 7.1 etc - our version number is there to say what is and what isn't binary compatible. Some of the others just play the number game (Mandrake, Slackware), SuSE seems to have their own versioning instead of just upping their number(I'm not sure what it is yet...) and Debian also has their own versioning.
And probably more features I'm just taking for granted now...
I've been dying to get RH7.0 for one reason: Parsec.
;>
According to this page the european RH7.0 version will include a playable demo (lan party beta release as they call it) with 50 MB of mp3 music aswell. Now what I want to know is will parsec be included in the iso(s) that are free for download? If anybody with insight could give some input on this I'd love to hear it.
And yes, I *HAVE* checked parsec for downloads. And no, there are none.
Hope this isn't too offtopic, but I'm dying to try parsec. Also wouldn't mind trying RH7.0, but that is not the main reason for me to upgrade
We're setting up a test drive of RedHat 7.0 in the Compaq Test Drive program today. It should be available this afternoon - we'll post an announcement on our main page when it is. Once it's ready, you'll be able to get a free shell account on it by going to our web site and registering. You'll be able to explore what the new release is like and try compiling your code against it without having to download and install it on your own system.
Actually, we think KDE 2.0 is very important.
The reason why we've ever had problems with KDE was the non-free nature of the Qt 1.x license - with Qt 2.0 (which is used by KDE 2.0 and can't be used with KDE 1.x), these problems are gone.
Qt 2.2.0 is even GPL (we'd still prefer LGPL, but given Trolltech's business model, it's perfectly clear that it won't happen, and that's ok).
If you've checked the beta, you've probably noticed we had a CVS snapshot of KDE 2 in there - both because of the great features of KDE 2 and because we'd like to get rid of Qt 1.x's license problems.
Unfortunately, it wasn't stable enough for prime time when we had to go gold, so we had to go back to KDE_1_1_BRANCH CVS - and packaged up the current beta for the preview directory.
Moving release dates (especially without knowing for sure when the stuff will finally be ready) would have been a big pain for the business side (I'm not part of that, so I can't give you the exact details, but the basics are obvious).
It'll be in 7.1 (which is already being heavily worked on) unless the planned KDE 2.0 release date is moved by months. (Actually the internal 7.1 build already has a CVS snapshot of KDE 2).
This message is provided under the terms outlined at http://www.bero.org/terms.html
Basically, you can make the upgrade yourself by upgrading a few things and installing a new kernel. It's not a huge release like 6.0 was, but it might be worth the money if you're not willing to wrestle with stuff like Glib, GTK, or Qt. If you want the new Gnome look without installing 7.0, your best bet is to install Helix Gnome.
Note: If you're running Pinstripe (the RH7 beta), the upgrade is a bit rocky. I would recommend either reinstalling Red Hat completely, or doing a manual upgrade.
--Dave
http://phattechnology.net
Ever since redhat was started, dot zero releases are like the front bumper of car that was driven 1300 miles in south Georgia and Florida in the summer.
Wait until RedHat x.1 to downgrade.
MarNuke