|Deletions are marked like this.||Additions are marked like this.|
|Line 14:||Line 14:|
|Line 17:||Line 16:|
|'''Qestion''': Why are you doing this? Why not use Anaconda/PGI/whatever? Why reinvent the wheel?||'''Question''': Why are you doing this? Why not use Anaconda/PGI/whatever? Why reinvent the wheel?|
|Line 20:||Line 19:|
|PCI can't do this. Anaconda can't do this. Only a system designed||PGI can't do this. Anaconda can't do this. Only a system designed|
Please add your own questions here. It's a Wiki. Just Click the EDIT button.
Question: Why does DebianInstaller always use DHCP? I want a static address!
Answer: Boot the installer in expert mode ("boot: expert"), and you will be able to configure a static address, and many other things besides.
Question: But, I'm not an expert, I only want to use static IP addresses.
Answer: If you see anything you don't understand in expert mode, just take the default. DebianInstaller is targeting a larger base of users than have historically installed Debian, including users who don't know what DHCP or static IP addresses are. We understand that the default behavior is annoying if you're a sysadmin installing a server on a network with DHCP, but need to use a static IP, but you're in a fairly small category of users, and really, expert mode was designed just for you.
Question: Why are you doing this? Why not use Anaconda/PGI/whatever? Why reinvent the wheel?
Answer: We're doing this because it's time. Debian has been burdened with a sub-par installer for a full decade, and it's time to change all that. Debian's installer needs to work on more platforms and more types of install media than any other. We need to support installs to S/390 mainframes that have only a teletype console. We need to support installs to m68k boxes that boot from floppies, as well as to netbooting Sun hardware. And yes, we want to support flashy easy installs on Intel clones booting from CD (and USB sticks). And many more; all the possibilities listed in http://www.debian.org/devel/debian-installer/ports-status . PGI can't do this. Anaconda can't do this. Only a system designed from the ground up to be completly modular and highly flexible can do so. DebianInstaller is that installer.
Question: Is the DebianInstaller going to be graphical in nature?
Answer: The DebianInstaller will not be graphical by nature, but modularity is a key in its design. It would allow the use of different kinds of frontends, including those of a graphical nature.
Question: Will the DebianInstaller support creating and installing to software RAID devices?
Answer: Yes, as of beta 3 this is fairly straightforward to do, using the menu item in the partitioner titled "Configure the Logical Volume Manger".
Question: Is anyone working on making DebianInstaller recognize and install on SATA-only drives? How soon before we should be able to try this?
Answer: This is supported as of beta 3 of the installer, at least as well as the 2.4.25 linux kernel supports them.
Question: DebianInstaller does not include a driver for my xyz network card, but I have (tarball) driver sources. What are the steps for building that driver? Do the steps include the phrase, "Assume you have kernel-headers?" Do you think you'll be able to include kernel-headers for the installer's kernel image(s) in the CD image, so we don't have to sneaker-net them around?
Answer: It's possible to do this, but we do not yet have good end-user docs explaining how to do so. We're waiting for an end user to accomplish it and write them from experience. We'd be glad to help you through the process, if you mail us, email@example.com