Slashdot Mirror
RedHat "Fisher" 7.1 Beta Out Now
Cranky Spice (and everyone, and everyone's brother) writes: "Get it here: ftp://ftp.redhat.com/pub/redhat/beta/fisher
They've moved to mainstream the 2.4 kernel (surprise),
there's an IA64 set of .iso files, the installer can wizard you up
a basic firewall config, all the usual minor tweaks and enhancements. Though they say PCMCIA support is still flaky, meaning my VAIO Z505 slimline might not be running Fisher anytime soon. :/" The flood will only increase now -- even PocketLinux was demonstrating 2.4 on their iPAQs today at LinuxWorld.
Fisher, is it is *STILL BETA* is only available on a few mirrors, those of which are:a /fisher
/ fisher
a /fisher
s /redhat/redhat/beta/fisher
/ redhat/redhat/beta/fisher
Indiana, USA:
http://csociety-ftp.ecn.purdue.edu/pub/redhat/bet
ftp://csociety-ftp.ecn.purdue.edu/pub/redhat/beta
Minnesota, USA:
ftp://ftp.mn-linux.org/linux/redhat/beta/fisher
Buffalo, New York, USA:
ftp://ftp.cse.buffalo.edu/mirror/Linux/redhat/bet
Pennsylvania, USA:
http://carroll.cac.psu.edu/pub/linux/distribution
ftp://carroll.cac.psu.edu/pub/linux/distributions
rsync://carroll.cac.psu.edu/redhat-beta/fisher
Anyone going to use Fisher should of course, goto Bugzilla.redhat.com and give plenty of bug reports and other issues while using this beta version of RedHat.
Linux: Because a PC is a terrible thing to waste.
James Brents
Because most of us think ext3 will be the better choice, and we are putting some effort into that.
One of the main advantages of ext3 is that it can use ext2's already very advanced userland recovery
tools - if something goes wrong that can't be fixed with a simple replay, ext3 won't be in much trouble. Add the fact that you can simply update
ext2->ext3, and you know some (not all) of the
main arguments for this.
But when reiserfs stabilizes, there's no reason not to have 2 (or more, with XFS, JFS, tux2 and all coming along) choices.
This message is provided under the terms outlined at http://www.bero.org/terms.html
- A.P.
--
* CmdrTaco is an idiot.
"Remember when the U.S. had a drug problem, and then we declared a War On Drugs, and now you can't buy drugs anymore?"
...late at night, Searching for Beta Fisher...
*sigh*
Hasn't it been proven enough yet that GCC 2.9.6 + the latest patches is by far the most standardized and bug free version of GCC yet?
Bero from Red Hat, among a few others, have beaten this to a pulp. The only people with problems are those who have written code that takes advantage of old GCC bugs!
And we won't have real binary compatibility until GCC 3 comes out. So why not have the best we can have now?
There are many reasons why this decision was right:
If you have any objections to the compiler, report the problems you are seeing rather than complaining without having tried it, the way many people seem to do lately.
This message is provided under the terms outlined at http://www.bero.org/terms.html
It's not integrated in the install (yet), but the kernel modules and userspace tools are included.
This is because we don't consider it stable enough for real production use at this time (though it's slowly starting to get there). Right now, it works quite reliably (unless you're NFS-exporting it) as long as everything can be fixed with journal replays.
If you're using reiserfs and you have a hardware or driver problem leading to a corruption that can't be fixed by a simple replay, you're pretty much on your own. ext2/ext3 can recover from some of this.
This message is provided under the terms outlined at http://www.bero.org/terms.html
No exact numbers, but there will be a performance gain because of kernel 2.4, more glibc optimizations, and some compiler patches improving code quality and optimizations.
Since we're using the compiler to compile the distribution, the compiler patches affect you even if you are not a developer.
This message is provided under the terms outlined at http://www.bero.org/terms.html
It works - so does the version from 7.0 updates.
Simply run "up2date -l" or go ftp://ftp.redhat.com/pub/redhat/updates/
This message is provided under the terms outlined at http://www.bero.org/terms.html
RedHat name evolution: (Most of this is stolen from this post)
... Any other guesses?
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
7.0 - Guinness - Beer (Guinness is a stout, Pinstripe is an ale)
beta - Fisher - Star Wars actors
7.1 - ? - ?
Maybe 7.1 final release will be named after a chess player
Cheers,
IT
Power corrupts. PowerPoint corrupts absolutely.
s/broken/great/
I don't think anyone who has actually tried one of the later gcc 2.96 releases (>= -69, the version from 7.0 updates) would call it broken.
If you have any actual issues with it, report them at bugzilla.
If you don't, don't call it broken.
This message is provided under the terms outlined at http://www.bero.org/terms.html
Our release schedule was ready quite a while before we knew when 2.4.0 would be released, so no, 2.4 doesn't create a rush to ship.
What do you mean by "more compliance with standards"? I guess you're talking about the compiler, in which case you actually mean "less compliance with standards" - 2.96 is the first gcc version that is fully ISO C99 and almost-fully ISO C++98 compliant.
This message is provided under the terms outlined at http://www.bero.org/terms.html
The beta is not intended to be used in a production environment.
Including prereleases IN A BETA makes perfect sense if we have reason to believe that the final will be out in time for our final or the version officially designated as beta is actually at least as stable as the latest version released as stable (tar and fileutils are perfect examples of the latter.)
The purpose of a beta release is to get bug reports and figure out what needs to be changed.
We don't have much of a use for, say, bug reports on KDE 2.0.1 if we know for sure we'll be shipping 2.1 (which has a lot of bugfixes [and probably also some new bugs]) in the final - we'd rather help the release we intend to ship to stabilize.
This message is provided under the terms outlined at http://www.bero.org/terms.html
On a related note, we've patched timidity++ and xmms to support the aRts (KDE sound system) backend [the release notes don't mention this, it's in the "not really major changes" category].
This message is provided under the terms outlined at http://www.bero.org/terms.html
You guys have been shipping the patches you've been making to correct the code and get stuff to compile with 2.96 back to the original authors of the software, correct?
Sure. Most of them have added the patches to their current versions. For example, the current KDE CVS tree compiles without any problems (KDE is a good example because it's C++ - and C++ is much stricter than C about many things).
There are some (few) other maintainers who didn't like the patches because they considered them to be workarounds for a "broken" compiler - there's nothing we can do about those, except for waiting for them to realize it's not the case when gcc 3.0 is released.
This message is provided under the terms outlined at http://www.bero.org/terms.html
2.96 can compile 2.4.x kernels and is used to compile kernels.
kgcc remains there for people who want to use 2.2.x kernels. (gcc 2.96 not being able to compile kernel 2.2.x is a kernel issue, not a gcc issue).
This message is provided under the terms outlined at http://www.bero.org/terms.html
I'm hoping that that option shows up soon. It would make it a great deal easier to use ReiserFS
"I object to doing things that computers can do." -- Olin Shivers, lispers.org