move manual to top-level directory, split out of debian-installer package

5 files changed, 417 insertions, 0 deletions

diff --git a/nl/preparing/nondeb-part/alpha.xml b/nl/preparing/nondeb-part/alpha.xml
new file mode 100644
index 000000000..de065da6d
--- /dev/null
+++ b/nl/preparing/nondeb-part/alpha.xml
@@ -0,0 +1,83 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 28997 untranslated -->
+
+
+  <sect2 arch="alpha"><title>Partitioning in Tru64 UNIX</title>
+<para>
+
+Tru64 UNIX, formerly known as Digital UNIX, which is in turn formerly
+known as OSF/1, uses the partitioning scheme similar to the BSD <quote>disk
+label</quote>, which allows for up to eight partitions per disk drive.  The
+partitions are numbered <quote>1</quote> through to <quote>8</quote> in
+Linux and <quote>lettered</quote> <quote>a</quote> through to
+<quote>h</quote> in UNIX.  Linux kernels 2.2 and higher always correspond
+<quote>1</quote> to <quote>a</quote>, <quote>2</quote> to <quote>b</quote>
+and so on.  For example, <filename>rz0e</filename> in Tru64 UNIX would most
+likely be called <filename>sda5</filename> in Linux.
+
+</para><para>
+
+Partitions in a Tru64 disk label may overlap.  Moreover, if this disk
+will be used from Tru64, the <quote>c</quote> partition is required to span
+the entire disk (thus overlapping all other non-empty partitions).  Under
+Linux this makes <filename>sda3</filename> identical to
+<filename>sda</filename> (<filename>sdb3</filename> to
+<filename>sdb</filename>, 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.
+
+</para><para>
+
+Another conventional requirement is for the <quote>a</quote> 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.
+
+</para><para>
+
+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
+<command>mkswap</command> 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 <command>mkswap</command> from the Linux start-up scripts before
+adding swap space with <command>swapon -a</command>.
+
+</para><para>
+
+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.
+
+</para>
+  </sect2>
+
+  <sect2 arch="alpha"><title>Partitioning in Windows NT</title>
+
+<para>
+
+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 you to write a <quote>harmless
+signature</quote> on non-Windows disks if you have any.
+<emphasis>Never</emphasis> let it do that, as this signature will destroy
+the partition information.
+
+</para><para>
+
+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.
+
+</para>
+  </sect2>
diff --git a/nl/preparing/nondeb-part/i386.xml b/nl/preparing/nondeb-part/i386.xml
new file mode 100644
index 000000000..b89864d7e
--- /dev/null
+++ b/nl/preparing/nondeb-part/i386.xml
@@ -0,0 +1,120 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 29561 untranslated -->
+
+
+  <sect2 arch="i386"><title>Partitioning From DOS or Windows</title>
+<para>
+
+If you are manipulating existing FAT or NTFS partitions, it is
+recommended that you either use the scheme below or native Windows or
+DOS tools.  Otherwise, it is not really necessary to partition from DOS
+or Windows; the Linux partitioning tools will generally do a better
+job.
+
+</para><para>
+
+But if you have a large IDE disk, and are using neither LBA addressing,
+overlay drivers (sometimes provided by hard disk manufacturers), nor a
+new (post 1998) BIOS that supports large disk access extensions, then
+you must locate your Debian boot partition carefully. In this case,
+you will have to put the boot partition into the first 1024 cylinders
+of your hard drive (usually around 524 megabytes, without BIOS
+translation). This may require that you move an existing FAT or NTFS
+partition.
+
+</para>
+
+   <sect3 id="lossless">
+   <title>Lossless Repartitioning When Starting From DOS, Win-32 or OS/2
+   </title>
+
+<para>
+
+One of the most common installations is onto a system that already
+contains DOS (including Windows 3.1), Win32 (such as Windows 95, 98, Me,
+NT, 2000, XP), or OS/2, and it is desired to put Debian onto the same disk
+without destroying the previous system. Note that the installer supports
+resizing of FAT and NTFS filesystems as used by DOS and Windows. Simply
+start the installer, select the option to <menuchoice> <guimenuitem>Manually
+edit partition table</guimenuitem> </menuchoice>, select the partition to
+resize, and specify its new size.
+So in most cases you should not need to use the method described below.
+
+</para><para>
+
+Before going any further, you should have decided how you will be
+dividing up the disk. The method in this section will only split a
+partition into two pieces. One will contain the original OS and the
+other will be used for Debian.  During the installation of Debian, you
+will be given the opportunity to use the Debian portion of the disk as you
+see fit, i.e., as swap or as a file system.
+
+</para><para>
+
+The idea is to move all the data on the partition to the beginning,
+before changing the partition information, so that nothing will be
+lost.  It is important that you do as little as possible between the
+data movement and repartitioning to minimize the chance of a file
+being written near the end of the partition as this will decrease the
+amount of space you can take from the partition.
+
+</para><para>
+
+The first thing needed is a copy of <command>fips</command> which is
+available in the <filename>tools/</filename> directory on your nearest Debian
+mirror. Unzip the archive and copy the files
+<filename>RESTORRB.EXE</filename>, <filename>FIPS.EXE</filename> and
+<filename>ERRORS.TXT</filename> to a bootable floppy.  A bootable floppy can
+be created using the command <filename>sys a:</filename> under DOS.
+<command>fips</command> comes with very good documentation which you may
+want to read.  You will definitely need to read the documentation if
+you use a disk compression driver or a disk manager.  Create the disk
+and read the documentation <emphasis>before</emphasis> you defragment the disk.
+
+</para><para>
+
+The next thing needed is to move all the data to the beginning of the
+partition. <command>defrag</command>, which comes standard with DOS 6.0 and
+later, can easily do the job.  See the <command>fips</command> documentation
+for a list of other software that may do the trick.  Note that if you
+have Windows 9x, you must run <command>defrag</command> from there, since
+DOS doesn't understand VFAT, which is used to support for long
+filenames, used in Windows 95 and higher.
+
+</para><para>
+
+After running the defragmenter (which can take a while on a large
+disk), reboot with the <command>fips</command> disk you created in the
+floppy drive.  Simply type <filename>a:\fips</filename> and follow the directions.
+
+</para><para>
+
+Note that there are many other partition managers out there, in
+case <command>fips</command> doesn't do the trick for you.
+
+</para>
+   </sect3>
+
+   <sect3 id="partitioning-for-dos"><title>Partitioning for DOS</title>
+
+<para>
+
+If you are partitioning for DOS drives, or changing the size of DOS
+partitions, using Linux tools, many people experience problems working
+with the resulting FAT partitions.  For instance, some have reported
+slow performance, consistent problems with <command>scandisk</command>, or
+other weird errors in DOS or Windows.
+
+</para><para>
+
+Apparently, whenever you create or resize a partition for DOS use,
+it's a good idea to fill the first few sectors with zeros.  Do this
+prior to running DOS's <command>format</command> command, from Linux:
+
+<informalexample><screen>
+# dd if=/dev/zero of=/dev/hdXX bs=512 count=4
+</screen></informalexample>
+
+</para>
+   </sect3>
+  </sect2>
diff --git a/nl/preparing/nondeb-part/m68k.xml b/nl/preparing/nondeb-part/m68k.xml
new file mode 100644
index 000000000..dbea5b44e
--- /dev/null
+++ b/nl/preparing/nondeb-part/m68k.xml
@@ -0,0 +1,127 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 28997 untranslated -->
+
+
+  <sect2 arch="m68k"><title>Partitioning in AmigaOS</title>
+<para>
+
+If you are running AmigaOS, you can use the <command>HDToolBox</command>
+program to adjust your native partitions prior to installation.
+
+</para>
+  </sect2>
+
+  <sect2 arch="m68k"><title>Partitioning in Atari TOS</title>
+<para>
+
+Atari partition IDs are three ASCII characters, use <quote>LNX</quote> for
+data and <quote>SWP</quote> for swap partitions. If using the low memory
+installation method, a small Minix partition is also needed (about 2 MB),
+for which the partition ID is <quote>MNX</quote>.  Failure to set the
+appropriate partition IDs not only prevents the Debian installation process
+from recognizing the partitions, but also results in TOS attempting to use
+the Linux partitions, which confuses the hard disk driver and renders the
+whole disk inaccessible.
+
+</para><para>
+
+There are a multitude of third party partitioning tools available (the
+Atari <command>harddisk</command> utility doesn't permit changing the
+partition ID); this manual cannot give detailed descriptions for all
+of them. The following description covers <command>SCSITool</command> (from
+Hard+Soft GmBH).
+
+<orderedlist>
+<listitem><para>
+
+Start <command>SCSITool</command> and select the disk you want to partition
+(<guimenu>Disk</guimenu> menu, item <guimenuitem>select</guimenuitem>).
+
+</para></listitem>
+<listitem><para>
+
+From the <guimenu>Partition</guimenu> menu, select either
+<guimenuitem>New</guimenuitem> to add new partitions or change the
+existing partition sizes, or <guimenuitem>Change</guimenuitem> to
+change one specific partition.  Unless you have already created
+partitions with the right sizes and only want to change the partition
+ID, <guimenuitem>New</guimenuitem> is probably the best choice.
+
+</para></listitem>
+<listitem><para>
+
+For the <guimenuitem>New</guimenuitem> choice, select
+<guilabel>existing</guilabel> in the dialog box
+prompting the initial settings. The next window shows a list of
+existing partitions which you can adjust using the scroll buttons, or
+by clicking in the bar graphs. The first column in the partition list
+is the partition type; just click on the text field to edit it.  When
+you are finished changing partition settings, save the changes by
+leaving the window with the <guibutton>OK</guibutton> button.
+
+</para></listitem>
+<listitem><para>
+
+For the <guimenuitem>Change</guimenuitem> option, select the partition
+to change in the selection list, and select <guilabel>other
+systems</guilabel> in the dialog box.  The
+next window lists detailed information about the location of this
+partition, and lets you change the partition ID.  Save changes by
+leaving the window with the <guibutton>OK</guibutton> button.
+
+</para></listitem>
+<listitem><para>
+
+Write down the Linux names for each of the partitions you created or
+changed for use with Linux &mdash; see <xref linkend="device-names"/>.
+
+</para></listitem>
+<listitem><para>
+
+Quit <command>SCSITool</command> using the
+<guimenuitem>Quit</guimenuitem> item from the <guimenu>File</guimenu>
+menu.  The computer will reboot to make sure the changed partition
+table is used by TOS. If you changed any TOS/GEM partitions, they will
+be invalidated and have to be reinitialized (we told you to back up
+everything on the disk, didn't we?).
+
+</para></listitem>
+</orderedlist>
+
+</para><para>
+
+There is a partitioning tool for Linux/m68k called
+<command>atari-fdisk</command> in the installation system, but for now we
+recommend you partition your disk using a TOS partition editor or some
+disk tool. If your partition editor doesn't have an option to edit the
+partition type, you can do this crucial step at a later stage (from
+the booted temporary install RAMdisk).  <command>SCSITool</command> is only
+one of the partition editors we know of which supports selection of
+arbitrary partition types. There may be others; select the tool that
+suits your needs.
+
+</para>
+</sect2>
+
+  <sect2 arch="m68k"><title>Partitioning in MacOS</title>
+<para>
+
+Partitioning tools for Macintosh tested include <command>pdisk</command>,
+<command>HD SC Setup</command> 7.3.5 (Apple), <command>HDT</command> 1.8 (FWB),
+<command>SilverLining</command> (LaCie), and <command>DiskTool</command> (Tim
+Endres, GPL). Full versions are required for <command>HDT</command> and
+<command>SilverLining</command>. The Apple tool requires a patch in order
+to recognize third-party disks (a description on how to patch <command>HD
+SC Setup</command> using <command>ResEdit</command> can be found at
+<ulink url="http://www.euronet.nl/users/ernstoud/patch.html"></ulink>).
+
+</para><para>
+
+For IDE based Macs, you need to use <command>Apple Drive Setup</command> to create
+empty space for the Linux partitions, and complete the partitioning under
+Linux, or use the MacOS version of pdisk available from the MkLinux FTP
+server.
+
+</para>
+</sect2>
+
diff --git a/nl/preparing/nondeb-part/powerpc.xml b/nl/preparing/nondeb-part/powerpc.xml
new file mode 100644
index 000000000..8b70dc6a3
--- /dev/null
+++ b/nl/preparing/nondeb-part/powerpc.xml
@@ -0,0 +1,43 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 28672 untranslated -->
+
+
+  <sect2 arch="powerpc"><title>MacOS/OSX Partitioning</title>
+
+<para>
+
+The <application>Apple Drive Setup</application> application can be found in the
+<filename>Utilities</filename> folder on the MacOS CD. It will not adjust existing
+partitions; it is limited to partitioning the entire disk at once. The
+disk driver partitions don't show up in <application>Drive Setup</application>.
+
+</para><para>
+
+Remember to create a placeholder partition for GNU/Linux, preferably
+positioned first in the disk layout. it doesn't matter what type it
+is, it will be deleted and replaced later inside the &debian; installer.
+
+</para><para>
+
+If you are planning to install both MacOS 9 and OS X, it is best to
+create separate partitions for OS 9 and OS X. If they are installed on
+the same partition, <application>Startup Disk</application> (and reboot) must be used to select
+between the two; the choice between the two systems can't be made at
+boot time. With separate partitions, separate options for OS 9 and OS
+X will appear when holding the <keycap>option</keycap> key at boot time, and separate
+options can be installed in the <application>yaboot</application> boot menu as well. Also,
+Startup Disk will de-bless all other mountable partitions, which can
+affect GNU/Linux booting. Both OS 9 and OS X partitions will be
+accessible from either OS 9 or OS X.
+
+</para><para>
+
+GNU/Linux is unable to access information on UFS partitions, but does
+support HFS+ (aka MacOS Extended) partitions. OS X requires one of these
+two types for its boot partition. MacOS 9 can be installed on either HFS
+(aka MacOS Standard) or HFS+. To share information between the MacOS and
+GNU/Linux systems, an exchange partition is handy. HFS, HFS+ and MS-DOS FAT
+partitions are supported by both MacOS and Linux.
+
+</para>
+  </sect2>
diff --git a/nl/preparing/nondeb-part/sparc.xml b/nl/preparing/nondeb-part/sparc.xml
new file mode 100644
index 000000000..9bcc1239b
--- /dev/null
+++ b/nl/preparing/nondeb-part/sparc.xml
@@ -0,0 +1,44 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 28997 untranslated -->
+
+
+  <sect2 arch="sparc"><title>Partitioning from SunOS</title>
+
+<para>
+
+It's perfectly fine to partition from SunOS; in fact, if you intend to
+run both SunOS and Debian on the same machine, it is recommended that
+you partition using SunOS prior to installing Debian.  The Linux
+kernel understands Sun disk labels, so there are no problems there.
+Just make sure you leave room for the Debian root partition within the
+first 1GB area of the boot disk. You can also place the kernel image on a
+UFS partition if that is easier than putting the root partition there.
+SILO supports booting Linux and SunOS from either EXT2 (Linux), UFS
+(SunOS), romfs and iso9660 (CDROM) partitions.
+
+</para>
+  </sect2>
+
+  <sect2 arch="sparc"><title>Partitioning from Linux or another OS</title>
+
+<para>
+
+Whatever system you are using to partition, make sure you create a
+<quote>Sun disk label</quote> on your boot disk.  This is the only kind of
+partition scheme that the OpenBoot PROM understands, and so it's the
+only scheme from which you can boot.  In <command>fdisk</command>, the
+<keycap>s</keycap> key is used to create Sun disk labels. You only need to do this
+on drives that do not already have a Sun disk label. If you are using a
+drive that was previously formatted using a PC (or other architecture) you
+must create a new disk label, or problems with the disk geometry will most
+likely occur.
+
+</para><para>
+
+You will probably be using <command>SILO</command> as your boot loader (the
+small program which runs the operating system kernel).
+<command>SILO</command> has certain requirements for partition sizes and
+location; see <xref linkend="partitioning"/>.
+
+</para>
+  </sect2>