diff options
Diffstat (limited to 'ca')
164 files changed, 17630 insertions, 0 deletions
diff --git a/ca/administrivia/administrivia.xml b/ca/administrivia/administrivia.xml new file mode 100644 index 000000000..611b58af0 --- /dev/null +++ b/ca/administrivia/administrivia.xml @@ -0,0 +1,155 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 29689 untranslated --> + +<appendix id="administrivia"> + <title>Administrivia</title> + + + <sect1 id="about"> + <title>About This Document</title> + +<para> + +This manual was created for Sarge's debian-installer, based on +the Woody installation manual for boot-floppies, which was based +on earlier Debian installation manuals, and on the Progeny +distribution manual which was released under GPL in 2003. + +</para><para> + +This document is written in DocBook XML. Output formats are generated +by various programs using information from the +<classname>docbook-xml</classname> and +<classname>docbook-xsl</classname> packages. + +</para><para> + +In order to increase the maintainability of this document, we use +a number of XML features, such as entities and profiling attributes. +These play a role akin to variables and conditionals in programming +languages. The XML source to this document contains information for +each different architecture — profiling attributes are used to +isolate certain bits of text as architecture-specific. + +<!-- +</para><para> + +Translators can uncomment this paragraph and add an acknowledgement +to the people responsible for the translation of the manual. +Translation teams are advised to just mention the coordinator and maybe +major contributors and thank everybody else in a phrase like "all +translators and reviewers from the translation team for <your language> +at <your l10n mailinglist>". + +(Note: support for this for translations using PO files will be added + soon.) +--> + +</para> + </sect1> + + <sect1 id="contributing"> + <title>Contributing to This Document</title> + +<para> + +If you have problems or suggestions regarding this document, you +should probably submit them as a bug report against the package +<classname>debian-installer-manual</classname>. See the +<classname>reportbug</classname> package or read the online +documentation of the <ulink url="&url-bts;">Debian Bug +Tracking System</ulink>. It would be nice if you could check the +<ulink url="&url-bts;debian-installer-manual">open bugs against +debian-installer-manual</ulink> to see whether your problem has +already been reported. If so, you can supply additional corroboration +or helpful information to +<email><replaceable>XXXX</replaceable>@bugs.debian.org</email>, +where <replaceable>XXXX</replaceable> is the number for the +already-reported bug. + +</para><para> + +Better yet, get a copy of the DocBook source for this document, and +produce patches against it. The DocBook source can be found at the +<ulink url="&url-d-i-websvn;">debian-installer WebSVN</ulink>. If +you're not familiar with DocBook, don't worry: +there is a simple cheatsheet in the manuals directory that will get +you started. It's like html, but oriented towards the meaning of +the text rather than the presentation. Patches submitted to the +debian-boot mailing list (see below) are welcomed. +For instructions on how to check out the sources via SVN, see +<ulink url="&url-d-i-readme;">README</ulink> +from the source root directory. + +</para><para> + +Please do <emphasis>not</emphasis> contact the authors of this +document directly. There is also a discussion list for &d-i;, which +includes discussions of this manual. The mailing list is +<email>debian-boot@lists.debian.org</email>. Instructions for +subscribing to this list can be found at the <ulink +url="&url-debian-lists-subscribe;">Debian Mailing +List Subscription</ulink> page; or you can browse the <ulink +url="&url-debian-list-archives;">Debian Mailing List Archives</ulink> +online. + +</para> + + </sect1> + + <sect1 id="contributors"> + <title>Major Contributions</title> + +<para> + +This document was originally written by Bruce Perens, Sven Rudolph, Igor +Grobman, James Treacy, and Adam Di Carlo. Sebastian Ley wrote the +Installation Howto. +Many, many Debian users and developers contributed to this document. +Particular note must be made of Michael Schmitz (m68k support), Frank +Neumann (original author of the <ulink +url="&url-m68k-old-amiga-install;">Amiga install manual</ulink>), +Arto Astala, Eric Delaunay/Ben Collins (SPARC information), Tapio +Lehtonen, and Stéphane Bortzmeyer for numerous edits and text. +We have to thank Pascal Le Bail for useful information about booting +from USB memory sticks. Miroslav Kuře has documented a lot of the new +functionality in Sarge's debian-installer. + +</para><para> + +Extremely helpful text and information was found in Jim Mintha's HOWTO +for network booting (no URL available), the <ulink +url="&url-debian-faq;">Debian FAQ</ulink>, the <ulink +url="&url-m68k-faq;">Linux/m68k FAQ</ulink>, the <ulink +url="&url-sparc-linux-faq;">Linux for SPARC Processors +FAQ</ulink>, the <ulink +url="&url-alpha-faq;">Linux/Alpha +FAQ</ulink>, amongst others. The maintainers of these freely +available and rich sources of information must be recognized. + +</para><para> + +The section on chrooted installations in this manual +(<xref linkend="linux-upgrade"/>) was derived in part from +documents copyright Karsten M. Self. + +</para><para arch="i386"> + +The section on installations over plip in this manual +(<xref linkend="plip"/>) was based on the +<ulink url="&url-plip-install-howto;">PLIP-Install-HOWTO</ulink> +by Gilles Lamiral. + +</para> + </sect1> + + <sect1 id="trademarks"> + <title>Trademark Acknowledgement</title> +<para> + +All trademarks are property of their respective trademark owners. + +</para> + </sect1> +</appendix> + diff --git a/ca/appendix/chroot-install.xml b/ca/appendix/chroot-install.xml new file mode 100644 index 000000000..6f32a25b1 --- /dev/null +++ b/ca/appendix/chroot-install.xml @@ -0,0 +1,430 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 untranslated --> + + <sect1 id="linux-upgrade"> + <title>Installing &debian; from a Unix/Linux System</title> + +<para> + +This section explains how to install &debian; from an existing +Unix or Linux system, without using the menu-driven installer as +explained in the rest of the manual. This <quote>cross-install</quote> +HOWTO has been requested by users switching to &debian; from +Red Hat, Mandrake, and SUSE. In this section some familiarity with +entering *nix commands and navigating the file system is assumed. In +this section, <prompt>$</prompt> symbolizes a command to be entered in +the user's current system, while <prompt>#</prompt> refers to a +command entered in the Debian chroot. + +</para><para> + +Once you've got the new Debian system configured to your preference, +you can migrate your existing user data (if any) to it, and keep on +rolling. This is therefore a <quote>zero downtime</quote> &debian; +install. It's also a clever way for dealing with hardware that +otherwise doesn't play friendly with various boot or installation +media. + +</para> + + <sect2> + <title>Getting Started</title> +<para> + +With your current *nix partitioning tools, repartition the hard +drive as needed, creating at least one filesystem plus swap. You +need at least 150MB of space available for a console only install, +or at least 300MB if you plan to install X. + +</para><para> + +To create file systems on your partitions. For example, to create an +ext3 file system on partition <filename>/dev/hda6</filename> (that's +our example root partition): + +<informalexample><screen> +# mke2fs -j /dev/hda6 +</screen></informalexample> + +To create an ext2 file system instead, omit <userinput>-j</userinput>. + +</para><para> + +Initialize and activate swap (substitute the partition number for +your intended Debian swap partition): + +<informalexample><screen> +# mkswap /dev/hda5 +# sync; sync; sync +# swapon /dev/hda5 +</screen></informalexample> + +Mount one partition as <filename>/mnt/debinst</filename> (the +installation point, to be the root (<filename>/</filename>) filesystem +on your new system). The mount point name is strictly arbitrary, it is +referenced later below. + +<informalexample><screen> +# mkdir /mnt/debinst +# mount /dev/hda6 /mnt/debinst +</screen></informalexample> + +</para> + </sect2> + + <sect2> + <title>Install <command>debootstrap</command></title> +<para> + +The tool that the Debian installer uses, which is recognized as the +official way to install a Debian base system, is +<command>debootstrap</command>. It uses <command>wget</command> and +<command>ar</command>, but otherwise depends only on +<classname>/bin/sh</classname>. Install <command>wget</command> and +<command>ar</command> if they aren't already on your current system, +then download and install <command>debootstrap</command>. + +</para><para> + +If you have an rpm-based system, you can use alien to convert the +.deb into .rpm, or download an rpm-ized version at +<ulink url="http://people.debian.org/~blade/install/debootstrap"></ulink> + +</para><para> + +Or, you can use the following procedure to install it +manually. Make a work folder for extracting the .deb into: + +<informalexample><screen> +# mkdir work +# cd work +</screen></informalexample> + +The <command>debootstrap</command> binary is located in the Debian +archive (be sure to select the proper file for your +architecture). Download the <command>debootstrap</command> .deb from +the <ulink url="http://ftp.debian.org/debian/pool/main/d/debootstrap/"> +pool</ulink>, copy the package to the work folder, and extract the +binary files from it. You will need to have root privileges to install +the binaries. + +<informalexample><screen> +# ar -x debootstrap_0.X.X_arch.deb +# cd / +# zcat /full-path-to-work/work/data.tar.gz | tar xv +</screen></informalexample> + +</para> + </sect2> + + <sect2> + <title>Run <command>debootstrap</command></title> +<para> + +<command>debootstrap</command> can download the needed files directly +from the archive when you run it. You can substitute any Debian +archive mirror for <userinput>http.us.debian.org/debian</userinput> in +the command example below, preferably a mirror close to you +network-wise. Mirrors are listed at +<ulink url="http://www.debian.org/misc/README.mirrors"></ulink>. + +</para><para> + +If you have a &releasename; &debian; CD mounted at +<filename>/cdrom</filename>, you could substitute a file URL instead +of the http URL: <userinput>file:/cdrom/debian/</userinput> + +</para><para> + +Substitute one of the following for <replaceable>ARCH</replaceable> +in the <command>debootstrap</command> command: + +<userinput>alpha</userinput>, +<userinput>arm</userinput>, +<userinput>hppa</userinput>, +<userinput>i386</userinput>, +<userinput>ia64</userinput>, +<userinput>m68k</userinput>, +<userinput>mips</userinput>, +<userinput>mipsel</userinput>, +<userinput>powerpc</userinput>, +<userinput>s390</userinput>, or +<userinput>sparc</userinput>. + +<informalexample><screen> +# /usr/sbin/debootstrap --arch ARCH &releasename; \ + /mnt/debinst http://http.us.debian.org/debian +</screen></informalexample> + +</para> + </sect2> + + <sect2> + <title>Configure The Base System</title> +<para> + +Now you've got a real Debian system, though rather lean, on disk. +<command>Chroot</command> into it: + +<informalexample><screen> +# LANG= chroot /mnt/debinst /bin/bash +</screen></informalexample> + +</para> + + <sect3> + <title>Mount Partitions</title> +<para> + +You need to create <filename>/etc/fstab</filename>. + +<informalexample><screen> +# editor /etc/fstab +</screen></informalexample> + +Here is a sample you can modify to suit: + +<informalexample><screen> +# /etc/fstab: static file system information. +# +# file system mount point type options dump pass +/dev/XXX / ext2 defaults 0 0 +/dev/XXX /boot ext2 ro,nosuid,nodev 0 2 + +/dev/XXX none swap sw 0 0 +proc /proc proc defaults 0 0 + +/dev/fd0 /mnt/floppy auto noauto,rw,sync,user,exec 0 0 +/dev/cdrom /mnt/cdrom iso9660 noauto,ro,user,exec 0 0 + +/dev/XXX /tmp ext2 rw,nosuid,nodev 0 2 +/dev/XXX /var ext2 rw,nosuid,nodev 0 2 +/dev/XXX /usr ext2 rw,nodev 0 2 +/dev/XXX /home ext2 rw,nosuid,nodev 0 2 +</screen></informalexample> + +Use <userinput>mount -a</userinput> to mount all the file systems you +have specified in your <filename>/etc/fstab</filename>, or to mount +file systems individually use: + +<informalexample><screen> +# mount /path # e.g.: mount /usr +</screen></informalexample> + +You can mount the proc file system multiple times and to arbitrary +locations, though /proc is customary. If you didn't use +<userinput>mount -a</userinput>, be sure to mount proc before +continuing: + +<informalexample><screen> +# mount -t proc proc /proc +</screen></informalexample> + +</para> + </sect3> + + <sect3> + <title>Configure Keyboard</title> +<para> + +To configure your keyboard: + +<informalexample><screen> +# dpkg-reconfigure console-data +</screen></informalexample> + +</para> + </sect3> + + <sect3> + <title>Configure Networking</title> +<para> + +To configure networking, edit +<filename>/etc/network/interfaces</filename>, +<filename>/etc/resolv.conf</filename>, and +<filename>/etc/hostname</filename>. + +<informalexample><screen> +# editor /etc/network/interfaces +</screen></informalexample> + +Here are some simple examples from +<filename>/usr/share/doc/ifupdown/examples</filename>: + +<informalexample><screen> +###################################################################### +# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8) +# See the interfaces(5) manpage for information on what options are +# available. +###################################################################### + +# We always want the loopback interface. +# +auto lo +iface lo inet loopback + +# To use dhcp: +# +# auto eth0 +# iface eth0 inet dhcp + +# An example static IP setup: (broadcast and gateway are optional) +# +# auto eth0 +# iface eth0 inet static +# address 192.168.0.42 +# network 192.168.0.0 +# netmask 255.255.255.0 +# broadcast 192.168.0.255 +# gateway 192.168.0.1 +</screen></informalexample> + +Enter your nameserver(s) and search directives in +<filename>/etc/resolv.conf</filename>: + +<informalexample><screen> +# editor /etc/resolv.conf +</screen></informalexample> + +A simple <filename>/etc/resolv.conf</filename>: + +<informalexample><screen> +search hqdom.local\000 +nameserver 10.1.1.36 +nameserver 192.168.9.100 +</screen></informalexample> + +Enter your system's host name (2 to 63 characters): + +<informalexample><screen> +# echo DebianHostName > /etc/hostname +</screen></informalexample> + +If you have multiple network cards, you should arrange the names of +driver modules in the <filename>/etc/modules</filename> file into the +desired order. Then during boot, each card will be associated with the +interface name (eth0, eth1, etc.) that you expect. + +</para> + </sect3> + + <sect3> + <title>Configure Timezone, Users, and APT</title> +<para> + +Set your timezone, add a normal user, and choose your <command>apt</command> +sources by running + +<informalexample><screen> +# /usr/sbin/base-config new +</screen></informalexample> + +</para> + </sect3> + + <sect3> + <title>Configure Locales</title> +<para> + +To configure your locale settings to use a language other than +English, install the locales support package and configure it: + +<informalexample><screen> +# apt-get install locales +# dpkg-reconfigure locales +</screen></informalexample> + +NOTE: Apt must be configured before, ie. during the base-config phase. +Before using locales with character sets other than ASCII or latin1, +please consult the appropriate localization HOWTO. + +</para> + </sect3> + </sect2> + + <sect2> + <title>Install a Kernel</title> +<para> + +If you intend to boot this system, you probably want a Linux kernel +and a boot loader. Identify available pre-packaged kernels with + +<informalexample><screen> +# apt-cache search kernel-image +</screen></informalexample> + +Then install your choice using its package name. + +<informalexample><screen> +# apt-get install kernel-image-<replaceable>2.X.X-arch-etc</replaceable> +</screen></informalexample> + +</para> + </sect2> + + <sect2> +<title>Set up the Boot Loader</title> +<para> + +To make your &debian; system bootable, set up your boot loader to load +the installed kernel with your new root partition. Note that debootstrap +does not install a boot loader, though you can use apt-get inside your +Debian chroot to do so. + +</para><para arch="i386"> + +Check <userinput>info grub</userinput> or <userinput>man +lilo.conf</userinput> for instructions on setting up the +bootloader. If you are keeping the system you used to install Debian, just +add an entry for the Debian install to your existing grub +<filename>menu.lst</filename> or <filename>lilo.conf</filename>. For +<filename>lilo.conf</filename>, you could also copy it to the new system and +edit it there. After you are done editing, call lilo (remember it will use +<filename>lilo.conf</filename> relative to the system you call it from). + +</para><para arch="i386"> + +Here is a basic <filename>/etc/lilo.conf</filename> as an example: + +<informalexample><screen> +boot=/dev/hda6 +root=/dev/hda6 +install=/boot/boot-menu.b +delay=20 +lba32 +image=/vmlinuz +label=Debian +</screen></informalexample> + +</para><para arch="powerpc"> + +Check <userinput>man yaboot.conf</userinput> for instructions on +setting up the bootloader. If you are keeping the system you used to +install Debian, just add an entry for the Debian install to your +existing <filename>yaboot.conf</filename>. You could also copy it to +the new system and +edit it there. After you are done editing, call ybin (remember it will +use <filename>yaboot.conf</filename> relative to the system you call it from). + +</para><para arch="powerpc"> + +Here is a basic <filename>/etc/yaboot.conf</filename> as an example: + +<informalexample><screen> +boot=/dev/hda2 +device=hd: +partition=6 +root=/dev/hda6 +magicboot=/usr/lib/yaboot/ofboot +timeout=50 +image=/vmlinux +label=Debian +</screen></informalexample> + +On some machines, you may need to use <userinput>ide0:</userinput> +instead of <userinput>hd:</userinput>. + +</para> + </sect2> + </sect1> diff --git a/ca/appendix/example-preseed-etch.xml b/ca/appendix/example-preseed-etch.xml new file mode 100644 index 000000000..79d3e143f --- /dev/null +++ b/ca/appendix/example-preseed-etch.xml @@ -0,0 +1,372 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 30373 untranslated --> + +<informalexample condition="etch"><screen> +#### Startup. + +# To use a preseed file, you'll first need to boot the installer, +# and tell it what preseed file to use. This is done by passing the +# kernel a boot parameter, either manually at boot or by editing the +# syslinux.cfg (or similar) file and adding the parameter to the end +# of the append line(s) for the kernel. +# +# If you're netbooting, use this: +# preseed/url=http://host/path/to/preseed +# If you're remastering a CD, you could use this: +# preseed/file=/cdrom/preseed +# If you're installing from USB media, use this, and put the preseed file +# in the toplevel directory of the USB stick. +# preseed/file=/hd-media/preseed +# +# If you feel comfortable modifying the installer's initrd image, +# you can also place a preseed file in the root directory of the initrd's +# filesystem, named "preseed.cfg" -- the installer will always use this +# file if it is present. Otherwise, be sure to copy this file to the location +# you specify. +# +# To make sure the installer gets the right preseed file, you can specify +# a checksum for the file. Currently this needs to be a md5sum, and if +# specified it must match the file or the installer will refuse to use the +# file. +# preseed/url/checksum=5da499872becccfeda2c4872f9171c3d +# preseed/file/checksum=5da499872becccfeda2c4872f9171c3d +# +# Some parts of the installation process cannot be automated using +# some forms of preseeding, because the questions are asked before +# the preseed file is loaded. For example, if the preseed file is +# downloaded over the network, the network setup must be done first. +# One reason to use initrd preseeding is that it allows preseeding +# of even these early steps of the installation process. +# +# If a preseed file cannot be used to preseed some steps, the install can +# still be fully automated, since you can pass preseed values to the kernel +# on the command line. Just pass path/to/var=value for any of the preseed +# variables listed below. +# +# While you're at it, you may want to throw a debconf/priority=critical in +# there, to avoid most questions even if the preseeding below misses some. +# And you might set the timeout to 1 in syslinux.cfg to avoid needing to hit +# enter to boot the installer. +# +# Note that the 2.4 kernel accepts a maximum of 8 command line options and +# 8 environment options (including any options added by default for the +# installer). If these numbers are exceeded, 2.4 kernels will drop any +# excess options and 2.6 kernels will panic. With kernel 2.6.9 or newer, +# you can use 32 command line options and 32 environment options. +# +# Some of the default options, like 'vga=normal' may be safely removed +# for most installations, which may allow you to add more options for +# preseeding. + +# To select your language and country, use this setting, but remember +# that this will only work for initrd based preseeding, for other forms of +# preseeding you must convert it into a kernel parameter, +# such as debian-installer/locale=en_US +d-i debian-installer/locale string en_US + +# To select your keyboard, use this setting. Again it will need to be +# passed as a kernel parameter for most preseed setups. +d-i console-keymaps-at/keymap select us + +#### Network configuration. + +# Of course, this won't work if you're loading your preseed file from the +# network! But it's great if you're booting from CD or USB stick. You can +# also pass network config parameters in on the kernel params if you are +# loading preseed files from the network. + +# netcfg will choose an interface that has link if possible. This makes it +# skip displaying a list if there is more than one interface. +d-i netcfg/choose_interface select auto + +# If you have a slow dhcp server and the installer times out waiting for +# it, this might be useful. +#d-i netcfg/dhcp_timeout string 60 + +# If you prefer to configure the network manually, here's how: +#d-i netcfg/disable_dhcp boolean true +#d-i netcfg/get_nameservers string 192.168.1.1 +#d-i netcfg/get_ipaddress string 192.168.1.42 +#d-i netcfg/get_netmask string 255.255.255.0 +#d-i netcfg/get_gateway string 192.168.1.1 +#d-i netcfg/confirm_static boolean true + +# Note that any hostname and domain names assigned from dhcp take +# precedence over values set here. However, setting the values still +# prevents the questions from being shown even if values come from dhcp. +d-i netcfg/get_hostname string unassigned-hostname +d-i netcfg/get_domain string unassigned-domain + +# Disable that annoying WEP key dialog. +d-i netcfg/wireless_wep string +# The wacky dhcp hostname that some ISPs use as a password of sorts. +#d-i netcfg/dhcp_hostname string radish + +#### Mirror settings. + +d-i mirror/country string enter information manually +d-i mirror/http/hostname string http.us.debian.org +d-i mirror/http/directory string /debian +d-i mirror/http/proxy string + +# What suite of Debian to install. +#d-i mirror/suite string testing +# What suite of Debian to use for loading installer components. +# (Defaults to same as mirror/suite.) +#d-i mirror/udeb/suite string testing + +#### Partitioning. + +# If the system has free space you can choose to only partition that space. +#d-i partman-auto/init_automatically_partition \ +# select Use the largest continuous free space + +# Alternatively, you can specify a disk to partition. The device name can +# be given in either devfs or traditional non-devfs format. +# For example, to use the first disk devfs knows of: +d-i partman-auto/disk string /dev/discs/disc0/disc + +# You can choose from any of the predefined partitioning recipes: +d-i partman-auto/choose_recipe \ + select All files in one partition (recommended for new users) +#d-i partman-auto/choose_recipe select Desktop machine +#d-i partman-auto/choose_recipe select Multi-user workstation + +# Or provide a recipe of your own... +# The recipe format is documented in the file devel/partman-auto-recipe.txt. +# If you have a way to get a recipe file into the d-i environment, you can +# just point at it. +#d-i partman-auto/expert_recipe_file string /hd-media/recipe + +# If not, you can put an entire recipe the preseed file in one (logical) +# line. This example creates a small /boot partition, suitable swap, and +# uses the rest of the space for the root partition: +#d-i partman-auto/expert_recipe string \ +# boot-root :: \ +# 40 50 100 ext3 \ +# $primary{ } $bootable{ } \ +# method{ format } format{ } \ +# use_filesystem{ } filesystem{ ext3 } \ +# mountpoint{ /boot } \ +# . \ +# 500 10000 1000000000 ext3 \ +# method{ format } format{ } \ +# use_filesystem{ } filesystem{ ext3 } \ +# mountpoint{ / } \ +# . \ +# 64 512 300% linux-swap \ +# method{ swap } format{ } \ +# . + +# This makes partman automatically partition without confirmation. +d-i partman/confirm_write_new_label boolean true +d-i partman/choose_partition \ + select Finish partitioning and write changes to disk +d-i partman/confirm boolean true + +#### Boot loader installation. + +# Grub is the default boot loader (for x86). If you want lilo installed +# instead, uncomment this: +#d-i grub-installer/skip boolean true + +# This is fairly safe to set, it makes grub install automatically to the MBR +# if no other operating system is detected on the machine. +d-i grub-installer/only_debian boolean true + +# This one makes grub-installer install to the MBR if if finds some other OS +# too, which is less safe as it might not be able to boot that other OS. +d-i grub-installer/with_other_os boolean true + +# Alternatively, if you want to install to a location other than the mbr, +# uncomment and edit these lines: +#d-i grub-installer/bootdev string (hd0,0) +#d-i grub-installer/only_debian boolean false +#d-i grub-installer/with_other_os boolean false + +#### Finishing up the first stage install. + +# Avoid that last message about the install being complete. +d-i prebaseconfig/reboot_in_progress note + +# This will prevent the installer from ejecting the CD during the reboot, +# which is useful in some situations. +#d-i cdrom-detect/eject boolean false + +#### Shell commands. + +# d-i preseeding is inherently not secure. Nothing in the installer checks +# for attempts at buffer overflows or other exploits of the values of a +# preseed file like this one. Only use preseed files from trusted +# locations! To drive that home, and because it's generally useful, here's +# a way to run any shell command you'd like inside the installer, +# automatically. + +# This first command is run as early as possible, just after +# preseeding is read. +#d-i preseed/early_command string anna-install some-udeb + +# This command is run just before the install finishes, but when there is +# still a usable /target directory. +#d-i preseed/late_command string echo foo > /target/etc/bar + +# This command is run just as base-config is starting up. +#base-config base-config/early_command string echo hi mom + +# This command is run after base-config is done, just before the login: +# prompt. This is a good way to install a set of packages you want, or to +# tweak the configuration of the system. +#base-config base-config/late_command \ +# string apt-get install zsh; chsh -s /bin/zsh + +###### Preseeding the 2nd stage of the installation. + +#### Preseeding base-config. + +# Avoid the introductory message. +base-config base-config/intro note + +# Avoid the final message. +base-config base-config/login note + +# If you installed a display manager, but don't want to start it immediately +# after base-config finishes. +#base-config base-config/start-display-manager boolean false + +# Some versions of the installer can report back on what you've installed. +# The default is not to report back, but sending reports helps the project +# determine what software is most popular and include it on CDs. +#popularity-contest popularity-contest/participate boolean false + +#### Clock and time zone setup. + +# Controls whether or not the hardware clock is set to UTC. +d-i clock-setup/utc boolean true + +# You may set this to any valid setting for $TZ; see the contents of +# /usr/share/zoneinfo/ for options. +d-i time/zone string US/Eastern + +#### Account setup. + +# To preseed the root password, you have to put it in the clear in this +# file. That is not a very good idea, use caution! +#passwd passwd/root-password password r00tme +#passwd passwd/root-password-again password r00tme + +# If you want to skip creation of a normal user account. +#passwd passwd/make-user boolean false + +# Alternatively, you can preseed the user's name and login. +#passwd passwd/user-fullname string Debian User +#passwd passwd/username string debian +# And their password, but use caution! +#passwd passwd/user-password password insecure +#passwd passwd/user-password-again password insecure + +#### Apt setup. + +# This question controls what source the second stage installation uses +# for packages. Choices are cdrom, http, ftp, filesystem, edit sources list +# by hand +base-config apt-setup/uri_type select http + +# If you choose ftp or http, you'll be asked for a country and a mirror. +base-config apt-setup/country select enter information manually +base-config apt-setup/hostname string http.us.debian.org +base-config apt-setup/directory string /debian +# Stop after choosing one mirror. +base-config apt-setup/another boolean false + +# You can choose to install non-free and contrib software. +#base-config apt-setup/non-free boolean true +#base-config apt-setup/contrib boolean true + +# Do enable security updates. +base-config apt-setup/security-updates boolean true + +#### Package selection. + +# You can choose to install any combination of tasks that are available. +# Available tasks as of this writing include: Desktop environment, +# Web server, Print server, DNS server, File server, Mail server, +# SQL database, Laptop, Standard system, manual package selection. The +# last of those will run aptitude. You can also choose to install no +# tasks, and force the installation of a set of packages in some other +# way. We recommend always including the Standard system task. +tasksel tasksel/first multiselect Desktop environment, Standard system +#tasksel tasksel/first multiselect Web server, Standard system + +#### Mailer configuration. + +# During a normal install, exim asks only a few questions. Here's how to +# avoid even those. More complicated preseeding is possible. +exim4-config exim4/dc_eximconfig_configtype \ + select no configuration at this time +exim4-config exim4/no_config boolean true +exim4-config exim4/no_config boolean true + +# It's a good idea to set this to whatever user account you choose to +# create. Leaving the value blank results in postmaster mail going to +# /var/mail/mail. +exim4-config exim4/dc_postmaster string + +#### X Configuration. + +# Preseeding Debian's X config is possible, but you probably need to know +# some details about the video hardware of the machine, since Debian's X +# configurator does not do fully automatic configuration of everything. + +# X can detect the right driver for some cards, but if you're preseeding, +# you override whatever it chooses. Still, vesa will work most places. +#xserver-xfree86 xserver-xfree86/config/device/driver select vesa + +# A caveat with mouse autodetection is that if it fails, X will retry it +# over and over. So if it's preseeded to be done, there is a possibility of +# an infinite loop if the mouse is not autodetected. +#xserver-xfree86 xserver-xfree86/autodetect_mouse boolean true + +# Monitor autodetection is recommended. +xserver-xfree86 xserver-xfree86/autodetect_monitor boolean true +# Uncomment if you have an LCD display. +#xserver-xfree86 xserver-xfree86/config/monitor/lcd boolean true +# X has three configuration paths for the monitor. Here's how to preseed +# the "medium" path, which is always available. The "simple" path may not +# be available, and the "advanced" path asks too many questions. +xserver-xfree86 xserver-xfree86/config/monitor/selection-method \ + select medium +xserver-xfree86 xserver-xfree86/config/monitor/mode-list \ + select 1024x768 @ 60 Hz + +#### Everything else. + +# Depending on what software you choose to install, or if things go wrong +# during the installation process, it's possible that other questions may +# be asked. You can preseed those too, of course. To get a list of every +# possible question that could be asked during an install, do an +# installation, and then run these commands: +# debconf-get-selections --installer > file +# debconf-get-selections >> file + +# If you like, you can include other preseed files into this one. +# Any settings in those files will override pre-existing settings from this +# file. More that one file can be listed, separated by spaces; all will be +# loaded. The included files can have preseed/include directives of their +# own as well. Note that if the filenames are relative, they are taken from +# the same directory as the preseed file that includes them. +#d-i preseed/include string x.cfg + +# The installer can optionally verify checksums of preseed files before +# using them. Currently only md5sums are supported, list the md5sums +# in the same order as the list of files to include. +#d-i preseed/include/checksum string 5da499872becccfeda2c4872f9171c3d + +# More flexibly, this runs a shell command and if it outputs the names of +# preseed files, includes those files. +#d-i preseed/include_command \ +# string echo if [ "`hostname`" = bob ]; then echo bob.cfg; fi + +# To check the format of your preseed file before performing an install, +# you can use debconf-set-selections: +# debconf-set-selections -c preseed.cfg +</screen></informalexample> diff --git a/ca/appendix/example-preseed-sarge.xml b/ca/appendix/example-preseed-sarge.xml new file mode 100644 index 000000000..3d79dda57 --- /dev/null +++ b/ca/appendix/example-preseed-sarge.xml @@ -0,0 +1,366 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 30372 untranslated --> + +<informalexample condition="sarge"><screen> +#### Startup. + +# To use a preseed file, you'll first need to boot the installer, +# and tell it what preseed file to use. This is done by passing the +# kernel a boot parameter, either manually at boot or by editing the +# syslinux.cfg (or similar) file and adding the parameter to the end +# of the append line(s) for the kernel. +# +# If you're netbooting, use this: +# preseed/url=http://host/path/to/preseed +# If you're remastering a CD, you could use this: +# preseed/file=/cdrom/preseed +# If you're installing from USB media, use this, and put the preseed file +# in the toplevel directory of the USB stick. +# preseed/file=/hd-media/preseed +# Be sure to copy this file to the location you specify. +# +# Some parts of the installation process cannot be automated using +# some forms of preseeding, because the questions are asked before +# the preseed file is loaded. For example, if the preseed file is +# downloaded over the network, the network setup must be done first. +# One reason to use initrd preseeding is that it allows preseeding +# of even these early steps of the installation process. +# +# If a preseed file cannot be used to preseed some steps, the install can +# still be fully automated, since you can pass preseed values to the kernel +# on the command line. Just pass path/to/var=value for any of the preseed +# variables listed below. +# +# While you're at it, you may want to throw a debconf/priority=critical in +# there, to avoid most questions even if the preseeding below misses some. +# And you might set the timeout to 1 in syslinux.cfg to avoid needing to hit +# enter to boot the installer. +# +# Note that the kernel accepts a maximum of 8 command line options and +# 8 environment options (including any options added by default for the +# installer). If these numbers are exceeded, 2.4 kernels will drop any +# excess options and 2.6 kernels will panic. With kernel 2.6.9 or newer, +# you can use 32 command line options and 32 environment options. +# +# Some of the default options, like 'vga=normal' may be safely removed +# for most installations, which may allow you to add more options for +# preseeding. + +# It is not possible to use preseeding to set language, country, and +# keyboard. Instead you should use kernel parameters. Example: +# languagechooser/language-name=English +# countrychooser/shortlist=US +# console-keymaps-at/keymap=us + +#### Network configuration. + +# Of course, this won't work if you're loading your preseed file from the +# network! But it's great if you're booting from CD or USB stick. You can +# also pass network config parameters in on the kernel params if you are +# loading preseed files from the network. + +# netcfg will choose an interface that has link if possible. This makes it +# skip displaying a list if there is more than one interface. +d-i netcfg/choose_interface select auto + +# If you have a slow dhcp server and the installer times out waiting for +# it, this might be useful. +#d-i netcfg/dhcp_timeout string 60 + +# If you prefer to configure the network manually, here's how: +#d-i netcfg/disable_dhcp boolean true +#d-i netcfg/get_nameservers string 192.168.1.1 +#d-i netcfg/get_ipaddress string 192.168.1.42 +#d-i netcfg/get_netmask string 255.255.255.0 +#d-i netcfg/get_gateway string 192.168.1.1 +#d-i netcfg/confirm_static boolean true + +# Note that any hostname and domain names assigned from dhcp take +# precedence over values set here. However, setting the values still +# prevents the questions from being shown even if values come from dhcp. +d-i netcfg/get_hostname string unassigned-hostname +d-i netcfg/get_domain string unassigned-domain + +# Disable that annoying WEP key dialog. +d-i netcfg/wireless_wep string +# The wacky dhcp hostname that some ISPs use as a password of sorts. +#d-i netcfg/dhcp_hostname string radish + +#### Mirror settings. + +d-i mirror/country string enter information manually +d-i mirror/http/hostname string http.us.debian.org +d-i mirror/http/directory string /debian +d-i mirror/suite string testing +d-i mirror/http/proxy string + +#### Partitioning. + +# If the system has free space you can choose to only partition that space. +#d-i partman-auto/init_automatically_partition \ +# select Use the largest continuous free space + +# Alternatively, you can specify a disk to partition. The device name can +# be given in either devfs or traditional non-devfs format. +# For example, to use the first disk devfs knows of: +d-i partman-auto/disk string /dev/discs/disc0/disc + +# You can choose from any of the predefined partitioning recipes: +d-i partman-auto/choose_recipe select \ + All files in one partition (recommended for new users) +#d-i partman-auto/choose_recipe select Desktop machine +#d-i partman-auto/choose_recipe select Multi-user workstation + +# Or provide a recipe of your own... +# The recipe format is documented in the file devel/partman-auto-recipe.txt. +# If you have a way to get a recipe file into the d-i environment, you can +# just point at it. +#d-i partman-auto/expert_recipe_file string /hd-media/recipe + +# If not, you can put an entire recipe in one line. This example creates +# a small /boot partition, suitable swap, and uses the rest of the space +# for the root partition: +#d-i partman-auto/expert_recipe string boot-root :: \ +# 20 50 100 ext3 $primary{ } $bootable{ } method{ format } format{ } \ +# use_filesystem{ } filesystem{ ext3 } mountpoint{ /boot } . \ +# 500 10000 1000000000 ext3 method{ format } format{ } \ +# use_filesystem{ } filesystem{ ext3 } mountpoint{ / } . \ +# 64 512 300% linux-swap method{ swap } format{ } . +# For reference, here is that same recipe in a more readable form: +# boot-root :: +# 40 50 100 ext3 +# $primary{ } $bootable{ } +# method{ format } format{ } +# use_filesystem{ } filesystem{ ext3 } +# mountpoint{ /boot } +# . +# 500 10000 1000000000 ext3 +# method{ format } format{ } +# use_filesystem{ } filesystem{ ext3 } +# mountpoint{ / } +# . +# 64 512 300% linux-swap +# method{ swap } format{ } +# . + +# This makes partman automatically partition without confirmation. +d-i partman/confirm_write_new_label boolean true +d-i partman/choose_partition select \ + Finish partitioning and write changes to disk +d-i partman/confirm boolean true + +#### Boot loader installation. + +# Grub is the default boot loader (for x86). If you want lilo installed +# instead, uncomment this: +#d-i grub-installer/skip boolean true + +# This is fairly safe to set, it makes grub install automatically to the MBR +# if no other operating system is detected on the machine. +d-i grub-installer/only_debian boolean true + +# This one makes grub-installer install to the MBR if if finds some other OS +# too, which is less safe as it might not be able to boot that other OS. +d-i grub-installer/with_other_os boolean true + +# Alternatively, if you want to install to a location other than the mbr, +# uncomment and edit these lines: +#d-i grub-installer/bootdev string (hd0,0) +#d-i grub-installer/only_debian boolean false +#d-i grub-installer/with_other_os boolean false + +#### Finishing up the first stage install. + +# Avoid that last message about the install being complete. +d-i prebaseconfig/reboot_in_progress note + +#### Shell commands. + +# d-i preseeding is inherently not secure. Nothing in the installer checks +# for attempts at buffer overflows or other exploits of the values of a +# preseed file like this one. Only use preseed files from trusted +# locations! To drive that home, and because it's generally useful, here's +# a way to run any shell command you'd like inside the installer, +# automatically. + +# This first command is run as early as possible, just after +# preseeding is read. +#d-i preseed/early_command string anna-install some-udeb + +# This command is run just before the install finishes, but when there is +# still a usable /target directory. +#d-i preseed/late_command string echo foo > /target/etc/bar + +# This command is run just as base-config is starting up. +#base-config base-config/early_command string echo hi mom + +# This command is run after base-config is done, just before the login: +# prompt. This is a good way to install a set of packages you want, or to +# tweak the configuration of the system. +#base-config base-config/late_command string \ +# apt-get install zsh; chsh -s /bin/zsh + +###### Preseeding the 2nd stage of the installation. + +#### Preseeding base-config. + +# Avoid the introductory message. +base-config base-config/intro note + +# Avoid the final message. +base-config base-config/login note + +# If you installed a display manager, but don't want to start it immediately +# after base-config finishes. +#base-config base-config/start-display-manager boolean false + +# Some versions of the installer can report back on what you've installed. +# The default is not to report back, but sending reports helps the project +# determine what software is most popular and include it on CDs. +#popularity-contest popularity-contest/participate boolean false + +#### Clock and time zone setup. + +# Controls whether or not the hardware clock is set to UTC. +#base-config tzconfig/gmt boolean true +# If you told the installer that you're in the United States, then you +# can set the time zone using this variable. +# (Choices are: Eastern, Central, Mountain, Pacific, Alaska, Hawaii, +# Aleutian, Arizona East-Indiana, Indiana-Starke, Michigan, Samoa, other) +#base-config tzconfig/choose_country_zone/US select Eastern +# If you told it you're in Canada. +# (Choices are: Newfoundland, Atlantic, Eastern, Central, +# East-Saskatchewan, Saskatchewan, Mountain, Pacific, Yukon, other) +#base-config tzconfig/choose_country_zone/CA select Eastern +# If you told it you're in Brazil. (Choices are: East, West, Acre, +# DeNoronha, other) +#base-config tzconfig/choose_country_zone/BR select East +# Many countries have only one time zone. If you told the installer you're +# in one of those countries, you can choose its standard time zone via this +# question. +#base-config tzconfig/choose_country_zone_single boolean true +# This question is asked as a fallback for countries other than those +# listed above, which have more than one time zone. You can preseed one of +# the time zones, or "other". +#base-config tzconfig/choose_country_zone_multiple select + +#### Account setup. + +# To preseed the root password, you have to put it in the clear in this +# file. That is not a very good idea, use caution! +#passwd passwd/root-password password r00tme +#passwd passwd/root-password-again password r00tme + +# If you want to skip creation of a normal user account. +#passwd passwd/make-user boolean false + +# Alternatively, you can preseed the user's name and login. +#passwd passwd/user-fullname string Debian User +#passwd passwd/username string debian +# And their password, but use caution! +#passwd passwd/user-password password insecure +#passwd passwd/user-password-again password insecure + +#### Apt setup. + +# This question controls what source the second stage installation uses +# for packages. Choices are cdrom, http, ftp, filesystem, edit sources list +# by hand +base-config apt-setup/uri_type select http + +# If you choose ftp or http, you'll be asked for a country and a mirror. +base-config apt-setup/country select enter information manually +base-config apt-setup/hostname string http.us.debian.org +base-config apt-setup/directory string /debian +# Stop after choosing one mirror. +base-config apt-setup/another boolean false + +# You can choose to install non-free and contrib software. +#base-config apt-setup/non-free boolean true +#base-config apt-setup/contrib boolean true + +# Do enable security updates. +base-config apt-setup/security-updates boolean true + +#### Package selection. + +# You can choose to install any combination of tasks that are available. +# Available tasks as of this writing include: Desktop environment, +# Web server, Print server, DNS server, File server, Mail server, +# SQL database, Laptop, Standard system, manual package selection. The +# last of those will run aptitude. You can also choose to install no +# tasks, and force the installation of a set of packages in some other +# way. We recommend always including the Standard system task. +tasksel tasksel/first multiselect Desktop environment, Standard system +#tasksel tasksel/first multiselect Web server, Standard system + +#### Mailer configuration. + +# During a normal install, exim asks only a few questions. Here's how to +# avoid even those. More complicated preseeding is possible. +exim4-config exim4/dc_eximconfig_configtype \ + select no configuration at this time +exim4-config exim4/no_config boolean true +exim4-config exim4/no_config boolean true + +# It's a good idea to set this to whatever user account you choose to +# create. Leaving the value blank results in postmaster mail going to +# /var/mail/mail. +exim4-config exim4/dc_postmaster string + +#### X Configuration. + +# Preseeding Debian's X config is possible, but you probably need to know +# some details about the video hardware of the machine, since Debian's X +# configurator does not do fully automatic configuration of everything. + +# X can detect the right driver for some cards, but if you're preseeding, +# you override whatever it chooses. Still, vesa will work most places. +#xserver-xfree86 xserver-xfree86/config/device/driver select vesa + +# A caveat with mouse autodetection is that if it fails, X will retry it +# over and over. So if it's preseeded to be done, there is a possibility of +# an infinite loop if the mouse is not autodetected. +#xserver-xfree86 xserver-xfree86/autodetect_mouse boolean true + +# Monitor autodetection is recommended. +xserver-xfree86 xserver-xfree86/autodetect_monitor boolean true +# Uncomment if you have an LCD display. +#xserver-xfree86 xserver-xfree86/config/monitor/lcd boolean true +# X has three configuration paths for the monitor. Here's how to preseed +# the "medium" path, which is always available. The "simple" path may not +# be available, and the "advanced" path asks too many questions. +xserver-xfree86 xserver-xfree86/config/monitor/selection-method \ + select medium +xserver-xfree86 xserver-xfree86/config/monitor/mode-list \ + select 1024x768 @ 60 Hz + +#### Everything else. + +# Depending on what software you choose to install, or if things go wrong +# during the installation process, it's possible that other questions may +# be asked. You can preseed those too, of course. To get a list of every +# possible question that could be asked during an install, do an +# installation, and then run these commands: +# debconf-get-selections --installer > file +# debconf-get-selections >> file + +# If you like, you can include other preseed files into this one. +# Any settings in those files will override pre-existing settings from this +# file. More that one file can be listed, separated by spaces; all will be +# loaded. The included files can have preseed/include directives of their +# own as well. Note that if the filenames are relative, they are taken from +# the same directory as the preseed file that includes them. +#d-i preseed/include string x.cfg + +# More flexibly, this runs a shell command and if it outputs the names of +# preseed files, includes those files. For example, to switch configs based +# on a particular usb storage device (in this case, a built-in card reader): +#d-i preseed/include_command string \ +# if $(grep -q "GUID: 0aec3050aec305000001a003" /proc/scsi/usb-storage-*/*); \ +# then echo kraken.cfg; else echo otherusb.cfg; fi + +# To check the format of your preseed file before performing an install, +# you can use debconf-set-selections: +# debconf-set-selections -c preseed.cfg +</screen></informalexample> diff --git a/ca/appendix/example-preseed.xml b/ca/appendix/example-preseed.xml new file mode 100644 index 000000000..58339363d --- /dev/null +++ b/ca/appendix/example-preseed.xml @@ -0,0 +1,39 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 30379 untranslated --> + +<sect1 id="example-preseed"> +<title>Preconfiguration File Example</title> + +<para> + +This is a complete working example of a preconfiguration file for an automated +install. Its use is explained in <xref linkend="automatic-install"/>. You +may want to uncomment some of the lines before using the file. + +</para> + +<note condition="sarge"><para> + +In order to be able to properly present this example in the manual, we've had +to split some lines. This is indicated by the use of the line-continuation-character +<quote>\</quote> and extra indentation in the next line. In a real preconfiguration +file, these split lines have to be joined into <emphasis>one single line</emphasis>. +If you do not, preconfiguration will fail with unpredictable results. + +</para><para> + +A <quote>clean</quote> example file is available from &urlset-example-preseed;. + +</para></note> + +<para condition="etch"> + +The example file is also available from &urlset-example-preseed;. + +</para><para> + +&example-preseed-sarge.xml; +&example-preseed-etch.xml; + +</para> +</sect1> diff --git a/ca/appendix/files.xml b/ca/appendix/files.xml new file mode 100644 index 000000000..555a6395b --- /dev/null +++ b/ca/appendix/files.xml @@ -0,0 +1,298 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 untranslated --> + + + <sect1 id="linuxdevices"><title>Linux Devices</title> +<para> + +In Linux you have various special files in +<filename>/dev</filename>. These files are called device files. In +the Unix world accessing hardware is different. There you have a +special file which actually runs a driver which in turn accesses the +hardware. The device file is an interface to the actual system +component. Files under <filename>/dev</filename> also behave +differently than ordinary files. Below are the most important device +files listed. + +</para><para> + +<informaltable><tgroup cols="2"><tbody> +<row> + <entry><filename>fd0</filename></entry> + <entry>First Floppy Drive</entry> +</row><row> + <entry><filename>fd1</filename></entry> + <entry>Second Floppy Drive</entry> +</row> +</tbody></tgroup></informaltable> + +<informaltable><tgroup cols="2"><tbody> +<row> + <entry><filename>hda</filename></entry> + <entry>IDE Hard disk / CD-ROM on the first IDE port (Master)</entry> +</row><row> + <entry><filename>hdb</filename></entry> + <entry>IDE Hard disk / CD-ROM on the first IDE port (Slave)</entry> +</row><row> + <entry><filename>hdc</filename></entry> + <entry>IDE Hard disk / CD-ROM on the second IDE port (Master)</entry> +</row><row> + <entry><filename>hdd</filename></entry> + <entry>IDE Hard disk / CD-ROM on the second IDE port (Slave)</entry> +</row><row> + <entry><filename>hda1</filename></entry> + <entry>First partition of the first IDE hard disk</entry> +</row><row> + <entry><filename>hdd15</filename></entry> + <entry>Fifteenth partition of the fourth IDE hard disk</entry> +</row> +</tbody></tgroup></informaltable> + +<informaltable><tgroup cols="2"><tbody> +<row> + <entry><filename>sda</filename></entry> + <entry>SCSI Hard disk with lowest SCSI ID (e.g. 0)</entry> +</row><row> + <entry><filename>sdb</filename></entry> + <entry>SCSI Hard disk with next higher SCSI ID (e.g. 1)</entry> +</row><row> + <entry><filename>sdc</filename></entry> + <entry>SCSI Hard disk with next higher SCSI ID (e.g. 2)</entry> +</row><row> + <entry><filename>sda1</filename></entry> + <entry>First partition of the first SCSI hard disk</entry> +</row><row> + <entry><filename>sdd10</filename></entry> + <entry>Tenth partition of the fourth SCSI hard disk</entry> +</row> +</tbody></tgroup></informaltable> + +<informaltable><tgroup cols="2"><tbody> +<row> + <entry><filename>sr0</filename></entry> + <entry>SCSI CD-ROM with the lowest SCSI ID</entry> +</row><row> + <entry><filename>sr1</filename></entry> + <entry>SCSI CD-ROM with the next higher SCSI ID</entry> +</row> +</tbody></tgroup></informaltable> + +<informaltable><tgroup cols="2"><tbody> +<row> + <entry><filename>ttyS0</filename></entry> + <entry>Serial port 0, COM1 under MS-DOS</entry> +</row><row> + <entry><filename>ttyS1</filename></entry> + <entry>Serial port 1, COM2 under MS-DOS</entry> +</row><row> + <entry><filename>psaux</filename></entry> + <entry>PS/2 mouse device</entry> +</row><row> + <entry><filename>gpmdata</filename></entry> + <entry>Pseudo device, repeater data from GPM (mouse) daemon</entry> +</row> +</tbody></tgroup></informaltable> + +<informaltable><tgroup cols="2"><tbody> +<row> + <entry><filename>cdrom</filename></entry> + <entry>Symbolic link to the CD-ROM drive</entry> +</row><row> + <entry><filename>mouse</filename></entry> + <entry>Symbolic link to the mouse device file</entry> +</row> +</tbody></tgroup></informaltable> + +<informaltable><tgroup cols="2"><tbody> +<row> + <entry><filename>null</filename></entry> + <entry>Everything pointed to this device will disappear</entry> +</row><row> + <entry><filename>zero</filename></entry> + <entry>One can endlessly read zeros out of this device</entry> +</row> +</tbody></tgroup></informaltable> + +</para> + + <sect2> +<title>Setting Up Your Mouse</title> + +<para> + +The mouse can be used in both the Linux console (with gpm) and the X window +environment. The two uses can be made compatible if the gpm repeater is used +to allow the signal to flow to the X server as shown: + +<informalexample><screen> +mouse => /dev/psaux => gpm => /dev/gpmdata -> /dev/mouse => X + /dev/ttyS0 (repeater) (symlink) + /dev/ttyS1 +</screen></informalexample> + +Set the repeater protocol to be raw (in <filename>/etc/gpm.conf</filename>) while +setting X to the original mouse protocol in <filename>/etc/X11/XF86Config</filename> +or <filename>/etc/X11/XF86Config-4</filename>. + +</para><para> + +This approach to use gpm even in X has advantages when the mouse is +unplugged inadvertently. Simply restarting gpm with + +<informalexample><screen> +# /etc/init.d/gpm restart +</screen></informalexample> + +will re-connect the mouse in software without restarting X. + +</para><para> + +If gpm is disabled or not installed with some reason, make sure to set X to +read directly from the mouse device such as /dev/psaux. For details, refer +to the 3-Button Mouse mini-Howto at +<filename>/usr/share/doc/HOWTO/en-txt/mini/3-Button-Mouse.gz</filename>, +<userinput>man gpm</userinput>, +<filename>/usr/share/doc/gpm/FAQ.gz</filename>, and +<ulink url="&url-xfree86;current/mouse.html">README.mouse</ulink>. + +</para><para arch="powerpc"> + +For PowerPC, in <filename>/etc/X11/XF86Config</filename> or +<filename>/etc/X11/XF86Config-4</filename>, set the mouse device to +<userinput>"/dev/input/mice"</userinput>. + +</para><para arch="powerpc"> + +Modern kernels give you the capability to emulate a three-button mouse +when your mouse only has one button. Just add the following lines to +<filename>/etc/sysctl.conf</filename> file. + +<informalexample><screen> +# 3-button mouse emulation +# turn on emulation +/dev/mac_hid/mouse_button_emulation = 1 +# Send middle mouse button signal with the F11 key +/dev/mac_hid/mouse_button2_keycode = 87 +# Send right mouse button signal with the F12 key +/dev/mac_hid/mouse_button3_keycode = 88 +# For different keys, use showkey to tell you what the code is. +</screen></informalexample> + +</para> + </sect2> + </sect1> + + <sect1 id="tasksel-size-list"> + <title>Disk Space Needed for Tasks</title> + +<!-- Note for d-i and manual maintainers + Sizes of tasks should be determined by running "tasksel new" on a system + that been fully installed without selecting any tasks. By selecting a + task together with the "manual selection" option, aptitude will be started + and show the sizes for the task. After deselecting the packages to be + installed, quit aptitude and repeat for other tasks. + Space requirements need to be determined from tasksel as tasksel will not + install recommended packages while selecting a task from aptitude will. +--> + +<para> + +The base installation for i386 using the default 2.4 kernel, +including all standard packages, requires 573MB of disk space. + +</para><para> + +The following table lists sizes reported by aptitude for the tasks listed +in tasksel. Note that some tasks have overlapping constituents, so the +total installed size for two tasks together may be less than the total +obtained by adding up the numbers. + +</para><para> + +Note that you will need to add the sizes listed in the table to the size +of the base installation when determining the size of partitions. +Most of the size listed as <quote>Installed size</quote> will end up in +<filename>/usr</filename>; the size listed as <quote>Download size</quote> +is (temporarily) required in <filename>/var</filename>. + +</para><para> + +<informaltable><tgroup cols="4"> +<thead> +<row> + <entry>Task</entry> + <entry>Installed size (MB)</entry> + <entry>Download size (MB)</entry> + <entry>Space needed to install (MB)</entry> +</row> +</thead> + +<tbody> +<row> + <entry>Desktop</entry> + <entry>1392</entry> + <entry>460</entry> + <entry>1852</entry> +</row> + +<row> + <entry>Web server</entry> + <entry>36</entry> + <entry>12</entry> + <entry>48</entry> +</row> + +<row> + <entry>Print server</entry> + <entry>168</entry> + <entry>58</entry> + <entry>226</entry> +</row> + +<row> + <entry>DNS server</entry> + <entry>2</entry> + <entry>1</entry> + <entry>3</entry> +</row> + +<row> + <entry>File server</entry> + <entry>47</entry> + <entry>24</entry> + <entry>71</entry> +</row> + +<row> + <entry>Mail server</entry> + <entry>10</entry> + <entry>3</entry> + <entry>13</entry> +</row> + +<row> + <entry>SQL database</entry> + <entry>66</entry> + <entry>21</entry> + <entry>87</entry> +</row> + +</tbody> +</tgroup></informaltable> + +<note><para> + +The <emphasis>Desktop</emphasis> task will install both the Gnome and KDE +desktop environments. + +</para></note> + +</para><para> + +If you install in a language other than English, <command>tasksel</command> +may automatically install a <firstterm>localization task</firstterm>, if one +is available for your language. Space requirements differ per language; +you should allow up to 200MB in total for download and installation. + +</para> + </sect1> diff --git a/ca/appendix/gpl.xml b/ca/appendix/gpl.xml new file mode 100644 index 000000000..ba5782af2 --- /dev/null +++ b/ca/appendix/gpl.xml @@ -0,0 +1,512 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 29618 untranslated --> + +<appendix id="appendix-gpl"><title>GNU General Public License</title> + +<para> + +Version 2, June 1991 + +</para><para> + +Copyright (C) 1989, 1991 Free Software Foundation, Inc. +— +51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA. +</para><para> + +Everyone is permitted to copy and distribute verbatim copies +of this license document, but changing it is not allowed. + +</para> + + <sect1><title>Preamble</title> +<para> + +The licenses for most software are designed to take away your freedom +to share and change it. By contrast, the gnu General Public License +is intended to guarantee your freedom to share and change free +software — to make sure the software is free for all its users. This +General Public License applies to most of the Free Software +Foundation's software and to any other program whose authors commit +to using it. (Some other Free Software Foundation software is covered +by the gnu Library General Public License instead.) You can apply it +to your programs, too. + +</para><para> + +When we speak of free software, we are referring to freedom, not +price. Our General Public Licenses are designed to make sure that you +have the freedom to distribute copies of free software (and charge +for this service if you wish), that you receive source code or can +get it if you want it, that you can change the software or use pieces +of it in new free programs; and that you know you can do these +things. + +</para><para> + +To protect your rights, we need to make restrictions that forbid +anyone to deny you these rights or to ask you to surrender the +rights. These restrictions translate to certain responsibilities for +you if you distribute copies of the software, or if you modify it. + +</para><para> + +For example, if you distribute copies of such a program, whether +gratis or for a fee, you must give the recipients all the rights that +you have. You must make sure that they, too, receive or can get the +source code. And you must show them these terms so they know their +rights. + +</para><para> + +We protect your rights with two steps: (1) copyright the software, +and (2) offer you this license which gives you legal permission to +copy, distribute and/or modify the software. + +</para><para> + +Also, for each author's protection and ours, we want to make certain +that everyone understands that there is no warranty for this free +software. If the software is modified by someone else and passed on, +we want its recipients to know that what they have is not the +original, so that any problems introduced by others will not reflect +on the original authors' reputations. + +</para><para> + +Finally, any free program is threatened constantly by software +patents. We wish to avoid the danger that redistributors of a free +program will individually obtain patent licenses, in effect making +the program proprietary. To prevent this, we have made it clear that +any patent must be licensed for everyone's free use or not licensed +at all. + +</para><para> + +The precise terms and conditions for copying, distribution and +modification follow. + +</para> + </sect1> + + <sect1><title>GNU GENERAL PUBLIC LICENSE</title> +<para> + +TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION + +</para> + +<itemizedlist><listitem><para> + +This License applies to any program or other work which contains a +notice placed by the copyright holder saying it may be distributed +under the terms of this General Public License. The "Program", below, +refers to any such program or work, and a "work based on the Program" +means either the Program or any derivative work under copyright law: +that is to say, a work containing the Program or a portion of it, +either verbatim or with modifications and/or translated into another +language. (Hereinafter, translation is included without limitation in +the term "modification".) Each licensee is addressed as "you". + +</para><para> + +Activities other than copying, distribution and modification are not +covered by this License; they are outside its scope. The act of +running the Program is not restricted, and the output from the +Program is covered only if its contents constitute a work based on +the Program (independent of having been made by running the Program). +Whether that is true depends on what the Program does. + +</para></listitem> +<listitem><para> + +You may copy and distribute verbatim copies of the Program's +source code as you receive it, in any medium, provided that you +conspicuously and appropriately publish on each copy an appropriate +copyright notice and disclaimer of warranty; keep intact all the +notices that refer to this License and to the absence of any +warranty; and give any other recipients of the Program a copy of this +License along with the Program. + +</para><para> + +You may charge a fee for the physical act of transferring a copy, and +you may at your option offer warranty protection in exchange for a +fee. + +</para></listitem> +<listitem><para> + +You may modify your copy or copies of the Program or any portion +of it, thus forming a work based on the Program, and copy and +distribute such modifications or work under the terms of Section 1 +above, provided that you also meet all of these conditions: + +</para><para> + +a) You must cause the modified files to carry prominent notices +stating that you changed the files and the date of any change. + +</para><para> + +b) You must cause any work that you distribute or publish, that in +whole or in part contains or is derived from the Program or any part +thereof, to be licensed as a whole at no charge to all third parties +under the terms of this License. + +</para><para> + +c) If the modified program normally reads commands interactively when +run, you must cause it, when started running for such interactive use +in the most ordinary way, to print or display an announcement +including an appropriate copyright notice and a notice that there is +no warranty (or else, saying that you provide a warranty) and that +users may redistribute the program under these conditions, and +telling the user how to view a copy of this License. (Exception: if +the Program itself is interactive but does not normally print such an +announcement, your work based on the Program is not required to print +an announcement.) + +</para><para> + +These requirements apply to the modified work as a whole. If +identifiable sections of that work are not derived from the Program, +and can be reasonably considered independent and separate works in +themselves, then this License, and its terms, do not apply to those +sections when you distribute them as separate works. But when you +distribute the same sections as part of a whole which is a work based +on the Program, the distribution of the whole must be on the terms of +this License, whose permissions for other licensees extend to the +entire whole, and thus to each and every part regardless of who wrote +it. + +</para><para> + +Thus, it is not the intent of this section to claim rights or contest +your rights to work written entirely by you; rather, the intent is to +exercise the right to control the distribution of derivative or +collective works based on the Program. + +</para><para> + +In addition, mere aggregation of another work not based on the +Program with the Program (or with a work based on the Program) on a +volume of a storage or distribution medium does not bring the other +work under the scope of this License. + +</para></listitem> +<listitem><para> + +You may copy and distribute the Program (or a work based on it, +under Section 2) in object code or executable form under the terms of +Sections 1 and 2 above provided that you also do one of the +following: + +</para><para> + +a) Accompany it with the complete corresponding machine-readable +source code, which must be distributed under the terms of Sections 1 +and 2 above on a medium customarily used for software interchange; +or, + +</para><para> + +b) Accompany it with a written offer, valid for at least three years, +to give any third party, for a charge no more than your cost of +physically performing source distribution, a complete +machine-readable copy of the corresponding source code, to be +distributed under the terms of Sections 1 and 2 above on a medium +customarily used for software interchange; or, + +</para><para> + +c) Accompany it with the information you received as to the offer to +distribute corresponding source code. (This alternative is allowed +only for noncommercial distribution and only if you received the +program in object code or executable form with such an offer, in +accord with Subsection b above.) + +</para><para> + +The source code for a work means the preferred form of the work for +making modifications to it. For an executable work, complete source +code means all the source code for all modules it contains, plus any +associated interface definition files, plus the scripts used to +control compilation and installation of the executable. However, as a +special exception, the source code distributed need not include +anything that is normally distributed (in either source or binary +form) with the major components (compiler, kernel, and so on) of the +operating system on which the executable runs, unless that component +itself accompanies the executable. + +</para><para> + +If distribution of executable or object code is made by offering +access to copy from a designated place, then offering equivalent +access to copy the source code from the same place counts as +distribution of the source code, even though third parties are not +compelled to copy the source along with the object code. + +</para></listitem> +<listitem><para> + +You may not copy, modify, sublicense, or distribute the Program +except as expressly provided under this License. Any attempt +otherwise to copy, modify, sublicense or distribute the Program is +void, and will automatically terminate your rights under this +License. However, parties who have received copies, or rights, from +you under this License will not have their licenses terminated so +long as such parties remain in full compliance. + +</para></listitem> +<listitem><para> + +You are not required to accept this License, since you have not +signed it. However, nothing else grants you permission to modify or +distribute the Program or its derivative works. These actions are +prohibited by law if you do not accept this License. Therefore, by +modifying or distributing the Program (or any work based on the +Program), you indicate your acceptance of this License to do so, and +all its terms and conditions for copying, distributing or modifying +the Program or works based on it. + +</para></listitem> +<listitem><para> + +Each time you redistribute the Program (or any work based on the +Program), the recipient automatically receives a license from the +original licensor to copy, distribute or modify the Program subject +to these terms and conditions. You may not impose any further +restrictions on the recipients' exercise of the rights granted +herein. You are not responsible for enforcing compliance by third +parties to this License. + +</para></listitem> +<listitem><para> + +If, as a consequence of a court judgment or allegation of patent +infringement or for any other reason (not limited to patent issues), +conditions are imposed on you (whether by court order, agreement or +otherwise) that contradict the conditions of this License, they do +not excuse you from the conditions of this License. If you cannot +distribute so as to satisfy simultaneously your obligations under +this License and any other pertinent obligations, then as a +consequence you may not distribute the Program at all. For example, +if a patent license would not permit royalty-free redistribution of +the Program by all those who receive copies directly or indirectly +through you, then the only way you could satisfy both it and this +License would be to refrain entirely from distribution of the +Program. + +</para><para> + +If any portion of this section is held invalid or unenforceable under +any particular circumstance, the balance of the section is intended +to apply and the section as a whole is intended to apply in other +circumstances. + +</para><para> + +It is not the purpose of this section to induce you to infringe any +patents or other property right claims or to contest validity of any +such claims; this section has the sole purpose of protecting the +integrity of the free software distribution system, which is +implemented by public license practices. Many people have made +generous contributions to the wide range of software distributed +through that system in reliance on consistent application of that +system; it is up to the author/donor to decide if he or she is +willing to distribute software through any other system and a +licensee cannot impose that choice. + +</para><para> + +This section is intended to make thoroughly clear what is believed to +be a consequence of the rest of this License. + +</para></listitem> +<listitem><para> + +If the distribution and/or use of the Program is restricted in +certain countries either by patents or by copyrighted interfaces, the +original copyright holder who places the Program under this License +may add an explicit geographical distribution limitation excluding +those countries, so that distribution is permitted only in or among +countries not thus excluded. In such case, this License incorporates +the limitation as if written in the body of this License. + +</para></listitem> +<listitem><para> + +The Free Software Foundation may publish revised and/or new +versions of the General Public License from time to time. Such new +versions will be similar in spirit to the present version, but may +differ in detail to address new problems or concerns. Each version is +given a distinguishing version number. If the Program specifies a +version number of this License which applies to it and "any later +version", you have the option of following the terms and conditions +either of that version or of any later version published by the Free +Software Foundation. If the Program does not specify a version number +of this License, you may choose any version ever published by the +Free Software Foundation. + +</para></listitem> +<listitem><para> + +If you wish to incorporate parts of the Program into other free +programs whose distribution conditions are different, write to the +author to ask for permission. For software which is copyrighted by +the Free Software Foundation, write to the Free Software Foundation; +we sometimes make exceptions for this. Our decision will be guided by +the two goals of preserving the free status of all derivatives of our +free software and of promoting the sharing and reuse of software +generally. + +</para><para> + +NO WARRANTY + +</para></listitem> +<listitem><para> + +because the program is licensed free of charge, there is no +warranty for the program, to the extent permitted by applicable law. +except when otherwise stated in writing the copyright holders and/or +other parties provide the program "as is" without warranty of any +kind, either expressed or implied, including, but not limited to, the +implied warranties of merchantability and fitness for a particular +purpose. the entire risk as to the quality and performance of the +program is with you. should the program prove defective, you assume +the cost of all necessary servicing, repair or correction. + +</para></listitem> +<listitem><para> + +in no event unless required by applicable law or agreed to in +writing will any copyright holder, or any other party who may modify +and/or redistribute the program as permitted above, be liable to you +for damages, including any general, special, incidental or +consequential damages arising out of the use or inability to use the +program (including but not limited to loss of data or data being +rendered inaccurate or losses sustained by you or third parties or a +failure of the program to operate with any other programs), even if +such holder or other party has been advised of the possibility of +such damages. + +</para></listitem> +</itemizedlist> +<para> + +END OF TERMS AND CONDITIONS + +</para> + </sect1> + + <sect1><title>How to Apply These Terms to Your New Programs</title> +<para> + +If you develop a new program, and you want it to be of the greatest +possible use to the public, the best way to achieve this is to make +it free software which everyone can redistribute and change under +these terms. + +</para><para> + +To do so, attach the following notices to the program. It is safest +to attach them to the start of each source file to most effectively +convey the exclusion of warranty; and each file should have at least +the "copyright" line and a pointer to where the full notice is found. + +</para><para> + +one line to give the program's name and a brief idea of what it +does. + +</para><para> + +Copyright (C) year name of author + +</para><para> + +This program is free software; you can redistribute it and/or modify +it under the terms of the gnu General Public License as published by +the Free Software Foundation; either version 2 of the License, or (at +your option) any later version. + +</para><para> + +This program is distributed in the hope that it will be useful, but +without any warranty; without even the implied warranty of +merchantability or fitness for a particular purpose. See the gnu +General Public License for more details. + +</para><para> + +You should have received a copy of the gnu General Public License +along with this program; if not, write to the Free Software +Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, +MA 02110-1301, USA. + +</para><para> + +Also add information on how to contact you by electronic and paper +mail. + +</para><para> + +If the program is interactive, make it output a short notice like +this when it starts in an interactive mode: + +</para><para> + +Gnomovision version 69, Copyright (C) year name of author + +</para><para> + +Gnomovision comes with absolutely no warranty; for details type `show +w'. + +</para><para> + +This is free software, and you are welcome to redistribute it under +certain conditions; type `show c' for details. + +</para><para> + +The hypothetical commands `show w' and `show c' should show the +appropriate parts of the General Public License. Of course, the +commands you use may be called something other than `show w' and +`show c'; they could even be mouse-clicks or menu items — whatever +suits your program. + +</para><para> + +You should also get your employer (if you work as a programmer) or +your school, if any, to sign a "copyright disclaimer" for the +program, if necessary. Here is a sample; alter the names: + +</para><para> + +Yoyodyne, Inc., hereby disclaims all copyright interest in the +program `Gnomovision' (which makes passes at compilers) written by +James Hacker. + +</para><para> + +signature of Ty Coon, 1 April 1989 + +</para><para> + +Ty Coon, President of Vice + +</para><para> + +This General Public License does not permit incorporating your +program into proprietary programs. If your program is a subroutine +library, you may consider it more useful to permit linking +proprietary applications with the library. If this is what you want +to do, use the gnu Library General Public License instead of this +License. + +</para> + </sect1> +</appendix> diff --git a/ca/appendix/plip.xml b/ca/appendix/plip.xml new file mode 100644 index 000000000..74913ab34 --- /dev/null +++ b/ca/appendix/plip.xml @@ -0,0 +1,194 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 29687 untranslated --> + + <sect1 id="plip" arch="i386"> + <title>Installing &debian; over Parallel Line IP (PLIP)</title> + +<para> + +This section explains how to install &debian; on a computer without +Ethernet card, but with just a remote gateway computer attached via +a Null-Modem cable (also called Null-Printer cable). The gateway +computer should be connected to a network that has a Debian mirror +on it (e.g. to the Internet). + +</para><para> + +In the example in this appendix we will set up a PLIP connection using +a gateway connected to the Internet over a dial-up connection (ppp0). +We will use IP addresses 192.168.0.1 and 192.168.0.2 for the PLIP +interfaces on the target system and the source system respectively +(these addresses should be unused within your network address space). + +</para><para> + +The PLIP connection set up during the installation will also be available +after the reboot into the installed system (see <xref linkend="boot-new"/>). + +</para><para> + +Before you start, you will need to check the BIOS configuration (IO base +address and IRQ) for the parallel ports of both the source and target +systems. The most common values are <literal>io=0x378</literal>, +<literal>irq=7</literal>. + +</para> + + <sect2> + <title>Requirements</title> + +<itemizedlist> +<listitem><para> + +A target computer, called <emphasis>target</emphasis>, where Debian will be +installed. + +</para></listitem> +<listitem><para> + +System installation media; see <xref linkend="installation-media"/>. + +</para></listitem> +<listitem><para> + +Another computer connected to the Internet, called <emphasis>source</emphasis>, +that will function as the gateway. + +</para></listitem> +<listitem><para> + +A DB-25 Null-Modem cable. See the +<ulink url="&url-plip-install-howto;">PLIP-Install-HOWTO</ulink> for more +information on this cable and instructions how to make your own. + +</para></listitem> +</itemizedlist> + + </sect2> + + <sect2> + <title>Setting up source</title> +<para> + +The following shell script is a simple example of how to configure the +source computer as a gateway to the Internet using ppp0. + +<informalexample><screen> +#!/bin/sh + +# We remove running modules from kernel to avoid conflicts and to +# reconfigure them manually. +modprobe -r lp parport_pc +modprobe parport_pc io=<replaceable>0x378</replaceable> irq=<replaceable>7</replaceable> +modprobe plip + +# Configure the plip interface (plip0 for me, see dmesg | grep plip) +ifconfig <replaceable>plip0 192.168.0.2</replaceable> pointopoint <replaceable>192.168.0.1</replaceable> netmask 255.255.255.255 up + +# Configure gateway +modprobe iptable_nat +iptables -t nat -A POSTROUTING -o <replaceable>ppp0</replaceable> -j MASQUERADE +echo 1 > /proc/sys/net/ipv4/ip_forward +</screen></informalexample> + +</para> + </sect2> + + <sect2> + <title>Installing target</title> +<para> + +Boot the installation media. The installation needs to be run in +expert mode; enter <userinput>expert</userinput> at the boot prompt. +Below are the answers that should be given during various stages of +the installation. + +</para> + +<orderedlist> +<listitem><para> + +<guimenuitem>Load installer components</guimenuitem> + +</para><para> + +Select the <userinput>plip-modules</userinput> option from the list; this +will make the PLIP drivers available to the installation system. + +</para></listitem> +<listitem><para> + +<guimenuitem>Detect network hardware</guimenuitem> + +</para> + + <itemizedlist> + <listitem><para> + +If target <emphasis>does</emphasis> have a network card, a list of driver +modules for detected cards will be shown. If you want to force &d-i; to +use plip instead, you have to deselect all listed driver modules. +Obviously, if target doesn't have a network card, the installer will not +show this list. + + </para></listitem> + <listitem><para> + +Prompt for module parameters: Yes + + </para></listitem> + <listitem><para> + +Because no network card was detected/selected earlier, the installer will +ask you to select a network driver module from a list. +Select the <userinput>plip</userinput> module. + + </para></listitem> + <listitem><para> + +Additional parameters for module parport_pc: +<userinput><replaceable>io=0x378 irq=7</replaceable></userinput> + + </para></listitem> + <listitem><para> + +Additional parameters for module plip: leave empty + + </para></listitem> + </itemizedlist> + +</listitem> +<listitem><para> + +<guimenuitem>Configure the network</guimenuitem> + + <itemizedlist> + <listitem><para> + +Auto-configure network with DHCP: No + + </para></listitem> + <listitem><para> + +IP address: <userinput><replaceable>192.168.0.1</replaceable></userinput> + + </para></listitem> + <listitem><para> + +Point-to-point address: +<userinput><replaceable>192.168.0.2</replaceable></userinput> + + </para></listitem> + <listitem><para> + +Name server addresses: you can enter the same addresses used on +source (see <filename>/etc/resolv.conf</filename>) + + </para></listitem> + </itemizedlist> + +</para></listitem> +</orderedlist> + + </sect2> + </sect1> diff --git a/ca/appendix/random-bits.xml b/ca/appendix/random-bits.xml new file mode 100644 index 000000000..517dda275 --- /dev/null +++ b/ca/appendix/random-bits.xml @@ -0,0 +1,11 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 29687 --> + +<appendix id="random-bits"><title>Informació variada</title> + +&example-preseed.xml; +&files.xml; +&chroot-install.xml; +&plip.xml; + +</appendix> diff --git a/ca/bookinfo.xml b/ca/bookinfo.xml new file mode 100644 index 000000000..4eb8c3674 --- /dev/null +++ b/ca/bookinfo.xml @@ -0,0 +1,58 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 29882 --> + +<bookinfo id="debian_installation_guide"> +<title>Guia d'instal·lació de &debian;</title> + +<abstract> +<para> +Aquest document conté les instruccions d'instal·lació per a la versió +&release; del sistema &debian; (nom en codi <quote>&releasename;</quote>) +per a l'arquitectura &arch-title; (<quote>&architecture;</quote>). També +conté referències per obtenir més informació i informació de com aprofitar +al màxim el vostre nou sistema Debian. +</para> + +<para> +<warning condition="not-checked"><para> +Aquesta guia d'instal·lació està basada en un manual anterior escrit +per al sistema d'insta·lació antic de Debian (els «boot-floppies»), +i ha estat actualitzat per a documentar el nou instal·lador de Debian. +No obstant, per a &architecture;, el manual no ha estat completament +actualitzat i comprovada la seva veracitat per al nou instal·lador. Pot +ser que algunes parts del manual encara estiguin incompletes o +desactualitzades o que encara documentin l'insta·lador «boot-floppies». +Podeu trobar una versió més nova d'aquest manual, possiblement documentant +millor aquesta arquitectura, a internet a la <ulink url="&url-d-i;">pàgina +de &d-i;</ulink>. Podreu trobar-hi també traduccions addicionals. +</para></warning> + +<note condition="checked"><para> +Tot i que aquesta guia d'instal·lació per a &architecture; està +majoritariament al dia, planegem fer alguns canvis i reorganitzar +part del manual després del llançament oficial de &releasename;. +Podeu trobar una versió més nova d'aquest manual a internet a la +<ulink url="&url-d-i;">pàgina de &d-i;</ulink>. Podreu trobar-hi +també traduccions addicionals. +</para></note> +</para> +</abstract> + +<copyright> + <year>2004</year> + <year>2005</year> + <holder>l'equip de l'instal·lador de Debian</holder> +</copyright> + +<legalnotice> +<para> + +Aquest manual és programari lliure; podeu redistribuir-lo i/o +modificar-lo sota els termes de la Llicència Pública General de GNU +publicada per la Free Software Foundation. Feu un cop d'ull +a la llicència a <xref linkend="appendix-gpl"/>. + +</para> +</legalnotice> +</bookinfo> + diff --git a/ca/boot-installer/alpha.xml b/ca/boot-installer/alpha.xml new file mode 100644 index 000000000..d43770c8b --- /dev/null +++ b/ca/boot-installer/alpha.xml @@ -0,0 +1,441 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 29334 untranslated --> + + <sect2 arch="alpha" id="alpha-firmware"> + <title>Alpha Console Firmware</title> +<para> + +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: + +</para> + +<itemizedlist> +<listitem><para> + + <emphasis>SRM console</emphasis>, based on the Alpha Console Subsystem + specification, which provides an operating environment for OpenVMS, Tru64 + UNIX, and Linux operating systems. + +</para></listitem> +<listitem><para> + + <emphasis>ARC, AlphaBIOS, or ARCSBIOS console</emphasis>, based on the + Advanced RISC Computing (ARC) specification, which provides an operating + environment for Windows NT. + +</para></listitem> +</itemizedlist> + +<para> + +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. + +</para><para> + +ARC requires that you use an MS-DOS partition table (as created by +<command>cfdisk</command>) for the boot disk. Therefore MS-DOS partition +tables are the <quote>native</quote> 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. + +</para><para> + +Conversely, SRM is <emphasis>incompatible</emphasis><footnote> + +<para> +Specifically, the bootsector format required by the Console Subsystem +Specification conflicts with the placement of the DOS partition table. +</para> + +</footnote> with MS-DOS partition tables. Since Tru64 Unix uses the BSD +disklabel format, this is the <quote>native</quote> partition format for +SRM installations. + +</para><para> + +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. + +</para><para> + +Because <command>MILO</command> 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. + +</para><para> + +The following table summarizes available and supported system +type/console combinations (see <xref linkend="alpha-cpus"/> for the +system type names). The word <quote>ARC</quote> below denotes any of the +ARC-compliant consoles. + +</para><para> + +<informaltable><tgroup cols="2"> +<thead> +<row> + <entry>System Type</entry> + <entry>Console Type Supported</entry> +</row> +</thead> + +<tbody> +<row> + <entry>alcor</entry> + <entry>ARC or SRM</entry> +</row><row> + <entry>avanti</entry> + <entry>ARC or SRM</entry> +</row><row> + <entry>book1</entry> + <entry>SRM only</entry> +</row><row> + <entry>cabriolet</entry> + <entry>ARC or SRM</entry> +</row><row> + <entry>dp264</entry> + <entry>SRM only</entry> +</row><row> + <entry>eb164</entry> + <entry>ARC or SRM</entry> +</row><row> + <entry>eb64p</entry> + <entry>ARC or SRM</entry> +</row><row> + <entry>eb66</entry> + <entry>ARC or SRM</entry> +</row><row> + <entry>eb66p</entry> + <entry>ARC or SRM</entry> +</row><row> + <entry>jensen</entry> + <entry>SRM only</entry> +</row><row> + <entry>lx164</entry> + <entry>ARC or SRM</entry> +</row><row> + <entry>miata</entry> + <entry>ARC or SRM</entry> +</row><row> + <entry>mikasa</entry> + <entry>ARC or SRM</entry> +</row><row> + <entry>mikasa-p</entry> + <entry>SRM only</entry> +</row><row> + <entry>nautilus</entry> + <entry>ARC (see motherboard manual) or SRM</entry> +</row><row> + <entry>noname</entry> + <entry>ARC or SRM</entry> +</row><row> + <entry>noritake</entry> + <entry>SRM only</entry> +</row><row> + <entry>noritake-p</entry> + <entry>SRM only</entry> +</row><row> + <entry>pc164</entry> + <entry>ARC or SRM</entry> +</row><row> + <entry>rawhide</entry> + <entry>SRM only</entry> +</row><row> + <entry>ruffian</entry> + <entry>ARC only</entry> +</row><row> + <entry>sable</entry> + <entry>SRM only</entry> +</row><row> + <entry>sable-g</entry> + <entry>SRM only</entry> +</row><row> + <entry>sx164</entry> + <entry>ARC or SRM</entry> +</row><row> + <entry>takara</entry> + <entry>ARC or SRM</entry> +</row><row> + <entry>xl</entry> + <entry>ARC only</entry> +</row><row> + <entry>xlt</entry> + <entry>ARC only</entry> +</row> + +</tbody> +</tgroup> +</informaltable> + +</para><para> + +Generally, none of these consoles can boot Linux directly, so the +assistance of an intermediary bootloader is required. For the SRM +console, <command>aboot</command>, a small, platform-independent +bootloader, is used. See the (unfortunately outdated) <ulink +url="&url-srm-howto;">SRM HOWTO</ulink> for more information on +<command>aboot</command>. + +</para><para condition="FIXME"> + +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. + +</para><para condition="FIXME"> + +Generally, none of these consoles can boot Linux directly, so the +assistance of an intermediary bootloader is required. There are two +mainstream Linux loaders: <command>MILO</command> and <command>aboot</command>. + +</para><para condition="FIXME"> + +<command>MILO</command> is itself a console, which replaces ARC or SRM in +memory. <command>MILO</command> can be booted from both ARC and SRM and is +the only way to bootstrap Linux from the ARC console. +<command>MILO</command> is platform-specific (a different <command>MILO</command> +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) <ulink url="&url-milo-howto;">MILO HOWTO</ulink>. + +</para><para condition="FIXME"> + +<command>aboot</command> is a small, platform-independent bootloader, which +runs from SRM only. See the (also unfortunately outdated) <ulink +url="&url-srm-howto;">SRM HOWTO</ulink> for more information on +<command>aboot</command>. + +</para><para condition="FIXME"> + +Thus, three scenarios are generally possible, depending on the +system's console firmware and whether or not <command>MILO</command> is +available: + +<informalexample><screen> +SRM -> aboot +SRM -> MILO +ARC -> MILO +</screen></informalexample> + +Because <command>MILO</command> 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 +<command>aboot</command> on new installations of GNU/Linux, unless you wish +to dual-boot with Windows NT. + +</para><para> + +The majority of AlphaServers and all current server and workstation +products contain both SRM and AlphaBIOS in their firmware. For +<quote>half-flash</quote> 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 <command>arc</command> +command). For the reasons mentioned above, we recommend switching to +SRM before installing &debian;. + +</para><para> + +As on other architectures, you should install the newest available +revision of the firmware<footnote> + +<para> +Except on Jensen, where Linux is not supported on firmware versions +newer than 1.7 — see <ulink url="&url-jensen-howto;"></ulink> +for more information. +</para> + +</footnote> before installing &debian;. +For Alpha, firmware updates can be obtained from +<ulink url="&url-alpha-firmware;">Alpha Firmware Updates</ulink>. + +</para> + </sect2> + + + <sect2 arch="alpha"><title>Booting with TFTP</title> +<para> + +In SRM, Ethernet interfaces are named with the <userinput>ewa</userinput> +prefix, and will be listed in the output of the <userinput>show dev</userinput> command, +like this (edited slightly): + +<informalexample><screen> +>>> 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 +</screen></informalexample> + +You first need to set the boot protocol: + +<informalexample><screen> +>>> set ewa0_protocol bootp +</screen></informalexample> + +Then check the medium type is correct: + +<informalexample><screen> +>>> set ewa0_mode <replaceable>mode</replaceable> +</screen></informalexample> + +You can get a listing of valid modes with <userinput>>>>set ewa0_mode</userinput>. + +</para><para> + +Then, to boot from the first Ethernet interface, you would type: + +<informalexample><screen> +>>> boot ewa0 -flags "" +</screen></informalexample> + +This will boot using the default kernel parameters as included in the +netboot image. + +</para><para> + +If you wish to use a serial console, you <emphasis>must</emphasis> +pass the <userinput>console=</userinput> parameter to the kernel. +This can be done using the <userinput>-flags</userinput> argument to +the SRM <userinput>boot</userinput> command. The serial ports are +named the same as their corresponding files in +<userinput>/dev</userinput>. 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 <userinput>ewa0</userinput> +and use a console on the first serial port, you would type: + +<informalexample><screen> +>>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 console=ttyS0" +</screen></informalexample> + +</para> + </sect2> + + <sect2 arch="alpha"><title>Booting from CD-ROM with the SRM Console</title> +<para> + +Type + +<informalexample><screen> +>>> boot xxxx -flags 0 +</screen></informalexample> + +where <replaceable>xxxx</replaceable> is your CD-ROM drive in SRM notation. + +</para> + </sect2> + + <sect2 arch="alpha" condition="FIXME"> + <title>Booting from CD-ROM with the ARC or AlphaBIOS Console</title> +<para> + +To boot a CD-ROM from the ARC console, find your sub-architecture code +name (see <xref linkend="alpha-cpus"/>), then enter +<filename>\milo\linload.exe</filename> as the boot loader and +<filename>\milo\<replaceable>subarch</replaceable></filename> (where +<replaceable>subarch</replaceable> is the proper subarchitecture name) +as the OS Path in the `OS Selection Setup' menu. Ruffians make an +exception: You need to use <filename>\milo\ldmilo.exe</filename> as +boot loader. + +</para> + </sect2> + + + <sect2 arch="alpha" condition="supports-floppy-boot"> + <title>Booting from Floppies with the SRM Console</title> +<para> + +At the SRM prompt (<prompt>>>></prompt>), issue the following +command: + +<informalexample><screen> +>>> boot dva0 -flags 0 +</screen></informalexample> + +possibly replacing <filename>dva0</filename> with the actual device +name. Usually, <filename>dva0</filename> is the floppy; type + +<informalexample><screen> +>>> show dev +</screen></informalexample> + +to see the list of devices (e.g., if you want to boot from a CD). +Note that if you are booting via MILO, <command>-flags</command> argument +is ignored, so you can just type <command>boot dva0</command>. +If everything works OK, you will eventually see the Linux kernel boot. + +</para><para> + +If you want to specify kernel parameters when booting via +<command>aboot</command>, use the following command: + +<informalexample><screen> +>>> boot dva0 -file linux.bin.gz -flags "root=/dev/fd0 load_ramdisk=1 arguments" +</screen></informalexample> + +(typed on one line), substituting, if necessary, the actual SRM boot +device name for <filename>dva0</filename>, the Linux boot device name for +<filename>fd0</filename>, and the desired kernel parameters for +<filename>arguments</filename>. + +</para><para> + +If you want to specify kernel parameters when booting via +<command>MILO</command>, you will have to interrupt bootstrap once you get +into MILO. See <xref linkend="booting-from-milo"/>. +</para> + </sect2> + + + <sect2 arch="alpha" condition="supports-floppy-boot"> + <title>Booting from Floppies with the ARC or AlphaBIOS Console</title> + +<para> + +In the OS Selection menu, set <command>linload.exe</command> as the boot +loader, and <command>milo</command> as the OS Path. Bootstrap using the +newly created entry. + +</para> + </sect2> + + <sect2 arch="alpha" condition="FIXME" id="booting-from-milo"><title>Booting with MILO</title> +<para> + +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. + +</para><para> + +If you want to specify all the bits explicitly (for example, to supply +additional parameters), you can use a command like this: + +<informalexample><screen> +MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 <!-- arguments --> +</screen></informalexample> + +If you are booting from something other than a floppy, substitute +<filename>fd0</filename> in the above example with the appropriate device name +in Linux notation. The <command>help</command> command would give you a brief +MILO command reference. + +</para> + </sect2> diff --git a/ca/boot-installer/arm.xml b/ca/boot-installer/arm.xml new file mode 100644 index 000000000..505a05323 --- /dev/null +++ b/ca/boot-installer/arm.xml @@ -0,0 +1,113 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 untranslated --> + + <sect2 arch="arm" id="boot-tftp"><title>Booting from TFTP</title> + +&boot-installer-intro-net.xml; + + <sect3 arch="arm"><title>Booting from TFTP on NetWinder</title> + +<para> + +NetWinders have two network interfaces: The 10Mbps NE2000-compatible +card is <filename>eth0</filename> and the 100Mbps Tulip card is +<filename>eth1</filename>. + +</para><note><para> + +You need NeTTrom 2.2.1 or later to boot the +installation system. NeTTrom 2.3.3 is recommended: get these files +from +<ulink url="ftp://ftp.netwinder.org/pub/netwinder/firmware/"></ulink>: +<itemizedlist> +<listitem><para> + +<filename>nettrom-2.3-3.armv4l.rpm</filename> + +</para></listitem> +<listitem><para> + +<filename>nettrom-2.3.3.bin</filename> + +</para></listitem> +<listitem><para> + +<filename>nettrom-2.3.3.bin.md5sum</filename> + +</para></listitem> +</itemizedlist> + +</para></note><para> + +After rebooting and interrupting the boot process during the countdown, you +must first configure the network either with a static address: + +<informalexample><screen> + NeTTrom command-> setenv eth0_ip 192.168.0.10/24 +</screen></informalexample> + +where 24 is the number of set bits in the netmask, or a dynamic address: + +<informalexample><screen> + NeTTrom command-> boot diskless +</screen></informalexample> + +You may also need to configure the <userinput>route1</userinput> +settings if the TFTP +server is not on the local subnet. The rest of the config is pretty +standard (the save-all step is optional): + +<informalexample><screen> + NeTTrom command-> setenv kerntftpserver 192.168.0.1 + NeTTrom command-> setenv kerntftpfile boot.img + NeTTrom command-> save-all + NeTTrom command-> setenv netconfig_eth0 flash + NeTTrom command-> setenv kernconfig tftp + NeTTrom command-> setenv rootdev /dev/ram + NeTTrom command-> setenv cmdappend root=/dev/ram +</screen></informalexample> + +Only the last four of these interfere with normal disk booting, so it is +safe to issue <command>save-all</command> right before them, which will +store the network settings in case you need to boot from the network +again. + +If you want to use the serial console to install your NetWinder, you also +need the following setting: + +<informalexample><screen> + NeTTrom command-> setenv cmdappend root=/dev/ram console=ttyS0,115200 +</screen></informalexample> + +Use the <command>printenv</command> command to review your +environment settings. Finally, if your <envar>cmdappend</envar> +NeTTrom variable has the <option>noinitrd</option> option, you must +remove it so the downloaded kernel can boot with its attached ramdisk. + +</para> + </sect3> + + <sect3 arch="arm"><title>Booting from TFTP on CATS</title> + +<para> + +On CATS machines, use <command>boot de0:</command> or similar at the +Cyclone prompt. + +</para> + </sect3> + </sect2> + + + + <sect2 arch="arm"><title>Booting from CD-ROM</title> + +&boot-installer-intro-cd.xml; + +<para> + +To boot a CD-ROM from the Cyclone console prompt, use the command +<command>boot cd0:cats.bin</command> + +</para> + </sect2> diff --git a/ca/boot-installer/boot-installer.xml b/ca/boot-installer/boot-installer.xml new file mode 100644 index 000000000..e1e5d9dae --- /dev/null +++ b/ca/boot-installer/boot-installer.xml @@ -0,0 +1,32 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 24701 --> + +<chapter id="boot-installer"><title>Arrencant el sistema d'instal·lació</title> + +<!-- Include only archs that are documented to avoid build-errors --> +<!-- The arch="..." condition can be deleted when al archs are present --> + <sect1 arch="alpha;arm;i386;ia64;m68k;mips;s390;powerpc;sparc"> + <title>Arrencant l'instal·lador en l'arquitectura &arch-title;</title> + +<!-- This info is so architecture dependent, that I have turned the --> +<!-- structure inside out for this chapter. Each arch has a document. --> +<!-- Note: archs hppa and mipsel are currently missing --> + +&boot-installer-alpha.xml; +&boot-installer-arm.xml; +<!-- &boot-installer-hppa.xml; --> +&boot-installer-i386.xml; +&boot-installer-ia64.xml; +&boot-installer-m68k.xml; +&boot-installer-mips.xml; +<!-- &boot-installer-mipsel.xml; --> +&boot-installer-s390.xml; +&boot-installer-powerpc.xml; +&boot-installer-sparc.xml; + + </sect1> + +&boot-installer-parameters.xml; +&boot-installer-trouble.xml; + +</chapter> diff --git a/ca/boot-installer/hppa.xml b/ca/boot-installer/hppa.xml new file mode 100644 index 000000000..0676332b2 --- /dev/null +++ b/ca/boot-installer/hppa.xml @@ -0,0 +1,12 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 24701 --> + + <sect2 arch="hppa"> + <title></title> +<para> + +<!-- Placeholder document; please write and include in + boot-installer.xml and build/templates/docstruct.ent --> + +</para> + </sect2> diff --git a/ca/boot-installer/i386.xml b/ca/boot-installer/i386.xml new file mode 100644 index 000000000..8d9aa8b3f --- /dev/null +++ b/ca/boot-installer/i386.xml @@ -0,0 +1,445 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 25149 --> + + <sect2 arch="i386"><title>Arrencant des d'un CD-ROM</title> + +&boot-installer-intro-cd.xml; + +<!-- We'll comment the following section until we know exact layout --> +<!-- +CD #1 of official Debian CD-ROM sets for &arch-title; will present a +<prompt>boot:</prompt> prompt on most hardware. Press +<keycap>F3</keycap> to see the list of kernel options available +from which to boot. Just type your chosen flavor name (idepci, +vanilla, compact, bf24) at the <prompt>boot:</prompt> prompt +followed by &enterkey;. + +</para><para> + +If your hardware doesn't support booting of multiple images, put one +of the other CDs in the drive. It appears that most SCSI CD-ROM drives +do not support <command>isolinux</command> multiple image booting, so users +with SCSI CD-ROMs should try either CD2 (vanilla) or CD3 (compact), +or CD5 (bf2.4). + +</para><para> + +CD's 2 through 5 will each boot a +different ``flavor'' depending on which CD-ROM is +inserted. See <xref linkend="kernel-choice"/> for a discussion of the +different flavors. Here's how the flavors are laid out on the +different CD-ROMs: + +<variablelist> +<varlistentry> +<term>CD 1</term><listitem><para> + +Allows a selection of kernel images to boot from (the idepci flavor is +the default if no selection is made). + +</para></listitem></varlistentry> +<varlistentry> +<term>CD 2</term><listitem><para> + +Boots the `vanilla' flavor. + +</para></listitem></varlistentry> +<varlistentry> +<term>CD 3</term><listitem><para> + +Boots the `compact' flavor. + +</para></listitem></varlistentry> +<varlistentry> +<term>CD 4</term><listitem><para> + +Boots the `idepci' flavor. + +</para></listitem></varlistentry> +<varlistentry> +<term>CD 5</term><listitem><para> + +Boots the `bf2.4' flavor. + +</para></listitem></varlistentry> + + </variablelist> + +</para><para> + +--> + + </sect2> + +<!-- FIXME the documented procedure does not exactly work, commented out + until fixes + + <sect2 arch="i386" id="install-from-dos"> + <title>Booting from a DOS partition</title> + +&boot-installer-intro-hd.xml; + +<para> + +Boot into DOS (not Windows) without any drivers being loaded. To do +this, you have to press <keycap>F8</keycap> at exactly the right +moment (and optionally select the `safe mode command prompt only' +option). Enter the subdirectory for the flavor you chose, e.g., + +<informalexample><screen> +cd c:\install +</screen></informalexample>. + +Next, execute <command>install.bat</command>. +The kernel will load and launch the installer system. + +</para><para> + +Please note, there is currently a loadlin problem (#142421) which +precludes <filename>install.bat</filename> from being used with the +bf2.4 flavor. The symptom of the problem is an +<computeroutput>invalid compressed format</computeroutput> error. + +</para> + </sect2> + +END FIXME --> + + <sect2 arch="i386" id="boot-initrd"> + <title>Arrencant des del Linux utilitzant el <command>LILO</command> o el + <command>GRUB</command></title> + +<para> + +Per arrencar l'instal·lador des d'un disc dur, primer heu de baixar +els fitxers necessaris tal i com es descriu a +<xref linkend="boot-drive-files"/>. + +</para> + +<para> + +Si voleu utilitzar el disc dur únicament per a l'arrencada i +voleu baixar-ho tot des de la xarxa, hauríeu de baixar el fitxer +<filename>netboot/debian-installer/i386/initrd.gz</filename> +i el nucli corresponent. + +Us permetrà tornar a particionar el disc dur del qual heu arrencat +l'instal·lador, tot i això, ho hauríeu de fer amb molt de compte. + +</para> + +<para> + +Si durant la instal·lació preteneu mantenir sense modificacions una +partició existent al disc dur, podeu baixar el fitxer +<filename>hd-media/initrd.gz</filename> i el nucli corresponent, i +també copiar una imatge iso del CD al dispositiu (assegureu-vos +que el nom del fitxer acaba amb «.iso»). En aquest cas l'instal·lador +pot arrencar del dispositiu i instal·lar des de la imatge del CD sense +necessitar la xarxa. + +</para> + +<para> + +Per utilitzar el <command>LILO</command> haureu de configurar +dos punts essencials del fitxer <filename>/etc/lilo.conf</filename>: + +<itemizedlist> +<listitem><para> + +carregar l'instal·lador <filename>initrd.gz</filename> a l'arrencada; + +</para></listitem> +<listitem><para> + +obligar al nucli <filename>vmlinuz</filename> a utilitzar un disc +de RAM com a partició arrel. + +</para></listitem> +</itemizedlist> + +A continuació trobareu un exemple del fitxer +<filename>/etc/lilo.conf</filename>: + +</para><para> + +<informalexample><screen> +image=/boot/newinstall/vmlinuz + label=newinstall + initrd=/boot/newinstall/initrd.gz + root=/dev/ram0 + append="devfs=mount,dall ramdisk_size=12000" +</screen></informalexample> + +Per a més informació vegeu les pàgines del manual +<citerefentry><refentrytitle>initrd</refentrytitle> +<manvolnum>4</manvolnum></citerefentry> i +<citerefentry><refentrytitle>lilo.conf</refentrytitle> +<manvolnum>5</manvolnum></citerefentry>. Executeu l'ordre +<userinput>lilo</userinput> i reinicieu el sistema. + +</para><para> + +El procediment pel <command>GRUB</command> és similar. Cerqueu el fitxer +<filename>menu.lst</filename> al directori <filename>/boot/grub/</filename> +(en algunes ocasions al directori <filename>/boot/boot/grub/</filename>) +i afegiu-hi les línies següents: + +<informalexample><screen> +title New Install +kernel (hd0,0)/boot/newinstall/vmlinuz root=/dev/ram0 ramdisk_size=12000 +initrd (hd0,0)/boot/newinstall/initrd.gz +</screen></informalexample> + +i reinicieu el sistema. Si l'arrencada falla, podeu provar afegint +<userinput>devfs=mount,dall</userinput> a la línia <quote>kernel</quote>. + +</para><para> +Recordeu que el valor de <userinput>ramdisk_size</userinput> s'hauria +d'ajustar a la mida de la imatge initrd. A partir d'aquí no hi hauria +d'haver cap diferència entre el <command>GRUB</command> i el +<command>LILO</command>. + +</para> + </sect2> + + <sect2 arch="i386" id="usb-boot"> + <title>Arrencant des d'un llapis USB</title> +<para> + +S'assumeix que heu seguit els passos descrits a +<xref linkend="boot-dev-select"/> i <xref linkend="boot-usb-files"/>. +Només heu de connectar el llapis USB a algun connector USB lliure i +reiniciar l'ordinador. El sistema s'hauria d'arrencar i us hauria +d'aparèixer l'indicador <prompt>boot:</prompt>. Podeu introduïr-hi +els paràmetres d'arrencada opcionals o únicament prémer &enterkey; + +</para><para> + +En el cas que el vostre ordinador no permeti l'arrencada des d'un +dispositiu de memòria USB, podeu utilitzar un disquet per fer +l'arrencada inicial i posteriorment commutar a l'USB. Arrenqueu el +vostre ordinador tal com està descrit a <xref linkend="floppy-boot"/>; +el nucli del disquet d'arrencada hauria de detectar automàticament el +llapis USB. Quan se us demani el disquet arrel, premeu &enterkey;. +Hauríeu de veure com s'inicialitza el &d-i;. + +</para> + </sect2> + + <sect2 arch="i386" id="floppy-boot"> + <title>Arrencant des dels disquets</title> +<para> + +Haureu d'haver descarregat les imatges del disquet i haver-ne +creat els disquets corresponents segons <xref linkend="create-floppy"/>. +<!-- missing-doc FIXME If you need to, you can also modify the boot floppy; see +<xref linkend="rescue-replace-kernel"/>. --> + +</para><para> + +Per arrencar des del disquet d'arrencada instal·lador, introduïu-lo +a la disquetera, atureu el sistema i torneu-lo a engegar. + +</para><para> + +Per instal·lar des d'una unitat LS-120 (versió ATAPI) utilitzant +un conjunt de disquets, heu d'especificar la ubicació virtual de la +disquetera. Ho podeu fer a través del paràmetre d'arrencada +<emphasis>root=</emphasis>, especificant que el controlador de la +disquetera-ide mapeja el dispositiu. Per exemple, si la unitat LS-120 +està connectada al primer dispositiu IDE (master) del segon cable, +hauríeu d'introduir <userinput>linux root=/dev/hdc</userinput> a +l'indicador d'arrencada. La instal·lació des del LS-120 només està +suportada a partir de la versió del nucli 2.4. + +</para><para> + +Recodeu que en alguns ordinadors la combinació +<keycombo><keycap>Control</keycap> +<keycap>Alt</keycap> <keycap>Delete</keycap></keycombo> +no reinicia correctament l'ordinador i es recomana +reiniciar-lo manualment. Si ho esteu instal·lant des d'un sistema operatiu +existent (ex. des d'un DOS) teniu l'opció. Si no és el cas reinicieu-lo +manualment durant l'arrencada. + +</para><para> + +S'hauria d'accedir al disquet i hauria d'aparèixer una pantalla +relacionada amb el disquet d'arrencada i que acaba amb +l'indicador <prompt>boot:</prompt>. + +</para><para> + +Al prémer &enterkey; hauríeu de veure el missatge +<computeroutput>Loading...</computeroutput>, seguit de +<computeroutput>Uncompressing Linux...</computeroutput>, i +a continuació una pàgina amb la informació del maquinari del sistema. +Per a més informació d'aquesta fase del procés d'arrencada vegeu +<xref linkend="kernel-msgs"/>. + +</para><para> + +Un cop arrencat des del disquet d'arrencada se us sol·licitarà +el disquet arrel. Inserteu el disquet arrel i permeu &enterkey;, +seguidament es carregaran els continguts a la memòria. +El programa instal·lador <command>debian-installer</command> +s'iniciarà automàticament. + +</para> + </sect2> + + <sect2 arch="i386" id="boot-tftp"><title>Arrencant via TFTP</title> + +&boot-installer-intro-net.xml; + +<para> + +Hi ha diversos mètodes per a arrencar via TFTP en i386. + +</para> + + <sect3><title>Tarja de xarxa o placa mare que suporta PXE</title> +<para> + +És possible que la vostra tarja de xarxa o la placa mare proporcionin +la possibilitat d'arrencada via PXE. Es tracta d'una reimplementació +d'<trademark class="trade">Intel</trademark> de l'arrencada via TFTP. +Si és el vostre cas podeu configurar la BIOS perquè arrenqui via la +xarxa. + +</para> + </sect3> + + <sect3><title>Tarja de xarxa amb una ROM d'arrencada via xarxa</title> +<para> + +És possible que la vostra tarja de xarxa proporcioni la possibilitat +d'arrencar via TFTP. + +</para><para condition="FIXME"> + +Informeu-nos (<email>&email-debian-boot-list;</email>) de com us ha anat. + +</para> + </sect3> + + <sect3><title>Etherboot</title> +<para> + +El <ulink url="http://www.etherboot.org">projecte etherboot</ulink> +proporciona disquets d'arrencada i fins hi tot roms d'arrencada +que permeten l'arrencada via TFTP. + +</para> + </sect3> + </sect2> + + <sect2 arch="i386"><title>Paràmetre d'arrencada i386</title> +<para> + +Quan arrenqui l'instal·lador us apareixerà l'indicador d'arrencada +<prompt>boot:</prompt>. En l'indicador <prompt>boot:</prompt> podeu +fer dues coses. Podeu prémer les tecles de <keycap>F1</keycap> +a <keycap>F10</keycap> per visualitzar pàgines d'informació útil, +o podeu prémer <keycap>Enter</keycap> per reiniciar el sistema. + +</para><para> + +Podeu accedir a informació interessant sobre els paràmetre d'arrencada +prement les tecles de <keycap>F3</keycap> a <keycap>F7</keycap>. +Si afegiu qualsevol paràmetre a la línia d'ordres d'arrencada, +assegureu-vos d'escriure el mètode d'arrencada (el predeterminat és +<userinput>linux</userinput>) i un espai abans del primer paràmetre +(ex. <userinput>linux floppy=thinkpad</userinput>). Prémer &enterkey;, +és el mateix que escriure <userinput>linux</userinput> sense cap +paràmetre especial. + +</para><para> + +Alguns sistemes tenen disqueteres amb els "DCL invertits". Si +us apareixen errors mentre esteu llegint de la disquetera tot +i saber que funciona correctament, proveu d'utilitzar el paràmetre +<userinput>floppy=thinkpad</userinput>. + +</para><para> + +En alguns sistemes com els IBM PS/1 o el ValuePoint (que disposa +dels controladors de disc del ST-506) la unitat IDE no es reconeixerà +correctament. En aquest cas proveu-ho sense paràmetres i espereu si +es reconeix correctament. Si no és el cas, cerqueu els paràmetres +del dispositiu (cilindres, capçals i sectors) i utilitzeu el paràmetre +<userinput>hd=<replaceable>cilindres</replaceable>,<replaceable>capçals</replaceable>,<replaceable>sectors</replaceable></userinput>. + +</para><para> + +Si disposeu d'un ordinador molt vell i el nucli es penja +després de mostrar el missatge +<computeroutput>Checking 'hlt' instruction...</computeroutput>, +hauríeu de provar el paràmetre d'arrencada que inhabilita la prova +<userinput>no-hlt</userinput>. + +</para><para> + +Si durant l'arrencada del nucli apareixen caràcters estranys a la pantalla, +és possible que el sistema disposi d'una tarja de vídeo problemàtica +que no commuta correctament al mode framebuffer. En aquest cas podeu +utilitzar el paràmetre d'arrencada +<userinput>debian-installer/framebuffer=false</userinput> o +<userinput>video=vga16:off</userinput> per inhabilitar el frambuffer. +Durant la instal·lació únicament es disposarà de l'idioma anglès +arran de les limitacions de la consola. Per a més informació +vegeu +<xref linkend="boot-parms"/>. + +</para> + </sect2> + + <sect2 arch="i386"> + <title>El sistema queda congelat durant la fase de configuració de la PCMCIA</title> + +<para> + +Alguns models d'ordinadors portàtils produïts per Dell són coneguts +per penjar-se quan la detecció de dispositius PCMCIA intenta accedir a +algunes adreces de maquinari. D'altres portàtils poden descriure +problemàtiques similars. Si patiu algun problema similar i durant +la instal·lació no preciseu del suport PCMCIA, el podeu inhabilitar +utilitzant el paràmetre d'arrencada +<userinput>hw-detect/start_pcmcia=false</userinput>. +Podeu configurar el suport de PCMCIA després de la instal·lació +i excloure'n el rang de recursos problemàtic. + +</para><para> + +D'altra banda, podeu arrencar l'instal·lador en mode expert. Se us +demanarà que introduïu les opcions del rang de recursos que precisa +el vostre maquinari. Per exemple, si disposeu d'un dels ordinadors +portàtils Dell anomenats anteriorment, hauríeu d'introduir-hi +<userinput>exclude port 0x800-0x8ff</userinput>. Disposeu d'una llista +de les opcions del rangs de recursos més habituals a +<ulink url="http://pcmcia-cs.sourceforge.net/ftp/doc/PCMCIA-HOWTO-1.html#ss1.12">System +resource settings section of the PCMCIA HOWTO</ulink>. +Recordeu que heu d'evitar la utilització de les comes a l'hora +d'introduir els valors a l'instal·lador. + +</para> + </sect2> + + <sect2 arch="i386"> + <title>El sistema queda congelat durant la càrrega dels mòduls USB</title> +<para> + +El nucli acostuma a intentar instal·lar els mòduls USB i els controladors +del teclat USB per suportar alguns teclats USB no estàndards. Tot i això, +hi ha alguns sistemes USB inconsistents en els quals el controlador +es penja durant la càrrega. Una possible solució és inhabilitar el controlador +USB en la configuració de la BIOS de la placa mare. Una altra opció és +passsar el paràmetre +<userinput>debian-installer/probe/usb=false</userinput> +a l'indicador d'arrencada, que evitarà que es carreguin els mòduls. + +</para> + </sect2> diff --git a/ca/boot-installer/ia64.xml b/ca/boot-installer/ia64.xml new file mode 100644 index 000000000..9afc8b61e --- /dev/null +++ b/ca/boot-installer/ia64.xml @@ -0,0 +1,464 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 untranslated --> + + <sect2 arch="ia64"><title>Booting from a CD-ROM</title> + +&boot-installer-intro-cd.xml; + + <note> + <title>CD Contents</title> + +<para> + +There are three basic variations of Debian Install CDs. +The <emphasis>Business Card</emphasis> CD has a minimal installation +that will fit on the small form factor CD media. +It requires a network connection in order to install the rest of the +base installation and make a usable system. +The <emphasis>Network Install</emphasis> CD has all of the packages +for a base install but requires a network connection to a Debian +mirror site in order to install the +extra packages one would want for a complete system . +The set of Debian CDs can install a complete system from the wide +range of packages without needing access to the network. +</para> + </note> + +<para> + +The IA-64 architecture uses the next generation Extensible Firmware Interface +(EFI) from Intel. +Unlike the traditional x86 BIOS which knows little about the boot +device other than the partition table and Master Boot Record (MBR), +EFI can read and write files from FAT16 or FAT32 formatted disk +partitions. +This simplifies the often arcane process of starting a system. +The system boot loader and the EFI firmware that supports it have +a full filesystem to store the files necessary for booting the +machine. +This means that the system disk on an IA-64 system has an additional +disk partition dedicated to EFI instead of the simple MBR or boot +block on more conventional systems. + +</para><para> + +The Debian Installer CD contains a small EFI partition where the +<command>ELILO</command> bootloader, its configuration file, the installer's +kernel, and initial filesystem (initrd) are located. +The running system also contains an EFI partition where the necessary +files for booting the system reside. +These files are readable from the EFI Shell as described below. + +</para><para> + +Most of the details of how <command>ELILO</command> actually loads and +starts a system are transparent to the system installer. +However, the installer must set up an EFI partition prior to installing +the base system. Otherwise, the installation of <command>ELILO</command> +will fail, rendering the system un-bootable. +The EFI partition is allocated and formatted in the partitioning step +of the installation prior to loading any packages on the system disk. +The partitioning task also verifies that a suitable EFI partition is +present before allowing the installation to proceed. + +</para><para> + +The EFI Boot Manager is presented as the last step of the firmware +initialization. +It displays a menu list from which the user can select +an option. +Depending on the model of system and what other software has been +loaded on the system, this menu may be different from one system +to another. +There should be at least two menu items displayed, +<command>Boot Option Maintenance Menu</command> and +<command>EFI Shell (Built-in)</command>. +Using the first option is preferred, however, if that +option is not available or the CD for some reason does not +boot with it, use the second option. + +</para> + + <warning> + <title>IMPORTANT</title> +<para> +The EFI Boot Manager will select a default boot action, typically +the first menu choice, within a pre-set number of seconds. +This is indicated by a countdown at the bottom of the screen. +Once the timer expires and the systems starts the default action, +you may have to reboot the machine in order to continue the installation. +If the default action is the EFI Shell, you can return to the Boot Manager +by running <command>exit</command> at the shell prompt. +</para> + </warning> + + <sect3 arch="ia64" id="bootable-cd"> + <title>Option 1: Booting from the Boot Option Maintenance Menu</title> +<para> + +</para> + +<itemizedlist> + +<listitem><para> +Insert the CD in the DVD/CD drive and reboot the machine. +The firmware will display the EFI Boot Manager page and menu after +it completes its system initialization. +</para></listitem> + +<listitem><para> +Select <command>Boot Maintenance Menu</command> from the menu +with the arrow keys and press <command>ENTER</command>. +This will display a new menu. +</para></listitem> + +<listitem><para> +Select <command>Boot From a File</command> from the menu +with the arrow keys and press <command>ENTER</command>. +This will display a list of devices probed by the firmware. +You should see two menu lines containing either the label +<command>Debian Inst [Acpi ...</command> or +<command>Removable Media Boot</command>. +If you examine the rest of the menu line, you will notice that +the device and controller information should be the same. +</para></listitem> + +<listitem><para> +You can choose either of the entries that refer to the CD/DVD +drive. +Select your choice with the arrow keys and press <command>ENTER</command>. +If you choose <command>Removable Media Boot</command> the machine +will immediately start the boot load sequence. +If you choose <command>Debian Inst [Acpi ...</command> instead, it +will display a directory listing of the bootable portion of the +CD, requiring you to proceed to the next (additional) step. +</para></listitem> + +<listitem><para> +You will only need this step if you chose +<command>Debian Inst [Acpi ...</command>. +The directory listing will also show +<command>[Treat like Removable Media Boot]</command> on the next to +the last line. +Select this line with the arrow keys and press <command>ENTER</command>. +This will start the boot load sequence. +</para></listitem> + +</itemizedlist> + +<para> + +These steps start the Debian boot loader which will display a +menu page for you to select a boot kernel and options. +Proceed to selecting the boot kernel and options. + +</para> + </sect3> + + <sect3 arch="ia64" id="boot-with-efi"> + <title>Option 2: Booting from the EFI Shell</title> +<para> + +If, for some reason, option 1 is not successful, reboot the machine +and when the EFI Boot Manager screen appears there should be +one option called <command>EFI Shell [Built-in]</command>. +Boot the Debian Installer CD with the following steps: + +</para> + +<itemizedlist> + +<listitem><para> +Insert the CD in the DVD/CD drive and reboot the machine. +The firmware will display the EFI Boot Manager page and menu after +it completes system initialization. +</para></listitem> + +<listitem><para> +Select <command>EFI Shell</command> from the menu with the arrow keys +and press <command>ENTER</command>. +The EFI Shell will scan all of the bootable devices and display +them to the console before displaying its command prompt. +The recognized bootable partitions on devices will show a device name of +<filename>fs<replaceable>n</replaceable>:</filename>. +All other recognized partitions will be named +<filename>blk<replaceable>n</replaceable>:</filename>. +If you inserted the CD just before entering the shell, this may +take a few extra seconds as it initializes the CD drive. +</para> +</listitem> + +<listitem><para> +Examine the output from the shell looking for the CDROM drive. +It is most likely the <filename>fs0:</filename> device although +other devices with bootable partitions will also show up as +<filename>fs<replaceable>n</replaceable></filename>. +</para></listitem> + +<listitem><para> +Enter <command>fs<replaceable>n</replaceable>:</command> and press +<command>ENTER</command> to select that +device where <replaceable>n</replaceable> is the partition number for the +CDROM. The shell will now display the partition number as its prompt. +</para></listitem> + +<listitem><para> +Enter <command>elilo</command> and press <command>ENTER</command>. +This will start the boot load sequence. +</para></listitem> + +</itemizedlist> + +<para> + +As with option 1, these steps start the Debian boot loader which will +display a menu page for you to select a boot kernel and options. +You can also enter the shorter +<command>fs<replaceable>n</replaceable>:elilo</command> command at +the shell prompt. +Proceed to selecting the boot kernel and options. + +</para> + + </sect3> + + <sect3 arch="ia64" id="serial-console"> + <title>Installing using a Serial Console</title> + +<para> + +You may choose to perform an install using a monitor and keyboard +or using a serial connection. To use a monitor/keyboard setup, +select an option containing the string [VGA console]. To install +over a serial connection, choose an option containing the string +[<replaceable>BAUD</replaceable> baud serial console], where +<replaceable>BAUD</replaceable> is the speed of your serial console. +Menu items for the most typical baud rate settings on the ttyS0 +device are preconfigured. + +</para><para> + +In most circumstances, you will want the installer to use the same +baud rate as your connection to the EFI console. If you aren't +sure what this setting is, you can obtain it using the command +<command>baud</command> at the EFI shell. + +</para><para> + +If there is not an option available that is configured for the serial +device or baud rate you would like to use, you may override the console setting +for one of the existing menu options. For example, to use a +57600 baud console over the ttyS1 device, enter +<command>console=ttyS1,57600n8</command> into +the <classname>Boot:</classname> text window. + +</para> + +<note><para> +Most IA-64 boxes ship with a default console setting of 9600 baud. +This setting is rather slow, and the normal installation process +will take a significant time to draw each screen. You should consider +either increasing the baud rate used for performing the installation, +or performing a Text Mode installation. See the <classname>Params</classname> +help menu for instructions on starting the installer in Text Mode. +</para></note> + +<warning><para> +If you select the wrong console type, you +will be able to select the kernel and enter parameters but both +the display and your input will go dead as soon as the kernel starts, +requiring you to reboot before you can begin the installation. +</para></warning> + </sect3> + + <sect3 arch="ia64" id="kernel-option-menu"> + <title>Selecting the Boot Kernel and Options</title> + +<para> + +The boot loader will display a form with a menu list and a text +window with a <classname>Boot:</classname> prompt. +The arrow keys select an item from the menu and any text typed +at the keyboard will appear in the text window. +There are also help screens which can be displayed by pressing +the appropriate function key. +The <classname>General</classname> help screen explains the menu +choices and the <classname>Params</classname> screen explains +the common command line options. + +</para><para> + +Consult the <classname>General</classname> help screen for the +description of the kernels and install modes most appropriate +for your installation. +You should also consult <xref linkend="boot-parms"/> below for any additional +parameters that you may want to set in the <classname>Boot:</classname> +text window. +The kernel version you choose selects the kernel version that will be +used for both the installation process and the installed system. +If you encounter kernel problems with the installation, you may also +have those same problems with the system you install. +The following two steps will select and start the install: + +</para> + +<itemizedlist> + +<listitem><para> +Select the kernel version and installation mode most +appropriate to your needs with the arrow keys. +</para></listitem> + +<listitem><para> +Enter any boot parameters by typing at the keyboard. +The text will be displayed directly in the text window. +This is where kernel parameters (such as serial console +settings) are specified. +</para></listitem> + +<listitem><para> +Press <command>ENTER</command>. This will load and start the +kernel. +The kernel will display its usual initialization messages followed +by the first screen of the Debian Installer. +</para></listitem> + +</itemizedlist> + +<para> + +Proceed to the next chapter to continue the installation where you will +set up the language locale, network, and disk partitions. + +</para> + </sect3> + </sect2> + + <sect2 arch="ia64" id="boot-tftp"><title>Booting with TFTP</title> + +<para> +Booting an IA64 system from the network is similar to a CD boot. +The only difference is how the installation kernel is loaded. +The EFI Boot Manager can load and start programs from a server on +the network. +Once the installation kernel is loaded and starts, the system install +will proceed thru the same steps as the CD install with the exception +that the packages of the base install will be loaded from the network +rather than the CD drive. + +</para> + +&boot-installer-intro-net.xml; + +<para> + +Network booting an ia64 system requires two architecture-specific actions. +On the boot server, DHCP and TFTP must be configured to deliver +<command>elilo</command>. +On the client a new boot option must be defined in the EFI boot manager +to enable loading over a network. + +</para> + + <sect3 arch="ia64" id="boot-tftp-server"> + <title>Configuring the Server</title> +<para> + +A suitable TFTP entry for network booting an ia64 system looks something +like this: + +<informalexample><screen> +host mcmuffin { + hardware ethernet 00:30:6e:1e:0e:83; + fixed-address 10.0.0.21; + filename "debian-installer/ia64/elilo.efi"; +} +</screen></informalexample> + +Note that the goal is to get <command>elilo.efi</command> running on +the client. + +</para><para> + +Extract the <filename>netboot.tar.gz</filename> file into the directory used +as the root for your tftp server. Typical tftp root directories include +<filename>/var/lib/tftp</filename> and <filename>/tftpboot</filename>. +This will create a <filename>debian-installer</filename> directory +tree containing the boot files for an IA-64 system. + +</para><para> + +<informalexample><screen> +# cd /var/lib/tftp +# tar xvfz /home/user/netboot.tar.gz +./ +./debian-installer/ +./debian-installer/ia64/ +[...] +</screen></informalexample> + +The <filename>netboot.tar.gz</filename> contains an +<filename>elilo.conf</filename> file that should work for most configurations. +However, should you need to make changes to this file, you can find it in the +<filename>debian-installer/ia64/</filename> directory. + +It is possible to have different config files for different clients by naming +them using the client's IP address in hex with the suffix +<filename>.conf</filename> instead of <filename>elilo.conf</filename>. +See documentation provided in the <classname>elilo</classname> package +for details. + +</para> + </sect3> + + <sect3 arch="ia64" id="boot-tftp-client"> + <title>Configuring the Client</title> +<para> + +To configure the client to support TFTP booting, start by booting to +EFI and entering the <guimenu>Boot Option Maintenance Menu</guimenu>. + +<itemizedlist> +<listitem><para> + +Add a boot option. + +</para></listitem> +<listitem><para> + +You should see one or more lines with the text +<guimenuitem>Load File [Acpi()/.../Mac()]</guimenuitem>. If more +than one of these entries exist, choose the one containing the +MAC address of the interface from which you'll be booting. +Use the arrow keys to highlight your choice, then press enter. + +</para></listitem> +<listitem><para> + +Name the entry <userinput>Netboot</userinput> or something similar, +save, and exit back to the boot options menu. + +</para></listitem> +</itemizedlist> + +You should see the new boot option you just created, and selecting it +should initiate a DHCP query, leading to a TFTP load of +<filename>elilo.efi</filename> from the server. + +</para><para> + +The boot loader will display its prompt after it has downloaded and +processed its configuration file. +At this point, the installation proceeds with the same steps as a +CD install. Select a boot option as in above and when the kernel +has completed installing itself from the network, it will start the +Debian Installer. + +</para><para> + +Proceed to the next chapter to continue the installation where +you will set up the language locale, network, and the disk partitions. + +</para> + </sect3> + </sect2> diff --git a/ca/boot-installer/intro-cd.xml b/ca/boot-installer/intro-cd.xml new file mode 100644 index 000000000..fa8770197 --- /dev/null +++ b/ca/boot-installer/intro-cd.xml @@ -0,0 +1,40 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 --> + +<para> + +La manera més fàcil per a la majoria de la gent serà utilitzar +un conjunt de CD de Debian. +Si disposeu d'un conjunt de CD i el vostre ordinador permet arrencar +directament des del CD, fantàstic! Només +<phrase arch="i386"> +heu de configurar el sistema perquè arrenqui des d'un CD tal i com es +descriu a <xref linkend="boot-dev-select"/>, +</phrase> +inseriu el CD, reinicieu l'ordinador i passeu al següent capítol. + +</para><para> + +Recordeu que alguns dispositius de CD poden necessitar controladors +especials i pot ser que aquests no siguin accessibles en els +primers passos de la instal·lació. Si el mètode estàndard +d'arrencada des d'un CD no us funciona al vostre ordinador, torneu +a repassar el capítol i pareu atenció a la utilització de nuclis +i mètodes d'instal·lació alternatius que probablement us funcionin. + +</para><para> + +Tot i que no pugueu arrencar des d'un CD, probablement podeu utilitzar-lo +per instal·lar els components del sistema debian i qualsevol paquet. +Simplement heu d'arrencar utilitzant un altre mitjà com podria +ser un disc. A l'hora d'instal·lar el sistema operatiu, el sistema +base i qualsevol paquet addicional, enllaceu el sistema +d'instal·lació amb el dispositiu CD-ROM. + +</para><para> + +Si teniu problemes en l'arrencada, vegeu +<xref linkend="boot-troubleshooting"/>. + +</para> + diff --git a/ca/boot-installer/intro-hd.xml b/ca/boot-installer/intro-hd.xml new file mode 100644 index 000000000..f494737e2 --- /dev/null +++ b/ca/boot-installer/intro-hd.xml @@ -0,0 +1,16 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 --> + +<para> + +L'arrencada des d'un sistema operatiu existent sovint és una opció +convenient. Per a alguns sistemes és l'únic mètode d'instal·lació +suportat. + +</para><para> + +Per arrencar l'instal·lador des d'un disc dur, prèviament haureu +d'haver baixat els fitxers necessaris +<xref linkend="boot-drive-files"/>. + +</para> diff --git a/ca/boot-installer/intro-net.xml b/ca/boot-installer/intro-net.xml new file mode 100644 index 000000000..cc1cd2a67 --- /dev/null +++ b/ca/boot-installer/intro-net.xml @@ -0,0 +1,19 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 11648 --> + +<para> + +Per arrencar des de la xarxa necessitareu una connexió +i un servidor d'arrencada de xarxa TFTP (DHCP, RARP o BOOTP). + +</para><para arch="hppa"> + +Els sistemes antics com el 715 poden necessitar utilitzar un servidor +d'RBOOT en comptes d'un BOOTP. + +</para><para> + +El mètode d'instal·lació per suportar l'arrencada de la xarxa és descriu a +<xref linkend="install-tftp"/>. + +</para> diff --git a/ca/boot-installer/m68k.xml b/ca/boot-installer/m68k.xml new file mode 100644 index 000000000..1dc18c6ec --- /dev/null +++ b/ca/boot-installer/m68k.xml @@ -0,0 +1,371 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 30283 untranslated --> + + <sect2 arch="m68k"><title>Choosing an Installation Method</title> + +<para> + +Some &arch-title; subarchs have the option of booting using either a +2.4.x or 2.2.x linux kernel. When such a choice exists, try the 2.4.x +linux kernel. The installer should also require less memory when using +a 2.4.x linux kernel as 2.2.x support requires a fixed-sized ramdisk +and 2.4.x uses tmpfs. + +</para><para condition="etch"> + +If you are using a 2.2.x linux kernel, then you need to use the &ramdisksize; +kernel parameter. + +</para><para> + +</para><para condition="sarge"> + +Also, if you are using a 2.2.x linux kernel, then you must make sure you +are using a ramdisk built to accommodate it, see the +<ulink url="&disturl;/main/installer-&architecture;/current/images/MANIFEST">MANIFEST</ulink>. +In general, this means you need to use the initrd22.gz ramdisk from the respective +directory. + +</para><para> + +Make sure <userinput>root=/dev/ram</userinput> is one of your kernel +parameters. + +</para><para> + +If you're having trouble, check +<ulink url="&url-m68k-cts-faq;">cts's &arch-title; debian-installer FAQ</ulink>. + +</para> + +<itemizedlist> + <listitem><para><xref linkend="m68k-boot-amiga"/></para></listitem> + <listitem><para><xref linkend="m68k-boot-atari"/></para></listitem> + <listitem><para><xref linkend="m68k-boot-bvme6000"/></para></listitem> + <listitem><para><xref linkend="m68k-boot-mac"/></para></listitem> + <listitem><para><xref linkend="m68k-boot-mvme"/></para></listitem> + <listitem><para><xref linkend="m68k-boot-q40"/></para></listitem> +</itemizedlist> + + + <sect3 id="m68k-boot-amiga"><title>Amiga</title> +<para> + +The only method of installation available to amiga is the hard drive +(see <xref linkend="m68k-boot-hd"/>). +<emphasis>In other words the cdrom is not bootable.</emphasis> + +</para><para> + +Amiga does not currently work with bogl, so if +you are seeing bogl errors, you need to include the kernel parameter +<userinput>debian-installer/framebuffer=false</userinput>. + +</para> + </sect3> + + <sect3 id="m68k-boot-atari"><title>Atari</title> +<para> + +The installer for atari may be started from either the hard +drive (see <xref linkend="m68k-boot-hd"/>) or from floppies +(see <xref linkend="boot-from-floppies"/>). +<emphasis>In other words the cdrom is not bootable.</emphasis> + +</para><para> + +Atari does not currently work with bogl, so if +you are seeing bogl errors, you need to include the kernel parameter +<userinput>debian-installer/framebuffer=false</userinput>. + +</para> + </sect3> + + <sect3 id="m68k-boot-bvme6000"><title>BVME6000</title> +<para> + +The installer for BVME6000 may be started from a cdrom +(see <xref linkend="m68k-boot-cdrom"/>), floppies +(see <xref linkend="boot-from-floppies"/>), or the net +(see <xref linkend="boot-tftp"/>). + +</para> + </sect3> + + <sect3 id="m68k-boot-mac"><title>Macintosh</title> +<para> + +The only method of installation available to mac is from +the hard drive (see <xref linkend="m68k-boot-hd"/>). +<emphasis>In other words the cdrom is not bootable.</emphasis> +Macs do not have a working 2.4.x kernel. + +</para><para> + +If your hardware uses a 53c9x-based scsi bus, then you may need to +include the kernel parameter <userinput>mac53c9x=1,0</userinput>. +Hardware with two such scsi buses, such as the Quadra 950, will need +<userinput>mac53c9x=2,0</userinput> instead. Alternatively, the +parameter can be specified as <userinput>mac53c9x=-1,0</userinput> +which will leave autodetection on, but which will disable SCSI +disconnects. Note that specifying this parameter is only necessary +if you have more than one hard disk; otherwise, the system will run +faster if you do not specify it. + +</para> + </sect3> + + <sect3 id="m68k-boot-mvme"><title>MVME147 and MVME16x</title> +<para> + +The installer for MVME147 and MVME16x may be started from +either floppies (see <xref linkend="boot-from-floppies"/>) +or the net (see <xref linkend="boot-tftp"/>). +<emphasis>In other words the cdrom is not bootable.</emphasis> + +</para> + </sect3> + + <sect3 id="m68k-boot-q40"><title>Q40/Q60</title> +<para> + +The only method of installation available to Q40/Q60 is +from the hard drive (see <xref linkend="m68k-boot-hd"/>). +<emphasis>In other words the cdrom is not bootable.</emphasis> + +</para> + </sect3> + + </sect2> + + <sect2 arch="m68k" id="m68k-boot-hd"><title>Booting from a Hard Disk</title> + +&boot-installer-intro-hd.xml; + +<para> + +At least six different ramdisks may be used to boot from the hard +drive, three different types each with and without support for a +2.2.x linux kernel (see +<ulink url="&disturl;/main/installer-&architecture;/current/images/MANIFEST">MANIFEST</ulink> +for details). + +</para><para> + +The three different types of ramdisks are <filename>cdrom</filename>, +<filename>hd-media</filename>, and <filename>nativehd</filename>. These +ramdisks differ only in their source for installation packages. +The <filename>cdrom</filename> ramdisk uses a cdrom to get +debian-installer packages. The <filename>hd-media</filename> ramdisk +uses an iso image file of a cdrom currently residing on a hard disk. +Finally, the <filename>nativehd</filename> ramdisk uses the net to +install packages. + +</para> + +<itemizedlist> + <listitem><para><xref linkend="m68k-boothd-amiga"/></para></listitem> + <listitem><para><xref linkend="m68k-boothd-atari"/></para></listitem> + <listitem><para><xref linkend="m68k-boothd-mac"/></para></listitem> + <listitem><para><xref linkend="m68k-boothd-q40"/></para></listitem> +</itemizedlist> + + + <sect3 id="m68k-boothd-amiga"><title>Booting from AmigaOS</title> +<para> + +In the <command>Workbench</command>, start the Linux installation +process by double-clicking on the <guiicon>StartInstall</guiicon> icon +in the <filename>debian</filename> directory. + +</para><para> + +You may have to press the &enterkey; key twice after the Amiga +installer program has output some debugging information into a window. +After this, the screen will go grey, there will be a few seconds' +delay. Next, a black screen with white text should come up, displaying +all kinds of kernel debugging information. These messages may scroll +by too fast for you to read, but that's OK. After a couple of +seconds, the installation program should start automatically, so you +can continue down at <xref linkend="d-i-intro"/>. + +</para> + </sect3> + + + <sect3 id="m68k-boothd-atari"><title>Booting from Atari TOS</title> +<para> + +At the GEM desktop, start the Linux installation process by +double-clicking on the <guiicon>bootstra.prg</guiicon> icon in the +<filename>debian</filename> directory and clicking +<guibutton>Ok</guibutton> at the program options dialog box. + +</para><para> + +You may have to press the &enterkey; key after the Atari +bootstrap program has output some debugging information into a +window. After this, the screen will go grey, there will be a few +seconds' delay. Next, a black screen with white text should come up, +displaying all kinds of kernel debugging information. These messages +may scroll by too fast for you to read, but that's OK. After a couple +of seconds, the installation program should start automatically, so +you can continue below at <xref linkend="d-i-intro"/>. + +</para> + </sect3> + + + <sect3 id="m68k-boothd-mac"><title>Booting from MacOS</title> +<para> + +You must retain the original Mac system and +boot from it. It is <emphasis>essential</emphasis> that, when booting +MacOS in preparation for booting the Penguin linux loader, you +hold the <keycap>shift</keycap> key down to prevent extensions from +loading. If you don't use MacOS except for loading linux, you can +accomplish the same thing by removing all extensions and control +panels from the Mac's System Folder. Otherwise extensions may be left +running and cause random problems with the running linux kernel. + +</para><para> + +Macs require the <command>Penguin</command> +bootloader. If you do not have the tools to handle +a <command>Stuffit</command> archive, &penguin19.hfs; is an +hfs disk image with <command>Penguin</command> unpacked. +<xref linkend="create-floppy"/> describes how to copy this +image to a floppy. + +</para><para> + +At the MacOS desktop, start the Linux installation process by +double-clicking on the <guiicon>Penguin Prefs</guiicon> icon in +the <filename>Penguin</filename> directory. The +<command>Penguin</command> booter will start up. Go to the +<guimenuitem>Settings</guimenuitem> item in the +<guimenu>File</guimenu> menu, click the +<guilabel>Kernel</guilabel> tab. Select the kernel +(<filename>vmlinuz</filename>) and ramdisk +(<filename>initrd.gz</filename>) images in the +<filename>install</filename> directory by clicking on the corresponding +buttons in the upper right corner, and navigating the file select +dialogs to locate the files. + +</para><para> + +To set the boot parameters in Penguin, choose <guimenu>File</guimenu> -> +<guimenuitem>Settings...</guimenuitem>, then switch to the +<guilabel>Options</guilabel> tab. Boot parameters may be typed in to +the text entry area. If you will always want to use these settings, +select <guimenu>File</guimenu> -> <guimenuitem>Save Settings as +Default</guimenuitem>. + +</para><para> + +Close the <guilabel>Settings</guilabel> +dialog, save the settings and start the bootstrap using the +<guimenuitem>Boot Now</guimenuitem> item in the +<guimenu>File</guimenu> menu. + +</para><para> + +The <command>Penguin</command> booter will output some debugging +information into a window. After this, the screen will go grey, there +will be a few seconds' delay. Next, a black screen with white text +should come up, displaying all kinds of kernel debugging +information. These messages may scroll by too fast for you to read, +but that's OK. After a couple of seconds, the installation program +should start automatically, so you can continue below at +<xref linkend="d-i-intro"/>. + +</para> + + </sect3> + + <sect3 id="m68k-boothd-q40"><title>Booting from Q40/Q60</title> + +<para> + +FIXME + +</para><para> + +The installation program should start automatically, so you can +continue below at <xref linkend="d-i-intro"/>. + +</para> + + </sect3> + </sect2> + + + <sect2 arch="m68k" id="m68k-boot-cdrom"><title>Booting from a CD-ROM</title> +<para> + +Currently, the only &arch-title; subarchitecture that +supports CD-ROM booting is the BVME6000. + +</para> + +&boot-installer-intro-cd.xml; + + </sect2> + + + <sect2 arch="m68k" id="boot-tftp"><title>Booting with TFTP</title> + +&boot-installer-intro-net.xml; + +<para> + +After booting the VMEbus systems you will be presented with the LILO +<prompt>Boot:</prompt> prompt. At that prompt enter one of the +following to boot Linux and begin installation proper of the Debian +software using vt102 terminal emulation: + +<!-- Because the &enterkey; definition uses <keycap>, --> +<!-- we use <screen> instead of <userinput> in this list --> + +<itemizedlist> +<listitem><para> + +type <screen>i6000 &enterkey;</screen> to install a BVME4000/6000 + +</para></listitem> +<listitem><para> + +type <screen>i162 &enterkey;</screen> to install an MVME162 + +</para></listitem> +<listitem><para> + +type <screen>i167 &enterkey;</screen> to install an MVME166/167 + +</para></listitem> + </itemizedlist> + +</para><para> + +You may additionally append the string +<screen>TERM=vt100</screen> to use vt100 terminal emulation, +e.g., <screen>i6000 TERM=vt100 &enterkey;</screen>. + +</para> + </sect2> + + + <sect2 arch="m68k" id="boot-from-floppies"> + <title>Booting from Floppies</title> +<para> + +For most &arch-title; architectures, booting from a local filesystem is the +recommended method. + +</para><para> + +Booting from the boot floppy is supported only for Atari and VME +(with a SCSI floppy drive on VME) at this time. + +</para> + </sect2> diff --git a/ca/boot-installer/mips.xml b/ca/boot-installer/mips.xml new file mode 100644 index 000000000..f237aa957 --- /dev/null +++ b/ca/boot-installer/mips.xml @@ -0,0 +1,100 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 24663 untranslated --> + + + <sect2 arch="mips" id="boot-tftp"><title>Booting with TFTP</title> + + <sect3> + <title>SGI Indys TFTP Booting</title> +<para> + +After entering the command monitor use + +<informalexample><screen> +bootp(): +</screen></informalexample> + +on SGI Indys to boot linux and to begin installation of the Debian +Software. In order to make this +work you may have to unset the <envar>netaddr</envar> environment +variable. Type + +<informalexample><screen> +unsetenv netaddr +</screen></informalexample> + +in the command monitor to do this. + +</para> + </sect3> + + <sect3> + <title>Broadcom BCM91250A TFTP Booting</title> +<para> + +On the Broadcom BCM91250A evaluation board, you have to load the SiByl boot +loader via TFTP which will then load and start the Debian installer. In +most cases, you will first obtain an IP address via DHCP but it is also +possible to configure a static address. In order to use DHCP, you can +enter the following command on the CFE prompt: + +<informalexample><screen> +ifconfig eth0 -auto +</screen></informalexample> + +Once you have obtained an IP address, you can load SiByl with the following +command: + +<informalexample><screen> +boot 192.168.1.1:/boot/sibyl +</screen></informalexample> + +You need to substitute the IP address listed in this example with either +the name or the IP address of your TFTP server. Once you issue this +command, the installer will be loaded automatically. + +</para> +</sect3> + </sect2> + + <sect2 arch="mips"><title>Boot Parameters</title> + + <sect3> + <title>SGI Indys TFTP Booting</title> +<para> + +On SGI Indys you can append boot parameters to the +<command>bootp():</command> command in the command monitor. + +</para><para> + +Following the <command>bootp():</command> command you can give the +path and name of the file to boot if you did not give an explicit name +via your bootp/dhcp server. Example: + +<informalexample><screen> +bootp():/boot/tftpboot.img +</screen></informalexample> + +Further kernel parameters can be passed via <command>append</command>: + +<informalexample><screen> +bootp(): append="root=/dev/sda1" +</screen></informalexample> + +</para> + </sect3> + + <sect3> + <title>Broadcom BCM91250A TFTP Booting</title> +<para> + +You cannot pass any boot parameters directly from the CFE prompt. Instead, +you have to edit the <filename>/boot/sibyl.conf</filename> file on the TFTP +server and add your parameters to the <replaceable>extra_args</replaceable> +variable. + +</para> + </sect3> + + </sect2> diff --git a/ca/boot-installer/mipsel.xml b/ca/boot-installer/mipsel.xml new file mode 100644 index 000000000..8bb5106b5 --- /dev/null +++ b/ca/boot-installer/mipsel.xml @@ -0,0 +1,12 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 24701 --> + + <sect2 arch="mipsel"> + <title></title> +<para> + +<!-- Placeholder document; please write and include in + boot-installer.xml and build/templates/docstruct.ent --> + +</para> + </sect2> diff --git a/ca/boot-installer/parameters.xml b/ca/boot-installer/parameters.xml new file mode 100644 index 000000000..280204c83 --- /dev/null +++ b/ca/boot-installer/parameters.xml @@ -0,0 +1,323 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 25171 --> + + <sect1 id="boot-parms"><title>Paràmetres d'arrencada</title> +<para> + +Els paràmetres d'arrencada són paràmetres del nucli de Linux que +s'utilitzen per assegurar que els perifèrics es gestionen +correctament. En la majoria de casos el nucli és capaç +de detectar automàticament la informació dels perifèrics. +Tot i això, en algunes ocasions haureu d'ajudar-lo. + +</para><para> + +Si és la primera vegada que arrenqueu el sistema utilitzeu +els paràmetres d'arrencada predeterminats (ex. no intenteu +especificar cap paràmetre) i observeu si s'executa +correctament; probablement ho farà. Si no és el cas, +podeu tornar a arrencar més tard i buscar qualsevol +paràmetre especial que informi al sistema respecte +al vostre maquinari. + +</para><para> + +Podeu trobar informació referent a molts paràmetre de l'arrencada a +<ulink url="http://www.tldp.org/HOWTO/BootPrompt-HOWTO.html">Linux +BootPrompt HOWTO</ulink>, inclosos alguns trucs per a maquinari +obscur. Aquesta secció conté únicament una representació dels paràmetres +més destacats. Podeu trobar una petita selecció dels problemes més +habituals a <xref linkend="boot-troubleshooting"/>. + +</para><para> + +A l'inici de l'arrencada del nucli hauria d'aparèixer el missatge + +<informalexample><screen> +Memòria:<replaceable>dispo</replaceable>k/<replaceable>total</replaceable>k disponible +</screen></informalexample> + +<replaceable>total</replaceable> hauria d'indicar la quantitat +total de RAM en kilobytes. Si no coincideix amb la quantitat de RAM que +teniu instal·lada utilitzeu el paràmetre +<userinput>mem=<replaceable>ram</replaceable></userinput>, +on <replaceable>ram</replaceable> correspon a la quantitat de memòria, +amb el sufix 'k' pels kilobytes, o 'm' per les megabytes. Per exemple, +<userinput>mem=65536K</userinput> i <userinput>mem=64M</userinput> +corresponen a 65MB de RAM. + +</para><para condition="supports-serial-console"> + +Si esteu arrencant via una consola sèrie el nucli ho detectarà +automàticament <phrase arch="mipsel"> (no en el cas de les estacions +DEC)</phrase>. +Si disposeu d'una tarja de vídeo (framebuffer) i un teclat connectats +a l'ordinador del qual voleu arrencar, hauríeu de passar passar el +paràmetre +<userinput>console=<replaceable>device</replaceable></userinput> +al nucli; <replaceable>device</replaceable> correspon al dispositiu +sèrie, que acostuma a ser similar a <filename>ttyS0</filename>. + +</para><para arch="sparc"> + +Per a l'arquitectura &arch-title; els dispositius sèrie són els +<filename>ttya</filename> o <filename>ttyb</filename>. +D'altra banda, definiu les variables OpenROM <envar>input-device</envar> +i <envar>output-device</envar> com a <filename>ttya</filename>. + +</para> + + <sect2 id="installer-args"><title>Paràmetres de l'instal·lador de Debian</title> +<para> + +El sistema d'instal·lació reconeix un conjunt de paràmetres +d'arrencada<footnote> + +<para> + +Tingueu en compte que el nucli accepta un màxim de 8 paràmetres de línia +d'ordres i 8 paràmetres d'entorn (incloent qualsevol paràmetre afegit de +forma predeterminada per l'instal·lador). Si s'excedeixen aquests números, +els nuclis 2.4 ignoraran qualsevol paràmetre restant i els nuclis 2.6 +produiran un pànic. + +</para> + +</footnote> addicionals que us podrien ser d'utilitat. + +</para> + +<variablelist> +<varlistentry> +<term>debconf/priority</term> +<listitem><para> + +Aquest paràmetre definirà la prioritat més alta dels missatges a mostrar. + +</para><para> + +La instal·lació predeterminada utilitza +<userinput>debconf/priority=high</userinput>. +En aquest cas es mostraran els missatges amb prioritat high i critical, +però s'anul·laran els missatges amb prioritat medium i low. Si +l'instal·lador detecta algun problema, ajustarà la prioritat en +funció de les necessitats que n'esdevinguin. + +</para><para> + +Si utilitzeu el paràmetre d'arrencada +<userinput>debconf/priority=medium</userinput>, se us mostrarà el +menú d'instal·lació i disposareu de més control sobre la instal·lació. +Quan s'utilitza el paràmetre <userinput>debconf/priority=low</userinput> +es mostraran tots els missatges (és equivalent al mètode d'arrencada +<emphasis>expert</emphasis>). En el cas de +<userinput>debconf/priority=critical</userinput>, el sistema +d'instal·lació mostrarà únicament els missatges crítics i +procurarà fer la feina correctament sense mostrar missatges. + + +</para></listitem> +</varlistentry> + +<varlistentry> +<term>DEBIAN_FRONTEND</term> +<listitem><para> + +Aquest paràmetre d'arrencada defineix el tipus d'interfície d'usuari +utilitzat per l'instal·lador. Els possibles paràmetres de configuració +actuals són: + +<itemizedlist> +<listitem> +<para><userinput>DEBIAN_FRONTEND=noninteractive</userinput></para> +</listitem><listitem> +<para><userinput>DEBIAN_FRONTEND=text</userinput></para> +</listitem><listitem> +<para><userinput>DEBIAN_FRONTEND=newt</userinput></para> +</listitem><listitem> +<para><userinput>DEBIAN_FRONTEND=slang</userinput></para> +</listitem><listitem> +<para><userinput>DEBIAN_FRONTEND=ncurses</userinput></para> +</listitem><listitem> +<para><userinput>DEBIAN_FRONTEND=bogl</userinput></para> +</listitem><listitem> +<para><userinput>DEBIAN_FRONTEND=gtk</userinput></para> +</listitem><listitem> +<para><userinput>DEBIAN_FRONTEND=corba</userinput></para> +</listitem> +</itemizedlist> + +El tipus predeterminat és +<userinput>DEBIAN_FRONTEND=newt</userinput>. +En el cas de les instal·lacions a través de la consola sèrie s'acostuma +a utilitzar +<userinput>DEBIAN_FRONTEND=text</userinput>. En general, l'únic tipus +disponible en el mitjà d'instal·lació predeterminat és el +<userinput>newt</userinput>, i per tant actualment no és molt útil. + +</para></listitem> +</varlistentry> + +<varlistentry> +<term>BOOT_DEBUG</term> +<listitem><para> + +Utilitzant aquest paràmetre d'arrencada induirà l'arrencada a mostrar +més missatges. + +<variablelist> +<varlistentry> +<term><userinput>BOOT_DEBUG=0</userinput></term> +<listitem><para>És el valor predeterminat.</para></listitem> +</varlistentry> + +<varlistentry> +<term><userinput>BOOT_DEBUG=1</userinput></term> +<listitem><para>Més missatges de l'habitual.</para></listitem> +</varlistentry> + +<varlistentry> +<term><userinput>BOOT_DEBUG=2</userinput></term> +<listitem><para>Molta informació de depuració.</para></listitem> +</varlistentry> + +<varlistentry> +<term><userinput>BOOT_DEBUG=3</userinput></term> +<listitem><para> + +Durant el procés d'arrencada s'executen diversos intèrprets d'ordres +que permeten una depuració més detallada. Per continuar l'arrencada +hareu de sortir de l'intèrpret d'ordres. + +</para></listitem> +</varlistentry> +</variablelist> + +</para></listitem> +</varlistentry> + +<varlistentry> +<term>INSTALL_MEDIA_DEV</term> +<listitem><para> + +El valor del paràmetre correspon al camí al dispositiu des del qual +carregar l'instal·lador de Debian. Per exemple, +<userinput>INSTALL_MEDIA_DEV=/dev/floppy/0</userinput> + +</para><para> + +El disquet d'arrencada, que normalment escaneja tots els disquets +i dispositius USB d'emmagatzematge per trobar el disquet arrel, es +pot substituir per aquest paràmetre per forçar que únicament busqui +en aquest dispositiu. + +</para></listitem> +</varlistentry> + +<varlistentry> +<term>debian-installer/framebuffer</term> +<listitem><para> + +Algunes arquitectures utilitzen el framebuffer del nucli per oferir +la instal·lació en diferents idiomes. Si el framebuffer us provoca +errors al sistema, podeu habilitar la característica utilitzant +el paràmetre <userinput>debian-installer/framebuffer=false</userinput>. +Els símptomes del problema són missatges d'error referents al +bogl, una pantalla en blanc o que es quedi congelat durant uns quants +minuts després d'iniciar la instal·lació. + +</para><para arch="i386"> + +Per inhabilitar el framebuffer també podeu utilitzar l'argument +<userinput>video=vga16:off</userinput>. La problemàtica relacionada +amb aquest paràmetre s'ha detectat en ordinadors Dell Inspiron +amb una tarja Mobile Radeon. + +</para><para arch="m68k"> + +La problemàtica s'ha detectat a l'Amiga 1220 i SE/30. + +</para><para arch="hppa"> + +La problemàtica s'ha detectat a l'hppa. + +</para></listitem> +</varlistentry> + +<varlistentry> +<term>debian-installer/probe/usb</term> +<listitem><para> + +Si l'intent d'arrencada a través d'USB us genera problemes, +el podeu evitar seleccionant <userinput>false</userinput>. + +</para></listitem> +</varlistentry> + +<varlistentry> +<term>netcfg/disable_dhcp</term> +<listitem><para> + +El &d-i; procura, per defecte, configurar la xarxa automàticament +utilitzant el DHCP. Si la configuració es realitza correctament +no podreu revisar-ne i modificar-ne els paràmetres obtinguts. +L'accés a la configuració manual de la xarxa només es donarà +quan falli la configuració per DHCP. + +</para><para> + +Si en la vostra xarxa local disposeu d'un servidor de DHCP però +no el voleu utilitzar, perquè per exemple us retorna respostes +incorrectes, podeu evitar-lo i introduir la informació manualment +utilitzant el paràmetre <userinput>netfcg/disable_dhcp=true</userinput>. + +</para></listitem> +</varlistentry> + +<varlistentry> +<term>hw-detect/start_pcmcia</term> +<listitem><para> + +Si us causa problemes i per evitar que s'iniciïn els serveis +PCMCIA trieu <userinput>false</userinput>. Aquest comportament +s'ha detectat en alguns ordinadors portàtils. + +</para></listitem> +</varlistentry> + +<varlistentry> +<term>preseed/url</term> +<listitem><para> + +Especifica l'URL que enllaça a un fitxer de preconfiguració +a baixar i utilitzar per automatitzar la instal·lació. +Per a més informació vegeu <xref linkend="automatic-install"/>. + +</para></listitem> +</varlistentry> + +<varlistentry> +<term>preseed/file</term> +<listitem><para> + +Especifica l'URL que enllaça a un fitxer de preconfiguració +a carregar per automatitzar la instal·lació. Per a més +informació vegeu <xref linkend="automatic-install"/> + +</para></listitem> +</varlistentry> + +<varlistentry> +<term>ramdisk_size</term> +<listitem><para> + +Si utilitzeu un nucli 2.2.x, probablement haureu d'especificar +la &ramdisksize;. + +</para></listitem> +</varlistentry> + +</variablelist> + </sect2> + </sect1> + diff --git a/ca/boot-installer/powerpc.xml b/ca/boot-installer/powerpc.xml new file mode 100644 index 000000000..214c176d4 --- /dev/null +++ b/ca/boot-installer/powerpc.xml @@ -0,0 +1,247 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 untranslated --> + + <sect2 arch="powerpc" id="boot-cd"><title>Booting from a CD-ROM</title> + +&boot-installer-intro-cd.xml; + +<para> + +Currently, the only &arch-title; subarchitectures that support CD-ROM +booting are PReP and New World PowerMacs. On PowerMacs, hold the +<keycap>c</keycap> key, or else the combination of +<keycap>Command</keycap>, <keycap>Option</keycap>, +<keycap>Shift</keycap>, and <keycap>Delete</keycap> +keys together while booting to boot from the CD-ROM. + +</para><para> + +OldWorld PowerMacs will not boot a Debian CD, because OldWorld +computers relied on a Mac OS ROM CD boot driver to be present on the CD, +and a free-software version of this driver is not available. All +OldWorld systems have floppy drives, so use the floppy drive to launch +the installer, and then point the installer to the CD for the needed +files. + +</para><para> + +If your system doesn't boot directly from CD-ROM, you can still use +the CD-ROM to install the system. On NewWorlds, you can also use an +OpenFirmware command to boot from the CD-ROM manually. Follow the +instructions in <xref linkend="boot-newworld"/> for booting from +the hard disk, except use the path to <command>yaboot</command> on the +CD at the OF prompt, such as + +<informalexample><screen> +0 > boot cd:,\install\yaboot +</screen></informalexample> + +</para> + </sect2> + + <sect2 arch="powerpc" id="install-drive"> + <title>Booting from Hard Disk</title> + +&boot-installer-intro-hd.xml; + + <sect3><title>Booting CHRP from OpenFirmware</title> + +<para> + + <emphasis>Not yet written.</emphasis> + +</para> + </sect3> + + <sect3><title>Booting OldWorld PowerMacs from MacOS</title> +<para> + +If you set up BootX in <xref linkend="files-oldworld"/>, you can +use it to boot into the installation system. Double click the +<guiicon>BootX</guiicon> application icon. Click on the +<guibutton>Options</guibutton> button and select <guilabel>Use +Specified RAM Disk</guilabel>. This will give you the +chance to select the <filename>ramdisk.image.gz</filename> file. You +may need to select the <guilabel>No Video Driver</guilabel> checkbox, +depending on your hardware. Then click the +<guibutton>Linux</guibutton> button to shut down MacOS and launch the +installer. + +</para> + </sect3> + + + <sect3 id="boot-newworld"> + <title>Booting NewWorld Macs from OpenFirmware</title> +<para> + +You will have already placed the <filename>vmlinux</filename>, +<filename>initrd.gz</filename>, <filename>yaboot</filename>, and +<filename>yaboot.conf</filename> files at the root level of your HFS +partition in <xref linkend="files-newworld"/>. +Restart the computer, and immediately (during the chime) hold down the +<keycap>Option</keycap>, <keycap>Command (cloverleaf/Apple)</keycap>, +<keycap>o</keycap>, and <keycap>f</keycap> keys all together. After +a few seconds you will be presented with the Open Firmware prompt. +At the prompt, type + +<informalexample><screen> +0 > boot hd:<replaceable>x</replaceable>,yaboot +</screen></informalexample> + +replacing <replaceable>x</replaceable> with the partition number of +the HFS partition where the +kernel and yaboot files were placed, followed by a &enterkey;. On some +machines, you may need to use <userinput>ide0:</userinput> instead of +<userinput>hd:</userinput>. In a few more seconds you will see a +yaboot prompt + +<informalexample><screen> +boot: +</screen></informalexample> + +At yaboot's <prompt>boot:</prompt> prompt, type either +<userinput>install</userinput> or <userinput>install video=ofonly</userinput> +followed by a &enterkey;. The +<userinput>video=ofonly</userinput> argument is for maximum +compatibility; you can try it if <userinput>install</userinput> +doesn't work. The Debian installation program should start. + +</para> + </sect3> + </sect2> + + <sect2 arch="powerpc" id="usb-boot"> + <title>Booting from USB memory stick</title> +<para> + +Currently, NewWorld PowerMac systems are known to support USB booting. + +</para> + +<para> + +Make sure you have prepared everything from <xref +linkend="boot-usb-files"/>. To boot a Macintosh system from a USB stick, +you will need to use the Open Firmware prompt, since Open Firmware does +not search USB storage devices by default. +<!-- TODO: although it could be made to; watch this space --> +To get to the prompt, hold down +<keycombo><keycap>Command</keycap> <keycap>Option</keycap> +<keycap>o</keycap> <keycap>f</keycap></keycombo> all together while +booting (see <xref linkend="invoking-openfirmware"/>). + +</para><para> + +You will need to work out where the USB storage device appears in the +device tree, since at the moment <command>ofpath</command> cannot work +that out automatically. Type <userinput>dev / ls</userinput> and +<userinput>devalias</userinput> at the Open Firmware prompt to get a +list of all known devices and device aliases. On the author's system +with various types of USB stick, paths such as +<filename>usb0/disk</filename>, <filename>usb0/hub/disk</filename>, +<filename>/pci@f2000000/usb@1b,1/disk@1</filename>, and +<filename>/pci@f2000000/usb@1b,1/hub@1/disk@1</filename> work. + +</para><para> + +Having worked out the device path, use a command like this to boot the +installer: + +<informalexample><screen> +boot <replaceable>usb0/disk</replaceable>:<replaceable>2</replaceable>,\\:tbxi +</screen></informalexample> + +The <replaceable>2</replaceable> matches the Apple_HFS or +Apple_Bootstrap partition onto which you copied the boot image earlier, +and the <userinput>,\\:tbxi</userinput> part instructs Open Firmware to +boot from the file with an HFS file type of "tbxi" (i.e. +<command>yaboot</command>) in the directory previously blessed with +<command>hattrib -b</command>. + +</para><para> + +The system should now boot up, and you should be presented with the +<prompt>boot:</prompt> prompt. Here you can enter optional boot +arguments, or just hit &enterkey;. + +</para><warning><para> + +This boot method is new, and may be difficult to get to work on some +NewWorld systems. If you have problems, please file an installation +report, as explained in <xref linkend="submit-bug"/>. + +</para></warning> + </sect2> + + <sect2 arch="powerpc" id="boot-tftp"><title>Booting with TFTP</title> + +&boot-installer-intro-net.xml; + +<para> + +Currently, PReP and New World PowerMac systems support netbooting. + +</para><para> + +On machines with Open Firmware, such as NewWorld Power Macs, enter the +boot monitor (see <xref linkend="invoking-openfirmware"/>) and +use the command <command>boot enet:0</command>. PReP and CHRP boxes +may have different ways of addressing the network. On a PReP machine, +you should try +<userinput>boot <replaceable>server_ipaddr</replaceable>,<replaceable>file</replaceable>,<replaceable>client_ipaddr</replaceable></userinput>. + +</para> + </sect2> + + + <sect2 arch="powerpc"> + <title>Booting from Floppies</title> +<para> + +Booting from floppies is supported for &arch-title;, although it is +generally only applicable for OldWorld systems. NewWorld systems are +not equipped with floppy drives, and attached USB floppy drives are +not supported for booting. + +</para><para> + +You will have already downloaded the floppy images you needed and +created floppies from the images in <xref linkend="create-floppy"/>. + +</para><para> + +To boot from the <filename>boot-floppy-hfs.img</filename> floppy, +place it in floppy drive after shutting the system down, and before +pressing the power-on button. + +</para><note><para> +For those not familiar with Macintosh +floppy operations: a floppy placed in the machine prior to boot will +be the first priority for the system to boot from. A floppy without a +valid boot system will be ejected, and the machine will then check for +bootable hard disk partitions. + +</para></note><para> + +After booting, the <filename>root.bin</filename> floppy is +requested. Insert the root floppy and press &enterkey;. The installer +program is automatically launched after the root system has been +loaded into memory. + +</para> + </sect2> + + + <sect2 arch="powerpc"><title>PowerPC Boot Parameters</title> +<para> + +Many older Apple monitors used a 640x480 67Hz mode. If your video +appears skewed on an older Apple monitor, try appending the boot +argument <userinput>video=atyfb:vmode:6</userinput> , which will +select that mode for most Mach64 and Rage video hardware. For Rage 128 +hardware, this changes to +<userinput>video=aty128fb:vmode:6</userinput> . + +</para> + </sect2> diff --git a/ca/boot-installer/s390.xml b/ca/boot-installer/s390.xml new file mode 100644 index 000000000..dcf89b594 --- /dev/null +++ b/ca/boot-installer/s390.xml @@ -0,0 +1,30 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 --> + + <sect2 arch="s390"><title>Limitacions a s390</title> +<para> + +Per tal de fer servir el sistema d'instal·lació a S/390, necessitareu +una configuració de xarxa que funcioni i una sessió ssh. + +</para><para> + +El procés d'arrencada comença amb una configuració de xarxa que us +preguntarà per diversos paràmetres de xarxa. Si la configuració té +èxit, connectareu al sistema començant una sessió ssh que +llençara el sistema estàndard d'instal·lació. + +</para> + </sect2> + + + <sect2 arch="s390"><title>Paràmetres d'arranc a s390</title> +<para> + +A S/390 podeu afegir paràmetres d'arranc al fitxer «parm». Aquest fitxer pot +estar en format ASCII o EBCDIC. Si us plau llegiu +<ulink url="&url-s390-devices;">Controladors de dispositius i ordres d'instal·lació</ulink> +per a més informació sobre paràmetres d'arranc específics de S/390. + +</para> + </sect2> diff --git a/ca/boot-installer/sparc.xml b/ca/boot-installer/sparc.xml new file mode 100644 index 000000000..81cad25e7 --- /dev/null +++ b/ca/boot-installer/sparc.xml @@ -0,0 +1,89 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 untranslated --> + + <sect2 arch="sparc" id="boot-tftp"><title>Booting with TFTP</title> + +&boot-installer-intro-net.xml; + +<para> + +On machines with OpenBoot, simply enter the boot monitor on the +machine which is being installed (see +<xref linkend="invoking-openboot"/>). +Use the command <userinput>boot net</userinput> to boot from a TFTP +and RARP server, or try <userinput>boot net:bootp</userinput> or +<userinput>boot net:dhcp</userinput> to boot from a TFTP and BOOTP +or DHCP server. Some older OpenBoot revisions require using +the device name, such as <userinput>boot le()</userinput>; these +probably don't support BOOTP nor DHCP. + +</para> + </sect2> + + + <sect2 arch="sparc"><title>Booting from a CD-ROM</title> + +&boot-installer-intro-cd.xml; + +<para> + +Most OpenBoot versions support the <userinput>boot cdrom</userinput> +command which is simply an alias to boot from the SCSI device on ID 6 +(or the secondary master for IDE based systems). You may have to use +the actual device name for older OpenBoot versions that don't support +this special command. Note that some problems have been reported on Sun4m +(e.g., Sparc 10s and Sparc 20s) systems booting from CD-ROM. + +</para> + </sect2> + + + <sect2 arch="sparc" condition="supports-floppy-boot"> + <title>Booting from Floppies</title> +<para> + +To boot from floppy on a Sparc, use + +<informalexample><screen> +Stop-A -> OpenBoot: "boot floppy" +</screen></informalexample> + +Be warned that the newer Sun4u (ultra) architecture does not support +floppy booting. A typical error message is <computeroutput>Bad magic +number in disk label - Can't open disk label package</computeroutput>. +Furthermore, a number of Sun4c models (such as the IPX) do not support +the compressed images found on the disks, so also are not supported. + +</para><para> + +Several Sparcs (e.g. Ultra 10) have an OBP bug that prevents them from +booting (instead of not supporting booting at all). The appropriate +OBP update can be downloaded as product ID 106121 from +<ulink url="http://sunsolve.sun.com"></ulink>. + +</para><para> + +If you are booting from the floppy, and you see messages such as + +<informalexample><screen> +Fatal error: Cannot read partition +Illegal or malformed device name +</screen></informalexample> + +then it is possible that floppy booting is simply not supported on +your machine. + +</para> + </sect2> + + <sect2 arch="sparc"><title>IDPROM Messages</title> +<para> + +If you cannot boot because you get messages about a problem with +<quote>IDPROM</quote>, then it's possible that your NVRAM battery, which +holds configuration information for you firmware, has run out. See the +<ulink url="&url-sun-nvram-faq;">Sun NVRAM FAQ</ulink> for more +information. + +</para> + </sect2> diff --git a/ca/boot-installer/trouble.xml b/ca/boot-installer/trouble.xml new file mode 100644 index 000000000..831d6aab5 --- /dev/null +++ b/ca/boot-installer/trouble.xml @@ -0,0 +1,274 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 untranslated --> + + <sect1 id="boot-troubleshooting"> + <title>Troubleshooting the Installation Process</title> +<para> +</para> + + <sect2 condition="supports-floppy-boot" id="unreliable-floppies"> + <title>Floppy Disk Reliability</title> + +<para> + +The biggest problem for people using floppy disks to install Debian +seems to be floppy disk reliability. + +</para><para> + +The boot floppy is the floppy with the worst problems, because it +is read by the hardware directly, before Linux boots. Often, the +hardware doesn't read as reliably as the Linux floppy disk driver, and +may just stop without printing an error message if it reads incorrect +data. There can also be failures in the Driver Floppies most of which +indicate themselves with a flood of messages about disk I/O errors. + +</para><para> + +If you are having the installation stall at a particular floppy, the +first thing you should do is re-download the floppy disk image and +write it to a <emphasis>different</emphasis> floppy. Simply +reformatting the old +floppy may not be sufficient, even if it appears that the floppy was +reformatted and written with no errors. It is sometimes useful to try +writing the floppy on a different system. + +</para><para> + +One user reports he had to write the images to floppy +<emphasis>three</emphasis> times before one worked, and then +everything was fine with the third floppy. + +</para><para> + +Other users have reported that simply rebooting a few times with the +same floppy in the floppy drive can lead to a successful boot. This is +all due to buggy hardware or firmware floppy drivers. + +</para> + </sect2> + + <sect2><title>Boot Configuration</title> + +<para> + +If you have problems and the kernel hangs during the boot process, +doesn't recognize peripherals you actually have, or drives are not +recognized properly, the first thing to check is the boot parameters, +as discussed in <xref linkend="boot-parms"/>. + +</para><para> + +If you are booting with your own kernel instead of the one supplied +with the installer, be sure that <userinput>CONFIG_DEVFS</userinput> is set in +your kernel. The installer requires +<userinput>CONFIG_DEVFS</userinput>. + +</para><para> + +Often, problems can be solved by removing add-ons and peripherals, and +then trying booting again. <phrase arch="i386">Internal modems, sound +cards, and Plug-n-Play devices can be especially problematic.</phrase> + +</para><para> + +If you have a large amount of memory installed in your machine, more +than 512M, and the installer hangs when booting the kernel, you may +need to include a boot argument to limit the amount of memory the +kernel sees, such as <userinput>mem=512m</userinput>. + +</para> + </sect2> + + <sect2 arch="i386" id="i386-boot-problems"> + <title>Common &arch-title; Installation Problems</title> +<para> + +There are some common installation problems that can be solved or avoided by +passing certain boot parameters to the installer. + +</para><para> + +Some systems have floppies with <quote>inverted DCLs</quote>. If you receive +errors reading from the floppy, even when you know the floppy is good, +try the parameter <userinput>floppy=thinkpad</userinput>. + +</para><para> + +On some systems, such as the IBM PS/1 or ValuePoint (which have ST-506 +disk drivers), the IDE drive may not be properly recognized. Again, +try it first without the parameters and see if the IDE drive is +recognized properly. If not, determine your drive geometry +(cylinders, heads, and sectors), and use the parameter +<userinput>hd=<replaceable>cylinders</replaceable>,<replaceable>heads</replaceable>,<replaceable>sectors</replaceable></userinput>. + +</para><para> + +If you have a very old machine, and the kernel hangs after saying +<computeroutput>Checking 'hlt' instruction...</computeroutput>, then +you should try the <userinput>no-hlt</userinput> boot argument, which +disables this test. + +</para><para> + +If your screen begins to show a weird picture while the kernel boots, +eg. pure white, pure black or colored pixel garbage, your system may +contain a problematic video card which does not switch to the +framebuffer mode properly. Then you can use the boot parameter +<userinput>debian-installer/framebuffer=false</userinput> or +<userinput>video=vga16:off</userinput> to disable the framebuffer +console. Only the English +language will be available during the installation due to limited +console features. See <xref linkend="boot-parms"/> for details. + +</para> + + <sect3> + <title>System Freeze During the PCMCIA Configuration Phase</title> +<para> + +Some laptop models produced by Dell are known to crash when PCMCIA device +detection tries to access some hardware addresses. Other laptops may display +similar problems. If you experience such a problem and you don't need PCMCIA +support during the installation, you can disable PCMCIA using the +<userinput>hw-detect/start_pcmcia=false</userinput> boot parameter. You can +then configure PCMCIA after the installation is completed and exclude the +resource range causing the problems. + +</para><para> + +Alternatively, you can boot the installer in expert mode. You will +then be asked to enter the resource range options your hardware +needs. For example, if you have one of the Dell laptops mentioned +above, you should enter <userinput>exclude port +0x800-0x8ff</userinput> here. There is also a list of some common +resource range options in the <ulink +url="http://pcmcia-cs.sourceforge.net/ftp/doc/PCMCIA-HOWTO-1.html#ss1.12">System +resource settings section of the PCMCIA HOWTO</ulink>. Note that you +have to omit the commas, if any, when you enter this value in the +installer. + +</para> + </sect3> + + <sect3> + <title>System Freeze while Loading the USB Modules</title> +<para> + +The kernel normally tries to install USB modules and the USB keyboard driver +in order to support some non-standard USB keyboards. However, there are some +broken USB systems where the driver hangs on loading. A possible workaround +may be disabling the USB controller in your mainboard BIOS setup. Another option +is passing the <userinput>debian-installer/probe/usb=false</userinput> parameter +at the boot prompt, which will prevent the modules from being loaded. + +</para> + </sect3> + </sect2> + + <sect2 id="kernel-msgs"> + <title>Interpreting the Kernel Startup Messages</title> + +<para> + +During the boot sequence, you may see many messages in the form +<computeroutput>can't find <replaceable>something</replaceable> +</computeroutput>, or <computeroutput> +<replaceable>something</replaceable> not present</computeroutput>, +<computeroutput>can't initialize <replaceable>something</replaceable> +</computeroutput>, or even <computeroutput>this driver release depends +on <replaceable>something</replaceable> </computeroutput>. +Most of these messages are harmless. You +see them because the kernel for the installation system is built to +run on computers with many different peripheral devices. Obviously, no +one computer will have every possible peripheral device, so the +operating system may emit a few complaints while it looks for +peripherals you don't own. You may also see the system pause for a +while. This happens when it is waiting for a device to respond, and +that device is not present on your system. If you find the time it +takes to boot the system unacceptably long, you can create a +custom kernel later (see <xref linkend="kernel-baking"/>). + +</para> + </sect2> + + + <sect2 id="problem-report"> + <title>Bug Reporter</title> +<para> + +If you get through the initial boot phase but cannot complete the +install, the bug reporter menu choice may be helpful. It copies system +error logs and configuration information to a user-supplied floppy. +This information may provide clues as to what went wrong and how to +fix it. If you are submitting a bug report you may want to attach +this information to the bug report. + +</para><para> + +Other pertinent installation messages may be found in +<filename>/var/log/</filename> during the +installation, and <filename>/var/log/debian-installer/</filename> +after the computer has been booted into the installed system. + +</para> + </sect2> + + <sect2 id="submit-bug"> + <title>Submitting Installation Reports</title> +<para> + +If you still have problems, please submit an installation report. We also +encourage installation reports to be sent even if the installation is +successful, so that we can get as much information as possible on the largest +number of hardware configurations. Please use this template when filling out +installation reports, and file the report as a bug report against the +<classname>installation-reports</classname> pseudo package, by sending it to +<email>submit@bugs.debian.org</email>. + +<informalexample><screen> +Package: installation-reports + +Debian-installer-version: <Fill in date and from where you got the image> +uname -a: <The result of running uname -a on a shell prompt> +Date: <Date and time of the install> +Method: <How did you install? What did you boot off? If network + install, from where? Proxied?> + +Machine: <Description of machine (eg, IBM Thinkpad R32)> +Processor: +Memory: +Root Device: <IDE? SCSI? Name of device?> +Root Size/partition table: <Feel free to paste the full partition + table, with notes on which partitions are mounted where.> +Output of lspci and lspci -n: + +Base System Installation Checklist: +[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it + +Initial boot worked: [ ] +Configure network HW: [ ] +Config network: [ ] +Detect CD: [ ] +Load installer modules: [ ] +Detect hard drives: [ ] +Partition hard drives: [ ] +Create file systems: [ ] +Mount partitions: [ ] +Install base system: [ ] +Install boot loader: [ ] +Reboot: [ ] + +Comments/Problems: + +<Description of the install, in prose, and any thoughts, comments + and ideas you had during the initial install.> +</screen></informalexample> + +In the bug report, describe what the problem is, including the last +visible kernel messages in the event of a kernel hang. Describe the +steps that you did which brought the system into the problem state. + +</para> + </sect2> + </sect1> diff --git a/ca/boot-new/boot-new.xml b/ca/boot-new/boot-new.xml new file mode 100644 index 000000000..8a1c07f30 --- /dev/null +++ b/ca/boot-new/boot-new.xml @@ -0,0 +1,294 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28730 --> + +<chapter id="boot-new"> + <title>Arrancada en el vostra nou sistema Debian</title> + + <sect1 id="base-boot"><title>El moment de la veritat</title> +<para> + +La primera arrencada del vostre sistema pels seus propis mitjans és el que els +enginyers electrònics anomenen la <quote>prova de foc</quote>. + +</para><para> + +Si esteu arrencant directament amb Debian, i el sistema no comença a +funcionar, utilitzeu el vostre medi d'instal·lació original, o bé inseriu +el disquet d'arrencada personalitzat si en teniu, i torneu a inicieu el +vostra sistema. D'aquesta manera, probablement necessitareu afegir algun +argument d'arrencada com +<userinput>root=<replaceable>arrel</replaceable></userinput>, on +<replaceable>l'arrel</replaceable> és la vostra partició arrel, com per +exemple <filename>/dev/sda1</filename>. +<phrase condition="etch"> +D'altra banda, vegeu <xref linkend="rescue"/> per instrucciones per a usar +el mode intern de rescat de l'instal·lador. +</phrase> + +</para> + + <sect2 arch="m68k"><title>Arrencada en un BVME 6000</title> +<para> + +Si acabeu de realitzar una instal·lació sense disc en una màquina BVM o +Motorola VMEbus: un cop el sistema hagi carregat el programa +<command>tftplilo</command> des del servidor TFTP, entreu un dels següents en +l'indicador <prompt>LILO Boot:</prompt>: + +<itemizedlist> +<listitem><para> + +<userinput>b6000</userinput> seguit de &enterkey; +per arrencar un BVME 4000/6000 + +</para></listitem><listitem><para> + +<userinput>b162</userinput> seguit de &enterkey; +per arrencar un MVME162 + +</para></listitem><listitem><para> + +<userinput>b167</userinput> seguit de &enterkey; +per arrencar un MVME166/167 + +</para></listitem> +</itemizedlist> + +</para> + + </sect2> + + <sect2 arch="m68k"><title>Arrencada en un Macintosh</title> + +<para> + +Aneu al directori que conté els fitxers d'instal·lació i inicieu el programa +d'arrencada <command>Penguin</command>, prement la tecla +<keycap>command</keycap>. Aneu al diàleg d'<userinput>Arranjament</userinput> +(<keycombo><keycap>command</keycap> <keycap>T</keycap> </keycombo>), i +localitzeu la línia d'opcions del nucli, que hauria d'assemblar-se a +<userinput>root=/dev/ram video=font:VGA8x16</userinput>. + +</para><para> + +Haureu de canviar l'entrada a +<userinput>root=/dev/<replaceable>yyyy</replaceable></userinput>. +Reemplaceu les <replaceable>yyyy</replaceable> amb el nom Linux de la partició +on vau instal·lar el sistema (p.ex. <filename>/dev/sda1</filename>); heu anotat +això abans. Es recomana l'opció <userinput>video=font:VGA8x8</userinput> +especialment als usuaris amb pantalles petites. El nucli seleccionaria una font +més maca (6x11) però com que el controlador de la consola per aquesta font pot +penjar la màquina, és més segur utilitzar 8x16 o 8x8 en aquesta fase. Podeu +canviar-ho en qualsevol moment. + +</para><para> + +Si no voleu arrencar el GNU/Linux immediatament cada vegada que inicieu, +desseleccioneu l'opció <userinput>Auto Arrencada</userinput>. Deseu el vostre +arranjament al fitxer <filename>Prefs</filename> utilitzant l'opció +<userinput>Desa l'arranjament com a perdeterminat</userinput>. + +</para><para> + +Seleccioneu ara <userinput>Arrencar ara</userinput> (<keycombo> +<keycap>command</keycap> <keycap>B</keycap> </keycombo>) per iniciar el +GNU/Linux recent instal·lat en comptes del sistema d'instal·lació RAMdisk. + +</para><para> + +Debian hauria d'arrencar, i hauríeu de veure el mateix missatge que quan +vau arrencar el sistema d'instal·lació per primera vegada, seguit per alguns +missatges nous. + +</para> + </sect2> + + + <sect2 arch="powerpc"><title>PowerMacs OldWorld</title> +<para> + +Si la màquina falla en arrencar després de completar la instal·lació, i +es para amb un indicador <prompt>boot:</prompt>, intenteu-ho teclejant +<userinput>Linux</userinput> seguit de &enterkey;. (La configuració +d'arrencada predeterminada a <filename>quik.conf</filename> té l'etiqueta +Linux). Les etiquetes definides a <filename>quik.conf</filename> es +mostraran si premeu la tecla <keycap>Tab</keycap> a l'indicador +<prompt>boot:</prompt>. També podeu provar d'arrencar de nou amb +l'instal·lador, i editar el <filename>/target/etc/quik.conf</filename> que +el pas <guimenuitem>Instal·la el Quik al disc dur</guimenuitem> +ha col·locat allà. A <ulink url="&url-powerpc-quik-faq;"></ulink> podeu +trobar pistes per tractar amb el <command>quik</command>. + +</para><para> + +Per arrencar de nou en el MacOS sense reinicialitzar la nvram, teclegeu +<userinput>bye</userinput> a l'indicador del OpenFirmware (suposant que +el MacOS no s'hagi tret de la màquina). Per obtenir un indicador de +l'OpenFirmware, manteniu premudes les tecles <keycombo> <keycap>command</keycap> +<keycap>option</keycap> <keycap>o</keycap> <keycap>f</keycap> +</keycombo> mentre feu una arrencada en fred de la màquina. Si necessiteu +desfer els canvis i tornar als valors predeterminats de l'OpenFirmware de +la nvram per tal de tornar a arrencar el MacOS, mantingueu premudes les +tecles <keycombo> <keycap>command</keycap> +<keycap>option</keycap> <keycap>p</keycap> <keycap>r</keycap> +</keycombo> mentre arrenqueu la màquina en fred. + +</para><para> + +Si utilitzeu <command>BootX</command> per arrencar amb el sistema instal·lat, +només seleccioneu el nucli desitjat en la carpeta <filename>Linux +Kernels</filename>, deseleccioneu l'opció ramdisk, i afegiu un dispositiu +arrel que correspongui amb la vostra instal·lació; p. ex. +<userinput>/dev/hda8</userinput>. + +</para> + </sect2> + + + <sect2 arch="powerpc"><title>NewWorld PowerMacs</title> +<para> + +A les màquines G4 i als iBooks, podeu mantenir la tecla +<keycap>option</keycap> premuda i obtindreu una pantalla gràfica amb +un botó per a cada sistema operatiu arrencable; el &debian; serà el +botó amb la icona d'un petit pingüí. + +</para><para> + +Si manteniu el MacOS i en algun punt us canvia la variable +<envar>boot-device</envar> de l'OpenFirmware hauríeu de tornar a +assignar a l'OpenFirmware la seva configuració predeterminada. Per fer +això manteniu les tecles <keycombo><keycap>command</keycap> +<keycap>option</keycap> <keycap>p</keycap> <keycap>r</keycap> +</keycombo> premudes mentre arrenqueu la màquina en fred. + +</para><para> + +Es mostraran les etiquetes definides a <filename>yaboot.conf</filename> +si premeu la tecla <keycap>Tab</keycap> a l'indicador +<prompt>boot:</prompt>. + +</para><para> + +Reinicialitzar l'OpenFirmware en el maquinari dels G3 o G4 causarà que +arranqui &debian; de manera predeterminada (si heu fet les particions +correctament i heu situat la partició de l'Apple_Bootstrap en primer lloc). +Si teniu &debian; en un disc SCSI i el MacOS en un disc IDE, pot ser que +això no funcioni i que hàgiu d'entrar a l'OpenFirmware i configurar la +variable <envar>boot-device</envar>; normalment el <command>ybin</command> +fa això automàticament. + +</para><para> + +Després d'arrencar &debian; per primer cop podreu afegir qualsevol opció +addicional que desitgeu (com opcions per a l'arrencada dual) a +<filename>/etc/yaboot.conf</filename> i executar <command>ybin</command> +per actualitzar la taula de particions la configuració de la qual hàgiu +canviat. Si us plau, per més informació llegiu el +<ulink url="&url-powerpc-yaboot-faq;">yaboot HOWTO</ulink>. + +</para> + </sect2> + </sect1> + + <sect1 id="base-config"> + <title>Configuració (bàsica) de Debian després de l'arrencada</title> + +<para> + +Després d'arrencar, se us indicarà que completeu la configuració del +vostre sistema bàsic, i posteriorment que seleccioneu els paquets +addicionals que desitgeu instal·lar. L'aplicació que us guiarà a través +d'aquest procés s'anomena <classname>base-config</classname>. El seu +concepte és molt similar al del &d-i; de la primera etapa. De fet, +el <classname>base-config</classname> consisteix en diversos components +especialitzats, cadascun dels quals s'encarrega d'una tasca de configuració, +conté <quote>menús amagats al darrera</quote> i també utilitza el mateix +sistema de navegació. + +</para><para> + +Si desitgeu tornar a executar el <classname>base-config</classname> +en qualsevol moment després que hagi acabat la instal·lació, +executeu com a root <userinput>base-config</userinput>. + +</para> + +&module-bc-timezone.xml; +&module-bc-shadow.xml; +&module-bc-ppp.xml; +&module-bc-apt.xml; +&module-bc-packages.xml; +&module-bc-install.xml; +&module-bc-mta.xml; + + </sect1> + + <sect1 id="login"> + <title>L'entrada</title> + +<para> + +Després que hàgiu instal·lat els paquets, s'us presentarà un +indicador d'entrada (login). Entreu utilitzant el nom d'usuari +personal i la contrasenya que hàgiu seleccionat. El vostre sistema +és a punt per ésser utilitzat. + +</para><para> + +Si sou un usuari nou, potser voleu explorar la documentació que ja està +instal·lada en el sistema quan comenceu a utilitzar-lo. Actualment hi ha +diversos sistemes de documentació; s'està fent feina per integrar els +diferents tipus de documentació. Aquí teniu alguns punts de partida. + +</para><para> + +La documentació que acompanya als programes que teniu instal·lats és a +<filename>/usr/share/doc/</filename>, sota un subdirectori que s'anomena +com el programa. Per exemple, la Guia d'usuari de l'APT per utilitzar +<command>apt</command> per instal·lar altres programes en el sistema, es +troba a <filename>/usr/share/doc/apt/guide.html/index.html</filename>. + +</para><para> + +Addicionalment, hi ha algunes carpetes especials dins de la +jerarquia de <filename>/usr/share/doc/</filename>. Els +COM ES FA de Linux s'instal·len en format +<emphasis>.gz</emphasis>, a +<filename>/usr/share/doc/HOWTO/en-txt/</filename>. Després +d'instal·lar <command>dhelp</command> trobareu un índex de +documentació navegable a +<filename>/usr/share/doc/HTML/index.html</filename>. + +</para><para> + +Una manera senzilla de veure aquests documents és amb +<userinput>cd /usr/share/doc/</userinput>, i teclejant +<userinput>lynx</userinput> seguit per un espai i un punt (el +punt es referix al directori actual). + +</para><para> + +També podeu teclejar <userinput>info +<replaceable>ordre</replaceable></userinput> o <userinput>man +<replaceable>ordre</replaceable></userinput> per veure la +documentació de la major part d'ordres disponibles a la línia de +comandes. Teclejant <userinput>help</userinput> es mostrarà +ajuda sobre les ordres de l'intèrpret. I teclejant una ordre +seguida de <userinput>--help</userinput> es visualitzarà usualment +un sumari curt de la utilització de l'ordre. Si el resultat d'una +ordre es desplaça passada la part superior de la pantalla, teclegeu +<userinput>| more</userinput> després de l'ordre per fer que els +resultats s'aturin abans de desplaçar-se fora de la pantalla. Per +veure una llista de totes les ordres disponibles que comencen amb una +certa lletra, teclegeu la lletra i després dos tabuladors. + +</para><para> + +Per una introducció més completa a Debian i al GNU/Linux, vegeu +<filename>/usr/share/doc/debian-guide/html/noframes/index.html</filename>. + +</para> + + </sect1> +</chapter> diff --git a/ca/boot-new/modules/apt.xml b/ca/boot-new/modules/apt.xml new file mode 100644 index 000000000..5b933cc7d --- /dev/null +++ b/ca/boot-new/modules/apt.xml @@ -0,0 +1,98 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 18642 --> + + <sect2 id="configure-apt"> + <title>Configurant l'APT</title> + +<para> + +El principal mètode que s'utilitza per instal·lar paquets al sistema, +és basa en la utilització d'un programa del paquet +<classname>apt</classname> anomenat <command>apt-get</command>.<footnote> + +<para> + +Recordeu que el programa que s'utilitza actualment per a la instal·lació +de paquets s'anomena <command>dpkg</command>. Tot i això, aquest paquet +és una eina de més baix nivell. L'<command>apt-get</command> cridarà +el <command>dpkg</command> de forma adecuada; el primer és de més alt +nivell, ja que és capaç d'instal·lar els paquets dels quals depèn el +paquet que voleu instal·lar i obtenir el paquet d'un CD, de la xarxa +o de qualsevol lloc. + +</para> +</footnote> + +L'APT s'ha de configurar perquè localitzi els llocs d'on ha d'obtenir +els paquets. L'aplicació que us ajudarà en el procés de configuració +s'anomena <command>apt-setup</command>. + +</para><para> + +El següent pas del procés de configuració és indicar a l'APT la +ubicació d'altres paquets de Debian. Recordeu que podeu tornar +a executar l'aplicació en qualsevol instant posterior a la instal·lació +utilitzant l'ordre <command>apt-setup</command> o editant manualment el +fitxer <filename>/etc/apt/sources.list</filename>. + +</para><para> + +Si en aquest instant hi ha insertat un CD-ROM a la unitat, aquest s'hauria +de configurar automàticament com a una font de l'apt. Us n'adonareu +perquè s'estarà escanejat el CD-ROM. + +</para><para> + +Els usuaris que no disposin d'un CD-ROM oficial podran accedir +als paquets de Debian a través de diversos mètodes: FTP, HTTP, CD-ROM +o el sistema de fitxers local. + +</para><para> + +Heu de saber que és viable disposar de múltiples fonts diferents +de l'APT, encara que corresponguin al mateix arxiu de Debian. +L'<command>apt-get</command> agafarà el paquet amb la versió +més alta de les múltiples versions disponibles. Per exemple, +si disposeu d'una font de l'APT en HTTP i una en CD-ROM, l' +<command>apt-get</command> hauria d'utilitzar automàticament +el CD-ROM local sempre que fos possible, i accedir a HTTP únicament +si hi hagués una versió més nova. Tot i això, no és recomanable +afegir fonts de l'APT innecessàries, ja que tendirà a alentir el procés +de comprovació de les noves versions en els arxius en xarxa. + +</para> + + <sect3 id="configure-apt-net"> + <title>Configurant les fonts de paquets en la xarxa</title> + +<para> + +Si planegeu instal·lar la resta del sistema mitjançant la xarxa, +l'opció més comuna és seleccionar la font <userinput>http</userinput>. +També s'accepta l'<userinput>ftp</userinput>, però tendeix a alentir +connexions més lentament. + +</para><para> + +El següent pas és especificar a l'<command>apt-setup</command> el +país on viviu. Aquesta opció configura el mirall d'Internet de +Debian oficial al qual us connectareu. En funció del país que +seleccioneu us apareixerà una llista d'ordinadors possibles. +En general és correcte escollir el primer de la llista, però +qualsevol d'ells hauria de funcionar correctament. + +</para><para> + +Si ho esteu instal·lant via HTTP, us preguntarà sobre la configuració +del servidor intermediari. Aquesta opció és necessària en cas d'estar +darrere un tallafocs, en una xarxa corporativa, etc. + +</para><para> + +Finalment es comprovarà la nova font de paquets de la xarxa. Si tot +funciona correctament us preguntarà si ho voleu repetir amb un +altre font de la xarxa. + +</para> + </sect3> + </sect2> diff --git a/ca/boot-new/modules/install.xml b/ca/boot-new/modules/install.xml new file mode 100644 index 000000000..8002a986a --- /dev/null +++ b/ca/boot-new/modules/install.xml @@ -0,0 +1,40 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 --> + + <sect2 id="debconf"> + <title>Preguntes durant la instal·lació del programari</title> + +<para> + +Cada paquet seleccionat utilitzant el <command>tasksel</command> +o l'<command>aptitude</command> es descarrega, es desempaqueta +i s'instal·la de forma ordenada a través dels programes +<command>apt-get</command> i <command>dpkg</command>. Si algun +programa necessita informació addicional de l'usuari, us la preguntarà +en aquesta etapa del procés. Probablement també us interessi estar +pendents de la sortida del procés per identificar error d'instal·lació +(tot i que se us consultarà la confirmació d'errors que impedeixin +la instal·lació d'un paquet). + +</para> + + <sect3 arch="powerpc" id="xserver"> + <title>Paràmetres de configuració del servidor d'X</title> + +<para> + +En els iMacs, i també en alguns Macintosh més vells, el programari +del servidor d'X no calcula correctament els paràmetres de configuració +de vídeo. Durant la configuració dels paràmetres de vídeo haureu de +triar l'opció <guimenuitem>Avançada</guimenuitem>. En el cas del rang de +sincronització horitzontal poseu 59–63. Podeu deixar el valor +predeterminat del rang de refresc vertical. + +</para><para> + +El dispositiu del ratolí s'hauria de definir com +<userinput>/dev/input/mice</userinput>. + +</para> + </sect3> + </sect2> diff --git a/ca/boot-new/modules/mta.xml b/ca/boot-new/modules/mta.xml new file mode 100644 index 000000000..e2e4fddc9 --- /dev/null +++ b/ca/boot-new/modules/mta.xml @@ -0,0 +1,101 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 22935 --> + + <sect2 id="base-config-mta"> + <title>Configurant el vostre agent de transport de correu electrònic</title> + +<para> + +Avui en dia el correu electrònic és una part molt important de la vida +de molta gent i, per tant, no és estrany que Debian us permeti configurar +el vostre sistema de correu en una etapa del procés d'instal·lació. +L'agent de transport de correu estàndard de Debian és +l'<command>exim4</command>, que caracteritza per ser relativament petit, +flexible i fàcil d'aprendre a utilitzar. + +</para><para> + +Us estareu preguntant si és necessari encara que el vostre ordinador +no estigui connectat a cap xarxa. La resposta curta és sí; l'explicació +llarga és que algunes eines del sistema (per exemple <command>cron</command>, +<command>quota</command>, <command>aide</command>, …) us +poden enviar avisos importants via correu electrònic. + +</para><para> + +En la primera pantalla se us presentaran múltiples escenaris +de correu habituals. Trieu el que s'adapti més a les vostres +necessitats: + +</para> + +<variablelist> +<varlistentry> +<term>lloc internet</term> +<listitem><para> + +El vostre sistema està connectat a una xarxa i el vostre correu +s'envia i es rep directament utilitzant SMTP. En les pantalles +següents se us preguntarà algunes qüestions bàsiques com el +nom del correu del vostre ordinador o una llista de dominis +dels quals accepteu o reenvieu correu. + +</para></listitem> +</varlistentry> + +<varlistentry> +<term>correu enviat a través d'un smarthost</term> +<listitem><para> + +En aquest escenari el vostre correu de sortida es reenviarà +a un altre ordinador anomenat <quote>smarthost</quote>, que +assumirà la tasca de l'enviament. L'smarthost acostuma a desar +els correus que us envien, la qual cosa us permet no haver +d'estar connectat de forma permanent. També significa que heu +de baixar el correu de l'smarthost utilitzant programes +com el fetchmail. Aquesta opció és la més idònia per a +usuaris que es connecten a través de la línia telefònica. + +</para></listitem> +</varlistentry> + +<varlistentry> +<term>únicament enviament local</term> +<listitem><para> + +El vostre sistema no està en un xarxa i el correu s'envia o es rep +únicament entre usuaris locals. Encara que no us plantegeu enviar +cap missatge, és una opció molt recomanable, ja que algunes +eines del sistema us podrien enviar avisos (un exemple podria ser +el <quote>Heu excedit la quota de disc</quote>). Aquesta opció +només és recomanable per a usuaris nous, ja que no realitza +més preguntes. + +</para></listitem> +</varlistentry> + +<varlistentry> +<term>temporalment sense configuració</term> +<listitem><para> + +Trieu aquesta opció si esteu absolutament convençut del que +esteu fent. Aquesta opció us deixarà el sistema de correu +desconfigurat — no podreu enviar ni rebre correu +fins que el configureu i probablement perdreu missatges importants +de les eines del sistema. + +</para></listitem> +</varlistentry> +</variablelist> + +<para> + +Si cap del escenaris anteriors satisfà les vostres necessitats o +us cal una configuració més específica, haureu d'editar els fitxers +de configuració del directori <filename>/etc/exim4</filename> un +cop finalitzada la instal·lació. Podreu trobar més informacó sobre +l'<command>exim4</command> al directori +<filename>/usr/share/doc/exim4</filename> + +</para> + </sect2> diff --git a/ca/boot-new/modules/packages.xml b/ca/boot-new/modules/packages.xml new file mode 100644 index 000000000..7cb0b6346 --- /dev/null +++ b/ca/boot-new/modules/packages.xml @@ -0,0 +1,125 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 18767 --> + + <sect2 id="install-packages"> + <title>Instal·lació de paquets</title> + +<para> + +Seguidament se us presentaran diverses configuracions de recopilacions +de programari que ofereix Debian. Sempre podríeu seleccionar el que +voleu instal·lar paquet a paquet, que és l'objectiu +del programa <command>aptitude</command>, descrit meś avall. +Tot i això, aquesta pot ser una tasca molt llarga tenint en comptes els +&num-of-distrib-pkgs; paquets disponibles de Debian! + +</para><para> + +Teniu la possibilitat de primer seleccionar <emphasis>tasques</emphasis>, +i posteriorment afegir paquets individuals. Aquestes tasques intenten +representar diferents de feines o coses que voleu/podeu +fer amb l'ordinador a l'estil de l'<quote>entorn d'escriptori</quote>, +<quote>servidor web</quote> o <quote>servidor d'impressora</quote>. + +<footnote> +<para> + +Per presentar la llista, el <command>base-config</command> executa +el programa <command>tasksel</command>. Per a la selecció manual +de paquets s'utilitza <command>aptitude</command>. Qualsevol d'ells +es pot executar després de la instal·lació per a instal·lar o +suprimir paquets. Si després de la instal·lació esteu buscant un +paquet específic, únicament executeu <userinput>apt-get install +<replaceable>paquet</replaceable></userinput>, on +<replaceable>paquet</replaceable> és el nom del paquet que esteu +buscant. + +</para> +</footnote> + +</para><para> + +Si voleu decidir els paquets a instal·lar un a un, seleccioneu la +<quote>selecció de paquets manual</quote> del <command>tasksel</command>. + +</para><para> + +Un cop seleccionades les tasques, premeu el botó +<guibutton>Ok</guibutton>. En aquest punt, l'<command>aptitude</command> +instal·larà els paquets seleccionats. Recordeu que tot i no haver +seleccionat cap tasca, s'instal·larà qualsevol paquet estàndard, +important o necessari. Aquesta funcionalitat és la mateixa que executar +l'ordre <userinput>tasksel -s</userinput> a la línia d'ordres, i +actualment implica la baixada d'unes 37M d'arxius. Us mostrarà +el nombre de paquets a instal·lar i quants kb de paquets, si són +necessaris, cal baixar. + +</para><para> + +Dels &num-of-distrib-pkgs; paquets disponibles a Debian, l'instal·lador +de tasques només en contempla una petita quantitat. Per a veure més +informació de més paquets, utilitzeu <userinput>apt-cache search +<replaceable>cadena-de-cerca</replaceable></userinput> per a una +cadena (vegeu la pàgina de manual <citerefentry> +<refentrytitle>apt-cache</refentrytitle> <manvolnum>8</manvolnum> +</citerefentry>), o executeu +l'<command>aptitude</command> tal i com es descriu més avall. + +</para> + + <sect3 id="aptitude"> + <title>Selecció avançada de paquets utilitzant l'<command>aptitude</command></title> + +<para> + +L'<command>aptitude</command> és una programa modern de gestió de +paquets. Permet la selecció individual de paquets, conjunts de paquets +que coincideixen en un criteri (per a usuaris avançats) o tasques +senceres. + +</para><para> + +Les combinacions de tecles bàsica són: + +<informaltable> +<tgroup cols="2"> +<thead> +<row> + <entry>Tecla</entry><entry>Acció</entry> +</row> +</thead> + +<tbody> +<row> + <entry><keycap>Amunt</keycap>, <keycap>Avall</keycap></entry> + <entry>Mou la selecció amunt o avall.</entry> +</row><row> + <entry>&enterkey;</entry> + <entry>Obre/col·lapsa/activa un element.</entry> +</row><row> + <entry><keycap>+</keycap></entry> + <entry>Marca el paquet per a la instal·lació.</entry> +</row><row> + <entry><keycap>-</keycap></entry> + <entry>Marca el paquet per a la supressió.</entry> +</row><row> + <entry><keycap>d</keycap></entry> + <entry>Mostra les dependències del paquet.</entry> +</row><row> + <entry><keycap>g</keycap></entry> + <entry>Baixa/instal·la/suprimeix paquets.</entry> +</row><row> + <entry><keycap>q</keycap></entry> + <entry>Surt de la vista actual.</entry> +</row><row> + <entry><keycap>F10</keycap></entry> + <entry>Activa el menú.</entry> +</row> +</tbody></tgroup></informaltable> + +Per a més ordres vegeu l'ajuda en línia utilitzant la tecla +<keycap>?</keycap>. + +</para> + </sect3> + </sect2> diff --git a/ca/boot-new/modules/ppp.xml b/ca/boot-new/modules/ppp.xml new file mode 100644 index 000000000..8c1266530 --- /dev/null +++ b/ca/boot-new/modules/ppp.xml @@ -0,0 +1,116 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 18642 --> + + <sect2 arch="not-s390" id="PPP"> + <title>Configurant el PPP</title> + +<para> + +Si el vostre ordinador no està connectat a una xarxa se us preguntarà +si voleu instal·lar la resta del sistema utilitzant el PPP. + +</para><para> + +Si escolliu configurar PPP en aquest punt, s'executarà un programa +anomenat <command>pppconfig</command>. Aquest programa us ajudarà +a configurar la vostra connexió PPP. <emphasis>Assegureu-vos de que +quan us pregunti el nom de la vostra connexió telefònica l'anomeneu +<userinput>provider</userinput>.</emphasis> + +</para><para> + +Afortunadament, el programa <command>pppconfig</command> us guiarà +a través d'una configuració de la connexió PPP sense excessiu +patiment. Tot i això, si aquest no us servís, seguiu llegint la +secció per a instruccions més detallades. + +</para><para> + +Per configurar el PPP necessitareu conèixer els conceptes bàsics +de la visualització i edició de fitxers en GNU/Linux. Per veure +fitxers podeu utilitzar <command>more</command> i +<command>zmore</command> per a fitxers comprimits amb l'extensió +<userinput>.gz</userinput>. Per exemple, per veure el fitxer +<filename>README.debian.gz</filename> escriviu <userinput>zmore +README.debian.gz</userinput>. El sistema base proporciona un +editor simple d'utilitzar però amb funcionalitats limitades anomenat +<command>nano</command>. Posteriorment probablement us interessarà +instal·lar editors i visualitzadors amb més funcionalitats com el +<command>jed</command>, <command>nvi</command>, <command>less</command> +i <command>emacs</command>. + +</para><para> + +Editeu el fitxer <filename>/etc/ppp/peers/provider</filename> +i substituïu <userinput>/dev/modem</userinput> per +<userinput>/dev/ttyS<replaceable>#</replaceable></userinput> +on <replaceable>#</replaceable> serà el número del vostre +port sèrie. En Linux els ports sèrie s'enumeren des de 0; el +primer port sèrie <phrase arch="i386">(p.e. +<userinput>COM1</userinput>)</phrase> és <filename>/dev/ttyS0</filename> +en Linux. + +<phrase arch="powepc;m68k">En els Macintosh amb ports sèrie, +el port del mòdem és <filename>/dev/ttyS0</filename> i el port +d'impressora és <filename>/dev/ttyS1</filename>.</phrase> + +El següent pas és editar el fitxer +<filename>/etc/chatscripts/provider</filename> i afegir-hi el +número de telèfon del vostre proveïdor, nom d'usuari i +contrasenya. Si us plau no suprimiu la <quote>q</quote> que +precedeix a la contrasenya. Aquesta característica fa que la +contrasenya no aparegui als fitxers registre. + +</para><para> + +Molts proveïdors utilitzen PAP o CHAP per a la seqüència +d'entrada en comptes de l'autenticació en mode de text. D'altres +utilitzen tots dos mètodes. Si el vostre proveïdor necessita +PAP o CHAP, necessitareu seguir un procediment diferent. Comenteu +tot el que estigui sota la línia de marcatge (la que comença per +<quote>ATDT</quote>) al fitxer <filename>/etc/chatscripts/provider</filename>, +modifiqueu el fitxer <filename>/etc/ppp/peers/provider</filename> +tal i com es descriu anteriorment i afegiu <userinput>user +<replaceable>nom</replaceable></userinput> on +<replaceable>nom</replaceable> serà el vostre nom d'usuari del +proveïdor al qual esteu intentant connectar. Seguidament editeu +el fitxer <filename>/etc/ppp/pap-secrets</filename> o el +<filename>/etc/ppp/chap-secrets</filename> i introduïu-hi +la vostra contrasenya. + +</para><para> + +També haureu d'editar el fitxer <filename>/etc/resolv.conf</filename> +i afegir-hi l'adreça d'IP del servidor de noms (DNS) del vostre +proveïdor. Les línies del fitxer <filename>/etc/resolv.conf</filename> +tenen el següent format: <userinput>nomservidor +<replaceable>xxx.xxx.xxx.xxx</replaceable></userinput> on +<replaceable>x</replaceable> correspon al números de l'adreça +d'IP. Opcionalment podeu afegir l'opció <userinput>usepeerdns</userinput> +al fitxer <filename>/etc/ppp/peers/provider</filename>, que +activarà la selecció automàtica dels servidors DNS apropiats, +utilitzant els valors que el servidor remot generalment proporciona. + +</para><para> + +Si no és que el vostre proveïdor té una seqüència diferent a la +de la majoria d'ISP, ja heu acabat la feina! Inicieu una connexió +PPP escrivint <command>pon</command> com a root i monitoritzeu el +procés utilitzant l'eina <command>plog</command>. Per a +desconnectar-vos utilitzeu <command>poff</command>, també com a +root. + +</para><para> + +Per a més informació de com utilitzar el PPP en Debian +llegiu el fitxer <filename>/usr/share/doc/ppp/README.Debian.gz</filename> + +</para><para> + +Per a connexions estàtiques SLIP, necessitareu afegir l'ordre +<userinput>slattach</userinput> (del paquet <classname>net-tools</classname>) +al fitxer <filename>/etc/init.d/network</filename>. L'SLIP dinàmic +necessitarà el paquet <classname>gnudip</classname>. + +</para> + </sect2> diff --git a/ca/boot-new/modules/shadow.xml b/ca/boot-new/modules/shadow.xml new file mode 100644 index 000000000..81f4ba1ff --- /dev/null +++ b/ca/boot-new/modules/shadow.xml @@ -0,0 +1,73 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 18642 --> + + <sect2 id="base-config-users"> + <title>Configurant usuaris i contrasenyes</title> + + <sect3 id="base-config-root"> + <title>Definint la contrasenya de root</title> + +<para> + +El compte <emphasis>root</emphasis> també anomenat +<emphasis>super-usuari</emphasis>; és un tipus d'usuari amb accés +especial que passa qualsevol restricció de seguretat del vostre sistema. +El compte root només s'hauria d'utilitzar per a tasques d'administració +del sistema i durant el mínim de temps possible. + +</para><para> + +Qualsevol contrasenya que creeu hauria de tenir un mínim de 6 +caràcters, combinant majúscules i minúscules i també caràcters +de puntuació. Cal que tingueu una especial cura durant la definició +de la contrasenya de root, ja que aquest compte no té restriccions. +Eviteu paraules del diccionari o utilitzar informació personal +susceptible de ser endevinada. + +</para><para> + +Si algú us diu que necessita la vostra contrasenya de root, +sigueu extremadament curosos. Normalment no hauríeu de donar la +contrasenya de root a ningú si no és que esteu administrant un +sistema amb múltiples administradors. + +</para> + </sect3> + + <sect3 id="make-normal-user"> + <title>Creant un usuari normal</title> + +<para> + +El sistema us preguntarà si voleu crear un compte d'usuari normal. +Aquest compte hauria de ser la vostra principal entrada. +<emphasis>No</emphasis> utilitzeu el compte root per a un us diari +o per accedir personalment. + +</para><para> + +Per què no? Bé, una raó per a evitar l'us dels privilegis de +root seria la facilitat amb la qual podeu danyar el sistema. Un +altre motiu seria la possibilitat de caure en el parany d'executar +un programa <emphasis>cavall de Troia</emphasis> — que és un +programa que utilitza els avantatges del vostre super-usuari per +comprometre la seguretat del vostre sistema d'amagat. Qualsevol +llibre d'administració de sistemes Unix tractarà amb més detall +aquest tema — considereu el llegir-ne un si el concepte us és +nou. + +</para><para> + +Se us preguntarà el nom complet de l'usuari. Seguidament us preguntarà +un nom pel compte d'usuari, normalment el vostre nom o similar serà +suficient, de fet, serà el predeterminat. Finalment us preguntarà la +contrasenya del compte. + +</para><para> + +Si en qualsevol moment posterior a la instal·lació voleu crear un +altre compte, utilitzeu l'ordre <command>adduser</command>. + +</para> + </sect3> + </sect2> diff --git a/ca/boot-new/modules/timezone.xml b/ca/boot-new/modules/timezone.xml new file mode 100644 index 000000000..028170325 --- /dev/null +++ b/ca/boot-new/modules/timezone.xml @@ -0,0 +1,35 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 19108 --> + + <sect2 id="base-config-tz"> + <title>Configurant el fus horari</title> + +<para> + +Després de la pantalla de benvinguda configurareu el fus +horari. Primer heu de seleccionar si el vostre rellotge +del maquinari està definit com hora local o Greenwich Mean Time +(GMT o UTC). L'hora que es mostra a la caixa de diàleg us +hauria d'ajudar a decidir-vos per l'opció correcta. +<phrase arch="m68k;powerpc">Els rellotge del maquinari dels +Macintosh normalment estan definits com hora local. Si voleu +una arrencada dual, seleccioneu l'hora local en comptes de la +GMT.</phrase> +<phrase arch="i386">Els sistemes que (també) executen Dos o +Windows normalment estan definits com hora local. Si voleu una +arrencada dual, seleccioneu l'hora local en comptes de la +GMT.</phrase> + +</para><para> + +En funció de la ubicació seleccionada a l'inici del procés +d'instal·lació, us mostrarà un fus horari o una llista +de fusos horaris relacionats amb la ubicació. Si només es +mostra un fus horari, trieu <guibutton>Sí</guibutton> per +a confirmar-la o trieu <guibutton>No</guibutton> per seleccionar +de la llista completa de fusos horaris. Si es mostra una llista, +seleccioneu-ne el vostre fus horari o seleccioneu Altres per +accedir a la llista completa. + +</para> + </sect2> diff --git a/ca/hardware/hardware-supported.xml b/ca/hardware/hardware-supported.xml new file mode 100644 index 000000000..f3f344f1d --- /dev/null +++ b/ca/hardware/hardware-supported.xml @@ -0,0 +1,337 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 --> + + <sect1 id="hardware-supported"> + <title>Maquinari suportat</title> + +<para> + +Debian no imposa cap requeriment mes enllà dels requeriments que demana +el nucli de Linux i el conjunt de ferramentes GNU. Per això, qualsevol +arquitectura o plataforma que s'haja portat el nucli de Linux, les libc, +<command>gcc</command>, etc. i per la qual s'haja portat Debian, es pot +executar Debian. Visiteu la pàgina dels Ports <ulink url="&url-ports;"></ulink> +per obtenir mes detalls dels sistemes on l'arquitectura &arch-title; +s'ha comprovat amb Debian. + +</para><para> + +Més que intentar descriure totes les configuracions diferents del maquinari +que estan separades per &arch-title;, esta secció conté informació general i +apunts d'on trobar més informació. + +</para> + + <sect2><title>Arquitectures suportades</title> + +<para> + +Debian &release; suporta onze arquitectures principals i diverses variacions +de cada arquitectura conegudes com <quote>sabors</quote>. + +</para><para> + +<informaltable> +<tgroup cols="4"> +<thead> +<row> + <entry>Arquitectura</entry><entry>Nom a Debian</entry> + <entry>Subarquitectura</entry><entry>Sabor</entry> +</row> +</thead> + +<tbody> +<row> + <entry morerows="2">basada en Intel x86</entry> + <entry morerows="2">i386</entry> + <entry morerows="2"></entry> + <entry>vanilla</entry> +</row><row> + <entry>speakup</entry> +</row><row> + <entry>linux26</entry> +</row> + +<row> + <entry morerows="5">Motorola 680x0</entry> + <entry morerows="5">m68k</entry> + <entry>Atari</entry> + <entry>atari</entry> +</row><row> + <entry>Amiga</entry> + <entry>amiga</entry> +</row><row> + <entry>68k Macintosh</entry> + <entry>mac</entry> +</row><row> + <entry morerows="2">VME</entry> + <entry>bvme6000</entry> +</row><row> + <entry>mvme147</entry> +</row><row> + <entry>mvme16x</entry> +</row> + +<row> + <entry>DEC Alpha</entry> + <entry>alpha</entry> + <entry></entry> + <entry></entry> +</row> + +<row> + <entry morerows="1">Sun SPARC</entry> + <entry morerows="1">sparc</entry> + <entry morerows="1"></entry> + <entry>sun4cdm</entry> +</row><row> + <entry>sun4u</entry> +</row> + +<row> + <entry morerows="3">ARM i StrongARM</entry> + <entry morerows="3">arm</entry> + <entry morerows="3"></entry> + <entry>netwinder</entry> +</row><row> + <entry>riscpc</entry> +</row><row> + <entry>shark</entry> +</row><row> + <entry>lart</entry> +</row> + +<row> + <entry morerows="3">IBM/Motorola PowerPC</entry> + <entry morerows="3">powerpc</entry> + <entry>CHRP</entry> + <entry>chrp</entry> +</row><row> + <entry>PowerMac</entry> + <entry>pmac</entry> +</row><row> + <entry>PReP</entry> + <entry>prep</entry> +</row><row> + <entry>APUS</entry> + <entry>apus</entry> +</row> + +<row> + <entry morerows="1">HP PA-RISC</entry> + <entry morerows="1">hppa</entry> + <entry>PA-RISC 1.1</entry> + <entry>32</entry> +</row><row> + <entry>PA-RISC 2.0</entry> + <entry>64</entry> +</row> + +<row> + <entry>basada en Intel ia64</entry> + <entry>ia64</entry> + <entry></entry> + <entry></entry> +</row> + +<row> + <entry morerows="2">MIPS (big endian)</entry> + <entry morerows="2">mips</entry> + <entry morerows="1">SGI Indy/Indigo 2</entry> + <entry>r4k-ip22</entry> +</row><row> + <entry>r5k-ip22</entry> +</row><row> + <entry>Broadcom BCM91250A (SWARM)</entry> + <entry>sb1-swarm-bn</entry> +</row> + +<row> + <entry morerows="3">MIPS (little endian)</entry> + <entry morerows="3">mipsel</entry> + <entry>Cobalt</entry> + <entry>cobalt</entry> +</row><row> + <entry morerows="1">DECstation</entry> + <entry>r4k-kn04</entry> +</row><row> + <entry>r3k-kn02</entry> +</row><row> + <entry>Broadcom BCM91250A (SWARM)</entry> + <entry>sb1-swarm-bn</entry> +</row> + +<row> + <entry morerows="1">IBM S/390</entry> + <entry morerows="1">s390</entry> + <entry>IPL de VM-reader i DASD</entry> + <entry>generic</entry> +</row><row> + <entry>IPL from tape</entry> + <entry>tape</entry> +</row> + +</tbody></tgroup></informaltable> + +</para><para> + +Aquest document cobreix la instal·lació per a l'arquitectura +<emphasis>&arch-title;</emphasis>. Si busqueu informació per qualsevol +altra arquitectura suportada per Debian, pegueu una ullada a les pàgines dels +<ulink url="http://www.debian.org/ports/">ports de Debian</ulink>. + +</para><para condition="new-arch"> + +Aquesta és la primera distribució oficial de &debian; per l'arquitectura + &arch-title;. Ha estat suficientment provada per ser alliberada. +Tanmateix, com que no ha estat exposada (i per tant provada pels usuaris) +a alguna de les arquitectures podeu trobar algunes errades. Utilitzeu el nostre +<ulink url="&url-bts;">Sistema de seguiment de errors</ulink> per informar de +qualsevol problema, assegureu-vos d'anomenar el fet que el error és a la +plataforma &arch-title;. Pot utilitzar-se també si és necessari la +<ulink url="&url-list-subscribe;">llista de correu debian-&architecture;</ulink> + +</para> + + </sect2> + +<!-- supported cpu docs --> +&supported-alpha.xml; +&supported-arm.xml; +&supported-hppa.xml; +&supported-i386.xml; +&supported-ia64.xml; <!-- FIXME: currently missing --> +&supported-m68k.xml; +&supported-mips.xml; +&supported-mipsel.xml; +&supported-powerpc.xml; +&supported-s390.xml; +&supported-sparc.xml; + + <sect2 id="gfx" arch="not-s390"><title>Targeta gràfica</title> + +<para arch="i386"> + +Hauríeu d'utilitzar una interfície de pantalla compatible amb VGA per la +consola del terminal. Quasi totes les targetes gràfiques modernes són +compatibles amb VGA. Estàndards antics com CGA, MDA, o HGA haurien de +funcionar, assumint que no necessiteu suport X11. Fixeu-vos que les X11 +no es fan servir al procés d'instal·lació, com es descriu en aquest document. + +</para><para> + +El suport de les interfícies gràfiques a Debian ve determinat pel suport +subjacent que es troba al sistema x11 de XFree86. La majoria de les +targes de vídeo AGP, PCI i PCIe funcionen a XFree86. Podeu trobar detalls +dels busos, targetes, monitors i dispositius senyaladors a +<ulink url="&url-xfree86;"></ulink>. Debian &release; ve amb la versió +&x11ver; de les XFree86. + +</para><para arch="mips"> + +El sistema de finestres XFree86 X11 tan sols està suportat al SGI Indy. La +placa d'avaluació Broadcom BCM91250A té ranures PCI 3.3v estàndard i suporta +emulació VGA o framebuffer de Linux a un rang seleccionat de targes +gràfiques. Hi ha disponible una <ulink url="&url-bcm91250a-hardware;">llista +de compatibilitats</ulink> pel BCM91250A. + +</para><para arch="mipsel"> + +El sistema de finestres XFree86 X11 tan sols està suportat a alguns models +de DECstation. La placa d'avaluació Broadcom BCM91250A té ranures PCI 3.3v +estàndard i suporta emulació VGA o framebuffer de Linux a un rang seleccionat +de targes gràfiques. Hi ha disponible una +<ulink url="&url-bcm91250a-hardware;">llista de compatibilitats</ulink> +pel BCM91250A. + +</para> + + </sect2> + + <sect2 arch="i386" id="laptops"><title>Ordinadors portàtils</title> +<para> + +També estan suportats els ordinadors portàtils. Moltes vegades contenen +maquinari especialitzat o propietari. Per vore si el vostre ordinador portàtil +funciona correctament amb GNU/Linux, visiteu les +<ulink url="&url-x86-laptop;">pàgines d'ordinadors portàtils amb Linux</ulink> + +</para> + </sect2> + + + <sect2 condition="defaults-smp"> +<title>Processadors múltiples</title> + +<para> + +El suport de processadors múltiples — també anomenat +<quote>symmetric multi-processing</quote> or SMP — està suportat per +aquesta arquitectura. El nucli de la Debian &release; estàndard es va +compilar amb suport SMP. Açò no hauria d'impedir la instal·lació, ja que +els nuclis SMP haurien d'arrancar també a sistemes que no siguin SMP; tan +sols provocarà una mica més d'escalfament. + +</para><para> + +Per optimitzar el nucli d'un sistema amb tan sols una CPU, hauríeu de +reemplaçar el nucli estàndard de Debian. Podeu trobar una discussió de +com fer-ho a <xref linkend="kernel-baking"/>. En aquest moment, +(versió del nucli &kernelversion;) la manera de deshabilitar el SMP és +desseleccionar l'opció <quote>&smp-config-option;</quote> a la secció +<quote>&smp-config-section;</quote> de la configuració del nucli. +</para> + + </sect2> + + + <sect2 condition="supports-smp"> + <title>Processadors múltiples</title> +<para> + +El suport de processadors múltiples — també anomenat +<quote>symmetric multi-processing</quote> or SMP — està suportat per +aquesta arquitectura. Tanmateix, la imatge del nucli de la Debian &release; +estàndard no suporta SMP. Açò no impedeix la instal·lació, ja que el nucli +no SMP estàndard hauria de arrencar també a sistemes SMP; el nucli tan sols +utilitzaria la primera CPU. + +</para><para> + +Per poder aprofitar múltiples processadors, heu de reemplaçar en nucli +estàndard de Debian. Podeu trobar discussions de com fer-ho a +<xref linkend="kernel-baking"/>. En aquest moment, (versió del nucli +&kernelversion;) la forma de habilitar el SMP és seleccionar l'opció +<quote>&smp-config-option;</quote> a la secció +<quote>&smp-config-section;</quote> de la configuració del nucli. + +</para> + </sect2> + + <sect2 condition="supports-smp-sometimes"> + <title>Processadors múltiples</title> +<para> + +El suport de processadors múltiples — també anomenat +<quote>symmetric multi-processing</quote> or SMP — està suportat +per aquesta arquitectura i està suportada per una imatge compilada del +nucli a Debian. Depenent del vostra mitjà d'instal·lació, s'instal·larà o +no el nucli amb capacitats SMP per defecte. Açò no hauria d'impedir la +instal·lació, ja que el nucli no SMP estàndard hauria d'arrencar a sistemes +SMP; simplement el nucli utilitzarà la primera CPU. + +</para><para> + +Per aprofitar els avantatges de tenir múltiples processadors, heu de comprovar +si teniu instal·lat un nucli amb suport SMP, i si no, escollir un paquet amb +un nucli apropiat. + +Podeu també construir el vostre nucli personalitzat amb SMP. Podeu trobar +discussions de com fer-ho a <xref linkend="kernel-baking"/>. En aquest +moment ( versió del nucli &kernelversion;) la manera d'habilitar el smp és +seleccionar <quote>&smp-config-option;</quote> a la secció <quote>&smp-config-section;</quote> +de la configuració del nucli. + +</para> + </sect2> + </sect1> diff --git a/ca/hardware/hardware.xml b/ca/hardware/hardware.xml new file mode 100644 index 000000000..a3eeb5e3c --- /dev/null +++ b/ca/hardware/hardware.xml @@ -0,0 +1,21 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 11648 --> + +<chapter id="hardware-req"> + <title>Requisits del sistema</title> + +<para> + +Aquesta secció conté informació sobre quin maquinari necessitareu +per començar amb Debian. També trobareu enllaços a més informació +referent al maquinari suportat per GNU i Linux. + +</para> + +&hardware-supported.xml; +&installation-media.xml; +&supported-peripherals.xml; +&memory-disk-requirements.xml; +&network-cards.xml; + +</chapter> diff --git a/ca/hardware/installation-media.xml b/ca/hardware/installation-media.xml new file mode 100644 index 000000000..d9b182897 --- /dev/null +++ b/ca/hardware/installation-media.xml @@ -0,0 +1,311 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 untranslated --> + + <sect1 id="installation-media"> + <title>Installation Media</title> + +<para> + +This section will help you determine which different media types you can use to +install Debian. For example, if you have a floppy disk drive on your machine, +it can be used to install Debian. There is a whole chapter devoted media, +<xref linkend="install-methods"/>, which lists the advantages and +disadvantages of each media type. You may want to refer back to this page once +you reach that section. + +</para> + + <sect2 condition="supports-floppy-boot"><title>Floppies</title> +<para> + +In some cases, you'll have to do your first boot from floppy disks. +Generally, all you will need is a +high-density (1440 kilobytes) 3.5 inch floppy drive. + +</para><para arch="powerpc"> + +For CHRP, floppy support is currently broken. + +</para> + </sect2> + + <sect2><title>CD-ROM/DVD-ROM</title> + +<note><para> + +Whenever you see <quote>CD-ROM</quote> in this manual, it applies to both +CD-ROMs and DVD-ROMs, because both technologies are really +the same from the operating system's point of view, except for some very +old nonstandard CD-ROM drives which are neither SCSI nor IDE/ATAPI. + +</para></note><para> + +CD-ROM based installation is supported for some architectures. +On machines which support bootable CD-ROMs, you should be able to do a +completely +<phrase arch="not-s390">floppy-less</phrase> +<phrase arch="s390">tape-less</phrase> +installation. Even if your system doesn't +support booting from a CD-ROM, you can use the CD-ROM in conjunction +with the other techniques to install your system, once you've booted +up by other means; see <xref linkend="boot-installer"/>. + +</para><para arch="i386"> + +Both SCSI and IDE/ATAPI CD-ROMs are supported. In addition, all +non-standard CD interfaces supported by Linux are supported by the +boot disks (such as Mitsumi and Matsushita drives). However, these +models might require special boot parameters or other massaging to get +them to work, and booting off these non-standard interfaces is +unlikely. The <ulink url="&url-cd-howto;">Linux CD-ROM HOWTO</ulink> +contains in-depth information on using CD-ROMs with Linux. + +</para><para arch="i386"> + +USB CD-ROM drives are also supported, as are FireWire devices that +are supported by the ohci1394 and sbp2 drivers. + +</para><para arch="alpha"> + +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 <ulink url="&url-srm-howto;">SRM HOWTO</ulink>. + +</para><para arch="arm"> + +IDE/ATAPI CD-ROMs are supported on all ARM machines. +On RiscPCs, SCSI CD-ROMs are also supported. + +</para><para arch="mips"> + +On SGI machines, booting from CD-ROM requires a SCSI CD-ROM drive +capable of working with a logical blocksize of 512 bytes. Many of the +SCSI CD-DROM drives sold for the PC market do not have this +capability. If your CD-ROM drive has a jumper labeled +<quote>Unix/PC</quote> or <quote>512/2048</quote>, place it in the +<quote>Unix</quote> or <quote>512</quote> position. +To start the install, simply choose the <quote>System installation</quote> +entry in the firmware. The Broadcom BCM91250A supports standard IDE devices, +including CD-ROM drives, but CD images for this platform are currently not +provided because the firmware doesn't recognize CD drives. + +</para><para arch="mipsel"> + +On DECstations, booting from CD-ROM requires a SCSI CD-ROM drive +capable of working with a logical blocksize of 512 bytes. Many of the +SCSI CD-DROM drives sold for the PC market do not have this capability. +If your CD-ROM drive has a jumper labeled <quote>Unix/PC</quote> or +<quote>512/2048</quote>, place it in the <quote>Unix</quote> or +<quote>512</quote> position. + +</para><para arch="mipsel"> + +CD 1 contains the installer for the r3k-kn02 subarchitecture +(the R3000-based DECstations 5000/1xx and 5000/240 as well as +the R3000-based Personal DECstation models), CD 2 the +installer for the r4k-kn04 subarchitecture (the R4x00-based +DECstations 5000/150 and 5000/260 as well as the Personal DECstation +5000/50). + +</para><para arch="mipsel"> + +To boot from CD, issue the command <userinput>boot +<replaceable>#</replaceable>/rz<replaceable>id</replaceable></userinput> +on the firmware prompt, where <replaceable>#</replaceable> is the +number of the TurboChannel device from which to boot (3 on most +DECstations) and <replaceable>id</replaceable> is the SCSI ID of the +CD-ROM drive. If you need to pass additional parameters, they can +optionally be appended with the following syntax: + +</para><para arch="mipsel"> + +<userinput>boot +<replaceable>#</replaceable>/rz<replaceable>id</replaceable> +param1=value1 param2=value2 ...</userinput> + +</para> + </sect2> + + <sect2><title>Hard Disk</title> + +<para> + +Booting the installation system directly from a hard disk is another option +for many architectures. This will require some other operating system +to load the installer onto the hard disk. + +</para><para arch="m68k"> + +In fact, installation from your local disk is the preferred +installation technique for most &architecture; machines. + +</para><para arch="sparc"> + +Although the &arch-title; does not allow booting from SunOS +(Solaris), you can install from a SunOS partition (UFS slices). + +</para> + </sect2> + + <sect2 condition="bootable-usb"><title>USB Memory Stick</title> + +<para> + +Many Debian boxes need their floppy and/or CD-ROM drives only for +setting up the system and for rescue purposes. If you operate some +servers, you will probably already have thought about omitting those +drives and using an USB memory stick for installing and (when +necessary) for recovering the system. This is also useful for small +systems which have no room for unnecessary drives. + +</para> + </sect2> + + <sect2><title>Network</title> + +<para condition="supports-tftp"> + +You can also <emphasis>boot</emphasis> your system over the network. +<phrase arch="mips">This is the preferred installation technique for +Mips.</phrase> + +</para><para condition="supports-nfsroot"> + +Diskless installation, using network booting from a local area network +and NFS-mounting of all local filesystems, is another option. + +</para><para> + +After the operating system kernel is installed, you can install the +rest of your system via any sort of network connection (including +PPP after installation of the base system), via FTP or HTTP. + +</para> + </sect2> + + <sect2><title>Un*x or GNU system</title> + +<para> + +If you are running another Unix-like system, you could use it to install +&debian; without using the &d-i; described in the rest of the +manual. This kind of install may be useful for users with otherwise +unsupported hardware or on hosts which can't afford downtime. If you +are interested in this technique, skip to the <xref +linkend="linux-upgrade"/>. + +</para> + </sect2> + + <sect2><title>Supported Storage Systems</title> + +<para> + +The Debian boot disks contain a kernel which is built to maximize the +number of systems it runs on. Unfortunately, this makes for a larger +kernel, which includes many drivers that won't be used for your +machine (see <xref linkend="kernel-baking"/> to learn how to +build your own kernel). Support for the widest possible range of +devices is desirable in general, to ensure that Debian can be +installed on the widest array of hardware. + +</para><para arch="i386"> + +Generally, the Debian installation system includes support for floppies, +IDE drives, IDE floppies, parallel port IDE devices, SCSI controllers and +drives, USB, and FireWire. The file systems supported include FAT, +Win-32 FAT extensions (VFAT), and NTFS, among others. + +</para><para arch="i386"> + +The disk interfaces that emulate the <quote>AT</quote> hard disk interface +which are often called MFM, RLL, IDE, or ATA are supported. Very old 8 bit +hard disk controllers used in the IBM XT computer are supported only +as a module. SCSI disk controllers from many different manufacturers +are supported. See the +<ulink url="&url-hardware-howto;">Linux Hardware Compatibility HOWTO</ulink> +for more details. + +</para><para arch="m68k"> + +Pretty much all storage systems supported by the Linux kernel are +supported by the Debian installation system. Note that the current +Linux kernel does not support floppies on the Macintosh at all, and +the Debian installation system doesn't support floppies for Amigas. +Also supported on the Atari is the Macintosh HFS system, and AFFS as a +module. Macs support the Atari (FAT) file system. Amigas support the +FAT file system, and HFS as a module. + +</para><para arch="sparc"> + +Any storage system supported by the Linux kernel is also supported by +the boot system. The following SCSI drivers are supported in the default +kernel: + +<itemizedlist> +<listitem><para> + +Sparc ESP + +</para></listitem> +<listitem><para> + +PTI Qlogic,ISP + +</para></listitem> +<listitem><para> + +Adaptec AIC7xxx + +</para></listitem> +<listitem><para> + +NCR and Symbios 53C8XX + +</para></listitem> +</itemizedlist> + +IDE systems (such as the UltraSPARC 5) are also supported. See +<ulink url="&url-sparc-linux-faq;">Linux for SPARC Processors FAQ</ulink> +for more information on SPARC hardware supported by the Linux kernel. + +</para><para arch="alpha"> + +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 +<ulink url="&url-jensen-howto;"></ulink> +for more information on booting the Jensen) + +</para><para arch="powerpc"> + +Any storage system supported by the Linux kernel is also supported by +the boot system. Note that the current Linux kernel does not support +floppies on CHRP systems at all. + +</para><para arch="hppa"> + +Any storage system supported by the Linux kernel is also supported by +the boot system. Note that the current Linux kernel does not support +the floppy drive. + +</para><para arch="mips"> + +Any storage system supported by the Linux kernel is also supported by +the boot system. + +</para><para arch="s390"> + +Any storage system supported by the Linux kernel is also supported by +the boot system. This means that FBA and ECKD DASDs are supported with +the old Linux disk layout (ldl) and the new common S/390 disk layout (cdl). + +</para> + + </sect2> + + </sect1> diff --git a/ca/hardware/memory-disk-requirements.xml b/ca/hardware/memory-disk-requirements.xml new file mode 100644 index 000000000..e048007b8 --- /dev/null +++ b/ca/hardware/memory-disk-requirements.xml @@ -0,0 +1,47 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 untranslated --> + + <sect1 id="memory-disk-requirements"> + <title>Memory and Disk Space Requirements</title> + +<para> + +You must have at least &minimum-memory; of memory and &minimum-fs-size; of hard disk +space. For a minimal console-based system (all standard packages), +250MB is required. If you want to install a reasonable amount of +software, including the X Window System, and some development programs +and libraries, you'll need at least 400MB. For a more or less complete +desktop system, you'll need a few gigabytes. + +</para><para arch="m68k"> + +On the Amiga the size of FastRAM is relevant towards the total memory +requirements. Also, using Zorro cards with 16-bit RAM is not +supported; you'll need 32-bit RAM. The <command>amiboot</command> +program can be used to disable 16-bit RAM; see the +<ulink url="&url-m68k-faq;">Linux/m68k FAQ</ulink>. Recent kernels should +disable 16-bit RAM automatically. + +</para><para arch="m68k"> + +On the Atari, both ST-RAM and Fast RAM (TT-RAM) are used by Linux. +Many users have reported problems running the kernel itself in Fast +RAM, so the Atari bootstrap will place the kernel in ST-RAM. The +minimum requirement for ST-RAM is 2 MB. You will need an additional +12 MB or more of TT-RAM. + +</para><para arch="m68k"> + +On the Macintosh, care should be taken on machines with RAM-based +video (RBV). The RAM segment at physical address 0 is used as screen +memory, making the default load position for the kernel unavailable. +The alternate RAM segment used for kernel and RAMdisk must be at least +4 MB. + +</para><para arch="m68k"> + +<emphasis condition="FIXME">FIXME: is this still true?</emphasis> + +</para> + + </sect1> diff --git a/ca/hardware/network-cards.xml b/ca/hardware/network-cards.xml new file mode 100644 index 000000000..d296a821e --- /dev/null +++ b/ca/hardware/network-cards.xml @@ -0,0 +1,214 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 untranslated --> + + <sect1 id="network-cards"> + <title>Network Connectivity Hardware</title> + +<para arch="i386"> + +<!-- last updated for kernel-image_2.0.36-2 --> + +Most PCI and many older ISA network cards are supported. +Some network interface cards are not supported by most Debian +installation disks, such as AX.25 cards and protocols; +NI16510 EtherBlaster cards; Schneider & Koch G16 cards; +and the Zenith Z-Note built-in network card. Microchannel (MCA) network +cards are not supported by the standard installation system, but see +<ulink url="&url-linux-mca;">Linux on MCA</ulink> for some (old) +instructions. +FDDI networks are also not supported by the installation disks, both +cards and protocols. + +<!-- missing-doc FIXME You can create a custom kernel which supports an +otherwise unsupported card and then substitute in the installer (see +<xref linkend="rescue-replace-kernel"/>). --> + +</para><para arch="i386"> + +As for ISDN, the D-channel protocol for the (old) German 1TR6 is not +supported; Spellcaster BRI ISDN boards are also not supported by the +&d-i;. + +</para> + +<para arch="m68k"> + +Any network interface card (NIC) supported by the Linux kernel should +also be supported by the boot disks. You may need to load your +network driver as a module. Again, see +<ulink url="&url-m68k-faq;"></ulink> for complete details. + +</para> + +<para arch="sparc"> + +The following network interface cards (NICs) are supported from the bootable +kernel directly: + +<itemizedlist> + <listitem><para> + +Sun LANCE + + +</para></listitem> + <listitem><para> + +Sun Happy Meal + + +</para></listitem> +</itemizedlist> + +</para><para arch="sparc"> + +The following network interface cards are supported as modules. They +can be enabled once the drivers are installed during the setup. +However, due to the magic of OpenPROM, you still should be able to +boot from these devices: + +<itemizedlist> + <listitem><para> + +Sun BigMAC + + +</para></listitem> + <listitem><para> + +Sun QuadEthernet + +</para></listitem> + <listitem><para> + +MyriCOM Gigabit Ethernet + +</para></listitem> +</itemizedlist> + +</para><para arch="alpha"> + +Any network interface card (NIC) supported by the Linux kernel should +also be supported by the boot disks. You may need to load your +network driver as a module. + +</para><para arch="powerpc"> + +Any network interface card (NIC) supported by the Linux kernel should +also be supported by the boot disks. You may need to load your +network driver as a module. + +</para><para arch="hppa"> + +Any network interface card (NIC) supported by the Linux kernel should +also be supported by the boot disks. You may need to load your +network driver as a module. + +</para><para arch="ia64"> + +Any network interface card (NIC) supported by the Linux kernel should +also be supported by the boot disks. You may need to load your +network driver as a module. + +</para><para arch="mips"> + +Any network interface card (NIC) supported by the Linux kernel should +also be supported by the boot disks. You may need to load your +network driver as a module. + +</para><para arch="mipsel"> + +Due to kernel limitations only the onboard network interfaces on +DECstations are supported, TurboChannel option network cards currently +do not work. + +</para><para arch="s390"> + +Any network interface card (NIC) supported by the Linux kernel are +also be supported by the boot disks. All network drivers are compiled +as modules so you need to load one first during the initial network +setup. The list of supported network devices is: + +<itemizedlist> + <listitem><para> + +Channel to Channel (CTC) and ESCON connection (real or emulated) + +</para></listitem> + <listitem><para> + +OSA-2 Token Ring/Ethernet and OSA-Express Fast Ethernet (non-QDIO) + +</para></listitem> +<listitem><para> + +Inter-User Communication Vehicle (IUCV) — available for VM guests only + +</para></listitem> +<listitem><para> + +OSA-Express in QDIO mode, HiperSockets and Guest-LANs + +</para></listitem> +</itemizedlist> + +</para> + +<para arch="arm"> + +The following network interface cards are supported directly by the +boot disks on NetWinder and CATS machines: + +<itemizedlist> + <listitem><para> + + PCI-based NE2000 + + +</para></listitem> + <listitem><para> + + DECchip Tulip + +</para></listitem> +</itemizedlist> + +</para><para arch="arm"> + +The following network interface cards are supported directly by the +boot disks on RiscPCs: + +<itemizedlist> + <listitem><para> + + Ether1 + +</para></listitem> + <listitem><para> + + Ether3 + +</para></listitem> + <listitem><para> + + EtherH + +</para></listitem> +</itemizedlist> + +</para><para arch="arm"> + +If your card is mentioned in the lists above, the complete installation +can be carried out from the network with no need for CD-ROMs or floppy +disks. + +</para><para arch="arm"> + +Any other network interface card (NIC) supported by the Linux kernel +should also be supported by the boot disks. You may need to load your +network driver as a module; this means that you will have to install +the operating system kernel and modules using some other media. + +</para> + + </sect1> diff --git a/ca/hardware/supported-peripherals.xml b/ca/hardware/supported-peripherals.xml new file mode 100644 index 000000000..f3ab5db99 --- /dev/null +++ b/ca/hardware/supported-peripherals.xml @@ -0,0 +1,187 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 29467 untranslated --> + + <sect1 id="supported-peripherals"> + <title>Peripherals and Other Hardware</title> +<para arch="not-s390"> + +Linux supports a large variety of hardware devices such as mice, +printers, scanners, PCMCIA and USB devices. However, most of these +devices are not required while installing the system. + +</para><para arch="i386"> + +USB hardware generally works fine, only some +USB keyboards may require additional configuration +(see <xref linkend="usb-keyboard-config"/>). + +</para><para arch="i386"> + +Again, see the +<ulink url="&url-hardware-howto;">Linux Hardware Compatibility HOWTO</ulink> +to determine whether your specific hardware is supported by Linux. + +</para><para arch="s390"> + +Package installations from XPRAM and tape are not supported by this +system. All packages that you want to install need to be available on a +DASD or over the network using NFS, HTTP or FTP. + +</para><para arch="mips"> + +The Broadcom BCM91250A evaluation board offers standard 3.3v 32 bit and 64 +bit PCI slots as well as USB connectors. + +</para><para arch="mipsel"> + +The Broadcom BCM91250A evaluation board offers standard 3.3v 32 bit and 64 +bit PCI slots as well as USB connectors. The Cobalt RaQ has no support for +additional devices but the Qube has one PCI slot. + +</para> +</sect1> + + <sect1 arch="not-s390"><title>Purchasing Hardware Specifically for GNU/Linux</title> + +<para> + +There are several vendors, who ship systems with Debian or other +distributions of GNU/Linux +<ulink url="&url-pre-installed;">pre-installed</ulink>. You might pay more +for the privilege, but it does buy a level of peace of mind, since you can +be sure that the hardware is well-supported by GNU/Linux. + +</para><para arch="m68k"> + +Unfortunately, it's quite rare to find any vendor shipping +new &arch-title; machines at all. + +</para><para arch="i386"> + +If you do have to buy a machine with Windows bundled, carefully read +the software license that comes with Windows; you may be able to +reject the license and obtain a rebate from your vendor. Searching +the Internet for <quote>windows refund</quote> may get you some useful +information to help with that. + +</para><para> + +Whether or not you are purchasing a system with Linux bundled, or even +a used system, it is still important to check that your hardware is +supported by the Linux kernel. Check if your hardware is listed in +the references found above. Let your salesperson (if any) know that +you're shopping for a Linux system. Support Linux-friendly hardware +vendors. + +</para> + + <sect2><title>Avoid Proprietary or Closed Hardware</title> +<para> + +Some hardware manufacturers simply won't tell us how to write drivers +for their hardware. Others won't allow us access to the documentation +without a non-disclosure agreement that would prevent us from +releasing the Linux source code. + +</para><para arch="m68k"> + +Another example is the proprietary hardware in the older +Macintosh line. In fact, no specifications or documentation have ever +been released for any Macintosh hardware, most notably the ADB +controller (used by the mouse and keyboard), the floppy controller, +and all acceleration and CLUT manipulation of the video hardware +(though we do now support CLUT manipulation on nearly all internal +video chips). In a nutshell, this explains why the Macintosh Linux +port lags behind other Linux ports. + +</para><para> + +Since we haven't been granted access to the documentation on these +devices, they simply won't work under Linux. You can help by asking +the manufacturers of such hardware to release the documentation. If +enough people ask, they will realize that the free software community +is an important market. + +</para> +</sect2> + + + <sect2 arch="i386"><title>Windows-specific Hardware</title> +<para> + +A disturbing trend is the proliferation of Windows-specific modems and +printers. In some cases these are specially designed to be operated by +the Microsoft Windows operating system and bear the legend <quote>WinModem</quote> +or <quote>Made especially for Windows-based computers</quote>. This +is generally done by removing the embedded processors of the hardware +and shifting the work they do over to a Windows driver that is run by +your computer's main CPU. This strategy makes the hardware less +expensive, but the savings are often <emphasis>not</emphasis> passed on to the +user and this hardware may even be more expensive than equivalent +devices that retain their embedded intelligence. + +</para><para> + +You should avoid Windows-specific hardware for two reasons. The first +is that the manufacturers do not generally make the resources +available to write a Linux driver. Generally, the hardware and +software interface to the device is proprietary, and documentation is +not available without a non-disclosure agreement, if it is available +at all. This precludes its being used for free software, since free +software writers disclose the source code of their programs. The +second reason is that when devices like these have had their embedded +processors removed, the operating system must perform the work of the +embedded processors, often at <emphasis>real-time</emphasis> priority, +and thus the CPU is not available to run your programs while it is +driving these devices. Since the typical Windows user does not +multi-process as intensively as a Linux user, the manufacturers hope +that the Windows user simply won't notice the burden this hardware +places on their CPU. However, any multi-processing operating system, +even Windows 2000 or XP, suffers from degraded performance when +peripheral manufacturers skimp on the embedded processing power of +their hardware. + +</para><para> + +You can help this situation by encouraging these manufacturers to +release the documentation and other resources necessary for us to +program their hardware, but the best strategy is simply to avoid this +sort of hardware until it is listed as working in the +<ulink url="&url-hardware-howto;">Linux Hardware Compatibility HOWTO</ulink>. + +</para> +</sect2> + + + <sect2 id="Parity-RAM"> + <title>Fake or <quote>Virtual</quote> Parity RAM</title> +<para> + +If you ask for Parity RAM in a computer store, you'll probably get +<emphasis>virtual parity</emphasis> memory modules instead of +<emphasis>true parity</emphasis> ones. Virtual parity SIMMs can often +(but not always) be distinguished because they only have one more chip +than an equivalent non-parity SIMM, and that one extra chip is smaller +than all the others. Virtual-parity SIMMs work exactly like non-parity +memory. They can't tell you when you have a single-bit RAM error the +way true-parity SIMMs do in a motherboard that implements +parity. Don't ever pay more for a virtual-parity SIMM than a +non-parity one. Do expect to pay a little more for true-parity SIMMs, +because you are actually buying one extra bit of memory for every 8 +bits. + +</para><para> + +If you want complete information on &arch-title; RAM issues, and what +is the best RAM to buy, see the +<ulink url="&url-pc-hw-faq;">PC Hardware FAQ</ulink>. + +</para><para arch="alpha"> + +Most, if not all, Alpha systems require true-parity RAM. + +</para> + + </sect2> + + </sect1> diff --git a/ca/hardware/supported/alpha.xml b/ca/hardware/supported/alpha.xml new file mode 100644 index 000000000..02e0ad4be --- /dev/null +++ b/ca/hardware/supported/alpha.xml @@ -0,0 +1,457 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 untranslated --> + + + <sect2 arch="alpha" id="alpha-cpus"><title>CPU, Main Boards, and Video Support</title> +<para> + +Complete information regarding supported DEC Alphas can be found at +<ulink url="&url-alpha-howto;">Linux Alpha HOWTO</ulink>. The +purpose of this section is to describe the systems supported +by the boot disks. + +</para><para> + +Alpha machines are subdivided into different system types because there +are a number of generations of motherboard and supporting chipsets. +Different systems (<quote>sub-architectures</quote>) often have radically +different engineering and capabilities. Therefore, the process of +installing and, more to the point, booting, can vary from system to system. + +</para><para> + +The following table lists the system types supported by the Debian +installation system. The table also indicates the <emphasis>code +name</emphasis> for these system types. You'll need to know this code +name when you actually begin the installation process: + +</para> + +<informaltable> +<tgroup cols="4"> +<colspec colname="c1"/> +<colspec colname="c2"/> +<colspec colname="c3"/> +<colspec colname="c4"/> +<thead> +<row> + <entry namest="c1" nameend="c2">Hardware Type</entry> + <entry>Aliases</entry><entry>MILO image</entry> +</row> +</thead> + +<tbody> +<row> + <entry morerows="3">ALCOR</entry> + <entry>AlphaStation 500 5/266.300</entry> + <entry>Maverick</entry> + <entry>alcor</entry> +</row><row> + <entry>AlphaStation 500 5/333...500</entry> + <entry>Bret</entry> + <entry>alcor</entry> +</row><row> + <entry>AlphaStation 600/266...300</entry> + <entry>Alcor</entry> + <entry>alcor</entry> +</row><row> + <entry>AlphaStation 600/300...433</entry> + <entry>XLT</entry> + <entry>xlt</entry> +</row> + +<row> + <entry>BOOK1</entry> + <entry>AlphaBook1 (laptop)</entry> + <entry>Alphabook1/Burns</entry> + <entry>book1</entry> +</row> + +<row> + <entry morerows="7">AVANTI</entry> + <entry>AlphaStation 200 4/100...166</entry> + <entry>Mustang</entry> + <entry>avanti</entry> +</row><row> + <entry>AlphaStation 200 4/233</entry> + <entry>Mustang+</entry> + <entry>avanti</entry> +</row><row> + <entry>AlphaStation 205 4/133...333</entry> + <entry>LX3</entry> + <entry>avanti</entry> +</row><row> + <entry>AlphaStation 250 4/300</entry> + <entry>M3+</entry> + <entry>avanti</entry> +</row><row> + <entry>AlphaStation 255 4/133...333</entry> + <entry>LX3+</entry> + <entry>avanti</entry> +</row><row> + <entry>AlphaStation 300 4/266</entry> + <entry>Melmac</entry> + <entry>avanti</entry> +</row><row> + <entry>AlphaStation 400 4/166</entry> + <entry>Chinet</entry> + <entry>avanti</entry> +</row><row> + <entry>AlphaStation 400 4/233...300</entry> + <entry>Avanti</entry> + <entry>avanti</entry> +</row> + +<row> + <entry morerows="3">EB164</entry> + <entry>AlphaPC164</entry> + <entry>PC164</entry> + <entry>pc164</entry> +</row><row> + <entry>AlphaPC164-LX</entry> + <entry>LX164</entry> + <entry>lx164</entry> +</row><row> + <entry>AlphaPC164-SX</entry> + <entry>SX164</entry> + <entry>sx164</entry> +</row><row> + <entry>EB164</entry> + <entry>EB164</entry> + <entry>eb164</entry> +</row> + +<row> + <entry morerows="2">EB64+</entry> + <entry>AlphaPC64</entry> + <entry>Cabriolet</entry> + <entry>cabriolet</entry> +</row><row> + <entry>AlphaPCI64</entry> + <entry>Cabriolet</entry> + <entry>cabriolet</entry> +</row><row> + <entry>EB64+</entry> + <entry>EB64+</entry> + <entry>eb64p</entry> +</row> + +<row> + <entry morerows="1">EB66</entry> + <entry>EB66</entry> + <entry>EB66</entry> + <entry>eb66</entry> +</row><row> + <entry>EB66+</entry> + <entry>EB66+</entry> + <entry>eb66p</entry> +</row> + +<row> + <entry morerows="2">JENSEN</entry> + <entry>DEC 2000 Model 300(S)</entry> + <entry>Jensen</entry> + <entry>N/A</entry> +</row><row> + <entry>DEC 2000 Model 500</entry> + <entry>Culzen</entry> + <entry>N/A</entry> +</row><row> + <entry>DECpc 150</entry> + <entry>Jensen</entry> + <entry>N/A</entry> +</row> + +<row> + <entry morerows="7">MIATA</entry> + <entry>Personal WorkStation 433a</entry> + <entry>Miata</entry> + <entry>miata</entry> +</row><row> + <entry>Personal WorkStation 433au</entry> + <entry>Miata</entry> + <entry>miata</entry> +</row><row> + <entry>Personal WorkStation 466au</entry> + <entry>Miata</entry> + <entry>miata</entry> +</row><row> + <entry>Personal WorkStation 500a</entry> + <entry>Miata</entry> + <entry>miata</entry> +</row><row> + <entry>Personal WorkStation 500au</entry> + <entry>Miata</entry> + <entry>miata</entry> +</row><row> + <entry>Personal WorkStation 550au</entry> + <entry>Miata</entry> + <entry>miata</entry> +</row><row> + <entry>Personal WorkStation 600a</entry> + <entry>Miata</entry> + <entry>miata</entry> +</row><row> + <entry>Personal WorkStation 600au</entry> + <entry>Miata</entry> + <entry>miata</entry> +</row> + +<row> + <entry morerows="3">MIKASA</entry> + <entry>AlphaServer 1000 4/200</entry> + <entry>Mikasa</entry> + <entry>mikasa</entry> +</row><row> + <entry>AlphaServer 1000 4/233..266</entry> + <entry>Mikasa+</entry> + <entry>mikasa</entry> +</row><row> + <entry>AlphaServer 1000 5/300</entry> + <entry>Mikasa-Pinnacle</entry> + <entry>mikasa</entry> +</row><row> + <entry>AlphaServer 1000 5/300</entry> + <entry>Mikasa-Primo</entry> + <entry>mikasa</entry> +</row> + +<row> + <entry morerows="1">NAUTILUS</entry> + <entry>UP1000</entry> + <entry>Nautilus</entry> + <entry>N/A</entry> +</row><row> + <entry>UP1100</entry> + <entry>Galaxy-Train/Nautilus Jr.</entry> + <entry>N/A</entry> +</row> + +<row> + <entry morerows="1">NONAME</entry> + <entry>AXPpci33</entry> + <entry>Noname</entry> + <entry>noname</entry> +</row><row> + <entry>UDB</entry> + <entry>Multia</entry> + <entry>noname</entry> +</row> + +<row> + <entry morerows="6">NORITAKE</entry> + <entry>AlphaServer 1000A 4/233...266</entry> + <entry>Noritake</entry> + <entry>N/A</entry> +</row><row> + <entry>AlphaServer 1000A 5/300</entry> + <entry>Noritake-Pinnacle</entry> + <entry>N/A</entry> +</row><row> + <entry>AlphaServer 1000A 5/333...500</entry> + <entry>Noritake-Primo</entry> + <entry>N/A</entry> +</row><row> + <entry>AlphaServer 800 5/333...500</entry> + <entry>Corelle</entry> + <entry>N/A</entry> +</row><row> + <entry>AlphaStation 600 A</entry> + <entry>Alcor-Primo</entry> + <entry>N/A</entry> +</row><row> + <entry>Digital Server 3300</entry> + <entry>Corelle</entry> + <entry>N/A</entry> +</row><row> + <entry>Digital Server 3300R</entry> + <entry>Corelle</entry> + <entry>N/A</entry> +</row> + +<row> + <entry>PLATFORM 2000</entry> + <entry>P2K</entry> + <entry>P2K</entry> + <entry>p2k</entry> +</row> + +<row> + <entry morerows="4">RAWHIDE</entry> + <entry>AlphaServer 1200 5/xxx</entry> + <entry>Tincup/DaVinci</entry> + <entry>N/A</entry> +</row><row> + <entry>AlphaServer 4000 5/xxx</entry> + <entry>Wrangler/Durango</entry> + <entry>N/A</entry> +</row><row> + <entry>AlphaServer 4100 5/xxx</entry> + <entry>Dodge</entry> + <entry>N/A</entry> +</row><row> + <entry>Digital Server 5300</entry> + <entry>Tincup/DaVinci</entry> + <entry>N/A</entry> +</row><row> + <entry>Digital Server 7300</entry> + <entry>Dodge</entry> + <entry>N/A</entry> +</row> + +<row> + <entry morerows="5">RUFFIAN</entry> + <entry>DeskStation AlphaPC164-UX</entry> + <entry>Ruffian</entry> + <entry>ruffian</entry> +</row><row> + <entry>DeskStation RPL164-2</entry> + <entry>Ruffian</entry> + <entry>ruffian</entry> +</row><row> + <entry>DeskStation RPL164-4</entry> + <entry>Ruffian</entry> + <entry>ruffian</entry> +</row><row> + <entry>DeskStation RPX164-2</entry> + <entry>Ruffian</entry> + <entry>ruffian</entry> +</row><row> + <entry>DeskStation RPX164-4</entry> + <entry>Ruffian</entry> + <entry>ruffian</entry> +</row><row> + <entry>Samsung AlphaPC164-BX</entry> + <entry>Ruffian</entry> + <entry>ruffian</entry> +</row> + +<row> + <entry morerows="3">SABLE</entry> + <entry>AlphaServer 2000 4/xxx</entry> + <entry>Demi-Sable</entry> + <entry>N/A</entry> +</row><row> + <entry>AlphaServer 2000 5/xxx</entry> + <entry>Demi-Gamma-Sable</entry> + <entry>N/A</entry> +</row><row> + <entry>AlphaServer 2100 4/xxx</entry> + <entry>Sable</entry> + <entry>N/A</entry> +</row><row> + <entry>AlphaServer 2100 5/xxx</entry> + <entry>Gamma-Sable</entry> + <entry>N/A</entry> +</row> + +<row> + <entry>TAKARA</entry> + <entry>21164 PICMG SBC</entry> + <entry>Takara</entry> + <entry>takara</entry> +</row> + +<row> + <entry morerows="3">TITAN</entry> + <entry>AlphaServer DS15</entry> + <entry>HyperBrick2</entry> + <entry>N/A</entry> +</row><row> + <entry>AlphaServer DS25</entry> + <entry>Granite</entry> + <entry>N/A</entry> +</row><row> + <entry>AlphaServer ES45</entry> + <entry>Privateer</entry> + <entry>N/A</entry> +</row><row> + <entry>UNKNOWN</entry> + <entry>Yukon</entry> + <entry>N/A</entry> +</row> + +<row> + <entry morerows="12">TSUNAMI</entry> + <entry>AlphaServer DS10</entry> + <entry>Webbrick</entry> + <entry>N/A</entry> +</row><row> + <entry>AlphaServer DS10L</entry> + <entry>Slate</entry> + <entry>N/A</entry> +</row><row> + <entry>AlphaServer DS20</entry> + <entry>Catamaran/Goldrush</entry> + <entry>N/A</entry> +</row><row> + <entry>AlphaServer DS20E</entry> + <entry>Goldrack</entry> + <entry>N/A</entry> +</row><row> + <entry>AlphaServer DS20L</entry> + <entry>Shark</entry> + <entry>N/A</entry> +</row><row> + <entry>AlphaServer ES40</entry> + <entry>Clipper</entry> + <entry>N/A</entry> +</row><row> + <entry>DP264</entry> + <entry>DP264</entry> + <entry>N/A</entry> +</row><row> + <entry>SMARTengine 21264 PCI/ISA SBC</entry> + <entry>Eiger</entry> + <entry>N/A</entry> +</row><row> + <entry>UNKNOWN</entry> + <entry>Warhol</entry> + <entry>N/A</entry> +</row><row> + <entry>UNKNOWN</entry> + <entry>Windjammer</entry> + <entry>N/A</entry> +</row><row> + <entry>UP2000</entry> + <entry>Swordfish</entry> + <entry>N/A</entry> +</row><row> + <entry>XP1000</entry> + <entry>Monet/Brisbane</entry> + <entry>N/A</entry> +</row><row> + <entry>XP900</entry> + <entry>Webbrick</entry> + <entry>N/A</entry> +</row> + +<row> + <entry morerows="1">WILDFIRE</entry> + <entry>AlphaServer GS160</entry> + <entry>Wildfire</entry> + <entry>N/A</entry> +</row><row> + <entry>AlphaServer GS320</entry> + <entry>Wildfire</entry> + <entry>N/A</entry> +</row> + +<row> + <entry>XL</entry> + <entry>XL-233...266</entry> + <entry>XL</entry> + <entry>xl</entry> +</row> + +</tbody></tgroup></informaltable> + +<para> + +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. + +</para> + </sect2> diff --git a/ca/hardware/supported/arm.xml b/ca/hardware/supported/arm.xml new file mode 100644 index 000000000..9ae4bef4e --- /dev/null +++ b/ca/hardware/supported/arm.xml @@ -0,0 +1,95 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 25809 untranslated --> + + + <sect2 arch="arm"><title>CPU, Main Boards, and Video Support</title> + +<para> + +Each distinct ARM architecture requires its own kernel. Because of +this the standard Debian distribution only supports installation on +a number of the most common systems. The Debian userland however may be used by <emphasis>any</emphasis> ARM CPU including xscale. + +</para> + +<para> + +Most ARM CPUs may be run in either endian mode (big or little). However, +almost every current system implementation uses little-endian mode. +Debian currently only supports little-endian ARM systems. + +</para> + +<para> + +The commonly supported systems are + +<variablelist> +<varlistentry> +<term>Netwinder</term> +<listitem><para> + +This is actually the name for the group of machines +based upon the StrongARM 110 CPU and Intel 21285 Northbridge. It +comprises of machines like: Netwinder (possibly one of the most common ARM +boxes), CATS (also known as the EB110ATX), EBSA 285 and Compaq +personal server (cps, aka skiff). + +</para></listitem> +</varlistentry> + +<varlistentry> +<term>Bast</term> +<listitem><para> + +This is a modern ARM 920 board with a 266MHz Samsung +processor. It has integrated IDE, USB, Serial, Parallel, audio, video, +flash and two ethernet ports. This system has a good bootloader which +is also found on the CATS and Riscstation systems. + +</para></listitem> +</varlistentry> + +<varlistentry> +<term>RiscPC</term> +<listitem><para> + +This machine is the oldest supported hardware: it was released +in 1994. It has RISC OS in ROM, Linux can be booted from that OS using +linloader. The RiscPC has a modular CPU card and typically has a 30MHz +610, 40MHz 710 or 233MHz Strongarm 110 CPU fitted. The mainboard has +integrated IDE, SVGA video, parallel port, single serial port, PS/2 +keyboard and proprietary mouse port. The proprietary module expansion +bus allows for up to eight expansion cards to be fitted depending on +configuration, several of these modules have Linux drivers. + +</para></listitem> +</varlistentry> + +<varlistentry> +<term>Riscstation</term> +<listitem><para> + +This is an inexpensive 56MHz 7500FE based machine with +integrated video, IDE, PS/2 keyboard and mouse and two serial +ports. Its lack of processing power was made up for by its price. It +may be found in two configurations one with RISC OS and one with a +simple bootloader. + +</para></listitem> +</varlistentry> + +<varlistentry> +<term>LART</term> +<listitem><para> + +This is a modular open hardware platform intended to be built +by enthusiasts. To be useful to install Debian it requires its KSB +expansion board. + +</para></listitem> +</varlistentry> +</variablelist> + +</para> + </sect2> diff --git a/ca/hardware/supported/hppa.xml b/ca/hardware/supported/hppa.xml new file mode 100644 index 000000000..746060492 --- /dev/null +++ b/ca/hardware/supported/hppa.xml @@ -0,0 +1,17 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 11648 --> + + + <sect2 arch="hppa"><title>Suport de CPU, plaques mare i vídeo</title> +<para> + +Hi ha dos sabors de <emphasis>&architecture;</emphasis> principals suportats: +PA-RISC 1.1 i PA-RISC 2.0. L'arquitectura PA-RISC 1.1 està encarada a +processadors de 32 bits, mentre que l'arquitectura 2.0 està encarada als +processadors de 64 bits. Alguns sistemes poden fer servir qualsevol dels +nuclis. En els dos casos, l'espai d'usuari és de 32 bits. Hi ha la possibilitat +en el futur d'un espai d'usuari de 64 bits. + +</para> + </sect2> + diff --git a/ca/hardware/supported/i386.xml b/ca/hardware/supported/i386.xml new file mode 100644 index 000000000..54605f5ac --- /dev/null +++ b/ca/hardware/supported/i386.xml @@ -0,0 +1,37 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 11648 --> + + + <sect2 arch="i386"><title>Suport de CPU, plaques mare i vídeo</title> +<para> + +La informació completa pertinent als dispositius suportats es pot trobar al +<ulink url="&url-hardware-howto;">COM ES FA de compatibilitat de maquinari de Linux</ulink>. +Aquesta secció merament destaca els detalls principals. + +</para> + + <sect3><title>CPU</title> +<para> + +Casi tots els processadors basats en x86 estan suportats; això inclou +també processadors AMD i VIA (anterior Cyrix). També estan suportats els +nous processadors com els Athlon XP i Intel P4 Xeon. No obstant, Linux +<emphasis>no</emphasis> funcionarà en processadors 286 o anteriors. + +</para> + </sect3> + + <sect3 id="bus"><title>Bus E/S</title> +<para> + +El bus del sistema és part de la placa mare, permetent a la CPU +comunicar-se amb els perifèrics tals com els dispositius d'emmagatzemament. +El vostre ordinador ha d'usar ISA, EISA, PCI, l'arquitectura Microchannel +(MCA, fet servir en la línia PS/2 d'IBM) o VESA Local Bus (VLB, alguns cops +anomenat el bus VL). + +</para> + </sect3> + </sect2> + diff --git a/ca/hardware/supported/ia64.xml b/ca/hardware/supported/ia64.xml new file mode 100644 index 000000000..5ab979f43 --- /dev/null +++ b/ca/hardware/supported/ia64.xml @@ -0,0 +1,3 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 11648 --> + diff --git a/ca/hardware/supported/m68k.xml b/ca/hardware/supported/m68k.xml new file mode 100644 index 000000000..4de0bc0f8 --- /dev/null +++ b/ca/hardware/supported/m68k.xml @@ -0,0 +1,39 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 untranslated --> + + <sect2 arch="m68k"><title>CPU, Main Boards, and Video Support</title> +<para> + +Complete information concerning supported M68000 based +(<emphasis>&architecture;</emphasis>) systems can be found at the +<ulink url="&url-m68k-faq;">Linux/m68k FAQ</ulink>. This section merely +outlines the basics. + +</para><para> + +The &architecture; port of Linux runs on any 680x0 with a PMMU (Paged +Memory Management Unit) and a FPU (floating-point unit). This +includes the 68020 with an external 68851 PMMU, the 68030, and better, +and excludes the <quote>EC</quote> line of 680x0 processors. See the +<ulink url="&url-m68k-faq;">Linux/m68k FAQ</ulink> for complete details. + +</para><para> + +There are four major flavors of supported +<emphasis>&architecture;</emphasis> flavors: Amiga, Atari, Macintosh +and VME machines. Amiga and Atari were the first two systems to which +Linux was ported; in keeping, they are also the two most +well-supported Debian ports. The Macintosh line is supported +incompletely, both by Debian and by the Linux kernel; see +<ulink url="&url-m68k-mac;">Linux m68k for Macintosh</ulink> for project +status and supported hardware. The BVM and Motorola single board +VMEbus computers are the most recent addition to the list of machines +supported by Debian. Ports to other &architecture; architectures, +such as the Sun3 architecture and NeXT black box, are underway but not +yet supported by Debian. + +</para> + </sect2> + + + diff --git a/ca/hardware/supported/mips.xml b/ca/hardware/supported/mips.xml new file mode 100644 index 000000000..7ea1a2bf7 --- /dev/null +++ b/ca/hardware/supported/mips.xml @@ -0,0 +1,52 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 22939 untranslated --> + + + <sect2 arch="mips"><title>CPU, Main Boards, and Video Support</title> +<para> + +Debian on &arch-title; currently supports two subarchitectures: + +<itemizedlist> +<listitem><para> + +SGI IP22: this platform includes the SGI machines Indy, Indigo 2 and +Challenge S. Since these machines are very similar, whenever this document +refers to the SGI Indy, the Indigo 2 and Challenge S are meant as well. + +</para></listitem> +<listitem><para> + +Broadcom BCM91250A (SWARM): this is an ATX form factor evaluation board from +Broadcom based on their SiByte processor family. + +</para></listitem> +</itemizedlist> + +Complete information regarding supported mips/mipsel machines can be found +at the <ulink url="&url-linux-mips;">Linux-MIPS homepage</ulink>. In the +following, only the systems supported by the Debian installer will be +covered. If you are looking for support for other subarchitectures, please +contact the <ulink url="&url-list-subscribe;"> +debian-&architecture; mailing list</ulink>. + +</para> + + <sect3><title>CPU</title> +<para> + +On SGI IP22, SGI Indy, Indigo 2 and Challenge S with R4000, R4400, R4600 and R5000 +processors are supported by the Debian installation system on big endian +MIPS. The Broadcom BCM91250A evaluation board comes with an SB1250 chip with +two SB-1 cores which are supported in SMP mode by this installer. + +</para><para> + +Some MIPS machines can be operated in both big and little endian mode. For +little endian MIPS, please read the documentation for the mipsel +architecture. + +</para> + </sect3> + </sect2> + diff --git a/ca/hardware/supported/mipsel.xml b/ca/hardware/supported/mipsel.xml new file mode 100644 index 000000000..63d5a5bc1 --- /dev/null +++ b/ca/hardware/supported/mipsel.xml @@ -0,0 +1,149 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 untranslated --> + + + <sect2 arch="mipsel"><title>CPU, Main Boards, and Video Support</title> +<para> + +Debian on &arch-title; currently supports three subarchitectures: + +<itemizedlist> +<listitem><para> + +DECstation: various models of the DECstation are supported. + +</para></listitem> +<listitem><para> + +Cobalt Microserver: only MIPS based Cobalt machines are covered here. +This included the Cobalt Qube, RaQ, Qube2 and RaQ2, and the Gateway +Microserver. + +</para></listitem> +<listitem><para> + +Broadcom BCM91250A (SWARM): this is an ATX form factor evaluation board from +Broadcom based on their SiByte processor family. + +</para></listitem> +</itemizedlist> + +Complete information regarding supported mips/mipsel machines can be found +at the <ulink url="&url-linux-mips;">Linux-MIPS homepage</ulink>. In the +following, only the systems supported by the Debian installer will be +covered. If you are looking for support for other subarchitectures, please +contact the <ulink url="&url-list-subscribe;"> +debian-&architecture; mailing list</ulink>. + +</para> + + <sect3><title>CPU/Machine types</title> + +<para> + +Currently only DECstations with R3000 and R4000/R4400 CPUs are +supported by the Debian installation system on little endian MIPS. +The Debian installation system works on the following machines: + +</para><para> + +<informaltable> +<tgroup cols="4"> +<thead> +<row> + <entry>System Type</entry><entry>CPU</entry><entry>Code-name</entry> + <entry>Debian subarchitecture</entry> +</row> +</thead> + +<tbody> +<row> + <entry>DECstation 5000/1xx</entry> + <entry>R3000</entry> + <entry>3MIN</entry> + <entry>r3k-kn02</entry> +</row><row> + <entry>DECstation 5000/150</entry> + <entry>R4000</entry> + <entry>3MIN</entry> + <entry>r4k-kn04</entry> +</row><row> + <entry>DECstation 5000/200</entry> + <entry>R3000</entry> + <entry>3MAX</entry> + <entry>r3k-kn02</entry> +</row><row> + <entry>DECstation 5000/240</entry> + <entry>R3000</entry> + <entry>3MAX+</entry> + <entry>r3k-kn02</entry> +</row><row> + <entry>DECstation 5000/260</entry> + <entry>R4400</entry> + <entry>3MAX+</entry> + <entry>r4k-kn04</entry> +</row><row> + <entry>Personal DECstation 5000/xx</entry> + <entry>R3000</entry> + <entry>Maxine</entry> + <entry>r3k-kn02</entry> +</row><row> + <entry>Personal DECstation 5000/50</entry> + <entry>R4000</entry> + <entry>Maxine</entry> + <entry>r4k-kn04</entry> +</row> +</tbody></tgroup></informaltable> + +</para><para> + +All Cobalt machines are supported which have a serial console (which is +needed for the installation). + +</para><para> + +The Broadcom BCM91250A evaluation board comes with an SB1250 chip with two +SB-1 cores which are supported in SMP mode by this installer. + +</para> + </sect3> + + <sect3><title>Supported console options</title> +<para> + +Serial console is available on all supported DECstations (9600 bps, +8N1). For using serial console, you have to boot the installer image +with the <literal>console=ttyS</literal><replaceable>x</replaceable> kernel +parameter (with <replaceable>x</replaceable> being the number +of the serial port you have your terminal connected to — usually +<literal>2</literal>, but <literal>0</literal> for the Personal DECstations). +On 3MIN and 3MAX+ (DECstation 5000/1xx, 5000/240 and 5000/260) local console +is available with the PMAG-BA and the PMAGB-B graphics options. + +</para><para> + +If you have a Linux system to use as serial terminal, an easy way +is to run <command>cu</command><footnote> + +<para> +In Woody this command was part of the <classname>uucp</classname> package, +but in later releases it is available as a separate package. +</para> + +</footnote> on it. Example: + +<informalexample><screen> +$ cu -l /dev/ttyS1 -s 9600 +</screen></informalexample> + +where the option <literal>-l</literal> (line) sets the serial port to use +and <literal>-s</literal> (speed) sets the speed for the connection (9600 +bits per second). + +</para><para> + +Both Cobalt and Broadcom BCM91250A use 115200 bps. + +</para> + </sect3> + </sect2> diff --git a/ca/hardware/supported/powerpc.xml b/ca/hardware/supported/powerpc.xml new file mode 100644 index 000000000..fbc4b2f8b --- /dev/null +++ b/ca/hardware/supported/powerpc.xml @@ -0,0 +1,381 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 30269 untranslated --> + + + <sect2 arch="powerpc"><title>CPU, Main Boards, and Video Support</title> +<para> + +There are four major supported <emphasis>&architecture;</emphasis> +subarchitectures: PMac (Power-Macintosh), PReP, APUS (Amiga Power-UP +System), and CHRP machines. Each subarchitecture has its own boot +methods. In addition, there are four different kernel flavours, +supporting different CPU variants. + +</para><para> + +Ports to other <emphasis>&architecture;</emphasis> architectures, such +as the Be-Box and MBX architecture, are underway but not yet supported +by Debian. We may have a 64-bit port in the future. + +</para> + + <sect3><title>Kernel Flavours</title> + +<para> + +There are four flavours of the powerpc kernel in Debian, based on the +CPU type: + +<variablelist> +<varlistentry> +<term>powerpc</term> +<listitem><para> + +Most systems use this kernel flavour, which supports the PowerPC 601, +603, 604, 740, 750, and 7400 processors. All Apple Power Macintosh +systems up to and including the G4 use one of these processors. + +</para></listitem> +</varlistentry> + +<varlistentry> +<term>power3</term> +<listitem><para> + +The POWER3 processor is used in older IBM 64-bit server systems: known +models include the IntelliStation POWER Model 265, the pSeries 610 and +640, and the RS/6000 7044-170, 7043-260, and 7044-270. + +</para></listitem> +</varlistentry> + +<varlistentry> +<term>power4</term> +<listitem><para> + +The POWER4 processor is used in more recent IBM 64-bit server systems: +known models include the pSeries 615, 630, 650, 655, 670, and 690. + +</para><para> + +The Apple G5 is also based on the POWER4 architecture, and uses this +kernel flavour. + +</para></listitem> +</varlistentry> + +<varlistentry> +<term>apus</term> +<listitem><para> + +This kernel flavour supports the Amiga Power-UP System. + +</para></listitem> +</varlistentry> +</variablelist> + +</para> + + </sect3> + + <sect3><title>Power Macintosh (pmac) subarchitecture</title> + +<para> + +Apple (and briefly a few other manufacturers — Power Computing, for +example) makes a series of Macintosh computers based on the PowerPC +processor. For purposes of architecture support, they are categorized +as NuBus, OldWorld PCI, and NewWorld. + +</para><para> + +Macintosh computers using the 680x0 series of processors are not in +the PowerPC family but are instead m68k machines. Those models start +with <quote>Mac II</quote> or have a 3-digit model number such as Centris 650 +or Quadra 950. Apple's pre-iMac PowerPC model numbers have four digits. + +</para><para> + +NuBus systems are not currently supported by debian/powerpc. The +monolithic Linux/PPC kernel architecture does not have support for +these machines; instead, one must use the MkLinux Mach microkernel, +which Debian does not yet support. These include the following: + +<itemizedlist> +<listitem><para> + +Power Macintosh 6100, 7100, 8100 + +</para></listitem> +<listitem><para> + +Performa 5200, 6200, 6300 + +</para></listitem> +<listitem><para> + +Powerbook 1400, 2300, and 5300 + +</para></listitem> +<listitem><para> + +Workgroup Server 6150, 8150, 9150 + +</para></listitem> +</itemizedlist> + +A linux kernel for these machines and limited support is available at +<ulink url="http://nubus-pmac.sourceforge.net/"></ulink> + +</para><para> + +OldWorld systems are most Power Macintoshes with a floppy drive and a +PCI bus. Most 603, 603e, 604, and 604e based Power Macintoshes are +OldWorld machines. The beige colored G3 systems are also OldWorld. + +</para><para> + +The so called NewWorld PowerMacs are any PowerMacs in translucent +colored plastic cases. That includes all iMacs, iBooks, G4 systems, +blue colored G3 systems, and most PowerBooks manufactured in and after +1999. The NewWorld PowerMacs are also known for using the <quote>ROM in +RAM</quote> system for MacOS, and were manufactured from mid-1998 onwards. + +</para><para> + +Specifications for Apple hardware are available at +<ulink url="http://www.info.apple.com/support/applespec.html">AppleSpec</ulink>, +and, for older hardware, +<ulink url="http://www.info.apple.com/support/applespec.legacy/index.html">AppleSpec Legacy</ulink>. + +</para><para> + +<informaltable> +<tgroup cols="3"> +<colspec colname="c1"/> +<colspec colname="c2"/> +<colspec colname="c3"/> +<thead> +<row> + <entry namest="c1" nameend="c2">Model Name/Number</entry> + <entry>Generation</entry> +</row> +</thead> + +<tbody> +<row> + <entry morerows="22">Apple</entry> + <entry>iMac Bondi Blue, 5 Flavors, Slot Loading</entry> + <entry>NewWorld</entry> +</row><row> + <entry>iMac Summer 2000, Early 2001</entry> + <entry>NewWorld</entry> +</row><row> + <entry>iMac G5</entry> + <entry>NewWorld</entry> +</row><row> + <entry>iBook, iBook SE, iBook Dual USB</entry> + <entry>NewWorld</entry> +</row><row> + <entry>iBook2</entry> + <entry>NewWorld</entry> +</row><row> + <entry>iBook G4</entry> + <entry>NewWorld</entry> +</row><row> + <entry>Power Macintosh Blue and White (B&W) G3</entry> + <entry>NewWorld</entry> +</row><row> + <entry>Power Macintosh G4 PCI, AGP, Cube</entry> + <entry>NewWorld</entry> +</row><row> + <entry>Power Macintosh G4 Gigabit Ethernet</entry> + <entry>NewWorld</entry> +</row><row> + <entry>Power Macintosh G4 Digital Audio, Quicksilver</entry> + <entry>NewWorld</entry> +</row><row> + <entry>Power Macintosh G5</entry> + <entry>NewWorld</entry> +</row><row> + <entry>PowerBook G3 FireWire Pismo (2000)</entry> + <entry>NewWorld</entry> +</row><row> + <entry>PowerBook G3 Lombard (1999)</entry> + <entry>NewWorld</entry> +</row><row> + <entry>PowerBook G4 Titanium</entry> + <entry>NewWorld</entry> +</row><row> + <entry>PowerBook G4 Aluminum</entry> + <entry>NewWorld</entry> +</row><row> + <entry>Xserve G5</entry> + <entry>NewWorld</entry> +</row><row> + <entry>Performa 4400, 54xx, 5500</entry> + <entry>OldWorld</entry> +</row><row> + <entry>Performa 6360, 6400, 6500</entry> + <entry>OldWorld</entry> +</row><row> + <entry>Power Macintosh 4400, 5400</entry> + <entry>OldWorld</entry> +</row><row> + <entry>Power Macintosh 7200, 7300, 7500, 7600</entry> + <entry>OldWorld</entry> +</row><row> + <entry>Power Macintosh 8200, 8500, 8600</entry> + <entry>OldWorld</entry> +</row><row> + <entry>Power Macintosh 9500, 9600</entry> + <entry>OldWorld</entry> +</row><row> + <entry>Power Macintosh (Beige) G3 Minitower</entry> + <entry>OldWorld</entry> +</row><row> + <entry>Power Macintosh (Beige) Desktop, All-in-One</entry> + <entry>OldWorld</entry> +</row><row> + <entry>PowerBook 2400, 3400, 3500</entry> + <entry>OldWorld</entry> +</row><row> + <entry>PowerBook G3 Wallstreet (1998)</entry> + <entry>OldWorld</entry> +</row><row> + <entry>Twentieth Anniversary Macintosh</entry> + <entry>OldWorld</entry> +</row><row> + <entry>Workgroup Server 7250, 7350, 8550, 9650, G3</entry> + <entry>OldWorld</entry> +</row> + +<row> + <entry morerows="1">Power Computing</entry> + <entry>PowerBase, PowerTower / Pro, PowerWave</entry> + <entry>OldWorld</entry> +</row><row> + <entry>PowerCenter / Pro, PowerCurve</entry> + <entry>OldWorld</entry> +</row> + +<row> + <entry>UMAX</entry> + <entry>C500, C600, J700, S900</entry> + <entry>OldWorld</entry> +</row> + +<row> + <entry>APS</entry> + <entry>APS Tech M*Power 604e/2000</entry> + <entry>OldWorld</entry> +</row> + +<row> + <entry>Motorola</entry> + <entry>Starmax 3000, 4000, 5000, 5500</entry> + <entry>OldWorld</entry> +</row> +</tbody></tgroup></informaltable> + +</para> + + </sect3> + + <sect3><title>PReP subarchitecture</title> + +<para> + +<informaltable> +<tgroup cols="2"> +<colspec colname="c1"/> +<colspec colname="c2"/> +<thead> +<row> + <entry namest="c1" nameend="c2">Model Name/Number</entry> +</row> +</thead> + +<tbody> +<row> + <entry morerows="4">Motorola</entry> + <entry>Firepower, PowerStack Series E, PowerStack II</entry> +</row><row> + <entry>MPC 7xx, 8xx</entry> +</row><row> + <entry>MTX, MTX+</entry> +</row><row> + <entry>MVME2300(SC)/24xx/26xx/27xx/36xx/46xx</entry> +</row><row> + <entry>MCP(N)750</entry> +</row> + +<row> + <entry morerows="3">IBM RS/6000</entry> + <entry>40P, 43P</entry> +</row><row> + <entry>Power 830/850/860 (6070, 6050)</entry> +</row><row> + <entry>6030, 7025, 7043</entry> +</row><row> + <entry>p640</entry> +</row> +</tbody></tgroup></informaltable> + +</para> + + </sect3> + + <sect3><title>CHRP subarchitecture</title> + +<para> + +<informaltable> +<tgroup cols="2"> +<colspec colname="c1"/> +<colspec colname="c2"/> +<thead> +<row> + <entry namest="c1" nameend="c2">Model Name/Number</entry> +</row> +</thead> + +<tbody> +<row> + <entry>IBM RS/6000</entry> + <entry>B50, 43P-150, 44P</entry> +</row> +<row> + <entry>Genesi</entry> + <entry>Pegasos I, Pegasos II</entry> +</row> +</tbody></tgroup></informaltable> + +</para> + + </sect3> + + <sect3><title>APUS subarchitecture</title> + +<para> + +<informaltable> +<tgroup cols="2"> +<colspec colname="c1"/> +<colspec colname="c2"/> +<thead> +<row> + <entry namest="c1" nameend="c2">Model Name/Number</entry> +</row> +</thead> + +<tbody> +<row> + <entry>Amiga Power-UP Systems (APUS)</entry> + <entry>A1200, A3000, A4000</entry> +</row> +</tbody></tgroup></informaltable> + +</para> + </sect3> + </sect2> diff --git a/ca/hardware/supported/s390.xml b/ca/hardware/supported/s390.xml new file mode 100644 index 000000000..5d9f6d558 --- /dev/null +++ b/ca/hardware/supported/s390.xml @@ -0,0 +1,21 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 --> + + + <sect2 arch="s390"><title>Tipus de maquines S/390 i zSeries</title> +<para> + +La informació completa referent al suport de maquines S/390 i zSeries es pot +trobar al llibre vermell d'IBM +<ulink url="http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf"> +Linux per a servidors IBM eServer zSeries i S/390: Distribucions</ulink> en +el capítol 2.1 o a la +<ulink url="http://oss.software.ibm.com/developerworks/opensource/linux390/documentation-2.4.shtml">plana web de detalls</ulink> a +<ulink url="http://oss.software.ibm.com/developerworks/opensource/linux390/index.shtml">developerWorks</ulink>. +Resumint, G5, Multiprise 3000, G6 i tots els zSeries estan completament +suportats; les maquines Multiprise 2000, G3 i G4 estan suportades amb +emulació de coma flotant IEEE i per tant rendiment degradat. + +</para> + </sect2> + diff --git a/ca/hardware/supported/sparc.xml b/ca/hardware/supported/sparc.xml new file mode 100644 index 000000000..d00c6b252 --- /dev/null +++ b/ca/hardware/supported/sparc.xml @@ -0,0 +1,82 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 untranslated --> + + + <sect2 arch="sparc" id="sparc-cpus"><title>CPU, Main Boards, and Video Support</title> +<para> + +Currently the <emphasis>&architecture;</emphasis> port supports +several types of Sparc systems. The most common identifiers for Sparc +systems are sun4, sun4c, sun4m, sun4d and sun4u. Currently we do not +support very old sun4 hardware. However, the other systems are +supported. Sun4d has been tested the least of these, so expect +possible problems with regard to the kernel stability. Sun4c and +Sun4m, the most common of the older Sparc hardware, includes such +systems as SparcStation 1, 1+, IPC, IPX and the SparcStation LX, 5, +10, and 20, respectively. The UltraSPARC class systems fall under the +sun4u identifier, and are supported using the sun4u set of install +images. Some systems that fall under these supported identifiers are +known to not be supported. Known unsupported systems are the AP1000 +multicomputer and the Tadpole Sparcbook 1. See the +<ulink url="&url-sparc-linux-faq;">Linux for SPARCProcessors FAQ</ulink> +for complete information. + +</para> + + <sect3><title>Memory Configuration</title> +<para> + +Some older Sun workstations, notably the Sun IPX and Sun IPC have +memory banks located at fixed locations in physical memory. Thus if +the banks are not filled gaps will exist in the physical memory space. +The Linux installation requires a contiguous memory block into which +to load the kernel and the initial RAMdisk. If this is not available a +<quote>Data Access Exception</quote> will result. + +</para><para> + +Thus you must configure the memory so that the lowest memory block is +contiguous for at least 8Mb. In the IPX and IPC cited above, memory banks +are mapped in at 16Mb boundaries. In effect this means that you must have +a sufficiently large SIMM in bank zero to hold the kernel and RAMdisk. +In this case 4Mb is <emphasis>not</emphasis> sufficient. + +</para><para> + +Example: +In a Sun IPX you have a 16Mb SIMM and a 4Mb SIMM. There are four +SIMM banks (0,1,2,3). [Bank zero is that furthest away from the SBUS +connectors]. You must therefore install the 16Mb SIMM in bank 0; it is +then recommended to install the 4Mb SIMM in bank 2. + +</para> + </sect3> + + <sect3><title>Graphics Configuration</title> +<para> + +Especially in the case of older Sun workstations, it is very common +for there to be an onboard framebuffer which has been superseded (for +example the bwtwo on a sun IPC), and an SBUS card containing a later +probably accelerated buffer is then plugged in to an SBUS slot. +Under Solaris/SunOS this causes no problems because both cards are +initialized. + +</para><para> + +However with Linux this can cause a problem, in that the boot PROM +monitor may display its output on this additional card; however the +linux kernel boot messages may then be directed to the original on +board framebuffer, leaving <emphasis>no</emphasis> error messages on +the screen, with the machine apparently stuck loading the RAMdisk. + +</para><para> + +To avoid this problem, connect the monitor (if required) to the video +card in the lowest numbered SBUS slot (on motherboard card counts +as below external slots). Alternatively it is possible to use a serial +console. + +</para> + </sect3> + </sect2> diff --git a/ca/howto/installation-howto.xml b/ca/howto/installation-howto.xml new file mode 100644 index 000000000..9cf68d79c --- /dev/null +++ b/ca/howto/installation-howto.xml @@ -0,0 +1,365 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 29046 --> + +<appendix id="installation-howto"> +<title>Com Instal·lar</title> + +<para> + +Aquest document descriu com instal·lar &debian; &releasename; per +&arch-title; (<quote>&architecture;</quote>) amb el nou &d-i;. És un passeig +ràpid pel procés d'instal·lació el qual hauria de contenir tota la informació +que necessiteu per la majoria d'instal·lacions. Quan sigui necessària mes +informació us remetrem a explicacions més detallades a la +<link linkend="debian_installation_guide">Guia d'Instal·lació de &debian; +</link>. + +</para> + + <sect1 id="howto-preliminaries"> + <title>Preliminars</title> +<para> + +<phrase condition="unofficial-build"> +El debian-installer es troba encara en fase beta. +</phrase> +Si trobeu errors al llarg de la instal·lació per favor dirigiu-vos a la +<xref linkend="submit-bug" /> per consultar la informació de com +informar-ho. Si teniu preguntes les quals no estan respostes a aquest +document, per favor informeu a la llista de correu debian-boot +(&email-debian-boot-list;) o pregunteu al IRC (#debian-boot a la xarxa +de freenode). + +</para> + </sect1> + + <sect1 id="howto-getting-images"> + <title>Arrancant l'instal·lador</title> +<para> + +<phrase condition="unofficial-build"> +Podeu trobar alguns enllaços ràpids a les imatges dels CD a +la <ulink url="&url-d-i;"> +pàgina inicial de &d-i; </ulink>. +</phrase> +L'equip de debian-cd construeix imatges dels CD que utilitzen el &d-i; a la +<ulink url="&url-debian-cd;">pàgina de Debian CD</ulink>. +Si voleu trobar més informació d'on descarregar-se els CDs, mireu +<xref linkend="official-cdrom" />. + +</para><para> + +Alguns mètodes d'instal·lació requereixen d'altres imatges a +mes a mes de les imatges dels CDs. +<phrase condition="unofficial-build"> +La <ulink url="&url-d-i;">pàgina inicial de &d-i;</ulink> teniu enllaços +a altres imatges. +</phrase> +A la <xref linkend="where-files" /> s'explica com podeu trobar imatges a +rèpliques de Debian + +</para><para> + +Les subseccions de baix us donaran detalls de quines imatges necessiteu +aconseguir per cada mecanisme d'instal·lació. + +</para> + + <sect2 id="howto-getting-images-cdrom"> + <title>CDROM</title> + +<para> + +Hi ha dues imatges de CD diferents per netinst que poden ser utilitzades +per instal·lar &releasename; amb &d-i;. Aquestes imatges s'han fet amb la +intenció d'arrancar des del CD i instal·lar els paquets addicionals fent ús +d'una xarxa, d'ahí el nom netinst. La diferència entre les dues imatges +és que a la imatge completa estan inclosos els paquets base, mentre que +si esteu utilitzant la imatge «tarja de negocis» haureu de descarregar-los +de la web. Si voleu, podeu aconseguir una imatge completa del CD a la qual +no necessiteu la xarxa per instal·lar. Tan sols necessiteu el primer CD del +conjunt de CDs de Debian. + +</para><para> + +Descarregueu la que preferiu i graveu-la a un CD. +<phrase arch="i386">Per arrancar el CD, necessiteu canviar la configuració de +la vostra BIOS, com s'explica a la <xref linkend="bios-setup" />.</phrase> +<phrase arch="powerpc"> +Per arrancar un PowerMac des de CD, premeu la tecla <keycap>c</keycap> mentre +esteu arrancant. Mireu <xref linkend="boot-cd" /> per altres maners d'arrancar +des de CD.</phrase> + +</para> + </sect2> + + <sect2 condition="supports-floppy-boot" id="howto-getting-images-floppy"> + <title>Disquet</title> +<para> + +Si no podeu arrancar des de CD, podeu descarregar les imatges dels disquets +Debian. Necessiteu les imatges <filename>floppy/boot.img</filename>, +<filename>floppy/root.img</filename> i possiblement un dels disquets +amb controladors. + +</para><para> + +El disquet d'arrancada és el que conté la imatge <filename>boot.img</filename>. +Quan arranqueu aquest disquet, us suggerirà que inseriu un segon disquet +— feu ús del que conté <filename>root.img</filename> dins. + +</para><para> + +Si esteu planejant fer la instal·lació per xarxa, normalment necessitareu +el disquet <filename>floppy/net-drivers.img</filename>, el qual conté +controladors addicionals per moltes targes de xarxa i suport per PCMCIA. + +</para><para> + +Si teniu un CD, però no podeu arrancar des d'ell, aleshores arranqueu des +de disquet i feu ús de <filename>floppy/cd-drivers.img</filename> com disc +de controladors, i completeu la instal·lació fent ús del CD. + +</para><para> + +Els disquets son un dels mitjans menys segurs, així que prepareu-vos per un +munt de fallades als disquets (mireu la <xref linkend="unreliable-floppies" />). +Cada fitxer <filename>.img</filename> que heu descarregat va a un únic +disquet; podeu fer ús de la comanda dd per escriure'l a /def/fd0 o +equivalents (podeu trobar més detalls a la <xref linkend="create-floppy" />). +Com que teniu més d'un disquet, no seria mala idea etiquetar-los. + +</para> + </sect2> + + <sect2 condition="bootable-usb" id="howto-getting-images-usb"> + <title>Clau de memòria USB</title> +<para> + +També podeu instal·lar des de una clau de memòria USB. Per exemple un +clauer USB pot ser un mitjà d'instal·lació de Debian molt còmode per portar +per tot arreu. + +</para><para> + +La forma més fàcil de preparar el vostre llapis de memòria USB és +descarregar el fitxer <filename>hd-media/boot.img.gz</filename>, i +utilitzar gunzip per extraure la imatge de 128 MB d'aquest fitxer. +Escriviu aquesta imatge directament al vostre llapis de memòria, que ha de +ser com a mínim de 128 mb de tamany. Per suposat, açò destruirà tot el que +hi havia al llapis de memòria. Després mounteu el llapis de memòria, que +ara ha de tenir un sistema de fitxers FAT. Ara, descarregueu una imatge del +CD netinst de Debian, i copieu el fitxer al llapis de memòria; qualsevol +nom és bo sempre que acabe amb <literal>.iso</literal>. + +</para><para> + +Hi ha formes més flexibles per preparar un llapis de memòria per fer ús del +debian-installer, i també és possible que funcioni amb llapis de memòria +mes petits. Per més detalls, podeu mirar <xref linkend="boot-usb-files" />. + +</para><para arch="i386"> + +Algunes BIOS poden arrancar directament de dispositius USB, i d'altres no. +Heu de configurar la vostra BIOS per que arranque des del «disc extraïble» o +de «USB-ZIP» per fer que arranque des del dispositiu USB. En cas contrari, +podeu arrancar des d'un disquet i utilitzar el USB per acabar la resta de la +instal·lació. Podeu trobar ajudes i detalls a <xref linkend="usb-boot" />. + +</para><para arch="powerpc"> + +Arrancar un sistema Macintosh des de un dispositiu d'emmagatzemament USB +requereix usar manualment l'Open Firmware. Per a instrucciones, vegeu +<xref linkend="usb-boot" />. + +</para> + </sect2> + + <sect2 id="howto-getting-images-netboot"> + <title>Arrancant de la xarxa</title> +<para> + +També és possible arrancar el &d-i; completament de la xarxa. Hi ha +diferents mètodes per arrancar per xarxa depenent de la teva arquitectura +i configuració d'arranc de xarxa. Els fitxers que podeu trobar a +<filename>netboot/</filename> poden utilitzar-se per arrancar de la +xarxa el &d-i;. + +</para><para arch="i386"> + +La manera més fàcil per configurar-ho és probablement l'arranc amb PXE. +Desempaqueteu amb el tar el fitxer <filename>netboot/pxeboot.tar.gz</filename> +a <filename>/var/lib/tftpboot</filename> o a un altre lloc al vostre servidor +tftp. Configureu el vostre servidor DHCP per que envie als clients el fitxer +<filename>/pxelinux.0</filename>, i amb una mica de sort tot anirà be. +Si voleu instruccions més detallades, mireu <xref linkend="install-tftp" />. + +</para> + </sect2> + + <sect2 id="howto-getting-images-hard-disk"> + <title>Arrancant des del disc dur</title> + +<para> + +Es possible arrancar l'instal·lador sense fer ús d'un dispositiu extraïble, +tan sols tenint un disc dur, que pot contenir un sistema operatiu diferent. +Descarregueu <filename>hd-media/initrd.gz</filename>, +<filename>hd-media/vmlinuz</filename>, i la imatge d'un CD de Debian al +directori principal del vostre disc dur. Assegureu-vos de que la imatge del +CD ha de tenir el nom acabat amb <literal>.iso</literal>. Ara tan sols us +queda arrancar el linux amb el initrd. +<phrase arch="i386"> +A la <xref linkend="boot-initrd" /> s'explica com fer-ho. +</phrase> + +</para> + </sect2> + </sect1> + + <sect1 id="howto-installation"> +<title>Instal·lació</title> + +<para> + +Una vegada l'instal·lador ha començat, voreu la pantalla de benvinguda. +Premeu &enterkey; per arrancar, o llegiu les instruccions per seleccionar +altres mètodes i paràmetres (vegeu la <xref linkend="boot-parms" />). +<phrase arch="i386"> +<phrase condition="sarge"> +Si voleu utilitzar el nucli 2.6, escriviu <userinput>linux26</userinput> +a la petició «<prompt>boot:</prompt>». +</phrase> +<phrase condition="etch"> +Si voleu utilitzar el nucli 2.4, escriviu <userinput>install24</userinput> +a la petició «<prompt>boot:</prompt>». +</phrase> +<footnote><para> + +<phrase condition="sarge"> +Podeu disposar del nucli 2.6 per la majoria dels mètodes d'arrancada, però +no quan arranqueu de disquet. +</phrase> +<phrase condition="etch"> +El nucli 2.6 és el predeterminat per la majoria dels mètodes d'arrancada, +però no està disponible quan arranqueu de disquet. +</phrase> + +</para></footnote> +</phrase> + +</para><para> + +Al cap d'una mica se ús demanarà que seleccioneu el vostre idioma. Feu ús de +les fletxes per seleccionar un idioma i premeu &enterkey; per continuar. +A continuació se ús preguntarà el vostre país, amb les eleccions possibles +s'inclourà una llista de països on es parla el vostre idioma. Si no es troba +a la llista curta, també disposeu d'una llista amb tots els països del mon. + +</para><para> + +És possible que necessiteu confirmar el vostre mapa de teclat. Escolliu el +valor per defecte a no ser que en conegueu un millor. + +</para><para> + +Ara seieu mentre el debian-installer detecta el vostre maquinari, i +carrega la resta de components des del CD, disquet, USB, etc. + +</para><para> + +Després l'instal·lador intentarà detectar el vostre maquinari de xarxa i +configurar la xarxa mitjançant DHCP. Si no esteu en xarxa o no disposeu de +DHCP, aleshores podreu configurar manualment la xarxa. + +</para><para> + +Aquest és el moment de particionar els vostres discs. Primer tindreu +l'oportunitat de triar si particionar automàticament el disc sencer, o +l'espai buit. Es el que us recomaneu si sou nous usuaris o si teniu pressa, +en altre cas, trieu «manual» des del menú. + +</para><para arch="i386"> + +Si teniu una partició amb DOS o Windows que voleu conservar, +aneu amb molt de compte amb la partició automàtica. Si seleccioneu +particionar manualment, podeu fer ús de l'instal·lador per canviar el +tamany d'una partició FAT o NTFS tan sols seleccionant la partició i +especificat el nou tamany. + +</para><para> + +A la pròxima pantalla voreu la vostra taula de particions, com seran +formatades les particions i on es muntaran. Seleccioneu una partició per +modificar-la o esborrar-la. Si particioneu automàticament, tan sols podreu +escollir <guimenuitem>Acabar el particionament</guimenuitem> al menú, per +utilitzar les opcions que heu triat. Recordeu d'assignar al menys una +partició d'intercanvi i muntar una partició a <filename>/</filename>. Podeu +trobar més informació sobre particionat a <xref linkend="partitioning" />. + +</para><para> + +Ara el &d-i; formata les vostres particions i comença a instal·lar el +sistema base, la qual cosa tardarà una mica. Desprès s'instal·larà el nucli. + +</para><para> + +L'últim pas és la instal·lació del gestor d'arrancada. Si l'instal·lador +detecta altres sistemes operatius al vostre ordinador, els afegirà al menú +d'arrancada i ho farà saber. +<phrase arch="i386">Per defecte el GRUB s'instal·larà al sector d'arranc del +vostre primer disc dur, cosa que normalment serà una bona elecció. Podreu +canviar-lo i instal·lar-lo a un altre lloc si ho desitgeu. +</phrase> + +</para><para> + +El &d-i; ús dirà que la instal·lació ha acabat. Traieu el cdrom o qualsevol +mitjà d'arrancada que hajau utilitzat i premeu &enterkey; per rearrancar la +màquina. Deuria arrancar al següent pas del procés d'instal·lació, com +s'explica al <xref linkend="boot-new" />. + +</para><para> + +Si necessiteu més informació del procés d'instal·lació, vegeu el +<xref linkend="d-i-intro" />. + +</para> + </sect1> + + <sect1 id="howto-installation-report"> + <title>Envieu un informe de la instal·lació</title> +<para> + +Si heu fet la instal·lació amb èxit fent ús del &d-i;, +preneu-vos una mica de temps per enviar-nos un informe. Hi ha una +plantilla anomenada <filename>install-report.template</filename> al +directori <filename>/root</filename> del sistema recentment instal·lat. +Ompliu-lo i envieu-lo com una errada del paquet +<classname>installation-reports</classname>, tal com s'explica a la +<xref linkend="submit-bug" />. + +</para><para> + +Si no heu aconseguit completar la configuració base o heu trobat algun +altre problema, probablement heu trobat una errada al debian-installer. +Per poder millorar el instal·lador, és necessari que el coneguem, així +que per favor preneu-vos un temps per informar-lo. Podeu fer ús d'un +informe d'instal·lació per informar-lo; si la instal·lació falla completament, +mireu la <xref linkend="problem-report" />. + +</para> + </sect1> + + <sect1 id="howto-installation-finally"> + <title>I finalment...</title> +<para> + +Esperem que la vostra instal·lació de Debian sigui satisfactòria i que +trobeu Debian d'utilitat. Ara és possible que vulgueu llegir +<xref linkend="post-install" />. + +</para> + </sect1> +</appendix> + diff --git a/ca/install-methods/automatic-install.xml b/ca/install-methods/automatic-install.xml new file mode 100644 index 000000000..9b258fa47 --- /dev/null +++ b/ca/install-methods/automatic-install.xml @@ -0,0 +1,116 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 --> + + <sect1 id="automatic-install"> + <title>Instal·lació automàtica</title> +<para> + +Si heu d'instal·lar a molts ordinadors, és possible fer instal·lacions +completament automatitzades. Els paquets dels que es disposa a Debian +per fer-ho són: +<classname>fai</classname> (que utilitza un servidor d'instal·lació), +<classname>replicator</classname>, +<classname>systemimager</classname>, +<classname>autoinstall</classname>, i el mateix instal·lador de Debian. + +</para> + + <sect2 id="preseed"> + <title>Instal·lació automàtica utilitzant l'instal·lador de Debian</title> +<para> + +L'instal·lador de Debian suporta l'automatització de la instal·lació +utilitzant fitxers de preconfiguració. Es pot carregar un fitxer de +preconfiguració des de la xarxa o des d'un mitjà extraïble, i el que +fa és emplenar amb respostes totes les preguntes fetes al procés +d'instal·lació. + +</para><para> + +Malgrat que els diàlegs utilitzats pel &d-i; es poden precarregar +utilitzant aquest mètode, hi ha algunes excepcions. Podeu (re)particionar +un disc complet o utilitzar l'espai buit a un disc, però no és possible +utilitzar les particions que ja teniu. En aquest moment no podeu +precarregar les opcions de configuració de RAID i LVM. +<phrase condition="sarge">A més a més, amb l'excepció dels mòduls dels +controladors de xarxa, no és possible preconfigurar els paràmetres dels +mòduls del nucli. +</phrase> + +</para><para> + +El fitxer de preconfiguració està en el format que utilitza l'ordre +«debconf-set-selections». Podeu trobar un exemple ben documentat i funcional +que podeu editar a <xref linkend="example-preseed"/>. + +</para><para> + +D'altra banda, una forma d'aconseguir un fitxer amb una llista completa amb +tots els valors que poden ser precarregats, és fer una instal·lació +manual, i aleshores utilitzar <filename>debconf-get-selections</filename>, +del paquet <classname>debconf-utils</classname>, per abocar les bases de +dades de debconf i cdebconf que està a /var/log/debian-installer/cdebconf +a un sol fitxer: + +<informalexample><screen> +$ debconf-get-selections --installer > <replaceable>fitxer</replaceable> +$ debconf-get-selections >> <replaceable>fitxer</replaceable> +</screen></informalexample> + +Però un fitxer generat d'aquesta manera, tindrà també alguns valors que no +haurien de ser precarregats, i el fitxer <xref linkend="example-preseed"/> +és un millor punt de partida per la majoria dels usuaris. + +</para><para> + +Quan estigui preparat el fitxer de preconfiguració, podeu editar-lo si ho +necessiteu, i podeu posar-lo a un servidor web, o copiar-lo a un mitjà +d'instal·lació. A qualsevol lloc que poseu el fitxer, necessitareu passar-li +un paràmetre a l'instal·lador en el moment de l'arrencada per dir-li que +utilitze el fitxer. + +</para><para> + +Per fer que l'instal·lador utilitze un fitxer de preconfiguració baixant-lo +de la xarxa, afegiu preseed/url=http://url/to/preseed.cfg als paràmetres +d'arrencada del nucli. Per suposat, el fitxer de preconfiguració no tindrà +efecte fins que es configure la xarxa per descarregar el fitxer, així que és +més normal si l'instal·lador pot configurar la xarxa per DHCP sense fer cap +pregunta. Si voleu, podeu configurar la prioritat d'instal·lació a «critical» +per evitar les preguntes fins que la xarxa estigui configurada. Vegeu +<xref linkend="installer-args"/>. + +</para><para> + +Per posar el fitxer de preconfiguració a un CD, necessitaríeu remasteritzar +la imatge ISO per incloure el fitxer de preconfiguració. Vegeu els detalls +a la pàgina del manual de mkisofs. De forma alternativa, poseu el fitxer de +preconfiguració a un disquet, i utilitzeu preseed/file=/floppy/preseed.cfg. + +</para><para arch="i386"> + +Si arrenqueu des d'un llapis de memòria USB, aleshores podeu copiar el fitxer +de preconfiguració al llapis de memòria i editar el fitxer syslinux.cfg per +afegir preseed/file=/hd-media/preseed.cfg als paràmetres d'arrencada del +nucli. + +</para> + + <sect3 condition="etch"> + <title>Utilització de precàrrega per canviar els valors predeterminats</title> +<para> + +És possible utilitzar les precàrregues per canviar les respostes +predeterminades a les preguntes, però tot i així haver-les de respondre. +Per fer-ho, la marca <firstterm>seen</firstterm> ha de posar-se a +<quote>false</quote> desprès de definir el valor a la plantilla. + +<informalexample><screen> +d-i foo/bar string value +d-i foo/bar seen false +</screen></informalexample> + +</para> + </sect3> + </sect2> + </sect1> diff --git a/ca/install-methods/boot-drive-files.xml b/ca/install-methods/boot-drive-files.xml new file mode 100644 index 000000000..e80cf406a --- /dev/null +++ b/ca/install-methods/boot-drive-files.xml @@ -0,0 +1,176 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 untranslated --> + + <sect1 condition="bootable-disk" id="boot-drive-files"> + <title>Preparing Files for Hard Disk Booting</title> +<para> + +The installer may be booted using boot files placed on an +existing hard drive partition, either launched from another operating +system or by invoking a boot loader directly from the BIOS. + +</para><para> + +A full, <quote>pure network</quote> installation can be achieved using this +technique. This avoids all hassles of removable media, like finding +and burning CD images or struggling with too numerous and +unreliable floppy disks. + +</para><para arch="i386"> + +The installer cannot boot from files on an NTFS file system. + +</para><para arch="powerpc"> + +The installer cannot boot from files on an HFS+ file system. MacOS +System 8.1 and above may use HFS+ file systems; NewWorld PowerMacs all +use HFS+. To determine whether your existing file system is HFS+, +select <userinput>Get Info</userinput> for the volume in question. HFS +file systems appear as <userinput>Mac OS Standard</userinput>, while +HFS+ file systems say <userinput>Mac OS Extended</userinput>. You must +have an HFS partition in order to exchange files between MacOS and +Linux, in particular the installation files you download. + +</para><para arch="powerpc"> + +Different programs are used for hard disk installation system booting, +depending on whether the system is a <quote>NewWorld</quote> or an +<quote>OldWorld</quote> model. + +</para> + + <sect2 arch="i386" id="files-lilo"> + <title>Hard disk installer booting using <command>LILO</command> or + <command>GRUB</command></title> +<para> + +This section explains how to add to or even replace an existing linux +installation using either <command>LILO</command> or +<command>GRUB</command>. + +</para><para> + +At boot time, both bootloaders support loading in memory not +only the kernel, but also a disk image. This RAM disk can be used as +the root file-system by the kernel. + +</para><para> + +Copy the following files from the Debian archives to a +convenient location on your hard drive, for instance to +<filename>/boot/newinstall/</filename>. + +<itemizedlist> +<listitem><para> + +<filename>vmlinuz</filename> (kernel binary) + +</para></listitem> +<listitem><para> + +<filename>initrd.gz</filename> (ramdisk image) + +</para></listitem> +</itemizedlist> + +</para><para> + +Finally, to configure the bootloader proceed to +<xref linkend="boot-initrd"/>. + +</para> + </sect2> + + + <sect2 arch="powerpc" id="files-oldworld"> + <title>Hard Disk Installer Booting for OldWorld Macs</title> +<para> + +The <filename>boot-floppy-hfs</filename> floppy uses +<application>miBoot</application> to launch Linux installation, but +<application>miBoot</application> cannot easily be used for hard disk +booting. <application>BootX</application>, launched from MacOS, +supports booting from files placed on the hard +disk. <application>BootX</application> can also be used to dual-boot +MacOS and Linux after your Debian installation is complete. For the +Performa 6360, it appears that <command>quik</command> cannot make the +hard disk bootable. So <application>BootX</application> is required +on that model. + +</para><para> + +Download and unstuff the <application>BootX</application> +distribution, available from <ulink url="&url-powerpc-bootx;"></ulink>, +or in the +<filename>dists/woody/main/disks-powerpc/current/powermac</filename> +directory on Debian http/ftp mirrors and official Debian CDs. Use +<application>Stuffit Expander</application> to extract it from its +archive. Within the package, there is an empty folder called +<filename>Linux Kernels</filename>. Download +<filename>linux.bin</filename> and +<filename>ramdisk.image.gz</filename> from the +<filename>disks-powerpc/current/powermac</filename> folder, and place +them in the <filename>Linux Kernels</filename> folder. Then place the +<filename>Linux Kernels</filename> folder in the active System Folder. + +</para> + </sect2> + + <sect2 arch="powerpc" id="files-newworld"> + <title>Hard Disk Installer Booting for NewWorld Macs</title> +<para> + +NewWorld PowerMacs support booting from a network or an ISO9660 +CD-ROM, as well as loading ELF binaries directly from the hard +disk. These machines will boot Linux directly via +<command>yaboot</command>, which supports loading a kernel and RAMdisk +directly from an ext2 partition, as well as dual-booting with +MacOS. Hard disk booting of the installer is particularly appropriate +for newer machines without floppy drives. <command>BootX</command> is +not supported and must not be used on NewWorld PowerMacs. + +</para><para> + +<emphasis>Copy</emphasis> (not move) the following four files which +you downloaded earlier from the Debian archives, onto the root level +of your hard drive (this can be accomplished by +<keycap>option</keycap>-dragging each file to the hard drive icon). + +<itemizedlist> +<listitem><para> + +<filename>vmlinux</filename> + +</para></listitem> +<listitem><para> + +<filename>initrd.gz</filename> + +</para></listitem> +<listitem><para> + +<filename>yaboot</filename> + +</para></listitem> +<listitem><para> + +<filename>yaboot.conf</filename> + +</para></listitem> +</itemizedlist> + +</para><para> + +Make a note of the partition number of the MacOS partition where you +place these files. If you have the MacOS <command>pdisk</command> +program, you can use the L command to check for the partition +number. You will need this partition number for the command you type +at the Open Firmware prompt when you boot the installer. + +</para><para> + +To boot the installer, proceed to <xref linkend="boot-newworld"/>. + +</para> + </sect2> + </sect1> diff --git a/ca/install-methods/boot-usb-files.xml b/ca/install-methods/boot-usb-files.xml new file mode 100644 index 000000000..13fdd49a4 --- /dev/null +++ b/ca/install-methods/boot-usb-files.xml @@ -0,0 +1,127 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 25496 --> + + <sect1 condition="bootable-usb" id="boot-usb-files"> + <title>Preparant els fitxers per arrencar amb el llapis de memòria USB</title> + +<para> + +Per preparar el llapis USB necessitareu un sistema on el GNU/Linux ja +estiga funcionant i que suporte el USB. Heu d'assegurar-vos que el mòdul +del nucli usb-storage estiga carregat (<userinput>modprobe +usb-storage</userinput>) i proveu de trobar a quin dispositiu SCSI s'ha +assignat el llapis USB (a aquest exemple s'ha utilitzat +<filename>/dev/sda</filename>). Per escriure al vostre llapis, haureu de +desconnectar la protecció d'escriptura. + +</para><para> + +Adoneu-vos, que el llapis USB ha de tenir una mida mínima de 128 MB (és +possible configurar amb llapis amb menys capacitat si seguiu +<xref linkend="usb-copy-flexible"/>). + +</para> + + <sect2 id="usb-copy-easy"> + <title>Copiant els fitxers — la manera fàcil</title> +<para arch="i386"> + +Hi ha un fitxer complet <filename>hd-media/boot.img.gz</filename> +que conté tots el fitxers de l'instal·lador (incloent el nucli) així com +<command>SYSLINUX</command> i el seu fitxer de configuració. Tan sols heu +d'extraure'l directament al vostre llapis USB: + +<informalexample><screen> +# zcat boot.img.gz > /dev/<replaceable>sda</replaceable> +</screen></informalexample> + +Per suposat, açò destruirà qualsevol dada que hi hagués al dispositiu, +així que aneu en compte de utilitzar el nom del dispositiu correcte pel +vostre llapis USB. + +</para><para arch="powerpc"> + +Hi ha un fitxer complet <filename>hd-media/boot.img.gz</filename> +que conté tots els fitxers de l'instal·lador (incloent el nucli) així com +<command>yaboot</command> i el seu fitxer de configuració. Creeu una +partició de tipus «Apple_Bootstrap» al vostre llapis USB utilitzant la +comanda <userinput>C</userinput> del <command>mac-fdisk</command> i +extraure la imatge directament: + +<informalexample><screen> +# zcat boot.img.gz > /dev/<replaceable>sda2</replaceable> +</screen></informalexample> + +Per suposat, açò destruirà qualsevol dada que hi hagués al dispositiu, +així que aneu en compte de utilitzar el nom del dispositiu correcte pel +vostre llapis USB. + +</para><para> + +Desprès d'això, munteu el llapis de memòria USB (<userinput>mount +<replaceable arch="i386">/dev/sda</replaceable> +<replaceable arch="powerpc">/dev/sda2</replaceable> +/mnt</userinput>), que ara tindrà +<phrase arch="i386">un sistema de fitxers FAT</phrase> +<phrase arch="powerpc">un sistema de fitxers HFS</phrase> +en ell, i copieu una imatge ISO de tarja de negocis o netinst a dins. +Adoneu-vos que el nom del fitxer ha d'acabar en <filename>.iso</filename>. +Desmunteu el llapis (<userinput>umount /mnt</userinput>) i ja està. + +</para> + </sect2> + + <sect2 id="usb-copy-flexible"> + <title>Copiant els fitxers — la forma flexible</title> +<para> + +Si voleu més flexibilitat o voleu saber que esteu fent, heu de seguir +aquest mètode per posar els fitxers al vostre llapis. + +</para> + +&usb-setup-i386.xml; +&usb-setup-powerpc.xml; + + <sect3> + <title>Afegint la imatge ISO</title> +<para> + +Ara hauríeu de posar una imatge ISO de Debian (la de tarja de negocis, +netinst o be una completa) al vostre llapis (si cap). El nom del fitxer +d'eixa imatge ha d'acabar en <filename>.iso</filename>. + +</para><para> + +Si voleu instal·lar damunt una xarxa, sense utilitzar una imatge ISO, +hauríeu d'ometre el pas previ. A més a més heu d'utilitzar el disc en +memòria inicial des del directori <filename>netboot</filename> en +comptes d'un del <filename>hd-media</filename>, perquè el +<filename>hd-media/initrd.gz</filename> no té suport per xarxa. + +</para><para> + +Quan acabeu, desmunteu el llapis USB (<userinput>umount /mnt</userinput>) +i activeu la protecció d'escriptura. + +</para> + </sect3> + + <!-- TODO: doesn't this section belong later? --> + <sect3 arch="i386"> + <title>Arrencant el llapis USB</title> +<warning><para> + +Si el sistema rebutja arrencar des del llapis de memòria, el llapis +podria tenir un registre inicial d'arranc invàlid (MBR). Per reparar-ho, +utilitzeu la comanda <command>install-mbr</command> del paquet +<classname>mbr</classname>: + +<informalexample><screen> +# install-mbr /dev/<replaceable>sda</replaceable> +</screen></informalexample> + +</para></warning> + </sect3> + </sect2> + </sect1> diff --git a/ca/install-methods/create-floppy.xml b/ca/install-methods/create-floppy.xml new file mode 100644 index 000000000..fbef8b01b --- /dev/null +++ b/ca/install-methods/create-floppy.xml @@ -0,0 +1,108 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 untranslated --> + + <sect1 condition="supports-floppy-boot" id="create-floppy"> + <title>Creating Floppies from Disk Images</title> +<para> + +Bootable floppy disks are generally used as a last resort to boot the +installer on hardware that cannot boot from CD or by other means. + +</para><para arch="powerpc"> + +Floppy disk booting reportedly fails on Mac USB floppy drives. + +</para><para arch="m68k"> + +Floppy disk booting is not supported on Amigas or +68k Macs. + +</para><para> + +Disk images are files containing the complete contents of a floppy +disk in <emphasis>raw</emphasis> form. Disk images, such as +<filename>boot.img</filename>, cannot simply be copied to floppy +drives. A special program is used to write the image files to floppy +disk in <emphasis>raw</emphasis> mode. This is required because these +images are raw representations of the disk; it is required to do a +<emphasis>sector copy</emphasis> of the data from the file onto the +floppy. + +</para><para> + +There are different techniques for creating floppies from disk images, +which depend on your platform. This section describes how to create +floppies from disk images on different platforms. + +</para><para> + +No matter which method you use to create your floppies, you should +remember to flip the write-protect tab on the floppies once you have +written them, to ensure they are not damaged unintentionally. + +</para> + + <sect2><title>Writing Disk Images From a Linux or Unix System</title> +<para> + +To write the floppy disk image files to the floppy disks, you will +probably need root access to the system. Place a good, blank floppy +in the floppy drive. Next, use the command + +<informalexample><screen> +$ dd if=<replaceable>filename</replaceable> of=/dev/fd0 bs=1024 conv=sync ; sync +</screen></informalexample> + +where <replaceable>filename</replaceable> is one of the floppy disk image +files (see <xref linkend="downloading-files"/> for what +<replaceable>filename</replaceable> should be). +<filename>/dev/fd0</filename> is a commonly used name of the floppy +disk device, it may be different on your workstation +<phrase arch="sparc">(on Solaris, it is +<filename>/dev/fd/0</filename>)</phrase>. +The command may return to the +prompt before Unix has finished writing the floppy disk, so look for +the disk-in-use light on the floppy drive and be sure that the light +is out and the disk has stopped revolving before you remove it from +the drive. On some systems, you'll have to run a command to eject the +floppy from the drive +<phrase arch="sparc">(on Solaris, use <command>eject</command>, see +the manual page)</phrase>. + +</para><para> + +Some systems attempt to automatically mount a floppy disk when you +place it in the drive. You might have to disable this feature before +the workstation will allow you to write a floppy in <emphasis>raw +mode</emphasis>. Unfortunately, how to accomplish this will vary +based on your operating system. +<phrase arch="sparc"> +On Solaris, you can work around +volume management to get raw access to the floppy. First, make sure +that the floppy is auto-mounted (using <command>volcheck</command> or +the equivalent command in the file manager). Then use a +<command>dd</command> command of the form given above, just replace +<filename>/dev/fd0</filename> with +<filename>/vol/rdsk/<replaceable>floppy_name</replaceable></filename>, +where <replaceable>floppy_name</replaceable> is the name the floppy +disk was given when it was formatted (unnamed floppies default to the +name <filename>unnamed_floppy</filename>). On other systems, ask your +system administrator. +</phrase> + +</para><para arch="powerpc"> + +If writing a floppy on powerpc Linux, you will need to eject it. The +<command>eject</command> program handles this nicely; you might need +to install it. + +</para> + + </sect2> + +&floppy-i386.xml; <!-- can be used for other arches --> +&floppy-m68k.xml; +&floppy-powerpc.xml; + + </sect1> + diff --git a/ca/install-methods/download/alpha.xml b/ca/install-methods/download/alpha.xml new file mode 100644 index 000000000..ff0250415 --- /dev/null +++ b/ca/install-methods/download/alpha.xml @@ -0,0 +1,36 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 untranslated --> + + + <sect3 arch="alpha"><title>Alpha Installation Files</title> +<para> + +If you choose to boot from ARC console firmware using +<command>MILO</command>, you will also need to prepare a disk +containing <command>MILO</command> and <command>LINLOAD.EXE</command> +from the provided disk images. See <xref linkend="alpha-firmware"/> +for more information on Alpha +firmware and boot loaders. The floppy images can be found in the +<filename>MILO</filename> directory as +<filename>milo_<replaceable>subarchitecture</replaceable>.bin</filename>. + +</para><para> + +Unfortunately, these <command>MILO</command> 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 +<command>MILO</command> binary onto the floppy +(<ulink url="&disturlftp;main/disks-alpha/current/MILO/"></ulink>). +Note that those <command>MILO</command>s don't support ext2 <quote>sparse +superblocks</quote>, 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 <command>MILO</command>. + +</para><para> + +<command>MILO</command> binaries are platform-specific. See +<xref linkend="alpha-cpus"/> to determine the appropriate +<command>MILO</command> image for your Alpha platform. + +</para> + </sect3> diff --git a/ca/install-methods/download/arm.xml b/ca/install-methods/download/arm.xml new file mode 100644 index 000000000..447f9c376 --- /dev/null +++ b/ca/install-methods/download/arm.xml @@ -0,0 +1,37 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 --> + + + <sect3 arch="arm" id="riscpc-install-files"> + <title>Fitxers d'instal·lació de RiscPC</title> +<para> + +L'instal·lador de RiscPC s'arrenca inicialment des de RISC OS. Tots els +fitxers necessaris es proveeixen en un arxiu Zip, &rpc-install-kit;. +Descarregueu aquest fitxer a la maquina RISC OS, copieu el +component <filename>linloader.!Boot</filename> a lloc, i executeu +<filename>!dInstall</filename>. + +</para> + </sect3> + + <sect3 arch="arm" id="netwinder-install-files"> + <title>Fitxers d'instal·lació de NetWinder</title> +<para> + +La manera més fàcil d'arrencar un NetWinder és a traves de la xarxa, +fent servir la imatge de TFTP proveïda &netwinder-boot-img;. + +</para> + </sect3> + + <sect3 arch="arm" id="cats-install-files"> + <title>Fitxers d'instal·lació de CATS</title> +<para> + +L'únic mètode d'arrencar per a CATS és fer servir la imatge combinada +&cats-boot-img;. Això es pot carregar des de qualsevol dispositiu +accessible per al carregador d'arranc Cyclone. + +</para> + </sect3> diff --git a/ca/install-methods/download/m68k.xml b/ca/install-methods/download/m68k.xml new file mode 100644 index 000000000..4ea3e1845 --- /dev/null +++ b/ca/install-methods/download/m68k.xml @@ -0,0 +1,23 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 --> + + + <sect3 arch="m68k" id="kernel-22"> + <title>Triant un nucli</title> + +<para> + +Algunes subarquitectures de m68k tenen nuclis a triar per a la instal·lació. +En general recomanem que proveu primer la versió mes recent. Si la vostra +subarquitectura o màquina necessita emprar un nucli 2.2.x, estigueu segurs +que trieu alguna de les imatges que suporten nuclis 2.2.x (vegeu el +<ulink url="&disturl;/main/installer-&architecture;/current/images/MANIFEST">MANIFEST</ulink>). + +</para> +<para> + +Totes les imatges de m68k per a ser emprades amb nuclis 2.2.x necessiten el +paràmetre de nucli &ramdisksize;. + +</para> + </sect3> diff --git a/ca/install-methods/download/powerpc.xml b/ca/install-methods/download/powerpc.xml new file mode 100644 index 000000000..d1dd228f9 --- /dev/null +++ b/ca/install-methods/download/powerpc.xml @@ -0,0 +1,28 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 untranslated --> + +<!-- commented out as it seems out of date and the links are broken + + <sect3 arch="powerpc" id="newworld-install-files"> + <title>NewWorld MacOS Installation Files </title> +<para> + +For floppy-less installation on NewWorld Macs, it may be most +convenient to obtain all the necessary files packaged into one Stuffit +archive from +<ulink url="&url-powerpc-of;"></ulink> (separate instructions are +included in the archive). Otherwise, obtain the normal installation +files listed above. Retrieve the files to an HFS (not HFS+) partition +on your system. You will also need the <filename>yaboot</filename> and +<filename>yaboot.conf</filename> files from the +<ulink url="&downloadable-file;new-powermac/">new-powermac</ulink> or +<ulink url="&downloadable-file;powermac/">powermac</ulink> archive folder. +However, the newest G4 PowerMacs, and those that work without MacOS 9, +need the newest version of <command>yaboot</command>; the one in the +archive will not work. Obtain the newest version from +<ulink url="http://penguinppc.org/projects/yaboot/"></ulink>. + +</para> + </sect3> + +--> diff --git a/ca/install-methods/downloading-files.xml b/ca/install-methods/downloading-files.xml new file mode 100644 index 000000000..832f39b01 --- /dev/null +++ b/ca/install-methods/downloading-files.xml @@ -0,0 +1,38 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 25148 --> + + <sect1 id="downloading-files"> + <title>Descarregar fitxers de les rèpliques de Debian</title> + +<para> + +Per trobar la rèplica mes pròxima (i possiblement la mes ràpida, mireu la +<ulink url="&url-debian-mirrors;">llista de rèpliques de Debian</ulink>. + +</para><para> + +Quan descarregueu fitxers de una rèplica de Debian, assegureu-vos que +descarregueu els fitxers en mode <emphasis>binari</emphasis>, ni mode +text ni mode automàtic. + +</para> + + <sect2 id="where-files"> + <title>On trobar imatges d'instal·lació</title> + +<para> +Les imatges d'instal·lació estan ubicades en cada rèplica de Debian al +directori <ulink url="&url-debian-installer;/images">debian/dists/&releasename;/main/installer-&architecture;/current/images/</ulink> +— el <ulink url="&url-debian-installer;/images/MANIFEST">MANIFEST</ulink> +llista cada imatge i el seu propòsit. +</para> + +&download-alpha.xml; +&download-arm.xml; +&download-powerpc.xml; +&download-m68k.xml; + + </sect2> + + </sect1> + diff --git a/ca/install-methods/floppy/i386.xml b/ca/install-methods/floppy/i386.xml new file mode 100644 index 000000000..740d84039 --- /dev/null +++ b/ca/install-methods/floppy/i386.xml @@ -0,0 +1,35 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 --> + + +<!-- This is not set off for i386 only, because many people will have --> +<!-- access to a PC in order to make a floppy for other arches. --> + + <sect2><title>Escrivint imatges de disquet des de DOS, Windows o OS/2</title> + +<para> + +Si teniu accés a una maquina i386, podeu usar un dels següents programes +per a copiar imatges a disquets. + +</para><para> + +Els programes <command>rawrite1</command> i <command>rawrite2</command> +es poden usar a MS-DOS. Per usar aquests programes, primer assegureu-vos +que esteu arrencant DOS. Intentar usar aquests programes des de dins d'una +finestra DOS a Windows o clicant dues vegades sobre aquests programes des +de Windows Explorer <emphasis>noo</emphasis> s'espera que funcioni. + +</para><para> + +El programa <command>rwwrtwin</command> funciona a Windows 95, NT, 98, 2000, +ME, XP i probablement versions posteriors. Per usar-lo necessitareu +desempaquetar diskio.dll en el mateix directori. + +</para><para> + +Aquestes eines es poden trobar als CD-ROM oficials de Debian dins del directori +<filename>/tools</filename>. + +</para> + </sect2> diff --git a/ca/install-methods/floppy/m68k.xml b/ca/install-methods/floppy/m68k.xml new file mode 100644 index 000000000..ff1e6eff4 --- /dev/null +++ b/ca/install-methods/floppy/m68k.xml @@ -0,0 +1,28 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 18672 --> + + + <sect2 arch="m68k"><title>Escrivint imatges de disquet en sistemes Atari</title> +<para> + +Trobareu el programa &rawwrite.ttp; al mateix directori que les imatges de +disquet. Inicieu el programa fent doble clic sobre la icona del programa, +i escriviu el nom del fitxer de la imatge de disquet que voleu escriure +al disquet en la línia d'ordres de la caixa de diàleg del programa TOS. + +</para> + + </sect2> + + <sect2 arch="m68k"><title>Escrivint imatges de disquet en sistemes Macintosh</title> +<para> + +No hi ha cap aplicació MacOS per a escriure imatges de disquet (i no tindria +sentit, ja que no es poden usar els disquets per arrencar el sistema +d'instal·lació o el nucli i els modules des d'un Macintosh). No obstant, +aquests fitxers són necessaris per a la instal·lació del sistema operatiu +i els mòduls, més tard en el procés. + +</para> + + </sect2> diff --git a/ca/install-methods/floppy/powerpc.xml b/ca/install-methods/floppy/powerpc.xml new file mode 100644 index 000000000..6c05a2e49 --- /dev/null +++ b/ca/install-methods/floppy/powerpc.xml @@ -0,0 +1,122 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 untranslated --> + + + <sect2 arch="powerpc"><title>Writing Disk Images From MacOS</title> +<para> + +An AppleScript, <application>Make Debian Floppy</application>, is +available for burning floppies from the provided disk image files. It +can be downloaded from +<ulink url="ftp://ftp2.sourceforge.net/pub/sourceforge/d/de/debian-imac/MakeDebianFloppy.sit"></ulink>. To +use it, just unstuff it on your desktop, and then drag any floppy +image file to it. You must have Applescript installed and enabled in +your extensions manager. Disk Copy will ask you to confirm that you +wish to erase the floppy and proceed to write the file image to it. + +</para><para> + +You can also use the MacOS utility <command>Disk Copy</command> +directly, or the freeware utility <command>suntar</command>. The +<filename>root.bin</filename> file is an example of a floppy +image. Use one of the following methods to create a floppy from the +floppy image with these utilities. + +</para> + + <sect3> + <title>Writing Disk Images with <command>Disk Copy</command></title> +<para> + +If you are creating the floppy image from files which were originally +on the official &debian; CD, then the Type and Creator are already set +correctly. The following <command>Creator-Changer</command> steps are +only necessary if you downloaded the image files from a Debian mirror. + +</para> +<orderedlist> +<listitem><para> + +Obtain +<ulink url="&url-powerpc-creator-changer;">Creator-Changer</ulink> +and use it to open the <filename>root.bin</filename> file. + +</para></listitem> +<listitem><para> + +Change the Creator to <userinput>ddsk</userinput> (Disk Copy), and the +Type to <userinput>DDim</userinput> (binary floppy image). The case is +sensitive for these fields. + +</para></listitem> +<listitem><para> + +<emphasis>Important:</emphasis> In the Finder, use <userinput>Get +Info</userinput> to display the Finder information about the floppy +image, and <quote>X</quote> the <userinput>File Locked</userinput> check box so +that MacOS will be unable to remove the boot blocks if the image is +accidentally mounted. + +</para></listitem> + <listitem><para> + +Obtain <command>Disk Copy</command>; if you have a MacOS system or CD it +will very likely be there already, otherwise try +<ulink url="&url-powerpc-diskcopy;"></ulink>. + +</para></listitem> +<listitem><para> + +Run <command>Disk Copy</command>, and select <menuchoice> +<guimenu>Utilities</guimenu> <guimenuitem>Make a Floppy</guimenuitem> +</menuchoice>, then select the +<emphasis>locked</emphasis> image file from the resulting dialog. It +will ask you to insert a floppy, then ask if you really want to erase +it. When done it should eject the floppy. + +</para></listitem> +</orderedlist> + + </sect3> + + <sect3> + <title>Writing Disk Images with <command>suntar</command></title> +<para> + +<orderedlist> +<listitem><para> + +Obtain <command>suntar</command> from <ulink url="&url-powerpc-suntar;"> +</ulink>. Start the <command>suntar</command> program and select +<quote>Overwrite Sectors...</quote> from the <userinput>Special</userinput> +menu. + +</para></listitem> +<listitem><para> + +Insert the floppy disk as requested, then hit &enterkey; (start at +sector 0). + +</para></listitem> +<listitem><para> + +Select the <filename>root.bin</filename> file in the file-opening dialog. + +</para></listitem> +<listitem><para> + +After the floppy has been created successfully, select <menuchoice> +<guimenu>File</guimenu> <guimenuitem>Eject</guimenuitem> </menuchoice>. +If there are any errors writing the floppy, simply toss that floppy and +try another. + +</para></listitem> +</orderedlist> + +Before using the floppy you created, <emphasis>set the write protect +tab</emphasis>! Otherwise if you accidentally mount it in MacOS, +MacOS will helpfully ruin it. + +</para> + </sect3> + </sect2> diff --git a/ca/install-methods/install-methods.xml b/ca/install-methods/install-methods.xml new file mode 100644 index 000000000..0eac6d805 --- /dev/null +++ b/ca/install-methods/install-methods.xml @@ -0,0 +1,16 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 11648 --> + +<chapter id="install-methods"> + <title>Obtenint el suport d'instal·lació del sistema</title> + +&official-cdrom.xml; +&downloading-files.xml; +&ipl-tape.xml; +&create-floppy.xml; +&boot-usb-files.xml; +&boot-drive-files.xml; +&install-tftp.xml; +&automatic-install.xml; + +</chapter> diff --git a/ca/install-methods/install-tftp.xml b/ca/install-methods/install-tftp.xml new file mode 100644 index 000000000..5aa11a9ef --- /dev/null +++ b/ca/install-methods/install-tftp.xml @@ -0,0 +1,430 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 29334 untranslated --> + + <sect1 condition="supports-tftp" id="install-tftp"> + <title>Preparing Files for TFTP Net Booting</title> +<para> + +If your machine is connected to a local area network, you may be able +to boot it over the network from another machine, using TFTP. If you +intend to boot the installation system from another machine, the +boot files will need to be placed in specific locations on that machine, +and the machine configured to support booting of your specific machine. + +</para><para> + +You need to setup a TFTP server, and for many machines, a BOOTP server +<phrase condition="supports-rarp">, or RARP server</phrase> +<phrase condition="supports-dhcp">, or DHCP server</phrase>. + +</para><para> + +<phrase condition="supports-rarp">The Reverse Address Resolution Protocol (RARP) is +one way to tell your client what IP address to use for itself. Another +way is to use the BOOTP protocol. </phrase> + +<phrase condition="supports-bootp">BOOTP is an IP protocol that +informs a computer of its IP address and where on the network to obtain +a boot image. </phrase> + +<phrase arch="m68k"> Yet another alternative exists on VMEbus +systems: the IP address can be manually configured in boot ROM. </phrase> + +<phrase condition="supports-dhcp">The DHCP (Dynamic Host Configuration +Protocol) is a more flexible, backwards-compatible extension of BOOTP. +Some systems can only be configured via DHCP. </phrase> + +</para><para arch="powerpc"> + +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. + +</para><para arch="alpha"> + +Unlike the Open Firmware found on Sparc and PowerPC machines, the SRM +console will <emphasis>not</emphasis> use RARP to obtain its IP +address, and therefore you must use BOOTP for net booting your +Alpha<footnote> + +<para> +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. +</para> + +</footnote>. You can also enter the IP configuration for network +interfaces directly in the SRM console. + +</para><para arch="hppa"> + +Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. +An RBOOTD package is available on the parisc-linux web site. + +</para><para> + +The Trivial File Transfer Protocol (TFTP) is used to serve the boot +image to the client. Theoretically, any server, on any platform, +which implements these protocols, may be used. In the examples in +this section, we shall provide commands for SunOS 4.x, SunOS 5.x +(a.k.a. Solaris), and GNU/Linux. + +<note arch="i386"><para> + +To use the Pre-boot Execution Environment (PXE) method of TFTP +booting, you will need a TFTP server with <userinput>tsize</userinput> +support. On a &debian; server, the <classname>atftpd</classname> and +<classname>tftpd-hpa</classname> packages qualify; we recommend +<classname>tftpd-hpa</classname>. + +</para></note> + +</para> + +&tftp-rarp.xml; +&tftp-bootp.xml; +&tftp-dhcp.xml; + + <sect2 id="tftpd"> + <title>Enabling the TFTP Server</title> +<para> + +To get the TFTP server ready to go, you should first make sure that +<command>tftpd</command> is enabled. This is usually enabled by having +something like the following line in <filename>/etc/inetd.conf</filename>: + +<informalexample><screen> +tftp dgram udp wait nobody /usr/sbin/tcpd in.tftpd /tftpboot +</screen></informalexample> + +Debian packages will in general set this up correctly by default when they +are installed. + +</para><para> + +Look in that file and remember the directory which is used as the +argument of <command>in.tftpd</command>; you'll need that below. The +<userinput>-l</userinput> argument enables some versions of +<command>in.tftpd</command> to log all requests to the system logs; +this is useful for diagnosing boot errors. If you've had to change +<filename>/etc/inetd.conf</filename>, you'll have to notify the +running <command>inetd</command> process that the file has changed. +On a Debian machine, run <userinput>/etc/init.d/inetd +reload</userinput>; on other machines, +find out the process ID for <command>inetd</command>, and run +<userinput>kill -HUP <replaceable>inetd-pid</replaceable></userinput>. + +</para><para arch="mips"> + +If you intend to install Debian on an SGI machine and your TFTP server is a +GNU/Linux box running Linux 2.4, you'll need to set the following on your +server: + +<informalexample><screen> +# echo 1 > /proc/sys/net/ipv4/ip_no_pmtu_disc +</screen></informalexample> + +to turn off Path MTU discovery, otherwise the Indy's PROM can't +download the kernel. Furthermore, make sure TFTP packets are sent from +a source port no greater than 32767, or the download will stall after +the first packet. Again, it's Linux 2.4.X tripping this bug in the +PROM, and you can avoid it by setting + +<informalexample><screen> +# echo "2048 32767" > /proc/sys/net/ipv4/ip_local_port_range +</screen></informalexample> + +to adjust the range of source ports the Linux TFTP server uses. + +</para> + </sect2> + + <sect2 id="tftp-images"> + <title>Move TFTP Images Into Place</title> +<para> + +Next, place the TFTP boot image you need, as found in +<xref linkend="where-files"/>, in the <command>tftpd</command> +boot image directory. Generally, this directory will be +<filename>/tftpboot</filename>. You'll have to make a link from that +file to the file which <command>tftpd</command> will use for booting a +particular client. Unfortunately, the file name is determined by the +TFTP client, and there are no strong standards. + +</para><para arch="powerpc"> + +On NewWorld Power Macintosh machines, you will need to set up the +<command>yaboot</command> boot loader as the TFTP boot image. +<command>Yaboot</command> will then retrieve the kernel and RAMdisk +images via TFTP itself. For net booting, use the +<filename>yaboot-netboot.conf</filename>. Just rename this to +<filename>yaboot.conf</filename> in the TFTP directory. + +</para><para arch="i386"> + +For PXE booting, everything you should need is set up in the +<filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this +tarball into the <command>tftpd</command> boot image directory. Make sure +your dhcp server is configured to pass <filename>/pxelinux.0</filename> +to <command>tftpd</command> as the filename to boot. + +</para><para arch="ia64"> + +For PXE booting, everything you should need is set up in the +<filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this +tarball into the <command>tftpd</command> boot image directory. Make sure +your dhcp server is configured to pass +<filename>/debian-installer/ia64/elilo.efi</filename> +to <command>tftpd</command> as the filename to boot. + +</para> + + <sect3 arch="mipsel"> + <title>DECstation TFTP Images</title> +<para> + +For DECstations, there are tftpimage files for each subarchitecture, +which contain both kernel and installer in one file. The naming +convention is <replaceable>subarchitecture</replaceable>/netboot-boot.img. +Copy the tftpimage file you would like to use to +<userinput>/tftpboot/tftpboot.img</userinput> if you work with the +example BOOTP/DHCP setups described above. + +</para><para> + +The DECstation firmware boots by TFTP with the command <userinput>boot +<replaceable>#</replaceable>/tftp</userinput>, where +<replaceable>#</replaceable> is the number of the TurboChannel device +from which to boot. On most DECstations this is <quote>3</quote>. If the +BOOTP/DHCP server does not supply the filename or you need to pass +additional parameters, they can optionally be appended with the +following syntax: + +</para><para> + +<userinput>boot #/tftp/filename param1=value1 param2=value2 ...</userinput> + +</para><para> + +Several DECstation firmware revisions show a problem with regard to +net booting: the transfer starts, but after some time it stops with +an <computeroutput>a.out err</computeroutput>. This can have several reasons: + +<orderedlist> +<listitem><para> + +The firmware does not respond to ARP requests during a TFTP +transfer. This leads to an ARP timeout and the transfer stops. The +solution is to add the MAC address of the Ethernet card in the +DECstation statically to the ARP table of the TFTP server. This is +done by running <userinput>arp -s +<replaceable>IP-address</replaceable> +<replaceable>MAC-address</replaceable></userinput> as root on the +machine acting as TFTP server. The MAC-address of the DECstation can +be read out by entering <command>cnfg</command> at the DECstation +firmware prompt. + +</para></listitem> +<listitem><para> + +The firmware has a size limit on the files that can be booted +by TFTP. + +</para></listitem> +</orderedlist> + +There are also firmware revisions that cannot boot via TFTP at all. An +overview about the different firmware revisions can be found at the +NetBSD web pages: +<ulink url="http://www.netbsd.org/Ports/pmax/board-list.html#proms"></ulink>. + +</para> + </sect3> + + <sect3 arch="alpha"> + <title>Alpha TFTP Booting</title> +<para> +On Alpha, you must specify the filename (as a relative path to the +boot image directory) using the <userinput>-file</userinput> argument +to the SRM <userinput>boot</userinput> command, or by setting the +<userinput>BOOT_FILE</userinput> environment variable. Alternatively, +the filename can be given via BOOTP (in ISC <command>dhcpd</command>, +use the <userinput>filename</userinput> directive). Unlike Open +Firmware, there is <emphasis>no default filename</emphasis> on SRM, so +you <emphasis>must</emphasis> specify a filename by either one of +these methods. + +</para> + </sect3> + + <sect3 arch="sparc"> + <title>SPARC TFTP Booting</title> +<para> + +SPARC architectures for instance use the subarchitecture names, such +as <quote>SUN4M</quote> or <quote>SUN4C</quote>; in some cases, the +architecture is left blank, so the file the client looks for is just +<filename>client-ip-in-hex</filename>. Thus, if your system +subarchitecture is a SUN4C, and its IP is 192.168.1.3, the filename +would be <filename>C0A80103.SUN4C</filename>. An easy way to determine +this is to enter the following command in a shell (assuming the +machine's intended IP is 10.0.0.4). + +<informalexample><screen> +$ printf '%.2x%.2x%.2x%.2x\n' 10 0 0 4 +</screen></informalexample> + +This will spit out the IP in hexadecimal; to get to the correct +filename, you will need to change all letters to uppercase and +if necessary append the subarchitecture name. + +</para><para> + +You can also force some sparc systems to look for a specific file name +by adding it to the end of the OpenPROM boot command, such as +<userinput>boot net my-sparc.image</userinput>. This must still reside +in the directory that the TFTP server looks in. + +</para> + </sect3> + + <sect3 arch="m68k"> + <title>BVM/Motorola TFTP Booting</title> +<para> + +For BVM and Motorola VMEbus systems copy the files +&bvme6000-tftp-files; to <filename>/tftpboot/</filename>. + +</para><para> + +Next, configure your boot ROMs or BOOTP server to initially load the +<filename>tftplilo.bvme</filename> or +<filename>tftplilo.mvme</filename> files from the TFTP server. Refer +to the <filename>tftplilo.txt</filename> file for your subarchitecture +for additional system-specific configuration information. + +</para> + </sect3> + + <sect3 arch="mips"> + <title>SGI Indys TFTP Booting</title> +<para> + +On SGI Indys you can rely on the <command>bootpd</command> to supply +the name of the TFTP file. It is given either as the +<userinput>bf=</userinput> in <filename>/etc/bootptab</filename> or as +the <userinput>filename=</userinput> option in +<filename>/etc/dhcpd.conf</filename>. + +</para> + </sect3> + + <sect3 arch="mips"> + <title>Broadcom BCM91250A TFTP Booting</title> +<para> + +You don't have to configure DHCP in a special way because you'll pass the +full path of the file to the loaded to CFE. + +</para> + </sect3> + + </sect2> + +<!-- FIXME: commented out since it seems too old to be usable and a current + way is not known + + <sect2 id="tftp-low-memory"> + <title>TFTP Installation for Low-Memory Systems</title> +<para> + +On some systems, the standard installation RAMdisk, combined with the +memory requirements of the TFTP boot image, cannot fit in memory. In +this case, you can still install using TFTP, you'll just have to go +through the additional step of NFS mounting your root directory over +the network as well. This type of setup is also appropriate for +diskless or dataless clients. + +</para><para> + +First, follow all the steps above in <xref linkend="install-tftp"/>. + +<orderedlist> +<listitem><para> + +Copy the Linux kernel image on your TFTP server using the +<userinput>a.out</userinput> image for the architecture you are +booting. + +</para></listitem> +<listitem><para> + +Untar the root archive on your NFS server (can be the same system as +your TFTP server): + +<informalexample><screen> +# cd /tftpboot +# tar xvzf root.tar.gz +</screen></informalexample> + +Be sure to use the GNU <command>tar</command> (other tar programs, like the +SunOS one, badly handle devices as plain files). + +</para></listitem> +<listitem><para> + +Export your <filename>/tftpboot/debian-sparc-root</filename> directory +with root access to your client. E.g., add the following line to +<filename>/etc/exports</filename> (GNU/Linux syntax, should be similar +for SunOS): + +<informalexample><screen> +/tftpboot/debian-sparc-root <replaceable>client</replaceable>(rw,no_root_squash) +</screen></informalexample> + +NOTE: <replaceable>client</replaceable> is the host name or IP address recognized +by the server for the system you are booting. + +</para></listitem> +<listitem><para> + +Create a symbolic link from your client IP address in dotted notation +to <filename>debian-sparc-root</filename> in the +<filename>/tftpboot</filename> directory. For example, if the client +IP address is 192.168.1.3, do + +<informalexample><screen> +# ln -s debian-sparc-root 192.168.1.3 +</screen></informalexample> + +</para></listitem> +</orderedlist> + +</para> + + </sect2> + + <sect2 condition="supports-nfsroot"> + <title>Installing with TFTP and NFS Root</title> +<para> + +Installing with TFTP and NFS Root is similar to +<xref linkend="tftp-low-memory"/> because you don't want to +load the RAMdisk anymore but boot from the newly created NFS-root file +system. You then need to replace the symlink to the tftpboot image by +a symlink to the kernel image (for example, +<filename>linux-a.out</filename>). + +</para><para> + +RARP/TFTP requires all daemons to be running on the same server (the +workstation is sending a TFTP request back to the server that replied +to its previous RARP request). + +</para> + + + </sect2> +END FIXME --> + </sect1> diff --git a/ca/install-methods/ipl-tape.xml b/ca/install-methods/ipl-tape.xml new file mode 100644 index 000000000..659a76543 --- /dev/null +++ b/ca/install-methods/ipl-tape.xml @@ -0,0 +1,23 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 --> + + <sect1 arch="s390" id="ipl-tape"> + <title>Creant una cinta IPL</title> + +<para> + +Si no podeu arrencar (IPL) des del CD i no esteu emprant la VM, +haureu de crear primer una cinta IPL. Aquest procés esta descrit +en la secció 3.4.3 en el «Redbook +<ulink url="http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf"> +Linux for IBM eServer zSeries and S/390: Distributions</ulink>». +Els fitxers que necessiteu per escriure a la cinta són (en aquest ordre): +<filename>kernel.debian</filename>, +<filename>parmfile.debian</filename> i +<filename>initrd.debian</filename>. Els fitxers es poden descarregar +del subdirectori <filename>tape</filename>, vegeu +<xref linkend="where-files"/>, + +</para> + </sect1> + diff --git a/ca/install-methods/official-cdrom.xml b/ca/install-methods/official-cdrom.xml new file mode 100644 index 000000000..a4269fed7 --- /dev/null +++ b/ca/install-methods/official-cdrom.xml @@ -0,0 +1,69 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 untranslated --> + + <sect1 id="official-cdrom"> + <title>Official &debian; CD-ROM Sets</title> +<para> + +By far the easiest way to install &debian; is from an Official +Debian CD-ROM Set. You can buy a set from a vendor (see the +<ulink url="&url-debian-cd-vendors;">CD vendors page</ulink>). +You may also download the CD-ROM images from a Debian mirror and make +your own set, if you have a fast network connection and a CD burner +(see the <ulink url="&url-debian-cd;">Debian CD page</ulink> for +detailed instructions). If you have a Debian CD set and CDs are +bootable on your machine, you can skip right to +<xref linkend="boot-installer"/>; much effort has been expended to ensure +the files most people need are there on the CD. Although a full set of +binary packages requires several CDs, it is unlikely you will need +packages on the third CD and above. You may also consider using the +DVD version, which saves a lot of space on your shelf and you avoid +the CD shuffling marathon. + +</para><para> + +If your machine doesn't support CD booting, but you do have a CD set, +you can use an alternative strategy such as + +<phrase condition="supports-floppy-boot">floppy disk,</phrase> + +<phrase arch="s390">tape, emulated tape,</phrase> + +<phrase condition="bootable-disk">hard disk,</phrase> + +<phrase condition="bootable-usb">usb stick,</phrase> + +<phrase condition="supports-tftp">net boot,</phrase> + +or manually loading the kernel from the CD to initially boot the +system installer. The files you need for booting by another means are +also on the CD; the Debian network archive and CD folder organization +are identical. So when archive file paths are given below for +particular files you need for booting, look for those files in the +same directories and subdirectories on your CD. + +</para><para> + +Once the installer is booted, it will be able to obtain all the other +files it needs from the CD. + +</para><para> + +If you don't have a CD set, then you will need to download the +installer system files and place them on the + +<phrase arch="s390">installation tape</phrase> + +<phrase condition="supports-floppy-boot">floppy disk or</phrase> + +<phrase condition="bootable-disk">hard disk or</phrase> + +<phrase condition="bootable-usb">usb stick or</phrase> + +<phrase condition="supports-tftp">a connected computer</phrase> + +so they can be used to boot the installer. + +</para> + + </sect1> diff --git a/ca/install-methods/tftp/bootp.xml b/ca/install-methods/tftp/bootp.xml new file mode 100644 index 000000000..b6683f0ad --- /dev/null +++ b/ca/install-methods/tftp/bootp.xml @@ -0,0 +1,72 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 untranslated --> + + + <sect2 condition="supports-bootp" id="tftp-bootp"> + <title>Setting up BOOTP server</title> +<para> + +There are two BOOTP servers available for GNU/Linux, the CMU +<command>bootpd</command> and the other is actually a DHCP server, ISC +<command>dhcpd</command>, which are contained in the +<classname>bootp</classname> and <classname>dhcp</classname> packages +in &debian;. + +</para><para> + +To use CMU <command>bootpd</command>, you must first uncomment (or +add) the relevant line in <filename>/etc/inetd.conf</filename>. On +&debian;, you can run <userinput>update-inetd --enable +bootps</userinput>, then <userinput>/etc/init.d/inetd +reload</userinput> to do so. Elsewhere, the line in question should +look like: + +<informalexample><screen> +bootps dgram udp wait root /usr/sbin/bootpd bootpd -i -t 120 +</screen></informalexample> + +Now, you must create an <filename>/etc/bootptab</filename> file. This +has the same sort of familiar and cryptic format as the good old BSD +<filename>printcap</filename>, <filename>termcap</filename>, and +<filename>disktab</filename> files. See the +<filename>bootptab</filename> manual page for more information. For +CMU <command>bootpd</command>, you will need to know the hardware +(MAC) address of the client. Here is an example +<filename>/etc/bootptab</filename>: + +<informalexample><screen> +client:\ + hd=/tftpboot:\ + bf=tftpboot.img:\ + ip=192.168.1.90:\ + sm=255.255.255.0:\ + sa=192.168.1.1:\ + ha=0123456789AB: +</screen></informalexample> + +You will need to change at least the <quote>ha</quote> option, which +specifies the hardware address of the client. The <quote>bf</quote> +option specifies the file a client should retrieve via TFTP; see +<xref linkend="tftp-images"/> for more details. + +<phrase arch="mips"> +On SGI Indys you can just enter the command monitor and type +<userinput>printenv</userinput>. The value of the +<userinput>eaddr</userinput> variable is the machine's MAC address. +</phrase> + +</para><para> + +By contrast, setting up BOOTP with ISC <command>dhcpd</command> is +really easy, because it treats BOOTP clients as a moderately special +case of DHCP clients. Some architectures require a complex +configuration for booting clients via BOOTP. If yours is one of +those, read the section <xref linkend="dhcpd"/>. Otherwise, you +will probably be able to get away with simply adding the +<userinput>allow bootp</userinput> directive to the configuration +block for the subnet containing the client, and restart +<command>dhcpd</command> with <userinput>/etc/init.d/dhcpd +restart</userinput>. + +</para> + </sect2> diff --git a/ca/install-methods/tftp/dhcp.xml b/ca/install-methods/tftp/dhcp.xml new file mode 100644 index 000000000..f51eb2622 --- /dev/null +++ b/ca/install-methods/tftp/dhcp.xml @@ -0,0 +1,97 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 29400 untranslated --> + + <sect2 condition="supports-dhcp" id="dhcpd"> + <title>Setting up a DHCP server</title> +<para> + +One free software DHCP server is ISC <command>dhcpd</command>. +In &debian;, this is available in the <classname>dhcp</classname> package. +Here is a sample configuration file for it (usually +<filename>/etc/dhcpd.conf</filename>): + +<informalexample><screen> +option domain-name "example.com"; +option domain-name-servers ns1.example.com; +option subnet-mask 255.255.255.0; +default-lease-time 600; +max-lease-time 7200; +server-name "servername"; + +subnet 192.168.1.0 netmask 255.255.255.0 { + range 192.168.1.200 192.168.1.253; + option routers 192.168.1.1; +} + +host clientname { + filename "/tftpboot/tftpboot.img"; + server-name "servername"; + next-server servername; + hardware ethernet 01:23:45:67:89:AB; + fixed-address 192.168.1.90; +} +</screen></informalexample> + +Note: the new (and preferred) <classname>dhcp3</classname> package uses +<filename>/etc/dhcp3/dhcpd.conf</filename>. + +</para><para> + +In this example, there is one server +<replaceable>servername</replaceable> which performs all of the work +of DHCP server, TFTP server, and network gateway. You will almost +certainly need to change the domain-name options, as well as the +server name and client hardware address. The +<replaceable>filename</replaceable> option should be the name of the +file which will be retrieved via TFTP. + +</para><para> + +After you have edited the <command>dhcpd</command> configuration file, +restart it with <userinput>/etc/init.d/dhcpd restart</userinput>. + +</para> + + <sect3 arch="i386"> + <title>Enabling PXE Booting in the DHCP configuration</title> +<para> +Here is another example for a <filename>dhcp.conf</filename> using the +Pre-boot Execution Environment (PXE) method of TFTP. + +<informalexample><screen> +option domain-name "example.com"; + +default-lease-time 600; +max-lease-time 7200; + +allow booting; +allow bootp; + +# The next paragraph needs to be modified to fit your case +subnet 192.168.1.0 netmask 255.255.255.0 { + range 192.168.1.200 192.168.1.253; + option broadcast-address 192.168.1.255; +# the gateway address which can be different +# (access to the internet for instance) + option routers 192.168.1.1; +# indicate the dns you want to use + option domain-name-servers 192.168.1.3; +} + +group { + next-server 192.168.1.3; + host tftpclient { +# tftp client hardware address + hardware ethernet 00:10:DC:27:6C:15; + filename "/tftpboot/pxelinux.0"; + } +} +</screen></informalexample> + +Note that for PXE booting, the client filename <filename>pxelinux.0</filename> +is a boot loader, not a kernel image (see <xref linkend="tftp-images"/> +below). + +</para> + </sect3> + </sect2> diff --git a/ca/install-methods/tftp/rarp.xml b/ca/install-methods/tftp/rarp.xml new file mode 100644 index 000000000..c6fd184d4 --- /dev/null +++ b/ca/install-methods/tftp/rarp.xml @@ -0,0 +1,64 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 untranslated --> + + + <sect2 condition="supports-rarp" id="tftp-rarp"> + <title>Setting up RARP server</title> +<para> + +To setup RARP, you need to know the Ethernet address (a.k.a. the MAC address) +of the client computers to be installed. +If you don't know this information, you can + +<phrase arch="sparc"> pick it off the initial OpenPROM boot messages, use the +OpenBoot <userinput>.enet-addr</userinput> command, or </phrase> + +boot into <quote>Rescue</quote> mode (e.g., from the rescue floppy) and use the +command <userinput>/sbin/ifconfig eth0</userinput>. + +</para><para> + +On a RARP server system using a Linux 2.2.x kernel, +you need to populate the kernel's RARP table. +To do this, run the following commands: + +<informalexample><screen> +# <userinput>/sbin/rarp -s +<replaceable>client-hostname</replaceable> +<replaceable>client-enet-addr</replaceable></userinput> + +# <userinput>/usr/sbin/arp -s +<replaceable>client-ip</replaceable> +<replaceable>client-enet-addr</replaceable></userinput> +</screen></informalexample> + +If you get + +<informalexample><screen> +SIOCSRARP: Invalid argument +</screen></informalexample> + +you probably need to load the RARP kernel module or else recompile the +kernel to support RARP. Try <userinput>modprobe rarp</userinput> and +then try the <command>rarp</command> command again. + +</para><para> + +On a RARP server system using a Linux 2.4.x kernel, +there is no RARP module, and +you should instead use the <command>rarpd</command> program. The +procedure is similar to that used under SunOS in the following +paragraph. + +</para><para> + +Under SunOS, you need to ensure that the Ethernet hardware address for +the client is listed in the <quote>ethers</quote> database (either in the +<filename>/etc/ethers</filename> file, or via NIS/NIS+) and in the +<quote>hosts</quote> database. Then you need to start the RARP daemon. +In SunOS 4, issue the command (as root): +<userinput>/usr/etc/rarpd -a</userinput>; in SunOS 5, use +<userinput>/usr/sbin/rarpd -a</userinput>. + +</para> + </sect2> diff --git a/ca/install-methods/usb-setup/i386.xml b/ca/install-methods/usb-setup/i386.xml new file mode 100644 index 000000000..cbeab6250 --- /dev/null +++ b/ca/install-methods/usb-setup/i386.xml @@ -0,0 +1,101 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 27345 untranslated --> + + <sect3 arch="i386"> + <title>USB stick partitioning on &arch-title;</title> +<para> + +We will show how to setup the memory stick to use the first partition, +instead of the entire device. + +</para><note><para> + +Since most USB sticks come pre-configured with a single FAT16 +partition, you probably won't have to repartition or reformat the +stick. If you have to do that anyway, use <command>cfdisk</command> +or any other partitioning tool for creating a FAT16 partition and then +create the filesystem using: + +<informalexample><screen> +# mkdosfs /dev/<replaceable>sda1</replaceable> +</screen></informalexample> + +Take care that you use the correct device name for your USB stick. The +<command>mkdosfs</command> command is contained in the +<classname>dosfstools</classname> Debian package. + +</para></note><para> + +In order to start the kernel after booting from the USB stick, we will +put a boot loader on the stick. Although any boot loader +(e.g. <command>LILO</command>) should work, it's convenient to use +<command>SYSLINUX</command>, since it uses a FAT16 partition and can +be reconfigured by just editing a text file. Any operating system +which supports the FAT file system can be used to make changes to the +configuration of the boot loader. + +</para><para> + +To put <command>SYSLINUX</command> on the FAT16 partition on your USB +stick, install the <classname>syslinux</classname> and +<classname>mtools</classname> packages on your system, and do: + +<informalexample><screen> +# syslinux /dev/<replaceable>sda1</replaceable> +</screen></informalexample> + +Again, take care that you use the correct device name. The partition +must not be mounted when starting <command>SYSLINUX</command>. This +procedure writes a boot sector to the partition and creates the file +<filename>ldlinux.sys</filename> which contains the boot loader code. + +</para><para> + +Mount the partition (<userinput>mount /dev/sda1 /mnt</userinput>) and +copy the following files from the Debian archives to the stick: + +<itemizedlist> +<listitem><para> + +<filename>vmlinuz</filename> (kernel binary) + +</para></listitem> +<listitem><para> + +<filename>initrd.gz</filename> (initial ramdisk image) + +</para></listitem> +<listitem><para> + +<filename>syslinux.cfg</filename> (SYSLINUX configuration file) + +</para></listitem> +<listitem><para> + +Optional kernel modules + +</para></listitem> +</itemizedlist> + +If you want to rename the files, please note that +<command>SYSLINUX</command> can only process DOS (8.3) file names. + +</para><para> + +The <filename>syslinux.cfg</filename> configuration file should +contain the following two lines: + +<informalexample><screen> +default vmlinuz +append initrd=initrd.gz ramdisk_size=12000 root=/dev/rd/0 init=/linuxrc rw +</screen></informalexample> + +Please note that the <userinput>ramdisk_size</userinput> parameter +may need to be increased, depending on the image you are booting. +<phrase condition="sarge"> +If the boot fails, you can try adding <userinput>devfs=mount,dall</userinput> +to the <quote>append</quote> line. +</phrase> + +</para> + </sect3> diff --git a/ca/install-methods/usb-setup/powerpc.xml b/ca/install-methods/usb-setup/powerpc.xml new file mode 100644 index 000000000..36c572fa4 --- /dev/null +++ b/ca/install-methods/usb-setup/powerpc.xml @@ -0,0 +1,111 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 27345 untranslated --> + + <sect3 arch="powerpc"> + <title>USB stick partitioning on &arch-title;</title> +<para> + +Most USB sticks do not come pre-configured in such a way that Open +Firmware can boot from them, so you will need to repartition the stick. +On Mac systems, run <userinput>mac-fdisk /dev/sda</userinput>, +initialise a new partition map using the <userinput>i</userinput> +command, and create a new partition of type Apple_Bootstrap using the +<userinput>C</userinput> command. (Note that the first "partition" will +always be the partition map itself.) Then type + +<informalexample><screen> +$ hformat /dev/<replaceable>sda2</replaceable> +</screen></informalexample> + +Take care that you use the correct device name for your USB stick. The +<command>hformat</command> command is contained in the +<classname>hfsutils</classname> Debian package. + +</para><para> + +In order to start the kernel after booting from the USB stick, we will +put a boot loader on the stick. The <command>yaboot</command> boot +loader can be installed on an HFS filesystem and can be reconfigured by +just editing a text file. Any operating system which supports the HFS +file system can be used to make changes to the configuration of the boot +loader. + +</para><para> + +The normal <command>ybin</command> tool that comes with +<command>yaboot</command> does not yet understand USB storage devices, +so you will have to install <command>yaboot</command> by hand using the +<classname>hfsutils</classname> tools. Type + +<informalexample><screen> +$ hmount /dev/sda2 +$ hcopy -r /usr/lib/yaboot/yaboot : +$ hattrib -c UNIX -t tbxi :yaboot +$ hattrib -b : +$ humount +</screen></informalexample> + +Again, take care that you use the correct device name. The partition +must not be otherwise mounted during this procedure. This procedure +writes the boot loader to the partition, and uses the HFS utilities to +mark it in such a way that Open Firmware will boot it. Having done this, +the rest of the USB stick may be prepared using the normal Unix +utilities. + +</para><para> + +Mount the partition (<userinput>mount /dev/sda2 /mnt</userinput>) and +copy the following files from the Debian archives to the stick: + +<itemizedlist> +<listitem><para> + +<filename>vmlinux</filename> (kernel binary) + +</para></listitem> +<listitem><para> + +<filename>initrd.gz</filename> (initial ramdisk image) + +</para></listitem> +<listitem><para> + +<filename>yaboot.conf</filename> (yaboot configuration file) + +</para></listitem> +<listitem><para> + +<filename>boot.msg</filename> (optional boot message) + +</para></listitem> +<listitem><para> + +Optional kernel modules + +</para></listitem> +</itemizedlist> + +</para><para> + +The <filename>yaboot.conf</filename> configuration file should +contain the following lines: + +<informalexample><screen> +default=install +root=/dev/ram + +message=/boot.msg + +image=/vmlinux + label=install + initrd=/initrd.gz + initrd-size=10000<phrase condition="sarge"> + append="devfs=mount,dall --"</phrase> + read-only +</screen></informalexample> + +Please note that the <userinput>initrd-size</userinput> parameter +may need to be increased, depending on the image you are booting. + +</para> + </sect3> diff --git a/ca/partitioning/device-names.xml b/ca/partitioning/device-names.xml new file mode 100644 index 000000000..49effd568 --- /dev/null +++ b/ca/partitioning/device-names.xml @@ -0,0 +1,161 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 untranslated --> + + + <sect1 id="device-names"> + <title>Device Names in Linux</title> +<para> + +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: + +</para> +<itemizedlist arch="not-s390"> +<listitem><para> + +The first floppy drive is named <filename>/dev/fd0</filename>. + +</para></listitem> +<listitem><para> + +The second floppy drive is named <filename>/dev/fd1</filename>. + +</para></listitem> +<listitem><para> + +The first SCSI disk (SCSI ID address-wise) is named +<filename>/dev/sda</filename>. + +</para></listitem> +<listitem><para> + +The second SCSI disk (address-wise) is named +<filename>/dev/sdb</filename>, and so on. + +</para></listitem> +<listitem><para> + +The first SCSI CD-ROM is named <filename>/dev/scd0</filename>, also +known as <filename>/dev/sr0</filename>. + +</para></listitem> +<listitem><para> + +The master disk on IDE primary controller is named +<filename>/dev/hda</filename>. + +</para></listitem> +<listitem><para> + +The slave disk on IDE primary controller is named +<filename>/dev/hdb</filename>. + +</para></listitem> +<listitem><para> + +The master and slave disks of the secondary controller can be called +<filename>/dev/hdc</filename> and <filename>/dev/hdd</filename>, +respectively. Newer IDE controllers can actually have two channels, +effectively acting like two controllers. + +<phrase arch="m68k"> +The letters may differ from what shows in the mac program pdisk +(i.e. what shows up as <filename>/dev/hdc</filename> on pdisk may show +up as <filename>/dev/hda</filename> in Debian). +</phrase> + +</para></listitem> + +<listitem arch="i386"><para> + +The first XT disk is named <filename>/dev/xda</filename>. + +</para></listitem> +<listitem arch="i386"><para> + +The second XT disk is named <filename>/dev/xdb</filename>. + +</para></listitem> +<listitem arch="m68k"><para> + +The first ACSI device is named <filename>/dev/ada</filename>, the +second is named <filename>/dev/adb</filename>. + +</para></listitem> +</itemizedlist> + +<itemizedlist arch="s390"> +<listitem><para> + +The first DASD device is named +<filename>/dev/dasda</filename>. + +</para></listitem> +<listitem><para> + +The second DASD device is named +<filename>/dev/dasdb</filename>, and so on. + +</para></listitem> +</itemizedlist> + +<para arch="not-s390"> + +The partitions on each disk are represented by appending a decimal +number to the disk name: <filename>sda1</filename> and +<filename>sda2</filename> represent the first and +second partitions of the first SCSI disk drive in your system. + +</para><para arch="not-s390"> + +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 <filename>sda</filename>, +and the second <filename>sdb</filename>. If the +<filename>sda</filename> drive has 3 partitions on it, these will be +named <filename>sda1</filename>, <filename>sda2</filename>, and +<filename>sda3</filename>. The same applies to the +<filename>sdb</filename> disk and its partitions. + +</para><para arch="not-s390"> + +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. + +</para><para arch="i386"> + +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 <filename>/dev/hda1</filename>. The logical partitions are +numbered starting at 5, so the first logical partition on that same +drive is <filename>/dev/hda5</filename>. 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. + +</para><para arch="m68k"> + +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 <filename>/dev/sfd0</filename>. + +</para><para arch="sparc"> + +Sun disk partitions allow for 8 separate partitions (or slices). The +third partition is usually (and is preferred to have) the <quote>Whole +Disk</quote> partition. This partition references all of the sectors of the +disk, and is used by the boot loader (either SILO, or Sun's). + +</para><para arch="s390"> + +The partitions on each disk are represented by appending a decimal +number to the disk name: <filename>dasda1</filename> and +<filename>dasda2</filename> represent the first and +second partitions of the first DASD device in your system. + +</para> + </sect1> diff --git a/ca/partitioning/partition-programs.xml b/ca/partitioning/partition-programs.xml new file mode 100644 index 000000000..c0b5bdaf7 --- /dev/null +++ b/ca/partitioning/partition-programs.xml @@ -0,0 +1,169 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 untranslated --> + + <sect1 id="partition-programs"> + <title>Debian Partitioning Programs</title> +<para> + +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. + +</para> + +<variablelist> + +<varlistentry> +<term><command>partman</command></term> +<listitem><para> + +Recommended partitioning tool in Debian. This swiss army knife can +also resize partitions, create filesystems +<phrase arch="i386"> (<quote>format</quote> in Windows speak)</phrase> +and assign them to the mountpoints. + +</para></listitem> +</varlistentry> + +<varlistentry condition="fdisk.txt"> +<term><command>fdisk</command></term> +<listitem><para> + +The original Linux disk partitioner, good for gurus. + +</para><para> + +Be careful if you have existing FreeBSD partitions on your machine. +The installation kernels include support for these partitions, but the +way that <command>fdisk</command> represents them (or not) can make the +device names differ. See the +<ulink url="&url-linux-freebsd;">Linux+FreeBSD HOWTO</ulink> + +</para></listitem> +</varlistentry> + +<varlistentry condition="cfdisk.txt"> +<term><command>cfdisk</command></term> +<listitem><para> + +A simple-to-use, full-screen disk partitioner for the rest of us. + +</para><para> + +Note that <command>cfdisk</command> doesn't understand FreeBSD +partitions at all, and, again, device names may differ as a result. + +</para></listitem> +</varlistentry> + +<varlistentry condition="atari-fdisk.txt"> +<term><command>atari-fdisk</command></term> +<listitem><para> + +Atari-aware version of <command>fdisk</command>. + +</para></listitem> +</varlistentry> + +<varlistentry condition="amiga-fdisk.txt"> +<term><command>amiga-fdisk</command></term> +<listitem><para> + +Amiga-aware version of <command>fdisk</command>. + +</para></listitem> +</varlistentry> + +<varlistentry condition="mac-fdisk.txt"> +<term><command>mac-fdisk</command></term> +<listitem><para> + +Mac-aware version of <command>fdisk</command>. + +</para></listitem> +</varlistentry> + +<varlistentry condition="pmac-fdisk.txt"> +<term><command>pmac-fdisk</command></term> +<listitem><para> + +PowerMac-aware version of <command>fdisk</command>, also used by BVM +and Motorola VMEbus systems. + +</para></listitem> +</varlistentry> + +<varlistentry condition="fdasd.txt"> +<term><command>fdasd</command></term> +<listitem><para> + +&arch-title; version of <command>fdisk</command>; Please read the +fdasd manual page or chapter 13 in +<ulink url="http://oss.software.ibm.com/developerworks/opensource/linux390/docu/l390dd08.pdf"> +Device Drivers and Installation Commands</ulink> for details. + +</para></listitem> +</varlistentry> +</variablelist> + +<para> + +One of these programs will be run by default when you select +<guimenuitem>Partition a Hard Disk</guimenuitem>. If the one which is run +by default isn't the one you want, quit the partitioner, go to the shell +(<userinput>tty2</userinput>) by pressing <keycap>Alt</keycap> +and <keycap>F2</keycap> keys together, and manually type in the +name of the program you want to use (and arguments, if any). Then +skip the <guimenuitem>Partition a Hard Disk</guimenuitem> step in +<command>debian-installer</command> and continue to the next step. + +</para><para> + +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 +<userinput>tty2</userinput> or under Execute A Shell to add a device +so the 21st partition can be initialized: + +<informalexample><screen> +# cd /dev +# mknod hda21 b 3 21 +# chgrp disk hda21 +# chmod 660 hda21 +</screen></informalexample> + +Booting into the new system will fail unless proper devices are present +on the target system. After installing the kernel and modules, execute: + +<informalexample><screen> +# cd /target/dev +# mknod hda21 b 3 21 +# chgrp disk hda21 +# chmod 660 hda21 +</screen></informalexample> + +<phrase arch="i386">Remember to mark your boot partition as +<quote>Bootable</quote>.</phrase> + +</para><para condition="mac-fdisk.txt"> + +One key point when partitioning for Mac type disks is that the +swap partition is identified by its name; it must be named <quote>swap</quote>. +All Mac linux partitions are the same partition type, +Apple_UNIX_SRV2. Please read the fine manual. We also suggest reading the +<ulink url="&url-mac-fdisk-tutorial;">mac-fdisk Tutorial</ulink>, which +includes steps you should take if you are sharing your disk with MacOS. + +</para> + +&partition-alpha.xml; +&partition-hppa.xml; +&partition-i386.xml; +&partition-ia64.xml; +&partition-mips.xml; +&partition-powerpc.xml; +&partition-sparc.xml; + + </sect1> diff --git a/ca/partitioning/partition/alpha.xml b/ca/partitioning/partition/alpha.xml new file mode 100644 index 000000000..240e7bd3d --- /dev/null +++ b/ca/partitioning/partition/alpha.xml @@ -0,0 +1,58 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 untranslated --> + + + <sect2 arch="alpha"><title>Partitioning for &arch-title;</title> +<para> + +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 +<xref linkend="alpha-firmware"/>.) As a result, <command>partman</command> +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. + +</para><para> + +If you have chosen to use <command>fdisk</command> 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 <quote>b</quote> +command to enter disk label mode. + +</para><para> + +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 +<emphasis>not</emphasis> make the third partition contain the whole +disk. This is not required by <command>aboot</command>, and in fact, +it may lead to confusion since the <command>swriteboot</command> +utility used to install <command>aboot</command> in the boot sector +will complain about a partition overlapping with the boot block. + +</para><para> + +Also, because <command>aboot</command> is written to the first few +sectors of the disk (currently it occupies about 70 kilobytes, or 150 +sectors), you <emphasis>must</emphasis> 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 <command>partman</command>, a small partition will still be +created for <command>aboot</command> for convenience reasons. + +</para><para condition="FIXME"> + +For ARC installations, you should make a small FAT partition at the +beginning of the disk to contain <command>MILO</command> and +<command>linload.exe</command> — 5 megabytes should be sufficient, see +<xref linkend="non-debian-partitioning"/>. Unfortunately, making FAT +file systems from the menu is not yet supported, so you'll have to do +it manually from the shell using <command>mkdosfs</command> before +attempting to install the boot loader. + +</para> + </sect2> diff --git a/ca/partitioning/partition/hppa.xml b/ca/partitioning/partition/hppa.xml new file mode 100644 index 000000000..521a5e848 --- /dev/null +++ b/ca/partitioning/partition/hppa.xml @@ -0,0 +1,22 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 untranslated --> + + + <sect2 arch="hppa"><title>Partitioning for &arch-title;</title> +<para> + +PALO, the HPPA boot loader, requires a partition of type <quote>F0</quote> 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 +<filename>/boot</filename>, since that is the directory where the Linux +kernel(s) will be stored. <filename>/boot</filename> needs to be big enough +to hold whatever kernels you might wish load; 8–16MB is generally +sufficient. + +</para> + </sect2> diff --git a/ca/partitioning/partition/i386.xml b/ca/partitioning/partition/i386.xml new file mode 100644 index 000000000..c4d621477 --- /dev/null +++ b/ca/partitioning/partition/i386.xml @@ -0,0 +1,94 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 untranslated --> + + + <sect2 arch="i386"><title>Partitioning for &arch-title;</title> +<para> + +If you have an existing other operating system such as DOS or Windows and +you want to preseve 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. + +</para><para> + +The PC BIOS generally adds additional constraints for disk +partitioning. There is a limit to how many <quote>primary</quote> and +<quote>logical</quote> 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 +<ulink url="&url-partition-howto;">Linux Partition HOWTO</ulink> and the +<ulink url="&url-phoenix-bios-faq-large-disk;">Phoenix BIOS FAQ</ulink>, but +this section will include a brief overview to help you plan most situations. + +</para><para> + +<quote>Primary</quote> partitions are the original partitioning scheme for PC +disks. However, there can only be four of them. To get past this +limitation, <quote>extended</quote> and <quote>logical</quote> 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. + +</para><para> + +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. + +</para><para> + +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). + +</para><para> + +This restriction doesn't apply if you have a BIOS newer than around +1995–98 (depending on the manufacturer) that supports the <quote>Enhanced +Disk Drive Support Specification</quote>. Both Lilo, the Linux loader, and +Debian's alternative <command>mbr</command> 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. + +</para><para> + +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 (<quote>Large</quote>). +More information about issues with large disks can be found in the +<ulink url="&url-large-disk-howto;">Large Disk HOWTO</ulink>. 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 <emphasis>translated</emphasis> representation of the +1024th cylinder. + +</para><para> + +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 +<emphasis>must</emphasis> be mounted on <filename>/boot</filename>, +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. + +</para> + </sect2> diff --git a/ca/partitioning/partition/ia64.xml b/ca/partitioning/partition/ia64.xml new file mode 100644 index 000000000..1dc42db62 --- /dev/null +++ b/ca/partitioning/partition/ia64.xml @@ -0,0 +1,125 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 untranslated --> + + + <sect2 arch="ia64"><title>Partitioning for &arch-title;</title> + +<para> + +The <command>partman</command> 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 <command>parted</command> to +do the on-disk partitioning. + +</para> + + <note> + <title>EFI Recognized Formats</title> +<para> + +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 <command>cfdisk</command>, +you should only use the <ulink url="parted.txt"> +<command>parted</command></ulink> because only it can manage both GPT +and MS-DOS tables correctly. + +</para></note> + +<para> + +The automatic partitioning recipes for <command>partman</command> +allocate an EFI partition as the first partition on the disk. +You can also set up the partition under the <guimenuitem>Guided +partitioning</guimenuitem> from the main menu in a manner similar to +setting up a <emphasis>swap</emphasis> partition. + +</para><para> + +The <command>partman</command> 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 +<command>parted</command> 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: + +<informalexample><screen> + mklabel gpt + mkpartfs primary fat 0 50 + mkpartfs primary linux-swap 51 1000 + mkpartfs primary ext2 1001 3000 + set 1 boot on + print + quit +</screen></informalexample> + +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 <command>parted</command> can take a few minutes to +complete, as it scans the partition for bad blocks. + +</para> + </sect2> + + <sect2 arch="ia64"><title>Boot Loader Partition Requirements</title> + +<para> + +ELILO, the ia64 boot loader, requires a partition containing a FAT +file system with the <userinput>boot</userinput> 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. + +</para><para> + +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 <command>partman</command> partitioner checks for an EFI partition +at the same time it checks for a properly set up <emphasis>root</emphasis> +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. + +</para><para> + +It is strongly recommended that you allocate the EFI boot partition +on the same disk as the <emphasis>root</emphasis> filesystem. + +</para> + + </sect2> + + <sect2 arch="ia64"><title>EFI Diagnostic Partitions</title> + +<para> + +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. + +</para> + + </sect2> diff --git a/ca/partitioning/partition/mips.xml b/ca/partitioning/partition/mips.xml new file mode 100644 index 000000000..fa135ab9b --- /dev/null +++ b/ca/partitioning/partition/mips.xml @@ -0,0 +1,16 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 untranslated --> + + + <sect2 arch="mips"><title>Partitioning for &arch-title;</title> +<para> + +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. + +</para> + </sect2> diff --git a/ca/partitioning/partition/powerpc.xml b/ca/partitioning/partition/powerpc.xml new file mode 100644 index 000000000..99e8324ee --- /dev/null +++ b/ca/partitioning/partition/powerpc.xml @@ -0,0 +1,57 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 23146 untranslated --> + + + <sect2 arch="powerpc"><title>Partitioning Newer PowerMacs</title> +<para> + +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 +<emphasis>Apple_Bootstrap</emphasis>. If the bootstrap partition is +not created with the <emphasis>Apple_Bootstrap</emphasis> type your +machine cannot be made bootable from the hard disk. This partition +can easily be created by creating a new partition in +<command>partman</command> and telling it to use it as a <quote>NewWorld +boot partition</quote>, or in <command>mac-fdisk</command> using the +<userinput>b</userinput> command. + +</para><para> + +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. + +</para><para> + +Note that the bootstrap partition is only meant to hold 3 very small +files: the <command>yaboot</command> binary, its configuration +<filename>yaboot.conf</filename>, and a first stage OpenFirmware +loader <command>ofboot.b</command>. It need not and must not be +mounted on your file system nor have kernels or anything else copied +to it. The <command>ybin</command> and <command>mkofboot</command> +utilities are used to manipulate this partition. + +</para><para> + +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 <command>mac-fdisk</command>'s +<userinput>r</userinput> 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. + +</para><para> + +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. + +</para> + </sect2> diff --git a/ca/partitioning/partition/sparc.xml b/ca/partitioning/partition/sparc.xml new file mode 100644 index 000000000..f4996a519 --- /dev/null +++ b/ca/partitioning/partition/sparc.xml @@ -0,0 +1,33 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 11648 untranslated --> + + + <sect2 arch="sparc"><title>Partitioning for &arch-title;</title> +<para> + +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. The +<keycap>s</keycap> key is used in <command>fdisk</command> to +create Sun disk labels. + +</para><para> + +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 +<emphasis>not</emphasis> 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. + +</para><para> + +It is also advised that the third partition should be of type <quote>Whole +disk</quote> (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 <command>SILO</command> boot loader keep its bearings. + +</para> + </sect2>
\ No newline at end of file diff --git a/ca/partitioning/partitioning.xml b/ca/partitioning/partitioning.xml new file mode 100644 index 000000000..2e5efcbf9 --- /dev/null +++ b/ca/partitioning/partitioning.xml @@ -0,0 +1,13 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 11648 --> + +<appendix id="partitioning"> +<title>Particionant per a Debian</title> + +&sizing.xml; +&tree.xml; +&schemes.xml; +&device-names.xml; +&partition-programs.xml; + +</appendix> diff --git a/ca/partitioning/schemes.xml b/ca/partitioning/schemes.xml new file mode 100644 index 000000000..1a98c734e --- /dev/null +++ b/ca/partitioning/schemes.xml @@ -0,0 +1,84 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 untranslated --> + + + <sect1> + <title>Recommended Partitioning Scheme</title> +<para> + +For new users, personal Debian boxes, home systems, and other +single-user setups, a single <filename>/</filename> 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. + +</para><para> + +For multi-user systems or systems with lots of disk space, it's best +to put <filename>/usr</filename>, <filename>/var</filename>, +<filename>/tmp</filename>, and <filename>/home</filename> each on +their own partitions separate from the <filename>/</filename> +partition. + +</para><para> + +You might need a separate <filename>/usr/local</filename> 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 <filename>/var/mail</filename> a separate partition. Often, +putting <filename>/tmp</filename> 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 +<filename>/home</filename> partition. In general, the partitioning +situation varies from computer to computer depending on its uses. + +</para><para> + +For very complex systems, you should see the +<ulink url="&url-multidisk-howto;"> +Multi Disk HOWTO</ulink>. This contains in-depth information, mostly +of interest to ISPs and people setting up servers. + +</para><para> + +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. + +</para><para arch="m68k"> + +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. + +</para><para> + +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 <quote>spindles</quote>) and, if possible, different SCSI or +IDE channels. The kernel will balance swap usage between multiple +swap partitions, giving better performance. + +</para><para> + +As an example, an older home machine might have 32MB of RAM and a +1.7GB IDE drive on <filename>/dev/hda</filename>. There might be a +500MB partition for another operating system on +<filename>/dev/hda1</filename>, a 32MB swap partition on +<filename>/dev/hda3</filename> and about 1.2GB on +<filename>/dev/hda2</filename>) as the Linux partition. + +</para><para> + +For an idea of the space taken by tasks +you might be interested in adding after your system installation is +complete, check <xref linkend="tasksel-size-list"/>. + +</para> + + </sect1> diff --git a/ca/partitioning/sizing.xml b/ca/partitioning/sizing.xml new file mode 100644 index 000000000..3a7441dc6 --- /dev/null +++ b/ca/partitioning/sizing.xml @@ -0,0 +1,52 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 11648 untranslated --> + + + <sect1 id="partition-sizing"> + <title>Deciding on Debian Partitions and Sizes</title> +<para> + +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. <quote>Swap</quote> is scratch space for an operating system, +which allows the system to use disk storage as <quote>virtual +memory</quote>. 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. + +</para><para> + +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 <quote>root partition</quote>. 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. + +</para><para> + +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 <filename>/var/mail</filename> a separate partition on the mail +server, most of the system will remain working even if you get spammed. + +</para><para> + +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? + +</para> + </sect1> diff --git a/ca/partitioning/tree.xml b/ca/partitioning/tree.xml new file mode 100644 index 000000000..8317cec8b --- /dev/null +++ b/ca/partitioning/tree.xml @@ -0,0 +1,150 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 untranslated --> + + + <sect1 id="directory-tree"> + <title>The Directory Tree</title> +<para> + +&debian; adheres to the +<ulink url="&url-fhs-home;">Filesystem Hierarchy Standard</ulink> +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 +<filename>/</filename>. At the root level, all Debian systems include +these directories: + +<informaltable> +<tgroup cols="2"> +<thead> +<row> + <entry>Directory</entry><entry>Content</entry> +</row> +</thead> + +<tbody> +<row> + <entry><filename>bin</filename></entry> + <entry>Essential command binaries</entry> +</row><row> + <entry><filename>boot</filename></entry> + <entry>Static files of the boot loader</entry> +</row><row> + <entry><filename>dev</filename></entry> + <entry>Device files</entry> +</row><row> + <entry><filename>etc</filename></entry> + <entry>Host-specific system configuration</entry> +</row><row> + <entry><filename>home</filename></entry> + <entry>User home directories</entry> +</row><row> + <entry><filename>lib</filename></entry> + <entry>Essential shared libraries and kernel modules</entry> +</row><row> + <entry><filename>media</filename></entry> + <entry>Contains mount points for replaceable media</entry> +</row><row> + <entry><filename>mnt</filename></entry> + <entry>Mount point for mounting a file system temporarily</entry> +</row><row> + <entry><filename>proc</filename></entry> + <entry>Virtual directory for system information (2.4 and 2.6 kernels)</entry> +</row><row> + <entry><filename>root</filename></entry> + <entry>Home directory for the root user</entry> +</row><row> + <entry><filename>sbin</filename></entry> + <entry>Essential system binaries</entry> +</row><row> + <entry><filename>sys</filename></entry> + <entry>Virtual directory for system information (2.6 kernels)</entry> +</row><row> + <entry><filename>tmp</filename></entry> + <entry>Temporary files</entry> +</row><row> + <entry><filename>usr</filename></entry> + <entry>Secondary hierarchy</entry> +</row><row> + <entry><filename>var</filename></entry> + <entry>Variable data</entry> +</row><row> + <entry><filename>opt</filename></entry> + <entry>Add-on application software packages</entry> +</row> +</tbody></tgroup></informaltable> +</para> + +<para> + +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. + +</para> +<itemizedlist> +<listitem><para> + +The root partition <filename>/</filename> must always physically +contain <filename>/etc</filename>, <filename>/bin</filename>, +<filename>/sbin</filename>, <filename>/lib</filename> and +<filename>/dev</filename>, otherwise you won't be able to boot. +Typically 150–250 MB is needed for the root partition. + +</para></listitem> +<listitem><para> + +<filename>/usr</filename>: contains all user programs +(<filename>/usr/bin</filename>), libraries +(<filename>/usr/lib</filename>), documentation +(<filename>/usr/share/doc</filename>), 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. + +</para></listitem> +<listitem><para> + +<filename>/var</filename>: 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 +<filename>/var</filename> 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. + +</para></listitem> +<listitem><para> + +<filename>/tmp</filename>: 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 +<filename>/tmp</filename> to temporarily store image files. If you +plan to use such applications, you should adjust the space available +in <filename>/tmp</filename> accordingly. + +</para></listitem> +<listitem><para> + +<filename>/home</filename>: 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 (MP3, movies) +in your home directory. + +</para></listitem> +</itemizedlist> + + </sect1> diff --git a/ca/post-install/further-reading.xml b/ca/post-install/further-reading.xml new file mode 100644 index 000000000..355a48850 --- /dev/null +++ b/ca/post-install/further-reading.xml @@ -0,0 +1,45 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 --> + + <sect1 id="further-reading"><title>Lectura i informació addicional</title> +<para> + +Si necessiteu informació sobre algun programa en concret, en primer lloc +intenteu fer +<userinput>man <replaceable>programa</replaceable></userinput>, o bé +<userinput>info <replaceable>programa</replaceable></userinput>. + +</para><para> + +També hi ha molta documentació útil a +<filename>/usr/share/doc</filename>. En concret, +<filename>/usr/share/doc/HOWTO</filename> i +<filename>/usr/share/doc/FAQ</filename> contenen informació d'interès +general. Per enviar informes d'errors, mireu +<filename>/usr/share/doc/debian/bug*</filename>. Si voleu saber més +sobre les característiques específiques dels programes a Debian, +consulteu +<filename>/usr/share/doc/(nom del paquet)/README.Debian</filename>. + +</para><para> + +La <ulink url="http://www.debian.org/">pàgina web de Debian</ulink> +té una gran quantitat de documentació sobre Debian. A destacar, +<ulink url="http://www.debian.org/doc/FAQ/">Debian PMF</ulink> i els +<ulink url="http://lists.debian.org/">arxius de les llistes de correu de +Debian</ulink>. La comunitat de Debian és autosuficient; si us voleu +subscriure a una o més llistes de correu, mireu la pàgina de +<ulink url="http://www.debian.org/MailingLists/subscribe">subscripció a +les llistes de correu</ulink>. + +</para><para> + +Una bona font d'informació sobre GNU/Linux en general és el +<ulink url="http://www.tldp.org/">Projecte de documentació de +Linux</ulink>. Allà hi trobareu els COM ES FA i enllaços a +d'altres llocs amb informació sobre les diferents parts d'un sistema +GNU/Linux. + +</para> + + </sect1> diff --git a/ca/post-install/kernel-baking.xml b/ca/post-install/kernel-baking.xml new file mode 100644 index 000000000..53bd03a09 --- /dev/null +++ b/ca/post-install/kernel-baking.xml @@ -0,0 +1,184 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 --> + + <sect1 id="kernel-baking"><title>Compilant un nou kernel</title> +<para> + +Per què algú voldria compilar un nou nucli? Sovint no és necessari, +ja que el nucli que distribueix Debian gestiona la majoria de les +configuracions. Tot i això, compilar un nou nucli és útil +per: + +<itemizedlist> +<listitem><para> + +gestionar maquinari especial o conflicte de maquinari amb els +nuclis proporcionats + +</para></listitem> +<listitem><para> + +gestionar maquinari o opcions que no estan incloses en el nucli estàndard, +alguns exemples poden ser l'APM o l'SMP + +</para></listitem> +<listitem><para> + +optimitzar el nucli suprimint controladors inútils per tal +d'agilitzar el temps d'arrencada + +</para></listitem> +<listitem><para> + +utilitzar opcions del nucli que no estan suportades pel nucli +predeterminat + +</para></listitem> +<listitem><para> + +executar un nucli actualitzat o de desenvolupament + +</para></listitem> +<listitem><para> + +impresionar als vostres amics, provar noves coses + +</para></listitem> +</itemizedlist> + +</para> + + <sect2><title>Gestió de la imatge del nucli</title> +<para> + +No tingueu por a l'hora de compilar el nucli. És divertit i profitós. + +</para><para> + +Per compilar un nucli a la manera de Debian, necessiteu alguns paquets: +<classname>kernel-package</classname>, +<classname>kernel-source-&kernelversion;</classname> (l'última versió +en el moment d'escriure aquest document), <classname>fakeroot</classname> +i alguns d'altres que probablement ja teniu instal·lats +(per accedir a la llista completa vegeu +<filename>/usr/share/doc/kernel-package/README.gz</filename>). + +</para><para> + +A través d'aquest mètode es generarà un .deb del codi font del nucli, +i en el cas que disposeu de mòduls no estàndard en crearà un .deb +dependent sincronitzat. És un mètode millor per gestionar imatges del nucli; +el directori <filename>/boot</filename> contindrà el nucli, el System.map i +un registre del fitxer de configuració actiu del muntatge. + +</para><para> + +Recordeu que no <emphasis>forçosament heu</emphasis> de compilar el kernel +seguint el <quote>mètode Debian</quote>; però creiem que utilitzar el sistema +d'empaquetat per gestionar el nucli és la manera més segura i fàcil. De fet, +podeu descarregar el codi font del nucli directament del Linus en comptes +de <classname>kernel-source-&kernelversion;</classname>, ja que utilitza +el mètode de compilació <classname>kernel-package</classname>. + +</para><para> + +Recordeu que trobareu documentació respecte a la utilització de +<classname>kernel-package</classname> al directori +<filename>/usr/share/doc/kernel-package</filename>. Aquesta +secció únicament conté un petit tutorial. + +</para><para> + +S'assumeix que disposeu de llibertat absoluta sobre el vostre sistema i que +extraureu el codi font del nucli en algun lloc del vostre directori +personal<footnote> + +<para> + +Hi ha d'altres ubicacions on podeu extreure el codi font del nucli i generar +el vostre nucli personalitzat, però aquest és el més fàcil al no precisar +de permisos especials. + +</para> + +</footnote>. Assumirem que la vostra versió del nucli és &kernelversion;. +Assegureu-vos d'estar al directori on voleu desempaquetar el codi +font del nucli, extraieu-lo utilitzant l'ordre +<userinput>tar xjf /usr/src/kernel-source-&kernelversion;.tar.bz2</userinput> +i entreu al directori que s'haurà creat <filename>kernel-source-&kernelversion;</filename>. + +</para><para> + +Ja podeu configurar el nucli. Si teniu instal·lat, configurat i executant-se +l'X11, executeu l'ordre <userinput>make xconfig</userinput>; si no el teniu +instal·lat executeu l'ordre <userinput>make menuconfig</userinput> (haureu +de tenir instal·lat <classname>libncurses5-dev</classname>). Preneu-vos el +temps necessari per llegir l'ajuda en línia i seleccionar les opcions de +forma acurada. En cas de dubte, normalment és millor introduir el controlador +del dispositiu (el programari que gestiona els perifèrics com la targeta +Ethernet, controladors SCSI i similars). Recordeu que en cas de no entendre +d'altres opcions no relacionades amb un maquinari específic, les hauríeu de +deixar amb el valor predeterminat. No oblideu seleccionar l'opció +<quote>Carregador de mòduls del nucli</quote> a <quote>Suport de mòduls +carregables</quote> (per defecte no està seleccionat). En cas de no incloure +l'opció, hi hauria problemes amb la instal·lació de Debian. + +</para><para> + +Netegeu l'arrel del codi font i reinicia els paràmetres +<classname>kernel-package</classname>. Per a fer-ho, utilitzeu +l'ordre <userinput>make-kpkg clean</userinput>. + +</para><para> + +Seguidament heu de compilar el nucli: +<userinput>fakeroot make-kpkg --revision=custom.1.0 kernel_image</userinput>. +El número de versió <quote>1.0</quote> es pot modificar; és únicament +un número de versió que s'utilitzarà per registrar les generacions del nucli. +Podeu utilitzar qualsevol paraula enlloc de <quote>custom</quote> +(ex. un nom d'ordinador). La duració de la compilació del nucli +dependrà de la potència de l'ordinador. + +</para><para condition="supports-pcmcia"> + +Si necessiteu el suport per a PCMCIA, també haureu d'instal·lar el paquet +<classname>pcmcia-source</classname>. Desempaqueteu el fitxer gzip tar +com a superusuari al directori <filename>/usr/src</filename> (és important +que els mòduls es trobin allà on s'espera que es trobin, +<filename>/usr/src/modules</filename>). Seguidament, i com a superusuari, +heu d'executar l'ordre <userinput>make-kpkg modules_image</userinput>. + +</para><para> + +Un cop finalitzada la compilació, podeu instal·lar el nucli personalitzat +com qualsevol altre paquet. Heu d'executar, com a superusuari, l'ordre +<userinput>dpkg -i ../kernel-image-&kernelversion;-<replaceable>subarquitectura</replaceable>_custom.1.0_&architecture;.deb</userinput>. +La part <replaceable>subarquitectura</replaceable> és una subarquitectura +opcional +<phrase arch="i386"> com per exemple <quote>i586</quote>, </phrase> +en funció de les opcions del nucli seleccionades. + +L'ordre <userinput>dpkg -i kernel-image...</userinput> instal·larà el nucli, +juntament amb d'altres fitxers de suport. Per exemple, s'instal·larà +<filename>System.map</filename> (que serà d'ajuda en els problemes +de depuració del nucli), i també s'instal·larà el fitxer +<filename>/boot/config-&kernelversion;</filename> que contindrà el conjunt +d'opcions de configuració actuals. El paquet +<classname>kernel-image-&kernelversion;</classname> +és capaç d'utilitzar directament el carregador d'arrencada de la plataforma +per executar l'actualització en l'arrencada, possibilitant l'arrencada sense +la necessitat de tornar a executar el carregador d'arrencada. Si heu creat +un paquet de mòduls, ex. si diposeu de PCMCIA, també haureu d'instal·lar-lo. + +</para><para> + +És el moment de reiniciar el sistema: llegiu acuradament qualsevol avís +produït pel pas anterior i executeu l'ordre <userinput>shutdown -r now</userinput>. +</para><para> + +Per a veure més informació sobre <classname>kernel-package</classname> llegiu +la documentació del directori <filename>/usr/share/doc/kernel-package</filename>. + +</para> + </sect2> + </sect1> diff --git a/ca/post-install/new-to-unix.xml b/ca/post-install/new-to-unix.xml new file mode 100644 index 000000000..464f39289 --- /dev/null +++ b/ca/post-install/new-to-unix.xml @@ -0,0 +1,29 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 --> + + + <sect1 id="unix-intro"> + <title>Si sou nous a Unix</title> +<para> + +Si sou nous a Unix, probablement hauríeu de comprar alguns llibres i +llegir una mica. Es pot trobar informació molt útil a la +<ulink url="&url-debian-reference;">Guia de referència de Debian</ulink>. +La <ulink url="&url-unix-faq;">llista de PMF de Unix</ulink>, +que conté alguns documents de UseNet, és una bona referència històrica. + +</para><para> + +Linux és una implementació de Unix. El +<ulink url="&url-ldp;">Projecte de documentació de Linux (LDP)</ulink> +recull alguns COM ES FA (HOW TO) i llibres relacionats amb Linux. La +major part d'aquests documents es poden instal·lar localment; simplement +instal·leu el paquet <classname>doc-linux-html</classname> (versions +en format HTML) o el paquet <classname>doc-linux-text</classname> +(versions ASCII), i aleshores mireu +<filename>/usr/share/doc/HOWTO</filename>. Les versions internacionals +dels COM ES FA de LDP també estan disponibles com a paquets de Debian. + +</para> + + </sect1> diff --git a/ca/post-install/orientation.xml b/ca/post-install/orientation.xml new file mode 100644 index 000000000..b3057aebe --- /dev/null +++ b/ca/post-install/orientation.xml @@ -0,0 +1,110 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 --> + + + <sect1 id="debian-orientation"><title>Orientant-vos a Debian</title> +<para> + +Debian és una mica diferent d'altres distribucions. Fins i tot si esteu +familiaritzats amb altres distribucions Linux, hi ha coses que hauríeu +de saber sobre Debian, i que us poden ajudar a mantenir el vostre sistema +en bon estat i net. Aquest capítol conté material d'ajuda per +orientar-vos; no pretén ser un tutorial sobre com usar Debian, sinó un +breu cop d'ull al sistema per als més apressats. + +</para> + + <sect2><title>El sistema de paquets de Debian</title> +<para> + +El concepte més important que heu de comprendre és els sistema +d'empaquetament. Essencialment, considereu que la major part del vostre +sistema està sota el control del sistema de paquets. Això inclou: + +<itemizedlist> +<listitem><para> + +<filename>/usr</filename> (excloent <filename>/usr/local</filename>) + +</para></listitem> +<listitem><para> + +<filename>/var</filename> (podeu crear +<filename>/var/local</filename> sense risc) + +</para></listitem> +<listitem><para> + +<filename>/bin</filename> + +</para></listitem> +<listitem><para> + +<filename>/sbin</filename> + +</para></listitem> +<listitem><para> + +<filename>/lib</filename> + +</para></listitem> +</itemizedlist> + +Per exemple, si reemplaceu <filename>/usr/bin/perl</filename>, +funcionarà, però si aleshores actualitzeu el vostre paquet +<classname>perl</classname>, el fitxer que hi havia serà reemplaçat de +nou. Els més experts ho podeu evitar posant els paquets a «hold» +(mantenir) a l'<command>aptitude</command>. + +</para><para> + +Un dels millors mètodes d'instal·lació és apt. Podeu usar la versió de +línia de comandes <command>apt-get</command>, o bé la versió amb +interfície de text a pantalla completa <application>aptitude</application>. +Noteu que apt també us deixarà combinar main, contrib i non-free +de tal manera que podeu tenir paquets amb restriccions d'exportació +així com versions estàndard. + +</para> + </sect2> + + <sect2><title>Gestió de versions de les aplicacions</title> +<para> + +Les versions alternatives de les aplicacions es gestionen mitjançant +update-alternatives. Si manteniu múltiples versions dels vostres +programes, llegiu la pàgina del manual de update-alternatives. + +</para> + </sect2> + + <sect2><title>Gestió de tasques amb cron</title> +<para> + +Qualsevol tasca sota la supervisió de l'administrador del sistema ha +d'estar a <filename>/etc</filename>, on hi ha els fitxers de configuració. +Si teniu una tasca cron com a root, podeu posar-la a +<filename>/etc/cron.{daily,weekly,monthly}</filename> segons si voleu +que sigui diària, setmanal o mensual. Aquestes tasques seran +invocades des de <filename>/etc/crontab</filename>, i executades per +ordre alfabètic. + +</para><para> + +D'altra banda, si teniu una tasca que s'ha d'executar (a) com a un +usuari en concret o (b) en un moment específic o amb una freqüència +establerta, podeu usar <filename>/etc/crontab</filename>, o encara +millor, <filename>/etc/cron.d/qualsevol_cosa</filename>. Aquests fitxers +tenen un camp addicional que permet definir l'usuari que executarà +la tasca. + +</para><para> + +En qualsevol cas, simplement editeu els fitxers i cron se n'adonarà +automàticament. No hi ha cap necessitat d'executar comandes especials. +Per a més informació, consulteu cron(8), crontab(5), i +<filename>/usr/share/doc/cron/README.Debian</filename>. + +</para> + </sect2> + </sect1> diff --git a/ca/post-install/post-install.xml b/ca/post-install/post-install.xml new file mode 100644 index 000000000..6bc81e2ed --- /dev/null +++ b/ca/post-install/post-install.xml @@ -0,0 +1,14 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28715 --> + +<chapter id="post-install"> + <title>Següents passos i per on seguir</title> + +&new-to-unix.xml; +&orientation.xml; +&reactivating-win.xml; +&further-reading.xml; +&kernel-baking.xml; +&rescue.xml; + +</chapter> diff --git a/ca/post-install/reactivating-win.xml b/ca/post-install/reactivating-win.xml new file mode 100644 index 000000000..968e6483e --- /dev/null +++ b/ca/post-install/reactivating-win.xml @@ -0,0 +1,73 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 --> + + + <sect1 arch="i386" id="reactivating-win"> + <title>Reactivant DOS i Windows</title> +<para> + +Després d'instal·lar el sistema base i escriure el <emphasis>registre +mestre d'arrencada</emphasis> (MBR), podreu arrencar Linux, però +probablement res més. Això dependrà de les opcions triades durant la +instal·lació. Aquest capítol descriu com podeu reactivar el vostre sistema +operatiu antic, de tal manera que també pugueu arrencar DOS o Windows. + +</para><para> + +<command>LILO</command> és un gestor amb el que podeu arrencar altres +sistemes operatius, a més de Linux, que siguin compatibles amb PC. +Aquest gestor d'arrencada es configura mitjançant el fitxer +<filename>/etc/lilo.conf</filename>. Si voleu modificar la configuració, +haureu d'editar el fitxer, i tot seguit executar +<command>lilo</command>. Això és necessari, ja que els canvis només +es produiran quan crideu aquest programa. + +</para><para> + +Les parts importants del fitxer <filename>lilo.conf</filename> són les +línies que contenen les paraules <userinput>image</userinput> i +<userinput>other</userinput>, així com les línies que les segueixen. +Aquestes s'utilitzen per descriure els sistemes que són arrencables des +del <command>LILO</command>. Cada sistema pot incloure un nucli +(<userinput>image</userinput>), una partició arrel, paràmetres +addicionals del nucli, etc. També pot incloure la configuració per +arrencar un altre sistema operatiu que no sigui Linux +(<userinput>other</userinput>). Aquestes paraules clau poden ser usades +més d'una vegada. L'ordre dels sistemes al fitxer de configuració és +important, ja que aquest determina quin serà el sistema que arrencarà +automàticament; per exemple, després d'un cert temps d'espera +(<userinput>delay</userinput>), i suposant que el <command>LILO</command> +no sigui aturat prement la tecla <keycap>shift</keycap>. + +</para><para> + +Després d'una nova instal·lació de Debian, només el sistema actual està +configurat per arrencar amb el <command>LILO</command>. Si voleu arrencar +un altre nucli de Linux, podeu editar el fitxer de configuració +<filename>/etc/lilo.conf</filename> i afegir les següents línies: + +<informalexample><screen> +&additional-lilo-image; +</screen></informalexample> + +Per a una configuració bàsica, només necessitareu les dos primeres +línies. Si voleu saber més sobre altres opcions, si us plau, consulteu +la documentació de <command>LILO</command>. La podeu trobar a +<filename>/usr/share/doc/lilo/</filename>. El fitxer que hauríeu de +llegir és <filename>Manual.txt</filename>. Per a una introducció +ràpida al món de l'arrencada de sistemes, podeu mirar també les +pàgines del manual de <command>LILO</command>: +<filename>lilo.conf</filename> per a tenir una visió general de les +paraules clau i <filename>lilo</filename> per a una descripció de la +instal·lació de noves configuracions al registre d'arrencada. + +</para><para> + +Tingueu en compte que també hi ha altres gestors d'arrencada disponibles +a &debian;, com ara GRUB (al paquet <classname>grub</classname>), CHOS +(paquet <classname>chos</classname>), Extended-IPL +(<classname>extipl</classname>), loadlin +(<classname>loadlin</classname>), etc. + +</para> + </sect1> diff --git a/ca/post-install/rescue.xml b/ca/post-install/rescue.xml new file mode 100644 index 000000000..4f239be8e --- /dev/null +++ b/ca/post-install/rescue.xml @@ -0,0 +1,73 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28732 --> + + <sect1 id="rescue" condition="etch"> + <title>Restaurant un sistema amb errors</title> +<para> + +En alguns casos, les coses no acaben de funcionar correctament, i el sistema +que curosament heu instal·lat no es torna a arrencar. Probablement el +carregador de l'arrencada no s'hagi executat correctament durant la +comprovació d'un canvi, o potser el nucli instal·lat no s'arrenqui, o potser +els raigs còsmics hagin efectat el disc i hagin alterat un bit del fitxer +<filename>/sbin/init</filename>. Independentment de l'origen l'error, +necessiteu un sistema per treballar mentre no solucioneu el problema, +en aquesta situació el mode de rescat us pot ser útil. + +</para><para> + +<!-- TODO: describe what to do on arches where this isn't set up in the + bootloader --> + +Per accedir al mode de rescat, escriviu <userinput>rescue</userinput> a +l'indicador <prompt>boot:</prompt> o arrenqueu amb el paràmetre +d'arrencada <userinput>rescue/enable=true</userinput>. Us apareixeran les +primeres pantalles de l'instal·lador amb una nota a la cantonada indicant +que l'esteu executant en el mode de rescat, no realitzant una instal·lació +completa. No us preocupeu, no se us sobreescriurà el sistema! El mode de +rescat únicament aprofita les facilitats de detecció de maquinari disponibles +en l'instal·lador per assegurar que disposeu dels discs, dispositius de xarxa +i similars durant la reparació del sistema. + +</para><para> + +En comptes de l'eina de particionat, us hauria d'aparèixer una llista de +particions del sistema i demanar-vos que n'escolliu una. En la majoria dels +casos hauríeu de seleccionar la partició que contingui el sistema de fitxers +arrel que voleu reparar. Us seria possible seleccionar les particions en +els dispositius RAID i LVM i les creades directament als discs. + +</para><para> + +L'instal·lador intentarà donar-vos accés a l'indicador de l'intèrpret d'ordres +del sistema de fitxers seleccionat amb el qual intentar reparar el sistema. + +<phrase arch="i386"> +Per exemple, si heu de tornar a instal·lar el carregador d'arrencada GRUB +al registre d'arrencada del primer disc dur, podríeu utilitzar l'ordre +<userinput>grub-install '(hd0)'</userinput>. +</phrase> + +</para><para> + +Si l'instal·lador no pot executar un intèrpret d'ordres en el sistema +de fitxers arrel que heu seleccionat, pot ser que el primer contingui +errors, en aquest cas mostrarà un avís us permetrà utilitzar un intèrpret +d'ordres en l'entorn de l'instal·lador. En aquest entorn no disposareu +de tantes eines, però segurament seran suficient per solucionar l'error +del sistema. L'arrel del sistema de fitxers que heu seleccionat es muntarà +al directori <filename>/target</filename>. + +</para><para> + +En qualsevol cas, un cop sortiu de la línia d'ordres el sistema es +reiniciarà. + +</para><para> + +Com apunt final, recordeu que la reparació d'un sistema amb errors pot ser +difícil, i que aquest manual no pretén endinsar-se en totes les possibles +causes o solucions. Si teniu problemes, consulteu un expert. + +</para> + </sect1> diff --git a/ca/post-install/shutdown.xml b/ca/post-install/shutdown.xml new file mode 100644 index 000000000..684e064d8 --- /dev/null +++ b/ca/post-install/shutdown.xml @@ -0,0 +1,25 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 21690 --> + + + <sect1 id="shutdown"> + <title>Aturant el sistema</title> + +<para> + +Per aturar un sistema Linux, ni heu de reiniciar prement el botó de reset +de l'ordinador, ni heu de prémer el botó d'apagar. Per evitar que es +perdin fitxers o es produeixin errors al disc cal aturar-lo de manera +controlada. Podeu prémer la combinació de tecles <keycombo> +<keycap>Ctrl</keycap> <keycap>Alt</keycap> <keycap>Del</keycap> </keycombo> +<phrase arch="powerpc;m68k"> o en el cas del sistemes Macintosh +<keycombo> <keycap>Control</keycap> <keycap>Shift</keycap> +<keycap>Power</keycap> </keycombo></phrase>. + +En cas que les combinacions de tecles anteriors no funcionin correctament +o vulgueu escriure les ordres, podeu entrar com a superusuari i escriure +<userinput>shutdown -h now</userinput>, +<userinput>reboot</userinput>, o <userinput>halt</userinput>. + +</para> + </sect1> diff --git a/ca/preface.xml b/ca/preface.xml new file mode 100644 index 000000000..395319996 --- /dev/null +++ b/ca/preface.xml @@ -0,0 +1,32 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 24750 --> + +<preface> + <title>Instal·lació de la versió &release; del sistema &debian; per a l'arquitectura &architecture;</title> +<para> + +Ens alegrem que us hageu decidit a provar Debian i estem segurs que +trobareu que la distribució Debian de GNU/Linux és única. &debian; +aporta l'alta qualitat del programari lliure d'arreu del món, +integrat en un conjunt coherent. Creiem que descobrireu que els +seus resultats són, veritablement, quelcom més que una simple +recopilació. + +</para><para> + +Entenem que molts de vosaltres voleu instal·lar Debian sense haver +de llegir aquest manual, i l'instal·lador de Debian ho contempla. Si +no disposeu del temps necessari per llegir la Guia d'instal·lació, +us recomanem que llegiu el document "Com instal·lar-lo", que us +guiarà a través del procés d'instal·lació bàsic i que fa referència +al manual pels temes més avançats o en cas d'error. El document +"Com instal·lar-lo" el podeu trobar a <xref linkend="installation-howto"/>. + +</para><para> + +Dit això, esperem que disposeu del temps necessari per llegir la +major part del manual, ja que, probablement, això us permetrà una +instal·lació probablement més satisfactòria i amb més informació. + +</para> +</preface> diff --git a/ca/preparing/backup.xml b/ca/preparing/backup.xml new file mode 100644 index 000000000..dd817bb13 --- /dev/null +++ b/ca/preparing/backup.xml @@ -0,0 +1,40 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 --> + + <sect1 id="backup"> + <title>Feu còpia de seguretat de les vostres dades!</title> +<para> + +Abans de començar, assegureu-vos de fer còpia de tots els fitxers del +vostre sistema. Si és la primera vegada que instal·leu un sistema operatiu +no natiu al vostre ordinador, és molt probable que necessiteu reparticionar +el vostre disc per fer espai per &debian;. Compteu en que cada vegada que +particioneu el vostre disc, perdreu tot el que hi ha al disc, independentment +del programa que utilitzeu. Els programes utilitzats a la instal·lació són +molt segurs i tenen molts anys d'ús, però són també molt potents i un moviment +en fals pot costar-vos car. Dos minuts de pensar pot estalviar hores de +treball innecessari. + +</para><para> + +Si esteu creant un sistema multi-arrencada, assegureu-vos de tenir els +mitjans de distribució de qualsevol altre sistema operatiu que tingueu a ma. +Especialment si reparticioneu el vostre disc d'arrencada, podríeu trobar-vos +en la situació d'haver de reinstal·lar el carregador del vostre sistema +operatiu, o en altres casos el sistema operatiu complet i tots els arxius +afectats pels canvis a les particions. + +</para> + +<para arch="m68k"> + +Amb l'excepció dels ordinadors BVM i Motorola VMEbus, l'únic mètode +d'instal·lació suportat pels sistemes m68k és arrencar des del disc local +o la disquetera utilitzant un arranc basat en AmigaOS/TOS/MacOS, en +aquestes màquines necessitareu el sistema operatiu original per arrencar +Linux. Per arrencar Linux a les maquines BVM i Motorola VMEbus necessitareu +les ROM d'arrencada «BVMBug» o «16xBug». + +</para> + + </sect1> diff --git a/ca/preparing/bios-setup/i386.xml b/ca/preparing/bios-setup/i386.xml new file mode 100644 index 000000000..dd0d4413b --- /dev/null +++ b/ca/preparing/bios-setup/i386.xml @@ -0,0 +1,330 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 --> + + + <sect2 arch="i386" id="bios-setup"><title>Invocant el Menú de configuració de la BIOS</title> + +<para> + +La BIOS proveeix les funcions bàsiques que es necessiten per arrencar la +vostra màquina per permetre al vostre sistema operatiu accedir al maquinari. +El vostre sistema probablement proveeix un menú de configuració que s'utilitza +per configurar la BIOS. Abans d'instal·lar, <emphasis>assegureu-vos</emphasis> +que la vostra BIOS està correctament configurada; no fer-ho pot portar a +fallades intermitents que incapacite per instal·lar Debian. + +</para><para> + +La resta d'aquesta secció s'ha agafat de +<ulink url="&url-pc-hw-faq;"></ulink>, responent a la pregunta, +«Com entre al menú de configuració del CMOS?». Si accediu al menú de +configuració de la BIOS (o «CMOS») depèn del programador del programari +de la BIOS: + +</para> + +<!-- From: burnesa@cat.com (Shaun Burnet) --> +<variablelist> + +<varlistentry> + <term>AMI BIOS</term> + <listitem><para> + +Tecla <keycap>Supr</keycap> al POST (prova d'autoverificació a l'arrencada) + +</para></listitem> +</varlistentry> + +<varlistentry> + <term>Award BIOS</term> + <listitem><para> + +Tecles +<keycombo> + <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Esc</keycap> +</keycombo>, o <keycap>Supr</keycap> al POST + +</para></listitem> +</varlistentry> + +<varlistentry><term>DTK BIOS</term> + <listitem><para> + +Tecla <keycap>Esc</keycap> al POST + +</para></listitem> +</varlistentry> + +<varlistentry><term>IBM PS/2 BIOS</term> + <listitem><para> + +Tecles +<keycombo> + <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Insert</keycap> +</keycombo> +després +<keycombo> + <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Supr</keycap> +</keycombo> + +</para></listitem> +</varlistentry> + +<varlistentry> + <term>Phoenix BIOS</term> + <listitem><para> +Tecles +<keycombo> + <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Esc</keycap> +</keycombo> +o +<keycombo> + <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>S</keycap> +</keycombo> +o +<keycap>F1</keycap> + +</para></listitem> +</varlistentry> +</variablelist> + +<para> + +Podeu trobar més informació de com activar altres rutines de BIOS a +<ulink url="&url-invoking-bios-info;"></ulink>. + +</para><para> + +Algunes màquines &arch-title; no tenen menú de configuració a la BIOS. +Aquestes necessiten d'un programa de configuració del CMOS. Si no teniu +el disc d'instal·lació i/o diagnòstics, podeu provar a utilitzar programari +de prova o programari gratuït. Proveu de buscar a +<ulink url="&url-simtel;"></ulink>. + +</para> + </sect2> + + <sect2 arch="i386" id="boot-dev-select"><title>Selecció del dispositiu d'arrencada</title> + +<para> + +Molts menús de configuració de les BIOS permeten seleccionar els dispositius +que s'utilitzaran per iniciar el sistema. Canvieu-ho per buscar un sistema +operatiu arrencable a <filename>A:</filename> (el primer disquet), +aleshores opcionalment el primer CD-ROM (possiblement amb el nom +<filename>D:</filename> o <filename>E:</filename>), i aleshores de +<filename>C:</filename> (el primer dur). Aquests paràmetres permeten +l'arrencada del disquet o CD-ROM, que són dos dels més comuns dispositius +d'arrencada per instal·lar Debian. + +</para><para> + +Si disposeu d'una controladora SCSI nova i disposeu d'un CD-ROM +connectat a ella, normalment podreu arrencar del CD-ROM. Tot el +que heu de fer és habilitar l'arrencada del CD-ROM a la BIOS de +la vostra controladora SCSI. + +</para><para> + +Altra opció freqüent és arrencar d'un dispositiu emmagatzemament USB +(també es diu llapis de memòria o clau USB). +Algunes BIOS poden arrencar directament d'un dispositiu USB, i d'altres no. +Podríeu necessitar configurar la vostra BIOS per que arrenqués des d'un +<quote>disc extraïble</quote> o bé d'un <quote>USB-ZIP</quote> per poder +arrencar del dispositiu USB. + +</para><para> + +Ací trobareu alguns detalls de com triar l'ordre d'arrencada. Recordeu +de canviar l'ordre d'arrencada després d'instal·lar Linux per poder +reiniciar el vostre ordinador des del disc dur. + +</para> + + <sect3 id="ctbooi"> + <title>Canviant l'ordre d'arrencada a ordinadors IDE</title> + +<orderedlist> +<listitem><para> + +Quan s'engegue el vostre ordinador, premeu les tecles per entrar a +la BIOS. Sovint, és la tecla <keycap>Supr</keycap>. Consulteu la +documentació del vostre maquinari per conèixer les tecles exactes. + +</para></listitem> +<listitem><para> + +Busqueu l'ordre d'arrencada a la vostra utilitat de configuració. El lloc +on es trobe depèn de la vostra BIOS, però heu de buscar un camp que te una +llista de discs. + +</para><para> + +Les opcions més comuns a maquines IDE són C, A, CD-ROM o A, C, CD-ROM. + +</para><para> + +C és el disc dur, i A és el disquet. + +</para></listitem> +<listitem><para> + +Canvieu l'ordre d'arrencada de manera que tingueu primer el +CD-ROM o el disquet. Normalment, les tecles <keycap>Re Pàg</keycap> o +<keycap>Av Pàg</keycap> van desplaçant-se per les opcions possibles. + +</para></listitem> +<listitem><para> + +Deseu els vostres canvis. Les instruccions a la pantalla us diran com +desar els canvis al vostre ordinador. + +</para></listitem> +</orderedlist> + </sect3> + + <sect3 id="ctboos"> + <title>Canviant l'ordre d'arrencada a màquines SCSI</title> +<para> + +<orderedlist> +<listitem><para> + +Quan el vostre ordinador comença, premeu les tecles per entrar a la +utilitat de configuració SCSI. + +</para><para> + +Podeu arrencar la utilitat de configuració SCSI desprès de comprovar la +memòria i veure el missatge de com arrencar la utilitat de la BIOS a l'arrencar +l'ordinador. + +</para><para> + +Les combinacions de tecles depenen de la utilitat. Sovint són +<keycombo><keycap>Ctrl</keycap><keycap>F2</keycap></keycombo>. +Consulteu la documentació del vostre maquinari per conèixer les +combinacions de tecles exactes. + +</para></listitem> +<listitem><para> + +Busqueu la utilitat per canviar l'ordre d'arrencada. + +</para></listitem> +<listitem><para> + +Configureu la utilitat de forma que el SCSI IDE del CD estigui al primer +lloc a la llista. + +</para></listitem> +<listitem><para> + +Deseu els canvis. Les instruccions a la pantalla us diran com +desar els canvis al vostre ordinador. Sovint es tracta de +<keycap>F10</keycap>. + +</para></listitem> +</orderedlist> + +</para> + </sect3> + </sect2> + + <sect2 arch="i386"> + <title>Paràmetres de la BIOS miscel·lànies</title> + + <sect3 id="cd-settings"><title>Paràmetres del CD-ROM</title> +<para> + +Algunes BIOS (com les BIOS Award) permeten fixar la velocitat del CD. +Eviteu-ho, i poseu la velocitat mínima. Si trobeu missatges d'error +<userinput>seek failed</userinput>, aquest podria ser el vostre problema. + +</para> + </sect3> + + <sect3><title>Memòria estesa vs. memòria expandida</title> +<para> + +Si el vostre sistema proveeix les dos, memòria estesa i +expandida, configureu-ho de manera que tingueu el màxim possible +d'estesa i el mínim possible d'expandida. Linux necessita +memòria estesa i no pot fer ús de memòria expandida. + +</para> + </sect3> + + <sect3><title>Protecció davant virus</title> +<para> + +Deshabiliteu qualsevol característica d'avís davant virus que pugui donar-vos +la vostra BIOS. Si teniu una placa base o altre maquinari especial, +assegureu-vos que s'ha deshabilitat o extraieu-la físicament mentre executeu +GNU/Linux. Aquestes no són compatibles amb GNU/Linux; és més, pels permisos del +sistema de fitxers i la memòria protegida del nucli de Linux, pràcticament no +es coneixen virus<footnote> +<para> + +Després de la instal·lació podeu activar la protecció del sector d'arrencada +si voleu. Açò no és cap mesura addicional de seguretat a Linux, però si +utilitzeu Windows, pot prevenir una catàstrofe. No hi ha necessitat de +utilitzar el Master Boot Record (MBR) desprès de configurar el gestor +d'arrencada. + +</para> +</footnote>. + +</para> + </sect3> + + <sect3><title>«Shadow RAM»</title> +<para> + +La vostra placa base pot facilitar <emphasis>shadow RAM</emphasis> o +memòria cau per la BIOS. Podeu veure els paràmetres per «Video BIOS Shadow», +«C800-CBFF Shadow», etc. <emphasis>Deshabiliteu</emphasis> tota la +«shadow RAM». La «shadow RAM» s'utilitza per accelerar l'accés a les ROM a +la vostra placa base i a algunes targes controladores. Linux no utilitza +questes ROM després d'arrencar ja que dona el seu programari de 32 bits en +lloc del programari de 16 bits de les ROM. Deshabilitar la «shadow RAM» +podria convertir-la en disponible per a programes com memòria normal. +Deixar activada la «shadow RAM» podria interferir amb l'accés que fa Linux +als dispositius físics. + +</para> + </sect3> + + <sect3><title>«Memory Hole»</title> +<para> + +Si la vostra BIOS us ofereix alguna cosa com «15–16 MB Memory Hole», +desactiveu-ho. Linux espera trobar memòria allí si té aquesta RAM. + +</para><para> + +Es coneix de una placa base Intel Endeavor, la que te una opció que +diu «LFB» o «Linear Frame Buffer». Te dos opcions: «Disabled» i +«1 Megabyte». Configureu-ho a «1 Megabyte». Quan l'opció està +deshabilitada, el disquet d'instal·lació no es llegeix correctament i el +sistema acaba fallant. En el moment d'escriure aquest document, no s'enten +que passa amb aquest dispositiu en particular — tan sols funciona amb +aquesta opció i no sense ella. + +</para> + </sect3> + +<!-- no other platforms other than x86 provide this sort of thing, AFAIK --> + + <sect3><title>Gestió avançada d'energia</title> +<para> + +Si la vostra placa base proveeix gestió avançada d'energia (APM), +configureu de forma que la gestió d'energia es controle mitjançant APM. +Deshabiliteu els modes «doze», «standby», «suspend», «nap», «sleep» i +deshabiliteu el temporitzador d'apagat del disc. Linux pot controlar +aquestos modes, i pot fer una millor gestió de l'energia que la BIOS. + +</para> + </sect3> + </sect2> diff --git a/ca/preparing/bios-setup/m68k.xml b/ca/preparing/bios-setup/m68k.xml new file mode 100644 index 000000000..e68cb35d7 --- /dev/null +++ b/ca/preparing/bios-setup/m68k.xml @@ -0,0 +1,23 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 untranslated --> + + + <sect2 arch="m68k" id="firmware-revs"> + <title>Firmware Revisions and Existing OS Setup</title> + +<para> + +&arch-title; machines are generally self-configuring and do not require +firmware configuration. However, you should make sure that you have +the appropriate ROM and system patches. On the Macintosh, MacOS +version >= 7.1 is recommended because version 7.0.1 contains a bug in +the video drivers preventing the boot loader from deactivating the +video interrupts, resulting in a boot hang. On the BVM VMEbus systems +you should make sure you are using BVMBug revision G or higher boot ROMs. +The BVMBug boot ROMs do not come as standard on the BVM systems but are +available from BVM on request free of charge. + +</para> + + </sect2> + diff --git a/ca/preparing/bios-setup/powerpc.xml b/ca/preparing/bios-setup/powerpc.xml new file mode 100644 index 000000000..2368a0853 --- /dev/null +++ b/ca/preparing/bios-setup/powerpc.xml @@ -0,0 +1,52 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 untranslated --> + + + <sect2 arch="powerpc" id="invoking-openfirmware"> + <title>Invoking OpenFirmware</title> +<para> + +There is normally no need to set up the BIOS (called OpenFirmware) on +&arch-title; systems. PReP and CHRP are equipped with OpenFirmware, +but unfortunately, the means you use to invoke it vary from +manufacturer to manufacturer. You'll have to consult the hardware +documentation which came with your machine. + +</para><para> + +On &arch-title; Macintoshes, you invoke OpenFirmware with +<keycombo><keycap>Command</keycap> <keycap>option</keycap> +<keycap>O</keycap> <keycap>F</keycap></keycombo> while booting. Generally it +will check for these keystrokes after the chime, but the exact timing +varies from model to model. See +<ulink url="&url-netbsd-powerpc-faq;"></ulink> for more hints. + +</para><para> + +The OpenFirmware prompt looks like this: + +<informalexample><screen> +ok +0 > +</screen></informalexample> + +Note that on older model &arch-title; Macs, the default and sometimes +hardwired I/O for OpenFirmware user interaction is through the serial +(modem) port. If you invoke OpenFirmware on one of these machines, you +will just see a black screen. In that case, a terminal program running +on another computer, connected to the modem port, is needed to +interact with OpenFirmware. + +</para><para> + +The OpenFirmware on OldWorld Beige G3 machines, OF versions 2.0f1 +and 2.4, is broken. These machines will most likely not be able to +boot from the hard drive unless the firmware is patched. A firmware +patch is included in the <application>System Disk 2.3.1</application> +utility, available from Apple at +<ulink url="ftp://ftp.apple.com/developer/macosxserver/utilities/SystemDisk2.3.1.smi.bin"></ulink>. +After unpacking the utility in MacOS, and launching it, select the +Save button to have the firmware patches installed to nvram. + +</para> + </sect2> diff --git a/ca/preparing/bios-setup/s390.xml b/ca/preparing/bios-setup/s390.xml new file mode 100644 index 000000000..b2ed18855 --- /dev/null +++ b/ca/preparing/bios-setup/s390.xml @@ -0,0 +1,106 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 untranslated --> + + + <sect2 arch="s390"><title>BIOS Setup</title> +<para> + +In order to install &debian; on a &arch-title; or zSeries +machine you have first boot a kernel into the system. The boot +mechanism of this platform is inherently different to other ones, +especially from PC-like systems: there are no floppy devices available +at all. You will notice another big difference while you work with +this platform: most (if not all) of the time you will work remote, +with the help of some client session software like telnet, or a +browser. This is due to that special system architecture where the +3215/3270 console is line-based instead of character-based. + +</para><para> + +Linux on this platform runs either natively on the bare machine, in a +so-called LPAR (Logical Partition) or in a virtual machine supplied by +the VM system. You can use a boot tape on all of those systems; you +may use some other boot media, too, but those may not be generally +available. For example, you can use the virtual card reader of a +virtual machine, or boot from the HMC (Hardware Management Console) of +an LPAR if the HMC and this option is available for you. + +</para><para> + +Before you actually perform an installation, you have to go over some +design and preparation steps. IBM has made documentation available +about the whole process, e.g. how to prepare an installation medium +and how actually boot from that medium. Duplicating that information +here is neither possible nor necessary. However, we will describe +here which kind of Debian-specific data is needed and where do you +find them. Based on both sources of information you have to prepare +your machine and the installation medium and to perform a boot from +it. When you see the welcome message in your client session join this +document again for the Debian-specific installation steps. + +</para> + </sect2> + + <sect2 arch="s390"> + <title>Native and LPAR installations</title> +<para> + +Please refer to chapter 5 of the +<ulink url="http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg244987.pdf"> +Linux for &arch-title;</ulink> +Redbook and chapter 3.2 of the +<ulink url="http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf"> +Linux for IBM eServer zSeries and &arch-title;: Distributions</ulink> +Redbook on how to set up an LPAR for Linux. + +</para> + </sect2> + + <sect2 arch="s390"> + <title>Installation as a VM guest</title> + +<para> + +Please refer to chapter 6 of the +<ulink url="http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg244987.pdf"> +Linux for &arch-title;</ulink> +Redbook and chapter 3.1 of the +<ulink url="http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf"> +Linux for IBM eServer zSeries and &arch-title;: Distributions</ulink> +Redbook on how to set up a VM guest for running Linux. + +</para><para> + +You need to copy all the files from the <filename>generic</filename> +sub-directory to your CMS disk. Be sure to transfer +<filename>kernel.debian</filename> and +<filename>initrd.debian</filename> in binary mode with a fixed record +length of 80 characters. + +</para> + </sect2> + + <sect2 arch="s390"> + <title>Setting up an installation server</title> + +<para> + +If you don't have a connection to the Internet (either directly or via +a web proxy) you need to create a local installation server that can +be accessed from your S/390. This server keeps all the packages +you want to install and must make them available using NFS, HTTP or +FTP. + +</para><para> + +The installation server needs to copy the exact directory structure +from any &debian; mirror but of only the s390 and +architecture-independent files are required. You can also copy the +contents of all installation CDs into such a directory tree. + +</para><para condition="FIXME"> + +<emphasis>FIXME: more information needed — from a Redbook?</emphasis> + +</para> + </sect2> diff --git a/ca/preparing/bios-setup/sparc.xml b/ca/preparing/bios-setup/sparc.xml new file mode 100644 index 000000000..591ea1415 --- /dev/null +++ b/ca/preparing/bios-setup/sparc.xml @@ -0,0 +1,103 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 untranslated --> + + + <sect2 arch="sparc" id="invoking-openboot"><title>Invoking OpenBoot</title> + +<para> + +OpenBoot provides the basic functions needed to boot the &arch-title; +architecture. This is rather similar in function to the BIOS in the +x86 architecture, although much nicer. The Sun boot PROMs have a +built-in forth interpreter which lets you do quite a number of things +with your machine, such as diagnostics, simple scripts, etc. + +</para><para> + +To get to the boot prompt you need to hold down the +<keycap>Stop</keycap> key (on older type 4 keyboards, use the +<keycap>L1</keycap> key, if you have a PC keyboard adapter, use +the <keycap>Break</keycap> key) and press the +<keycap>A</keycap> key. The boot PROM will give you a prompt, +either <userinput>ok</userinput> or <userinput>></userinput>. It is +preferred to have the <userinput>ok</userinput> prompt. So if you get +the old style prompt, hit the <keycap>n</keycap> key to get the new +style prompt. + +</para><para> + +If you are using a serial console, send a break to the machine. With Minicom, +use <keycap>Ctrl-A F</keycap>, with cu, hit <keycap>Enter</keycap>, then type +<userinput>%~break</userinput>. Consult the documentation of your terminal +emulator if you are using a different program. + +</para> + </sect2> + + <sect2 arch="sparc" id="boot-dev-select-sun"> + <title>Boot Device Selection</title> + +<para> + +You can use OpenBoot to boot from specific devices, and also to change +your default boot device. However, you need to know some details +about how OpenBoot names devices; it's much different from Linux +device naming, described in <xref linkend="device-names"/>. +Also, the command will vary a bit, depending on what version of +OpenBoot you have. More information about OpenBoot can be found in +the <ulink url="&url-openboot;">Sun OpenBoot Reference</ulink>. + +</para><para> + +Typically, with newer revisions, you can use OpenBoot device such as +<quote>floppy</quote>, <quote>cdrom</quote>, <quote>net</quote>, +<quote>disk</quote>, or <quote>disk2</quote>. These have the obvious +meanings; the <quote>net</quote> device is for booting from the network. +Additionally, the device name can specify a particular partition of a disk, +such as <quote>disk2:a</quote> to boot disk2, first partition. Full +OpenBoot device names have the form + +<informalexample> +<screen> +<replaceable>driver-name</replaceable>@ +<replaceable>unit-address</replaceable>: +<replaceable>device-arguments</replaceable> +</screen></informalexample>. + +In older revisions of OpenBoot, device naming is a bit different: the +floppy device is called <quote>/fd</quote>, and SCSI disk devices are of +the form <quote>sd(<replaceable>controller</replaceable>, +<replaceable>disk-target-id</replaceable>, +<replaceable>disk-lun</replaceable>)</quote>. The command +<userinput>show-devs</userinput> in newer OpenBoot revisions is useful +for viewing the currently configured devices. For full information, +whatever your revision, see the +<ulink url="&url-openboot;">Sun OpenBoot Reference</ulink>. + +</para><para> + +To boot from a specific device, use the command <userinput>boot +<replaceable>device</replaceable></userinput>. You can set this +behavior as the default using the <userinput>setenv</userinput> +command. However, the name of the variable to set changed between +OpenBoot revisions. In OpenBoot 1.x, use the command +<userinput>setenv boot-from +<replaceable>device</replaceable></userinput>. In later revisions of +OpenBoot, use the command <userinput>setenv boot-device +<replaceable>device</replaceable></userinput>. Note, this is also +configurable using the <command>eeprom</command> command on Solaris, +or modifying the appropriate files in +<filename>/proc/openprom/options/</filename>, for example under Linux: + +<informalexample><screen> +# echo disk1:1 > /proc/openprom/options/boot-device +</screen></informalexample> + +and under Solaris: + +<informalexample><screen> +eeprom boot-device=disk1:1 +</screen></informalexample> + +</para> + </sect2> diff --git a/ca/preparing/install-overview.xml b/ca/preparing/install-overview.xml new file mode 100644 index 000000000..0b2f57a41 --- /dev/null +++ b/ca/preparing/install-overview.xml @@ -0,0 +1,185 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 untranslated --> + + <sect1 id="install-overview"> + <title>Overview of the Installation Process</title> +<para> + +First, just a note about re-installations. With Debian, a +circumstance that will require a complete re-installation of your +system is very rare; perhaps mechanical failure of the hard disk would +be the most common case. + +</para><para> + +Many common operating systems may require a complete installation to +be performed when critical failures take place or for upgrades to new +OS versions. Even if a completely new installation isn't required, +often the programs you use must be re-installed to operate properly in +the new OS. + +</para><para> + +Under &debian;, it is much more likely that your OS can be repaired +rather than replaced if things go wrong. Upgrades never require a +wholesale installation; you can always upgrade in-place. And the +programs are almost always compatible with successive OS releases. If +a new program version requires newer supporting software, the Debian +packaging system ensures that all the necessary software is +automatically identified and installed. The point is, much effort has +been put into avoiding the need for re-installation, so think of it as +your very last option. The installer is <emphasis>not</emphasis> +designed to re-install over an existing system. + +</para><para> + +Here's a road map for the steps you will take during the installation +process. + +</para> + +<orderedlist> +<listitem><para> + +Back up any existing data or documents on the hard disk where you +plan to install. + +</para></listitem> +<listitem><para> + +Gather information about your computer and any needed documentation, +before starting the installation. + +</para></listitem> +<listitem><para> + +Create partition-able space for Debian on your hard disk. + +</para></listitem> +<listitem><para> + +Locate and/or download the installer software and any specialized +driver files your machine requires (except Debian CD users). + +</para></listitem> +<listitem><para> + +Set up boot tapes/floppies/USB sticks, or place boot files (most Debian +CD users can boot from one of the CDs). + +</para></listitem> +<listitem><para> + +Boot the installation system. + +</para></listitem> +<listitem arch="not-s390"><para> + +Select installation language. + +</para></listitem> +<listitem arch="not-s390"><para> + +Activate the ethernet network connection, if available. + +</para></listitem> + +<listitem arch="s390"><para> + +Configure one network interface. + +</para></listitem> +<listitem arch="s390"><para> + +Open a ssh connection to the new system. + +</para></listitem> +<listitem arch="s390"><para> + +Attach one or more DASDs (Direct Access Storage Device). + +</para></listitem> + +<listitem><para> + +Create and mount the partitions on which Debian will be installed. + +</para></listitem> +<listitem><para> + +Watch the automatic download/install/setup of the +<firstterm>base system</firstterm>. + +</para></listitem> +<listitem><para> + +Install a <firstterm>boot loader</firstterm> +which can start up &debian; and/or your existing system. + +</para></listitem> +<listitem><para> + +Load the newly installed system for the first time, and make some +initial system settings. + +</para></listitem> +<listitem arch="s390"><para> + +Open a ssh connection to the new system. + +</para></listitem> +<listitem><para> + +Install additional software (<firstterm>tasks</firstterm> +and/or <firstterm>packages</firstterm>), at your discretion. + +</para></listitem> +</orderedlist> + +<para> + +If you have problems during the installation, it helps to know which +packages are involved in which steps. Introducing the leading software +actors in this installation drama: + +</para><para> + +The installer software, <classname>debian-installer</classname>, is +the primary concern of this manual. It detects hardware and loads +appropriate drivers, uses <classname>dhcp-client</classname> to set up the +network connection, and runs <classname>debootstrap</classname> to install +the base system packages. Many more actors play smaller parts in this process, +but <classname>debian-installer</classname> has completed its task when +you load the new system for the first time. + +</para><para> + +Upon loading the new base system, <classname>base-config</classname> +supervises adding users, setting a time zone (via +<classname>tzsetup</classname>), and setting up the +package installation system (using <classname>apt-setup</classname>). It then +launches <classname>tasksel</classname> which can be used to select large +groups of related programs, and in turn can run <classname>aptitude</classname> +which allows you to choose individual software packages. + +</para><para> + +When <classname>debian-installer</classname> finishes, before the +first system load, you have only a very basic command line driven +system. The graphical interface which displays windows on your monitor +will not be installed unless you select it during the final steps, +with either <classname>tasksel</classname> or +<classname>aptitude</classname>. It's optional because many &debian; +systems are servers which don't really have any need for a graphical +user interface to do their job. + +</para><para arch="not-s390"> + +Just be aware that the X system is completely separate from +<classname>debian-installer</classname>, and in fact is much more +complicated. Installation and trouble shooting of the X window +installation is not within the scope of this manual. + +</para> + </sect1> + diff --git a/ca/preparing/minimum-hardware-reqts.xml b/ca/preparing/minimum-hardware-reqts.xml new file mode 100644 index 000000000..763e92e70 --- /dev/null +++ b/ca/preparing/minimum-hardware-reqts.xml @@ -0,0 +1,135 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 untranslated --> + + <sect1 id="minimum-hardware-reqts"> +<title>Meeting Minimum Hardware Requirements</title> +<para> + +Once you have gathered information about your computer's hardware, +check that your hardware will let you do the type of installation +that you want to do. + +</para><para arch="not-s390"> + +Depending on your needs, you might manage with less than some of the +recommended hardware listed in the table below. However, most users +risk being frustrated if they ignore these suggestions. + +</para><para arch="i386"> + +A Pentium 100 is the minimum recommended for desktop +systems, and a Pentium II-300 for a Server. + +</para><para arch="m68k"> + +A 68030 or better processor is recommended for m68k +installs. You may get by with a little less drive space than shown. + +</para><para arch="powerpc"> + +Any OldWorld or NewWorld PowerPC can serve well +as a Desktop System. For servers, a minimum 132-Mhz machine is +recommended. + +</para> + +<table> +<title>Recommended Minimum System Requirements</title> +<tgroup cols="3"> +<thead> +<row> + <entry>Install Type</entry><entry>RAM</entry><entry>Hard Drive</entry> +</row> +</thead> + +<tbody> +<row> + <entry>No desktop</entry> + <entry>24 megabytes</entry> + <entry>450 megabytes</entry> +</row><row> + <entry>With Desktop</entry> + <entry>64 megabytes</entry> + <entry>1 gigabyte</entry> +</row><row> + <entry>Server</entry> + <entry>128 megabytes</entry> + <entry>4 gigabytes</entry> +</row> + +</tbody></tgroup></table> + +<para> + +Here is a sampling of some common Debian system configurations. +You can also get an idea of the disk space used by related groups +of programs by referring to <xref linkend="tasksel-size-list"/>. + +</para> +<variablelist> + +<varlistentry> + <term>Standard Server</term> + <listitem><para> + +This is a small server profile, useful for a stripped down server +which does not have a lot of niceties for shell users. It includes an +FTP server, a web server, DNS, NIS, and POP. For these 100MB of disk +space would suffice, and then you would need to add space +for any data you serve up. + +</para></listitem> +</varlistentry> + +<varlistentry arch="not-s390"> + <term>Desktop</term> + <listitem><para> + +A standard desktop box, including the X window system, full desktop +environments, sound, editors, etc. You'll need about 2GB using the +standard desktop task, though it can be done in far less. + +</para></listitem> +</varlistentry> + +<varlistentry arch="not-s390"> + <term>Work Console</term> + <listitem><para> + +A more stripped-down user machine, without the X window system or X +applications. Possibly suitable for a laptop or mobile computer. The +size is around 140MB. + +</para></listitem> +</varlistentry> + +<varlistentry> + <term>Developer</term> + <listitem><para> + +A desktop setup with all the development packages, such as Perl, C, +C++, etc. Size is around 475MB. Assuming you are adding X11 and some +additional packages for other uses, you should plan around 800MB for +this type of machine. + +</para></listitem> +</varlistentry> + +</variablelist><para> + +Remember that these sizes don't include all the other materials which +are usually to be found, such as user files, mail, and data. It is +always best to be generous when considering the space for your own +files and data. Notably, the <filename>/var</filename> partition contains +a lot of state information specific to Debian in addition to its regular +contents like logfiles. The +<command>dpkg</command> files (with information on all installed +packages) can easily consume 20MB. Also, +<command>apt-get</command> puts downloaded packages here before they are +installed. You should +usually allocate at least 100MB for <filename>/var</filename>. + +</para> + + </sect1> + diff --git a/ca/preparing/needed-info.xml b/ca/preparing/needed-info.xml new file mode 100644 index 000000000..c3ccc9b5c --- /dev/null +++ b/ca/preparing/needed-info.xml @@ -0,0 +1,397 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 untranslated --> + + <sect1 id="needed-info"> + <title>Information You Will Need</title> + + <sect2> + <title>Documentation</title> + + <sect3> + <title>Installation Manual</title> + +<para> + +This file you are now reading, in plain ASCII, HTML or PDF format. + +</para> + +<itemizedlist> + +&list-install-manual-files; + +</itemizedlist> +</sect3> + + + <sect3><title>Hardware documentation</title> +<para> + +Often contains useful information on configuring or using your hardware. + +</para> + + <!-- We need the arch dependence for the whole list to ensure proper xml + as long as not architectures have a paragraph --> + <itemizedlist arch="i386;m68k;alpha;sparc;mips;mipsel"> +<listitem arch="i386"><para> + +<ulink url="&url-hardware-howto;">Linux Hardware Compatibility HOWTO</ulink> + +</para></listitem> + +<listitem arch="m68k"><para> + +<ulink url="&url-m68k-faq;">Linux/m68k FAQ</ulink> + +</para></listitem> + +<listitem arch="alpha"><para> + +<ulink url="&url-alpha-faq;">Linux/Alpha FAQ</ulink> + +</para></listitem> + +<listitem arch="sparc"><para> + +<ulink url="&url-sparc-linux-faq;">Linux for SPARC Processors FAQ</ulink> + +</para></listitem> + +<listitem arch="mips;mipsel"><para> + +<ulink url="&url-mips-howto;">Linux/Mips Howto</ulink> + +</para></listitem> + +</itemizedlist> + </sect3> + + + <sect3 arch="s390"> + <title>&arch-title; Hardware References</title> +<para> + + +Installation instructions and device drivers (DASD, XPRAM, Console, + tape, z90 crypto, chandev, network) for Linux on &arch-title; using + kernel 2.4 + +</para> + +<itemizedlist> +<listitem><para> + +<ulink url="http://oss.software.ibm.com/developerworks/opensource/linux390/docu/l390dd08.pdf">Device Drivers and Installation Commands</ulink> + +</para></listitem> +</itemizedlist> + +<para> + +IBM Redbook describing how Linux can be combined with z/VM on +zSeries and &arch-title; hardware. + +</para> + +<itemizedlist> +<listitem><para> + +<ulink url="http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg244987.pdf"> +Linux for &arch-title;</ulink> + +</para></listitem> +</itemizedlist> + +<para> + +IBM Redbook describing the Linux distributions available for the +mainframe. It has no chapter about Debian but the basic installation +concepts are the same across all &arch-title; distributions. + +</para> + +<itemizedlist> +<listitem><para> + +<ulink url="http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf"> +Linux for IBM eServer zSeries and &arch-title;: Distributions</ulink> + +</para></listitem> +</itemizedlist> + </sect3> + + </sect2> + + <sect2 id="fsohi"> + <title>Finding Sources of Hardware Information</title> +<para> + +In many cases, the installer will be able to automatically detect your +hardware. But to be prepared, we do recommend familiarizing +yourself with your hardware before the install. + +</para><para> + +Hardware information can be gathered from: + +</para> + +<itemizedlist> +<listitem><para> + +The manuals that come with each piece of hardware. + +</para></listitem> +<listitem><para> + +The BIOS setup screens of your computer. You can view these screens +when you start your computer by pressing a combination of keys. Check +your manual for the combination. Often, it is the <keycap>Delete</keycap> key. + +</para></listitem> +<listitem><para> + +The cases and boxes for each piece of hardware. + +</para></listitem> + +<listitem arch="i386"><para> + +The System window in the Windows Control Panel. + + +</para></listitem> +<listitem><para> + +System commands or tools in another operating system, including file +manager displays. This source is especially useful for information +about RAM and hard drive memory. + +</para></listitem> +<listitem><para> + +Your system administrator or Internet Service Provider. These +sources can tell you the settings you need to set up your +networking and e-mail. + +</para></listitem> +</itemizedlist> + +<para> + +<table> +<title>Hardware Information Needed for an Install</title> +<tgroup cols="2"> +<thead> +<row> + <entry>Hardware</entry><entry>Information You Might Need</entry> +</row> +</thead> + +<tbody> +<row arch="not-s390"> + <entry morerows="5">Hard Drives</entry> + <entry>How many you have.</entry> +</row> +<row arch="not-s390"><entry>Their order on the system.</entry></row> +<row arch="not-s390"> + <entry>Whether IDE or SCSI (most computers are IDE).</entry> +</row> +<row arch="not-s390"><entry>Available free space.</entry></row> +<row arch="not-s390"><entry>Partitions.</entry></row> +<row arch="not-s390"> + <entry>Partitions where other operating systems are installed.</entry> +</row> + +<row arch="not-s390"> + <entry morerows="5">Monitor</entry> + <entry>Model and manufacturer.</entry> +</row> +<row arch="not-s390"><entry>Resolutions supported.</entry></row> +<row arch="not-s390"><entry>Horizontal refresh rate.</entry></row> +<row arch="not-s390"><entry>Vertical refresh rate.</entry></row> +<row arch="not-s390"> + <entry>Color depth (number of colors) supported.</entry> +</row> +<row arch="not-s390"><entry>Screen size.</entry></row> + +<row arch="not-s390"> + <entry morerows="3">Mouse</entry> + <entry>Type: serial, PS/2, or USB.</entry> +</row> +<row arch="not-s390"><entry>Port.</entry></row> +<row arch="not-s390"><entry>Manufacturer.</entry></row> +<row arch="not-s390"><entry>Number of buttons.</entry></row> + +<row arch="not-s390"> + <entry morerows="1">Network</entry> + <entry>Model and manufacturer.</entry> +</row> +<row arch="not-s390"><entry>Type of adapter.</entry></row> + +<row arch="not-s390"> + <entry morerows="1">Printer</entry> + <entry>Model and manufacturer.</entry> +</row> +<row arch="not-s390"><entry>Printing resolutions supported.</entry></row> + +<row arch="not-s390"> + <entry morerows="2">Video Card</entry> + <entry>Model and manufacturer.</entry> +</row> +<row arch="not-s390"><entry>Video RAM available.</entry></row> +<row arch="not-s390"> + <entry>Resolutions and color depths supported (these should be + checked against your monitor's capabilities).</entry> +</row> + +<row arch="s390"> + <entry morerows="1">DASD</entry> + <entry>Device number(s).</entry> +</row> +<row arch="s390"><entry>Available free space.</entry></row> + +<row arch="s390"> + <entry morerows="2">Network</entry> + <entry>Type of adapter.</entry> +</row> +<row arch="s390"><entry>Device numbers.</entry></row> +<row arch="s390"><entry>Relative adapter number for OSA cards.</entry></row> + +</tbody></tgroup></table> + +</para> + </sect2> + + <sect2> + <title>Hardware Compatibility</title> + +<para> + +Many brand name products work without trouble on Linux. Moreover, +hardware for Linux is improving daily. However, Linux still does not +run as many different types of hardware as some operating systems. + +</para><para arch="i386"> + +In particular, Linux usually cannot run hardware that requires a +running version of Windows to work. + +</para><para arch="i386"> + +Although some Windows-specific hardware can be made to run on Linux, +doing so usually requires extra effort. In addition, Linux drivers +for Windows-specific hardware are usually specific to one Linux +kernel. Therefore, they can quickly become obsolete. + +</para><para arch="i386"> + +So called win-modems are the most common type of this hardware. +However, printers and other equipment may also be Windows-specific. + +</para><para> + +You can check hardware compatibility by: + +<itemizedlist> +<listitem><para> + +Checking manufacturers' web sites for new drivers. + +</para></listitem> +<listitem><para> + +Looking at web sites or manuals for information about emulation. +Lesser known brands can sometimes use the drivers or settings for +better-known ones. + +</para></listitem> +<listitem><para> + +Checking hardware compatibility lists for Linux on web sites +dedicated to your architecture. + +</para></listitem> +<listitem><para> + +Searching the Internet for other users' experiences. + +</para></listitem> +</itemizedlist> + +</para> + </sect2> + + <sect2> + <title>Network Settings</title> + +<para> + +If your computer is connected to a network 24 hours a day (i.e., an +Ethernet or equivalent connection — not a PPP connection), you +should ask your network's system administrator for this information. + +<itemizedlist> +<listitem><para> + +Your host name (you may be able to decide this on your own). + +</para></listitem> +<listitem><para> + +Your domain name. + +</para></listitem> +<listitem><para> + +Your computer's IP address. + +</para></listitem> +<listitem><para> + +The netmask to use with your network. + +</para></listitem> +<listitem><para> + +The IP address of the default gateway system you should route to, if +your network <emphasis>has</emphasis> a gateway. + +</para></listitem> +<listitem><para> + +The system on your network that you should use as a DNS (Domain Name +Service) server. + +</para></listitem> +</itemizedlist> + +</para><para condition="supports-dhcp"> + +On the other hand, if your administrator tells you that a DHCP server +is available and is recommended, then you don't need this information +because the DHCP server will provide it directly to your computer +during the installation process. + +</para><para> + +If you use a wireless network, you should also find out: + +<itemizedlist> +<listitem><para> + +ESSID of your wireless network. + +</para></listitem> +<listitem><para> + +WEP security key (if applicable). + +</para></listitem> +</itemizedlist> + +</para> + </sect2> + + </sect1> diff --git a/ca/preparing/non-debian-partitioning.xml b/ca/preparing/non-debian-partitioning.xml new file mode 100644 index 000000000..995dda157 --- /dev/null +++ b/ca/preparing/non-debian-partitioning.xml @@ -0,0 +1,198 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 untranslated --> + + <sect1 id="non-debian-partitioning"> + <title>Pre-Partitioning for Multi-Boot Systems</title> +<para> + +Partitioning your disk simply refers to the act of breaking up your +disk into sections. Each section is then independent of the others. +It's roughly equivalent to putting up walls inside a house; if you add +furniture to one room it doesn't affect any other room. + +</para><para arch="s390"> + +Whenever this section talks about <quote>disks</quote> you should translate +this into a DASD or VM minidisk in the &arch-title; world. Also a machine +means an LPAR or VM guest in this case. + +</para><para> + +If you already have an operating system on your system + +<phrase arch="i386"> +(Windows 9x, Windows NT/2000/XP, OS/2, MacOS, Solaris, FreeBSD, …) +</phrase> + +<phrase arch="alpha"> +(Tru64 (Digital UNIX), OpenVMS, Windows NT, FreeBSD, …) +</phrase> + +<phrase arch="s390"> +(VM, z/OS, OS/390, …) +</phrase> + +<phrase arch="m68k"> +(Amiga OS, Atari TOS, Mac OS, …) +</phrase> + +and want to stick Linux on the same disk, you will need to repartition +the disk. Debian requires its own hard disk partitions. It cannot be +installed on Windows or MacOS partitions. It may be able to share some +partitions with other Linux systems, but that's not covered here. At +the very least you will need a dedicated partition for the Debian +root. + +</para><para> + +You can find information about your current partition setup by using +a partitioning tool for your current operating system<phrase +arch="i386">, such as fdisk or PartitionMagic</phrase><phrase +arch="powerpc">, such as Drive Setup, HD Toolkit, or MacTools</phrase><phrase +arch="m68k">, such as HD SC Setup, HDToolBox, or SCSITool</phrase><phrase +arch="s390">, such as the VM diskmap</phrase>. Partitioning tools always +provide a way to show existing partitions without making changes. + +</para><para> + +In general, changing a partition with a file system already on +it will destroy any information there. Thus you should always make +backups before doing any repartitioning. Using the analogy of the +house, you would probably want to move all the furniture out of the +way before moving a wall or you risk destroying it. + +</para><para arch="hppa" condition="FIXME"> + +<emphasis>FIXME: write about HP-UX disks?</emphasis> + +</para><para> + +If your computer has more than one hard disk, you may want to dedicate +one of the hard disks completely to Debian. If so, you don't need to +partition that disk before booting the installation system; the +installer's included partitioning program can handle the job nicely. + +</para><para> + +If your machine has only one hard disk, and you would like to +completely replace the current operating system with &debian;, +you also can wait to partition as part of the installation process +(<xref linkend="partman"/>), after you have booted the +installation system. However this only works if you plan to boot the +installer system from tapes, CD-ROM or files on a connected machine. +Consider: if you boot from files placed on the hard disk, and then +partition that same hard disk within the installation system, thus +erasing the boot files, you'd better hope the installation is +successful the first time around. At the least in this case, you +should have some alternate means of reviving your machine like the +original system's installation tapes or CDs. + +</para><para> + +If your machine already has multiple partitions, and enough space can +be provided by deleting and replacing one or more of them, then you +too can wait and use the Debian installer's partitioning program. You +should still read through the material below, because there may be +special circumstances like the order of the existing partitions within +the partition map, that force you to partition before installing +anyway. + +</para><para arch="i386"> + +If your machine has a FAT or NTFS filesystem, as used by DOS and Windows, +you can wait and use Debian installer's partitioning program to +resize the filesystem. + +</para><para> + +If none of the above apply, you'll need to partition your hard disk before +starting the installation to create partition-able space for +Debian. If some of the partitions will be owned by other operating +systems, you should create those partitions using native operating +system partitioning programs. We recommend that you do +<emphasis>not</emphasis> attempt to create partitions for &debian; +using another operating system's tools. Instead, you should just +create the native operating system's partitions you will want to +retain. + +</para><para> + +If you are going to install more than one operating system on the same +machine, you should install all other system(s) before proceeding with +Linux installation. Windows and other OS installations may destroy +your ability to start Linux, or encourage you to reformat non-native +partitions. + +</para><para> + +You can recover from these actions or avoid them, but installing +the native system first saves you trouble. + +</para><para arch="powerpc"> + +In order for OpenFirmware to automatically boot &debian; the Linux +partitions should appear before all other partitions on the disk, +especially MacOS boot partitions. This should be kept in mind when +pre-partitioning; you should create a Linux placeholder partition to +come <emphasis>before</emphasis> the other bootable partitions on the +disk. (The small partitions dedicated to Apple disk drivers are not +bootable.) You can delete the placeholder with the Linux partition +tools later during the actual install, and replace it with Linux +partitions. + +</para><para> + +If you currently have one hard disk with one partition (a common setup +for desktop computers), and you want to multi-boot the native +operating system and Debian, you will need to: + + <orderedlist> +<listitem><para> + +Back up everything on the computer. + +</para></listitem> +<listitem><para> + +Boot from the native operating system installer media such as CD-ROM +or tapes. + +<phrase arch="powerpc">When booting from a MacOS CD, hold the +<keycap>c</keycap> key while +booting to force the CD to become the active MacOS system.</phrase> + +</para></listitem> +<listitem><para> + +Use the native partitioning tools to create native system +partition(s). Leave either a place holder partition or free space for +&debian;. + +</para></listitem> +<listitem><para> + +Install the native operating system on its new partition. + +</para></listitem> +<listitem><para> + +Boot back into the native system to verify everything's OK, + and to download the Debian installer boot files. + +</para></listitem> +<listitem><para> + +Boot the Debian installer to continue installing Debian. + +</para></listitem> +</orderedlist> + +</para> + +&nondeb-part-alpha.xml; +&nondeb-part-i386.xml; +&nondeb-part-m68k.xml; +&nondeb-part-sparc.xml; +&nondeb-part-powerpc.xml; + + </sect1> diff --git a/ca/preparing/nondeb-part/alpha.xml b/ca/preparing/nondeb-part/alpha.xml new file mode 100644 index 000000000..de065da6d --- /dev/null +++ b/ca/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/ca/preparing/nondeb-part/i386.xml b/ca/preparing/nondeb-part/i386.xml new file mode 100644 index 000000000..b89864d7e --- /dev/null +++ b/ca/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/ca/preparing/nondeb-part/m68k.xml b/ca/preparing/nondeb-part/m68k.xml new file mode 100644 index 000000000..dbea5b44e --- /dev/null +++ b/ca/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 — 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/ca/preparing/nondeb-part/powerpc.xml b/ca/preparing/nondeb-part/powerpc.xml new file mode 100644 index 000000000..8b70dc6a3 --- /dev/null +++ b/ca/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/ca/preparing/nondeb-part/sparc.xml b/ca/preparing/nondeb-part/sparc.xml new file mode 100644 index 000000000..9bcc1239b --- /dev/null +++ b/ca/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> diff --git a/ca/preparing/pre-install-bios-setup.xml b/ca/preparing/pre-install-bios-setup.xml new file mode 100644 index 000000000..74d57db2d --- /dev/null +++ b/ca/preparing/pre-install-bios-setup.xml @@ -0,0 +1,151 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 untranslated --> + + <sect1 id="pre-install-bios-setup"> + <title>Pre-Installation Hardware and Operating System Setup</title> +<para> + +This section will walk you through pre-installation hardware setup, if +any, that you will need to do prior to installing Debian. Generally, +this involves checking and possibly changing firmware settings for +your system. The <quote>firmware</quote> is the core software used by the +hardware; it is most critically invoked during the bootstrap process +(after power-up). Known hardware issues affecting the reliability of +&debian; on your system are also highlighted. + +</para> + +&bios-setup-i386.xml; +&bios-setup-m68k.xml; +&bios-setup-powerpc.xml; +&bios-setup-sparc.xml; +&bios-setup-s390.xml; + + <sect2><title>Hardware Issues to Watch Out For</title> +<para arch="not-s390"> + +Many people have tried operating their 90 MHz CPU at 100 MHz, etc. It +sometimes works, but is sensitive to temperature and other factors and +can actually damage your system. One of the authors of this document +over-clocked his own system for a year, and then the system started +aborting the <command>gcc</command> program with an unexpected signal +while it was compiling the operating system kernel. Turning the CPU +speed back down to its rated value solved the problem. + +</para><para arch="not-s390"> + +The <command>gcc</command> compiler is often the first thing to die +from bad memory modules (or other hardware problems that change data +unpredictably) because it builds huge data structures that it +traverses repeatedly. An error in these data structures will cause it +to execute an illegal instruction or access a non-existent +address. The symptom of this will be <command>gcc</command> dying from +an unexpected signal. + +</para><para arch="m68k"> + +Atari TT RAM boards are notorious for RAM problems under Linux; if you +encounter any strange problems, try running at least the kernel in +ST-RAM. Amiga users may need to exclude RAM using a booter memfile. + +<phrase condition="FIXME"><emphasis> + +FIXME: more description of this needed. + +</emphasis></phrase> + +</para><para arch="i386"> + +The very best motherboards support parity RAM and will actually tell +you if your system has a single-bit error in RAM. Unfortunately, they +don't have a way to fix the error, thus they generally crash +immediately after they tell you about the bad RAM. Still, it's better +to be told you have bad memory than to have it silently insert errors +in your data. Thus, the best systems have motherboards that support +parity and true-parity memory modules; see +<xref linkend="Parity-RAM"/>. + +</para><para arch="i386"> + +If you do have true-parity RAM and your motherboard can handle it, be +sure to enable any BIOS settings that cause the motherboard to +interrupt on memory parity errors. + +</para> + + <sect3 arch="i386"><title>The Turbo Switch</title> +<para> + +Many systems have a <emphasis>turbo</emphasis> switch that controls +the speed of the CPU. Select the high-speed setting. If your BIOS +allows you to disable software control of the turbo switch (or +software control of CPU speed), do so and lock the system in +high-speed mode. We have one report that on a particular system, while +Linux is auto-probing (looking for hardware devices) it can +accidentally touch the software control for the turbo switch. + +</para> + </sect3> + + <sect3 arch="i386"><title>Cyrix CPUs and Floppy Disk Errors</title> +<para> + +Many users of Cyrix CPUs have had to disable the cache in their +systems during installation, because the floppy disk has errors if +they do not. If you have to do this, be sure to re-enable your cache +when you are finished with installation, as the system runs +<emphasis>much</emphasis> slower with the cache disabled. + +</para><para> + +We don't think this is necessarily the fault of the Cyrix CPU. It may +be something that Linux can work around. We'll continue to look into +the problem. For the technically curious, we suspect a problem with +the cache being invalid after a switch from 16-bit to 32-bit code. + +</para> + </sect3> + + <sect3 arch="i386"><title>Peripheral Hardware Settings</title> +<para> + +You may have to change some settings or jumpers on your computer's +peripheral cards. Some cards have setup menus, while others rely on +jumpers. This document cannot hope to provide complete information on +every hardware device; what it hopes to provide is useful tips. + +</para><para> + +If any cards provide <quote>mapped memory</quote>, the memory should be +mapped somewhere between 0xA0000 and 0xFFFFF (from 640K to just below 1 +megabyte) or at an address at least 1 megabyte greater than the total +amount of RAM in your system. + +</para> + </sect3> + + <sect3 arch="i386" id="usb-keyboard-config"> + <title>USB BIOS support and keyboards</title> +<para> + +If you have no AT-style keyboard and only a USB model, you may need +to enable legacy AT keyboard emulation in your BIOS setup. Only do this if +the installation system fails to use your keyboard in USB mode. Conversely, +for some systems (especially laptops) you may need to disable legacy USB +support if your keyboard does not respond. +Consult your main board manual and look in the BIOS for <quote>Legacy +keyboard emulation</quote> or <quote>USB keyboard support</quote> options. + +</para> + </sect3> + + <sect3><title>More than 64 MB RAM</title> +<para> + +The Linux Kernel cannot always detect what amount of RAM you have. If +this is the case please look at <xref linkend="boot-parms"/>. + +</para> + </sect3> + </sect2> + </sect1> diff --git a/ca/preparing/preparing.xml b/ca/preparing/preparing.xml new file mode 100644 index 000000000..e82f8b651 --- /dev/null +++ b/ca/preparing/preparing.xml @@ -0,0 +1,22 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 16467 --> + +<chapter id="preparing"> + <title>Abans d'instal·lar &debian;</title> +<para> + +Aquest capítol s'ocupa de la preparació per instal·lar Debian abans que +arranqueu l'instal·lador. Això inclou fer copies de seguretat de la vostres +dades, recollir informació del vostre maquinari i localitzar qualsevol +informació necessària. + +</para> + +&install-overview.xml; +&backup.xml; +&needed-info.xml; +&minimum-hardware-reqts.xml; +&non-debian-partitioning.xml; +&pre-install-bios-setup.xml; + +</chapter> diff --git a/ca/using-d-i/components.xml b/ca/using-d-i/components.xml new file mode 100644 index 000000000..cfedc5912 --- /dev/null +++ b/ca/using-d-i/components.xml @@ -0,0 +1,163 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 29895 --> + + <sect1 id="module-details"> + <title>Utilització dels elements individualment</title> +<para> + +En aquesta secció descriurem detalladament cada element de l'instal·lador. Els +elements s'han agrupat en fases que els usuaris haurien de reconèixer. +Es presenten en l'ordre que apareixen durant la instal·lació. Recordeu que +en cada instal·lació no s'utilitzaran tots els mòduls, els que realment +s'utilitzen depenen del mètode d'instal·lació que s'utilitza i del +maquinari. + +</para> + + <sect2 id="di-setup"> + <title>Configuració de l'instal·lador de Debian i del maquinari</title> +<para> + +Suposem que l'instal·lador de Debian ha arrencat i que esteu davant la +primera pantalla. En aquesta fase, les capacitats del &d-i; encara són +bastant limitades. Desconeix la major part de característiques del +maquinari, idioma preferit, o fins i tot quina tasca ha de realitzar. +No us preocupeu, el &d-i; és bastant llest i pot enquestar automàticament +el vostre maquinari, localitzar la resta dels seus elements i +actualitzar-se a un sistema d'instal·lació capaç. + +Tot i això encara caldrà ajudar el &d-i; amb alguna informació que +no pot determinar automàticament (com la selecció de l'idioma preferit, +l'esquema del teclat o la rèplica de xarxa a utilitzar). + +</para><para> + +Notareu que en aquesta fase el &d-i; realitza la <firstterm>detecció de maquinari</firstterm> +diverses vegades. El primer cop, l'objectiu és, específicament, +el maquinari necessari per carregar els elements de l'instal·lador (p. ex. el +CD-ROM o targeta de xarxa). Com que no tots els controladors estan +disponibles en aquesta primera execució, és necessari repetir la detecció de +maquinari posteriorment. + +</para> + +&module-lowmem.xml; +&module-languagechooser.xml; +&module-countrychooser.xml; +&module-localechooser.xml; +&module-kbd-chooser.xml; +&module-s390-netdevice.xml; +&module-ddetect.xml; +&module-cdrom-detect.xml; +&module-iso-scan.xml; +&module-anna.xml; +&module-netcfg.xml; +&module-choose-mirror.xml; + + </sect2> + + <sect2 id="di-partition"> + <title>Realització de particions i selecció de punts de muntatge</title> +<para> + +En aquest instant, després de l'última execució de la detecció de maquinari, +el &d-i; hauria d'estar a plena potència, adaptat a les necessitats +de l'usuari i preparat per fer la feina real. + +Tal i com indica el títol d'aquesta secció, la tasca principal del pròxims +elements és fer les particions als vostres discs, crear els sistemes de +fitxers, assignar els punts de muntatges i, opcionalment, configurar +qüestions estretament relacionades com l'LVM o els dispositius RAID. + +</para> + +&module-s390-dasd.xml; +&module-partman.xml; +&module-autopartkit.xml; +&module-partitioner.xml; +&module-partconf.xml; +&module-lvmcfg.xml; +&module-mdcfg.xml; + </sect2> + + <sect2 id="di-install-base"> + <title>Instal·lació del sistema base</title> +<para> + +Encara que aquesta fase és la menys problemàtica consumeix la major +part del temps de la instal·lació, ja que es baixa, verifica i +desempaqueta el sistema base complet. Si teniu un ordinador o una +connexió de xarxa lents pot portar el seu temps. + +</para> + +&module-base-installer.xml; + </sect2> + + <sect2 id="di-make-bootable"> + <title>Com fer el sistema arrencable</title> + +<para condition="supports-nfsroot"> + +Si esteu instal·lant una estació de treball sense disc, arrencar des del +disc local és, evidentment, una opció sense sentit i s'ometrà aquest pas. +<phrase arch="sparc">Potser desitgeu configurar l'OpenBoot perquè arrenqui +des de la xarxa predeterminada, vegeu +<xref linkend="boot-dev-select-sun"/>.</phrase> + +</para><para> + +Recordeu que diversos sistemes operatius arrencant des d'una sola +màquina encara implica una mica d'art fosc. Aquest document fins i +tot no intenta documentar els diversos gestors d'arrencada, que poden +variar segons l'arquitectura i fins i tot segons la subarquitectura. +Per obtenir més informació hauríeu de veure la documentació del vostre +gestor d'arrencada. + +</para> + +&module-os-prober.xml; +&module-alpha-aboot-installer.xml; +&module-hppa-palo-installer.xml; +&module-i386-grub-installer.xml; +&module-i386-lilo-installer.xml; +&module-ia64-elilo-installer.xml; +&module-mips-arcboot-installer.xml; +&module-mipsel-colo-installer.xml; +&module-mipsel-delo-installer.xml; +&module-powerpc-yaboot-installer.xml; +&module-powerpc-quik-installer.xml; +&module-s390-zipl-installer.xml; +&module-sparc-silo-installer.xml; +&module-nobootloader.xml; + </sect2> + + <sect2 id="di-finish"> + <title>Acabament de la primera fase</title> +<para> + +Aquests són els últims detalls per fer abans de tornar a arrencar el nou +Debian, principalment ordenar les coses després del &d-i; + +</para> + +&module-prebaseconfig.xml; + </sect2> + + <sect2 id="di-miscellaneous"> + <title>Miscel·lània</title> +<para> + +Els elements que es llisten en aquesta secció normalment no estan involucrats +en el procés d'instal·lació, però s'esperen en segon pla per ajudar l'usuari +en cas que alguna cosa vagi malament. + +</para> + +&module-save-logs.xml; +&module-cdrom-checker.xml; +&module-shell.xml; +&module-network-console.xml; +&module-baseconfig.xml; + </sect2> + </sect1> diff --git a/ca/using-d-i/modules/alpha/aboot-installer.xml b/ca/using-d-i/modules/alpha/aboot-installer.xml new file mode 100644 index 000000000..2d58e0f74 --- /dev/null +++ b/ca/using-d-i/modules/alpha/aboot-installer.xml @@ -0,0 +1,19 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 25496 untranslated --> + + <sect3 arch="alpha"> + <title>Install <command>aboot</command> on a Hard Disk</title> +<para> + +If you have booted from SRM, if you select this option, the installer +will write <command>aboot</command> to the first sector of the disk on +which you installed Debian. Be <emphasis>very</emphasis> careful — it +is <emphasis>not</emphasis> 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. + +</para> + </sect3> diff --git a/ca/using-d-i/modules/anna.xml b/ca/using-d-i/modules/anna.xml new file mode 100644 index 000000000..9442b9d2f --- /dev/null +++ b/ca/using-d-i/modules/anna.xml @@ -0,0 +1,2 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 11648 --> diff --git a/ca/using-d-i/modules/autopartkit.xml b/ca/using-d-i/modules/autopartkit.xml new file mode 100644 index 000000000..9442b9d2f --- /dev/null +++ b/ca/using-d-i/modules/autopartkit.xml @@ -0,0 +1,2 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 11648 --> diff --git a/ca/using-d-i/modules/base-installer.xml b/ca/using-d-i/modules/base-installer.xml new file mode 100644 index 000000000..692fdb01d --- /dev/null +++ b/ca/using-d-i/modules/base-installer.xml @@ -0,0 +1,30 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 --> + + <sect3 id="base-installer"> + <title>Instal·lació del sistema base</title> + +<para> + +Al llarg de la instal·lació base, els missatges del desempaquetament +dels paquets i de la instal·lació es redirigeixen a +<userinput>tty3</userinput>. Podeu accedir a aquesta terminal prement +<keycombo><keycap>Alt esquerra</keycap><keycap>F3</keycap></keycombo>; +torneu al procés principal de l'instal·lador amb +<keycombo><keycap>Alt esquerra</keycap><keycap>F1</keycap></keycombo>. + +</para><para> + +Els missatges de desempaquetament i configuració que genera la instal·lació +base es guarden a <filename>/var/log/messages</filename> quan la instal·lació +es realitza a través d'una consola sèrie. + +</para><para> + +Com a part de la instal·lació, s'instal·larà un nucli del Linux. A la prioritat +per defecte, l'instal·lador elegirà aquell que es correspongui millor amb el +maquinari. En modes de prioritat més baixa, podreu elegir a partir d'una +llista dels nuclis disponibles. + +</para> + </sect3> diff --git a/ca/using-d-i/modules/baseconfig.xml b/ca/using-d-i/modules/baseconfig.xml new file mode 100644 index 000000000..c7ba72695 --- /dev/null +++ b/ca/using-d-i/modules/baseconfig.xml @@ -0,0 +1,18 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 29903 --> + + <sect3 id="baseconfig"> + <title>Utilitzant el <command>base-config</command> des del &d-i;</title> + +<para> + +Si executeu l'ordre <command>base-config</command> en una entorn +<firstterm>chroot</firstterm> podreu configurar el sistema base +en la primera etapa de l'instal·lador (abans de reiniciar el sistema +des del disc dur). Bàsicament és útil per provar l'instal·lador, +i normalment s'hauria d'ometre. + +<!-- Feel free to prove me I'm wrong --> + +</para> + </sect3> diff --git a/ca/using-d-i/modules/cdrom-checker.xml b/ca/using-d-i/modules/cdrom-checker.xml new file mode 100644 index 000000000..29dc138a1 --- /dev/null +++ b/ca/using-d-i/modules/cdrom-checker.xml @@ -0,0 +1,2 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 14337 --> diff --git a/ca/using-d-i/modules/cdrom-detect.xml b/ca/using-d-i/modules/cdrom-detect.xml new file mode 100644 index 000000000..9442b9d2f --- /dev/null +++ b/ca/using-d-i/modules/cdrom-detect.xml @@ -0,0 +1,2 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 11648 --> diff --git a/ca/using-d-i/modules/choose-mirror.xml b/ca/using-d-i/modules/choose-mirror.xml new file mode 100644 index 000000000..746804ecd --- /dev/null +++ b/ca/using-d-i/modules/choose-mirror.xml @@ -0,0 +1,17 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 16990 untranslated --> + +<!-- +- Component is only selected and executed if the installer needs to load + installer components or the base system from the network + (either local or the internet). +- This means you first have to configure a network interface. +- A list of countries is displayed with the default based on the country you + selected earlier. +- Note that not all mirrors are equal (see http://www.nl.debian.org/mirror/list) +- Selection of a local mirror (at top of the list: manual selection). +- After selecting a country, a list of mirrors in the country will be shown. + +- The selected mirror will be tested. +- How to handle problems with mirrors. +-->
\ No newline at end of file diff --git a/ca/using-d-i/modules/countrychooser.xml b/ca/using-d-i/modules/countrychooser.xml new file mode 100644 index 000000000..d72ea0968 --- /dev/null +++ b/ca/using-d-i/modules/countrychooser.xml @@ -0,0 +1,26 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28343 --> + + + <sect3 id="country-chooser" condition="sarge"> + <title>Selecció del país</title> + +<para> + +Si heu seleccionat un idioma a <xref linkend="lang-chooser"/> que +té més d'un país associat (això passa pel xinès, l'anglès, el +francès, i molts altres idiomes), aquí podeu especificar el país. +Si seleccioneu <guimenuitem>altre</guimenuitem> al final de la llista, +se us presentarà una llista amb tots els països, agrupats per continents. + +</para><para> + +Aquesta selecció s'utilitzarà més endavant del procés d'instal·lació per +seleccionar la zona horària per defecte i un mirall de Debian apropiat per +la vostra localització geogràfica. Si els valors per defecte proposats per +l'instal·lador no són apropiats, podeu fer una elecció diferent. El país +seleccionat, junt amb l'idioma seleccionat, també pot afectar la configuració +de localització del sistema Debian. + +</para> + </sect3> diff --git a/ca/using-d-i/modules/ddetect.xml b/ca/using-d-i/modules/ddetect.xml new file mode 100644 index 000000000..9442b9d2f --- /dev/null +++ b/ca/using-d-i/modules/ddetect.xml @@ -0,0 +1,2 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 11648 --> diff --git a/ca/using-d-i/modules/hppa/palo-installer.xml b/ca/using-d-i/modules/hppa/palo-installer.xml new file mode 100644 index 000000000..84a3608e8 --- /dev/null +++ b/ca/using-d-i/modules/hppa/palo-installer.xml @@ -0,0 +1,20 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 14602 untranslated --> + + <sect3 arch="hppa"> + <title><command>palo</command>-installer</title> +<para> + +The bootloader on PA-RISC is <quote>palo</quote>. +<command>PALO</command> is similar in configuration and usage to +<command>LILO</command>, with a few exceptions. First of all, +<command>PALO</command> allows you to boot any kernel image on your +boot partition. This is because <command>PALO</command> can actually +read Linux partitions. + +</para><para condition="FIXME"> + +hppa FIXME ( need more info ) + +</para> + </sect3> diff --git a/ca/using-d-i/modules/i386/grub-installer.xml b/ca/using-d-i/modules/i386/grub-installer.xml new file mode 100644 index 000000000..6d2a375e9 --- /dev/null +++ b/ca/using-d-i/modules/i386/grub-installer.xml @@ -0,0 +1,27 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 18640 --> + + <sect3 arch="i386"> + <title>Instal·lació del carregador d'arrencada <command>grub</command> en + un disc dur</title> + +<para> + +El carregador d'arrencada principal de &architecture; s'anomena +<quote>grub</quote>. El grub és un carregador d'arrencada robust +i flexible i una bona opció per als usuaris nouvinguts o similars. + +</para><para> + +El grub s'instal·larà per defecte al Master Boot Record (MBR), on agafarà +el control del procés d'arrencada. Si ho preferiu el podeu instal·lar a un +altre lloc. Per a més informació vegeu el manual del grub. + +</para><para> + +Si no voleu instal·lar el grub, utilitzeu el botó Endarrere per tornar +al menú principal i des d'allà sel·leccioneu el carregador d'arrencada +que voleu utilitzar. + +</para> + </sect3> diff --git a/ca/using-d-i/modules/i386/lilo-installer.xml b/ca/using-d-i/modules/i386/lilo-installer.xml new file mode 100644 index 000000000..23e5703f8 --- /dev/null +++ b/ca/using-d-i/modules/i386/lilo-installer.xml @@ -0,0 +1,70 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 22935 --> + + <sect3 arch="i386"> + <title>Instal·lació del carregador d'arrencada <command>LILO</command> + a un disc dur</title> +<para> + +El segon carregador d'arrencada de &architecture; s'anomena <quote>LILO</quote>. +És una programa antic i complex que ofereix moltes funcionalitats, +inclosa la gestió de l'arrencada del DOS, Windows i OS/2. Si teniu alguna +necessitat especial llegiu atentament les instruccions del directori +<filename>/usr/share/doc/lilo/</filename>; també podeu fer una ullada al +<ulink url="&url-lilo-howto;">LILO mini-HOWTO</ulink>. + +</para><para> + +Actualment la instal·lació del LILO només crearà entrades de menú per +altres sistemes operatius si aquests poden ser <firstterm>carregats en +cadena</firstterm>. +Això significa que haureu d'afegir manualment una entrada de menú per +a sistemes operatius com GNU/Linux i GNU/Hurd després de la instal·lació. + +</para><para> + +El &d-i; us permet triar, entre tres opcions diferents, on instal·lar el +carregador d'arrencada <command>LILO</command>: + +<variablelist> +<varlistentry> +<term>Master Boot Record (MBR)</term><listitem><para> + +En aquest cas el <command>LILO</command> disposarà del control complet del +procés d'arrencada. + +</para></listitem></varlistentry> +<varlistentry> +<term>una nova partició de Debian</term><listitem><para> + +Escolliu aquesta opció si voleu utilitzar un altre gestor +d'arrencada. El <command>LILO</command> s'instal·larà a l'inici +de la nova partició de Debian i funcionarà com a carregador +d'arrencada secundari. + +</para></listitem></varlistentry> +<varlistentry> +<term>Una altra opció</term><listitem><para> + +És útil per a usuaris avançats que pretenen instal·lar el +<command>LILO</command> en una altra ubicació. En aquest cas se us +demanarà la nova ubicació. Podeu utilitzar l'estil dels noms del devfs, +com per exemple els que comencen per <filename>/dev/ide</filename>, +<filename>/dev/scsi</filename>, i <filename>/dev/discs</filename>, +també els noms tradicionals com <filename>/dev/hda</filename> o +<filename>/dev/sda</filename>. + +</para></listitem></varlistentry> +</variablelist> + +</para><para> + +Si després d'aquest pas ja no podeu arrencar el Windows 9x (o DOS), +per tornar a instal·lar el master boot record haureu d'utilitzar un +disc d'arrencada del Windows 9x (o DOS) i utilitzar l'ordre +<userinput>fdisk /mbr</userinput> — recordeu que significarà +que haureu de tornar a Debian d'una altra manera! Per a més informació +llegiu <xref linkend="reactivating-win"/>. + +</para> + </sect3> diff --git a/ca/using-d-i/modules/ia64/elilo-installer.xml b/ca/using-d-i/modules/ia64/elilo-installer.xml new file mode 100644 index 000000000..7953befe6 --- /dev/null +++ b/ca/using-d-i/modules/ia64/elilo-installer.xml @@ -0,0 +1,135 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 24321 untranslated --> + + <sect3 arch="ia64"> + <title>Install the <command>ELILO</command> Boot Loader + on a Hard Disk</title> +<para> + +The &architecture; boot loader is called <quote>elilo</quote>. +It is modeled on the <quote>lilo</quote> boot loader for the +x86 architecture and uses a similar configuration file. +However, instead of writing an MBR or partition boot record to +the disk, it copies the necessary files to a separate FAT formatted +disk partition and modifies the <guimenuitem>EFI Boot Manager</guimenuitem> +menu in the firmware to point to the files in the EFI partition. +The <command>elilo</command> boot loader is really in two parts. +The <filename>/usr/sbin/elilo</filename> command manages the partition and +copies file into it. +The <filename>elilo.efi</filename> program is copied into the EFI +partition and then run by the <quote>EFI Boot Manager</quote> to actually +do the work of loading and starting the Linux kernel. + +</para><para> + +The <quote>elilo</quote> configuration and installation is done as the +last step of installing the packages of the base installation. +&d-i; will present you with a list of potential disk partitions that it +has found suitable for an EFI partition. +Select the partition you set up earlier in the installation, typically +a partition on the same disk that contains your +<emphasis>root</emphasis> filesystem. + +</para> + + <warning><title>Choose the correct partition!</title> + +<para> + +The criteria for selecting a partition is that it is FAT format +filesystem with its <emphasis>boot</emphasis> flag set. +&d-i; may show multiple choices depending on what it finds from scanning +all of the disks of the system including EFI partitions of other system +disks and EFI diagnostic partitions. +Remember, the <command>elilo</command> may format the partition during +the installation, erasing any previous contents! + +</para></warning> + + </sect3> + + <sect3 arch="ia64"> + <title>EFI Partition Contents</title> + +<para> + +The EFI partition is a FAT filesystem format partition on one of the +hard disks of the system, usually the same disk that contains the +<emphasis>root</emphasis> filesystem. +It is normally not mounted on a running system as it is only needed +by the <quote>EFI Boot Manager</quote> to load the system and the +installer part of the <command>elilo</command> writes to the filesystem +directly. +The <command>/usr/sbin/elilo</command> utility writes the following files +into the <filename>efi/debian</filename> directory of the EFI +partition during the installation. +Note that the <quote>EFI Boot Manager</quote> would find these files +using the path <filename>fs<replaceable>n</replaceable>:\efi\debian</filename>. +There may be other files in this filesystem as well over time as +the system is updated or re-configured. + +</para> + +<variablelist> + +<varlistentry> +<term><filename>elilo.conf</filename></term> +<listitem><para> + +This is the configuration file read by the boot loader when it starts. +It is a copy of the <filename>/etc/elilo.conf</filename> with +the filenames re-written to refer to files in the EFI partition. + +</para></listitem></varlistentry> + +<varlistentry> +<term><filename>elilo.efi</filename></term> +<listitem><para> + +This is the boot loader program that the <quote>EFI Boot Manager</quote> +runs to boot the system. +It is the program behind the <guimenuitem>Debian GNU/Linux</guimenuitem> +menu item of the <quote>EFI Boot Manager</quote> command menu. + +</para></listitem></varlistentry> + +<varlistentry> +<term><filename>initrd.img</filename></term> +<listitem><para> + +This is the initial root filesystem used to boot the kernel. +It is a copy of the file referenced in the +<filename>/etc/elilo.conf</filename>. +In a standard Debian installation it would be the file in +<filename>/boot</filename> pointed to by the symbolic link +<filename>/initrd.img</filename>. + +</para></listitem></varlistentry> + +<varlistentry> +<term><filename>readme.txt</filename></term> +<listitem><para> + +This is a small text file warning you that the contents of the +directory are managed by the <command>elilo</command> and that +any local changes would be lost at the next time +<filename>/usr/sbin/elilo</filename> is run. + +</para></listitem></varlistentry> + +<varlistentry> +<term><filename>vmlinuz</filename></term> +<listitem><para> + +This is the compressed kernel itself. +It is a copy of the file referenced in the +<filename>/etc/elilo.conf</filename>. +In a standard Debian installation it would be the file in +<filename>/boot</filename> pointed to by the symbolic link +<filename>/vmlinuz</filename>. + +</para></listitem></varlistentry> + +</variablelist> + + </sect3> diff --git a/ca/using-d-i/modules/iso-scan.xml b/ca/using-d-i/modules/iso-scan.xml new file mode 100644 index 000000000..296d2d753 --- /dev/null +++ b/ca/using-d-i/modules/iso-scan.xml @@ -0,0 +1,49 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 23058 --> + + <sect3 id="iso-scan"> + <title>Cerca de la imatge ISO de l'instal·lador de Debian</title> +<para> + +Quan instal·leu segons el mètode <emphasis>hd-media</emphasis>, hi +haurà un moment en què necessitareu trobar i muntar la imatge ISO de +l'instal·lador de Debian per tal d'obtenir la resta de fitxers de la +instal·lació. Això és exactament el que fa el component +<command>iso-scan</command>. + +</para><para> + +Al principi, l'<command>iso-scan</command> munta automàticament tots +els dispositius de bloc (p.ex. particions) que tinguin algun sistema +de fitxers conegut i cerca de forma seqüencial noms de fitxer acabats en +<filename>.iso</filename> (o, per aquest propòsit, +<filename>.ISO</filename>). Preneu atenció que el primer intent només +escaneja fitxers en el directori arrel i en el primer nivell de +subdirectoris (p.ex. troba +<filename>/<replaceable>qualsevol_cosa</replaceable>.iso</filename> i +<filename>/data/<replaceable>qualsevol_cosa</replaceable>.iso</filename>, +però no +<filename>/data/tmp/<replaceable>qualsevol_cosa</replaceable>.iso</filename>). +Després que hagi trobat una imatge iso, l'<command>iso-scan</command> +comprova el seu contingut per determinar si la imatge és una imatge iso +de Debian vàlida o no. En el primer cas hem acabat, en el segon +l'<command>iso-scan</command> cerca una altra imatge. + +</para><para> + +En el cas que l'intent previ per trobar una imatge iso de l'instal·lador +falli, l'<command>iso-scan</command> us preguntarà si voleu realitzar +una cerca més exhaustiva. En aquest cas, no es mira només els directoris +superiors, sinó que es recorre el sistema de fitxers complet. + +</para><para> + +Si l'<command>iso-scan</command> no descobreix la imatge iso de l'instal·lador, +torneu a arrencar al vostre sistema operatiu original i comproveu si la +imatge té un nom correcte (acabat en <filename>.iso</filename>), si es troba +en un sistema de fitxers que el &d-i; pugui reconèixer, i si no és corrupte +(verifiqueu la suma de comprovació). Els usuaris de Unix experimentats poden +fer-ho des de la segona consola, sense tornar a arrencar. + +</para> + </sect3> diff --git a/ca/using-d-i/modules/kbd-chooser.xml b/ca/using-d-i/modules/kbd-chooser.xml new file mode 100644 index 000000000..6fb15a792 --- /dev/null +++ b/ca/using-d-i/modules/kbd-chooser.xml @@ -0,0 +1,43 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 21579 --> + + <sect3 id="kbd-chooser"> + <title>Selecció d'un teclat</title> + +<para> + +Els teclats acostumen a estar adaptats als caràcters utilitzats en un idioma. +Seleccioneu un format idoni al teclat que esteu utilitzant o un de similar +en cas de que no aparegui. Una vegada instal·lat el sistema +podreu seleccionar-ne un entre un rang de possibilitats més gran +(un cop finalitzada la instal·lació executeu l'ordre +<command>kbdconfig</command> com a superusuari). + +</para><para> + +Moveu el ressaltat al teclat que voleu utilitzar i premeu +&enterkey;. Utilitzeu el cursor del teclat per moure el — ressaltat; +tots els formats de teclat de tots els idiomes situen el cursor en la mateixa +ubicació i, per tant, són independents a la configuració del teclat. +Un teclat «extès» disposa de les tecles <keycap>F1</keycap> a +<keycap>F10</keycap> en la fila superior. + +</para><para arch="mipsel"> + +En les estacions DEC no hi ha cap mapa de teclat que es pugui carregar, +haureu d'ometre'n la selecció i mantenir el predeterminat pel nucli +(LK201 US). Aquesta situació probablement canviarà en el futur, +ja que va lligada al desenvolupament del nucli Linux/MIPS. + +</para><para arch="powerpc"> + +Hi ha dos formats de teclat pels teclats US. El qwerty/mac-usb-us +(Apple USB) assignarà la funció Alt a la tecla <keycap>Command/Apple</keycap> +(a la posició del teclat al costat de la tecla d'<keycap>espai</keycap> +similar al <keycap>Alt</keycap> en els teclats de PC). En el cas del +qwerty/us (Standard) assignarà la funció ALT a la tecla <keycap>Option</keycap> +(en la majoria de teclats de Mac amb el text «alt» grabat). En la resta de +característiques els dos formats són similars. + +</para> + </sect3> diff --git a/ca/using-d-i/modules/languagechooser.xml b/ca/using-d-i/modules/languagechooser.xml new file mode 100644 index 000000000..fb7f07760 --- /dev/null +++ b/ca/using-d-i/modules/languagechooser.xml @@ -0,0 +1,25 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28343 --> + + + <sect3 id="lang-chooser" condition="sarge"> + <title>Selecció de l'idioma</title> + +<para> + +El primer pas de la instal·lació és seleccionar l'idioma que voleu +utilitzar durant el procés. Els noms dels idiomes apareixen en anglès +(banda esquerra) i en l'idioma original (banda dreta); els noms de la +dreta també es mostren amb la tipografia original que li correspon. +La llista està ordenada pel nom anglès. + +</para><para> + +L'idioma que trieu s'utilitzarà per a la resta del procés d'instal·lació, +disposareu d'una traducció de les diferents caixes de diàleg. +En cas de no disposar de cap traducció per l'idioma seleccionat, +s'agafarà l'anglès com a predeterminat. L'idioma +també s'utilitzarà per ajudar a la selecció d'un format de teclat idoni. + +</para> + </sect3> diff --git a/ca/using-d-i/modules/localechooser.xml b/ca/using-d-i/modules/localechooser.xml new file mode 100644 index 000000000..5ba593cb6 --- /dev/null +++ b/ca/using-d-i/modules/localechooser.xml @@ -0,0 +1,70 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28856 --> + + + <sect3 id="localechooser" condition="etch"> + <title>Seleccionant les opcions de localització</title> + +<para> + +En la majoria dels casos, les primeres qüestions que us apareixaran +faran referència a les opcions de localització a utilitzar en la +instal·lació i pel sistema instal·lat. Les opcions de localització +consisteixen en l'idioma, el país i el locales. + +</para><para> + +L'idioma seleccionat s'utilitzarà en la resta del procés d'instal·lació, +es disposa d'una traducció de les diferents caixes de diàleg. +En cas de no existir una traducció de l'idioma seleccionat, +l'instal·lador utilitzarà la traducció de l'anglès. + +</para><para> + +El país seleccionat s'utilitzarà posteriorment en el procés d'instal·lació +per seleccionar el fus horari predeterminat i una rèplica apropiada en +funció de la vostra ubicació geogràfica. L'idioma i el país s'utilitzaran +per definir el locale predeterminat del sistema i per ajudar en la +selecció del teclat. + +</para><para> + +Primer se us demanarà que seleccioneu el vostre idioma preferit. Els +noms dels idiomes estan llistats en anglès (banda esquerra) i en +el propi idioma (banda dreta); els noms de la banda dreta +es mostren utilitzant la tipografia pròpia de l'idioma. La llista +està ordenada en funció dels noms en anglès. Al capdemunt de la llista +hi ha un opció extra que permet seleccionar el locale <quote>C</quote> +en comptes d'un idioma. Si seleccioneu el locale <quote>C</quote> +la instal·lació es realitzarà en anglès; el sistema instal·lat +no disposarà del suport per a la localització, ja que el paquet +<classname>locales</classname> no estarà instal·lat. + +</para><para> + +Si heu seleccionant un idioma que està reconegut com a idioma oficial +en més d'un país<footnote> + +<para> + +En termes tècnics: en cas que hi hagi múltiples locales per l'idioma amb +diferents codis de país. + +</para> + +</footnote>, se us demanarà que seleccioneu un país. +Si seleccioneu l'opció <guimenuitem>Altres</guimenuitem> de la part inferior +de la llista, us apareixerà una llista de tot els països, agrupats +per continent. En cas que l'idioma únicament tingui un país associat, +aquest es seleccionarà automàticament. + +</para><para> + +Se seleccionarà un locale predeterminat en funció de l'idioma i país +seleccionats. +Si esteu en una instal·lació de prioritat mitjana o baixa, podreu +seleccionar un locale predeterminat diferent i seleccionar locales +addicionals a generar pel sistema instal·lat. + +</para> + </sect3> diff --git a/ca/using-d-i/modules/lowmem.xml b/ca/using-d-i/modules/lowmem.xml new file mode 100644 index 000000000..bd4bada12 --- /dev/null +++ b/ca/using-d-i/modules/lowmem.xml @@ -0,0 +1,21 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 16990 --> + + <sect3 id="lowmem"> + <title>Comprovació de la memòria disponible</title> + +<para> + +Una de les primeres coses que fa el &d-i; és comprovar la memòria +disponible. Si la memòria disponible és limitada, el component +realitzarà algunes modificacions en el procés d'instal·lació +que us haurien de permetre instal·lar &debian; al sistema. + +</para><para> + +Durant una instal·lació en una sistema amb poca memòria no +es podrà accedir a tots els components. Una de les limitacions +és que no podreu triar l'idioma de la instal·lació. + +</para> + </sect3> diff --git a/ca/using-d-i/modules/lvmcfg.xml b/ca/using-d-i/modules/lvmcfg.xml new file mode 100644 index 000000000..989c72843 --- /dev/null +++ b/ca/using-d-i/modules/lvmcfg.xml @@ -0,0 +1,100 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 30207 --> + + <sect3 id="lvmcfg"> + <title>Configurant el Gestor de Volums Lògics (LVM)</title> +<para> + +Si esteu utilitzant l'ordinador com a administrador de sistemes o +usuari <quote>avançat</quote>, segur que us heu trobat en la situació +que alguna partició del disc (normalment la més important) ha +exhaurit tot l'espai lliure, mentre que d'altres particions estan +molt poc utilitzades i heu hagut de reconduir la situació movent +continguts, creant enllaços simbòlics, etc. + +</para><para> + +Per evitar la situació descrita anteriorment podeu utilitzar el Gestor +de Volums Lògics (LVM). Resumit d'una manera fàcil, amb LVM podeu +combinar particions (anomenades <firstterm>volums físics</firstterm> en +l'entorn de LVM) per formar un disc virtual (anomenat <firstterm>grup de +volums</firstterm>), que es pot dividir en particions virtuals +(<firstterm>volums lògics</firstterm>). La característica interessant és +que els volums lògics (i per descomptat els grups de volums associats) +es poden expandir a través de múltiples discs físics. + +</para><para> + +En cas d'adonar-vos que necessiteu més espai per a l'antiga partició +<filename>/home</filename> de 160GB, simplement podeu afegir un nou +disc de 300GB i ajuntar-lo al grup de volums i seguidament redimensionar +el volum lògic que disposa el sistema de fitxers <filename>/home</filename> i +per art de màgia — els usuaris disposaran de més espai en +la seva nova partició de 460GB. Aquest exemple està un pèl sobresimplificat. +Llegiu el document <ulink url="&url-lvm-howto;">LVM HOWTO</ulink> en cas +d'encara no haver-ho fet. + +</para><para> + +La configuració de LVM en l'&d-i; és força simple. Primer heu de +marcar les particions per a ser utilitzades com a volums físics +per part de LVM (l'opció s'habilita al <command>partman</command> +al menú <guimenu>Paràmetres de la partició</guimenu> on hauríeu +de seleccionar <menuchoice> <guimenu>Utilitza com a:</guimenu> +<guimenuitem>volum físic per a LVM</guimenuitem> </menuchoice>). +Seguidament inicieu el mòdul <command>lvmcfg</command> (directament +a través de <command>partman</command> o a través de l'opció +del menú principal del &d-i;) i combineu volums físics amb grups +de volums a través del menú <guimenuitem>Modifica els volums de grups (VG) +</guimenuitem>. A continuació hauríeu de crear volums lògics sobre +els grups de volums al menú <guimenuitem>Modifica els volums lògics (LV) +</guimenuitem>. + +<note arch="powerpc" condition="sarge"><para> + +No hi ha un estàndard àmpliament acceptat per identificar les particions +que contenen dades LVM en el cas del maquinari de l'Apple Power Macintosh. +En aquest maquinari concret, el procediment anterior per a la creació de +volums física i grups de volums no funcionarà. Hi ha una bona solució +alternativa per a aquesta limitació, considerant que sou coneixedor de +les eines associades al LVM. + +</para><para> + +Per a la instal·lació utilitzant volums lògics en el maquinari del +Power Macintosh hauríeu de crear segons el procediment normal, totes les + particions del disc pels volums lògics. En el menú <guimenu>Paràmetres +de la partició</guimenu> hauríeu de seleccionar <menuchoice><guimenu> +Utilitza com a:</guimenu><guimenuitem>No ho utilitzis</guimenuitem> +</menuchoice> per a les particions (no us apareixerà l'opció +d'utilitzar la partició com un volum físic). Un cop creades les particions, +hauríeu d'iniciar el gestor de volums lògics. Tot i això, com que no +s'han creat volums físics heu d'accedir a l'intèrpret d'ordres +disponible al segon terminal virtual (vegeu <xref linkend="shell"/>) i +crear-los manualment. + +</para><para> + +Per crear un volum físic en cada una de les particions escollides, +utilitzeu l'ordre <command>pvcreate</command> a l'indicador de +l'intèrpret d'ordres. Seguidament utilitzeu l'ordre <command> +vgcreate</command> per crear cada grup de volums. Podeu ignorar +els errors referents a les sumes de verificació de les capçaleres +de l'àrea de metadades i els errors de l'fsync. Un cop creats +tots els grups de volums, hauríeu de tornar al primer terminal +virtual i saltar directament a l'element del menú +<command>lvmcfg</command> per a la gestió de volums lògics. +Visualitzareu els grups de volums i podreu crear els volums +lògics necessari seguint el mètode habitual. + +</para></note> + +</para><para> + +Un cop finalitzada l'execució de <command>lvmcfg</command> torneu a +<command>partman</command>, visualitzareu qualsevol volum lògic creat +de la mateixa manera que les particions ordinàries (i les haureu +de gestionar de la mateixa manera). + +</para> + </sect3> diff --git a/ca/using-d-i/modules/mdcfg.xml b/ca/using-d-i/modules/mdcfg.xml new file mode 100644 index 000000000..3b91f4421 --- /dev/null +++ b/ca/using-d-i/modules/mdcfg.xml @@ -0,0 +1,229 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 27118 --> + + <sect3 id="mdcfg"> + <title>Configuració de dispositius de discs múltiples (RAID de programari)</title> +<para> + +Si teniu més d'un disc dur<footnote><para> + +Per ser honestos, podeu construir dispositius de discs múltiples fins +i tot a partir de particions en un mateix dispositiu físic, però això no us +portarà a res útil. + +</para></footnote> en el vostre ordinador, podeu utilitzar el +<command>mdcfg</command> per configurar els vostres discs per obtenir +un millor rendiment i/o més seguretat en les vostres dades. El +resultat s'anomena <firstterm>dispositiu de discs múltiples</firstterm> (MD) +(o la seva variant més coneguda, <firstterm>RAID de programari</firstterm>). + +</para><para> + +Els MD són bàsicament un grapat de particions localitzades a diversos discs i +que es combinen juntes per formar un dispositiu <emphasis>lògic</emphasis>. +Aquest dispositiu es pot utilitzar llavors com una partició ordinària (p.ex. +en el <command>partman</command> la podeu formatar, assignar-li un punt de +muntatge, etc.). + +</para><para> + +El benefici que obteniu depèn del tipus de dispositiu MD que creeu. Actualment +se suporten: + +<variablelist> +<varlistentry> + +<term>RAID0</term><listitem><para> + +S'enfoca principalment al rendiment. El RAID0 reparteix totes les dades +entrants en <firstterm>bandes</firstterm> i les distribueix de la mateixa +manera sobre cada disc de la matriu. Això pot augmentar la velocitat de +les operacions de lectura/escriptura, però quan un dels discs falla, ho +perdreu <emphasis>tot</emphasis> (part de la informació encara és al disc/s +sa, l'altra part <emphasis>era</emphasis> al disc que ha fallat). + +</para><para> + +L'ús típic del RAID0 és una partició per edició de vídeo. + +</para></listitem> +</varlistentry> +<varlistentry> + +<term>RAID1</term><listitem><para> + +És adequat per les configuracions on la fiabilitat és la primera preocupació. +Consisteix en diverses (usualment dues) particions de la mateixa mida en les +quals es guarden les mateixes dades. Això significa essencialment tres coses. +La primera, que si un dels discs falla, encara teniu les dades repetides en +els discs restants. La segona, que només podeu utilitzar una fracció de la +capacitat disponible (més precisament, la mida de la partició més petita del +RAID). La tercera, que les lectures als fitxers s'equilibren entre els discs, +cosa que pot augmentar el rendiment en un servidor, com un servidor de fitxers, +que tendeix a carregar-se amb més lectures que no pas escriptures. + +</para><para> + +Opcionalment podeu tenir un disc de recanvi en la matriu que agafaria el lloc +del disc espatllat en cas de fallida. + +</para></listitem> +</varlistentry> +<varlistentry> + +<term>RAID5</term><listitem><para> + +És un bon compromís entre velocitat, rendiment i redundància de les dades. +El RAID5 reparteix totes les dades entrants en bandes i les distribueix +equitativament entre tots els discs excepte un (similar al RAID0). A +diferència del RAID0, el RAID5 també calcula informació de +<firstterm>paritat</firstterm>, que s'escriu en el disc restant. El disc +de paritat no és estàtic (això seria l'anomenat RAID4), sinó que canvia +periòdicament, de manera que la informació de paritat es distribueixi +equitativament entre tots els discs. Quan un dels discs falla, la part +d'informació que falta es pot calcular a partir de les dades restants i +de la seva paritat. El RAID5 ha de consistir en almenys tres particions +actives. Opcionalment podeu tenir un disc de recanvi en la matriu, el +qual agafaria el lloc del disc espatllat en cas de fallida. + +</para><para> + +Com podeu veure, el RAID5 té un grau de rendiment similar al RAID1 però +aconsegueix menys redundància. Per altra banda pot resultar una mica +més lent en les operacions d'escriptura que no pas el RAID0 degut al +càlcul de la informació de paritat. + +</para></listitem> +</varlistentry> +</variablelist> + +Per fer un sumari: + +<informaltable> +<tgroup cols="5"> +<thead> +<row> + <entry>Tipus</entry> + <entry>Dispositius mínims</entry> + <entry>Dispositiu de recanvi</entry> + <entry>Sobreviu a una fallida de disc?</entry> + <entry>Espai disponible</entry> +</row> +</thead> + +<tbody> +<row> + <entry>RAID0</entry> + <entry>2</entry> + <entry>no</entry> + <entry>no</entry> + <entry>Mida de la partició més petita multiplicada pel nombre de + dispositius en el RAID</entry> +</row> + +<row> + <entry>RAID1</entry> + <entry>2</entry> + <entry>opcional</entry> + <entry>sí</entry> + <entry>Mida de la partició més petita en el RAID</entry> +</row> + +<row> + <entry>RAID5</entry> + <entry>3</entry> + <entry>opcional</entry> + <entry>sí</entry> + <entry>Mida de la partició més petita multiplicada pel (nombre de + dispositius en el RAID menys ú) + </entry> +</row> + +</tbody></tgroup></informaltable> + +</para><para> + +Si voleu conèixer tota la veritat sobre el RAID de programari, doneu +un cop d'ull al <ulink url="&url-software-raid-howto;">COM ES FA del RAID +de programari</ulink>. + +</para><para> + +Per crear un dispositiu MD, necessiteu tenir les particions de què +desitgeu que consti marcades per a ser usades en un RAID. (Això és fa +en el menú <guimenu>Paràmetres de la partició</guimenu> del +<command>partman</command> on hauríeu de seleccionar <menuchoice> +<guimenu>Utilitza-ho com:</guimenu> <guimenuitem>volum físic per a +RAID</guimenuitem> </menuchoice>). + +</para><warning><para> + +El suport per MD és una addició relativament nova a l'instal·lador. +Podeu experimentar problemes per alguns nivells de RAID i en +combinació amb alguns carregadors de l'arrencada si intenteu +utilitzar MD pel sistema de fitxers arrel (<filename>/</filename>). +Pels usuaris experimentats, pot ser possible solucionar temporalment +alguns d'aquests problemes executant manualment alguns passos de la +configuració o de la instal·lació des d'un intèrpret d'ordres. + +</para></warning><para> + +A continuació, hauríeu d'elegir <guimenuitem>Configura el RAID de +programari</guimenuitem> del menú principal del <command>partman</command>. +A la primera pantalla del <command>mdcfg</command> seleccioneu simplement +<guimenuitem>Crea dispositius MD</guimenuitem>. Se us presentarà una +llista dels tipus de dispositius MD suportats, dels quals n'haureu +d'escollir un (p.ex. RAID1). El que segueixi dependrà del tipus de MD que +seleccioneu. + +</para> + +<itemizedlist> +<listitem><para> + +El RAID0 és senzill — se us proporcionarà una llista de les +particions RAID disponibles i la vostra única tasca serà seleccionar +la partició que formarà el MD. + +</para></listitem> +<listitem><para> + +El RAID1 és una mica més delicat. Primer, se us demanarà que introduïu +el nombre de dispositius actius i el nombre de dispositius de recanvi que +formaran el MD. A continuació, necessitareu seleccionar d'una llista de +les particions RAID disponibles aquelles que seran actives i aquelles que +serviran de recanvi. El compte de particions seleccionades ha de ser igual +al nombre proporcionat uns segons abans. No us preocupeu. Si feu un error i +seleccioneu un nombre diferent de particions, el &d-i; no us permetrà +continuar fins que corregiu la qüestió. + +</para></listitem> +<listitem><para> + +El RAID5 té un procediment de configuració similar al RAID1 amb l'excepció +que necessitareu utilitzar almenys <emphasis>tres</emphasis> particions +actives. + +</para></listitem> +</itemizedlist> + +<para> + +És perfectament possible tenen diversos tipus de MD a la vegada. Per +exemple si teniu tres discs durs de 200 GB dedicats a MD, i cadascun +conté dues particions de 100 GB, podeu combinar les primeres particions +dels tres discs en un RAID0 (partició ràpida de 300 GB per edició de vídeo) +i utilitzar les altres tres particions (2 actives i 1 de recanvi) per +un RAID1 (una partició bastant fiable de 100 GB pel +<filename>/home</filename>). + +</para><para> + +Després que hàgiu configurat les dispositius MD al vostre gust, podeu +seleccionar <guimenuitem>Finalitza</guimenuitem> el <command>mdcfg</command> +per retornar al <command>partman</command> per crear els sistemes de fitxers +en els nous dispositius MD i assignar-los els atributs usuals com els punts +de muntatge. + +</para> + </sect3> diff --git a/ca/using-d-i/modules/mips/arcboot-installer.xml b/ca/using-d-i/modules/mips/arcboot-installer.xml new file mode 100644 index 000000000..13eba925e --- /dev/null +++ b/ca/using-d-i/modules/mips/arcboot-installer.xml @@ -0,0 +1,69 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 24663 untranslated --> + + <sect3 arch="mips"> + <title><command>arcboot</command>-installer</title> +<para> + +The boot loader on SGI Indys is <command>arcboot</command>. +It has to be installed on the same hard disk as the kernel (this is done +automatically by the installer). Arcboot supports different configurations +which are set up in <filename>/etc/arcboot.conf</filename>. Each +configuration has a unique name, +the default setup as created by the installer is <quote>linux</quote>. +After arcboot has been installed, the system can be booted from hard disk +by setting some firmware environment variables entering + +<informalexample><screen> +<userinput> setenv SystemPartition scsi(<replaceable>scsi</replaceable>)disk(<replaceable>disk</replaceable>)rdisk(0)partition(0)</userinput> +<userinput> setenv OSLoadPartition scsi(<replaceable>scsi</replaceable>)disk(<replaceable>disk</replaceable>)rdisk(0)partition(<replaceable>partnr</replaceable>)</userinput> +<userinput> setenv OSLoader arcboot</userinput> +<userinput> setenv OSLoadFilename <replaceable>config</replaceable></userinput> +<userinput> setenv AutoLoad yes</userinput> +</screen></informalexample> + +on the firmware prompt, and then typing <command>boot</command>. + +</para> + +<variablelist> +<varlistentry> +<term> <replaceable>scsi</replaceable> </term> +<listitem><para> + +is the SCSI bus to be booted from, this is <userinput>0</userinput> +for the onboard controllers + +</para></listitem> +</varlistentry> +<varlistentry> +<term> <replaceable>disk</replaceable> </term> +<listitem><para> + +is the SCSI ID of the hard disk on which <command>arcboot</command> is +installed + +</para></listitem> +</varlistentry> +<varlistentry> +<term> <replaceable>partnr</replaceable> </term> +<listitem><para> + +is the number of the partition on which +<filename>/etc/arcboot.conf</filename> resides + +</para></listitem> +</varlistentry> +<varlistentry> +<term> <replaceable>config</replaceable> </term> +<listitem><para> + +is the name of the configuration entry in +<filename>/etc/arcboot.conf</filename>, which is <quote>linux</quote> by +default. + +</para></listitem> +</varlistentry> +</variablelist> + + </sect3> diff --git a/ca/using-d-i/modules/mipsel/colo-installer.xml b/ca/using-d-i/modules/mipsel/colo-installer.xml new file mode 100644 index 000000000..29dc138a1 --- /dev/null +++ b/ca/using-d-i/modules/mipsel/colo-installer.xml @@ -0,0 +1,2 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 14337 --> diff --git a/ca/using-d-i/modules/mipsel/delo-installer.xml b/ca/using-d-i/modules/mipsel/delo-installer.xml new file mode 100644 index 000000000..7325398ac --- /dev/null +++ b/ca/using-d-i/modules/mipsel/delo-installer.xml @@ -0,0 +1,76 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 24663 untranslated --> + + <sect3 arch="mipsel"> + <title><command>delo</command>-installer</title> +<para> + +The boot loader on DECstations is <command>DELO</command>. +It has to be installed on the same hard disk as the kernel (this is done +automatically by the installer). DELO supports different configurations +which are set up in <filename>/etc/delo.conf</filename>. Each +configuration has a unique name, +the default setup as created by the installer is <quote>linux</quote>. +After DELO has been installed, the system can be booted from hard disk +by entering + +<informalexample><screen> +<userinput>boot <replaceable>#</replaceable>/rz<replaceable>id</replaceable> <replaceable>partnr</replaceable>/<replaceable>name</replaceable></userinput> +</screen></informalexample> + +on the firmware prompt. + +</para> + +<variablelist> +<varlistentry> +<term> <replaceable>#</replaceable> </term> +<listitem><para> + +is the TurboChannel device to be booted from, on most DECstations this +is <userinput>3</userinput> for the onboard controllers + +</para></listitem> +</varlistentry> +<varlistentry> +<term> <replaceable>id</replaceable> </term> +<listitem><para> + +is the SCSI ID of the hard disk on which <command>DELO</command> is +installed + +</para></listitem> +</varlistentry> +<varlistentry> +<term> <replaceable>partnr</replaceable> </term> +<listitem><para> + +is the number of the partition on which +<filename>/etc/delo.conf</filename> resides + +</para></listitem> +</varlistentry> +<varlistentry> +<term> <replaceable>name</replaceable> </term> +<listitem><para> + +is the name of the configuration entry in +<filename>/etc/delo.conf</filename>, which is <quote>linux</quote> by +default. + +</para></listitem> +</varlistentry> +</variablelist> + +<para> + +In case <filename>/etc/delo.conf</filename> is on the first partition +on the disk and the default configuration shall be booted, it is +sufficient to use + +<informalexample><screen> +<userinput>boot #/rz<replaceable>id</replaceable></userinput> +</screen></informalexample> + +</para> + </sect3> diff --git a/ca/using-d-i/modules/netcfg.xml b/ca/using-d-i/modules/netcfg.xml new file mode 100644 index 000000000..e3d972f18 --- /dev/null +++ b/ca/using-d-i/modules/netcfg.xml @@ -0,0 +1,59 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 23058 --> + + <sect3 id="netcfg"> + <title>Configuració de la xarxa</title> + +<para> + +Quan entreu en aquest pas, si el sistema detecta que teniu més d'un +dispositiu de xarxa, se us demanarà que elegiu quin dispositiu serà +la vostra interfície de xarxa <emphasis>primària</emphasis>, és a dir, +la que voleu utilitzar per a la instal·lació. Les altres interfícies no +es configuraran en aquest moment. Podeu configurar les altres interfícies +un cop hagi finalitzat la instal·lació; vegeu la pàgina de manual +<citerefentry><refentrytitle>interfaces</refentrytitle> +<manvolnum>5</manvolnum></citerefentry>. + +</para><para> + +De manera predeterminada, el &d-i; intenta configurar la xarxa del vostre +ordinador automàticament via DHCP. Si la prova té èxit, ja estareu. Si la +prova falla es pot deure a molts factors, des d'un cable de xarxa +desconnectat, fins a una mala configuració del DHCP. O potser no disposeu +d'un servidor DHCP a la vostra xarxa local. Per a més explicacions comproveu +els missatges d'error a la tercera consola. En qualsevol cas, se us +preguntarà si ho voleu tornar a intentar, o si voleu realitzar una +configuració manual. Els servidors DHCP de vegades son realment lents en +les seves respostes, per tant, si esteu segurs que tot és correcte, +intenteu-ho de nou. + +</para><para> + +La configuració manual de la xarxa us preguntarà algunes qüestions sobre +la vostra xarxa, notablement +<computeroutput>L'adreça IP</computeroutput>, +<computeroutput>La màscara de la subxarxa</computeroutput>, +<computeroutput>La passarel·la</computeroutput>, +<computeroutput>L'adreça del servidor de noms</computeroutput>, i un +<computeroutput>nom per l'ordinador</computeroutput>. +A més, si teniu una interfície de xarxa sense fils, se us demanarà que +indiqueu el vostre <computeroutput>Wireless ESSID</computeroutput> i una +<computeroutput>clau WEP</computeroutput>. Ompliu-ho amb les respostes de +<xref linkend="needed-info"/>. + +</para><note><para> + +Alguns detalls tècnics que podeu, o no, trobar útils: el programa +suposa que l'adreça IP de la xarxa és l'AND bit a bit de la IP +del vostre sistema i la màscara. Suposarà que l'adreça de difusió és +l'OR bit a bit de l'adreça IP del vostre sistema amb la negació bit a bit +de la màscara. També endevinarà la passarel·la. Si no podeu trobar +alguna d'aquestes respostes, utilitzeu les propostes del sistema — +si és necessari, podeu canviar-les un cop el sistema s'hagi instal·lat +editant el fitxer <filename>/etc/network/interfaces</filename>. +Alternativament, podeu instal·lar l'<classname>etherconf</classname>, que +us guiarà pas a pas a través de la configuració de la vostra xarxa. + +</para></note> + </sect3> diff --git a/ca/using-d-i/modules/network-console.xml b/ca/using-d-i/modules/network-console.xml new file mode 100644 index 000000000..40e90f6ee --- /dev/null +++ b/ca/using-d-i/modules/network-console.xml @@ -0,0 +1,107 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 30086 untranslated --> + + <sect3 id="network-console"> + <title>Installation Over the Network</title> + +<para arch="not-s390"> + +One of the more interesting components is +<firstterm>network-console</firstterm>. It allows you to do a large +part of the installation over the network via SSH. The use of the +network implies you will have to perform the first steps of the +installation from the console, at least to the point of setting up +the networking. (Although you can automate that part with +<xref linkend="automatic-install"/>.) + +</para><para arch="not-s390"> + +This component is not loaded into the main installation menu by default, +so you have to explicitly ask for it. + +If you are installing from CD, you need to boot with medium priority or +otherwise invoke the main installation menu and choose <guimenuitem>Load +installer components from CD</guimenuitem> and from the list of +additional components select <guimenuitem>network-console: Continue +installation remotely using SSH</guimenuitem>. Successful load is +indicated by a new menu entry called <guimenuitem>Continue +installation remotely using SSH</guimenuitem>. + +</para><para arch="s390"> + +For installations on &arch-title;, this is the default method after +setting up the network. + +</para><para> + +<phrase arch="not-s390">After selecting this new entry, you</phrase> +<phrase arch="s390">You</phrase> will be asked for a new password +to be used for connecting to the installation system and for its +confirmation. That's all. Now you should see a screen which instructs +you to login remotely as the user <emphasis>installer</emphasis> with +the password you just provided. Another important detail to notice on +this screen is the fingerprint of this system. You need to transfer +the fingerprint securely to the <quote>person who will continue the +installation remotely</quote>. + +</para><para> + +Should you decide to continue with the installation locally, you +can always press &enterkey;, which will bring you back to +the main menu, where you can select another component. + +</para><para> + +Now let's switch to the other side of the wire. As a prerequisite, you +need to configure your terminal for UTF-8 encoding, because that is +what the installation system uses. If you do not, remote installation +will be still possible, but you may encounter strange display +artefacts like destroyed dialog borders or unreadable non-ascii +characters. Establishing a connection with the installation system +is as simple as typing: + +<informalexample><screen> +<prompt>$</prompt> <userinput>ssh -l installer <replaceable>install_host</replaceable></userinput> +</screen></informalexample> + +Where <replaceable>install_host</replaceable> is either the name +or IP address of the computer being installed. Before the actual +login the fingerprint of the remote system will be displayed and +you will have to confirm that it is correct. + +</para><note><para> + +If you install several computers in turn and they happen to have the +same IP address or hostname, <command>ssh</command> will refuse to connect +to such host. The reason is that it will have different fingerprint, which +is usually a sign of a spoofing attack. If you are sure this is not the +case, you will need to delete the relevant line from +<filename>~/.ssh/known_hosts</filename> and try again. + +</para></note><para> + +After the login you will be presented with an initial screen where you +have two possibilities called <guimenuitem>Start menu</guimenuitem> and +<guimenuitem>Start shell</guimenuitem>. The former brings you to the +main installer menu, where you can continue with the installation as +usual. The latter starts a shell from which you can examine and possibly +fix the the remote system. You should only start one SSH session for the +installation menu, but may start multiple sessions for shells. + +</para><warning><para> + +After you have started the installation remotely over SSH, you should +not go back to the installation session running on the local console. +Doing so may corrupt the database that holds the configuration of +the new system. This in turn may result in a failed installation or +problems with the installed system. + +</para><para> + +Also, if you are running the SSH session from an X terminal, you should +not resize the window as that will result in the connection being +terminated. + +</para></warning> + + </sect3> diff --git a/ca/using-d-i/modules/nobootloader.xml b/ca/using-d-i/modules/nobootloader.xml new file mode 100644 index 000000000..82b480163 --- /dev/null +++ b/ca/using-d-i/modules/nobootloader.xml @@ -0,0 +1,31 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 25513 --> + + <sect3 id="nobootloader"> + <title>Continuant sense el carregador d'arrencada</title> + +<para> + +Aquesta opció es pot utilitzar per finalitzar la instal·lació tot +i no instal·lar un carregador de l'arrencada, ja sigui perquè +l'arq/subarq no en proporciona cap, o perquè no us és necessari +(ex. utilitzareu el carregador d'arrencada existent). +<phrase arch="m68k">Aquesta opció és especialment útil pels +sistemes Macintosh, Atari i Amiga, on s'ha de mantenir el sistema +operatiu original i utilitzar-lo per arrencar el GNU/Linux.</phrase> + +</para><para> + +Si preteneu configurar manualment el carregador de l'arrencada, +hauríeu de comprovar el nom del nucli instal·lat a +<filename>/target/boot</filename>. +També hauríeu de comprovar si hi ha el fitxer +<firstterm>initrd</firstterm> i, si és el cas, probablement indicar-li al carregador +de l'arrencada. Informació addicional que us farà falta correspon +al disc i partició que heu seleccionat anteriorment pel sistema de fitxers +<filename>/</filename> i, en el cas d'escollir instal·lar el +<filename>/boot</filename> en una partició separada, +el sistema de fitxers <filename>/boot</filename>. + +</para> + </sect3> diff --git a/ca/using-d-i/modules/os-prober.xml b/ca/using-d-i/modules/os-prober.xml new file mode 100644 index 000000000..ff4574ae3 --- /dev/null +++ b/ca/using-d-i/modules/os-prober.xml @@ -0,0 +1,39 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 27596 --> + + <sect3 id="os-prober"> + <title>Detectant d'altres sistemes operatius</title> + +<para> + +Previ a la instal·lació del carregador de l'arrencada l'instal·lador +intentarà detectar d'altres sistemes operatius instal·lats a +la màquina. Si detecta un sistema operatiu suportat se us informarà +en el pas d'instal·lació del carregador de l'arrencada i +l'ordinador es configurarà per arrencar-lo addicionalment +a Debian. + +</para><para> + +Recordeu que l'arrencada de múltiples sistemes operatius en una sola +màquina continua sent una qüestió de màgia negra. El suport automàtic +de detecció i configuració dels carregadors de l'arrencada per arrencar +d'altres sistemes operatius varia en funció de l'arquitectura i inclús +subarquitectura. Si no us funciona hauríeu de buscar més informació +a la documentació del gestor de l'arrencada. + +<!-- TODO: Maybe include some arch-dependent tables with supported OS'es here --> + +</para> + +<note condition="sarge"><para> + +L'instal·lador pot no detectar d'altres sistemes operatius si les particions +on estan instal·lats estan muntats durant la detecció. Aquesta situació es +podria donar si seleccioneu un punt de muntatge (ex. /win) per a una partició +que contigui un altre sistemes operatiu a <command>partman</command>, +o si heu muntat les particions manualment des de la consola. + +</para></note> + + </sect3> diff --git a/ca/using-d-i/modules/partconf.xml b/ca/using-d-i/modules/partconf.xml new file mode 100644 index 000000000..9442b9d2f --- /dev/null +++ b/ca/using-d-i/modules/partconf.xml @@ -0,0 +1,2 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 11648 --> diff --git a/ca/using-d-i/modules/partitioner.xml b/ca/using-d-i/modules/partitioner.xml new file mode 100644 index 000000000..5ab979f43 --- /dev/null +++ b/ca/using-d-i/modules/partitioner.xml @@ -0,0 +1,3 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 11648 --> + diff --git a/ca/using-d-i/modules/partman.xml b/ca/using-d-i/modules/partman.xml new file mode 100644 index 000000000..9729de8a3 --- /dev/null +++ b/ca/using-d-i/modules/partman.xml @@ -0,0 +1,209 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 30158 --> + + <sect3 id="partman"> + <title>Particionant els discs</title> + +<para> + +Ha arribat el moment de particionar els discs. Si no esteu convençuts +de com particionar o simplement voleu obtenir més informació, vegeu +<xref linkend="partitioning"/>. + +</para><para> + +Primer podreu particionar automàticament la unitat sencera +o l'espai lliure corresponent. Aquesta opció s'anomena +partició <quote>guiada</quote>. Si no voleu la partició +automàtica escolliu l'opció del menú +<guimenuitem>Editar manualment la taula de particions</guimenuitem>. + +</para><para> + +Si escolliu la partició guiada podreu escollir entre els esquemes +que es llisten a la taula següent. Tots els esquemes tenen els seus +avantatges els seus inconvenients, alguns dels quals es discuteixen a +<xref linkend="partitioning"/>. Si no n'esteu segurs, escolliu +la primera opció. Heu de tenir present que la partició guiada precisa +d'un mínim d'espai lliure amb el qual treballar. Si no li assigneu +un mínim de 1GB d'espai (en funció de l'esquema escollit), es +produirà un error en la partició guiada. + +</para> + +<informaltable> +<tgroup cols="3"> +<thead> +<row> + <entry>Esquema de partició</entry> + <entry>Espai mínim</entry> + <entry>Particions creades</entry> +</row> +</thead> + +<tbody> +<row> + <entry>Tots els fitxers en una partició</entry> + <entry>600MB</entry> + <entry><filename>/</filename>, swap</entry> +</row><row> + <entry>Màquina d'escriptori</entry> + <entry>500MB</entry> + <entry> + <filename>/</filename>, <filename>/home</filename>, swap + </entry> +</row><row> + <entry>Estació de treball multiusuari</entry> + <entry>1GB</entry> + <entry> + <filename>/</filename>, <filename>/home</filename>, + <filename>/usr</filename>, <filename>/var</filename>, + <filename>/tmp</filename>, swap + </entry> +</row> + +</tbody></tgroup></informaltable> + +<para arch="ia64"> + +Si escolliu la partició automàtica per un sistema IA64 hi haurà +una partició addicional formatejada com un sistema de fitxers +arrencable FAT16, pel carregador de l'arrencada EFI. +També hi ha un opció addicional del menú de formatat per +configurar manualment una partició com a partició d'arrencada EFI. + +</para><para arch="alpha"> + +Si escolliu la partició automàtica per un sistema Alpha, s'assignarà +una partició no formatada addicional a l'inici del disc per reservar +espai pel carregador de l'arrencada aboot. + +</para><para> + +Després de la selecció d'un esquema, la pantalla següent mostrarà +la nova taula de particions, on s'inclourà informació respecte a si +i com es formataran les particions i on es muntaran. + +</para><para> + +La llista de particions hauria de ser similar a: + +<!-- TODO: show some flags here (lightning, skull, smiley) --> +<informalexample><screen> + IDE1 master (hda) - 6.4 GB WDC AC36400L + #1 primary 16.4 MB ext2 /boot + #2 primary 551.0 MB swap swap + #3 primary 5.8 GB ntfs + pri/log 8.2 MB FREE SPACE + + IDE1 slave (hdb) - 80.0 GB ST380021A + #1 primary 15.9 MB ext3 + #2 primary 996.0 MB fat16 + #3 primary 3.9 GB xfs /home + #5 logical 6.0 GB ext3 / + #6 logical 1.0 GB ext3 /var + #7 logical 498.8 MB ext3 + #8 logical 551.5 MB swap swap + #9 logical 65.8 GB ext2 +</screen></informalexample> + +L'exemple mostra dos discs dur IDE dividits en múltiples particions; +el primer disc disposa d'espai lliure. Cada línia de partició disposa +del número de partició, el tipus, mida, senyaladors opcionals, sistema +de fitxers i punt de muntatge (si n'hi ha). + +</para><para> + +En aquest punt finalitza la partició guiada. Si la taula de particions +generada satisfà les vostres necessitats podeu escollir l'opció +de menú +<guimenuitem>Finalitza la partició i escriu els canvis al disc</guimenuitem> +per desar la nova taula de particions (tal i com es descriu +al final d'aquesta secció). Si no satisfà les vostres necessitats podeu +escollir l'opció <guimenuitem>Desfés els canvis de les particions</guimenuitem> +per tornar a executar la partició guiada o modifica els canvis proposats +tal i com es descriu posteriorment en la partició manual. + +</para><para> + +En cas d'escollir la partició manual us apareixerà una pantalla +similar a la mostrada anteriorment, exceptuant que es mostrarà +la taula de particions actual i sense els punts de muntatges. +El mètode per configurar manualment la taula de particions i +la utilització de les particions per part de Debian es descriurà +al llarg de la resta de la secció. + +</para><para> + +Si escolliu un disc nou sense particions o espai lliure, se us oferirà +la possibilitat de crear una nova taula de particions (és necessària +per crear noves particions). Posteriorment hauria d'aparèixer +una nova línia sota el disc seleccionat +amb el títol <quote>ESPAI LLIURE</quote>. + +</para><para> + +Si seleccioneu l'espai lliure se us oferirà la possibilitat de crear +una nova partició. Haureu de contestar a una sèrie de qüestions +ràpides referents a la mida, tipus (primària o lògica) i la ubicació +(al principi o al final de l'espai lliure). Posteriorment se us +presentarà la informació referent a la nova partició. Hi ha opcions +com el punt de muntatges, opcions de muntatge, senyaladors d'arrencada +o el mètode d'utilització. Podeu modificar lliurements els valors +predeterminats en funció de les vostres necessitats. Ex. +seleccionant l'opció <guimenuitem>Utilitza com:</guimenuitem>, +podeu seleccionar si utilitzar la partició per a swap, RAID per +software, LVM o cap utilitat específica. Una altra característica +interessant és la possibilitat de copiar les dades des de +particions existents a la nova. +Un cop la nova partició satisfaci les vostres necessitats seleccioneu +l'opció <guimenuitem>S'ha finalitzat de preparar la partició</guimenuitem> i +retorneu a la pantalla principal del <command>partman</command>. + +</para><para> + +Si voleu modificar alguna característica de la partició seleccioneu-la +i accedireu al menú de configuració de la partició. Com que és la mateixa +pantalla que la utilitzada en la creació de noves particions, podreu +modificar-ne les mateixes característiques. Una característica que +probablement no sigui evident en un primer moment és la possibilitat +de modificar la mida de la partició seleccionant l'element +que mostra la mida de la partició. Els sistemes de fitxers que s'han +comprovat que funcionen són, com a mínim, fat16, fat32, ext2, ext3 +i swap. Aquest menú també us permet suprimir una partició. + +</para><para> + +Assegureu-vos de crear un mínim de dues particions: una pel +sistema de fitxers +<emphasis>root</emphasis> (que s'ha de muntar com a +<filename>/</filename>) i una pel <emphasis>swap</emphasis>. +Si us oblideu de muntar el sistema de fitxers root, el +<command>partman</command> no us deixarà continuar fins +que no solucioneu el problema. + +</para><para arch="ia64"> + +Si us heu oblidat de seleccionar i formatar una partició d'arrencada +EFI, el <command>partman</command> ho detectarà us deixarà continuar +fins que no n'assigneu una. + +</para><para> + +Les possibilitats del <command>partman</command> es poden ampliar a través +dels mòduls de l'instal·lador, però dependran de l'arquitectura del sistema. +Si no teniu accés a totes les possibilitats que esperàveu comproveu que heu +carregat tots els mòduls necessaris +(ex. <filename>partman-ext3</filename>, <filename>partman-xfs</filename>, +o <filename>partman-lvm</filename>). + +</para><para> + +Un cop la partició satisfaci les vostres necessitats, seleccioneu +l'opció de partició <guimenuitem>Finalitza la partició i escriu +els canvis al disc</guimenuitem>. Se us presentarà un resum dels canvis +realitzats als disc i se us demanarà que confirmeu la creació +dels sistemes de fitxers tal i com els heu sol·licitat. + +</para> + </sect3> diff --git a/ca/using-d-i/modules/powerpc/quik-installer.xml b/ca/using-d-i/modules/powerpc/quik-installer.xml new file mode 100644 index 000000000..ed6aa6a60 --- /dev/null +++ b/ca/using-d-i/modules/powerpc/quik-installer.xml @@ -0,0 +1,15 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 14975 untranslated --> + + <sect3 arch="powerpc"> + <title>Install <command>Quik</command> on a Hard Disk</title> +<para> + +The boot loader for OldWorld Power Macintosh machines is +<command>quik</command>. You can also use it on CHRP. The installer +will attempt to set up <command>quik</command> automatically. The +setup has been known to work on 7200, 7300, and 7600 Powermacs, and on +some Power Computing clones. + +</para> + </sect3> diff --git a/ca/using-d-i/modules/powerpc/yaboot-installer.xml b/ca/using-d-i/modules/powerpc/yaboot-installer.xml new file mode 100644 index 000000000..4bba348fb --- /dev/null +++ b/ca/using-d-i/modules/powerpc/yaboot-installer.xml @@ -0,0 +1,17 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 14975 untranslated --> + + <sect3 arch="powerpc"> + <title>Install <command>Yaboot</command> on a Hard Disk</title> +<para> + +Newer (mid 1998 and on) PowerMacs use <command>yaboot</command> as +their boot loader. The installer will set up <command>yaboot</command> +automatically, so all you need is a small 820k partition named +<quote>bootstrap</quote> with type +<emphasis>Apple_Bootstrap</emphasis> created back in the partitioning +component. If this step completes successfully then your disk should +now be bootable and OpenFirmware will be set to boot &debian;. + +</para> + </sect3> diff --git a/ca/using-d-i/modules/prebaseconfig.xml b/ca/using-d-i/modules/prebaseconfig.xml new file mode 100644 index 000000000..720421bff --- /dev/null +++ b/ca/using-d-i/modules/prebaseconfig.xml @@ -0,0 +1,23 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 21672 --> + + <sect3 id="prebaseconfig"> + <title>Finalització de la instal·lació i arrancada automàtica</title> + +<para> + +Aquest és el darrer pas del procés inicial de la instal·lació de Debian. +Se us indicarà que extragueu el mitjà d'instal·lació (CD, disquet, etc.) que +heu fet servir per arrancar l'instal·lador. Aquest farà algunes tasques finals +i després arrancarà el nou sistema Debian. + +</para><para arch="s390"> + +En l'arquitectura &arch-title; no es pot fer una arrancada automàtica. Per +tant, seleccioneu l'opció <guimenuitem>Finalitza la instal·lació</guimenuitem>, +la qual atura el sistema. Després, arranqueu vosaltres el GNU/Linux amb l'IPL +des del DASD que vàreu seleccionar per al sistema d'arxius arrel (root +filesystem) durant els primers passos de la instal·lació. + +</para> + </sect3> diff --git a/ca/using-d-i/modules/s390/dasd.xml b/ca/using-d-i/modules/s390/dasd.xml new file mode 100644 index 000000000..9442b9d2f --- /dev/null +++ b/ca/using-d-i/modules/s390/dasd.xml @@ -0,0 +1,2 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 11648 --> diff --git a/ca/using-d-i/modules/s390/netdevice.xml b/ca/using-d-i/modules/s390/netdevice.xml new file mode 100644 index 000000000..9442b9d2f --- /dev/null +++ b/ca/using-d-i/modules/s390/netdevice.xml @@ -0,0 +1,2 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 11648 --> diff --git a/ca/using-d-i/modules/s390/zipl-installer.xml b/ca/using-d-i/modules/s390/zipl-installer.xml new file mode 100644 index 000000000..61aa6465c --- /dev/null +++ b/ca/using-d-i/modules/s390/zipl-installer.xml @@ -0,0 +1,16 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 14602 untranslated --> + + <sect3 arch="s390"> + <title><command>zipl</command>-installer</title> +<para> + +The boot loader on &arch-title; is <quote>zipl</quote>. +<command>ZIPL</command> is similar in configuration and usage to +<command>LILO</command>, with a few exceptions. Please take a look at +<quote>LINUX for &arch-title; Device Drivers and Installation +Commands</quote> from IBM's developerWorks web site if you want to +know more about <command>ZIPL</command>. + +</para> + </sect3> diff --git a/ca/using-d-i/modules/save-logs.xml b/ca/using-d-i/modules/save-logs.xml new file mode 100644 index 000000000..2f0576518 --- /dev/null +++ b/ca/using-d-i/modules/save-logs.xml @@ -0,0 +1,24 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 --> + + <sect3 id="save-logs"> + <title>Desament dels registres de la instal·lació</title> + +<para> + +Si la instal·lació resulta reeixida, els fitxers de registre +creats durant el procés d'instal·lació es desaran automàticament +a <filename>/var/log/debian-installer/</filename> en el nou +sistema Debian. + +</para><para> + +Si elegiu <guimenuitem>Desa els registres de depuració</guimenuitem> +des del menú principal, podreu desar els fitxers de registre a un +disquet<phrase condition="etch">, xarxa, disc dur o altre +medi</phrase>. Això pot ser útil si trobeu problemes fatals durant la +instal·lació i desitgeu estudiar els registres en un altre sistema, +o adjuntar-los a un informe d'instal·lació. + +</para> + </sect3> diff --git a/ca/using-d-i/modules/shell.xml b/ca/using-d-i/modules/shell.xml new file mode 100644 index 000000000..0a649a227 --- /dev/null +++ b/ca/using-d-i/modules/shell.xml @@ -0,0 +1,41 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 21579 --> + + <sect3 id="shell"> + <title>Utilització de l'intèrpret d'ordres i visualització dels arxius de registre</title> + <!-- TODO: There is nothing about logs in this section! --> + +<para> + +En el menú teniu l'opció <guimenuitem>Executa un intèrpret +d'ordres</guimenuitem>. Si el menú no és a l'abast i us cal l'intèrpret +d'ordres, premeu <keycombo><keycap>Alt(esquerre)</keycap> <keycap>F2</keycap></keycombo> +(en un teclat Mac, <keycombo><keycap>Option</keycap> <keycap>F2</keycap> +</keycombo>) per accedir al segon <emphasis>intèrpret d'ordres +virtual</emphasis>; és a dir, la tecla <keycap>Alt</keycap> a l'esquerre +de la <keycap>barra espaiadora</keycap> i la tecla de funció +<keycap>F2</keycap>, alhora. Anireu a una altra finestra que executa +l'<command>ash</command>, un clon del Bash (l'intèrpret d'ordres Bourne). + +</para><para> + +En aquest moment heu arrancat des del disc RAM, per tant el conjunt d'utilitats +Linux que teniu disponibles és limitat. Podeu veure els programes a l'abast amb +l'ordre <command>ls /bin /sbin /usr/bin /usr/sbin</command> o bé teclejant +<command>help</command>. L'editor de text és el <command>nano</command>. +L'intèrpret d'ordres disposa d'algunes característiques pràctiques, com +l'autocompleció i l'historial. + +</para><para> + +Feu servir els menús per dur a terme qualsevol tasca que pugueu fer amb ells +— l'intèrpret i les ordres sols hi són en cas que alguna cosa vaja +malament. En particular, sempre hauríeu de fer servir els menús, i mai no +l'intèrpret, per activar la partició d'intercanvi (swap), ja que si ho heu fet +des de l'intèrpret, el programari del menú no ho detectarà pas. Premeu +<keycombo><keycap>Alt(esquerre)</keycap> <keycap>F1</keycap></keycombo> per +tornar als menús, o bé teclegeu <command>exit</command> si heu emprat l'opció +del menú per obrir l'intèrpret d'ordres. + +</para> + </sect3> diff --git a/ca/using-d-i/modules/sparc/silo-installer.xml b/ca/using-d-i/modules/sparc/silo-installer.xml new file mode 100644 index 000000000..3ce2b6ac6 --- /dev/null +++ b/ca/using-d-i/modules/sparc/silo-installer.xml @@ -0,0 +1,25 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 24582 untranslated --> + + <sect3 arch="sparc"> + <title>Install the <command>SILO</command> Boot Loader + on a Hard Disk</title> +<para> + +The standard &architecture; boot loader is called <quote>silo</quote>. +It is documented in +<filename>/usr/share/doc/silo/</filename>. <command>SILO</command> is +similar in configuration and usage to <command>LILO</command>, with +a few exceptions. First of all, <command>SILO</command> allows you to +boot any kernel image on your drive, even if it is not listed in +<filename>/etc/silo.conf</filename>. This is because +<command>SILO</command> can actually read Linux partitions. Also, +<filename>/etc/silo.conf</filename> is read at boot time, so there is +no need to rerun <command>silo</command> after installing a new kernel +like you would with <command>LILO</command>. <command>SILO</command> +can also read UFS partitions, which means it can boot SunOS/Solaris +partitions as well. This is useful if you want to install GNU/Linux +alongside an existing SunOS/Solaris install. + +</para> + </sect3> diff --git a/ca/using-d-i/using-d-i.xml b/ca/using-d-i/using-d-i.xml new file mode 100644 index 000000000..7d932ed6d --- /dev/null +++ b/ca/using-d-i/using-d-i.xml @@ -0,0 +1,383 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 --> + + + <chapter id="d-i-intro"><title>Utilització de l'instal·lador de Debian</title> + + <sect1><title>Com funciona l'instal·lador</title> +<para> + +L'instal·lador de Debian és un conjunt d'elements amb objectius +específics que realitzen cada una de les tasques de la instal·lació. +Cada element executa la seva tasca, preguntant a l'usuari les qüestions +necessàries per realitzar-la. Les preguntes tenen assignades prioritats, +i la prioritat de les preguntes que s'han de fer s'estableix quan s'inicia +l'instal·lador. + +</para><para> + +Quan s'executa una instal·lació per defecte només es fan les preguntes +essencials (d'alta prioritat). En aquest cas és un procés +d'instal·lació altament automatitzat amb poca interacció de l'usuari. +Els elements s'executen automàticament en una seqüència, la selecció dels +elements que s'executen depèn principalment del mètode d'instal·lació +que utilitzeu i del vostre maquinari. L'instal·lador utilitzarà valors +predeterminats per a les preguntes que no es facin. + +</para><para> + +Si hi hagués un problema, l'usuari veuria una pantalla d'error i potser es +mostraria el menú d'instal·lació perquè seleccionés alguna acció +alternativa. Si no hi ha problemes, l'usuari mai veurà el menú +d'instal·lació, sinó que simplement haurà de contestar les preguntes +de cada element. Les notificacions d'errors greus tenen una prioritat +«crítica» de manera que sempre es notifiqui a l'usuari. + +</para><para> + +Alguns dels valors predeterminats que utilitza l'instal·lador es poden canviar +passant-li arguments d'arrencada quan s'inicia el &d-i;. Per exemple, +si voleu forçar una configuració de xarxa estàtica (el DHCP s'utilitza +de forma predeterminada si està disponible), podeu afegir el paràmetre +d'arrencada <userinput>netcfg/disable_dhcp=true</userinput>. +Podeu veure les opcions disponibles a <xref linkend="installer-args"/>. + +</para><para> + +Els usuaris avançats es poden sentir més còmodes amb una interfície +conduïda a través de menús, on l'usuari controla cada pas en comptes de +deixar que l'instal·lador els realitzi automàticament en una seqüència. +Per utilitzar l'instal·lador de forma manual, a través de menús, afegiu +l'argument d'arrencada <userinput>debconf/priority=medium</userinput>. + +</para><para> + +Si el vostre maquinari necessita que passeu opcions als mòduls del nucli +a mida que es van instal·lant, necessitareu iniciar l'instal·lador en mode +<quote>expert</quote>. Aquesta opció es pot activar utilitzant l'ordre +<command>expert</command> per arrencar l'instal·lador o bé afegint +l'argument d'arrencada <userinput>debconf/priority=low</userinput>. El mode +expert us proporciona control total sobre el &d-i; + +</para><para> + +La visualització normal de l'instal·lador es basa en caràcters +(contràriament a les interfícies gràfiques, actualment més familiars). +El ratolí no és operacional en aquest entorn. Aquí teniu les tecles +que podeu utilitzar per navegar pels diversos diàlegs. El +<keycap>Tab</keycap> o la tecla de cursor a la <keycap>dreta</keycap> +mouen «endavant», i les <keycombo> <keycap>Maj</keycap> +<keycap>Tab</keycap> </keycombo> o el cursor a +l'<keycap>esquerra</keycap> mouen «endarrere» entre els botons +i seleccions que es mostren. Les tecles de cursor <keycap>amunt</keycap> +i <keycap>avall</keycap> seleccionen diferents elements en una llista +desplaçable, i també desplacen la mateixa llista. A més, en llistes +llargues, podeu teclejar una lletra per fer que la llista es desplaci +directament a la secció que tingui elements que comencin amb aquesta lletra +i utilitzar <keycap>Re Pàg</keycap> i <keycap>Av Pàg</keycap> per +desplaçar la llista per seccions. La <keycap>barra espaiadora</keycap> +selecciona un objecte com un quadre de verificació. Utilitzeu la tecla +&enterkey; per activar les eleccions. + +</para><para arch="s390"> + +L'S/390 no suporta consoles virtuals. Podeu obrir una segona i tercera sessions +ssh per veure els registres que es descriuen a sota. + +</para><para> + +Els missatges d'error es redirigeixen a la tercera consola. Podeu accedir a +aquesta consola prement +<keycombo><keycap>Alt esquerra</keycap><keycap>F3</keycap></keycombo> +(manteniu premuda l'<keycap>Alt</keycap> esquerra mentre premeu la tecla de +funció <keycap>F3</keycap>); torneu al procés principal de l'instal·lador +amb <keycombo><keycap>Alt esquerra</keycap><keycap>F1</keycap></keycombo>. + +</para><para> + +També podeu trobar aquests missatges a <filename>/var/log/messages</filename>. +Després de la instal·lació, aquest registre es copia a +<filename>/var/log/debian-installer/messages</filename> del nou +sistema. Altres missatges de la instal·lació es poden trobar a +<filename>/var/log/</filename> durant la instal·lació i a +<filename>/var/log/debian-installer/</filename> després que l'ordinador +s'hagi iniciat amb el sistema instal·lat. + +</para> + </sect1> + + + <sect1 id="modules-list"><title>Introducció als elements</title> +<para> + +Aquí hi ha una llista dels elements de l'instal·lador amb una breu +descripció de la tasca de cada element. Els detalls que podeu necessitar +per saber com utilitzar un element en particular els podeu trobar a +<xref linkend="module-details"/>. + +</para> + +<variablelist> +<varlistentry> + +<term>main-menu</term><listitem><para> + +Mostra la llista d'elements durant l'operació de l'instal·lador +i inicia un element quan se selecciona. Les preguntes del menú principal +tenen assignada una prioritat mitjana, si la vostra prioritat +està definida a alta o crítica (alta és el valor per predeterminat), no veureu +el menú. D'altra banda, si hi hagués un error que requerís la vostra +intervenció, la prioritat de les qüestions es pot baixar temporalment per +permetre resoldre el problema i, en aquest cas, pot aparèixer el menú. + +</para><para> + +Podeu arribar al menú principal seleccionant el botó "Endarrere" repetidament, +per retrocedir tot el camí fet per l'element en execució. + +</para></listitem> +</varlistentry> +<varlistentry condition="sarge"> + +<term>languagechooser</term><listitem><para> + +Mostra una llista d'idiomes i variants d'idiomes. L'instal·lador mostrarà +els missatges en l'idioma triat si no és que la traducció per aquell idioma +és incompleta. Quan una traducció no és completa es mostraran missatges +en anglès. + +</para></listitem> +</varlistentry> +<varlistentry condition="sarge"> + +<term>countrychooser</term><listitem><para> + +Mostra una llista de països. L'usuari pot triar el país on viu. + +</para></listitem> +</varlistentry> +<varlistentry condition="etch"> + +<term>localechooser</term><listitem><para> + +Permet a l'usuari seleccionar les opcions de localització per a +l'instal·lació i el sistema instal·lat: idioma, país i locals. +L'instal·lador mostrarà els missatges en l'idioma seleccionat, +en el cas que la traducció per aquest idioma no sigui completa +alguns missatges pot ser que es mostrin en angles. + +</para></listitem> +</varlistentry> +<varlistentry> + +<term>kbd-chooser</term><listitem><para> + +Mostra una llista de teclats dels quals l'usuari tria el model que es +correspon amb el seu. + +</para></listitem> +</varlistentry> +<varlistentry> + +<term>hw-detect</term><listitem><para> + +Detecta automàticament la major part de maquinari del sistema, incloent +targes de xarxa, unitats de disc i PCMCIA. + +</para></listitem> +</varlistentry> +<varlistentry> + +<term>cdrom-detect</term><listitem><para> + +Cerca i munta un CD d'instal·lació de Debian. + +</para></listitem> +</varlistentry> +<varlistentry> + +<term>netcfg</term><listitem><para> + +Configura les connexions de xarxa de l'ordinador perquè que es pugui +comunicar a través de la Internet. + +</para></listitem> +</varlistentry> +<varlistentry> + +<term>iso-scan</term><listitem><para> + +Cerca sistema de fitxers ISO, que poden ésser a un CD-ROM o al disc dur. + +</para></listitem> +</varlistentry> +<varlistentry> + +<term>choose-mirror</term><listitem><para> + +Presenta una llista de rèpliques de l'arxiu de Debian. L'usuari pot triar la +font dels seus paquets d'instal·lació. + +</para></listitem> +</varlistentry> +<varlistentry> + +<term>cdrom-checker</term><listitem><para> + +Comprova la integritat d'un CD-ROM. D'aquesta manera, l'usuari pot estar segur +que el CD-ROM d'instal·lació no està corromput. + +</para></listitem> +</varlistentry> +<varlistentry> + +<term>lowmem</term><listitem><para> + +El «lowmem» intenta detectar sistema amb poca memòria, en aquest cas +realitza diversos trucs per treure parts innecessàries del &d-i; de la +memòria (a canvi de perdre algunes funcions). + +</para></listitem> +</varlistentry> +<varlistentry> + +<term>anna</term><listitem><para> + +Anna's Not Nearly APT (l'Anna casi no és l'APT). Instal·la paquets que s'han +obtingut de la rèplica o CD triat. + +</para></listitem> +</varlistentry> +<varlistentry> + +<term>partman</term><listitem><para> + +Permet a l'usuari fer particions als discs adjunts al sistema, crear sistemes +de fitxers a les particions seleccionades, i adjuntar-los als punts de +muntatge. També s'inclouen funcions interessants com un mode completament +automàtic i suport per LVM. Aquesta és l'eina de gestió de particions +preferida a Debian. + +</para></listitem> +</varlistentry> +<varlistentry> + +<term>autopartkit</term><listitem><para> + +Fa particions a un disc complet automàticament d'acord amb les preferències +preestablertes de l'usuari. + +</para></listitem> +</varlistentry> +<varlistentry> + +<term>partitioner</term><listitem><para> + +Permet a l'usuari fer particions als discs adjunts al sistema. S'elegeix un +programa de particions apropiat per a l'arquitectura del vostre ordinador. + +</para></listitem> +</varlistentry> +<varlistentry> + +<term>partconf</term><listitem><para> + +Visualitza una llista de particions i crea sistemes de fitxers a les +particions seleccionades segons les instruccions de l'usuari. + +</para></listitem> +</varlistentry> +<varlistentry> + +<term>lvmcfg</term><listitem><para> + +Ajuda a l'usuari a configurar el <firstterm>LVM</firstterm> +(Logical Volume Manager, gestor de volums lògics). + +</para></listitem> +</varlistentry> +<varlistentry> + +<term>mdcfg</term><listitem><para> + +Permet a l'usuari configurar el programari <firstterm>RAID</firstterm> +(Redundant Array of Inexpensive Disks, matriu redundant de discs barats). +Aquest programari RAID normalment és superior als barats controladors RAID +IDE (pseudomaquinari) que es troben a les plaques bases més noves. + +</para></listitem> +</varlistentry> +<varlistentry> + +<term>base-installer</term><listitem><para> + +Instal·la el conjunt de paquets més bàsic que permeten a l'ordinador +funcionar sota Linux quan es torna a arrencar. + +</para></listitem> +</varlistentry> +<varlistentry> + +<term>os-prober</term><listitem><para> + +Detecta els sistemes operatius instal·lats actualment a l'ordinador i passa +aquesta informació al bootloader-installer (instal·lador del carregador de +l'arrencada), que pot oferir la capacitat d'afegir els sistemes operatius +descoberts al menú d'inici del carregador de l'arrencada. D'aquesta manera, +l'usuari pot triar fàcilment, durant l'arrencada, quin sistema operatiu +iniciar. + +</para></listitem> +</varlistentry> +<varlistentry> + +<term>bootloader-installer</term><listitem><para> + +Instal·la un programa carregador de l'arrencada al disc dur, que és +necessari perquè l'ordinador pugui arrencar el Linux sense utilitzar un +disquet o CD-ROM. Molts carregadors de l'arrencada permeten a l'usuari triar +un sistema operatiu alternatiu cada vegada que s'arrenca l'ordinador. + +</para></listitem> +</varlistentry> +<varlistentry> + +<term>base-config</term><listitem><para> + +Proporciona diàlegs per configurar els paquets bàsics del sistema segons +les preferències de l'usuari. Aquesta possibilitat es realitza, normalment, +després de tornar a arrencar l'ordinador, és la «primera execució» del +nou sistema Debian. + +</para></listitem> +</varlistentry> +<varlistentry> + +<term>shell</term><listitem><para> + +Permet a l'usuari executar un intèrpret d'ordres des del menú o en una +segona consola. + +</para></listitem> +</varlistentry> +<varlistentry> + +<term condition="sarge">bugreporter</term><term condition="etch">save-logs</term><listitem><para> + +Proporciona un mètode perquè l'usuari pugui registrar informació en +disquet<phrase condition="etch">, xarxa, disc dur or altres medis</phrase> +quan es troba algun problema. Posteriorment i de forma +acurada, pot informar als desenvolupadors de Debian dels problemes +amb el programari d'instal·lació. + +</para></listitem> +</varlistentry> + +</variablelist> + + </sect1> + +&using-d-i-components.xml; + +</chapter> + diff --git a/ca/welcome/about-copyright.xml b/ca/welcome/about-copyright.xml new file mode 100644 index 000000000..d4d2f0ea4 --- /dev/null +++ b/ca/welcome/about-copyright.xml @@ -0,0 +1,95 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 29000 --> + + <sect1> +<title>Sobre el copyright i les llicències del programari + </title> + +<para> + +Segur que ja heu llegit alguna cosa sobre les llicències que venen amb +la majoria del programari comercial — normalment diuen que només +podeu utilitzar una còpia del programari en un únic ordinador. La +llicència del sistema Debian GNU/Linux no és del tot així. Us animem +a posar una còpia de Debian GNU/Linux en cada ordinador de la vostra +escola o lloc de treball. Deixeu el vostre mitjà d'instal·lació als +vostres amics i ajudeu-los amb la instal·lació als seus ordinadors! +Podeu fer centenars de còpies i <emphasis>vendre-les</emphasis> — +encara que amb algunes restriccions. La vostra llibertat per instal·lar +i utilitzar el sistema us la dóna directament Debian al basar-se en +<emphasis>programari lliure</emphasis>. + +</para><para> + +Anomenar-se programari <emphasis>lliure</emphasis> no significa que el +programari no tingui copyright i no vol dir que els CD que contenen aquest +programari hagin de ser distribuïts gratuïtament. Programari lliure, +en part, significa que les llicències dels programes individuals no +obliguen a pagar pel privilegi de distribuir o utilitzar-los. +El programari lliure també comporta que no només qualsevol el pot +ampliar, adaptar i modificar, sinó que també en pot distribuir el +resultant dels canvis. + +<note><para> + +El projecte Debian, com a concessió pragmàtica cap els +seus usuaris, permet que alguns paquets disponibles no compleixin +els nostres criteris per a ser considerats lliures. Aquests paquets +no formen part de la distribució oficial, tot i això, estan +disponibles a les àrees <userinput>contrib</userinput> o +<userinput>non-free</userinput> de les rèpliques de Debian o en la tercera +part dels CD-ROM; per a més informació sobre la disposició i el contingut +dels arxius, mireu les <ulink url="&url-debian-faq;">Debian PMF</ulink> als +<quote>Arxius d'FTP de Debian</quote>. + +</para></note> + +</para><para> + +Molts dels programes del sistema estan sota la llicència de +<emphasis>GNU</emphasis> <emphasis>Llicència Pública General</emphasis>, +sovint anomenada simplement <quote>la GPL</quote>. La GPL necessita que +deixeu el <emphasis>codi font</emphasis> dels programes sempre disponible +quan distribuïu una còpia binària del programa; amb aquesta condició +de la llicència s'assegura que qualsevol usuari pugui modificar el +programari. Arran d'aquesta condició, el codi font<footnote> +<para> + +Per més informació de com trobar, desempaquetar i construir binaris +des dels paquets font de Debian, mireu les +<ulink url="&url-debian-faq;">Debian PMF</ulink>, a <quote>Informació +bàsica sobre el sistema Debian de gestió de paquets</quote>. + +</para> +</footnote> de tots aquests programes estarà disponible al sistema Debian. + +</para><para> + +Hi ha algunes formes més de declaracions de copyright i de llicències +de programari utilitzades en els programes de Debian. Podeu trobar +els copyrights i les llicències per a cada paquet instal·lat en el +vostre sistema mirant el fitxer +<filename>/usr/share/doc/<replaceable>nom-paquet</replaceable>/copyright</filename> un +cop estigui instal·lat. + +</para><para> + +Per més informació sobre les llicències i com es decideix si +un programari compleix les característiques per ser inclòs en una +distribució oficial de Debian, mireu +<ulink url="&url-dfsg;">els Principis del programari lliure de Debian</ulink>. + +</para><para> + +El punt legal més important és que aquest programari <emphasis>no té +garanties</emphasis>. Els programadors que han creat aquest programari, +ho fan per beneficiar a la comunitat. No és tenen garanties envers +d'un ús concret del programari. Tot i això, com que el programari és +lliure, teniu la possibilitat de modificar-lo +per adaptar-lo a les vostres necessitats — i disfrutar dels +beneficis dels canvis fets per d'altres que han ampliat el programari +a la seva manera. + +</para> + </sect1> + diff --git a/ca/welcome/doc-organization.xml b/ca/welcome/doc-organization.xml new file mode 100644 index 000000000..7972a0b73 --- /dev/null +++ b/ca/welcome/doc-organization.xml @@ -0,0 +1,124 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 --> + + <sect1 id="doc-organization"> + <title>Organització d'aquest document</title> + +<para> + +Aquest document està pensat per servir de manual per aquells que +utilitzin Debian per primer cop. Intenta fer el mínim de suposicions +possibles pel que fa al nivell dels coneixements. Tot i això, +se suposen uns certs coneixements generals sobre com +funciona el maquinari de l'ordinador. + +</para><para> + +Els usuaris experts també hi poden trobar informació de referència +interessant, incloent-hi l'espai mínim per a la instal·lació, detalls +sobre el maquinari suportat pel sistema d'instal·lació de Debian i +d'altres coses. Encoratgem als usuaris experts a saltar d'una secció a +l'altra d'aquest document. + +</para><para> + +En general, aquest manual s'ha organitzat de forma lineal, portant-vos a +través del procés d'instal·lació des del principi fins al final. A +continuació teniu els passos per a instal·lar &debian;, i les seccions +d'aquest document que s'hi corresponen: + +<orderedlist> +<listitem><para> + +Determineu si el vostre maquinari reuneix els requisits per utilitzar el +sistema d'instal·lació a <xref linkend="hardware-req"/>. + +</para></listitem> +<listitem><para> + +Feu una còpia de seguretat del vostre sistema, dueu a terme qualsevol +planificació i configuració del maquinari previs a la instal·lació +de Debian a <xref linkend="preparing"/>. Si esteu preparant un sistema +d'arrencada múltiple, potser necessitareu crear espai al disc dur per +fer-hi les particions que utilitzarà Debian. + +</para></listitem> +<listitem><para> + +A <xref linkend="install-methods"/>, obtindreu els fitxers d'instal·lació +necessaris per al vostre mètode d'instal·lació. + +</para></listitem> +<listitem><para> + +<xref linkend="boot-installer"/> descriu l'arrencada del sistema +d'instal·lació. Aquest capítol també discuteix els procediments +de resolució de problemes en cas que tingueu problemes en aquest pas. + +</para></listitem> +<listitem><para> + +Realitzeu la instal·lació pròpiament dita segons +<xref linkend="d-i-intro"/>. Implica la tria de l'idioma, +la configuració del mòduls controladors de dispositius, la configuració +de la connexió de xarxa, de manera que la resta de fitxers de la +instal·lació es puguin obtenir directament d'un servidor de Debian (si no +esteu instal·lant a partir d'un CD), el mètode de partició de les vostres +unitats de disc i la instal·lació del sistema funcional mínim. +(A <xref linkend="partitioning"/> trobareu alguna informació sobre com +configurar les particions pel vostre sistema Debian). + +</para></listitem> +<listitem><para> + +Arrenqueu el sistema base instal·lat i feu una ullada a les tasques +de configuració addicionals a <xref linkend="boot-new"/>. + +</para></listitem> +<listitem><para> + +Instal·leu programari addicional amb <xref linkend="install-packages"/>. + +</para></listitem> +</orderedlist> + +</para><para> + +Un cop tingueu el vostre sistema instal·lat, podeu llegir +<xref linkend="post-install"/>. Aquest capítol explica on podeu cercar +més informació sobre Unix i Debian i com reemplaçar el vostre nucli. + +<!-- XXX FIXME: Si voleu construir el vostre propi sistema d'instal·lació +a partir dels fonts, assegureu-vos d'haver llegit +<xref linkend="boot-floppy-techinfo"/>. --> + +</para><para> + +Finalment, podeu trobar informació sobre aquest document i com +contribuir-hi a <xref linkend="administrivia"/>. + +</para> + + </sect1> + + <sect1 condition="FIXME"> + <title>La vostra documentació d'ajuda és benvinguda</title> + +<para> + +S'apreciarà enormement qualsevol ajuda, suggeriment i, especialment, +pedaços. Es poden trobar versions funcionals d'aquest document a +<ulink url="&url-d-i-alioth-manual;" />. Aquí trobareu una llista +de totes les arquitectures i idiomes pels quals està disponible +el document. + +</para><para> + +Les fonts també estan disponibles públicament. Per trobar informació +referent a la contribució feu un cop d'ull a +<xref linkend="administrivia"/>. Agraïm els suggeriments, comentaris, +pedaços i informes d'error (pel errors utilitzeu el paquet &d-i-manual;, +comproveu primer que el problema no s'hagi notificat prèviament). + +</para> + </sect1> diff --git a/ca/welcome/getting-newest-doc.xml b/ca/welcome/getting-newest-doc.xml new file mode 100644 index 000000000..42fd0145b --- /dev/null +++ b/ca/welcome/getting-newest-doc.xml @@ -0,0 +1,19 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 --> + + <sect1 id="getting-newest-doc"> + <title>Obtenció de l'última versió d'aquest document</title> + +<para> + +Aquest document es revisa constantment. Per trobar la informació +d'última hora sobre el llançament &release; del sistema Debian +assegureu-vos de comprovar les <ulink url="&url-release-area;">pàgines +de Debian &release;</ulink>. Les versions actualitzades d'aquest +manual d'instal·lació estan disponibles a les +<ulink url="&url-install-manual;">pàgines del manual +d'instal·lació oficial</ulink>. + +</para> + + </sect1> diff --git a/ca/welcome/getting-newest-inst.xml b/ca/welcome/getting-newest-inst.xml new file mode 100644 index 000000000..9e02e4437 --- /dev/null +++ b/ca/welcome/getting-newest-inst.xml @@ -0,0 +1,25 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 --> + + <sect1 id="getting-newest-inst"> + <title>Obtenció de Debian</title> + +<para> + +Per obtenir informació sobre com baixar &debian; de la Internet o a qui es +poden comprar els CD oficials de Debian vegeu la +<ulink url="&url-debian-distrib;">pàgina web de distribució</ulink>. La +<ulink url="&url-debian-mirrors;">llista de rèpliques de Debian</ulink> +conté un conjunt complet de rèpliques oficials de Debian perquè +pugueu trobar-hi fàcilment la més propera. + +</para><para> + +Debian es pot actualitzar fàcilment Debian després de la instal·lació. +El procés d'instal·lació us ajudarà a configurar el sistema de manera +que pugueu fer aquestes actualitzacions, si són necessàries, un cop +finalitzada la instal·lació. + +</para> + + </sect1> diff --git a/ca/welcome/welcome.xml b/ca/welcome/welcome.xml new file mode 100644 index 000000000..ee6fdf2d6 --- /dev/null +++ b/ca/welcome/welcome.xml @@ -0,0 +1,23 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 --> + +<chapter id="welcome"><title>Benvingut a Debian</title> +<para> + +Aquest capítol proporciona una vista prèvia del projecte Debian i +&debian;. Si ja coneixeu la història del projecte Debian i de +la distribució &debian;, podeu passar tranquil·lament al +següent capítol. + +</para> + +&what-is-debian.xml; +&what-is-linux.xml; +&what-is-debian-linux.xml; +&what-is-debian-hurd.xml; +&getting-newest-inst.xml; +&getting-newest-doc.xml; +&doc-organization.xml; +&about-copyright.xml; + +</chapter> diff --git a/ca/welcome/what-is-debian-hurd.xml b/ca/welcome/what-is-debian-hurd.xml new file mode 100644 index 000000000..5f60998ad --- /dev/null +++ b/ca/welcome/what-is-debian-hurd.xml @@ -0,0 +1,28 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 --> + +<!-- conditionalised because the hurd port is not yet an official debian +release --> + <sect1 id="what-is-debian-hurd" condition="unofficial-build"> + <title>Què és Debian GNU/Hurd?</title> + +<para> + +Debian GNU/Hurd és un sistema Debian GNU que reemplaça el nucli +monolític del Linux pel GNU Hurd — un conjunt de servidors que +s'executen sobre del micronucli GNU Mach. El Hurd encara no és acabat +i no és adequat per l'ús diari, però continua en desenvolupament. +Actualment, el Hurd només s'està desenvolupant per l'arquitectura +i386, tot i que quan el sistema sigui més estable, es faran +adaptacions a d'altres arquitectures. + +</para><para> + +Per obtenir més informació vegeu la +<ulink url="http://www.debian.org/ports/hurd/">pàgina d'adaptacions +de Debian GNU/Hurd</ulink> i la llista de correu +<email>debian-hurd@lists.debian.org</email>. + +</para> + + </sect1> diff --git a/ca/welcome/what-is-debian-linux.xml b/ca/welcome/what-is-debian-linux.xml new file mode 100644 index 000000000..d3918c6ae --- /dev/null +++ b/ca/welcome/what-is-debian-linux.xml @@ -0,0 +1,91 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 25496 --> + + <sect1 id="what-is-debian-linux"> + <title>Què és &debian;?</title> +<para> + +De la combinació de la filosofia i metodologia Debian amb les +utilitats de GNU, el nucli Linux i altre programari lliure, n'esdevé +una distribució única anomenada Debian &debian;. Aquesta distribució +es basa en una quantitat enorme de <emphasis>paquets</emphasis> de +programari. Cada paquet de la distribució té executables, seqüències, +documentació, i informació de la configuració, així com un +<emphasis>mantenidor</emphasis>, que és el principal responsable de +mantenir-lo actualitzat, analitzar i reparar-ne els errors de +programació i de comunicar-se amb els desenvolupadors del paquet de +programari. L'enorme quantitat d'usuaris combinada amb el sistema de +seguiment d'errors permet que aquests es localitzin i depurin +ràpidament. + +</para><para> + +La importància que Debian dóna als detalls ens permet produir una +distribució estable, ampliable i d'alta qualitat. Les instal·lacions +poden ser fàcilment configurades per dur a terme diferents papers, des +de muntar tallafocs pels centres de treball científics a servidors de +xarxa d'alta qualitat. + +</para><para> + +Debian és especialment popular entre els usuaris avançats arran +de les seves excel·lències tècniques i el compromís amb les +necessitats i expectatives de la comunitat Linux. Debian també ha +introduït moltes característiques al Linux que actualment són +quotidianes. + +</para><para> + +Per exemple, Debian va ser la primera distribució de Linux que +va incloure un sistema de gestió de paquets per facilitar +la instal·lació i supressió de programari. També va ser la primera +distribució de Linux que es podia actualitzar sense necessitar +la reinstal·lació completa. + +</para><para> + +Debian continua sent un projecte líder en el desenvolupament de +Linux. El seu procés de desenvolupament és un exemple de com pot +arribar a funcionar un model de desenvolupament de programari lliure +— fins i tot per tasques complexes com generar i mantenir un +sistema operatiu complet. + +</para><para> + +La característica que més diferencia Debian de les altres +distribucions GNU/Linux és el seu sistema de manteniment de paquets. +Aquestes utilitats donen a l'administrador d'un sistema Debian el +control total sobre els paquets instal·lats en el sistema, +incloent-hi la possibilitat d'instal·lar un únic paquet o +d'actualitzar totalment el sistema operatiu. Els paquets individuals +també es poden actualitzar. En el sistema de manteniment de paquets +podeu establir quin programari us heu compilat vosaltres mateixos i +les dependències que té. + +</para><para> + +Per protegir el sistema contra <quote>cavalls de Troia</quote> i +d'altre programari perjudicial, els servidors de Debian verifiquen +que els paquets apujats procedeixin dels mantenidors de Debian +registrats. Els empaquetadors de Debian també tenen cura de +configurar els paquets de forma segura. Quan apareixen problemes de +seguretat als paquets en circulació, les actualitzacions normalment +estan disponibles en poc temps. Amb unes simples opcions d'actualització +de Debian les actualitzacions de seguretat es poden descarregar i +instal·lar automàticament a través d'Internet. + +</para><para> + +La millor forma d'obtenir ajuda per utilitzar el sistema Debian +GNU/Linux i poder-vos comunicar amb els desenvolupadors de Debian és +a través d'algunes llistes de correu mantingudes pel projecte Debian +(en el moment que s'escrivia aquest document n'hi havia més de +&num-of-debian-maillists;). La manera més fàcil per subscriure's +a una o més llistes és visitant la pàgina de subscripcions a la +llista de correu de Debian <ulink url="&url-debian-lists-subscribe;"> +http://www.debian.org/MailingLists/subscribe</ulink> i emplenar el +formulari que hi trobareu. + +</para> + + </sect1> diff --git a/ca/welcome/what-is-debian.xml b/ca/welcome/what-is-debian.xml new file mode 100644 index 000000000..9ebc849c5 --- /dev/null +++ b/ca/welcome/what-is-debian.xml @@ -0,0 +1,110 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 --> + + <sect1 id="what-is-debian"> + <title>Què és Debian?</title> +<para> + +Debian és una organització formada únicament per voluntaris i dedicada al +desenvolupament del programari lliure i a la promoció dels ideals de la Free +Software Foundation. El projecte Debian va començar l'any 1993, quan n'Ian +Murdock va difondre una invitació oberta als desenvolupadors de programari per +contribuir a una distribució de programari completa i coherent, basada en el +relativament nou nucli del Linux. Aquest petit grup d'entusiastes +especialitzats, que originalment va ser patrocinat per la +<ulink url="&url-fsf-intro;">Free Software Foundation</ulink> +i influenciat per la filosofia <ulink url="&url-gnu-intro;">GNU</ulink>, ha +crescut amb els anys fins a esdevenir una organització d'aproximadament +&num-of-debian-developers; <firstterm>desenvolupadors de Debian</firstterm>. + +</para><para> + +Els desenvolupadors de Debian estan involucrats en diverses activitats que +inclouen l'administració dels llocs <ulink url="&url-debian-home;">Web</ulink> +i <ulink url="&url-debian-ftp;">FTP</ulink>, el disseny gràfic, l'anàlisi +legal de les llicències de programari, la redacció de documentació i, +evidentment, el manteniment de paquets de programari. + +</para><para> + +Amb l'objectiu de comunicar la nostra filosofia i atreure els +desenvolupadors que creuen en els principis que representa Debian, +hem publicat una colla de documents que estructuren els nostres +valors i serveixen de guia sobre què significa ser un desenvolupador +de Debian: + +<itemizedlist> +<listitem><para> + +El <ulink url="&url-social-contract;">Contracte Social de Debian</ulink> és +una declaració dels compromisos de Debian respecte la comunitat del programari +lliure. Qualsevol persona que accepti acollir-se al Contracte Social pot +convertir-se en un <ulink url="&url-new-maintainer;">mantenidor</ulink>. +Qualsevol mantenidor pot introduir nou programari a Debian — sempre +que aquest programari es consideri lliure segons els nostres criteris i +el paquet segueixi els nostres estàndards de qualitat. + +</para></listitem> +<listitem><para> + +Les +<ulink url="&url-dfsg;">Directives del Programari Lliure de Debian</ulink> +(DFSG) són una declaració clara i concisa del criteris de Debian referents +al programari lliure. Les DFSG són un document amb molta influència dins +el moviment del programari lliure, i és la base de la +<ulink url="&url-osd;">definició de codi obert</ulink>. + +</para></listitem> +<listitem><para> + +El <ulink url="&url-debian-policy;">manual de política de Debian</ulink> +és una especificació extensa dels estàndards de qualitat del projecte +Debian. + +</para></listitem> +</itemizedlist> +</para><para> + +Els desenvolupadors de Debian també estan involucrats en d'altres projectes; +alguns d'ells específics de Debian i d'altres relacionats amb parts o +amb la totalitat de la comunitat del Linux. Alguns exemples poden ser: + +<itemizedlist> +<listitem><para> + +La <ulink url="&url-lsb-org;">Base Estàndard del Linux</ulink> és un +projecte enfocat a estandarditzar el sistema bàsic GNU/Linux, que +permetrà als desenvolupadors de programari i maquinari de terceres parts +dissenyar fàcilment programes i controladors de dispositius per Linux +en general, en comptes de fer-ho per una distribució específica de +GNU/Linux. + +</para></listitem> +<listitem><para> + +L'<ulink url="&url-fhs-home;">estàndard de jerarquia del sistema de +fitxers</ulink> (FHS) és un esforç per estandarditzar l'esquema del +sistema de fitxers del Linux. L'FHS permetrà als desenvolupadors de +programari concentrar els seus esforços a dissenyar els programes, sense +haver de preocupar-se de com s'instal·larà el paquet en diferents +distribucions de GNU/Linux. + +</para></listitem> +<listitem><para> + +El <ulink url="&url-debian-jr;">Debian Jr.</ulink> és un projecte intern +que vol assegurar-se que Debian té alguna cosa per oferir als usuaris +més joves. + +</para></listitem> +</itemizedlist> + +</para><para> + +Per obtenir informació més general sobre Debian vegeu les +<ulink url="&url-debian-faq;">PMF de Debian</ulink>. + +</para> + + </sect1> + diff --git a/ca/welcome/what-is-linux.xml b/ca/welcome/what-is-linux.xml new file mode 100644 index 000000000..18710262c --- /dev/null +++ b/ca/welcome/what-is-linux.xml @@ -0,0 +1,103 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 --> + + <sect1 id="what-is-linux"> + <title>Què és GNU/Linux?</title> +<para> + +Linux és un sistema operatiu: una sèrie de programes que us permetran +interactuar amb el vostre ordinador i executar altres programes. + +</para><para> + +Un sistema operatiu és un conjunt de programes fonamentals +necessaris perquè l'ordinador pugui comunicar-se i rebre +instruccions dels usuaris, llegir i escriure dades al disc dur, a cintes +i a impressores, controlar l'ús de la memòria i executar més programari. +La part més important d'un sistema operatiu és el nucli. En un sistema +GNU/Linux, Linux és el component que fa de nucli. La resta del sistema +està format d'altres programes, molts dels quals han estat escrits pel o per +a el projecte GNU. Com que el nucli Linux per sí sol no és un sistema +operatiu funcional, preferim utilitzar el terme <quote>GNU/Linux</quote> +per referir-nos al sistema que molta gent acostuma a anomenar +<quote>Linux</quote>. + +</para><para> + +Linux està modelat sobre el sistema operatiu Unix. Des dels seus inicis +es va dissenyar per ser un sistema multitasca i multiusuari. Aquestes +característiques són suficients per fer Linux diferent d'altres sistemes +operatius ben coneguts. Però Linux és inclús més diferent del que pugueu +imaginar. Contràriament a d'altres sistemes operatius, ningú és propietari +de Linux. Molta part del seu desenvolupament el realitzen voluntaris que +no cobren per fer-ho. + +</para><para> + +El desenvolupament del que més endavant seria GNU/Linux començà el 1984, +quan la <ulink url="http://www.gnu.org/">Free Software Foundation</ulink> +va començar a desenvolupar un sistema operatiu lliure similar al Unix +anomenat GNU. + +</para><para> + +El projecte GNU ha desenvolupat un ampli conjunt d'eines de programari +lliure per utilitzar amb sistemes operatius Unix™ o similars, com +Linux. Aquestes eines permeten als usuaris realitzar tasques que van des +de les més mundanes (com copiar o suprimir fitxers del sistema) fins a les +més complexes (com escriure i compilar programes o fer edicions sofisticades +de documents en diferents formats). + +</para><para> + +Tot i que molts grups i persones han contribuït en el desenvolupament de +Linux, el contribuïdor individual més gran segueix sent la Free Software +Foundation, que ha creat no només la major part de les eines utilitzades +en Linux, sinó també la filosofia i la comunitat que ha fet que +Linux sigui possible. + +</para><para> + +El <ulink url="&url-kernel-org;">nucli Linux</ulink> va aparèixer +per primer cop el 1991, quan un estudiant d'informàtica finlandès +anomenat Linus Torvalds va anunciar una primera versió d'un +reemplaçament del nucli del Minix al grup de notícies de Usenet +<userinput>comp.os.minix</userinput>. Vegeu la +<ulink url="&url-linux-history;">pàgina d'història de Linux</ulink>, +de Linux International. + +</para><para> + +En Linus Torvalds segueix coordinant el treball de centenars de +desenvolupadors amb l'ajuda d'alguns col·laboradors de confiança. +Hi ha un excel·lent resum setmanal de les discussions de la llista +de correu del <userinput>nucli Linux</userinput> a +<ulink url="&url-kernel-traffic;">Kernel Traffic</ulink>. També podeu +trobar més informació sobre la llista de correu del +<userinput>nucli Linux</userinput> a les +<ulink url="&url-linux-kernel-list-faq;">PMF de la llista de correu del +nucli Linux.</ulink>. + +</para><para> + +Els usuaris de Linux tenen una immensa llibertat d'elecció del seu +programari. Per exemple, els usuaris de Linux poden triar entre una +dotzena de programes d'intèrpret d'ordres diferents i bastants escriptoris +gràfics. Aquesta llibertat d'elecció sovint resulta desconcertant pels +usuaris d'altres sistemes operatius, els quals no estan acostumats a +pensar en l'intèrpret d'ordres o en l'escriptori com quelcom que poden +canviar. + +</para><para> + +Linux també és menys probable que causi una fallada del sistema, +és més capaç d'executar més d'un programa al mateix temps i és +més segur que molts d'altres sistemes operatius. Amb aquests avantatges, +Linux és el sistema operatiu que té un creixement més ràpid en +el mercat de servidors. Més recentment, Linux també ha començat a +fer-se popular entre els usuaris domèstics i de negocis. + +</para> + + </sect1> + |