From c9a8d5309d23424fe3ff0e68f491d782bc0fadd9 Mon Sep 17 00:00:00 2001 From: Frans Pop Date: Fri, 15 Sep 2006 10:19:10 +0000 Subject: Update of Dutch translation --- nl/appendix/files.xml | 20 ++--- nl/appendix/plip.xml | 6 +- nl/appendix/preseed.xml | 23 ++++-- nl/boot-installer/alpha.xml | 4 +- nl/hardware/hardware-supported.xml | 141 +++++++++++++++++++---------------- nl/hardware/installation-media.xml | 4 +- nl/hardware/supported/i386.xml | 57 ++++++++++++-- nl/hardware/supported/s390.xml | 6 +- nl/howto/installation-howto.xml | 4 +- nl/install-methods/floppy/i386.xml | 4 +- nl/install-methods/tftp/rarp.xml | 53 +++---------- nl/partitioning/partition/alpha.xml | 15 ++-- nl/post-install/kernel-baking.xml | 4 +- nl/post-install/post-install.xml | 3 +- nl/post-install/shutdown.xml | 28 ++++--- nl/preparing/bios-setup/i386.xml | 7 +- nl/using-d-i/modules/partman-lvm.xml | 83 ++++++++++++++++----- nl/using-d-i/modules/partman.xml | 32 ++++---- 18 files changed, 294 insertions(+), 200 deletions(-) (limited to 'nl') diff --git a/nl/appendix/files.xml b/nl/appendix/files.xml index 481a28aec..ea39f0903 100644 --- a/nl/appendix/files.xml +++ b/nl/appendix/files.xml @@ -1,18 +1,18 @@ - + Linux Devices -In Linux you have various special files in -/dev. These files are called device files. In -the Unix world accessing hardware is different. There you have a -special file which actually runs a driver which in turn accesses the -hardware. The device file is an interface to the actual system -component. Files under /dev also behave -differently than ordinary files. Below are the most important device -files listed. +In Linux various special files can be found under the directory +/dev. These files are called device files and +behave unlike ordinary files. The most common types of device files +are for block devices and character devices. These files are an +interface to the actual driver (part of the Linux kernel) which in +turn accesses the hardware. Another, less common, type of device file +is the named pipe. +The most important device files are listed in the tables below. @@ -106,7 +106,7 @@ files listed. null - Everything pointed to this device will disappear + Anything written to this device will disappear zero One can endlessly read zeros out of this device diff --git a/nl/appendix/plip.xml b/nl/appendix/plip.xml index 9c1532cba..a6b5361ba 100644 --- a/nl/appendix/plip.xml +++ b/nl/appendix/plip.xml @@ -1,5 +1,5 @@ - + Installing &debian; over Parallel Line IP (PLIP) @@ -100,7 +100,7 @@ echo 1 > /proc/sys/net/ipv4/ip_forward Boot the installation media. The installation needs to be run in expert mode; enter expert at the boot prompt. -If you need to set paramenters for kernel modules, you also need to +If you need to set parameters for kernel modules, you also need to do this at the boot prompt. For example, to boot the installer and set values for the io and irq options for the parport_pc module, enter the following at the boot prompt: @@ -117,7 +117,7 @@ the installation. -Load installer components +Load installer components from CD diff --git a/nl/appendix/preseed.xml b/nl/appendix/preseed.xml index d24188876..85113571c 100644 --- a/nl/appendix/preseed.xml +++ b/nl/appendix/preseed.xml @@ -1,5 +1,5 @@ - + - + Alpha Console Firmware @@ -286,7 +286,7 @@ ewc0.0.0.2002.0 EWC0 00-06-2B-01-32-B0 You first need to set the boot protocol: ->>> set ewa0_protocol bootp +>>> set ewa0_protocols bootp Then check the medium type is correct: diff --git a/nl/hardware/hardware-supported.xml b/nl/hardware/hardware-supported.xml index a9699dcfb..c06bd1eff 100644 --- a/nl/hardware/hardware-supported.xml +++ b/nl/hardware/hardware-supported.xml @@ -1,9 +1,8 @@ - + Supported Hardware - Debian does not impose hardware requirements beyond the requirements @@ -25,10 +24,9 @@ information can be found. Supported Architectures - -Debian &release; supports eleven major architectures and several +Debian &release; supports twelve major architectures and several variations of each architecture known as flavors. @@ -44,34 +42,17 @@ variations of each architecture known as flavors. - Intel x86-based - i386 - - vanilla - - speakup - - linux26 + Intel x86-based + i386 + + - Motorola 680x0 - m68k - Atari - atari - - Amiga - amiga - - 68k Macintosh - mac - - VME - bvme6000 - - mvme147 - - mvme16x + AMD64 & Intel EM64t + amd64 + + @@ -81,15 +62,6 @@ variations of each architecture known as flavors. - - Sun SPARC - sparc - - sun4cdm - - sun4u - - ARM and StrongARM arm @@ -103,22 +75,6 @@ variations of each architecture known as flavors. rpc - - IBM/Motorola PowerPC - powerpc - CHRP - chrp - - PowerMac - pmac - - PReP - prep - - APUS - apus - - HP PA-RISC hppa @@ -170,6 +126,51 @@ variations of each architecture known as flavors. sb1a-bcm91480b + + Motorola 680x0 + m68k + Atari + atari + + Amiga + amiga + + 68k Macintosh + mac + + VME + bvme6000 + + mvme147 + + mvme16x + + + + IBM/Motorola PowerPC + powerpc + CHRP + chrp + + PowerMac + pmac + + PReP + prep + + APUS + apus + + + + Sun SPARC + sparc + + sun4cdm + + sun4u + + IBM S/390 s390 @@ -204,11 +205,11 @@ problems; make sure to mention the fact that the bug is on the as well. - &supported-alpha.xml; +&supported-amd64.xml; &supported-arm.xml; &supported-hppa.xml; &supported-i386.xml; @@ -221,7 +222,6 @@ as well. &supported-sparc.xml; Graphics Card - You should be using a VGA-compatible display interface for the console @@ -257,7 +257,6 @@ of graphics cards. A compatibility listing for Broadcom evaluation boards is available. - Laptops @@ -271,10 +270,8 @@ with GNU/Linux, see the - -Multiple Processors - + Multiple Processors Multi-processor support — also called symmetric multi-processing @@ -293,12 +290,30 @@ to do this in . At this time section of the kernel config. - + +Multiple Processors + + + +Multi-processor support — also called symmetric +multi-processing or SMP — is available for this architecture. +The standard Debian &release; kernel image was compiled with +SMP-alternatives support. This means that the kernel +will detect the number of processors (or processor cores) and will +automatically deactivate SMP on uniprocessor systems. + + + +The 486 flavour of the Debian kernel image packages for &arch-title; +is not compiled with SMP support. + + + - Multiple Processors + Multiple Processors Multi-processor support — also called symmetric @@ -321,7 +336,7 @@ section of the kernel config. - Multiple Processors + Multiple Processors Multi-processor support — also called symmetric diff --git a/nl/hardware/installation-media.xml b/nl/hardware/installation-media.xml index 5251ad417..3f9a9725f 100644 --- a/nl/hardware/installation-media.xml +++ b/nl/hardware/installation-media.xml @@ -1,5 +1,5 @@ - + Installation Media @@ -221,7 +221,7 @@ 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. - + Disk interfaces that emulate the AT hard disk interface — often called MFM, RLL, IDE, or ATA — are supported. Very old diff --git a/nl/hardware/supported/i386.xml b/nl/hardware/supported/i386.xml index 4b1e4a2ca..ab356c23d 100644 --- a/nl/hardware/supported/i386.xml +++ b/nl/hardware/supported/i386.xml @@ -1,8 +1,8 @@ - + - CPU, Main Boards, and Video Support + CPU, Main Boards, and Video Support Complete information concerning supported peripherals can be found at @@ -14,10 +14,52 @@ This section merely outlines the basics. CPU -Nearly all x86-based processors are supported; this includes AMD and -VIA (former Cyrix) processors as well. Also the new processors like -Athlon XP and Intel P4 Xeon are supported. However, Linux will -not run on 286 or earlier processors. +Nearly all x86-based (IA-32) processors still in use in personal computers +are supported, including all varieties of Intel's "Pentium" series. +This also includes 32-bits AMD and VIA (former Cyrix) processors, and new +processors like the Athlon XP and Intel P4 Xeon. + + + + +If your system has a 64-bits AMD64, Intel EM64t or Intel Core 2 Duo processor, +you will probably want to use the installer for the amd64 architecture instead +of the installer for the (32-bits) i386 architecture. + + + + +However, Debian GNU/Linux &releasename; will not run +on 386 or earlier processors. Despite the architecture name "i386", Debian +Sarge has dropped support for actual 80386 processors +(and their clones), which were supported by earlier releases + + +We have long tried to avoid this, but in the end it was necessary due a +unfortunate series of issues with the compiler and the kernel, starting +with an bug in the C++ ABI provided by GCC. You should still be able to +run Debian GNU/Linux on actual 80386 processors if you compile your own +kernel and compile all packages from source, but that is beyond the +scope of this manual. + + +. (No version of Linux has ever supported the 286 or earlier +chips in the series.) All i486 and later processors are still +supported + + + +Many Debian packages will actually run slightly faster on modern computers +as a positive side effect of dropping support for these old chips. The +i486, introduced in 1989, has three opcodes (bswap, cmpxchg, and xadd) +which the i386, introduced in 1986, did not have. Previously, these could not +be easily used by most Debian packages; now they can. + + + +. + + @@ -29,7 +71,8 @@ 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 -bus). +bus). Essentially all personal computers sold in recent years use one +of these. diff --git a/nl/hardware/supported/s390.xml b/nl/hardware/supported/s390.xml index edda7217d..237674566 100644 --- a/nl/hardware/supported/s390.xml +++ b/nl/hardware/supported/s390.xml @@ -1,5 +1,5 @@ - + S/390 and zSeries machine types @@ -10,8 +10,8 @@ be found in IBM's Redbook Linux for IBM eServer zSeries and S/390: Distributions in chapter 2.1 or at the -technical details web page at -developerWorks. +zSeries +page at the developerWorks. In short, G5, Multiprise 3000, G6 and all zSeries are fully supported; Multiprise 2000, G3 and G4 machines are supported with IEEE floating point emulation and thus degraded performance. diff --git a/nl/howto/installation-howto.xml b/nl/howto/installation-howto.xml index 38db1c33f..2f8b570f4 100644 --- a/nl/howto/installation-howto.xml +++ b/nl/howto/installation-howto.xml @@ -1,5 +1,5 @@ - + Installation Howto @@ -213,7 +213,7 @@ it's just a matter of booting linux with the initrd. Once the installer starts, you will be greeted with an initial screen. Press &enterkey; to boot, or read the instructions for other boot methods and parameters (see ). - + If you want a 2.4 kernel, type install24 at the boot: prompt. diff --git a/nl/install-methods/floppy/i386.xml b/nl/install-methods/floppy/i386.xml index 00a80a4df..3cd6b77bb 100644 --- a/nl/install-methods/floppy/i386.xml +++ b/nl/install-methods/floppy/i386.xml @@ -1,5 +1,5 @@ - + @@ -9,7 +9,7 @@ -If you have access to an i386 machine, you can use one of the +If you have access to an i386 or amd64 machine, you can use one of the following programs to copy images to floppies. diff --git a/nl/install-methods/tftp/rarp.xml b/nl/install-methods/tftp/rarp.xml index c6fd184d4..e449b79ac 100644 --- a/nl/install-methods/tftp/rarp.xml +++ b/nl/install-methods/tftp/rarp.xml @@ -1,12 +1,12 @@ - + - Setting up RARP server + Setting up RARP server -To setup RARP, you need to know the Ethernet address (a.k.a. the MAC address) +To set up RARP, you need to know the Ethernet address (a.k.a. the MAC address) of the client computers to be installed. If you don't know this information, you can @@ -18,47 +18,16 @@ command /sbin/ifconfig eth0. -On a RARP server system using a Linux 2.2.x kernel, -you need to populate the kernel's RARP table. -To do this, run the following commands: - - -# /sbin/rarp -s -client-hostname -client-enet-addr - -# /usr/sbin/arp -s -client-ip -client-enet-addr - - -If you get - - -SIOCSRARP: Invalid argument - - -you probably need to load the RARP kernel module or else recompile the -kernel to support RARP. Try modprobe rarp and -then try the rarp command again. - - - -On a RARP server system using a Linux 2.4.x kernel, -there is no RARP module, and -you should instead use the rarpd program. The -procedure is similar to that used under SunOS in the following -paragraph. - - - -Under SunOS, you need to ensure that the Ethernet hardware address for -the client is listed in the ethers database (either in the +On a RARP server system using a Linux 2.4 or 2.6 kernel, or Solaris/SunOS, +you use the rarpd program. +You need to ensure that the Ethernet hardware address for the client is +listed in the ethers database (either in the /etc/ethers file, or via NIS/NIS+) and in the hosts database. Then you need to start the RARP daemon. -In SunOS 4, issue the command (as root): -/usr/etc/rarpd -a; in SunOS 5, use -/usr/sbin/rarpd -a. +Issue the command (as root): /usr/sbin/rarpd -a +on most Linux systems and SunOS 5 (Solaris 2), +/usr/sbin/in.rarpd -a on some other Linux systems, +or /usr/etc/rarpd -a in SunOS 4 (Solaris 1). diff --git a/nl/partitioning/partition/alpha.xml b/nl/partitioning/partition/alpha.xml index 21ea31ff0..965ee8602 100644 --- a/nl/partitioning/partition/alpha.xml +++ b/nl/partitioning/partition/alpha.xml @@ -1,5 +1,5 @@ - + Partitioning for &arch-title; @@ -25,12 +25,13 @@ command to enter disk label mode. Unless you wish to use the disk you are partitioning from Tru64 Unix or one of the free 4.4BSD-Lite derived operating systems (FreeBSD, -OpenBSD, or NetBSD), it is suggested that you do -not make the third partition contain the whole -disk. This is not required by aboot, and in fact, -it may lead to confusion since the swriteboot -utility used to install aboot in the boot sector -will complain about a partition overlapping with the boot block. +OpenBSD, or NetBSD), you should not create the +third partition as a whole disk partition (i.e. with +start and end sectors to span the whole disk), as this renders the +disk incompatible with the tools used to make it bootable with aboot. +This means that the disk configured by the installer for use as the +Debian boot disk will be inaccessible to the operating systems mentioned +earlier. diff --git a/nl/post-install/kernel-baking.xml b/nl/post-install/kernel-baking.xml index c2cfa53d3..05f13162a 100644 --- a/nl/post-install/kernel-baking.xml +++ b/nl/post-install/kernel-baking.xml @@ -1,5 +1,5 @@ - + Compiling a New Kernel @@ -158,7 +158,7 @@ like any package. As root, do The subarchitecture part is an optional sub-architecture, - such as i586, + such as 686, depending on what kernel options you set. dpkg -i will install the kernel, along with some other nice supporting files. For instance, diff --git a/nl/post-install/post-install.xml b/nl/post-install/post-install.xml index 59c327813..fa3d06167 100644 --- a/nl/post-install/post-install.xml +++ b/nl/post-install/post-install.xml @@ -1,9 +1,10 @@ - + Next Steps and Where to Go From Here +&shutdown.xml; &new-to-unix.xml; &orientation.xml; &reactivating-win.xml; diff --git a/nl/post-install/shutdown.xml b/nl/post-install/shutdown.xml index e326be12d..27967df91 100644 --- a/nl/post-install/shutdown.xml +++ b/nl/post-install/shutdown.xml @@ -1,25 +1,31 @@ - + - Shutting Down the System + Shutting down the system To shut down a running Linux system, you must not reboot with the reset switch on the front or back of your computer, or just turn off -the computer. Linux must be shut down in a controlled manner, -otherwise files may be lost and disk damage incurred. You can press -the key combination Ctrl -Alt Del +the computer. Linux should be shut down in a controlled manner, +otherwise files might get lost and/or disk damage might occur. If you run a +desktop environment, there is usually an option to log out +available from the application menu that allows you to shutdown (or reboot) +the system. + + + +Alternatively you can press the key combination +Ctrl Alt Del or Control Shift Power on Macintosh -systems. You may also log in as -root and type shutdown -h now, -reboot, or halt if -either of the key combinations do not work or you prefer to type -commands. +systems. A last option is to log in as root and type one of the +commands poweroff, halt or +shutdown -h now if either of the key combinations do not +work or you prefer to type commands; use reboot to reboot +the system. diff --git a/nl/preparing/bios-setup/i386.xml b/nl/preparing/bios-setup/i386.xml index abac7a249..174e5a38a 100644 --- a/nl/preparing/bios-setup/i386.xml +++ b/nl/preparing/bios-setup/i386.xml @@ -1,6 +1,11 @@ - + + Invoking the BIOS Set-Up Menu diff --git a/nl/using-d-i/modules/partman-lvm.xml b/nl/using-d-i/modules/partman-lvm.xml index 1de105994..17979057d 100644 --- a/nl/using-d-i/modules/partman-lvm.xml +++ b/nl/using-d-i/modules/partman-lvm.xml @@ -1,5 +1,5 @@ - + Logisch volumebeheer (LVM) instellen @@ -37,26 +37,73 @@ aan om, voor zover u dat nog niet heeft gedaan, de -Het instellen van LVM in &d-i; is relatief eenvoudig. Allereerst dient u de -partities te markeren die u wilt gebruiken als fysieke volumes voor LVM. -Hiervoor selecteert u in partman vanuit het menu -Partitie-instellingen de optie -Gebruiken als: Fysiek volume voor -LVM . Vervolgens start u de module -lvmcfg (dit is mogelijk zowel direct vanuit -partman als vanuit het hoofdmenu van &d-i;) en voegt u -vanuit de menukeuze Volumegroepen (VG) aanpassen -de fysieke volumes samen tot één of meerdere volumegroepen. Vervolgens -dient u nog vanuit de menukeuze Logische volumes (LV) -aanpassen de logische volumes te creëren bovenop de -volumegroepen. +Het instellen van LVM in &d-i; is relatief eenvoudig en volledig ondersteund +in partman. Allereerst dient u de partitie(s) die u wilt +gebruiken als fysieke volumes voor LVM, te markeren. +Hiervoor selecteert u in partman +vanuit het menu Partitie-instellingen +de optie Gebruiken als: +Fysiek volume voor LVM . -Nadat u vanuit lvmcfg terugkeert in -partman, zult u de aangemaakte logische volumes als ware -het gewone partities terugvinden in het menu (en u kunt ze verder ook als -zodanig behandelen). +Als u terugkeert op het hoofdscherm van partman, zult u +een nieuwe optie Logisch volumebeheer (LVM) instellen. +Als u deze selecteert, zal u eerst worden gevraagd om nog niet vastgelegde +wijzigingen in de partitietabel te bevestigen (als die er zijn) en vervolgens +zal het configuratiemenu voor LVM worden getoond. Het menu is contextgevoelig +en toont alleen toegestane acties. De mogelijke acties zijn: + + + + Toon configuratiedetails: + toont onder andere de structuur van LVM-elementen en de namen en groottes + van logische volumes + + + Volumegroep aanmaken + + + Logisch volume aanmaken + + + Volumegroep verwijderen + + + Logisch volume verwijderen/guimenuitem> + + + Volumegroep uitbreiden + + + Volumegroep verkleinen + + + Einde: + keer terug naar het hoofdscherm van partman + + + + + +Gebruik de opties in dit menu om eerst een volume groep en vervolgens +daaronder de gewenste logische volumes. + + + + +U kunt dit menu ook gebruiken om een bestaande LVM configuratie van uw +harde schijf te verwijderen voordat U Begeleide schijfindeling met +gebruik van LVM kiest. Begeleide schijfindeling met LVM is niet +mogelijk als er al volumegroepen gedefinieerd zijn, maar door ze eerst te +verwijderen kunt u een schone uitgangssituatie creëren. + + + + +Als u wederom terugkeert op het hoofdscherm van partman, +zult u de aangemaakte logische volumes als ware het gewone partities +terugvinden in het menu (en u kunt ze verder ook als zodanig behandelen). diff --git a/nl/using-d-i/modules/partman.xml b/nl/using-d-i/modules/partman.xml index f51ad993e..d2a47fde5 100644 --- a/nl/using-d-i/modules/partman.xml +++ b/nl/using-d-i/modules/partman.xml @@ -1,5 +1,5 @@ - + Uw harde schijven indelen @@ -22,14 +22,23 @@ bepalen uit het menu. Als u kiest voor begeleide schijfindeling, heeft u mogelijk twee opties: de partities direct op de harde schijf aanmaken (de klassieke methode) of -gebruik maken van logish volumebeheer (LVM). In het tweede geval zal het +gebruik maken van logisch volumebeheer (LVM). In het tweede geval zal het installatiesysteem de meeste partities aanmaken binnen één grote overkoepelende partitie; het voordeel van deze methode is dat de grootte van de partities binnen die overkoepelende partitie relatief eenvoudig kan worden gewijzigd. Merk op dat de optie om gebruik te maken van LVM niet op alle platforms beschikbaar hoeft te zijn. - + + + +Als u kiest voor begeleide schijfindeling met gebruik van LVM, zal het +niet mogelijk zijn om wijzigingen in de partitietabel ongedaan te maken. +Met deze keuze worden effectief alle gegevens verwijderd die zich nu op +de harde schijf bevinden + + + Nadat u heeft gekozen voor begeleide schijfindeling (klassieke methode danwel met gebruik van LVM), kunt u een keuze maken uit de schema's @@ -145,20 +154,9 @@ voorgestelde indeling, kunt u de menuoptie Schijfindeling afsluiten & veranderingen naar schijf schrijven kiezen om de nieuwe partitie-indeling te implementeren (zoals beschreven aan het einde van deze paragraaf). Als u nog niet tevreden bent, kunt u kiezen voor -Veranderingen aan partities ongedaan maken - - - -Als u heeft gekozen voor begeleide schijfindeling met gebruik van LVM, dan zal -u niet alle wijzigingen ongedaan kunnen maken aangezien sommige wijzigingen -reeds naar de harde schijf weggeschreven zullen zijn. Het installatiesysteem -zal echter waarchuwen voordat dit gebeurt. - - - - en de begeleide schijfindeling nogmaals uit te voeren of om de -voorgestelde indeling te wijzigen zoals hieronder beschreven voor handmatige -schijfindeling. +Veranderingen aan partities ongedaan maken en de +begeleide schijfindeling nogmaals uit te voeren of om de voorgestelde indeling +te wijzigen zoals hieronder beschreven voor handmatige schijfindeling. -- cgit v1.2.3