From f2ec7e797f51c30671c127e7fceb10e4939f66cc Mon Sep 17 00:00:00 2001 From: Frans Pop Date: Mon, 2 Nov 2009 23:04:22 +0000 Subject: Remove alpha from nl translation --- nl/boot-installer/accessibility.xml | 6 +- nl/boot-installer/alpha.xml | 454 ------------------------ nl/boot-installer/boot-installer.xml | 3 +- nl/boot-installer/parameters.xml | 2 +- nl/hardware/accessibility.xml | 2 +- nl/hardware/hardware-supported.xml | 8 - nl/hardware/installation-media.xml | 18 - nl/hardware/supported/alpha.xml | 457 ------------------------- nl/install-methods/download/alpha.xml | 36 -- nl/install-methods/downloading-files.xml | 1 - nl/install-methods/install-tftp.xml | 33 -- nl/partitioning/partition-programs.xml | 1 - nl/partitioning/partition/alpha.xml | 59 ---- nl/preparing/needed-info.xml | 8 +- nl/preparing/non-debian-partitioning.xml | 5 - nl/preparing/nondeb-part/alpha.xml | 83 ----- nl/using-d-i/components.xml | 1 - nl/using-d-i/modules/alpha/aboot-installer.xml | 19 - nl/using-d-i/modules/partman.xml | 7 - 19 files changed, 7 insertions(+), 1196 deletions(-) delete mode 100644 nl/boot-installer/alpha.xml delete mode 100644 nl/hardware/supported/alpha.xml delete mode 100644 nl/install-methods/download/alpha.xml delete mode 100644 nl/partitioning/partition/alpha.xml delete mode 100644 nl/preparing/nondeb-part/alpha.xml delete mode 100644 nl/using-d-i/modules/alpha/aboot-installer.xml diff --git a/nl/boot-installer/accessibility.xml b/nl/boot-installer/accessibility.xml index eb0345b4b..b18093453 100644 --- a/nl/boot-installer/accessibility.xml +++ b/nl/boot-installer/accessibility.xml @@ -7,7 +7,7 @@ Some users may need specific support because of e.g. some visual impairment. -USB braille displays are detected +USB braille displays are detected automatically, but most other Most accessibility features have to be enabled manually. @@ -19,7 +19,7 @@ loader interprets your keyboard as a QWERTY keyboard. - + USB Braille Displays @@ -35,7 +35,7 @@ url="&url-brltty-driver-help;">brltty website. - + Serial Braille Displays diff --git a/nl/boot-installer/alpha.xml b/nl/boot-installer/alpha.xml deleted file mode 100644 index b598bcc2d..000000000 --- a/nl/boot-installer/alpha.xml +++ /dev/null @@ -1,454 +0,0 @@ - - - - - Alpha Console Firmware - - -Console firmware is stored in a flash ROM and started when an Alpha -system is powered up or reset. There are two different console -specifications used on Alpha systems, and hence two classes of console -firmware available: - - - - - - - SRM console, based on the Alpha Console Subsystem - specification, which provides an operating environment for OpenVMS, Tru64 - UNIX, and Linux operating systems. - - - - - ARC, AlphaBIOS, or ARCSBIOS console, based on the - Advanced RISC Computing (ARC) specification, which provides an operating - environment for Windows NT. - - - - - - -From the user's perspective, the most important difference between SRM -and ARC is that the choice of console constrains the possible -disk-partitioning scheme for the hard disk which you wish to boot off -of. - - - -ARC requires that you use an MS-DOS partition table (as created by -cfdisk) for the boot disk. Therefore MS-DOS partition -tables are the native partition format when booting from -ARC. In fact, since AlphaBIOS contains a disk partitioning utility, you may -prefer to partition your disks from the firmware menus before -installing Linux. - - - -Conversely, SRM is incompatible - - -Specifically, the bootsector format required by the Console Subsystem -Specification conflicts with the placement of the DOS partition table. - - - with MS-DOS partition tables. Since Tru64 Unix uses the BSD -disklabel format, this is the native partition format for -SRM installations. - - - -GNU/Linux is the only operating system on Alpha that can be booted from -both console types, but &debian; &release; only supports booting on -SRM-based systems. If you have an Alpha for which no version of SRM is -available, if you will be dual-booting the system with Windows NT, or if -your boot device requires ARC console support for BIOS initialization, -you will not be able to use the &debian; &release; installer. You can -still run &debian; &release; on such systems by using other install -media; for instance, you can install Debian woody with MILO and upgrade. - - - -Because MILO is not available for any of the Alpha -systems currently in production (as of February 2000), and because it -is no longer necessary to buy an OpenVMS or Tru64 Unix license to have -SRM firmware on your older Alpha, it is recommended that you use SRM -when possible. - - - -The following table summarizes available and supported system -type/console combinations (see for the -system type names). The word ARC below denotes any of the -ARC-compliant consoles. - - - - - - - System Type - Console Type Supported - - - - - - alcor - ARC or SRM - - avanti - ARC or SRM - - book1 - SRM only - - cabriolet - ARC or SRM - - dp264 - SRM only - - eb164 - ARC or SRM - - eb64p - ARC or SRM - - eb66 - ARC or SRM - - eb66p - ARC or SRM - - jensen - SRM only - - lx164 - ARC or SRM - - miata - ARC or SRM - - mikasa - ARC or SRM - - mikasa-p - SRM only - - nautilus - ARC (see motherboard manual) or SRM - - noname - ARC or SRM - - noritake - SRM only - - noritake-p - SRM only - - pc164 - ARC or SRM - - rawhide - SRM only - - ruffian - ARC only - - sable - SRM only - - sable-g - SRM only - - sx164 - ARC or SRM - - takara - ARC or SRM - - xl - ARC only - - xlt - ARC only - - - - - - - - -Generally, none of these consoles can boot Linux directly, so the -assistance of an intermediary bootloader is required. For the SRM -console, aboot, a small, platform-independent -bootloader, is used. See the (unfortunately outdated) SRM HOWTO for more information on -aboot. - - - -The following paragraphs are from the woody install manual, and are -included here for reference; they may be useful to someone at a later -date when Debian supports MILO-based installs again. - - - -Generally, none of these consoles can boot Linux directly, so the -assistance of an intermediary bootloader is required. There are two -mainstream Linux loaders: MILO and aboot. - - - -MILO is itself a console, which replaces ARC or SRM in -memory. MILO can be booted from both ARC and SRM and is -the only way to bootstrap Linux from the ARC console. -MILO is platform-specific (a different MILO -is needed for each system type) and exist only for those systems, for -which ARC support is shown in the table above. See also the -(unfortunately outdated) MILO HOWTO. - - - -aboot is a small, platform-independent bootloader, which -runs from SRM only. See the (also unfortunately outdated) SRM HOWTO for more information on -aboot. - - - -Thus, three scenarios are generally possible, depending on the -system's console firmware and whether or not MILO is -available: - - -SRM -> aboot -SRM -> MILO -ARC -> MILO - - -Because MILO is not available for any of the Alpha -systems currently in production (as of February 2000), and because it -is no longer necessary to buy an OpenVMS or Tru64 Unix license to have -SRM firmware on your older Alpha, it is recommended that you use SRM and -aboot on new installations of GNU/Linux, unless you wish -to dual-boot with Windows NT. - - - -The majority of AlphaServers and all current server and workstation -products contain both SRM and AlphaBIOS in their firmware. For -half-flash machines such as the various evaluation boards, -it is possible to switch from one version to another by reflashing the -firmware. Also, once SRM is installed, it is possible to run -ARC/AlphaBIOS from a floppy disk (using the arc -command). For the reasons mentioned above, we recommend switching to -SRM before installing &debian;. - - - -As on other architectures, you should install the newest available -revision of the firmware - - -Except on Jensen, where Linux is not supported on firmware versions -newer than 1.7 — see -for more information. - - - before installing &debian;. -For Alpha, firmware updates can be obtained from -Alpha Firmware Updates. - - - - - - Booting with TFTP - - -In SRM, Ethernet interfaces are named with the ewa -prefix, and will be listed in the output of the show dev command, -like this (edited slightly): - - ->>> show dev -ewa0.0.0.9.0 EWA0 08-00-2B-86-98-65 -ewb0.0.0.11.0 EWB0 08-00-2B-86-98-54 -ewc0.0.0.2002.0 EWC0 00-06-2B-01-32-B0 - - -You first need to set the boot protocol: - - ->>> set ewa0_protocols bootp - - -Then check the medium type is correct: - - ->>> set ewa0_mode mode - - -You can get a listing of valid modes with >>>set ewa0_mode. - - - -Then, to boot from the first Ethernet interface, you would type: - - ->>> boot ewa0 -flags "" - - -This will boot using the default kernel parameters as included in the -netboot image. - - - -If you wish to use a serial console, you must -pass the console= parameter to the kernel. -This can be done using the -flags argument to -the SRM boot command. The serial ports are -named the same as their corresponding files in -/dev. Also, when specifying additional kernel -parameters, you must repeat certain default options that are needed by -the &d-i; images. For example, to boot from ewa0 -and use a console on the first serial port, you would type: - - ->>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 console=ttyS0" - - - - - - Booting from CD-ROM with the SRM Console - - -The &debian; install CDs include several preconfigured boot options for -VGA and serial consoles. Type - - ->>> boot xxxx -flags 0 - - -to boot using VGA console, where xxxx is your -CD-ROM drive in SRM notation. To use serial console on the first -serial device, type - - ->>> boot xxxx -flags 1 - - -and for console on the second serial port, type - - ->>> boot xxxx -flags 2 - - - - - - - Booting from CD-ROM with the ARC or AlphaBIOS Console - - -To boot a CD-ROM from the ARC console, find your sub-architecture code -name (see ), then enter -\milo\linload.exe as the boot loader and -\milo\subarch (where -subarch is the proper subarchitecture name) -as the OS Path in the `OS Selection Setup' menu. Ruffians make an -exception: You need to use \milo\ldmilo.exe as -boot loader. - - - - - - - Booting from Floppies with the SRM Console - - -At the SRM prompt (>>>), issue the following -command: - - ->>> boot dva0 -flags 0 - - -possibly replacing dva0 with the actual device -name. Usually, dva0 is the floppy; type - - ->>> show dev - - -to see the list of devices (e.g., if you want to boot from a CD). -Note that if you are booting via MILO, -flags argument -is ignored, so you can just type boot dva0. -If everything works OK, you will eventually see the Linux kernel boot. - - - -If you want to specify kernel parameters when booting via -aboot, use the following command: - - ->>> boot dva0 -file linux.bin.gz -flags "root=/dev/fd0 load_ramdisk=1 arguments" - - -(typed on one line), substituting, if necessary, the actual SRM boot -device name for dva0, the Linux boot device name for -fd0, and the desired kernel parameters for -arguments. - - - -If you want to specify kernel parameters when booting via -MILO, you will have to interrupt bootstrap once you get -into MILO. See . - - - - - - Booting from Floppies with the ARC or AlphaBIOS Console - - - -In the OS Selection menu, set linload.exe as the boot -loader, and milo as the OS Path. Bootstrap using the -newly created entry. - - - - - Booting with MILO - - -MILO contained on the bootstrap media is configured to proceed straight -to Linux automatically. Should you wish to intervene, all you need is to -press space during MILO countdown. - - - -If you want to specify all the bits explicitly (for example, to supply -additional parameters), you can use a command like this: - - -MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 - - -If you are booting from something other than a floppy, substitute -fd0 in the above example with the appropriate device name -in Linux notation. The help command would give you a brief -MILO command reference. - - - diff --git a/nl/boot-installer/boot-installer.xml b/nl/boot-installer/boot-installer.xml index 483c8a95b..d5bfac342 100644 --- a/nl/boot-installer/boot-installer.xml +++ b/nl/boot-installer/boot-installer.xml @@ -5,7 +5,7 @@ - + Booting the Installer on &arch-title; @@ -30,7 +30,6 @@ For information on how to boot the graphical installer, see -&boot-installer-alpha.xml; &boot-installer-arm.xml; &boot-installer-x86.xml; diff --git a/nl/boot-installer/parameters.xml b/nl/boot-installer/parameters.xml index 347d541dd..f9dae44eb 100644 --- a/nl/boot-installer/parameters.xml +++ b/nl/boot-installer/parameters.xml @@ -416,7 +416,7 @@ disable that authentication. - + ramdisk_size diff --git a/nl/hardware/accessibility.xml b/nl/hardware/accessibility.xml index d60d85f5a..d2eca700a 100644 --- a/nl/hardware/accessibility.xml +++ b/nl/hardware/accessibility.xml @@ -1,7 +1,7 @@ - + Braille Displays diff --git a/nl/hardware/hardware-supported.xml b/nl/hardware/hardware-supported.xml index 114a88793..eef1e202e 100644 --- a/nl/hardware/hardware-supported.xml +++ b/nl/hardware/hardware-supported.xml @@ -55,13 +55,6 @@ variations of each architecture known as flavors. - - DEC Alpha - alpha - - - - ARM armel @@ -194,7 +187,6 @@ as well. -&supported-alpha.xml; &supported-amd64.xml; &supported-arm.xml; &supported-hppa.xml; diff --git a/nl/hardware/installation-media.xml b/nl/hardware/installation-media.xml index 1a88ecd3e..eff05af38 100644 --- a/nl/hardware/installation-media.xml +++ b/nl/hardware/installation-media.xml @@ -61,15 +61,6 @@ on using CD-ROMs with Linux. USB CD-ROM drives are also supported, as are FireWire devices that are supported by the ohci1394 and sbp2 drivers. - - -Both SCSI and IDE/ATAPI CD-ROMs are supported on &arch-title;, as long -as the controller is supported by the SRM console. This rules out many -add-on controller cards, but most integrated IDE and SCSI chips and -controller cards that were provided by the manufacturer can be expected -to work. To find out whether your device is supported from the SRM -console, see the SRM HOWTO. - IDE/ATAPI CD-ROMs are supported on all ARM machines. @@ -218,15 +209,6 @@ IDE systems (such as the UltraSPARC 5) are also supported. See Linux for SPARC Processors FAQ for more information on SPARC hardware supported by the Linux kernel. - - -Any storage system supported by the Linux kernel is also supported by -the boot system. This includes both SCSI and IDE disks. Note, however, -that on many systems, the SRM console is unable to boot from IDE drives, -and the Jensen is unable to boot from floppies. (see - -for more information on booting the Jensen) - Any storage system supported by the Linux kernel is also supported by diff --git a/nl/hardware/supported/alpha.xml b/nl/hardware/supported/alpha.xml deleted file mode 100644 index 02e0ad4be..000000000 --- a/nl/hardware/supported/alpha.xml +++ /dev/null @@ -1,457 +0,0 @@ - - - - - CPU, Main Boards, and Video Support - - -Complete information regarding supported DEC Alphas can be found at -Linux Alpha HOWTO. The -purpose of this section is to describe the systems supported -by the boot disks. - - - -Alpha machines are subdivided into different system types because there -are a number of generations of motherboard and supporting chipsets. -Different systems (sub-architectures) often have radically -different engineering and capabilities. Therefore, the process of -installing and, more to the point, booting, can vary from system to system. - - - -The following table lists the system types supported by the Debian -installation system. The table also indicates the code -name for these system types. You'll need to know this code -name when you actually begin the installation process: - - - - - - - - - - - - Hardware Type - AliasesMILO image - - - - - - ALCOR - AlphaStation 500 5/266.300 - Maverick - alcor - - AlphaStation 500 5/333...500 - Bret - alcor - - AlphaStation 600/266...300 - Alcor - alcor - - AlphaStation 600/300...433 - XLT - xlt - - - - BOOK1 - AlphaBook1 (laptop) - Alphabook1/Burns - book1 - - - - AVANTI - AlphaStation 200 4/100...166 - Mustang - avanti - - AlphaStation 200 4/233 - Mustang+ - avanti - - AlphaStation 205 4/133...333 - LX3 - avanti - - AlphaStation 250 4/300 - M3+ - avanti - - AlphaStation 255 4/133...333 - LX3+ - avanti - - AlphaStation 300 4/266 - Melmac - avanti - - AlphaStation 400 4/166 - Chinet - avanti - - AlphaStation 400 4/233...300 - Avanti - avanti - - - - EB164 - AlphaPC164 - PC164 - pc164 - - AlphaPC164-LX - LX164 - lx164 - - AlphaPC164-SX - SX164 - sx164 - - EB164 - EB164 - eb164 - - - - EB64+ - AlphaPC64 - Cabriolet - cabriolet - - AlphaPCI64 - Cabriolet - cabriolet - - EB64+ - EB64+ - eb64p - - - - EB66 - EB66 - EB66 - eb66 - - EB66+ - EB66+ - eb66p - - - - JENSEN - DEC 2000 Model 300(S) - Jensen - N/A - - DEC 2000 Model 500 - Culzen - N/A - - DECpc 150 - Jensen - N/A - - - - MIATA - Personal WorkStation 433a - Miata - miata - - Personal WorkStation 433au - Miata - miata - - Personal WorkStation 466au - Miata - miata - - Personal WorkStation 500a - Miata - miata - - Personal WorkStation 500au - Miata - miata - - Personal WorkStation 550au - Miata - miata - - Personal WorkStation 600a - Miata - miata - - Personal WorkStation 600au - Miata - miata - - - - MIKASA - AlphaServer 1000 4/200 - Mikasa - mikasa - - AlphaServer 1000 4/233..266 - Mikasa+ - mikasa - - AlphaServer 1000 5/300 - Mikasa-Pinnacle - mikasa - - AlphaServer 1000 5/300 - Mikasa-Primo - mikasa - - - - NAUTILUS - UP1000 - Nautilus - N/A - - UP1100 - Galaxy-Train/Nautilus Jr. - N/A - - - - NONAME - AXPpci33 - Noname - noname - - UDB - Multia - noname - - - - NORITAKE - AlphaServer 1000A 4/233...266 - Noritake - N/A - - AlphaServer 1000A 5/300 - Noritake-Pinnacle - N/A - - AlphaServer 1000A 5/333...500 - Noritake-Primo - N/A - - AlphaServer 800 5/333...500 - Corelle - N/A - - AlphaStation 600 A - Alcor-Primo - N/A - - Digital Server 3300 - Corelle - N/A - - Digital Server 3300R - Corelle - N/A - - - - PLATFORM 2000 - P2K - P2K - p2k - - - - RAWHIDE - AlphaServer 1200 5/xxx - Tincup/DaVinci - N/A - - AlphaServer 4000 5/xxx - Wrangler/Durango - N/A - - AlphaServer 4100 5/xxx - Dodge - N/A - - Digital Server 5300 - Tincup/DaVinci - N/A - - Digital Server 7300 - Dodge - N/A - - - - RUFFIAN - DeskStation AlphaPC164-UX - Ruffian - ruffian - - DeskStation RPL164-2 - Ruffian - ruffian - - DeskStation RPL164-4 - Ruffian - ruffian - - DeskStation RPX164-2 - Ruffian - ruffian - - DeskStation RPX164-4 - Ruffian - ruffian - - Samsung AlphaPC164-BX - Ruffian - ruffian - - - - SABLE - AlphaServer 2000 4/xxx - Demi-Sable - N/A - - AlphaServer 2000 5/xxx - Demi-Gamma-Sable - N/A - - AlphaServer 2100 4/xxx - Sable - N/A - - AlphaServer 2100 5/xxx - Gamma-Sable - N/A - - - - TAKARA - 21164 PICMG SBC - Takara - takara - - - - TITAN - AlphaServer DS15 - HyperBrick2 - N/A - - AlphaServer DS25 - Granite - N/A - - AlphaServer ES45 - Privateer - N/A - - UNKNOWN - Yukon - N/A - - - - TSUNAMI - AlphaServer DS10 - Webbrick - N/A - - AlphaServer DS10L - Slate - N/A - - AlphaServer DS20 - Catamaran/Goldrush - N/A - - AlphaServer DS20E - Goldrack - N/A - - AlphaServer DS20L - Shark - N/A - - AlphaServer ES40 - Clipper - N/A - - DP264 - DP264 - N/A - - SMARTengine 21264 PCI/ISA SBC - Eiger - N/A - - UNKNOWN - Warhol - N/A - - UNKNOWN - Windjammer - N/A - - UP2000 - Swordfish - N/A - - XP1000 - Monet/Brisbane - N/A - - XP900 - Webbrick - N/A - - - - WILDFIRE - AlphaServer GS160 - Wildfire - N/A - - AlphaServer GS320 - Wildfire - N/A - - - - XL - XL-233...266 - XL - xl - - - - - - -It is believed that Debian &releasename; supports installing on all -alpha sub-architectures with the exception of the ARC-only Ruffian and -XL sub-architectures and the Titan subarchitecture, which requires a -change to the kernel compile options. - - - diff --git a/nl/install-methods/download/alpha.xml b/nl/install-methods/download/alpha.xml deleted file mode 100644 index ff0250415..000000000 --- a/nl/install-methods/download/alpha.xml +++ /dev/null @@ -1,36 +0,0 @@ - - - - - Alpha Installation Files - - -If you choose to boot from ARC console firmware using -MILO, you will also need to prepare a disk -containing MILO and LINLOAD.EXE -from the provided disk images. See -for more information on Alpha -firmware and boot loaders. The floppy images can be found in the -MILO directory as -milo_subarchitecture.bin. - - - -Unfortunately, these MILO images could not be -tested and might not work for all subarchitectures. If you find it -doesn't work for you, try copying the appropriate -MILO binary onto the floppy -(). -Note that those MILOs don't support ext2 sparse -superblocks, so you can't use them to load kernels from newly -generated ext2 file systems. As a workaround, you can put your kernel -onto the FAT partition next to the MILO. - - - -MILO binaries are platform-specific. See - to determine the appropriate -MILO image for your Alpha platform. - - - diff --git a/nl/install-methods/downloading-files.xml b/nl/install-methods/downloading-files.xml index 4cda65819..f833867c1 100644 --- a/nl/install-methods/downloading-files.xml +++ b/nl/install-methods/downloading-files.xml @@ -26,7 +26,6 @@ The installation images are located on each Debian mirror in the directory lists each image and its purpose. -&download-alpha.xml; &download-arm.xml; &download-powerpc.xml; diff --git a/nl/install-methods/install-tftp.xml b/nl/install-methods/install-tftp.xml index 5415c585a..564e772d2 100644 --- a/nl/install-methods/install-tftp.xml +++ b/nl/install-methods/install-tftp.xml @@ -38,23 +38,6 @@ For PowerPC, if you have a NewWorld Power Macintosh machine, it is a good idea to use DHCP instead of BOOTP. Some of the latest machines are unable to boot using BOOTP. - - -Unlike the Open Firmware found on Sparc and PowerPC machines, the SRM -console will not use RARP to obtain its IP -address, and therefore you must use BOOTP for net booting your -Alpha - - -Alpha systems can also be net-booted using the DECNet MOP (Maintenance -Operations Protocol), but this is not covered here. Presumably, your -local OpenVMS operator will be happy to assist you should you have -some burning need to use MOP to boot Linux on your Alpha. - - -. You can also enter the IP configuration for network -interfaces directly in the SRM console. - Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. @@ -221,22 +204,6 @@ to tftpd as the filename to boot. - - Alpha TFTP Booting - -On Alpha, you must specify the filename (as a relative path to the -boot image directory) using the -file argument -to the SRM boot command, or by setting the -BOOT_FILE environment variable. Alternatively, -the filename can be given via BOOTP (in ISC dhcpd, -use the filename directive). Unlike Open -Firmware, there is no default filename on SRM, so -you must specify a filename by either one of -these methods. - - - - SPARC TFTP Booting diff --git a/nl/partitioning/partition-programs.xml b/nl/partitioning/partition-programs.xml index cb3574ec2..d7c1ab9e1 100644 --- a/nl/partitioning/partition-programs.xml +++ b/nl/partitioning/partition-programs.xml @@ -128,7 +128,6 @@ includes steps you should take if you are sharing your disk with MacOS. -&partition-alpha.xml; &partition-hppa.xml; &partition-x86.xml; &partition-ia64.xml; diff --git a/nl/partitioning/partition/alpha.xml b/nl/partitioning/partition/alpha.xml deleted file mode 100644 index 965ee8602..000000000 --- a/nl/partitioning/partition/alpha.xml +++ /dev/null @@ -1,59 +0,0 @@ - - - - - Partitioning for &arch-title; - - -Booting Debian from the SRM console (the only disk boot method supported -by &releasename;) requires you to have a BSD disk label, not a DOS -partition table, on your boot disk. (Remember, the SRM boot block is -incompatible with MS-DOS partition tables — see -.) As a result, partman -creates BSD disk labels when running on &architecture;, but if your disk -has an existing DOS partition table the existing partitions will need to be -deleted before partman can convert it to use a disk label. - - - -If you have chosen to use fdisk to partition your -disk, and the disk that you have selected for partitioning does not -already contain a BSD disk label, you must use the b -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), 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. - - - -Also, because aboot is written to the first few -sectors of the disk (currently it occupies about 70 kilobytes, or 150 -sectors), you must leave enough empty space at -the beginning of the disk for it. In the past, it was suggested that -you make a small partition at the beginning of the disk, to be left -unformatted. For the same reason mentioned above, we now suggest that -you do not do this on disks that will only be used by GNU/Linux. When -using partman, a small partition will still be -created for aboot for convenience reasons. - - - -For ARC installations, you should make a small FAT partition at the -beginning of the disk to contain MILO and -linload.exe — 5 megabytes should be sufficient, see -. Unfortunately, making FAT -file systems from the menu is not yet supported, so you'll have to do -it manually from the shell using mkdosfs before -attempting to install the boot loader. - - - diff --git a/nl/preparing/needed-info.xml b/nl/preparing/needed-info.xml index 939942953..0aa9f9960 100644 --- a/nl/preparing/needed-info.xml +++ b/nl/preparing/needed-info.xml @@ -46,19 +46,13 @@ Bevat vaak bruikbare informatie over de configuratie of het gebruik van uw hardware. - + Linux Hardware Compatibility HOWTO - - -Linux/Alpha FAQ - - - Linux for SPARC Processors FAQ diff --git a/nl/preparing/non-debian-partitioning.xml b/nl/preparing/non-debian-partitioning.xml index f801478d3..349578cf6 100644 --- a/nl/preparing/non-debian-partitioning.xml +++ b/nl/preparing/non-debian-partitioning.xml @@ -24,10 +24,6 @@ Als er al een besturingssysteem op uw systeem aanwezig is (Windows 9x, Windows NT/2000/XP, OS/2, MacOS, Solaris, FreeBSD, …) - -(Tru64 (Digital UNIX), OpenVMS, Windows NT, FreeBSD, …) - - (VM, z/OS, OS/390, …) @@ -192,7 +188,6 @@ van Debian. -&nondeb-part-alpha.xml; &nondeb-part-x86.xml; &nondeb-part-sparc.xml; &nondeb-part-powerpc.xml; diff --git a/nl/preparing/nondeb-part/alpha.xml b/nl/preparing/nondeb-part/alpha.xml deleted file mode 100644 index 38d1c5c15..000000000 --- a/nl/preparing/nondeb-part/alpha.xml +++ /dev/null @@ -1,83 +0,0 @@ - - - - - Partitioning in Tru64 UNIX - - -Tru64 UNIX, formerly known as Digital UNIX, which is in turn formerly -known as OSF/1, uses the partitioning scheme similar to the BSD disk -label, which allows for up to eight partitions per disk drive. The -partitions are numbered 1 through to 8 in -Linux and lettered a through to -h in UNIX. Linux kernels 2.2 and higher always correspond -1 to a, 2 to b -and so on. For example, rz0e in Tru64 UNIX would most -likely be called sda5 in Linux. - - - -Partitions in a Tru64 disk label may overlap. Moreover, if this disk -will be used from Tru64, the c partition is required to span -the entire disk (thus overlapping all other non-empty partitions). Under -Linux this makes sda3 identical to -sda (sdb3 to -sdb, if present, and so on). However, the partman -partitioning tool used by &d-i; cannot handle overlapping partitions at -present. As a result, it is currently not recommended to share disks -between Tru64 and Debian. Partitions on Tru64 disks can be mounted -under Debian after installation has been completed. - - - -Another conventional requirement is for the a partition to -start from the beginning of the disk, so that it always includes the boot -block with the disk label. If you intend to boot Debian from that disk, you -need to size it at least 2MB to fit aboot and perhaps a kernel. -Note that this partition is only required for compatibility; you must -not put a file system onto it, or you'll destroy data. - - - -It is possible, and indeed quite reasonable, to share a swap partition -between UNIX and Linux. In this case it will be needed to do a -mkswap on that partition every time the system is rebooted -from UNIX into Linux, as UNIX will damage the swap signature. You may -want to run mkswap from the Linux start-up scripts before -adding swap space with swapon -a. - - - -If you want to mount UNIX partitions under Linux, note that Digital UNIX -can use two different file system types, UFS and AdvFS, of which Linux -only understands the former. - - - - - Partitioning in Windows NT - - - -Windows NT uses the PC-style partition table. If you are manipulating -existing FAT or NTFS partitions, it is recommended that you use the -native Windows NT tools (or, more conveniently, you can also -repartition your disk from the AlphaBIOS setup menu). Otherwise, it -is not really necessary to partition from Windows; the Linux -partitioning tools will generally do a better job. Note that when you -run NT, the Disk Administrator may offer to write a harmless -signature on non-Windows disks if you have any. -Never let it do that, as this signature will destroy -the partition information. - - - -If you plan to boot Linux from an ARC/AlphaBIOS/ARCSBIOS console, you -will need a (small) FAT partition for MILO. 5 MB is quite -sufficient. If Windows NT is installed, its 6 MB bootstrap partition -can be employed for this purpose. Debian &releasename; does not support -installing MILO. If you already have MILO installed on your system, or -install MILO from other media, Debian can still be booted from ARC. - - - diff --git a/nl/using-d-i/components.xml b/nl/using-d-i/components.xml index cf357c551..c06f72e8f 100644 --- a/nl/using-d-i/components.xml +++ b/nl/using-d-i/components.xml @@ -147,7 +147,6 @@ linkend="boot-dev-select-sun"/>. &module-os-prober.xml; -&module-alpha-aboot-installer.xml; &module-hppa-palo-installer.xml; &module-x86-grub-installer.xml; &module-x86-lilo-installer.xml; diff --git a/nl/using-d-i/modules/alpha/aboot-installer.xml b/nl/using-d-i/modules/alpha/aboot-installer.xml deleted file mode 100644 index ce069fd1b..000000000 --- a/nl/using-d-i/modules/alpha/aboot-installer.xml +++ /dev/null @@ -1,19 +0,0 @@ - - - - - Install <command>aboot</command> on a Hard Disk - - -If you have booted from SRM and you select this option, the installer -will write aboot to the first sector of the disk on -which you installed Debian. Be very careful — it -is not possible to boot multiple operating -systems (e.g. GNU/Linux, Free/Open/NetBSD, OSF/1 a.k.a. Digital Unix -a.k.a. Tru64 Unix, or OpenVMS) from the same disk. If you also have a -different operating system installed on the disk where you have -installed Debian, you will have to boot GNU/Linux from a floppy -instead. - - - diff --git a/nl/using-d-i/modules/partman.xml b/nl/using-d-i/modules/partman.xml index b9097322d..66765691b 100644 --- a/nl/using-d-i/modules/partman.xml +++ b/nl/using-d-i/modules/partman.xml @@ -101,13 +101,6 @@ worden aangemaakt ten behoeve van de EFI-opstartlader. Er is ook een aanvullende menuoptie in het keuzemenu met formateeropties om handmatig een EFI-opstartpartitie te kunnen aanmaken. - - -Als u voor uw Alpha systeem kiest voor begeleide schijfindeling, zal een -extra, niet-geformatteerde partitie worden aangemaakt aan het begin van -uw harde schijf om deze schijfruimte te reserveren voor de opstartlader -aboot. - Nadat u een schema heeft geselecteerd, zal op het volgende scherm de -- cgit v1.2.3