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."
It's never been difficult to add Dag and Livna, but it's now even easier: http://rpmfusion.org/ I really liked the polish of Fedora 9, it was a huge step up from 8. Hopefully Fedora 10 continues in that direction.
The wheel is turning, but the hamster is dead.
Palm trees and 8
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.
jh
Cutting edge, baby! (Why are standard components taking this long to get written?)
I've always found yum to use a ridiculous amount of resources on my setups. Whenever I install something on my tiny P4 server it will drain so much memory that the computer can't do anything else at the same time. I had a copy of debian on it in the past and I could run apt upgrades and still work in another terminal just fine. Yum does have some pros over apt but they sure aren't speed and efficiency.
Fedora and Ubuntu are aimed at different audiences and/or "market" segments. Ubuntu is a great "just works" distro, whereas Fedora is much nicer for tweakers.
Both have little things the other lacks, or work slightly differently in some ways.
I say use the one you prefer.
Try upgrading to the latest 9.04 alpha if you're not using it on a critical box. KDE4.1 has been much improved (might even be 4.2... dunno), but there are still lots of random broken packages and such.
That said, KDE4.1 is definitely the issue with Kubuntu. It's still not mature, though it is "stable".
My blog. Good stuff (when I remember to update it). Read it.
Xen as a dom0 is in fact losing favor in the Red Hat world. There are technologies being developed that will allow a KVM host to run Xen guests. It's called "xenner" http://kraxel.fedorapeople.org/xenner/ and is coming along nicely, but not super stable yet.
Virtualization is important to Red Hat, and given how much of Red Hat Enterprise Linux 5 was focused around virtualization, there is little doubt that existing deployments on Xen won't have a migration path to what RHEL 6 offers. Red Hat hedged their bets by using lib-virt as the api for everything, so that they could change the underlying virt technology without breaking software.
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!
I seriously hope nobody is shipping RPMs with more than 2 GB of executable code, but many applications ship with gigabytes worth of templates, samples, artwork, models, benchmark data sets, maps, etc. Even if you break the contents of an installation DVD into functionally distinct subpackages, you can easily end up with a dozen libraries that are a few hundred KB, a few distinct applications that are tens of megabytes each, and few GB of application data that can't logically be split any further.
There's no failure quite as dissatisfying as a complete and total solution to the wrong problem.