Linked by Adam S on Mon 22nd Sep 2003 18:28 UTC, submitted by Robert Renling
"Red Hat and Fedora Linux are pleased to announce an alignment of their mutually complementary core proficiencies leveraging them synergistically in the creation of the Fedora Project, a paradigm shift for Linux technology development and rolling early deployment models." Read more at Fedora Linux's site.
Permalink for comment
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
What I don't get, is people having beef with RPM. I am VERY sure that more than half the people out there that complain about it, have never really used it.
Installing redhat, and trying to install ONE package, and having it fail on you, so you move distros, doesn't qualify you for an opinion. Use your brain, and get apt, or the dependencies.
Um, some of us _have_ used both Redhat and Mandrake have good reason to loathe RPM (at least before the dependency resolving tools). Here's a fun situation I've had before:
- try to install (say) GAIM, but it requires a newer version of GTK than the distro ships with.
- no prob, download newer version of GTK and rpm -ivh it.
- der, GTK won't install because some other app depends on the older version of it specifically
It's like tail-chasing and whack-a-mole combined!
Another point is ease of use. Drivers? People say that 'modprobe <drivername>' is difficult. Oh, really? What about all the times I've had to install drivers for my friends, cause Windows XP just wouldn't do it right. Or the number of times I've had to do it for myself. Windows is easy when it comes preinstalled, alright. But there is *no* way to keep the difficulties away from the user. No OS has done this. Not even the legendary OSX.
I would say BeOS did/does (with the caveat being "on supported hardware"). Installing a driver on BeOS was usually a matter of downloading the archive, unzipping it, and then it could be as simple as the driver binary and a symlink to the directory it goes in named something like "drop [binary filename] here and restart networking/media/etc". And it was almost too automatic when it came to adding a piece of hardware that you already had a driver for. I stuck a BT 878 capture card in my PC and the only indication that it was detected and supported was that tv apps now worked and there were settings for it in the media prefs.
And of course there's the oft-repeated anecdote of a BeOS user taking a drive from one machine, putting it in another, and watching it boot no complaint, no "windows protection fault", not even much of a noticeable delay in the bootup time. I believe you can do this with MacOS 8-9, dunno about X. However, that's significantly easier to do on a mostly homogenous platform like Apples than it is to do on the range of hardware configurations that BeOS can run on. Windows 9x can do it, contrary to popular belief, but it's not nearly as painless. You usually have to start in safe mode first (or you get win protection fault error), then restart and feed it drivers from the windows CD for 5-10 minutes. Haven't tried with 2k/XP, but I've been told you have to delete the hardware portion of the registry to force it to re-detect hardware in the new machine.
While the limited range of supported hardware that BeOS supports can be frustrating, I think it should at least serve as a lesson to other OSes when it comes to the way it handles drivers and hardware detection.