Thank you gentlemen. This is rumor control. Here are the facts. As some of you know, new Red Hat Linux Beta bits crash landed here at 1000 on the morning watch. There was one survivor. Two dead processes, and a daemon that was hopelessly smashed beyond repair. The survivor is called SEVERN.
It's that time again. (Time to floss?) (Time to make a gooky?)
No, it's time for a Red Hat Linux Beta, named SEVERN.
"I just want to say that I took a vow of stability. That also includes betas. We all took the vow. Now let me say, that I for one, do not appreciate Company policy allowing beta bits to freely intermingle..."
"Cheeky bastard, right sir?"
"What brother means to say is ... We view the presence of any outside OS, beta, as a violation of the stability, a potential break in the spiritual unity."
We are well aware of your feelings in this matter. You will be pleased to know that I have requested a testing team - Hopefully, they will be here inside of a few hours and evaluate it A.S.A.P.
As always, betas such as SEVERN are not intended for use on production environments. Use as such could lead to your machines being slaughtered like pigs by the dragon. Or just public laughter.
Problems with SEVERN should be reported via bugzilla, at:
http://bugzilla.redhat.com/bugzilla/
What's its development status?
"It doesn't seem too horrendously in flux. Difficult at this moment to make a specific diagnosis."
Among other things, SEVERN has: - a new graphical boot - GCC 3.3 - an updated 2.4.21 kernel - updated Evolution and Mozilla - and more!
Will it live?
"Yes, I should think so."
Look, none of us here is naive. It's in everybody's best interests if this beta doesn't come out into production until the testing team is through with it. And certainly not without the proper qualification and bug reports. Right? So we should all stick to our set routines and not get unduly agitated. Correct? All right. Thank you gentlemen.
Speaking of unduly agitated... there's lots of rumors going on about Red Hat Linux. We've been doing it for nearly ten years now, and in that time, there's been various changes. From rpp to RPM, from Red Hat Commercial Linux to Official Red Hat Linux, from 'install' to anaconda. And now, we're making another change.
We changed the rules. We said our Linux should be your Linux. Just as most of the software in Red Hat Linux is developed in an open fashion, so should Red Hat Linux itself; driven by those who develop, test, document, and translate. To accomplish this, we're opening up our process.
Now this is an evolution, not a revolution. The first steps will be moving much of our development discussions and schedules external, via mailing lists and other means, and including external developers in the process of making technical decisions. More will be done from there. Red Hat Linux will remain as it has been; a freely available general purpose operating system, released on the average every six months. For more information, see:
For discussion of SEVERN, send mail to:
rhl-beta-list-request@redhat.com
with
subscribe
in the subject line. You can leave the body empty. Or see:
https://listman.redhat.com/mailman/listinfo/rhl-beta-list/
As always, you can get SEVERN at redhat.com, specifically:
ftp://ftp.redhat.com/pub/redhat/beta/severn/
Or the following mirrors:
North America: United States: ftp://moni.msci.memphis.edu/pub/redhat/linux/beta/severn/ http://moni.msci.memphis.edu/pub/redhat/linux/beta/severn/ ftp://linux.stanford.edu/pub/mirrors/redhat/linux/beta/severn/ ftp://ftp.cse.buffalo.edu/pub/RedHat/redhat/linux/beta/severn/ ftp://mirror.eas.muohio.edu/mirrors/redhat/linux/beta/severn/ ftp://mirrors.secsup.org/pub/linux/redhat/beta/severn/ ftp://redhat.dulug.duke.edu/pub/redhat/linux/beta/severn/ ftp://mirror.hiwaay.net/redhat/redhat/linux/beta/severn/ http://mirror.hiwaay.net/redhat/redhat/linux/beta/severn/ http://www.gtlib.cc.gatech.edu/pub/redhat/linux/beta/severn/ ftp://ftp.gtlib.cc.gatech.edu/pub/redhat/linux/beta/severn/ rsync://rsync.gtlib.cc.gatech.edu/redhat/linux/beta/severn/
Canada: ftp://less.cogeco.net/pub/redhat/linux/beta/severn/ ftp://ftp.nrc.ca/pub/systems/linux/redhat/ftp.redhat.com/linux/beta/severn/
South America: Brazil: http://bastion.las.ic.unicamp.br/pub/redhat/linux/beta/severn ftp://bastion.las.ic.unicamp.br/pub/redhat/linux/beta/severn Chile: ftp://ftp.tecnoera.com/Linux/redhat-beta/severn/
Europe: Austria: ftp://gd.tuwien.ac.at/opsys/linux/redhat.com/dist/linux/beta/severn/ http://gd.tuwien.ac.at/opsys/linux/redhat.com/dist/linux/beta/severn/ rsync://gd.tuwien.ac.at/opsys/linux/redhat.com/dist/linux/beta/severn/ Czech Republic: ftp://sunsite.mff.cuni.cz/MIRRORS/ftp.redhat.com/redhat/linux/beta/severn/ ftp://ultra.linux.cz/MIRRORS/ftp.redhat.com/redhat/linux/beta/severn/ ftp://sunsite.cnlab-switch.ch/mirror/redhat/linux/beta/severn/ ftp://ftp.linux.cz/pub/linux/redhat/linux/beta/severn/ ftp://ftp6.linux.cz/pub/linux/redhat/linux/beta/severn/ Denmark: ftp://klid.dk/pub/redhat/linux/beta/severn/ Germany: ftp://ftp.tu-chemnitz.de/pub/linux/redhat-ftp/redhat/linux/beta/severn/ http://wftp.tu-chemnitz.de/pub/linux/redhat-ftp/redhat/linux/beta/severn/ ftp://ftp.informatik.uni-frankfurt.de/pub/linux/Mirror/ftp.redhat.com/linux/beta/severn/ ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/redhat/linux/beta/severn/ Ireland: ftp://ftp.esat.net/mirrors/ftp.redhat.com/redhat/linux/beta/severn/ http://ftp.esat.net/mirrors/ftp.redhat.com/redhat/linux/beta/severn/ rsync://ftp.esat.net/mirrors/ftp.redhat.com/redhat/linux/beta/severn/ Netherlands: ftp://ftp.nluug.nl/pub/os/Linux/distr/RedHat/ftp/redhat/linux/beta/severn/ ftp://ftp.surfnet.nl/pub/os/Linux/distr/RedHat/ftp/redhat/linux/beta/severn/ ftp://alviss.et.tudelft.nl/pub/redhat/beta/severn/ Poland: ftp://sunsite.icm.edu.pl/pub/Linux/redhat/linux/beta/severn/ rsync://sunsite.icm.edu.pl/ftp/pub/Linux/redhat/linux/beta/severn/ http://sunsite.icm.edu.pl/pub/Linux/redhat/linux/beta/severn/ Romania: ftp://ftp.iasi.roedu.net/pub/mirrors/ftp.redhat.com/pub/redhat/linux/beta/severn/ http://ftp.iasi.roedu.net/mirrors/ftp.redhat.com/pub/redhat/linux/beta/sever... rsync://ftp.iasi.roedu.net/ftp.redhat.com/pub/redhat/linux/beta/severn/ Turkey: ftp://ftp.linux.org.tr/pub/redhat/beta/severn/ United Kingdom: http://zeniiia.linux.org.uk/pub/distributions/redhat/beta/severn/ ftp://zeniiia.linux.org.uk/pub/distributions/redhat/beta/severn/ rsync://zeniiia.linux.org.uk/ftp/pub/distributions/redhat/beta/severn/
Asia/Pacific: Australia: http://planetmirror.com/pub/redhat/linux/beta/severn/ ftp://ftp.planetmirror.com/pub/redhat/linux/beta/severn/ http://mirror.aarnet.edu.au/pub/redhat/linux/severn/ ftp://mirror.aarnet.edu.au/pub/redhat/linux/severn/ Japan: ftp://ftp.sfc.wide.ad.jp/pub/Linux/RedHat/linux/beta/severn/ Singapore: ftp://ftp.oss.eznetsols.org/linux/redhat/linux/beta/severn/ rsync://rsync.oss.eznetsols.org/linux/redhat/linux/beta/severn/
One additional feature provided by the Linux community is the availability of SEVERN via BitTorrent.
http://torrent.dulug.duke.edu/severn-binary-iso.torrent http://torrent.dulug.duke.edu/severn-source-iso.torrent
RPMS for Red Hat Linux 7.3 through 9 of BitTorrent are available from: http://torrent.dulug.duke.edu/btrpms/
Usage is simple: btdownloadcurses.py --url http://URL.torrent
Allow incoming TCP 6881 - 6889 to join the torrent swarm. http://torrent.dulug.duke.edu/
The email announcement correctly gave the gcc version as 3.3 however the included release notes state gcc 3.2.3.
"Gerald" == Gerald Henriksen ghenriks@rogers.com writes:
Gerald> The email announcement correctly gave the gcc version as 3.3 Gerald> however the included release notes state gcc 3.2.3.
No -- read the header for that section of the release notes carefully: these are *packages* that are new to the distro. GCC is, indeed at 3.3, but there is also the gcc32 package (notice the different name), which contains GCC 3.2.3...
Ed
On 21 Jul 2003 11:41:57 -0400, you wrote:
"Gerald" == Gerald Henriksen ghenriks@rogers.com writes:
Gerald> The email announcement correctly gave the gcc version as 3.3 Gerald> however the included release notes state gcc 3.2.3.
No -- read the header for that section of the release notes carefully: these are *packages* that are new to the distro. GCC is, indeed at 3.3, but there is also the gcc32 package (notice the different name), which contains GCC 3.2.3...
For whatever reason I overlooked the 32 part (both before and after slashdot incorrectly stated) so my mistake.
My next question would be why is including a second older compiler necessary? I could understand it for the transition to 2.96, and then to 3.2, but why is it necessary from 3.2.* to 3.3?
Gerald Henriksen (ghenriks@rogers.com) said:
My next question would be why is including a second older compiler necessary? I could understand it for the transition to 2.96, and then to 3.2, but why is it necessary from 3.2.* to 3.3?
The kernel is not quite ready to be compiled with gcc-3.3, although it should be getting pretty close at this point.
Bill
My next question would be why is including a second older compiler necessary? I could understand it for the transition to 2.96, and then to 3.2, but why is it necessary from 3.2.* to 3.3?
Gcc 3.3 has an improved parser which rejects some borderline bogus constructs that gcc 3.2 permitted. The kernel like several other projects found it had a few of them. Most notably it used to accept
printk("hello there\n");
now it correctly requires
printk("hello" \ "there\n");
The 2.4.22 kernel should have all these dealt with, and its very much a case of a stricter compiler forcing us to clean up mess.
Actually I thought the second example was legal but overkill. I thought this was also legal.
printk("hello " "there\n");
And technically I believe this is also legal although nasty to read when indented because the second line cannot be indented in most cases.
printk("hello \ there\n");
Of course, the first case you presented is and should be utterly illegal.
It's nice to see you here Alan. {^_^} Joanne "Somewhat crazed trying to avoid some real work" Dow ----- Original Message ----- From: "Alan Cox" alan@redhat.com
My next question would be why is including a second older compiler necessary? I could understand it for the transition to 2.96, and then to 3.2, but why is it necessary from 3.2.* to 3.3?
Gcc 3.3 has an improved parser which rejects some borderline bogus constructs that gcc 3.2 permitted. The kernel like several other projects found it had a few of them. Most notably it used to accept
printk("hello there\n");
now it correctly requires
printk("hello" \ "there\n");
The 2.4.22 kernel should have all these dealt with, and its very much a case of a stricter compiler forcing us to clean up mess.
On Mon, Jul 21, 2003 at 07:26:57PM -0400, Alan Cox wrote:
My next question would be why is including a second older compiler necessary? I could understand it for the transition to 2.96, and then to 3.2, but why is it necessary from 3.2.* to 3.3?
Gcc 3.3 has an improved parser which rejects some borderline bogus constructs that gcc 3.2 permitted. The kernel like several other projects found it had a few of them. [...]
Does that mean that the kernel for severn has to be build with gcc 3.2.x? I.e. could I develop and build binary kernel modules for severn's kernel from RH9 tools?
Axel Thimm (Axel.Thimm@physik.fu-berlin.de) said:
Gcc 3.3 has an improved parser which rejects some borderline bogus constructs that gcc 3.2 permitted. The kernel like several other projects found it had a few of them. [...]
Does that mean that the kernel for severn has to be build with gcc 3.2.x?
The kernel in severn is currently built with gcc-3.2.x.
Bill
-
Alan Cox -
Axel Thimm -
Bill Nottingham -
Edward C. Bailey -
Gerald Henriksen -
jdow