Differences between revisions 1 and 289 (spanning 288 versions)
Revision 1 as of 2004-01-11 21:33:59
Size: 3141
Editor: anonymous
Comment:
Revision 289 as of 2018-09-03 03:20:48
Size: 5155
Editor: PaulWise
Comment: https
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## Auto-converted by kwiki2moinmoin v2005-10-07
'''debian-installer''' is the installation system that sarge is going to use when it is released. '''boot-floppies''', its predecessor for woody, is dead and buried.
#language en
~-Translation(s): [[pt_BR/DebianInstaller|Brasileiro]] - English - [[es/DebianInstaller|Español]] - [[fr/DebianInstaller|Français]] - [[id/DebianInstaller|Indonesian]] - [[it/DebianInstaller|Italiano]] - [[ru/DebianInstaller|Русский]] - [[zh_CN/DebianInstaller|简体中文]] -~
----
DebianInstaller is the official installation system for the Debian distribution since the [[DebianSarge|Sarge]] (3.1) release. It is brought to you by the [[/Team|Debian Installer Team]].

You can:
 * go to the [[https://www.debian.org/devel/debian-installer/|Home page]] of the project

Contact:
 * Email: debian-boot@lists.debian.org
 * IRC: [[irc://irc.debian.org/debian-boot|#debian-boot]]

<<TableOfContents(3)>>
Line 5: Line 16:
__Currently broken things__ == Information for users ==
 * Read the [[/FAQ|Frequently Asked Questions]] first
 * Read the Installation Manual first as well:
   * the [[https://www.debian.org/releases/stable/installmanual|stable version]]
   * the [[https://www.debian.org/releases/testing/installmanual|testing version]]
   * the [[https://d-i.debian.org/manual/|latest version]]
Line 7: Line 23:
 * AlmostNoPartitioningTool === Using Debian Installer ===
  * Automate installs with [[/Preseed|preseed]]
  * Install Debian on a system using [[/SataRaid|Serial ATA (SATA) RAID]] (DebianPkg:dmraid)
  * Install Debian under [[/UMLInstall|User Mode Linux]]
  * Install Debian as [[/Xen|Xen]] (Domain0) or in Xen (DomU)
  * Install Debian on [[/MultipathSupport|Multipath devices]]
Line 9: Line 30:
 * NoMultipleArchitectureSupport, only i386, alpha and powerpc. === Troubleshooting ===
  * How to [[/Rescue|rescue]] a broken system
Line 11: Line 33:
 * Firewire discs, this includes FW CD-ROMS. === Creating CD ===
If you want to make [[image|images]] and CD/DVD related stuff:
  * Build your own Debian CDs with this [[DebianCustomCD|HowTo]] or with [[Simple-CDD]]
  * Download a [[DebianCustomCD/CustomDownload|partial mirror]] of only specified packages
  * Use [[DebianLive]]
  * Integrate a [[/NetInstWithThirdPartyNetworkDriver|third party network driver]] with DebianInstaller's netinst
Line 13: Line 40:
 * discover2, that is new version of discover hardware.
   * check the reduced HW list.
=== Internationalization resources ===
  * [[https://d-i.debian.org/doc/internals/|Internationalization and Localization Guide]]
  * [[https://d-i.debian.org/doc/languages.html|Supported languages]]
  * [[https://d-i.debian.org/l10n-stats/translation-status.html|Translation status for Debian Installer]]
  * [[https://d-i.debian.org/doc/installation-guide/|Translation status for the Installation Guide]]
  * [[https://d-i.debian.org/l10n-spellcheck/|Spell check and translation errors]]
  * [[/TranslationsPendingInWeblate]] Recent translation changings in Weblate, which are not yet committed to svn
Line 16: Line 48:
 * Shouldn't complain about not having a floppy drive when it isn't necessary. === Other information ===
 * [[/CustomImages|Third party]] using the installer
 * For [[/NetworkConsole|remote installs]]
 * An idea to perform remote graphical Debian installations [[/WebInstaller|using a web browser]]
'''Additional links''' can be found in [[/Links]].
Line 18: Line 54:
 * Shouldn't complain about missing IDE hardware. Not all machines use IDE. == Development ==
 * Follow day to day development: [[/JessieMinutes|Jessie Minutes]].
 * How to [[/Contrib|help us]] develop the installer
 * How to [[/CheckOut|checkout the source]]
 * Read the developer reference for the installer: [[https://d-i.debian.org/doc/internals/|Debian Installer internals]]
 * [[/GUI]] - information and status of the graphical installer
 * [[/Accessibility]] - how to test it
 * [[/Build]] - how to build your own DebianInstaller images
 * [[/Modify]] - how to modify an existing Installer image
 * [[/Bugs]] and /BugsPolicy
 * [[/ConsoleLayout]] - console font and keyboard configuration
 * /ProcessingInstallationReports - processing installation reports
 * /PartmanCrypto - encrypted filesystem support in partman
 * [[/Manual]] - uploading the manual
Line 20: Line 69:
 * Verify that the USB keyboard works. ( So tell us! ) === Organization ===
 * [[/Meetings]] and in-person [[/WorkSessions]]
 * [[/Tasks]] - tasks involved in the installer development and who is in charge of what
 * [[/SpamClean]] - coordinating the cleaning of spam from the debian-boot mailing list
Line 22: Line 74:
=== Release preparation ===
  * [[/JessieGoals|Goals for Jessie]] development
  * [[/WheezyGoals|Goals for Wheezy]] development
  * [[/SqueezeGoals|Goals for Squeeze]] development
  * [[/ReleaseProcess|Release process]] overview
  * [[/ReleaseAnnounce|Release announcement]] draft
  * [[/HumanReadableChangelogs|Comprehensive changelogs]] of the whole debian-installer
  * [[https://d-i.debian.org/testing-summary.html|summary of packages providing udebs]] that have different versions in testing and unstable; also mentions build dependencies for the debian-installer package.
  * [[https://d-i.debian.org/edos/|Installability of udebs]]
Line 23: Line 84:
Read more in the DebianInstallerSecondStatusreport. === Ports ===
  * Status of d-i port to [[/Hurd|hurd-i386]]
  * d-i development for the [[/M68k|m68k]] port
  * d-i development for the [[/kFreeBSD|GNU/kFreeBSD]] port
Line 25: Line 89:
__How you can help__

Code is a great way to contribute. Testing is pretty good too. Now, code that comes with tests: that's the best. Follow DebianInstallerBuild instructions.

__Ideas__

 * InstallOnDemand, UninstallOnExpiry, RevertingBackToNormalTextMode, DebianUserModels

 * Make debconf and config4gnu work together and use it for ConfigurationHandling issues allready during installation as well as in the running system. Config4gnu is the long awaited universal engine, back- and frontend framework to handle original and authoritative standard configuration files. The guys that started the project have really thought it through after having considered allready existing (sub-optimal) solutions. http://config4gnu.sourceforge.net

__Important addresses__

 * http://cvs.debian.org/debian-installer/ -- the CVS repository

 * aph@debian.org -- can get you CVS commit access

 * http://lists.debian.org/debian-boot/ is the mailing list.

 * tsauter@debian.org -- ["PowerPC"] fella..
== Old material ==
These pages are kept here for historical reasons
  * How to work around problems with combined [[/RAIDvsCrypto|RAID + crypto setups]]
Line 46: Line 94:

For booting debian-installer floppy images over network see:

 * ["DebianInstallerBootpTFTP"] for most architectures
 * DebianInstallerMknbi for IBM PC
 * DebianInstallerMknbiDos for IBM PC
----
DebianInstallerConcepts
----

Note that this page will constantly evolve as the installer progresses. If there's something on it you know is wrong, __fix it__.

----

Is the DebianInstaller project not going to use PGI b/c it only works for i386 ? - PGI works not only in i386 but in other architectures, like ["IA64"], too - I've read this in PGI documentation ( http://www.progeny.com/products/pgi/guide.html#id2781733 ):

PGI is architecture-independent and has been designed for portability. In its first release, PGI supports the Intel x86 and IA-64 architectures. Hooks are in place for developers on other architectures to add support for their platforms without having to make infrastructural changes to PGI.


Is the DebianInstaller going to graphical in nature?

The DebianInstaller will not be graphical by nature, but modularity is a key in his design. It would allow to use different kinds of frontends, of which graphical one(s).

Why can't the installation detect to see if the machine being installed is supported by PGI, if so, use pgi, if not, use a non-graphical gui?
{{{
 comments about how Debian is really not ready for the inexpert user, and once again we'll deserve them.
}}}
## This page is referenced from https://www.debian.org/doc/user-manuals
## This page is referenced from https://www.debian.org/releases/stable/debian-installer/
## This page is referenced from https://www.debian.org/releases/oldstable/debian-installer/
CategoryPermalink

Translation(s): Brasileiro - English - Español - Français - Indonesian - Italiano - Русский - 简体中文


DebianInstaller is the official installation system for the Debian distribution since the Sarge (3.1) release. It is brought to you by the Debian Installer Team.

You can:

Contact:

Information for users

Using Debian Installer

Troubleshooting

  • How to rescue a broken system

Creating CD

If you want to make images and CD/DVD related stuff:

Internationalization resources

Other information

Additional links can be found in /Links.

Development

Organization

  • /Meetings and in-person /WorkSessions

  • /Tasks - tasks involved in the installer development and who is in charge of what

  • /SpamClean - coordinating the cleaning of spam from the debian-boot mailing list

Release preparation

Ports

  • Status of d-i port to hurd-i386

  • d-i development for the m68k port

  • d-i development for the ?GNU/kFreeBSD port

Old material

These pages are kept here for historical reasons

  • How to work around problems with combined ?RAID + crypto setups


CategoryPermalink