From 549410e15b28137b76dc86e32ca5935d8000e8d0 Mon Sep 17 00:00:00 2001 From: Frans Pop Date: Sun, 30 Jul 2006 15:03:12 +0000 Subject: More corrections suggested by Clytie Siddall --- en/partitioning/partition-programs.xml | 2 +- en/partitioning/partition/alpha.xml | 4 ++-- en/partitioning/partition/i386.xml | 5 +++-- en/partitioning/partition/ia64.xml | 17 ++++++----------- en/partitioning/schemes.xml | 2 +- en/partitioning/tree.xml | 12 ++++++------ 6 files changed, 19 insertions(+), 23 deletions(-) (limited to 'en') diff --git a/en/partitioning/partition-programs.xml b/en/partitioning/partition-programs.xml index 8cd19e989..6514f910d 100644 --- a/en/partitioning/partition-programs.xml +++ b/en/partitioning/partition-programs.xml @@ -38,7 +38,7 @@ Be careful if you have existing FreeBSD partitions on your machine. The installation kernels include support for these partitions, but the way that fdisk represents them (or not) can make the device names differ. See the -Linux+FreeBSD HOWTO +Linux+FreeBSD HOWTO. diff --git a/en/partitioning/partition/alpha.xml b/en/partitioning/partition/alpha.xml index 54378128a..50621edb9 100644 --- a/en/partitioning/partition/alpha.xml +++ b/en/partitioning/partition/alpha.xml @@ -11,8 +11,8 @@ 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. +has an existing DOS partition table the existing partitions will need to be +deleted before partman can convert it to use a disk label. diff --git a/en/partitioning/partition/i386.xml b/en/partitioning/partition/i386.xml index 3f32729bb..52ce988ac 100644 --- a/en/partitioning/partition/i386.xml +++ b/en/partitioning/partition/i386.xml @@ -9,8 +9,9 @@ If you have an existing other operating system such as DOS or Windows and you want to preserve that operating system while installing Debian, you may need to resize its partition to free up space for the Debian installation. The installer supports resizing of both FAT and NTFS filesystems; when you -get to the installer's partitioning step, select the option to partition -manually and then simply select an existing partition and change its size. +get to the installer's partitioning step, select the option +Manually edit partition table and then simply +select an existing partition and change its size. diff --git a/en/partitioning/partition/ia64.xml b/en/partitioning/partition/ia64.xml index b7dc396ef..c319f6d06 100644 --- a/en/partitioning/partition/ia64.xml +++ b/en/partitioning/partition/ia64.xml @@ -3,15 +3,14 @@ Partitioning for &arch-title; - The partman disk partitioner is the default partitioning tool for the installer. It manages the set of partitions and their mount points to ensure -that the disks and filesystems is properly configured for a successful -installation. It actually uses the parted to -do the on-disk partitioning. +that the disks and filesystems are properly configured for a successful +installation. It actually uses parted to do the +on-disk partitioning. @@ -22,8 +21,8 @@ do the on-disk partitioning. The IA64 EFI firmware supports two partition table (or disk label) formats, GPT and MS-DOS. MS-DOS, the format typically used on i386 PCs, is no longer recommended for IA64 systems. Although -the installer also provides the cfdisk, -you should only use the +the installer also provides cfdisk, +you should only use parted because only it can manage both GPT and MS-DOS tables correctly. @@ -71,7 +70,6 @@ complete, as it scans the partition for bad blocks. Boot Loader Partition Requirements - ELILO, the ia64 boot loader, requires a partition containing a FAT @@ -102,11 +100,9 @@ It is strongly recommended that you allocate the EFI boot partition on the same disk as the root filesystem. - EFI Diagnostic Partitions - The EFI firmware is significantly more sophisticated than the usual @@ -121,5 +117,4 @@ The easiest time to set up a diagnostics partition is at the same time you set up the EFI boot partition. - - + diff --git a/en/partitioning/schemes.xml b/en/partitioning/schemes.xml index 6924cc3e7..e1297d1d9 100644 --- a/en/partitioning/schemes.xml +++ b/en/partitioning/schemes.xml @@ -28,7 +28,7 @@ you plan to install many programs that are not part of the Debian distribution. If your machine will be a mail server, you might need to make /var/mail a separate partition. Often, putting /tmp on its own partition, for instance -20 to 50MB, is a good idea. If you are setting up a server with lots +20–50MB, is a good idea. If you are setting up a server with lots of user accounts, it's generally good to have a separate, large /home partition. In general, the partitioning situation varies from computer to computer depending on its uses. diff --git a/en/partitioning/tree.xml b/en/partitioning/tree.xml index 76a0f0994..352365afd 100644 --- a/en/partitioning/tree.xml +++ b/en/partitioning/tree.xml @@ -94,7 +94,7 @@ The root partition / must always physically contain /etc, /bin, /sbin, /lib and /dev, otherwise you won't be able to boot. -Typically 150–250 MB is needed for the root partition. +Typically 150–250MB is needed for the root partition. @@ -104,10 +104,10 @@ Typically 150–250 MB is needed for the root partition. (/usr/lib), documentation (/usr/share/doc), etc. This is the part of the file system that generally takes up most space. -You should provide at least 500 MB of disk space. This amount should +You should provide at least 500MB of disk space. This amount should be increased depending on the number and type of packages you plan to install. A generous workstation or server installation should allow -4-6 GB. +4–6GB. @@ -118,7 +118,7 @@ under this directory. The size of this directory depends greatly on the usage of your system, but for most people will be dictated by the package management tool's overhead. If you are going to do a full installation of just about everything Debian has to offer, all in one -session, setting aside 2 or 3 gigabyte of space for +session, setting aside 2 or 3 GB of space for /var should be sufficient. If you are going to install in pieces (that is to say, install services and utilities, followed by text stuff, then X, ...), you can get away with 300–500 @@ -129,7 +129,7 @@ major system updates, you can get by with as little as 30 or 40 MB. /tmp: temporary data created by programs will -most likely go in this directory. 40–100 MB should usually +most likely go in this directory. 40–100MB should usually be enough. Some applications — including archive manipulators, CD/DVD authoring tools, and multimedia software — may use /tmp to temporarily store image files. If you @@ -143,7 +143,7 @@ in /tmp accordingly. into a subdirectory of this directory. Its size depends on how many users will be using the system and what files are to be stored in their directories. Depending on your planned usage you should reserve -about 100 MB for each user, but adapt this value to your needs. Reserve +about 100MB for each user, but adapt this value to your needs. Reserve a lot more space if you plan to save a lot of multimedia files (pictures, MP3, movies) in your home directory. -- cgit v1.2.3