Debian And The Rise of Linux
There's an article in this month's LinMagAu that asks a question about how the rise of Linux will impact Debian and what that could mean. Good article, especially interesting if you have been a fan of Debian.
← Back to Stories (view on slashdot.org)
This is a self-fullfilling prophecy, and to change this will take quite a major change from the existing Debian (fairly elitist) culture.
Where Debian will shine is not nessicarily as a mainstream distro itself, but as the basis of systems that are more widely used, such as Xandros and Knoppix. Is this a bad thing?
It does run the risk that Debian-as-distro/brand become marginalised, but all that needs to happen for the Debian project to stay healthy is that Debian-as-underlying-system is widespread.
This said, my Ideal World(tm) is every man and his dog running Deb... ;)
"To any truly impartial person, it would be obvious that I am right."
WARNING : THIS IS NOT A FLAMEBAIT. I LOVE DEBIAN, BUT READ ON ...
I started using Linux with SlackWare when it was the only distro available out there. I used to love them tarballs, but then at the time systems still had manageable sizes, so one really could compile everything in a reasonable time.
Then I had the (mis?)fortune of being hired by a certain Caldera spinoff and was forced to use OpenLinux 1.2. That was my first contact with RPM, and that was a painful contact. Part of my work also involved writing and maintaining specfiles for various cross-platform packages. That's when I learned that (1) RPM was better than tarballs because it had dependencies, (2) RPM dependencies are not powerful enough and (3) RPM isn't backward-compatible. In short, RPM is not good but it's better than nothing.
At that company, I also had the misfortune of meeting a Debian fanatic. Note that I say he's a fanatic of Debian, not that Debian made him a fanatic. Having tried Debian long ago myself, when it wasn't ready for prime-time, and having found it complicated and messy at the time, I was conforted in this idea by the truly detestable way this guy was patronizing everybody who didn't use Debian, and was turned off Debian for another 2 years.
Then, several months ago, it was a sunday afternoon, my local computer shop was closed, and I couldn't find my RH CD to reinstall my box. I though : what the hell, I'm no more stupid than the average Debian user and I have nothing to do, let's try the Debian network-install. Well, I went through a little pain (it's not quite totally polished yet), but I've never looked back. dpkg and apt-get are just a godsend, and I too am now a convert today.
Moral of the story : I avoided using Debian for several years entirely due to the advocacy of one (well, several actually) Debian bigot. You can always say that I should have been more intelligent and I should have made my own opinion, but I never had time and the experience you get from other users do count for me.
In conclusion : what's the biggest good that could happen to Debian ? that other distros' package management got better so Debian bigots wouldn't have such an powerful incentive to behave like asses and disgust other people of Debian before they even try it. Or better still, that the Debian bigots start realizing that they won't win anybody to Debian by being patronizing.
"A door is what a dog is perpetually on the wrong side of" - Ogden Nash
Why I like Debian:
(1) Serious philosophical principles. The only people to say GNU/Linux with a straight face. People concerned with my liberty above all else.
(2) No Prepackaged Experience. I run Fluxbox, Gnome-Terminal, Mozilla, and Konqueror, and have a proper GTK/KDE library environment. It all works the way I want it.
(3) The system state is transactional. Glitz is antithetical to transactionality. Glitz hides transactions. I like transactions.
(4) No waiting forever to compile stuff pointlessly.
#1 is the crucial element. Liberty is paramount.
I don't think Debian is going to collapse soon, But I do agree the installer could use some rethinking. Things I would like to see included: System recovery (using distributed backups over the lan), hardware autodetection, an installation blog - or something like that where you can put your installation remarks/choices, etc. Also, I'm looking for a command that would backup all config files that have been changed, or all files not managed by apt.
Also, if there were a central repository for those installation blogs, developers could easily see where most of the problems arise.. Just some random thoughts..
"It's too bad that stupidity isn't painful." - Anton LaVey