From 1ea73eea5ecc6a8ed901316049259aee737ee554 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 7 Oct 2005 19:51:38 +0000 Subject: move manual to top-level directory, split out of debian-installer package --- it/preparing/nondeb-part/alpha.xml | 85 +++++++++++++++++++++++ it/preparing/nondeb-part/i386.xml | 120 ++++++++++++++++++++++++++++++++ it/preparing/nondeb-part/m68k.xml | 129 +++++++++++++++++++++++++++++++++++ it/preparing/nondeb-part/powerpc.xml | 43 ++++++++++++ it/preparing/nondeb-part/sparc.xml | 45 ++++++++++++ 5 files changed, 422 insertions(+) create mode 100644 it/preparing/nondeb-part/alpha.xml create mode 100644 it/preparing/nondeb-part/i386.xml create mode 100644 it/preparing/nondeb-part/m68k.xml create mode 100644 it/preparing/nondeb-part/powerpc.xml create mode 100644 it/preparing/nondeb-part/sparc.xml (limited to 'it/preparing/nondeb-part') diff --git a/it/preparing/nondeb-part/alpha.xml b/it/preparing/nondeb-part/alpha.xml new file mode 100644 index 000000000..f118f3cb6 --- /dev/null +++ b/it/preparing/nondeb-part/alpha.xml @@ -0,0 +1,85 @@ + + + + + + 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 you 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/it/preparing/nondeb-part/i386.xml b/it/preparing/nondeb-part/i386.xml new file mode 100644 index 000000000..b89864d7e --- /dev/null +++ b/it/preparing/nondeb-part/i386.xml @@ -0,0 +1,120 @@ + + + + + Partitioning From DOS or Windows + + +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. + + + +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. + + + + + Lossless Repartitioning When Starting From DOS, Win-32 or OS/2 + + + + +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 Manually +edit partition table , select the partition to +resize, and specify its new size. +So in most cases you should not need to use the method described below. + + + +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. + + + +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. + + + +The first thing needed is a copy of fips which is +available in the tools/ directory on your nearest Debian +mirror. Unzip the archive and copy the files +RESTORRB.EXE, FIPS.EXE and +ERRORS.TXT to a bootable floppy. A bootable floppy can +be created using the command sys a: under DOS. +fips 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 before you defragment the disk. + + + +The next thing needed is to move all the data to the beginning of the +partition. defrag, which comes standard with DOS 6.0 and +later, can easily do the job. See the fips documentation +for a list of other software that may do the trick. Note that if you +have Windows 9x, you must run defrag from there, since +DOS doesn't understand VFAT, which is used to support for long +filenames, used in Windows 95 and higher. + + + +After running the defragmenter (which can take a while on a large +disk), reboot with the fips disk you created in the +floppy drive. Simply type a:\fips and follow the directions. + + + +Note that there are many other partition managers out there, in +case fips doesn't do the trick for you. + + + + + Partitioning for DOS + + + +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 scandisk, or +other weird errors in DOS or Windows. + + + +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 format command, from Linux: + + +# dd if=/dev/zero of=/dev/hdXX bs=512 count=4 + + + + + diff --git a/it/preparing/nondeb-part/m68k.xml b/it/preparing/nondeb-part/m68k.xml new file mode 100644 index 000000000..28a375c81 --- /dev/null +++ b/it/preparing/nondeb-part/m68k.xml @@ -0,0 +1,129 @@ + + + + + + Partitioning in AmigaOS + + +If you are running AmigaOS, you can use the HDToolBox +program to adjust your native partitions prior to installation. + + + + + + Partitioning in Atari TOS + + +Atari partition IDs are three ASCII characters, use LNX for +data and SWP 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 MNX. 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. + + + +There are a multitude of third party partitioning tools available (the +Atari harddisk utility doesn't permit changing the +partition ID); this manual cannot give detailed descriptions for all +of them. The following description covers SCSITool (from +Hard+Soft GmBH). + + + + +Start SCSITool and select the disk you want to partition +(Disk menu, item select). + + + + +From the Partition menu, select either +New to add new partitions or change the +existing partition sizes, or Change to +change one specific partition. Unless you have already created +partitions with the right sizes and only want to change the partition +ID, New is probably the best choice. + + + + +For the New choice, select +existing 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 OK button. + + + + +For the Change option, select the partition +to change in the selection list, and select other +systems 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 OK button. + + + + +Write down the Linux names for each of the partitions you created or +changed for use with Linux — see . + + + + +Quit SCSITool using the +Quit item from the File +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?). + + + + + + +There is a partitioning tool for Linux/m68k called +atari-fdisk 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). SCSITool 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. + + + + + + Partitioning in MacOS + + +Partitioning tools for Macintosh tested include pdisk, +HD SC Setup 7.3.5 (Apple), HDT 1.8 (FWB), +SilverLining (LaCie), and DiskTool (Tim +Endres, GPL). Full versions are required for HDT and +SilverLining. The Apple tool requires a patch in order +to recognize third-party disks (a description on how to patch HD +SC Setup using ResEdit can be found at +). + + + +For IDE based Macs, you need to use Apple Drive Setup 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. + + + diff --git a/it/preparing/nondeb-part/powerpc.xml b/it/preparing/nondeb-part/powerpc.xml new file mode 100644 index 000000000..8b70dc6a3 --- /dev/null +++ b/it/preparing/nondeb-part/powerpc.xml @@ -0,0 +1,43 @@ + + + + + MacOS/OSX Partitioning + + + +The Apple Drive Setup application can be found in the +Utilities 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 Drive Setup. + + + +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. + + + +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, Startup Disk (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 option key at boot time, and separate +options can be installed in the yaboot 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. + + + +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. + + + diff --git a/it/preparing/nondeb-part/sparc.xml b/it/preparing/nondeb-part/sparc.xml new file mode 100644 index 000000000..f508f2169 --- /dev/null +++ b/it/preparing/nondeb-part/sparc.xml @@ -0,0 +1,45 @@ + + + + + + Partitioning from SunOS + + +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. + + + + + + Partitioning from Linux or another OS + + + +Whatever system you are using to partition, make sure you create a +Sun disk label 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 fdisk, the +s 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. + + + +You will probably be using SILO as your boot loader (the +small program which runs the operating system kernel). +SILO has certain requirements for partition sizes and +location; see . + + + -- cgit v1.2.3