Slashdot Mirror
RedHat 7.3 beta (skipjack) is out
Just saw in Red Hat's FTP's - Redhat 7.3 (codename:skipjack) is available for download. There aren't lots of changes there, but you'll find that RedHat 7.3 comes with KDE 3.0 (rc3 is on this beta), you'll need to remove the Ximian Gnome before upgrade, and in general - read the release notes before testing this release. As always, don't try it on your main Linux partition, and use the mirrors. Annoucment is here (thanks to Linux Weekly News)
I always thought Red Hat did X.0 X.1 and then X.2 before going to back to X.0. Have they always released a X.3 ?
Oh, wait, this is Skipjack the distribution, not Skipjack the algorithm. Never mind...
Oh, my, in my paranoia I just don't know what to do!
Use 'slashdot stuff' in the subject line in any email you send me if you want to get past the spam filter.
Sure but RedHat's market isn't the desktop. It's all about the server side for them. If RedHat was targeting the desktop, there CEO wouldn't have said that Linux will not make it on the desktop.
You want a desktop distribution? Try Mandrake. A little bloated but pretty good.
Free Mac Mini
From the release notes linked to in the article:
Currently, Red Hat Linux offers Sendmail and Postfix as two Mail Transport Agent (MTA) alternatives. For print daemon alternatives, the choices are LPRng and CUPS. The configurations for LPRng and CUPS are completely separate. If you switch from one printing system to another, you will have to reconfigure your printers.
CUPS 1.1.14 is included, and Qt, KDE and wine are compiled with libcups support.
This message is provided under the terms outlined at http://www.bero.org/terms.html
Is there an automated and clean way to do it ?
I can't reproduce this on any of our boxes, including 7.1, 7.2 and current beta installations.
A backtrace submitted to Bugzilla helps getting things fixed - how are we supposed to fix something we don't even know breaks for you? (Chances are this is a very weird local setup problem)
This message is provided under the terms outlined at http://www.bero.org/terms.html
So I gleefully logon to grab a set of beta ISOs and get some real value out of this subscription and what do I find as far as 7.3 beta goes? Jack. :-(
Come on Redhat...
When 7.3 final comes out, will it show up on rhn at the same time it goes on the public ftp site at least?
You boot in normal install mode and then select "Upgrade" when it prompts you for installation type.
The choice has been moved from the boot loader to the {T,G}UI.
This message is provided under the terms outlined at http://www.bero.org/terms.html
it's actually 3 ISO's - the 3rd is half CD.
The rest ISO's are source code for the distribution.
Hetz (Heunique)
The 4th and 5th CDs are source RPMs, so if you just want to give it a test run without looking at the code, you won't need them.
This message is provided under the terms outlined at http://www.bero.org/terms.html
Usually, X.X is a release, and X.X.XX is a beta.
This message is provided under the terms outlined at http://www.bero.org/terms.html
It isn't.
It doesn't work the "Oh, we need to push a new release out of the door, let's call the current rawhide a beta!" way.
There is a QA cycle even for beta releases to make sure people who aren't asking for it (by using rawhide) aren't getting completely broken stuff.
This message is provided under the terms outlined at http://www.bero.org/terms.html
What they should include instead is Webmin
;) ) and we usually don't ship stuff we can't support well.
Not in the base OS.
Webmin is a nice, user friendly tool, but it's code is horrible (at least to people who don't breathe perl instead of air
Webmin is included on the almost-unsupported extra CD found in European boxes (bandwidth is very expensive in most European countries, so including another CD with stuff you could just download makes sense in the European box).
This message is provided under the terms outlined at http://www.bero.org/terms.html
this is a common problem w/the up and coming Linux users and goes to show why distributions like Mandrake continue to exist even when *I* (being of middle ages Linux) can't stand bloated shit.
;)
Users feel that everything should come standard w/each distribution. Just b/c a distrib is not using X does NOT mean its broken. In fact RH is known for its excellent testing.
Stop being so lazy. Sheesh.
The youngins just need to learn
Knowing RedHat, I would expect them to put the development version [of gnome 2.0] in the final release
That's certainly not going to happen. We don't do major upgrades to an important part of the distribution after a beta, and if you compare any beta versions of RHL with their subsequent release version, you'll notice we never did.
This message is provided under the terms outlined at http://www.bero.org/terms.html
The things you mention don't have much to do with whether or not they upgrade the major number.
I agree it's good they're (apparently) doing a point release instead of 8.0, but for different reasons:
* GCC 3.1 isn't yet ready, but will be within a few months
* ditto glibc 2.3
Had they released 8.0 with the current gcc 2.96 and glibc 2.2, we'd likely be stuck with them for another couple years!
As it is, an 8.0 with those things, along with a new binary compatibility standard that should LAST a while, should be out this summer or early fall. It's win-win.
As for what you mentioned, KDE 3.0 *is* in this release. They upgraded from KDE 1.x to 2.x in Red Hat 7.1, so they can do that kind of thing in minor releases. Same with Mozilla and Gnome. Major releases are only for binary compatibility changes.
Try do that with Redhat
/pub/redhat/linux/beta/skipjack/en/ os/i386/
You need only one floppy to do a Red Hat ftp install. 8)
Get the image
here, boot it, and point the installer at ftp.redhat.com
This message is provided under the terms outlined at http://www.bero.org/terms.html
Rawhide is the only truly e XP erimental release we make...
This message is provided under the terms outlined at http://www.bero.org/terms.html
Unless some miracle happens and KDE 3.0 is delayed by several weeks even though it works,
the released version will have KDE 3.0 final.
A beta release doesn't mean we don't upgrade anything... It just (usually) means we won't do any major upgrades (if KDE 2.2.2 were in the beta, seeing 3.0 in the final would be extremely unlikely).
This message is provided under the terms outlined at http://www.bero.org/terms.html
The gcc3 packages are likely to return for the final, once a final decision on 3.0.4 vs 3.1 has been made.
This message is provided under the terms outlined at http://www.bero.org/terms.html
Carrie Fisher and Alec Guiness were both cast emembers of Star Wars
the fisher and wolverine are both members of the weazel family
The U.S.S. Wolverine and U.S.S. Seawolf are both submarines
The Seawolf was the first sub powered by a liquid metal cooled reactor. It was completed exactly 10 years after the Roswell incident
Enigma is the name of a UFO museum in Roswell, NM
Skipjack and Enigma are both encryption algorithms
Reference: Freshrpms
I'm against picketing, but I don't know how to show it.
Yes. Off the top of my head:
This message is provided under the terms outlined at http://www.bero.org/terms.html
Sure, the zlib stuff has been fixed in *whatever the release will be called*.
This message is provided under the terms outlined at http://www.bero.org/terms.html
Support for Cups?
Yes
Kamera support seems to be compiled in
It is. If you have the equipment, please give it a try.
I've done the port of Kamera from the gphoto 2.0beta3 API to the gphoto 2.0final API, and I don't have the hardware to run any tests other than the Microsoftish "it compiles, therefore it works".
What about cdparanoia/lame and ogg bindings for the
AudioCD IOSlave?
cdparanoia and ogg are built in, lame isn't because it's illegal (patent issues - if you want the support in, write to your government explaining why software patents are evil).
This message is provided under the terms outlined at http://www.bero.org/terms.html
> I try to keep my laptop pure redhat with no
.spec file. A growing number of projects include one. A tarball with a .spec file it better than a SRPM file for all practical intents and purposes. Just do "rpm -tb .tar.gz instead of "rpm -i .srpm ;rpm -bb /usr/src/redhat/SPECS/.spec"
> self compiles.
There is a way to have your cake and eat it too. Build your own RPMS with anything you want that didn't ship on the CD or rebuild their packages with different options. If you build it yourself you can know it will run with your libraries and such. Keep the SRPMS around and you can quickly rebuild anything that breaks after the next OS upgrade. Since you are keeping everything managed with RPM your packages get managed in the same way as RH supplied software and everything 'just works."
It isn't that hard anymore. If you can't find a SRPM on rpmfind.net grab the tar.gz and look inside for a
Democrat delenda est
Mostly the fact that 3.0.x -> 3.1 will break binary compatibility yet again, and will be out soon. .0 release with gcc 3.0.x would mean having to do gcc 3.0.x throughout all .x releases, even after it's obsolete.
Releasing a
It's better to just skip 3.0.x and get a 3.1 or 3.2 based distribution out when it's ready.
This message is provided under the terms outlined at http://www.bero.org/terms.html
The kernel is 2.4.18+patches, so if 2.4.x started to work for you in 2.4.15, you should be ok.
We haven't had any problems with the 2.4.9 errata kernel for 7.2, though.
This message is provided under the terms outlined at http://www.bero.org/terms.html
Hmmm - we are running a server rack with Dell 2550 poweredges, Compaq DM360 + DM 370 a HP LH with internal RAID and a EMC Celera supplying 2TB of NFS mounts on RH 7.2/ 2.4.9 without a burp.
Dod you just download a vanilla 2.4 kernel, or did you use something from RedHat? The -ac series is generally more stable than the stuff you get from kernel.org.
As someone else mentioned, the Skipjack is/was a submarine. It was the first nuclear submarine with an Albacore-type hull. In essence the first 'true' submarine that was truly optimized for underwater, and not a surface ship that temporarily sinks.
Also FYI, the Albacore has been made into a museum, and is the BEST submarine tour I've ever been on, better than any WWII boats, and better than the Nautilus. The WWII boats are too old and worn, and the Nautilus is all behind plexiglass, and they've torn it up too much putting stairs and such in. The albacore is a single level, pretty much accessable from stem to stern.
Former submarine nut, until someone told me in second grade that I would be too tall to be on one. Still, it got me to read 20,000 Leagues Under the Sea at age 9.
The living have better things to do than to continue hating the dead.
Sure, the zlib stuff has been fixed in *whatever the release will be called*.
;) This is only slashdot; if you tell us we can keep a secret!
You're really getting annoyed by all of the version number questions, aren't you?
In all seriousness, though, your presence here and the answers you provide are really appreciated by myself and probably many others. Thank you!
It's only software!
at least 2 products seem to object strongly to the 2.96 gcc (I remember reiserfs having a fit about 2.96; and I forget the other thing that didn't like 2.96, sorry)..
:)
Maybe that would be Mplayer. See here and here. From these links you'd think there's a little friction between the Mplayer guys and the Red Hat crew. Can't we all get along?
I don't understand what this 'binary incompatibility' is. Does this mean .solibs will need to be replaced?
*********
You are thinking C, but this is mostly in regard to C++. C++ does really nasty things to class/function/method names when it compiles. And, on top of that, there's no standard for it. Thus, in almost every release, GCC breaks binary C++ compatibility. I don't see why anyone even tries to dynamically link C++ - just statically link all C++ parts. However, others disagree.
Engineering and the Ultimate
does redhat have a dozen people all reading slashdot and answering questions with the same login
the real bero is probably still busy defending the choice to include gcc-2.96 on usenet
Agreed, and its a big deal to numerical types who use athlons. Our chem. dept. put together a cluster of dual 1.2 ghz athlon boards. Ran a test case using sandia labs MPQC (Massively Parallel Quantum Computing, GPLed by the way :-), comparing it to results from the prof.s single cpu 800 mhz athlon. The 800 mhz athlon kicked ass on the dual 1.2 ghz, until we researched the problems with later gcc and athlons, downloaded an older compiler, and recompiled MPQC. Then it rocked! Interested people might google for ATLAS (or take the ATLAS link after googling LAPACK).
This will delete any important system components installed / updated by Ximian, and is likely to break your system. Please moderate it down if possible.
The simplest way to use 7.2.92 is to upgrade, then reinstall Ximian GNOME like it says.
If you did want to get rid of Ximian GNOME, do it with apt-get, avaliable from freshrpms.net. This will make sure your system is always in a working state during the deinstallation process
I just looked at the RPMs in Skipjack. Seems like you decided not to include enlightenment (0.16) in the next release. Now, that's kinda disappointing. I know for sure there are still a lot of ppl still using it.
I hope you'll include it in the next release.
I was quite pleased with the gcc 2.96 release. I got to start using some C++ features that I've been wanting to use for a long time, but didn't work with the older compilers. I submitted a few bug reports, but recent versions have been stable as a rock for me.
Need a Python, C++, Unix, Linux develop
OpenOffice will be included when it's ready.
This means among other things that it must build without relying on proprietary crap like Sun JDK, and the resulting binaries must work.
We're trying to get it to build with gcj for the Java parts, but that doesn't work yet. No promises or estimates.
This message is provided under the terms outlined at http://www.bero.org/terms.html
Yes !!!
postfix-1.1.4-3.i386.rpm
vsftpd-1.0.1-4.i386.rpm
I must be dreaming, postfix and vsftp in the next redhat. I am going to upgrade my servers to 7.3 when it is ready. Yes, definitely, yes, going to upgrade ...
RFC1925