Fedora 10 Released

ekimd writes "Fedora 10, aka 'Cambridge,' was released today. Some of the major features include: 'wireless connection sharing enables ad hoc network sharing, better setup and use of printers through improved management tools, virtualization storage provisioning for local and remote connections now simplified, SecTool is a new security audit and intrusion detection system.' Versions of major software include: Gnome 2.24, Eclipse 3.4 and RPM 4.6. A features list can be found here." Reader Nate2 suggests LinuxFormat's detailed look at the new release, and adds a few more details about the software it contains: the release includes "a new graphical boot-up sequence, OpenOffice.org 3, many improvements to sound support via PulseAudio and other updates."

Comments

Breaking the law is always easy

[betterunixthanunix]

The fun thing about using Ubuntu is that Canonical does not have any concerns about the laws of the United States of America. Red Hat does, because unlike Canonical, Red Hat is an American corporation. Red Hat cannot ship any software that could violate patent or copyright law, and many of the codecs in the non-free repositories do violate those laws. If you do not like the consequences of those laws, then:

1. Let your congressman know that, unless he at least attempts to undo those laws, you will stop voting for him.
2. Join the campaign to repeal those laws
3. Use free codecs and demand that people send you media that is free-libre

Re:They are using RPM 4.6.0 release candidate

[prefect42]

I think you hit it right on the head. Fedora can do this, because that's what it's for. It avoids getting trapped behind painful changes because of worries that it'll cause short term pain.

Fedora should be all about long term gain, and if RPM 4.6 is a little bit experimental, great. Let's get the bugs out in the open and sort it out.

Re:Will it fix the most notorious Linux bug??

[beav007]

I think you've misspelled "Windows NT" as "Linux".

This bug actually applies to Win 9x, rather than to NT[1]. I'm led to believe that the reason is that MS used an int as a millisecond counter in VMM[2]. At 49.7* days, the int wraps, and Windows panics.

The bug was not discovered until 1999. Reportedly, that's how long it took for someone to convince Microsoft that they actually managed to keep Windows up for 49.7 days.

* Yes, the number is 49.7, not 47.9.

[1] Windows may crash after 49.7 days[3]
[2] Windows crash after 49.7 days, Automatically... Do you know?
[3] That's right: it's cited, bitches!