Interview with Debian Project Leader
brunotorres writes "I've interviewed Martin Michlmayr, Debian project leader. In this interview we talked about the upcoming Debian release, Sarge. An excerpt: 'We heard for years that Debian is hard to install and the old installer wasn't very easy to maintain or advance, so we we decided to throw the installer away and start from scratch. The new installer is much more modular, which makes it easier to maintain and extend.'" Reader ron_ivi points out that new Debian/Hurd CDs are available. Newsforge and Slashdot are both part of OSTG.
We heard for years that Debian is hard to install and the old installer wasn't very easy to maintain or advance, so we we decided to throw the installer away and start from scratch. The new installer is much more modular, which makes it easier to maintain and extend.
:)
heh, so if I'm reading this right, they know the old installer is hard to use, but they really don't care. The new one is easier to extend and maintain, and that's all that's important.
Mod me down with all of your hatred and your journey towards the dark side will be complete!
I've always thought there should be two versions of linux: bleeding edge, and ignorant housewife editions.
Red Hate falls squarely into the ignorant housewife category, where gentoo and LFS are for linux users with balls of steel.
Unless you can do source on the fly, I don't see the gentoo-type crowd getting excited over this.
Just my $.02 (that's $4.00 canadian)
http://www.ubuntulinux.org/ They will mail (snail) you 10 copies for free... The installer is nice and the desktop looks pretty damn good... Uptown (not an Ubuntu salesman) Joe
All the other architectures I tried (Suns, _old_ x86s, _new_ x86s) worked great.
I really reall really like the fact that the minimal install and the installer itself doesn't require the X-windows bloat.
Is Your Development Project a Sinking Ship?
So now, is HURD so unimportant to slashdot that news related to it is just grouped under some other news? The same slashdot that carries a front page story about even release candidates of the Linux kernel?
I'm looking forward to a Hurd LiveCD - I understand this is technically pretty complex but when it happens, trying out hurd will be simplified massively.
See what I've been reading.
The only time it gave me headaches was when I banged my head on the desk trying to seewhat type of chipset my ethernet card had, and what type of graphics card was inside the box.
As long as you know what type of hardware you have, debian is simple to install, and very easy to keep updated. I think most people just don't like to read the text on screen detailing exactly what's going on during the install.
Well, I wondered the same thing until I tried out Debian and realized you could do interesting things like downgrade packages to previous versions. In general, the install system had features Portage doesn't, until the next version of Portage anyway.
:)
That didn't stop me from happily moving to FreeBSD, however.
Wouldn't Viagra accomplish the same thing.
Sarge is great. When it becomes the new Stable, I may just switch from Testing to Stable.
See what I've been reading.
Why does each and every distribution need to reinvent the installer and the package management tools and the portage system and the system layout?
Can't we have just one installer, one package management tool and one portage system that is shared by all the linux distributions, the bsd variants, OS X fink, windows cygwin, the comercial vendors, and all the rest?
I mean really, reinventing a new tool to do something that people have been doing for 30 years is the height of arrogance. And even if they do invent their own package management system, does it only have to run with their own custom portage system? Can we have multiple interfaces to just one portage system that works across all posix systems?
Ideally I should be able to pop in a DVD, and have a single installer come up that lets me mix and match my kernel with my package management system and select what packages I want to install and then have it install them in a known location that is the same as everyone elses in the world.
I should be able to deploy a software package one time and just have it compile and install itself on any unix like system. And work.
All you separate distributions and operating systems need to get off your high horses and share the labor for things that are common between all of you. This is why we don't have unix on every desktop right now. The fragmentation is killing adoption of unix on the desktop.
IIRC, ubuntu uses the new debian-installer.
The problem with all installers (Fedora included) is that dependency tracking is extremely difficult and complex, and packages don't always accurately describe their dependencies. They also don't have any good way of handling multiple flavours of (essentially) the same product. They also don't talk with each other, so don't expect apt or rpm to know about anything you installed from CPAN or CPANPLUS, even though there's absolutely no reason why you couldn't have a program to rationalize the contents of different installer databases.
However, that is not the fault of Debian, but rather the fault of the problem being solved. It is extremely complex, and no good solution currently exists.
As a distribution, I like Debian a lot. No, that's not just because they included my FOLK patches as an alternative kernel (though that is a factor, because it means Debian is far more capable of including interesting ideas than almost any other distribution). Debian is simply a damn good distribution. It's comprehensive, it's consistant in approach, and it's been able to maintain a very high level of quality, despite having a very large number of contributors. (Or maybe because they do.)
There have been a lot of distributions, over the ages. Some have failed because the maintainers gave up (SLS, for example). Some failed because they appealed to too specialized an audience, so there wasn't a userbase to keep things going (QLinux is an example of that). Some failed because of political reasons (Stampede Linux got busted over a "trademark infringement" that pushed credibility a little far). Some failed because the maintainers went commercial (Red Hat Linux, I'm talking to you!).
Given that kind of turbulent history, it's impressive that Debian has done as well as it has. Those involved in the project should feel proud of themselves. IIRC, Slackware is the only other distro that has lasted as long, or atracted such a following.
It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
Why does it matter if the wheel is constantly re-invented? No one is forcing you to do the reinvention and you don't have to use the new wheels.
Freedom to tinker is a major part of the driving force behind free software at the moment. As for fragmentation "killing adoption of unix on the desktop" (assuming that you are including GNU/Linux with unix), there are more *nix systems on desktops now than there ever have been previously. Strength through diversity, etc.
flossie
Write now. Defend liberty
"I wouldn't recommend Debian on the desktop for people who are new to Linux, but it's perfectly suited for people who have some experience with Linux or have an admin who takes care of their machine."
I like the comment, though it's probably been said a thousand times before. I would say though, that it still takes SysAdmin-type powers to be comfortable with most Linux distros, at least in my experience. Everybody that I ever came across that said "use Linux, it's great" turned out to have a decent amount of tech knowledge and (it later turned out) had climbed the sometimes steep learning curve that goes with it. I went through/still am going through that same curve and finding it immensely enjoyable and rewarding - I'm even seeing people that would benefit from using Linux but the hoops you sometimes have to go through to even get a printer to work would fox these people. If I'd let it loose on em, it'd mean constant calls every day/week.
The comment made me think about this again, thats all. We're close I reckon, but not quite there...
Well, Debian and OS X Fink do share an install system - apt-get. "All the Linux distributions"? Would be nice, but there are a fair few .deb-based ones out there now. RedHat and Cygwin share a system I believe (I'm prepared to be corrected here), because Cygwin was originally has ties to RedHat.
Ideally I should be able to pop in a DVD, and have a single installer come up...
Ah, well you've lost me there already you see. A DVD? I run Debian on a old laptop that hasn't got a CD drive, let alone a DVD. I also run it on a Cobalt RaQ - not even a floppy drive there. A single installer? But on my flashy new hardware I like graphical installs, whereas I would spit blood at anything requiring a graphical install if I was trying to put it onto the Cobalt.
All you separate distributions and operating systems need to get off your high horses and share the labor for things that are common between all of you.
OK. So who gets off whose horse first? I know - let's dump RPM, I always hated it. But hold on, it's used with some of the most popular and commercially supported distros right? So I know, let's dump .deb, after all it's only minority. But hang on, some of the most stable distributions there are use .deb so there must be some merit in it. I know, let's dump RPM...and repeat ad nauseam.
Cheers,
Ian
Oh, you don't know anything about computers? Try our Ignorant Housewife edition. See, it's for stupid people - like you.
One of the things I've noticed of late with Debian is that their vaulted upgrade procedure between versions is definitely not working for Woody and Sarge.
/etc directory is a little much.
Upgrading from a fresh Woody install -- of 3.0r0, to be precise -- directly to Sarge as it now stands destroys Gnome completely. It will boot, start X11, but then die horribly for reasons I have yet to sort out fully. (I did this three weeks ago, for an old beater that was a gift) And it would die consistently only in that operating any Gnome application in tandem with another would do it.
The only way I could get the install procedure to update correctly was by using a sarge netinstall CD with a beta from August.
I believe the kernel versions changing has a lot to do with this. Of course, blaming Debian for this is not fair, but expecting users to suddenly know everything about the kernel version, the module loading/management procedure and the deep changes to the
I don't care about a GUI installer. I do care about Debian's stability between versions. I used to think Debian's upgrade process flawed (speed of releases) but essentially fine for those people who didn't want to think about dependency hell when using an online upgrading service. But now I am wondering if they really have it under control; I think they've taken policy as far as they can go.
They should commit to a regular timeframe for stable/server/stale versions and stick to it. Once a year is plenty of time.
========================================
Death will come, and will have your eyes
-- Pavese
Though just about anything, including poking one's eyes out with a sharp stick, would be better than the old Debian installer. I've been a hardcore Unix user/developer since 1982, and Linux since 1991, and yet I was completely baffled at some of the questions the old installer asked, and at the sheer number of questions.
It's nice to read an interview from a distro project member where the problems/limitations of the distro, (such as the long release cycle), are openly admitted. All too often distro maintainers (and users) make excuses for current limitations in their distros and stubbornly refuse to address them in a rational manner.
That's funny, because I just copied your very words into my KDE Klipper from Firefox then pasted them right into an OpenOffice document. And I'm running Debian Sarge/Sid!
Try the FUD, it's excellent today. May I suggest a full-bodied whine with that?
Knowledge is power. Knowledge shared is power multiplied.
As a side note, I'd really like to see someone try to do this with Windows. Upgrading from 95 to 98 to 2k to XP and replacing HDs, CPUs and MBs under that system, while not having to reinstall all your applications and redo all the settings.
If programs would be read like poetry, most programmers would be Vogons.
"Can't we have just one installer, one package management tool and one portage system that is shared by all the linux distributions, the bsd variants, OS X fink, windows cygwin, the comercial vendors, and all the rest?"
No.
You must be new here.
Taking what you are saying a step further, why can't we just have a single distro? No we can't. The different free distros cater for different needs. Gentoo is for putting together a distro from the source. Debian is a distro with virtually all the apps out there and with a lot of ways to install the packages and supports many architectures. Fedora is for new users and people who want the latest eye candy apps. The commercial distros like SuSE and Mandrake *can* be unified but they're just in it for the money and they wont do it. Try convincing them.
Now, why can't we have a single package management system/installation system? Same reasoning - different distros do different things. You can't have a single package management system for both pre-compiled and source code distros without putting extra overhead on one of them. Same thing goes for installation system. And commercial distros just won't do it. Again, try convincing them.
8700 packages for Debian GNU/Linux? Great. New installer? Nice. If I buy a small server, though, I can't even get a stable version that ships with SATA support. Debian may be a wonderful community project, but it is becoming too bloated to move forward like it used to.
Systemd: the PulseAudio of init systems
(after you've chosen a boot often such as "vanilla" or "bf24" and then selected a language)
/proc/pci
ALT+F2
cat
voila! Hardware devices (well, PCI/AGP anyhow).
heh, so if I'm reading this right, they know the old installer is hard to use
Well, indirectly, since the new installer isn't "easy". The "easy" route is picking from a list of a whopping 7 choices. Pick "Desktop Machine" if you are okay with KDE, GNOME, and several other WM's being installed, and lots of random cruft, OR you get to do "Manual Package Selection", and wade through Debian's 8000+ packages. Neither the 7-super-mega-package-selection, nor the Manual Package Selection, is an option for most sane people. The only way to do it really is just installing the base system, and proceed with a self-paced Gentoo-style bit-by-bit install using apt-get. The difference in time spent installing, for me, was statistically insignificant.
This isn't necessarily bad, some of us like putting together systems that way, but thats another story...
"NF: I think there should be framebuffer options in the installation boot prompt, something like choosing resolution. I had to type linux26 vga=791. Do you plan to put resolution options in the boot menu?
MM: Debian-installer works very well in the default resolution; putting in too many options would confuse users. You should use the command line option."
As much as I love Debian this is stupid.
It took me more than a week to figure out what was wrong with my laptop when I tried Potato! (look, it was my second linux installation and the first with debian and my laptop)
This is not helping newcomers!
I also fail to see why not supporting reiser4 (ok, ok, pleas dont flame, I will compile it myself, no big deal... I just tought that, ok Ill shut up)
So... at least two CDs for KDE/GNOME.
WTPOUAWYHTTOTWPA
What's the point of using acronyms when you have to type out the whole phrase anyways?
Now you will log into the system and enjoy it.
Yes, SIR! Appropriate for a release called 'sarge'.
Wah!
Debian:
"Stable". Apt-get is beautiful. jsut type in what you want ot get and you ahve it. Dependancies are always wonderful with this because it deals with it automaticly. The problem is if you use the stable package, be prepared to wait years for a new version of your software. I usually say testing for my install, so my things are relatively current, but not totally buggy. Not really for a total linux newbie, but if you are smart enough to understand basic computer things, you coudl get by.
Mandrake:
URMPI is like apt get, but from what I noticed, not with as many packages. Its my distro of choice at the moment. Things (NFS, SMB, SSH) just work, with minimal setup. If you are migrating, it's the best for that.
Redhat:
Good for enterprize. If you want basic office stuff, this is the distro for oyu. If yu want something any more then what is already on the disk, be prepared for dependancy issues (I knwo there is apt-get, but package selection is limited). Circular dependantcies are a pain in the ass (you want to install A, but can't because oyu need B, but you can't install B because oyu need C, and you can't install C, becasue you need A)
Something else:
Lycoris is another "mirgration" type of linux. The install even has a solitarie game for oyu to play while you wait. It's all dumbed down...I found that to be very limiting.
Slackware was my "first" distro when I was a linux virgin..and I sure promise yo if oyu make that your first distro, you will feel like a virgin. Pain in the ass. I lost many harddrives due to it. Lucky for me, the drives were small 500MBish drives on a 486.
KNoppix. TRy it first. If you can familiarize yourself with knoppix, it helps reduce the risk to your system from a bad install, and you can muck around with it without killing anything important.
Gentoo. Ricer jokes aside, it's a good distro if oyu need a special custom configuration...say if oyu have a 64 bit processor or something, otherwise, be prepared to spend hours and hours compiling linux. (I haven't used Gentoo, but this is what I heard).
There are other distros out there, you will probably install linux several times before oyu find the one that works for you.
http://distrowatch.com/ has a more complete list of distros.
-------
Support Indy Music. Buy
An example:
Here we have the typical video driver selection screen. Can you seriously expect anyone who wasn't weaned with a transistorized soother to understand this screen?
Who but the eternal geek will know that VESA is only used for ancient systems or vmware, or that trident means the old, ancient trident chipset, and probably not the one that could show up in their laptop? - actually I don't even know myself on this one. I'd just have to try a bunch of installs to see, something a user should not have to do.
A little description beside each cryptic 4-5 letter identifier would be EXTREMELY helpful here.
Better yet would be some kind of auto-detection mechanism for the most common modern cards like other distros do.
Debian is not the only offender in this category.
Here's my favorite:
This is priceless.
What the hell is Simple, or Medium, or Advanced? Who's going to know what method will get their windowing environment working properly? (and really, that's all the user wants anyway)
Debian seriously needs a real user-interface designer to do their installer. So long as it's done by geeks, it will continue to be useable only by geeks. The folks at debian are assuming too much arcane knowledge upon their users, and because of that, they will continue to alienate the majority of users right from the outset.
Haha, that was funny. And true. A friend of mine who used mandrake for a few days went on to install gentoo, for rumour had it that if you can install it, you'll learn a lot about the system.
Spent hours and hours installing it, (which doesn't make too much sense - why not have a functioning system in 5 minutes and then rebuild everything?), installation documentation in his lap, and after a while he managed to install it. Took another day to get alsa working (couldn't help him, I myself was confused by it). Anyway, in a few days, he had a working system with X (and without working kpdf, for he missed a use-flag apparently). And I spent the next few weeks explaining the most trivial things I could learned reading the Introduction to Linux guide on my two-hour trip home on a train. Apparently, my friend didn't buy into the "I'm now a geek cause I installed gentoo" myth, and was very very frustrated. Finally, I dug up the excellent Machtelt Garrels guide (still the best in linuxland for newbies I think) and I lent it to him.
(Then later he switched back to Win2000, and just upgraded to XP recently).
http://www.ubuntulinux.org/ They will mail (snail) you 10 copies for free... The installer is nice and the desktop looks pretty damn good... Uptown (not an Ubuntu salesman) Joe nopes, not anymore.. Though you can still download cd isos from:http://www.ubuntulinux.org/download/ their download page.
... Disclaimer: I barely know how to Read, please dont expect me to spell right!
You have it backwards; Viagra helps you extend and maintain, not maintain and extend.
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
He displayed a genuine interest in linux, and I encouraged him to try gentoo (myself already using a ports based "distro"). And later seeing his frustrations, I realized my mistake. I think one of the most important things if you want to get someone on the linux/unix train is documentation. Which is almost there in gentoo, but not quite. The other is: a clear system layout. Debian comes close to it (I might try sarge when it comes out, just to keep my linux skills honed - not long ago I couldn't make usb flash drive work in SuSE, and I felt really embarrassed), but I still didn't know what mplayer.conf does in /etc (or .operarc for that matter).
So my recent method of getting people trying out linux (or freebsd) is to give them a book. I would say: don't touch anything on your computer. Read this or that, and if you are still interested, and enjoyed your reading (because you'll have to do a lot of reading later as well), than you can go on following installation instruction. One important note: never give docs in electronic format. It is easier to grasp the basic concepts if in book form, and (strange as it may sound) without sitting in the front of a puter. And then I would recommend a kind of distro you mentioned: it might be gentoo or debian or slackware, it doesn't really matter (as long as it's not rh or mandrake)
Anyway, for nostalgia's sake, I dug up some of my friend's posts on gentooforums. Note the growing use-flag paranoia (and I refer back to the above post in a post below, just for recursivity's sake. :)
Why does each and every distribution need to reinvent the installer and the package management tools and the portage system and the system layout?
Debian is "reinventing" the installer, because it needed to be. The Debian project needed an installer that could be run on any of the dozen or so architectures it supports. Not only that, but they did an excellent job of separating the installer from the frontend it uses. Now that the installer is near completion, it shouldn't be hard to create a GUI frontend to the install scripts.
Not to mention, your question can be answered with the same answer that is used to argue why we shouldn't all just use one operating system, one brand of processor, and one computer manufacturer.
No comment.
Go with Ubuntu. It's Debian based. Very easy to install and use. Check it out at http://www.ubuntulinux.org.
RedHat and Cygwin share a system I believe (I'm prepared to be corrected here), because Cygwin was originally has ties to RedHat.
Ok. Cygwin has the *worst* package management ever, but one of the best front-ends. Go figure.
A package in Cygwin is a tarball, basically run from /. So you can download a Cygwin package with, say, your web browser, cd / in your cygwin install, tar -xzvf *thefile*, and that installs it. It's crap, it's nothing but crap. Dependency resolution? Don't know how they do it, really, unless the database they use to store packages also contains dependency information.
RPM, on the other hand, stores dependency information and some other useful metadata in the package itself. So theoretically an rpm *can* be installed on a non-rpm-based distribution, provided the rpm program (a perl script, of all things) is available, as well as the other tools needed (tar, a few others). Practically, it doesn't work out so well, and I wouldn't really try ot install an rpm into a non-rpm-based system, and there's even incompatibility between rpm-based systems, but it's not the fault of the package manager, it's the fault of the fools that arranged the system in incompatible ways, and for what? Vendor lock-in? Anyway, the problems come in with some of the optional flags. Some rpms can be installed anywhere if you pass a flag to rpm, but some rpms (anything built by Mandrake, one of my pet peeves with them) *must* be installed where they specify. Furthermore, some package maintainers specify specific versions of dependencies that they really don't need to specify, making it so that their package can only install on a narrow range of distributions that came out when that particular dependency was standard at that version. Luckily, most package maintainers don't do that, myself for example. When I put dependencies on pyAlarm, I just specified "pyao" and "pymad", no versions. So it would install if you had them, or if you used urpmi you could install the dependencies too, and it worked fine. (Granted, there were no doubt numerous bugs on numerous other systems that I never heard about, the new system in pyAlarm's much better, because it does its own dependency checking at runtime, but that's not an optimal solution for every program)
Anyway, Cygwin wasn't developed by RedHat. It was developed by someone else (I forget who), and RedHat acquired them. So now Cygwin is owned by RedHat, where previously it wasn't.
Like what I said? You might like my music
KDE 3.3.1 had just made the Sarge mirrors. I doubt they'd pull it out and go back to 3.2.3 for release.