# SOME DESCRIPTIVE TITLE. # Copyright (C) YEAR Free Software Foundation, Inc. # FIRST AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: partitioning\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" "POT-Creation-Date: 2006-01-31 23:11+0000\n" "PO-Revision-Date: 2005-12-15 22:08+0100\n" "Last-Translator: Daniel Nylander \n" "Language-Team: Swedish \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: title #: partitioning.xml:5 #, no-c-format msgid "Partitioning for Debian" msgstr "Partitionering för Debian" #. Tag: title #: partitioning.xml:13 #, no-c-format msgid "Deciding on Debian Partitions and Sizes" msgstr "Besluta Debians partitioner och storlekar" #. Tag: para #: partitioning.xml:14 #, no-c-format msgid "" "At a bare minimum, GNU/Linux needs one partition for itself. You can have a " "single partition containing the entire operating system, applications, and " "your personal files. Most people feel that a separate swap partition is also " "a necessity, although it's not strictly true. Swap is scratch " "space for an operating system, which allows the system to use disk storage " "as virtual memory. By putting swap on a separate partition, " "Linux can make much more efficient use of it. It is possible to force Linux " "to use a regular file as swap, but it is not recommended." msgstr "" #. Tag: para #: partitioning.xml:26 #, no-c-format msgid "" "Most people choose to give GNU/Linux more than the minimum number of " "partitions, however. There are two reasons you might want to break up the " "file system into a number of smaller partitions. The first is for safety. If " "something happens to corrupt the file system, generally only one partition " "is affected. Thus, you only have to replace (from the backups you've been " "carefully keeping) a portion of your system. At a bare minimum, you should " "consider creating what is commonly called a root partition. " "This contains the most essential components of the system. If any other " "partitions get corrupted, you can still boot into GNU/Linux to fix the " "system. This can save you the trouble of having to reinstall the system from " "scratch." msgstr "" #. Tag: para #: partitioning.xml:40 #, no-c-format msgid "" "The second reason is generally more important in a business setting, but it " "really depends on your use of the machine. For example, a mail server " "getting spammed with e-mail can easily fill a partition. If you made " "/var/mail a separate partition on the mail server, most " "of the system will remain working even if you get spammed." msgstr "" #. Tag: para #: partitioning.xml:48 #, no-c-format msgid "" "The only real drawback to using more partitions is that it is often " "difficult to know in advance what your needs will be. If you make a " "partition too small then you will either have to reinstall the system or you " "will be constantly moving things around to make room in the undersized " "partition. On the other hand, if you make the partition too big, you will be " "wasting space that could be used elsewhere. Disk space is cheap nowadays, " "but why throw your money away?" msgstr "" #. Tag: title #: partitioning.xml:67 #, no-c-format msgid "The Directory Tree" msgstr "Mappträdet" #. Tag: para #: partitioning.xml:68 #, no-c-format msgid "" "&debian; adheres to the Filesystem Hierarchy " "Standard for directory and file naming. This standard allows users " "and software programs to predict the location of files and directories. The " "root level directory is represented simply by the slash /. At the root level, all Debian systems include these directories:" msgstr "" #. Tag: entry #: partitioning.xml:82 #, no-c-format msgid "Directory" msgstr "Mapp" #. Tag: entry #: partitioning.xml:82 #, no-c-format msgid "Content" msgstr "Innehåll" #. Tag: filename #: partitioning.xml:88 #, no-c-format msgid "bin" msgstr "bin" #. Tag: entry #: partitioning.xml:89 #, no-c-format msgid "Essential command binaries" msgstr "Nödvändiga kommandobinärer" #. Tag: filename #: partitioning.xml:91 #, no-c-format msgid "boot" msgstr "boot" #. Tag: entry #: partitioning.xml:92 #, no-c-format msgid "Static files of the boot loader" msgstr "Statistika filer för boot-laddaren" #. Tag: filename #: partitioning.xml:94 #, no-c-format msgid "dev" msgstr "dev" #. Tag: entry #: partitioning.xml:95 #, no-c-format msgid "Device files" msgstr "Enhetsfiler" #. Tag: filename #: partitioning.xml:97 #, no-c-format msgid "etc" msgstr "etc" #. Tag: entry #: partitioning.xml:98 #, no-c-format msgid "Host-specific system configuration" msgstr "Värdspecifik systemkonfiguration" #. Tag: filename #: partitioning.xml:100 #, no-c-format msgid "home" msgstr "home" #. Tag: entry #: partitioning.xml:101 #, no-c-format msgid "User home directories" msgstr "Användarnas hemkataloger" #. Tag: filename #: partitioning.xml:103 #, no-c-format msgid "lib" msgstr "lib" #. Tag: entry #: partitioning.xml:104 #, no-c-format msgid "Essential shared libraries and kernel modules" msgstr "" #. Tag: filename #: partitioning.xml:106 #, no-c-format msgid "media" msgstr "media" #. Tag: entry #: partitioning.xml:107 #, no-c-format msgid "Contains mount points for replaceable media" msgstr "" #. Tag: filename #: partitioning.xml:109 #, no-c-format msgid "mnt" msgstr "mnt" #. Tag: entry #: partitioning.xml:110 #, no-c-format msgid "Mount point for mounting a file system temporarily" msgstr "Monteringspunkt för montering av temporärt filsystem" #. Tag: filename #: partitioning.xml:112 #, no-c-format msgid "proc" msgstr "proc" #. Tag: entry #: partitioning.xml:113 #, no-c-format msgid "Virtual directory for system information (2.4 and 2.6 kernels)" msgstr "" #. Tag: filename #: partitioning.xml:115 #, no-c-format msgid "root" msgstr "root" #. Tag: entry #: partitioning.xml:116 #, no-c-format msgid "Home directory for the root user" msgstr "Hemkatalog för root-användaren" #. Tag: filename #: partitioning.xml:118 #, no-c-format msgid "sbin" msgstr "sbin" #. Tag: entry #: partitioning.xml:119 #, no-c-format msgid "Essential system binaries" msgstr "Nödvändiga systembinärer" #. Tag: filename #: partitioning.xml:121 #, no-c-format msgid "sys" msgstr "sys" #. Tag: entry #: partitioning.xml:122 #, no-c-format msgid "Virtual directory for system information (2.6 kernels)" msgstr "" #. Tag: filename #: partitioning.xml:124 #, no-c-format msgid "tmp" msgstr "tmp" #. Tag: entry #: partitioning.xml:125 #, no-c-format msgid "Temporary files" msgstr "Temporära filer" #. Tag: filename #: partitioning.xml:127 #, no-c-format msgid "usr" msgstr "usr" #. Tag: entry #: partitioning.xml:128 #, no-c-format msgid "Secondary hierarchy" msgstr "Sekundär hierarki" #. Tag: filename #: partitioning.xml:130 #, no-c-format msgid "var" msgstr "var" #. Tag: entry #: partitioning.xml:131 #, no-c-format msgid "Variable data" msgstr "Variabeldata" #. Tag: filename #: partitioning.xml:133 #, no-c-format msgid "opt" msgstr "opt" #. Tag: entry #: partitioning.xml:134 #, fuzzy, no-c-format msgid "Add-on application software packages" msgstr "/opt - program som installeras i form av tilläggspaket" #. Tag: para #: partitioning.xml:139 #, no-c-format msgid "" "The following is a list of important considerations regarding directories " "and partitions. Note that disk usage varies widely given system " "configuration and specific usage patterns. The recommendations here are " "general guidelines and provide a starting point for partitioning." msgstr "" #. Tag: para #: partitioning.xml:149 #, no-c-format msgid "" "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." msgstr "" #. Tag: para #: partitioning.xml:158 #, no-c-format msgid "" "/usr: contains all user programs (/usr/bin), libraries (/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 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." msgstr "" #. Tag: para #: partitioning.xml:171 #, no-c-format msgid "" "/var: variable data like news articles, e-mails, web " "sites, databases, the packaging system cache, etc. will be placed 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 /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 MB. If hard drive space is at a premium and you don't plan on " "doing major system updates, you can get by with as little as 30 or 40 MB." msgstr "" #. Tag: para #: partitioning.xml:187 #, no-c-format msgid "" "/tmp: temporary data created by programs will most " "likely go in this directory. 40–100 MB 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 plan to use such applications, you " "should adjust the space available in /tmp accordingly." msgstr "" #. Tag: para #: partitioning.xml:198 #, no-c-format msgid "" "/home: every user will put his personal data 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 a lot more space if you " "plan to save a lot of multimedia files (pictures, MP3, movies) in your home " "directory." msgstr "" #. Tag: title #: partitioning.xml:219 #, no-c-format msgid "Recommended Partitioning Scheme" msgstr "Rekommenderad partitioneringstabell" #. Tag: para #: partitioning.xml:220 #, no-c-format msgid "" "For new users, personal Debian boxes, home systems, and other single-user " "setups, a single / partition (plus swap) is probably " "the easiest, simplest way to go. However, if your partition is larger than " "around 6GB, choose ext3 as your partition type. Ext2 partitions need " "periodic file system integrity checking, and this can cause delays during " "booting when the partition is large." msgstr "" #. Tag: para #: partitioning.xml:229 #, no-c-format msgid "" "For multi-user systems or systems with lots of disk space, it's best to put " "/usr, /var, /tmp, and /home each on their own partitions " "separate from the / partition." msgstr "" #. Tag: para #: partitioning.xml:237 #, no-c-format msgid "" "You might need a separate /usr/local partition if 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 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." msgstr "" #. Tag: para #: partitioning.xml:249 #, no-c-format msgid "" "For very complex systems, you should see the Multi Disk HOWTO. This contains in-depth information, " "mostly of interest to ISPs and people setting up servers." msgstr "" #. Tag: para #: partitioning.xml:256 #, no-c-format msgid "" "With respect to the issue of swap partition size, there are many views. One " "rule of thumb which works well is to use as much swap as you have system " "memory. It also shouldn't be smaller than 16MB, in most cases. Of course, " "there are exceptions to these rules. If you are trying to solve 10000 " "simultaneous equations on a machine with 256MB of memory, you may need a " "gigabyte (or more) of swap." msgstr "" #. Tag: para #: partitioning.xml:265 #, no-c-format msgid "" "On the other hand, Atari Falcons and Macs feel pain when swapping, so " "instead of making a large swap partition, get as much RAM as possible." msgstr "" #. Tag: para #: partitioning.xml:270 #, no-c-format msgid "" "On 32-bit architectures (i386, m68k, 32-bit SPARC, and PowerPC), the maximum " "size of a swap partition is 2GB. That should be enough for nearly any " "installation. However, if your swap requirements are this high, you should " "probably try to spread the swap across different disks (also called " "spindles) and, if possible, different SCSI or IDE channels. " "The kernel will balance swap usage between multiple swap partitions, giving " "better performance." msgstr "" #. Tag: para #: partitioning.xml:280 #, no-c-format msgid "" "As an example, an older home machine might have 32MB of RAM and a 1.7GB IDE " "drive on /dev/hda. There might be a 500MB partition for " "another operating system on /dev/hda1, a 32MB swap " "partition on /dev/hda3 and about 1.2GB on /" "dev/hda2 as the Linux partition." msgstr "" #. Tag: para #: partitioning.xml:289 #, no-c-format msgid "" "For an idea of the space taken by tasks you might be interested in adding " "after your system installation is complete, check ." msgstr "" #. Tag: title #: partitioning.xml:305 #, no-c-format msgid "Device Names in Linux" msgstr "Enhetsnamn i Linux" #. Tag: para #: partitioning.xml:306 #, no-c-format msgid "" "Linux disks and partition names may be different from other operating " "systems. You need to know the names that Linux uses when you create and " "mount partitions. Here's the basic naming scheme:" msgstr "" #. Tag: para #: partitioning.xml:314 #, no-c-format msgid "The first floppy drive is named /dev/fd0." msgstr "Den första diskettenheten kallas /dev/fd0." #. Tag: para #: partitioning.xml:319 #, no-c-format msgid "The second floppy drive is named /dev/fd1." msgstr "Den andra diskettenheten kallas /dev/fd1." #. Tag: para #: partitioning.xml:324 #, no-c-format msgid "" "The first SCSI disk (SCSI ID address-wise) is named /dev/sda." msgstr "" "Den första SCSI-disken (enligt SCSI ID-address) kallas /dev/sda." #. Tag: para #: partitioning.xml:330 #, no-c-format msgid "" "The second SCSI disk (address-wise) is named /dev/sdb, " "and so on." msgstr "" "Den andra SCSI-disken (enligt SCSI ID-address) kallas /dev/sdb." #. Tag: para #: partitioning.xml:336 #, no-c-format msgid "" "The first SCSI CD-ROM is named /dev/scd0, also known as " "/dev/sr0." msgstr "" "Den första SCSI Cd-rom kallas /dev/scd0 också känd som " "/dev/sr0." #. Tag: para #: partitioning.xml:342 #, no-c-format msgid "" "The master disk on IDE primary controller is named /dev/hda." msgstr "" #. Tag: para #: partitioning.xml:348 #, no-c-format msgid "" "The slave disk on IDE primary controller is named /dev/hdb." msgstr "" #. Tag: para #: partitioning.xml:354 #, no-c-format msgid "" "The master and slave disks of the secondary controller can be called " "/dev/hdc and /dev/hdd, " "respectively. Newer IDE controllers can actually have two channels, " "effectively acting like two controllers. The letters " "may differ from what shows in the mac program pdisk (i.e. what shows up as " "/dev/hdc on pdisk may show up as /dev/hda in Debian). " msgstr "" #. Tag: para #: partitioning.xml:369 #, no-c-format msgid "The first XT disk is named /dev/xda." msgstr "" #. Tag: para #: partitioning.xml:374 #, no-c-format msgid "The second XT disk is named /dev/xdb." msgstr "" #. Tag: para #: partitioning.xml:379 #, no-c-format msgid "" "The first ACSI device is named /dev/ada, the second is " "named /dev/adb." msgstr "" #. Tag: para #: partitioning.xml:388 #, no-c-format msgid "The first DASD device is named /dev/dasda." msgstr "" #. Tag: para #: partitioning.xml:394 #, no-c-format msgid "" "The second DASD device is named /dev/dasdb, and so on." msgstr "" #. Tag: para #: partitioning.xml:402 #, no-c-format msgid "" "The partitions on each disk are represented by appending a decimal number to " "the disk name: sda1 and sda2 " "represent the first and second partitions of the first SCSI disk drive in " "your system." msgstr "" #. Tag: para #: partitioning.xml:409 #, no-c-format msgid "" "Here is a real-life example. Let's assume you have a system with 2 SCSI " "disks, one at SCSI address 2 and the other at SCSI address 4. The first disk " "(at address 2) is then named sda, and the second " "sdb. If the sda drive has 3 " "partitions on it, these will be named sda1, " "sda2, and sda3. The same applies " "to the sdb disk and its partitions." msgstr "" #. Tag: para #: partitioning.xml:420 #, no-c-format msgid "" "Note that if you have two SCSI host bus adapters (i.e., controllers), the " "order of the drives can get confusing. The best solution in this case is to " "watch the boot messages, assuming you know the drive models and/or " "capacities." msgstr "" #. Tag: para #: partitioning.xml:427 #, no-c-format msgid "" "Linux represents the primary partitions as the drive name, plus the numbers " "1 through 4. For example, the first primary partition on the first IDE drive " "is /dev/hda1. The logical partitions are numbered " "starting at 5, so the first logical partition on that same drive is " "/dev/hda5. Remember that the extended partition, that " "is, the primary partition holding the logical partitions, is not usable by " "itself. This applies to SCSI disks as well as IDE disks." msgstr "" #. Tag: para #: partitioning.xml:438 #, no-c-format msgid "" "VMEbus systems using the TEAC FC-1 SCSI floppy drive will see it as normal " "SCSI disk. To make identification of the drive simpler the installation " "software will create a symbolic link to the appropriate device and name it " "/dev/sfd0." msgstr "" #. Tag: para #: partitioning.xml:445 #, no-c-format msgid "" "Sun disk partitions allow for 8 separate partitions (or slices). The third " "partition is usually (and is preferred to have) the Whole Disk partition. This partition references all of the sectors of the disk, " "and is used by the boot loader (either SILO, or Sun's)." msgstr "" #. Tag: para #: partitioning.xml:452 #, no-c-format msgid "" "The partitions on each disk are represented by appending a decimal number to " "the disk name: dasda1 and dasda2 " "represent the first and second partitions of the first DASD device in your " "system." msgstr "" #. Tag: title #: partitioning.xml:467 #, no-c-format msgid "Debian Partitioning Programs" msgstr "Debians partitioneringsprogram" #. Tag: para #: partitioning.xml:468 #, no-c-format msgid "" "Several varieties of partitioning programs have been adapted by Debian " "developers to work on various types of hard disks and computer " "architectures. Following is a list of the program(s) applicable for your " "architecture." msgstr "" #. Tag: command #: partitioning.xml:480 #, no-c-format msgid "partman" msgstr "partman" #. Tag: para #: partitioning.xml:481 #, no-c-format msgid "" "Recommended partitioning tool in Debian. This Swiss army knife can also " "resize partitions, create filesystems (format in Windows speak) and assign them to the mountpoints." msgstr "" #. Tag: command #: partitioning.xml:492 #, no-c-format msgid "fdisk" msgstr "fdisk" #. Tag: para #: partitioning.xml:493 #, no-c-format msgid "The original Linux disk partitioner, good for gurus." msgstr "" #. Tag: para #: partitioning.xml:497 #, no-c-format msgid "" "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" msgstr "" #. Tag: command #: partitioning.xml:509 #, no-c-format msgid "cfdisk" msgstr "cfdisk" #. Tag: para #: partitioning.xml:510 #, no-c-format msgid "A simple-to-use, full-screen disk partitioner for the rest of us." msgstr "" #. Tag: para #: partitioning.xml:514 #, no-c-format msgid "" "Note that cfdisk doesn't understand FreeBSD partitions at " "all, and, again, device names may differ as a result." msgstr "" #. Tag: command #: partitioning.xml:523 #, no-c-format msgid "atari-fdisk" msgstr "atari-fdisk" #. Tag: para #: partitioning.xml:524 #, no-c-format msgid "Atari-aware version of fdisk." msgstr "" #. Tag: command #: partitioning.xml:532 #, no-c-format msgid "amiga-fdisk" msgstr "amiga-fdisk" #. Tag: para #: partitioning.xml:533 #, no-c-format msgid "Amiga-aware version of fdisk." msgstr "" #. Tag: command #: partitioning.xml:541 #, no-c-format msgid "mac-fdisk" msgstr "mac-fdisk" #. Tag: para #: partitioning.xml:542 #, no-c-format msgid "Mac-aware version of fdisk." msgstr "" #. Tag: command #: partitioning.xml:550 #, no-c-format msgid "pmac-fdisk" msgstr "pmac-fdisk" #. Tag: para #: partitioning.xml:551 #, no-c-format msgid "" "PowerMac-aware version of fdisk, also used by BVM and " "Motorola VMEbus systems." msgstr "" #. Tag: command #: partitioning.xml:560 #, no-c-format msgid "fdasd" msgstr "fdasd" #. Tag: para #: partitioning.xml:561 #, no-c-format msgid "" "&arch-title; version of fdisk; Please read the fdasd " "manual page or chapter 13 in Device Drivers and " "Installation Commands for details." msgstr "" #. Tag: para #: partitioning.xml:572 #, no-c-format msgid "" "One of these programs will be run by default when you select " "Partition a Hard Disk. If the one which is run by " "default isn't the one you want, quit the partitioner, go to the shell " "(tty2) by pressing Alt and " "F2 keys together, and manually type in the name of the " "program you want to use (and arguments, if any). Then skip the " "Partition a Hard Disk step in debian-" "installer and continue to the next step." msgstr "" #. Tag: para #: partitioning.xml:583 #, no-c-format msgid "" "If you will be working with more than 20 partitions on your ide disk, you " "will need to create devices for partitions 21 and beyond. The next step of " "initializing the partition will fail unless a proper device is present. As " "an example, here are commands you can use in tty2 or " "under Execute A Shell to add a device so the 21st partition can be " "initialized: \n" "# cd /dev\n" "# mknod hda21 b 3 21\n" "# chgrp disk hda21\n" "# chmod 660 hda21\n" " Booting into the new system will fail unless " "proper devices are present on the target system. After installing the kernel " "and modules, execute: \n" "# cd /target/dev\n" "# mknod hda21 b 3 21\n" "# chgrp disk hda21\n" "# chmod 660 hda21\n" " Remember to mark your boot " "partition as Bootable." msgstr "" #. Tag: para #: partitioning.xml:602 #, no-c-format msgid "" "One key point when partitioning for Mac type disks is that the swap " "partition is identified by its name; it must be named swap. " "All Mac linux partitions are the same partition type, Apple_UNIX_SRV2. " "Please read the fine manual. We also suggest reading the mac-fdisk Tutorial, which includes steps you " "should take if you are sharing your disk with MacOS." msgstr "" #. Tag: title #: partitioning.xml:618 partitioning.xml:678 partitioning.xml:702 #: partitioning.xml:798 partitioning.xml:917 partitioning.xml:994 #, no-c-format msgid "Partitioning for &arch-title;" msgstr "Partitionering för &arch-title;" #. Tag: para #: partitioning.xml:619 #, no-c-format msgid "" "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." msgstr "" #. Tag: para #: partitioning.xml:630 #, no-c-format msgid "" "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." msgstr "" #. Tag: para #: partitioning.xml:637 #, no-c-format msgid "" "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." msgstr "" #. Tag: para #: partitioning.xml:648 #, no-c-format msgid "" "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." msgstr "" #. Tag: para #: partitioning.xml:660 #, no-c-format msgid "" "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." msgstr "" #. Tag: para #: partitioning.xml:679 #, no-c-format msgid "" "PALO, the HPPA boot loader, requires a partition of type F0 " "somewhere in the first 2GB. This is where the boot loader and an optional " "kernel and RAMdisk will be stored, so make it big enough for that — at " "least 4Mb (I like 8–16MB). An additional requirement of the firmware " "is that the Linux kernel must reside within the first 2GB of the disk. This " "is typically achieved by making the root ext2 partition fit entirely within " "the first 2GB of the disk. Alternatively you can create a small ext2 " "partition near the start of the disk and mount that on /boot, since that is the directory where the Linux kernel(s) will be " "stored. /boot needs to be big enough to hold whatever " "kernels you might wish load; 8–16MB is generally sufficient." msgstr "" #. Tag: para #: partitioning.xml:703 #, no-c-format msgid "" "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." msgstr "" #. Tag: para #: partitioning.xml:712 #, no-c-format msgid "" "The PC BIOS generally adds additional constraints for disk partitioning. " "There is a limit to how many primary and logical partitions a drive can contain. Additionally, with pre 1994–98 " "BIOSes, there are limits to where on the drive the BIOS can boot from. More " "information can be found in the Linux " "Partition HOWTO and the Phoenix BIOS FAQ, but this section will include a brief " "overview to help you plan most situations." msgstr "" #. Tag: para #: partitioning.xml:723 #, no-c-format msgid "" "Primary partitions are the original partitioning scheme for " "PC disks. However, there can only be four of them. To get past this " "limitation, extended and logical partitions " "were invented. By setting one of your primary partitions as an extended " "partition, you can subdivide all the space allocated to that partition into " "logical partitions. You can create up to 60 logical partitions per extended " "partition; however, you can only have one extended partition per drive." msgstr "" #. Tag: para #: partitioning.xml:734 #, no-c-format msgid "" "Linux limits the partitions per drive to 15 partitions for SCSI disks (3 " "usable primary partitions, 12 logical partitions), and 63 partitions on an " "IDE drive (3 usable primary partitions, 60 logical partitions). However the " "normal &debian; system provides only 20 devices for partitions, so you may " "not install on partitions higher than 20 unless you first manually create " "devices for those partitions." msgstr "" #. Tag: para #: partitioning.xml:744 #, no-c-format msgid "" "If you have a large IDE disk, and are using neither LBA addressing, nor " "overlay drivers (sometimes provided by hard disk manufacturers), then the " "boot partition (the partition containing your kernel image) must be placed " "within the first 1024 cylinders of your hard drive (usually around 524 " "megabytes, without BIOS translation)." msgstr "" #. Tag: para #: partitioning.xml:752 #, no-c-format msgid "" "This restriction doesn't apply if you have a BIOS newer than around " "1995–98 (depending on the manufacturer) that supports the " "Enhanced Disk Drive Support Specification. Both Lilo, the " "Linux loader, and Debian's alternative mbr must use the " "BIOS to read the kernel from the disk into RAM. If the BIOS int 0x13 large " "disk access extensions are found to be present, they will be utilized. " "Otherwise, the legacy disk access interface is used as a fall-back, and it " "cannot be used to address any location on the disk higher than the 1023rd " "cylinder. Once Linux is booted, no matter what BIOS your computer has, these " "restrictions no longer apply, since Linux does not use the BIOS for disk " "access." msgstr "" #. Tag: para #: partitioning.xml:766 #, no-c-format msgid "" "If you have a large disk, you might have to use cylinder translation " "techniques, which you can set from your BIOS setup program, such as LBA " "(Logical Block Addressing) or CHS translation mode (Large). " "More information about issues with large disks can be found in the Large Disk HOWTO. If you are using a " "cylinder translation scheme, and the BIOS does not support the large disk " "access extensions, then your boot partition has to fit within the " "translated representation of the 1024th cylinder." msgstr "" #. Tag: para #: partitioning.xml:778 #, no-c-format msgid "" "The recommended way of accomplishing this is to create a small (5–10MB " "should suffice) partition at the beginning of the disk to be used as the " "boot partition, and then create whatever other partitions you wish to have, " "in the remaining area. This boot partition must be " "mounted on /boot, since that is the directory where the " "Linux kernel(s) will be stored. This configuration will work on any system, " "regardless of whether LBA or large disk CHS translation is used, and " "regardless of whether your BIOS supports the large disk access extensions." msgstr "" #. Tag: para #: partitioning.xml:800 #, no-c-format msgid "" "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." msgstr "" #. Tag: title #: partitioning.xml:812 #, fuzzy, no-c-format msgid "EFI Recognized Formats" msgstr "EFI-startpartition" #. Tag: para #: partitioning.xml:813 #, no-c-format msgid "" "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 parted because only it can manage both GPT " "and MS-DOS tables correctly." msgstr "" #. Tag: para #: partitioning.xml:825 #, no-c-format msgid "" "The automatic partitioning recipes for partman allocate " "an EFI partition as the first partition on the disk. You can also set up the " "partition under the Guided partitioning from the " "main menu in a manner similar to setting up a swap " "partition." msgstr "" #. Tag: para #: partitioning.xml:833 #, no-c-format msgid "" "The partman partitioner will handle most disk layouts. " "For those rare cases where it is necessary to manually set up a disk, you " "can use the shell as described above and run the parted " "utility directly using its command line interface. Assuming that you want to " "erase your whole disk and create a GPT table and some partitions, then " "something similar to the following command sequence could be used: " "\n" " mklabel gpt\n" " mkpartfs primary fat 0 50\n" " mkpartfs primary linux-swap 51 1000\n" " mkpartfs primary ext2 1001 3000\n" " set 1 boot on\n" " print\n" " quit\n" " This creates a new partition table, and three " "partitions to be used as an EFI boot partition, swap space, and a root file " "system. Finally it sets the boot flag on the EFI partition. Partitions are " "specified in Megabytes, with start and end offsets from the beginning of the " "disk. So, for example, above we created a 1999MB ext2 file system starting " "at offset 1001MB from the start of the disk. Note that formatting swap space " "with parted can take a few minutes to complete, as it " "scans the partition for bad blocks." msgstr "" #. Tag: title #: partitioning.xml:858 #, no-c-format msgid "Boot Loader Partition Requirements" msgstr "Krav för startladdarens partition" #. Tag: para #: partitioning.xml:860 #, no-c-format msgid "" "ELILO, the ia64 boot loader, requires a partition containing a FAT file " "system with the boot flag set. The partition must be " "big enough to hold the boot loader and any kernels or RAMdisks you may wish " "to boot. A minimum size would be about 20MB, but if you expect to run with " "multiple kernels, then 128MB might be a better size." msgstr "" #. Tag: para #: partitioning.xml:869 #, no-c-format msgid "" "The EFI Boot Manager and the EFI Shell fully support the GPT table so the " "boot partition does not necessarily have to be the first partition or even " "on the same disk. This is convenient if you should forget to allocate the " "partition and only find out after you have formatted the other partitions on " "your disk(s). The partman partitioner checks for an EFI " "partition at the same time it checks for a properly set up root partition. This gives you an opportunity to correct the disk " "layout before the package install begins. The easiest way to correct this " "omission is to shrink the last partition of the disk to make enough free " "space for adding an EFI partition." msgstr "" #. Tag: para #: partitioning.xml:884 #, no-c-format msgid "" "It is strongly recommended that you allocate the EFI boot partition on the " "same disk as the root filesystem." msgstr "" #. Tag: title #: partitioning.xml:893 #, fuzzy, no-c-format msgid "EFI Diagnostic Partitions" msgstr "Beräknar de nya partitionerna..." #. Tag: para #: partitioning.xml:895 #, no-c-format msgid "" "The EFI firmware is significantly more sophisticated than the usual BIOS " "seen on most x86 PCs. Some system vendors take advantage of the ability of " "the EFI to access files and run programs from a hard disk filesystem to " "store diagnostics and EFI based system management utilities on the hard " "disk. This is a separate FAT format filesystem on the system disk. Consult " "the system documentation and accessories that come with the system for " "details. The easiest time to set up a diagnostics partition is at the same " "time you set up the EFI boot partition." msgstr "" #. Tag: para #: partitioning.xml:918 #, no-c-format msgid "" "SGI Indys require an SGI disk label in order to make the system bootable " "from hard disk. It can be created in the fdisk expert menu. The thereby " "created volume header(partition number 9) should be at least 3MB large. If " "the volume header created is too small, you can simply delete partition " "number 9 and re-add it with a different size. Note that the volume header " "must start at sector 0." msgstr "" #. Tag: title #: partitioning.xml:935 #, no-c-format msgid "Partitioning Newer PowerMacs" msgstr "Partitionering av nyare PowerMac" #. Tag: para #: partitioning.xml:936 #, no-c-format msgid "" "If you are installing onto a NewWorld PowerMac you must create a special " "bootstrap partition to hold the boot loader. The size of this partition must " "be 800KB and its partition type must be Apple_Bootstrap. If the bootstrap partition is not created with the " "Apple_Bootstrap type your machine cannot be made " "bootable from the hard disk. This partition can easily be created by " "creating a new partition in partman and telling it to use " "it as a NewWorld boot partition, or in mac-fdisk using the b command." msgstr "" #. Tag: para #: partitioning.xml:949 #, no-c-format msgid "" "The special partition type Apple_Bootstrap is required to prevent MacOS from " "mounting and damaging the bootstrap partition, as there are special " "modifications made to it in order for OpenFirmware to boot it automatically." msgstr "" #. Tag: para #: partitioning.xml:956 #, no-c-format msgid "" "Note that the bootstrap partition is only meant to hold 3 very small files: " "the yaboot binary, its configuration yaboot." "conf, and a first stage OpenFirmware loader ofboot.b. It need not and must not be mounted on your file system nor have " "kernels or anything else copied to it. The ybin and " "mkofboot utilities are used to manipulate this partition." msgstr "" #. Tag: para #: partitioning.xml:966 #, no-c-format msgid "" "In order for OpenFirmware to automatically boot &debian; the bootstrap " "partition should appear before other boot partitions on the disk, especially " "MacOS boot partitions. The bootstrap partition should be the first one you " "create. However, if you add a bootstrap partition later, you can use " "mac-fdisk's r command to reorder " "the partition map so the bootstrap partition comes right after the map " "(which is always partition 1). It's the logical map order, not the physical " "address order, that counts." msgstr "" #. Tag: para #: partitioning.xml:978 #, no-c-format msgid "" "Apple disks normally have several small driver partitions. If you intend to " "dual boot your machine with MacOSX, you should retain these partitions and a " "small HFS partition (800k is the minimum size). That is because MacOSX, on " "every boot, offers to initialize any disks which do not have active MacOS " "partitions and driver partitions." msgstr "" #. Tag: para #: partitioning.xml:995 #, no-c-format msgid "" "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. The s key " "is used in fdisk to create Sun disk labels." msgstr "" #. Tag: para #: partitioning.xml:1003 #, no-c-format msgid "" "Furthermore, on &arch-title; disks, make sure your first partition on your " "boot disk starts at cylinder 0. While this is required, it also means that " "the first partition will contain the partition table and the boot block, " "which are the first two sectors of the disk. You must not put swap on the first partition of the boot drive, since swap " "partitions do not preserve the first few sectors of the partition. You can " "put Ext2 or UFS partitions there; these will leave the partition table and " "the boot block alone." msgstr "" #. Tag: para #: partitioning.xml:1014 #, no-c-format msgid "" "It is also advised that the third partition should be of type Whole " "disk (type 5), and contain the entire disk (from the first cylinder " "to the last). This is simply a convention of Sun disk labels, and helps the " "SILO boot loader keep its bearings." msgstr ""