First Look at Debian's Next Generation Installer
An anonymous reader writes "Over at LinMagAu There is an interesting look at the new beta version of the Next Gerneration Debian Installer. Putting aside the fuss around Ian Murdock, Progeny and Anaconda, this is how Debian is constructing the future of what is known to be it's Achilles heel. It's a well done beginning." While still not a graphical installer (and the article does a good job of explaining why that's not a priority) the installer now autodetects hardware, streamlining module selection, which was previously one of the more confusing parts of the install for newbies.
Hardware auto-detection is pretty much a requirement for any modern operating system. I remember having to set up all my hardware back in the day, and it's not an experience I'd like to repeat.
Javascript + Nintendo DSi = DSiCade
I don't really care about a pretty install, I'm just glad they finally got hardware detection.
I wonder why isn't it not yet graphical? Any reasons at all?
While still not a graphical installer (and the article does a good job of explaining why that's not a priority)...
Who ever said we needed a graphical installer? There is absolutly nothing wrong with a good text installer. And for installing small footprint it's always best.
And besides, this is the logical progression. First you do the text installer, then you move on to a graphical installer if you so desire. Not the other way around.
Really, I know what I'm doing...Ohhhh, look at the shiny buttons!
Why does it silently switch to Dvorak when you select diff languages?
"If you select "English (USA)" you'll be safe, but be warned that if you choose "English (Australia)" or "English (United Kingdom)" your keyboard will switch to the Dvorak layout! Not quite what most people expect."
Be warned, though, there is a big catch here: some of the language options don't default to a Qwerty layout! In the past you were asked what keyboard layout to use but now it just makes a guess based on the language setting. If you select "English (USA)" you'll be safe, but be warned that if you choose "English (Australia)" or "English (United Kingdom)" your keyboard will switch to the Dvorak layout! Not quite what most people expect.
Yeah, cause everybody knows those crazy Aussies all use Dvorak...
Come on, guys - it's only one extra question, OK? Just add it in there. It'll save you a lot of grief later on.
im willing to bet that in soviet russia....you still have trouble installing debian.
By and large, language is a tool for concealing the truth. -- George Carlin
It looks like Anaconda 0.0.2!! I'm not one of those that demands a GUI installer but, surely they can put together an ncurses app that looks better and less confusing that this abomination? This installer is crude to say the very least.
A good installer for a vanilla desktop user would take advantage of all the hardware on their system. It should detect your sound card, and then play a sound that says "hey, we found your sound card!" and it should let you use your USB mouse, show all this stuff on your display in such a fashion that acknowledges the existence of the video card, etc.
Basically, it should be more like Knoppix.
Now, I wouldn't want to lock the user, who may not be a vanilla desktop user and may not even have a mouse or video card on the machine, into this setup, but it sure would be nice to have the option, wouldn't it?
Knoppix is wonderful and all, but it leaves behind some artifacts of the live CD setup that can make package upgrades (which users ought to be able to do graphically, and with little pain) very painful. If we could get stuff like this in the base Debian distribution, we'd be a lot closer to Debian being sufficiently user-friendly that we could hand a disc to grandma without fear.
*prepares for the "get redhat" flames*
WARNING: there is a trojan on your
How about getting someone who has done some human-computer interaction work, or even joe doe from the street, to go trough the install screens and say "no" to the Debian developers. Really, a screen for configuring dvorak or a zillion other layouts, hmm.... "No, let's drop that".
Really, this work seems to bring the Debian installer up to around Red Hat 7 functionality. Can I do FTP installs? How about over VNC? 1 CDR, then FTP for rest of the discs? Does it look nice?
So Anaconda doesn't work on 11 architectures. That's a pretty crappy reason for holding the dominant arch down. Debian needs to take an attitude like Linus has to the archs and the Linux kernel; if some some arch can't keep it up with x86, though shit, maybe the next version will work better (if you submit the patches in time).
Personally, I've never had good luck with Debian. I know lots of people love it, and bully for them, but I have never been able to get a Debian system up and running to my satisfaction. I believed this was a personal failure until I succeeded two times with Gentoo, which is to Debian as Alaska is to Montana, in terms of frontier cred. Anyway, I agree that things that are dumb about the Debian installer could be improved, but I'm still a little worried that an installer my mama could run isn't right around the corner...
As everyone knows, Debian is maintained by an organization of volunteers. When people working on the distribution support users, it takes away from the time that they could be spending to improve the distribution. Therefore, it makes sense for them to not make Debian open for anybody to install. If someone can't make it through an installer that requires some attention and knowledge on the part of the user, then they should probably be using a commercial distribution that offers support for money or whatever. That's one of the things I like best about Gentoo's root shell installer. It immediately gets rid of people that are intimidated by that sort of thing, and prevents them from sucking up tons of attention on mailing lists or forums. The difficulty of the installer should be like those little signs in front of rides at amusement parks: "You must be this tall to ride."
The target audience of Debian doesn't need a graphical installer, so there's really no reason to put one in. If you want the easy graphical installer, perhaps you should ask yourself why you chose Debian in the first place. Besides, with distributions like Debian and Gentoo, using the installer is more likely than not a one time thing, because you can upgrade the version of your operating system without bothering with the installer. I'm all for installer improvements that save time for the core users of a distribution, but revising the installer to open the distribution to a new class of users should not be entered into lightly
I prefer to go through the difficult installation process Debian is known for - I know what hardware I have and can update drivers in the kernel if necessary, manually. So has does an installer perform? How about detecting a p4p800 deluxe motherboard with a 3com 3C940 nic? Unfortunately not. The disadvantage with installer is that users generally become lazy because of the very nature of an installer. It's purpose is to automatically detect a user's hardware - if it does not, then a user will likely give up and not naturally, say, update a drive in the kernel.
"There ought to be limits to freedom"
the Next Gerneration Debian Installer.
/. move to a new generation of editors who can spell? Or at least, give Cmdr Taco a spell checker?
When will
just few weeks(2? or something) ago when i installed debian on the machine sitting next to this. to be frank apart from the bootup screen i didn't see anything new in it compared to my memories of the previous installers, except maybe some minor differences. it's been easy enough for years if you figure out the fact that most of the time you really want to do a netinstall and not install from the cd's. the package selecting might be the problem,though imho dselect isn't that bad if you'd just take time to read through the keystrokes just even once and don't bash the keyboard mindlessly(no offence to the one's that do.. but that's not really a way to get anything done ever on any system).
btw. synergy rooooocks for mouse sharing..
world was created 5 seconds before this post as it is.
Is it really necessary?
I mean, once you install a "server" operating system using a generic kernel, then go and recompile the kernel to include support for whatever hardware you have in your server.
What exactly is the purpose of hardware detection in this case? You won't be using X11, USB, or any of that stuff that needs to be "detected" on a server, and by installing Linux in the first place you accept the responsibility that you know what you are doing.
Or is this no longer the case?
Wel, its stil along of completing this installer i gues.
;-). Partinioning is stil hell, because it fails to detect again. Funny little installer this is. Even slackware works better.
;-).
Last time i used it was trying to install debian on a compaq server. I tried it 6 times (and 6 times a reboot) and it completely failed to detect the raid-5 controller, network seemed to work at first. Then when trying to instal software via ftp it did not work
But i like debian. Hope they fix the stuf soon. Its rock sollid (stable version that is). And i think that since redhat has gone the way of the dodo debian needs/deserves al the support it can get.
Come one peeps, lets make debian the best GNU/linux there is
Yours truely,
Debian and slackware lover....
what the hell is a "gerneration"?
I don't want to be a troll, but I thought the whole idea about open source is you can copy from each other and not reinvent the wheel. If Mandrake has a really good hardware detection, then why are these dudes writing something from scratch?
10 ?"Hello World" life was simple then
I don't really see the logic. Linux in general used to get beat up severly because of installation difficulties. Over the years many distros heard these complaints and addressed them by developing better and better installers. Today, there are numerous distros available that have such excellent installers that installation is a moot topic, except for Debian, Slack and Gentoo.
Most, if not all, of these better installers are open source GPLed programs. It seems to me that "logical progression" would be Debian taking one or many of these better installers and adapting them to Debian. Instead they choose to reinvent the wheel and have produced a crude installer whose interface was passe years ago. Where is the logic?
Someday someone who knows how to program a gui installer will join the debian project until then they'll just make neat excuses about why gui installers are not leet.
Forgot to mention that i used one of the 'Official "testing" images'.
Thanks...
it works, if you stick with woody, it's pretty much a "hit enter" proposition. It's not as good as libranet or knoppix/gnoppix/morphix. But given the "Debian Mindset" it is a step forward.
~corporate tool, but employed~
If these magazines are in trouble, its because they are asking WAY more than they are worth. For the content level currently in each issue, $3.50 max. The idea is, you make enough money to keep afloat long enough to get the advertizing. Then you maximize readership by lowering prices and make your money off advertizing. Thats not a difficult concept. Look at Woman's Day, and Family Circle: $1.50. They are the most popular magazines in America. Learn something from them.
Sorry if this was OT. It had to be said.
Drop me a line at:
Key ID: 0x54D1D809
On the package selection side, it would be nice to see some change. tasksel is decent enough for a very basic user, but for individual packet selection I find aptitude *a lot* more intuitive and, well, generally shiny, than I suspect dselect will ever be.
First Look: Next-Generation Debian Installer
The Debian installer has been considered its Achilles heel for a long time, but in the last couple of months things have really been heating up in Debian-installer-land. Ian Murdock recently announced to the Debian project that Progeny, the Debian-based distro that created the Progeny Graphical Installer, was dropping PGI in favour of porting Red Hat's Anaconda installer to Debian. But things haven't been sitting still within Debian itself either, with frantic work over the last couple of months to get the next-generation Debian Installer to the point where Sarge (Debian 3.1) can be released.
A Debian-Installer Debcamp in Germany in September saw many of the core developers get together for several days of intensive coding, with the result that Beta 1 of the new installer is now ready for the world to come and gawk, and poke, and kick the tyres, and even take it for a spin around the block. It's still changing on a daily basis but the developers want as many people as possible to give it a whirl and report back any problems they have.
So, for your edutainment and complete with pretty pictures, I present to you this first look at the next-generation Debian Installer.
Installer Rationale
To understand some of the design decisions that have been made with respect to the installer and why it's taken so long to get to this point, it's important to know a little about the Debian project itself. For many people this section will be rehashing old ground so if you just want to get to the guts of it skip ahead now to the next section, "Getting The Installer".
The long and the short of it is that Debian is committed to supporting multiple processor architectures. It's famous for being the most broadly deployable Linux distro (and possibly operating system) in existence, running on at least 11 distinct architectures. Nobody has more expertise in porting software to different platforms than the Debian project.
While that causes some problems when distributing normal user-space software, they're difficulties that can be worked around: for example, a package written in C needs to compile on all 11 architectures, but not all architectures use the same C libraries. No problem, Debian's server farm just autobuilds the package with different libraries for each platform.
When it comes to an installer, though, things are different. An installer needs to be bootable on all platforms, but different platforms boot in totally different ways. x86 systems start up and look for local disks in a certain way, Power Macintosh systems do it another way, and S/390 is different again. Then consider that the job of an installer is to figure out what local hardware you have available and setting up the system in a way that will work on that hardware. How does it detect the hardware? Will a detection system that works on one architecture fail horribly on another?
Probably.
But it gets worse: think about what happens when you first launch an installer. It boots up and displays some stuff on screen, right? But some machines use an AGP or PCI graphics subsystem, while others may not have a graphics subsystem at all, only a serial interface with a character-based console. What should the installer do if it starts up and finds the host system doesn't even have a graphics card installed?
The more you think about questions like that, the more it'll bake your noodle when you consider the task faced by the Debian Installer team.
In essence, they are trying to make a universal installer that will run on any architecture with any hardware detection method and any display system.
So people may bitch and moan about how it's taken so long for Debian to produce a "pretty" installer while other distros have had one for years, or they may say that Debian should just adopt a third-party installer like PGI or Anaconda, but that doesn't really take the big picture into account. Debian's mantra is to be the Universal Operating System, a
-Fork for architectures: i know lots of people don't like to wait for upgraded packages because they break on different architectures. This is what's happenning with xfree 4.3 not being available. If there were a debian-x86 fork, it would use optimization and wouldn't be behind other distros in package versions.
/dev/null. The debian installer was never the problem. It isn't harder than slackware, but dselect really, really sucks.
-Dselect needs to be sent to
-Loose the restrictions a little bit: why mplayer is missing and xine not? Mplayer has been 100% gpl since 0.9 and it was rejected from getting a package because of ffmpeg, which xine also has.
-More customization: the USE variable of Gentoo is really powerful, and it would be great when apt getting source packages. I want package X, and it wants me to install package Y that is optional and i dont want.
-Updated versions! Slackware is current, and it's stable.
-Re-do the stable, testing and unstable package list: they should only contain base, critical packages. So i want to run the latest kde with my stable setup? Is kde 2.2 more stable than 3.1? The security bugs fixed between them say no (yeah, i know they backport, but those packages never get the same QA) User-level desktop apps which aren't critical shouldn't be restricted in the same stable, testing and unstable trees, or at least they could mix and match.
And lot of other things i can't remember...
Open Source Java Web Forum with LDAP authentication
Breaking News
First Look: Next-Generation Debian Installer
The Debian installer has been considered its Achilles heel for a long time, but in the last couple of months things have really been heating up in Debian-installer-land. Ian Murdock recently announced to the Debian project that Progeny, the Debian-based distro that created the Progeny Graphical Installer, was dropping PGI in favour of porting Red Hat's Anaconda installer to Debian. But things haven't been sitting still within Debian itself either, with frantic work over the last couple of months to get the next-generation Debian Installer to the point where Sarge (Debian 3.1) can be released.
A Debian-Installer Debcamp in Germany in September saw many of the core developers get together for several days of intensive coding, with the result that Beta 1 of the new installer is now ready for the world to come and gawk, and poke, and kick the tyres, and even take it for a spin around the block. It's still changing on a daily basis but the developers want as many people as possible to give it a whirl and report back any problems they have.
So, for your edutainment and complete with pretty pictures, I present to you this first look at the next-generation Debian Installer.
Installer Rationale
To understand some of the design decisions that have been made with respect to the installer and why it's taken so long to get to this point, it's important to know a little about the Debian project itself. For many people this section will be rehashing old ground so if you just want to get to the guts of it skip ahead now to the next section, "Getting The Installer".
The long and the short of it is that Debian is committed to supporting multiple processor architectures. It's famous for being the most broadly deployable Linux distro (and possibly operating system) in existence, running on at least 11 distinct architectures. Nobody has more expertise in porting software to different platforms than the Debian project.
While that causes some problems when distributing normal user-space software, they're difficulties that can be worked around: for example, a package written in C needs to compile on all 11 architectures, but not all architectures use the same C libraries. No problem, Debian's server farm just autobuilds the package with different libraries for each platform.
When it comes to an installer, though, things are different. An installer needs to be bootable on all platforms, but different platforms boot in totally different ways. x86 systems start up and look for local disks in a certain way, Power Macintosh systems do it another way, and S/390 is different again. Then consider that the job of an installer is to figure out what local hardware you have available and setting up the system in a way that will work on that hardware. How does it detect the hardware? Will a detection system that works on one architecture fail horribly on another?
Probably.
But it gets worse: think about what happens when you first launch an installer. It boots up and displays some stuff on screen, right? But some machines use an AGP or PCI graphics subsystem, while others may not have a graphics subsystem at all, only a serial interface with a character-based console. What should the installer do if it starts up and finds the host system doesn't even have a graphics card installed?
The more you think about questions like that, the more it'll bake your noodle when you consider the task faced by the Debian Installer team.
In essence, they are trying to make a universal installer that will run on any architecture with any hardware detection method and any display system.
So people may bitch and moan about how it's taken so long for Debian to produce a "pretty" installer while other distros have had one for years, or they may say that Debian should just adopt a third-party installer like PGI or Anaconda, but that doesn't really take the big picture into account. Debian's mantra is to be the Universal Op
My servers have all sorts of hardware that I want supported. My servers have NIC cards, video cards, SCSI cards, RAID Array controllers, Fibre Channel controllers, integrated out of band management controllers, hot-plug PCI controllers, and more. I really like it when the installer detects these and loads the modules for me rather than having to do it manually or recompiling the kernel.
The main problem I had with the Debian installation process was their specification of what should be included in "installation".
... are we?
Debian install includes setting up the refresh rate of your monitor, for example. This can't always be autodetected reliably, and the Debian install has always made a bad choice for me (usually too low a refresh rate, because the install picks the maximum possible resolution). You can fix this, but you have to be willing to dig and (horrors!) think.
The right thing to do is what Windows has always done: make it easy to change. The guys at Redmond occasionally get something right. The Display Properties | Settings dialog box is very right, and it's time GNU/Linux had something equivalent. We're not too childish to learn from our opponents
Debians installer works great if you have 1996 hardware like a 3dfx video card and serial mouse and maybe a us robotics 33.6 dial up modem...
But if you have anything modern you'll definately have to spend an hour or two fucking around after the install to make sure it all works properly.
(and yes, I did RTFA, the new installer looks very good and kinda-sorta makes me want to go back to Debian, cos APT beats the stuffing out of RPM)
If I choose to install X, even with the new autodetection, do I still have to manually edit the XF86Config file to suit my needs?
Does ALSA/OSS work immediately? Will USB stuff?
(flame appropriately)
Never pet a burning dog.
Now, I haven't clikced through it in a couple months, but I hardly remember setting more than *where* it was going in the text-mode UI. All the actual configuration (localization, components, network settings, additional drivers etc. are set from a GUI after first reboot. (Unless you need them to load a 3rd party driver to for SCSI or RAID).
Anyway, on the Linux side I can only compare it to the RedHat installer, which I think was quite nice. Since the article is slashdotted, I don't know more about Debian's than what is in the summary....
Kjella
Live today, because you never know what tomorrow brings
While seleting modules by hand may not be confusing for non-newbies, it's still annoying. Sure, I know exactly which modules I need, and I could select them all by hand, but I shouldn't have to. One of the great things about RedHat's installer (I know, I know, RedHat is dead) is the kickstart option. I can put in a disk, kickstart a net install, take the disk out, and move on. And barring any unusual hardware, I'll come back to a fully installed system. This is great for bulk-installing machines.
I'm glad to see Debian has moved closer to this goal by doing module auto-detection.
There is no sig, there is only Zuul.
The authors need a little perspective. From the story:
They also state that it may be the most broadly deployable OS in existance because it runs on 11 architectures. No mean feat, I'm sure. But others run on more platforms. At least 17 CPU architectures and who knows how many "platforms" :-) Still, I'm excited about this new installer and can't wait to see if/how PGI integrates with it. Apart from this small (and very excusable IMO) bit of myopia the article does a great job of walking you through what to expect... definitely worth saving the link to read when the slashdotting is over if you can't get to it now.
.sig: file not found
i guess. but for individual packages that you know already what you're looking for i still prefer apt-get install over anything(and looking for the packages is pretty handy with apt-cache search).
anyways.. i just remembered that the installer i used was from the xfs bootdisks(may or may not be the same as this new installer, i haven't really been following up).
why xfs? just for kicks..
world was created 5 seconds before this post as it is.
All the others have GUI's which, believe it or not alot of people really really like. Easy that a monkey could do it. This doesn't look that easy.
Only 'flamers' flame!
Does slashdot hate my posts?
The right thing to do is what Windows has always done: make it easy to change.
XFree 4.3 has an extension called randr that allows changing resolution and vertical refresh on the fly, and the latest versions of both Gnome and KDE now include control panel applets for setting resolution and refresh rate. How long it will take for that to trickle down into Debian stable is anyone's guess, but the Linux community at large is already there.
0 1 - just my two bits
For the most part, this is a huge improvement on the old Debian installer. But I have a gripe about figure 34exim.jpeg ("Which Major configuration? local, internet, smarthost, satellite, none"). Would it kill them to put some brief descriptions like "workstation", "home", "server", or "laptop"?
boy I hope that trout has teeth..
- fork for architectures:
This is still one of the easiest things to make
sure things work. Things that only work on i386
show normally only that it only works by chance,
and may similar easily fail there later.
- dselect
Dselect is still the most powerfull package managing frontent ever. There are many new approaches to it, with many new ideas and concepts, that are worth discovering. But once
you are used to it, anything else is only
the kid's variant.
- mplayer
Well, if anyone can believable tell it is pute gpl, then it will be in Debian quite fast. Problem is the only people that might easily tell so are the authors, which have lied several times about this...
The next point I do not understand. Apt can already get you the source and install all build-depencencies. What else you describe are limites build-depencencies. Though I never saw any concept, how this could be reliably solved
- updated version
Well there is always a problem with new software. With 50% I could use more bleedy software. With the other 50% Debian updates to fast for me... (think gcc and co)
- doing quality control only for base packages.
This is one of the most stupid things I ever heared, and heared it often. There is nothing like a "base" and "user-level" in any sense like it could be used for your argument. Expect when you limit to "like people like I need it", which will make it worse for the 90% beeing the rest...
Well, I have to admit, having a old KDE is a problem. New broken-by-design software is better then old broken-by-design software. Perhaps some day in the future they will start to make concepts and develop something useful, then hunt after concepts, that already proofed in Windows, that one can only work ineffectively and once one got used to them...
The people who develop debian are not paid professionals but amateurs who get their self esteem from developing a backwards convoluted shit system.
If it was easy they wouldn't be uber-leet debian-doods anymore.
These are the people that want linux to remain the realm of the no life geek so they can feel cool.
If everyone could use debian they wouldn't be "Special" and "unique" for using it now would they?
"It was probably easier to write something from scratch than adapt say RedHat's installer to meet those requirements. It also doesn't sound as crude as your making it out to be. This installer has hardware detection and automatic module configuration. "
Implement the equivalent of latebinding for the installer. The bootable CD/DISK need only know how to get a base FS structure setup with a kernel+network driver and basic userland + rest of the installer. Stage 2 (located on a harddrive with network access, etc) could then be a text or GUI, and do all the rest with simplified logic because the initiall installation part was separate.
This is how all the recent Windows flavours do it, as well as some other OSes.
--
Internet Explorer (n): Another bug -- that is, a feature that can't be turned off -- in Windows.
Well, I think the old debian-installer was in the light of its user interface one of the most user friendly installer I ever met. Anybody that would read what is on the screen could make use of it. And it additonally had a extremly good documentation available.
The new thing is too much looking to ask as few questions as possible. With such ridicilous consequences of multiple choices resulting in the same action, as they all depend on the first so doing this first. Or silently guessing network mask and gateway, which is about the most stupid thing I can think of.
Face it the debian people are keeping mplayer out of debian for personal reasons.
The excuses they use about mplayer applies equally to xine but no one says anything about xine, but then again the xine developers dont have the kind of balls and spine mplayer devs do.
The disadvantage with installer is that users generally become lazy because of the very nature of an installer. It's purpose is to automatically detect a user's hardware - if it does not, then a user will likely give up and not naturally, say, update a drive in the kernel.
I'll take the most ridiculous part of that statement first... there's nothing natural about knowing how to update a driver in the kernel. Maybe it's a as natural as to clean the spark plugs for an auto mechanic, but in both cases you it only comes "naturally" because you understand how the computer/car works. An average person would go "Huh?"
So what's the installer for? It's not for making you "lazy", it's a tool to help you do yourself what most people would *never* do otherwise. The alternative wouldn't be to take a CS degree or a mechanic's education, the alternative would be to hire in a specialist ($$$) such as yourself to do it for them. That way, the customer would end up with a turn-key system/car, which in the end is all the customer wants.
Kjella
Live today, because you never know what tomorrow brings
Everyone on here is bitching away how the Debian 'installer' sucks. I think what you mean is their old installer sucked ass. How can you call this one shity, when it has everything but pretty pictures? Text is nice, and I for one don't need a picture for everything while I install a system. How can you say its only up to 'redhat 7' when it has everything redhat9.2 has and more. Realize that this is a new installer, this story is not called 'Lets bitch about the 'installer' and assume it still sucks like the old one'. This is not a flaimbait.... I just want people to know that debian did what was needed. A new installer, and look a new installer is what they've come up with. Understand something before you make statements about it. The installer 'is up to redhat7.0 standards'. Lets avoid ignorant statements, and obviously flaimbaits. This is not a flaimbait, its just my discust of having all these mod 3+ posts that talk about it sucking etc etc.. I think we all know the old one sucked, becaise it was extremely old, broken and missing important features.
No, this is
I'm personally moving all of my servers from SuSE 7.3-8.2 to Debian. For server installs I don't care about GUI. The Debian install worked great when I started with the 2.4 kernel and it detected my compaq smart array 3200 controller.
However, an average desktop user needs a graphical install. Maybe not through debian though... I mean maybe debian becomes the server/power user version and knoppix becomes the desktop install for the average computer user.
That being said, knoppix's hardware detection locks up on some of my off the shelf compaq servers. I never troubleshot the problem to see which piece of hardware it was hanging on.
The man who trades freedom for security does not deserve nor will he ever receive either. - Benjamin Franklin
It depends what you count. First of all the mapping between what they call architectures is different. In Debian is merely specifies the general processor family, so that it equals a larger number of Debian ones. On the other hand there are some architectures, where NetBSD support
quite more of the actual machines that have such a processor.
And then there is the question, what constitutes as port. Every architecture Debian has has autobuilders and developer machines actually running them all the time. Testing the software and actually building them. From how many netbsd prots do you know if the current snapshot would run without any changes?
Now I have to say, I tried to use this installer a few weeks ago. I know it's a work in progress, but it was basically entirely non functional on my computer. Bits crashed, bits had to be fixed in other virtual terminals, then it stopped switching virtual terminals (the main installer started writing all over them). In the end, I gave up and used the stable base installer and used apt to get unstable.
It didn't look like it was very near release, or at least, there's some frantic work to be done.
On another front, is there any reason why the installer cannot let you choose in between GRUB and LILO like Anaconda does?
Wow man this installer was so cutting edge...in 1999 when redhat used it...wow i'm so excited i just cant hide it!
This installer will be a very cutting edge advance in linux usability...if you got a time machine that can take me back in time to 1998 before redhat used it in redhat 6 or something...
Debian might even replace the free RedHat Linux as a good starter for newbies. I mean they even now got a easy installation (graphical one won't be bad), easy way to install packages with dselect, and I am sure there exist tool that will check for newest updates with dselect and notify the user.
CHEERS
--RoadkillBunny
Cheers,
RoadkillBunny
Hey!
Just use NetBSD, all you need is two floppy disks to install it from network.
Is this already the installer you get with Debian, or is it still in development.
I'm thinking of going back from Gentoo to Debian, but it seems sensible to wait until this new installer is deployed.
Debian's had an excellent installer for a while now...
It's called Knoppix
I was looking to install a Linux distribution that did things how the package authors intended, not how the distributor thought things should work. Red Hat et. al... tended to modify original packages, file locations, etc. a bit too much for my liking.
Knoppix's hdinstall method got me an up & running Debian install in one easy step. The boot CD lets you test your hardware for compatibility before anything's installed. When everything's tested, a simple hdinstall invocation copies the working system over to disk.
Easy as pie.
What's the frequency, Kenneth?
Good, we're thinking Knoppix here. Anyway, for those who want a brain-dead easy Debian install, this is exactly what we want to do.
Let's break this down like the old Mac commercials. Step one, boot your CD-ROM bootable computer to Knoppix. Step two, open the Root Shell and type knx-hdinstall.
There's no step three! There's no step three!
This is the reason why what Debian is doing to make their text-mode installer more friendly and more modern is just fine, and why Knoppix is a viable graphical installer for Debian, or at least the Knoppix flavor of Debian.
Knowledge is power. Knowledge shared is power multiplied.
The easiest Debian installer is Knoppix.
You boot from a Knoppix CD, and all you have to do is install a base system and apt to your hard disk, and you've got a Debian system that's already configured.
They should acknowledge this fact and officially support Knoppix as an install method for desktop users. Then they can still focus their installer on people who want to install Debian on an Alpha over their serial line.
Win dain a lotica, en vai tu ri silota
Congratulations on your shortsightedness and ignorance. Text-based installs are the most flexible as they make server installations easier, and allow interoperation with old hardware (not everyone has all new hardware, even if you personally haven't seen the old stuff in use lately).
The interface was built to be extended where necessary, including graphical installers. RTFA.
...would be that one which reads my mind and installs the OS exactly the way I want it.
;-D
I wouldn't care whether it's graphical or text-based
I'm not trolling.
/dev/hda1, /dev/hda2, etc.. list. After creating 5 or 6 partitions, am I suppose to remember all details about each partition?
/dev/hdX? Redhat 5.2 had this feature 5 years ago.
I installed Redhat 5.2 almost five years ago without previous Linux/Unix experience. That installer was way better than Debian 3.0 installer which I used a year ago.
Debian installer had two major flaws:
1. Mounting partitions. I have nothing against text-based fdisk. However, when it was time to choose a mount point, Debian presented veeery informative
It it so hard to put additional information like starting and ending cyliner and partition size after
2. Manually selecting packages. Debian package selector didn't seem to have any king of sane logic. I don't anything fancy or graphical, just:
- list of all package categories
- after selecting categories, list of all packages in that category
- space or enter selects the package and there should be OK/Cancel buttons
I hope that this faults have been fixed in a new installer.
Don't bother. The installation isn't the only thing that needs rehauling. Linux in general is more work to maintain and be productive in than 98. Want a media jukebox? Download itunes, or (ugh) Musicmatch, or many of the free varieties. Want a media jukebox on linux? Download juk, or rhythmbox, or any of the other free varieties. ... And spend a couple days just trying to get it to compile, or finding the necessary dependencies.
Enter, Enter, Enter, Enter, Enter, Enter, Enter, Enter, Enter, Down, Enter, Enter, Enter, Down, Down, Enter, Enter, (wait 10 minutes to download), Enter, Enter, Eject.
Debian!
Sig rhymes with Fig
I could deal with dselect and the overall clunkiness of the install interface, but what burned me was how Debian took the liberty of shuffling my IRQ settings everytime I installed it (and God knows what else it did to my BIOS). Of course Windows wigged out apon boot up, so I'm running Redhat.
Debians still cool, but I need what little sanity I have left!
SEO Copywriter. Just Say ON
Looks pretty pointless.
About the only thing it appears to do different is hardware detection. I guess that's a good thing as it seems every hardware type has 50 subvarieties - gee...is it a 3c509 or a 3c905 that's in this machine? Usually gets me once in a while.
And it automates the network settings by assuming you want DHCP.
Then, what is probably one of the more complex things for people who would whine about the installer, disk partitioning, is left to the same crappy program. Same with partition mounting and filesystem selection.
Why on earth if you are assuming the person must just want DHCP would you require them to manually partition and set mountpoints, end even more so, why would you offer them a choice of filesystems? If you think they can't setup networking on their own, just give them ext3 and be done.
And after you reboot, you still have tasksel and dselect as ways of installing packages. These SUCK. If you're gonna try to cater to people who think Debian sucks cause the installer, perhaps you should work on the way that an average joe would select packages. A simple curses front end to apt-cache search and apt-get would take care of this. Don't do like dselect does and as soon as they say they want package X, tell them package Y,Z, and Q are required....just let them select it, perhaps as part of the description have the depedencies listed.
I for one don't like the Debian installer. I find it hard to use and confusing. And if dselect wasn't evil enough you are now stuck with this thing which automatically selects sets of packages with some packages you don't need and then have to deinstall. If you don't want that, you have the choice of using deslect. Yay! Don't get me wrong. I was a long time Debian user and I'll probably use it again. But the installer pretty much sucks and there's room for improvement. There's no need for a GUI, just a better text installer.
On the other hand I find the Slackware and FreeBSD installers very easy to use. The FreeBSD installer exit options are a bit confusing at first, but after you get used it just rocks. No comment about the Slackware installer. It's almost perfect.
Is it just me, or does the Debian project as a whole seem to have the nastiest case of NIH ever?
Lets see... installer needs to work on multiple architectures. Anaconda is used on all of PPC (Yellowdog), x86, s390. I think that's good evidence that it fits the bill.
Installer should to work on everything from serial cable to graphical interfaces. I've used anaconda on RLX blades with a serial interface, and my workstations with graphical interfaces.
Installer should handle CDROM, HTTP, FTP, NFS, hard drive sources for the install media. Yep, anaconda does those.
And furthermore, the idea that "nobody has more expertise in porting software to different platforms than the Debian project" is pompous and ludicrous. I don't have to say anything other than "NetBSD" as an answer to that.
Red Hat's employees have commented that when they seriously thought about joining the Debian project when they were planning the future of their hobbyist/developer distribution, but decided that it probably wouldn't work out. Articles like this remind me why.
I seriously doubt that the Debian team even looked at the available GPL licensed installers before deciding to write their own from scratch.
Hot DOG ! Look at that next-generation installer ! 1997 is HERE, baby !
If your toaster had a floppy drive, you could.
It's called "a KNOPPIX CD". Fire it up, type "su knoppix-install", choose "debian system", and sit back and enjoy. The only enhancement they probably ought to make is to have a prominent menu-item for this feature.
"'I pass the test,' she said. 'I will diminish, and go into the West, and remain Galadriel.'"
- JRR Tolkien.
Maybe I'm wrong but I would think even the most basic users would recognize the difference. I mean there are a lot of people that freak out when they don't have a mouse pointer on the screen.
Granted, maybe those aren't the right audience to be selling on using linux on their desktop anyway, but I kind of think without those people it will be tough to gain market share.
The man who trades freedom for security does not deserve nor will he ever receive either. - Benjamin Franklin
This issue varies from distro to distro. Under debian I've never had any problems like that, which is part of the reason I use it on my laptop.
On my desktop I use Source Mage, which sometimes has those sorts of problems, but It's worth it for me for the learning and control it gives me.
Blessed are the pessimists, for they have made backups.
He's right about the context switching between mouse and keyboard. Constantly switching over like that can also lead to repetitive stress injury if your job is hectic and you have to do a lot of stuff quick for hours on end.
I read it here, downloaded it (ISO) and tried it (under VMWARE) and it worked beautifully. Very nice indeed.
The review author says
" Next the installer throws you into cfdisk to set up the actual partitions:
Personally I think a very good thing would be an option at this point to ask if you want the installer to take care of the partitioning for you. While many people will want to configure the partitions themselves, most new users (and many experts for that matter) just want a standard set of partitions that work in 95% of cases. Having a "Please decide for me" button that just nukes the disk and sets up a standard partition set would be very useful at this point. "
I was in cfdisk and forgot to create a / partition before quitting. And THEN it put me where I can select "choose for me" (or the equivalent). I agree with the author that they should move that question to a point before it goes into the cfdisk partitioning. Then the chicken can do it!
X still gives some trouble under VMWARE to install, but that's another issue not related to the new and wonderful installer.
Where do they come up with these names? And what does it mean? I don't even know what a Gerneration is, much less what the Next one will be like.
--
"Outlook not so good." That magic 8-ball knows everything! I'll ask about Exchange Server next.
I went to both the site mentioned in the article and the main Debian site and could not locate the much-talked-about "new" installer.
So where in the name of king-kong is it???
dselect is more powerful than any of the other front-ends. It's not even that hard to learn to use it either. There's a small (about 6 pages) PDF on debian.org that explains what each screen does and what the status lines mean. It took me about a half hour to become proficient with it, and now I use it whenever I want a front-end. Most of the time I use no front-end at all, just apt-cache and apt-get because I don't even have to leave the shell (it's faster).
it seems sensible to wait until this new installer is deployed
If you mean, wait until it's in the "stable" release, you could have a long, LONG wait. This is one of the real problems with Debian. Debian people will be so busy making sure that it works for the 3 people on the planet who want to run Linux on a Myxolidian 237 architecture, that it will be at least a year from now before they release the next major version on x86. Some earlier posts praised Debian for supporting 11 CPU architectures. It is good to support something other than Intel/AMD, and definitely worthwhile to support emerging 64-bit CPUs, but no rational case can be made for supporting more than about 5. Any more just slows down progress on the archs that matter.
I ain't no genius, but I'm pretty handy with Linux. My server recently suffered a motherboard failure, and since I had to crack the box and do lots of work on it anyway, I decided to give up on RH 7.3 and go to Debian for stability and security. After having heard how nasty the installer was, I was relatively impressed with how easily it went. I used one of the LiveCD installers packaged by the Debian team members. It was *much* smoother than the Gentoo install I did recently on a home system.
Anyway, I'm not going to diss efforts to make a better installer, but I didn't find Debian installation to be as bad as folks have told me it would be, and the distro itself is just lovely once working.
Online citizen journalism from the inner city: The View From The Ground
"To be fair, the only time most people ever need to even insert any hardware modules for the install is to install a single network card driver. The modules for the rest of a person's hardware are generally loaded by the kernel after installation."
HA!
Maybe my system isn't "general" enough for Debian. I've spent the last 2 days installing Woody, reconfiguring and recompiling kernels, and reinstalling packages, just to get my network card (Intel Eepro 10/100) and CD writer working. Debian doesn't correctly configure the network card modules during the install, and doesn't even bother to think about the CD writer.
I think the only "fair" thing to say about Debian's current installer is that it's competitive with Redhat's 1998 installer. So, ultimately, I have to spend 3x as long installing the system as I would using Redhat, and I'll get a system composed of packages that are old. Why is this worthwhile, again?
I'm burning a Fedora Core CD as I write....
Let's try not to let fact interfere with our speculation here, OK?
I constantly see people beefing over linux installation software. WHO CARES?! It's an install! It is ment to be done ONCE! After you install it there is nothing more to talk about! IT's over! DONE! The Debian installation IMHO assumes you have basic computer knowledge ie: What a partition is, Network settings etc....there is no problem with the installer. Use it, and forget about it. You all talk as if you sit in your rooms with linux CD's and continuously run the installation software until your blue in the face. Shut up already.
The last thing we need is someone rehashing that old "we need a GUI install" troll. Next thing you know, people will be talking about pouring hot grits down their pants.
To further prove this point, ever been to an art gallery? Ever noticed that the paintings aren't always very useful or good? I went to an art gallery once, the only reason that I got anything out of the experience was because of a self guided tour, which had words!I whole heartedly agree. I think that the next generation of installers will make software suggestions based on hardware cofigurations. For example:This type of a suggestion works well with all types of users. Here's another example.
Take care...
It's called Knoppix...
"You must be doing something wrong. My epro 10/100 works just by loading the module during the install and the CD writer "just works". /me wonders what is wrong with you?"
Ah, you must be part of the highly-touted "community support" for Debian!
What is wrong with me, if you must know, is that I stuck a Debian CD into my drive, and naively assumed that it would work.
Frankly, between half-assed installs, old packages and trolls like yourself, I don't have any problem using Redhat or Fedora. I prefer to get work done, rather than fskcing around with my CD drive for days....
Let's try not to let fact interfere with our speculation here, OK?
I use Japanese keyboard.
When I misconfigured X11,I must type the keyboard with english keyboard mapping.
I had really hard time.
That's "could HAVE," you idiot. "Of" is a preposition, not a verb.
...it raises that question, you fucking ignoramus!
I installed Mandrake 9.2 on this laptop. It didn't even mention the CD burner, because the machine doesn't have one (but it didn't on the desktop box underneath it either, which has a Sony CRX220E1 52x24x52 IDE CD burner in it). I effortlessly pulled 503 photos from a Sony DSC-F717 camera onto my laptop during the course of a day. I plugged in a "Genesys" 5.25-inch external USB2 cage containing an IDE DVD burner (a Pioneer DVR-106D) and put a CD blank into it.
- K, Applications, Archiving, CD Burners, k3b;
- drag folder to "Data1" project;
- click Burn.
I waited 3 minutes. My wife is delivering the resulting CD (and two spare children) to her sister as I type. SuSE is similarly easy, but I still prefer Mandrake.You should get out and about more often. (-:
Got time? Spend some of it coding or testing
Windows often comes up in a full colour screen after a reboot, as long as the full colour you had in mind was blue. Well... I say "full colour", but it's got some white lettering on it too.
Got time? Spend some of it coding or testing
AFAICT The installer's written almost entirely in PERL, and has several text modes as well, which would make porting it to those fabulous 11 different architectures much easier. If you could make the initial logic just that tiny bit cleverer and eliminate most of the RAMdisk stuff for most configurations, it'd probably install in 8 or 16MB.
Got time? Spend some of it coding or testing
I'm glad I'm not the only one that feels this way. Graphical installers introduce too many glitches and failures. Many of times I've ran into installing Mandrake and having it freeze on me, only having to reboot and try again.
;)
Debian and Slackware installers are probably my favorite (never tried FreeBSD but it looks the same), they are smooth and not that confusing if you actually read. I've tried Redhat text install and it didn't feel as smooth. Graphical installers are not necessary especially if you're going to be setting up a server that's not going to use a GUI anyways. All I ask is for easy menus and a back button to fix any mistakes I've made.
The auto detection is a nice feature, but isn't necessary in my situation because I know all the hardware I have. Although I see this helpful in a corporate environment where you don't know what kind of hardware is set up on a client's computer.
Overall I think this new installer is a great compromise. We don't have the shiny GUI install where a mindless drone can just "duhhh next next next", but at the same time, the install is much easier. Plus no worrying about your installer trying to figure how to get your funky video card to work in X
A 'nice pretty' GUI installer is still needed if you want the unwashed masses to warm up to it.
Techie types, sure we can do with out, but the market share of the general public is what you are after..
And to get there, you must make it brainless and pretty...
---- Booth was a patriot ----
now if they would just add the possibility to install it on software raid without having to fsck around with uncomrpessing raidtools on the second console and ccompiling kernel before the first reboot..
redhat has had it for years
What a ridiculous statement. NetBSD runs on 30+ platforms. I think it's very clear who has more expertise in porting software to different platforms.
now I am a command line guy for more things that most folks. (I like being able to use things like a pipe or a single command to do a fileop that would take thousands of clicks in a GUI, but that is another discussion) back to CD burning.
:)
In both rh6.2 and rh7.3, cd burning has been cake!.
used both scsi and ide burners under rh6.2, ide under 7.3. In all cases just have mkisofs and cdrecord instaleld and then do:
mkisofs -J -T -R -v -o
cdrecord -v dev=0,0,0
(the dev may vary depending on your hardware config, than is what cdrecord -scanbus is for)
Have no idea about burning under a RH GUI but see above
While still not a graphical installer (and the article does a good job of explaining why that's not a priority)
Just because it doesn't use a bitmap doesn't make it non-gui. An X frontend would likely be exactly the same functionality only displayed as a pretty bitmap.
When I started out running redhat 5.1 back in the day, it took me days... partly b/c of the lack of hardware detection and partly b/c of the text menus that I couldn't understand. Installing an OS shouldn't be intimidating.
You are wrong my friend.
... 'Frontend' (split into two and hyphenated if you please).
A frontend can be written that'll, say, automatically select options (eg. Auto-select Qwerty). But there'll still be a text-based interface to allow power users to do whatever they please.
It's the best of both (Friendly vs Functional) worlds.
The answer to that is no. It is more important for the results to reflect the exercise than for the people to have faith in the collection method. To be perfectly frank, if the gov't wants to use electronic voting machines, it will. It is the duty of those who build and test the machines to make sure that the machines are tamper-evident and relieble. If the system does not function securely, then it must not be used. IMHO, if there is no paper receipt for the votes cast, the incentive to cheat will be overwhelming. One solution to this issue might be to have an electronic voting machine which punches a card (like a butterfly ballot or an IBM-style punchcard) indicating what vote was cast. These votes could be counted electrically, but would retain a physical record of the vote. Thus there would be the same sort of instant tally that a fully electronic system offers, but there also would be physical receipts to confirm the tally in the case of any questions. If the physical votes do not match the electronic one, you know you have a problem. Each precinct gets exactly the number of voting cards they need for all of their registered voters, returning the unused ones to ensure that there are no votes being replaced with forged votes.
The debian installer, overall, isn't all that terrible. The package selection, however, is attrocious. You have two options: Install everything, or spend hours flipping back and forth between the choices and the "fulfill your dependencies" screen a thousand times. If the package selection were designed without the intent of making your life tedious and boring, then the process would be much better. The process isn't hard, it's just long and drawn out.
Now, lest anyone think that this is a Debian-bash, other installers and package-selectors have their flaws as well. RedHat lets you choose packages quickly, and deal with dependencies afterward. However, once it's figured out your dependencies, you either have to go back and try it yourself, or make a blanket decision that will affect all of the packages. A combination of the two would be nice - pick your packages, then let it figure out the dependencies, and let you choose on a package-by-package basis what you want to do.
In RedHat's case, the dependencies are insane. While Perl is a really need programming language, the idea of having a non-working vi because Perl isn't present seems insane to me. And the idea that X-windows just won't work without openssl isn't much better!
Oh, you're not stuck, you're just unable to let go of the onion rings.
What I don't like about Debians installer is the step where one selects what packages to install. Trying to determine which packages one needs from a list of thousands of packages needs a very smart GUI that can group related packages etc in numerous ways. I don't think any distribution has got this part right.
Ok, guys. You can log into your other accounts and mod my posts down. The thing is, I can see you doing it, and what goes around comes around.
It's one thing to abuse the moderation system. It's quite another to be so transparent about it that you avoid moderating a personal insult in the grandparent post, while targeting my own.
If people want to use Debian and they want a 3 step installer, they can use LindowsOS. You hit enter 3 times, name your computer and it's installed in 5 minutes.
This new Debian installer seems like a solid tool for the power user. If they want more control, then they get it.
Seems like Debian world is getting a complete offering of installer products from low cost, easy commercial to free, power-user tools.
This is a good thing for Linux and a good thing for Debian.
Uhhh, JRR Tolkien is a HE !!
In the parent post, I express a legitimate concern about the quality of the Debian install process. I believe I have been unfairly censored, so I will repost the core of my complaint.
To recap: I just bought a new system, containing fairly run-of-the-mill hardware, including an Intel eepro100-derived network card and a CD writer. Debian Woody, as installed directly from the net, does not properly detect my network hardware at boot time, and furthermore, doesn't even bother to set up my CD writer. I said as much in the parent post. I did not insult anyone, post false information, or try to start an argument. I posted my experience, and was moderated as flamebait.
I guess I have to wonder what the discussion on this site is worth if posts like mine are so easily censored. Perhaps those individuals who are so extremely sensitive about critiques of Debian's quality should spend a little time fixing bugs, and a little less time moderating posting on slashdot...
Let's try not to let fact interfere with our speculation here, OK?