From c27cefb9830b174b22714d7bef48a40380462619 Mon Sep 17 00:00:00 2001 From: Frans Pop Date: Fri, 3 Oct 2008 16:40:22 +0000 Subject: Update of untranslated documents --- nl/appendix/graphical.xml | 32 +------- nl/appendix/preseed.xml | 10 ++- nl/hardware/buying-hardware.xml | 44 +---------- nl/hardware/hardware-supported.xml | 126 ++++++++++++++++--------------- nl/hardware/hardware.xml | 3 +- nl/hardware/installation-media.xml | 24 +++--- nl/hardware/network-cards.xml | 24 +++--- nl/hardware/supported-peripherals.xml | 116 +--------------------------- nl/hardware/supported/i386.xml | 5 +- nl/howto/installation-howto.xml | 16 ++-- nl/install-methods/downloading-files.xml | 7 +- nl/partitioning/device-names.xml | 12 +-- 12 files changed, 114 insertions(+), 305 deletions(-) diff --git a/nl/appendix/graphical.xml b/nl/appendix/graphical.xml index 2bc631104..ea23b24e4 100644 --- a/nl/appendix/graphical.xml +++ b/nl/appendix/graphical.xml @@ -1,5 +1,5 @@ - + The Graphical Installer @@ -128,41 +128,13 @@ that there are some known issues. We continue to work on resolving these. Information on some screens is not yet nicely formatted into columns as it -should be. This is most visible during partitioning. - - - - -Typing some characters may not work and in some cases the wrong character -may be printed. For example, "composing" a character by typing an accent and -then the letter over/under which the accent should appear does not work. +should be. Support for touchpads is not yet optimal. - - - -Starting a shell from the graphical frontend is currently not supported. -This means that relevant options to do that (which are available when you -use the textual frontend), will not be shown in the main menu of the -installation system and in the menu for the rescue mode. You will instead -have to switch (as described above) to the shells that are available on -virtual consoles VT2 and VT3. - - - -After booting the installer in rescue mode, it may be useful to start a shell -in the root partition of an already installed system. This is possible (after -you have selected the partition to be mounted as the root partition) by -switching to VT2 or VT3 and entering the following command: - - -# chroot /target - - diff --git a/nl/appendix/preseed.xml b/nl/appendix/preseed.xml index 74323b17f..9287190ed 100644 --- a/nl/appendix/preseed.xml +++ b/nl/appendix/preseed.xml @@ -1,5 +1,5 @@ - + - - - - Peripherals and Other Hardware - - -Linux supports a large variety of hardware devices such as mice, -printers, scanners, PCMCIA and USB devices. However, most of these -devices are not required while installing the system. - - - -USB hardware generally works fine, only some -USB keyboards may require additional configuration -(see ). - - - -Again, see the -Linux Hardware Compatibility HOWTO -to determine whether your specific hardware is supported by Linux. - - - -Package installations from XPRAM and tape are not supported by this -system. All packages that you want to install need to be available on a -DASD or over the network using NFS, HTTP or FTP. - - - -The Broadcom BCM91250A evaluation board offers standard 3.3v 32 bit and 64 -bit PCI slots as well as USB connectors. The Broadcom BCM91480B evaluation -board features four 64 bit PCI slots. - - - -The Broadcom BCM91250A evaluation board offers standard 3.3v 32 bit and 64 -bit PCI slots as well as USB connectors. The Broadcom BCM91480B evaluation -board features four 64 bit PCI slots. The Cobalt RaQ has no support for -additional devices but the Qube has one PCI slot. - - - + Purchasing Hardware Specifically for GNU/Linux diff --git a/nl/hardware/hardware-supported.xml b/nl/hardware/hardware-supported.xml index 7648085e0..eebd7ec51 100644 --- a/nl/hardware/hardware-supported.xml +++ b/nl/hardware/hardware-supported.xml @@ -231,67 +231,6 @@ as well. &supported-s390.xml; &supported-sparc.xml; - Graphics Card Support - - -You should be using a VGA-compatible display interface for the console -terminal. Nearly every modern display card is compatible with -VGA. Ancient standards such CGA, MDA, or HGA should also work, -assuming you do not require X11 support. Note that X11 is not used -during the installation process described in this document. - - - -Debian's support for graphical interfaces is determined by the -underlying support found in X.Org's X11 system. Most AGP, PCI and -PCIe video cards work under X.Org. Details on supported graphics -buses, cards, monitors, and pointing devices can be found at -. Debian &release; ships -with X.Org version &x11ver;. - - - - -The X.Org X Window System is only supported on the SGI Indy and the O2. The -Broadcom BCM91250A and BCM91480B evaluation boards have standard 3.3v PCI -slots and support VGA emulation or Linux framebuffer on a selected range -of graphics cards. A compatibility -listing for Broadcom evaluation boards is available. - - - -The Broadcom BCM91250A and BCM91480B evaluation boards have standard 3.3v PCI -slots and support VGA emulation or Linux framebuffer on a selected range -of graphics cards. A compatibility -listing for Broadcom evaluation boards is available. - - - -Most graphics options commonly found on Sparc-based machines are supported. -X.org graphics drivers are available for sunbw2, suncg14, suncg3, suncg6, -sunleo and suntcx framebuffers, Creator3D and Elite3D cards (sunffb driver), -PGX24/PGX64 ATI-based video cards (ati driver), and PermediaII-based cards -(glint driver). To use an Elite3D card with X.org you additionally need to -install the afbinit package, and read the documentation -included with it on how to activate the card. - - - -It is not uncommon for a Sparc machine to have two graphics cards in a -default configuration. In such a case there is a possibility that the -Linux kernel will not direct its output to the card initially used by the -firmware. The lack of output on the graphical console may then be mistaken -for a hang (usually the last message seen on console is 'Booting Linux...'). -One possible solution is to physically remove one of the video cards; -another option is to disable one of the cards using a kernel boot parameter. -Also, if graphical output is not required or desired, serial console may be -used as an alternative. On some systems use of serial console can be -activated automatically by disconnecting the keyboard before booting the -system. - - - - Laptops @@ -396,4 +335,69 @@ section of the kernel config. + + Graphics Card Support + + +You should be using a VGA-compatible display interface for the console +terminal. Nearly every modern display card is compatible with +VGA. Ancient standards such CGA, MDA, or HGA should also work, +assuming you do not require X11 support. Note that X11 is not used +during the installation process described in this document. + + + +Debian's support for graphical interfaces is determined by the +underlying support found in X.Org's X11 system. Most AGP, PCI and +PCIe video cards work under X.Org. Details on supported graphics +buses, cards, monitors, and pointing devices can be found at +. Debian &release; ships +with X.Org version &x11ver;. + + + + +The X.Org X Window System is only supported on the SGI Indy and the O2. The +Broadcom BCM91250A and BCM91480B evaluation boards have standard 3.3v PCI +slots and support VGA emulation or Linux framebuffer on a selected range +of graphics cards. A compatibility +listing for Broadcom evaluation boards is available. + + + +The Broadcom BCM91250A and BCM91480B evaluation boards have standard 3.3v PCI +slots and support VGA emulation or Linux framebuffer on a selected range +of graphics cards. A compatibility +listing for Broadcom evaluation boards is available. + + + +Most graphics options commonly found on Sparc-based machines are supported. +X.org graphics drivers are available for sunbw2, suncg14, suncg3, suncg6, +sunleo and suntcx framebuffers, Creator3D and Elite3D cards (sunffb driver), +PGX24/PGX64 ATI-based video cards (ati driver), and PermediaII-based cards +(glint driver). To use an Elite3D card with X.org you additionally need to +install the afbinit package, and read the documentation +included with it on how to activate the card. + + + +It is not uncommon for a Sparc machine to have two graphics cards in a +default configuration. In such a case there is a possibility that the +Linux kernel will not direct its output to the card initially used by the +firmware. The lack of output on the graphical console may then be mistaken +for a hang (usually the last message seen on console is 'Booting Linux...'). +One possible solution is to physically remove one of the video cards; +another option is to disable one of the cards using a kernel boot parameter. +Also, if graphical output is not required or desired, serial console may be +used as an alternative. On some systems use of serial console can be +activated automatically by disconnecting the keyboard before booting the +system. + + + + +&network-cards.xml; +&supported-peripherals.xml; + diff --git a/nl/hardware/hardware.xml b/nl/hardware/hardware.xml index 798fe2cad..9eecf6792 100644 --- a/nl/hardware/hardware.xml +++ b/nl/hardware/hardware.xml @@ -13,9 +13,8 @@ about hardware supported by GNU and Linux. &hardware-supported.xml; +&buying-hardware.xml; &installation-media.xml; -&supported-peripherals.xml; &memory-disk-requirements.xml; -&network-cards.xml; diff --git a/nl/hardware/installation-media.xml b/nl/hardware/installation-media.xml index 053e597a1..2f63ce3e7 100644 --- a/nl/hardware/installation-media.xml +++ b/nl/hardware/installation-media.xml @@ -1,5 +1,5 @@ - + Installation Media @@ -52,13 +52,9 @@ up by other means; see . -Both SCSI and IDE/ATAPI CD-ROMs are supported. In addition, all -non-standard CD interfaces supported by Linux are supported by the -boot disks (such as Mitsumi and Matsushita drives). However, these -models might require special boot parameters or other massaging to get -them to work, and booting off these non-standard interfaces is -unlikely. The Linux CD-ROM HOWTO -contains in-depth information on using CD-ROMs with Linux. +SCSI, SATA and IDE/ATAPI CD-ROMs are supported. The Linux CD-ROM HOWTO contains in-depth information +on using CD-ROMs with Linux. @@ -186,17 +182,15 @@ installed on the widest array of hardware. Generally, the Debian installation system includes support for floppies, -IDE drives, IDE floppies, parallel port IDE devices, SCSI controllers and -drives, USB, and FireWire. The supported file systems include FAT, -Win-32 FAT extensions (VFAT) and NTFS. +IDE (also known as PATA) drives, IDE floppies, parallel port IDE devices, SATA +and SCSI controllers and drives, USB, and FireWire. The supported file systems +include FAT, Win-32 FAT extensions (VFAT) and NTFS. Disk interfaces that emulate the AT hard disk interface -— often called MFM, RLL, IDE, or ATA — are supported. Very old -8–bit hard disk controllers used in the IBM XT computer are supported -only as a module. SCSI disk controllers from many different manufacturers -are supported. See the +— often called MFM, RLL, IDE, or PATA — are supported. SATA and +SCSI disk controllers from many different manufacturers are supported. See the Linux Hardware Compatibility HOWTO for more details. diff --git a/nl/hardware/network-cards.xml b/nl/hardware/network-cards.xml index e833d1587..f394568b4 100644 --- a/nl/hardware/network-cards.xml +++ b/nl/hardware/network-cards.xml @@ -1,7 +1,7 @@ - + Network Connectivity Hardware @@ -90,7 +90,7 @@ supported; Spellcaster BRI ISDN boards are also not supported by the - + Drivers Requiring Firmware @@ -118,9 +118,9 @@ also copy the firmware to that location for the installed system before the reboot at the end of the installation. - + - + Wireless Network Cards @@ -146,9 +146,9 @@ use the ndiswrapper package, which allows you to use a Windows driver. - + - + Known Issues for &arch-title; @@ -157,7 +157,7 @@ mentioning here. - Conflict between tulip and dfme drivers + Conflict between tulip and dfme drivers @@ -188,9 +188,9 @@ Note that the wrong module may then still be loaded when the system is rebooted. - + - Sun B100 blade + Sun B100 blade @@ -198,6 +198,6 @@ The cassini network driver does not work with Sun B100 blade systems. - - - + + + diff --git a/nl/hardware/supported-peripherals.xml b/nl/hardware/supported-peripherals.xml index 88dbdbd8d..7a752fbe2 100644 --- a/nl/hardware/supported-peripherals.xml +++ b/nl/hardware/supported-peripherals.xml @@ -1,7 +1,7 @@ - + Peripherals and Other Hardware @@ -41,116 +41,4 @@ board features four 64 bit PCI slots. The Cobalt RaQ has no support for additional devices but the Qube has one PCI slot. - - - Purchasing Hardware Specifically for GNU/Linux - - - -There are several vendors, who ship systems with Debian or other -distributions of GNU/Linux -pre-installed. You might pay more -for the privilege, but it does buy a level of peace of mind, since you can -be sure that the hardware is well-supported by GNU/Linux. - - - -Unfortunately, it's quite rare to find any vendor shipping -new &arch-title; machines at all. - - - -If you do have to buy a machine with Windows bundled, carefully read -the software license that comes with Windows; you may be able to -reject the license and obtain a rebate from your vendor. Searching -the Internet for windows refund may get you some useful -information to help with that. - - - -Whether or not you are purchasing a system with Linux bundled, or even -a used system, it is still important to check that your hardware is -supported by the Linux kernel. Check if your hardware is listed in -the references found above. Let your salesperson (if any) know that -you're shopping for a Linux system. Support Linux-friendly hardware -vendors. - - - - Avoid Proprietary or Closed Hardware - - -Some hardware manufacturers simply won't tell us how to write drivers -for their hardware. Others won't allow us access to the documentation -without a non-disclosure agreement that would prevent us from -releasing the Linux source code. - - - -Another example is the proprietary hardware in the older -Macintosh line. In fact, no specifications or documentation have ever -been released for any Macintosh hardware, most notably the ADB -controller (used by the mouse and keyboard), the floppy controller, -and all acceleration and CLUT manipulation of the video hardware -(though we do now support CLUT manipulation on nearly all internal -video chips). In a nutshell, this explains why the Macintosh Linux -port lags behind other Linux ports. - - - -Since we haven't been granted access to the documentation on these -devices, they simply won't work under Linux. You can help by asking -the manufacturers of such hardware to release the documentation. If -enough people ask, they will realize that the free software community -is an important market. - - - - - - Windows-specific Hardware - - -A disturbing trend is the proliferation of Windows-specific modems and -printers. In some cases these are specially designed to be operated by -the Microsoft Windows operating system and bear the legend WinModem -or Made especially for Windows-based computers. This -is generally done by removing the embedded processors of the hardware -and shifting the work they do over to a Windows driver that is run by -your computer's main CPU. This strategy makes the hardware less -expensive, but the savings are often not passed on to the -user and this hardware may even be more expensive than equivalent -devices that retain their embedded intelligence. - - - -You should avoid Windows-specific hardware for two reasons. The first -is that the manufacturers do not generally make the resources -available to write a Linux driver. Generally, the hardware and -software interface to the device is proprietary, and documentation is -not available without a non-disclosure agreement, if it is available -at all. This precludes it being used for free software, since free -software writers disclose the source code of their programs. The -second reason is that when devices like these have had their embedded -processors removed, the operating system must perform the work of the -embedded processors, often at real-time priority, -and thus the CPU is not available to run your programs while it is -driving these devices. Since the typical Windows user does not -multi-process as intensively as a Linux user, the manufacturers hope -that the Windows user simply won't notice the burden this hardware -places on their CPU. However, any multi-processing operating system, -even Windows 2000 or XP, suffers from degraded performance when -peripheral manufacturers skimp on the embedded processing power of -their hardware. - - - -You can help improve this situation by encouraging these manufacturers -to release the documentation and other resources necessary for us to -program their hardware, but the best strategy is simply to avoid this -sort of hardware until it is listed as working in the -Linux Hardware Compatibility HOWTO. - - - - + diff --git a/nl/hardware/supported/i386.xml b/nl/hardware/supported/i386.xml index 4f3a0021b..69bfbe36b 100644 --- a/nl/hardware/supported/i386.xml +++ b/nl/hardware/supported/i386.xml @@ -1,5 +1,5 @@ - + CPU, Main Boards, and Video Support @@ -69,8 +69,7 @@ be easily used by most Debian packages; now they can. The system bus is the part of the motherboard which allows the CPU to communicate with peripherals such as storage devices. Your computer -must use the ISA, EISA, PCI, the Microchannel Architecture (MCA, used -in IBM's PS/2 line), or VESA Local Bus (VLB, sometimes called the VL +must use the ISA, EISA, PCI, PCIe, or VESA Local Bus (VLB, sometimes called the VL bus). Essentially all personal computers sold in recent years use one of these. diff --git a/nl/howto/installation-howto.xml b/nl/howto/installation-howto.xml index cdba56ad7..e7e95b291 100644 --- a/nl/howto/installation-howto.xml +++ b/nl/howto/installation-howto.xml @@ -1,5 +1,5 @@ - + Installation Howto @@ -249,7 +249,7 @@ installer will only ask to select one if a country has multiple zones. Now it is time to partition your disks. First you will be given the opportunity to automatically partition either an entire drive, or available -free space on a drive (guided partitioning). +free space on a drive (see ). This is recommended for new users or anyone in a hurry. If you do not want to autopartition, choose Manual from the menu. @@ -268,7 +268,10 @@ delete it. If you did automatic partitioning, you should just be able to choose Finish partitioning and write changes to disk from the menu to use what it set up. Remember to assign at least one partition for swap space and to mount a partition on /. - has more information about partitioning. +For more detailed information on how to use the partitioner, please refer +to ; the appendix has more general information about +partitioning. @@ -289,9 +292,10 @@ See for additional information about this step. -Partitioning is followed by setting up user accounts. By default you will -need to provide a password for the root (administrator) -account and information necessary to create one regular user account. +Installation of the base system is followed by setting up user accounts. By +default you will need to provide a password for the root +(administrator) account and information necessary to create one regular user +account. diff --git a/nl/install-methods/downloading-files.xml b/nl/install-methods/downloading-files.xml index 2e5495cc5..0b39acc7d 100644 --- a/nl/install-methods/downloading-files.xml +++ b/nl/install-methods/downloading-files.xml @@ -1,5 +1,5 @@ - + Downloading Files from Debian Mirrors @@ -11,9 +11,8 @@ To find the nearest (and thus probably the fastest) mirror, see the -When downloading files from a Debian mirror, be sure to download the -files in binary mode, not text or automatic -mode. +When downloading files from a Debian mirror using FTP, be sure to download the +files in binary mode, not text or automatic mode. diff --git a/nl/partitioning/device-names.xml b/nl/partitioning/device-names.xml index ead4f1942..48272eef7 100644 --- a/nl/partitioning/device-names.xml +++ b/nl/partitioning/device-names.xml @@ -1,5 +1,5 @@ - + @@ -67,16 +67,6 @@ up as /dev/hda in Debian). - - -The first XT disk is named /dev/xda. - - - - -The second XT disk is named /dev/xdb. - - The first ACSI device is named /dev/ada, the -- cgit v1.2.3