# SOME DESCRIPTIVE TITLE. # Copyright (C) YEAR Free Software Foundation, Inc. # FIRST AUTHOR , YEAR. # #, fuzzy msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" "POT-Creation-Date: 2006-01-31 23:11+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" "MIME-Version: 1.0\n" "Content-Type: application/x-xml2pot; charset=UTF-8\n" "Content-Transfer-Encoding: ENCODING\n" #. Tag: title #: install-methods.xml:5 #, no-c-format msgid "Obtaining System Installation Media" msgstr "" #. Tag: title #: install-methods.xml:12 #, no-c-format msgid "Official &debian; CD-ROM Sets" msgstr "" #. Tag: para #: install-methods.xml:13 #, no-c-format msgid "" "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 CD vendors page). 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 Debian CD " "page for detailed instructions). If you have a Debian CD set and CDs " "are bootable on your machine, you can skip right to ; 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." msgstr "" #. Tag: para #: install-methods.xml:30 #, no-c-format msgid "" "If your machine doesn't support CD booting, but you do have a CD set, you " "can use an alternative strategy such as floppy disk, tape, emulated tape, hard disk, usb stick, net boot, 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." msgstr "" #. Tag: para #: install-methods.xml:52 #, no-c-format msgid "" "Once the installer is booted, it will be able to obtain all the other files " "it needs from the CD." msgstr "" #. Tag: para #: install-methods.xml:57 #, no-c-format msgid "" "If you don't have a CD set, then you will need to download the installer " "system files and place them on the installation tape floppy disk or " "hard disk or usb stick or a " "connected computer so they can be used to boot the installer." msgstr "" #. Tag: title #: install-methods.xml:83 #, no-c-format msgid "Downloading Files from Debian Mirrors" msgstr "" #. Tag: para #: install-methods.xml:85 #, no-c-format msgid "" "To find the nearest (and thus probably the fastest) mirror, see the list of Debian mirrors." msgstr "" #. Tag: para #: install-methods.xml:90 #, no-c-format msgid "" "When downloading files from a Debian mirror, be sure to download the files " "in binary mode, not text or automatic mode." msgstr "" #. Tag: title #: install-methods.xml:99 #, no-c-format msgid "Where to Find Installation Images" msgstr "" #. Tag: para #: install-methods.xml:101 #, no-c-format msgid "" "The installation images are located on each Debian mirror in the directory " "debian/dists/&releasename;/main/" "installer-&architecture;/current/images/ — the MANIFEST lists each image " "and its purpose." msgstr "" #. Tag: title #: install-methods.xml:113 #, no-c-format msgid "Alpha Installation Files" msgstr "" #. Tag: para #: install-methods.xml:114 #, no-c-format msgid "" "If you choose to boot from ARC console firmware using MILO, you will also need to prepare a disk containing MILO and LINLOAD.EXE from the provided disk images. " "See for more information on Alpha " "firmware and boot loaders. The floppy images can be found in the " "MILO directory as " "milo_subarchitecture.bin." msgstr "" #. Tag: para #: install-methods.xml:125 #, no-c-format msgid "" "Unfortunately, these MILO 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 MILO binary onto the " "floppy (). " "Note that those MILOs don't support ext2 sparse " "superblocks, 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 MILO." msgstr "" #. Tag: para #: install-methods.xml:137 #, no-c-format msgid "" "MILO binaries are platform-specific. See to determine the appropriate MILO image " "for your Alpha platform." msgstr "" #. Tag: title #: install-methods.xml:152 #, no-c-format msgid "RiscPC Installation Files" msgstr "" #. Tag: para #: install-methods.xml:153 #, no-c-format msgid "" "The RiscPC installer is booted initially from RISC OS. All the necessary " "files are provided in one Zip archive, &rpc-install-kit;. Download this file " "onto the RISC OS machine, copy the linloader.!Boot " "components into place, and run !dInstall." msgstr "" #. Tag: title #: install-methods.xml:165 #, no-c-format msgid "NetWinder Installation Files" msgstr "" #. Tag: para #: install-methods.xml:166 #, no-c-format msgid "" "The easiest way to boot a NetWinder is over the network, using the supplied " "TFTP image &netwinder-boot-img;." msgstr "" #. Tag: title #: install-methods.xml:175 #, no-c-format msgid "CATS Installation Files" msgstr "" #. Tag: para #: install-methods.xml:176 #, no-c-format msgid "" "The only supported boot method for CATS is to use the combined image &cats-" "boot-img;. This can be loaded from any device accessible to the Cyclone " "bootloader." msgstr "" #. Tag: title #: install-methods.xml:221 #, no-c-format msgid "Choosing a Kernel" msgstr "" #. Tag: para #: install-methods.xml:223 #, no-c-format msgid "" "Some m68k subarchs have a choice of kernels to install. In general we " "recommend trying the most recent version first. If your subarch or machine " "needs to use a 2.2.x kernel, make sure you choose one of the images that " "supports 2.2.x kernels (see the MANIFEST)." msgstr "" #. Tag: para #: install-methods.xml:232 #, no-c-format msgid "" "All of the m68k images for use with 2.2.x kernels, require the kernel " "parameter &ramdisksize;." msgstr "" #. Tag: title #: install-methods.xml:250 #, no-c-format msgid "Creating an IPL tape" msgstr "" #. Tag: para #: install-methods.xml:252 #, no-c-format msgid "" "If you can't boot (IPL) from the CD-ROM and you are not using VM you need to " "create an IPL tape first. This is described in section 3.4.3 in the Linux " "for IBM eServer zSeries and S/390: Distributions Redbook. The files " "you need to write to the tape are (in this order): kernel.debian, parmfile.debian and initrd.debian. The files can be downloaded from the tape " "sub-directory, see ," msgstr "" #. Tag: title #: install-methods.xml:276 #, no-c-format msgid "Creating Floppies from Disk Images" msgstr "" #. Tag: para #: install-methods.xml:277 #, no-c-format msgid "" "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." msgstr "" #. Tag: para #: install-methods.xml:282 #, no-c-format msgid "Floppy disk booting reportedly fails on Mac USB floppy drives." msgstr "" #. Tag: para #: install-methods.xml:286 #, no-c-format msgid "Floppy disk booting is not supported on Amigas or 68k Macs." msgstr "" #. Tag: para #: install-methods.xml:291 #, no-c-format msgid "" "Disk images are files containing the complete contents of a floppy disk in " "raw form. Disk images, such as boot.img, cannot simply be copied to floppy drives. A special program is " "used to write the image files to floppy disk in raw " "mode. This is required because these images are raw representations of the " "disk; it is required to do a sector copy of the data " "from the file onto the floppy." msgstr "" #. Tag: para #: install-methods.xml:302 #, no-c-format msgid "" "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." msgstr "" #. Tag: para #: install-methods.xml:308 #, no-c-format msgid "" "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." msgstr "" #. Tag: title #: install-methods.xml:316 #, no-c-format msgid "Writing Disk Images From a Linux or Unix System" msgstr "" #. Tag: para #: install-methods.xml:317 #, no-c-format msgid "" "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 \n" "$ dd if=filename of=/dev/fd0 bs=1024 conv=sync ; " "sync\n" " where filename is one " "of the floppy disk image files (see " "for what filename should be). /dev/fd0 is a commonly used name of the floppy disk device, it may be " "different on your workstation (on Solaris, it is " "/dev/fd/0). 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 " "(on Solaris, use eject, see the " "manual page)." msgstr "" #. Tag: para #: install-methods.xml:341 #, no-c-format msgid "" "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 raw mode. " "Unfortunately, how to accomplish this will vary based on your operating " "system. 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 volcheck or the equivalent command " "in the file manager). Then use a dd command of the form " "given above, just replace /dev/fd0 with /vol/" "rdsk/floppy_name, where " "floppy_name is the name the floppy disk was given " "when it was formatted (unnamed floppies default to the name " "unnamed_floppy). On other systems, ask your system " "administrator. " msgstr "" #. Tag: para #: install-methods.xml:362 #, no-c-format msgid "" "If writing a floppy on powerpc Linux, you will need to eject it. The " "eject program handles this nicely; you might need to " "install it." msgstr "" #. Tag: title #: install-methods.xml:380 #, no-c-format msgid "Writing Disk Images From DOS, Windows, or OS/2" msgstr "" #. Tag: para #: install-methods.xml:382 #, no-c-format msgid "" "If you have access to an i386 machine, you can use one of the following " "programs to copy images to floppies." msgstr "" #. Tag: para #: install-methods.xml:387 #, no-c-format msgid "" "The rawrite1 and rawrite2 programs can " "be used under MS-DOS. To use these programs, first make sure that you are " "booted into DOS. Trying to use these programs from within a DOS box in " "Windows, or double-clicking on these programs from the Windows Explorer is " "not expected to work." msgstr "" #. Tag: para #: install-methods.xml:395 #, no-c-format msgid "" "The rwwrtwin program runs on Windows 95, NT, 98, 2000, " "ME, XP and probably later versions. To use it you will need to unpack diskio." "dll in the same directory." msgstr "" #. Tag: para #: install-methods.xml:401 #, no-c-format msgid "" "These tools can be found on the Official Debian CD-ROMs under the /" "tools directory." msgstr "" #. Tag: title #: install-methods.xml:414 #, no-c-format msgid "Writing Disk Images on Atari Systems" msgstr "" #. Tag: para #: install-methods.xml:415 #, no-c-format msgid "" "You'll find the &rawwrite.ttp; program in the same directory as the floppy " "disk images. Start the program by double clicking on the program icon, and " "type in the name of the floppy image file you want written to the floppy at " "the TOS program command line dialog box." msgstr "" #. Tag: title #: install-methods.xml:426 #, no-c-format msgid "Writing Disk Images on Macintosh Systems" msgstr "" #. Tag: para #: install-methods.xml:427 #, no-c-format msgid "" "There is no MacOS application to write images to floppy disks (and there " "would be no point in doing this as you can't use these floppies to boot the " "installation system or install kernel and modules from on Macintosh). " "However, these files are needed for the installation of the operating system " "and modules, later in the process." msgstr "" #. Tag: title #: install-methods.xml:445 #, no-c-format msgid "Writing Disk Images From MacOS" msgstr "" #. Tag: para #: install-methods.xml:446 #, no-c-format msgid "" "An AppleScript, Make Debian Floppy, is available " "for burning floppies from the provided disk image files. It can be " "downloaded from . 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." msgstr "" #. Tag: para #: install-methods.xml:457 #, no-c-format msgid "" "You can also use the MacOS utility Disk Copy directly, or " "the freeware utility suntar. The root.bin 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." msgstr "" #. Tag: title #: install-methods.xml:468 #, no-c-format msgid "Writing Disk Images with Disk Copy" msgstr "" #. Tag: para #: install-methods.xml:469 #, no-c-format msgid "" "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 Creator-Changer steps are only necessary if " "you downloaded the image files from a Debian mirror." msgstr "" #. Tag: para #: install-methods.xml:478 #, no-c-format msgid "" "Obtain Creator-Changer " "and use it to open the root.bin file." msgstr "" #. Tag: para #: install-methods.xml:485 #, no-c-format msgid "" "Change the Creator to ddsk (Disk Copy), and the Type " "to DDim (binary floppy image). The case is sensitive " "for these fields." msgstr "" #. Tag: para #: install-methods.xml:492 #, no-c-format msgid "" "Important: In the Finder, use Get Info to display the Finder information about the floppy image, and " "X the File Locked check box so that " "MacOS will be unable to remove the boot blocks if the image is accidentally " "mounted." msgstr "" #. Tag: para #: install-methods.xml:501 #, no-c-format msgid "" "Obtain Disk Copy; if you have a MacOS system or CD it " "will very likely be there already, otherwise try ." msgstr "" #. Tag: para #: install-methods.xml:508 #, no-c-format msgid "" "Run Disk Copy, and select " "Utilities Make a Floppy , then select the locked 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." msgstr "" #. Tag: title #: install-methods.xml:523 #, no-c-format msgid "Writing Disk Images with suntar" msgstr "" #. Tag: para #: install-methods.xml:527 #, no-c-format msgid "" "Obtain suntar from . Start the suntar program and select " "Overwrite Sectors... from the Special " "menu." msgstr "" #. Tag: para #: install-methods.xml:535 #, no-c-format msgid "" "Insert the floppy disk as requested, then hit &enterkey; (start at sector 0)." msgstr "" #. Tag: para #: install-methods.xml:541 #, no-c-format msgid "" "Select the root.bin file in the file-opening dialog." msgstr "" #. Tag: para #: install-methods.xml:546 #, no-c-format msgid "" "After the floppy has been created successfully, select " "File Eject . If " "there are any errors writing the floppy, simply toss that floppy and try " "another." msgstr "" #. Tag: para #: install-methods.xml:554 #, no-c-format msgid "" "Before using the floppy you created, set the write protect tab! Otherwise if you accidentally mount it in MacOS, MacOS will " "helpfully ruin it." msgstr "" #. Tag: title #: install-methods.xml:573 #, no-c-format msgid "Preparing Files for USB Memory Stick Booting" msgstr "" #. Tag: para #: install-methods.xml:575 #, no-c-format msgid "" "For preparing the USB stick you will need a system where GNU/Linux is " "already running and where USB is supported. You should ensure that the usb-" "storage kernel module is loaded (modprobe usb-storage) and try to find out which SCSI device the USB stick has been " "mapped to (in this example /dev/sda is used). To write " "to your stick, you will probably have to turn off its write protection " "switch." msgstr "" #. Tag: para #: install-methods.xml:585 #, no-c-format msgid "" "Note, that the USB stick should be at least 128 MB in size (smaller setups " "are possible if you follow )." msgstr "" #. Tag: title #: install-methods.xml:593 #, no-c-format msgid "Copying the files — the easy way" msgstr "" #. Tag: para #: install-methods.xml:594 #, no-c-format msgid "" "There is an all-in-one file hd-media/boot.img.gz which " "contains all the installer files (including the kernel) as well as " "SYSLINUX and its configuration file. You only have to " "extract it directly to your USB stick:" msgstr "" #. Tag: screen #: install-methods.xml:601 #, no-c-format msgid "# zcat boot.img.gz > /dev/sda" msgstr "" #. Tag: para #: install-methods.xml:603 #, no-c-format msgid "" "There is an all-in-one file hd-media/boot.img.gz which " "contains all the installer files (including the kernel) as well as " "yaboot and its configuration file. Create a partition of " "type \"Apple_Bootstrap\" on your USB stick using mac-fdisk's C command and extract the image directly " "to that:" msgstr "" #. Tag: screen #: install-methods.xml:612 #, no-c-format msgid "# zcat boot.img.gz > /dev/sda2" msgstr "" #. Tag: para #: install-methods.xml:615 #, no-c-format msgid "" "Using this method will destroy anything already on the device. Make sure " "that you use the correct device name for your USB stick." msgstr "" #. Tag: para #: install-methods.xml:621 #, no-c-format msgid "" "After that, mount the USB memory stick (mount /dev/sda /dev/sda2 /mnt), which will now have a " "FAT filesystem an HFS filesystem " "on it, and copy a Debian netinst or businesscard ISO image to it. Please " "note that the file name must end in .iso. Unmount the " "stick (umount /mnt) and you are done." msgstr "" #. Tag: title #: install-methods.xml:637 #, no-c-format msgid "Copying the files — the flexible way" msgstr "" #. Tag: para #: install-methods.xml:638 #, no-c-format msgid "" "If you like more flexibility or just want to know what's going on, you " "should use the following method to put the files on your stick." msgstr "" #. Tag: title #: install-methods.xml:650 install-methods.xml:742 #, no-c-format msgid "USB stick partitioning on &arch-title;" msgstr "" #. Tag: para #: install-methods.xml:651 #, no-c-format msgid "" "We will show how to setup the memory stick to use the first partition, " "instead of the entire device." msgstr "" #. Tag: para #: install-methods.xml:656 #, no-c-format msgid "" "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 cfdisk or any other partitioning tool " "for creating a FAT16 partition and then create the filesystem using: " "\n" "# mkdosfs /dev/sda1\n" " Take care that you use the correct device name " "for your USB stick. The mkdosfs command is contained in " "the dosfstools Debian package." msgstr "" #. Tag: para #: install-methods.xml:670 #, no-c-format msgid "" "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. LILO) should work, it's convenient to use SYSLINUX, " "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." msgstr "" #. Tag: para #: install-methods.xml:680 #, no-c-format msgid "" "To put SYSLINUX on the FAT16 partition on your USB stick, " "install the syslinux and mtools packages on your system, and do: \n" "# syslinux /dev/sda1\n" " Again, take care that you use the correct device " "name. The partition must not be mounted when starting SYSLINUX. This procedure writes a boot sector to the partition and creates " "the file ldlinux.sys which contains the boot loader " "code." msgstr "" #. Tag: para #: install-methods.xml:693 #, no-c-format msgid "" "Mount the partition (mount /dev/sda1 /mnt) and copy " "the following files from the Debian archives to the stick: " " vmlinuz (kernel binary) initrd.gz (initial ramdisk " "image) syslinux.cfg " "(SYSLINUX configuration file) Optional " "kernel modules If you want to rename the " "files, please note that SYSLINUX can only process DOS " "(8.3) file names." msgstr "" #. Tag: para #: install-methods.xml:724 #, no-c-format msgid "" "The syslinux.cfg configuration file should contain the " "following two lines: \n" "default vmlinuz\n" "append initrd=initrd.gz ramdisk_size=12000 root=/dev/ram rw\n" " Please note that the ramdisk_size parameter may need to be increased, depending on the image you " "are booting." msgstr "" #. Tag: para #: install-methods.xml:743 #, no-c-format msgid "" "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 mac-fdisk /dev/sda, initialise a new " "partition map using the i command, and create a new " "partition of type Apple_Bootstrap using the C " "command. (Note that the first \"partition\" will always be the partition map " "itself.) Then type \n" "$ hformat /dev/sda2\n" " Take care that you use the correct device name " "for your USB stick. The hformat command is contained in " "the hfsutils Debian package." msgstr "" #. Tag: para #: install-methods.xml:759 #, no-c-format msgid "" "In order to start the kernel after booting from the USB stick, we will put a " "boot loader on the stick. The yaboot 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." msgstr "" #. Tag: para #: install-methods.xml:768 #, no-c-format msgid "" "The normal ybin tool that comes with yaboot does not yet understand USB storage devices, so you will have to " "install yaboot by hand using the hfsutils tools. Type \n" "$ hmount /dev/sda2\n" "$ hcopy -r /usr/lib/yaboot/yaboot :\n" "$ hattrib -c UNIX -t tbxi :yaboot\n" "$ hattrib -b :\n" "$ humount\n" " 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." msgstr "" #. Tag: para #: install-methods.xml:784 #, no-c-format msgid "" "Mount the partition (mount /dev/sda2 /mnt) and copy " "the following files from the Debian archives to the stick:" msgstr "" #. Tag: para #: install-methods.xml:790 #, no-c-format msgid "vmlinux (kernel binary)" msgstr "" #. Tag: para #: install-methods.xml:795 #, no-c-format msgid "initrd.gz (initial ramdisk image)" msgstr "" #. Tag: para #: install-methods.xml:800 #, no-c-format msgid "yaboot.conf (yaboot configuration file)" msgstr "" #. Tag: para #: install-methods.xml:805 #, no-c-format msgid "boot.msg (optional boot message)" msgstr "" #. Tag: para #: install-methods.xml:810 #, no-c-format msgid "Optional kernel modules" msgstr "" #. Tag: para #: install-methods.xml:817 #, no-c-format msgid "" "The yaboot.conf configuration file should contain the " "following lines: \n" "default=install\n" "root=/dev/ram\n" "\n" "message=/boot.msg\n" "\n" "image=/vmlinux\n" " label=install\n" " initrd=/initrd.gz\n" " initrd-size=10000\n" " read-only\n" " Please note that the initrd-size parameter may need to be increased, depending on the image you " "are booting." msgstr "" #. Tag: title #: install-methods.xml:832 #, no-c-format msgid "Adding an ISO image" msgstr "" #. Tag: para #: install-methods.xml:833 #, no-c-format msgid "" "Now you should put any Debian ISO image (businesscard, netinst or even a " "full one) onto your stick (if it fits). The file name of such an image must " "end in .iso." msgstr "" #. Tag: para #: install-methods.xml:839 #, no-c-format msgid "" "If you want to install over the network, without using an ISO image, you " "will of course skip the previous step. Moreover you will have to use the " "initial ramdisk from the netboot directory instead of " "the one from hd-media, because hd-media/" "initrd.gz does not have network support." msgstr "" #. Tag: para #: install-methods.xml:848 #, no-c-format msgid "" "When you are done, unmount the USB memory stick (umount /mnt) and activate its write protection switch." msgstr "" #. Tag: title #: install-methods.xml:858 #, no-c-format msgid "Booting the USB stick" msgstr "" #. Tag: para #: install-methods.xml:859 #, no-c-format msgid "" "If your system refuses to boot from the memory stick, the stick may contain " "an invalid master boot record (MBR). To fix this, use the install-" "mbr command from the package mbr:" msgstr "" #. Tag: screen #: install-methods.xml:866 #, no-c-format msgid "# install-mbr /dev/sda" msgstr "" #. Tag: title #: install-methods.xml:878 #, no-c-format msgid "Preparing Files for Hard Disk Booting" msgstr "" #. Tag: para #: install-methods.xml:879 #, no-c-format msgid "" "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." msgstr "" #. Tag: para #: install-methods.xml:885 #, no-c-format msgid "" "A full, pure network 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." msgstr "" #. Tag: para #: install-methods.xml:892 #, no-c-format msgid "The installer cannot boot from files on an NTFS file system." msgstr "" #. Tag: para #: install-methods.xml:896 #, no-c-format msgid "" "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 Get " "Info for the volume in question. HFS file systems appear as " "Mac OS Standard, while HFS+ file systems say " "Mac OS Extended. You must have an HFS partition in " "order to exchange files between MacOS and Linux, in particular the " "installation files you download." msgstr "" #. Tag: para #: install-methods.xml:907 #, no-c-format msgid "" "Different programs are used for hard disk installation system booting, " "depending on whether the system is a NewWorld or an " "OldWorld model." msgstr "" #. Tag: title #: install-methods.xml:916 #, no-c-format msgid "" "Hard disk installer booting using LILO or GRUB" msgstr "" #. Tag: para #: install-methods.xml:918 #, no-c-format msgid "" "This section explains how to add to or even replace an existing linux " "installation using either LILO or GRUB." msgstr "" #. Tag: para #: install-methods.xml:924 #, no-c-format msgid "" "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." msgstr "" #. Tag: para #: install-methods.xml:930 #, no-c-format msgid "" "Copy the following files from the Debian archives to a convenient location " "on your hard drive, for instance to /boot/newinstall/." msgstr "" #. Tag: para #: install-methods.xml:937 #, no-c-format msgid "vmlinuz (kernel binary)" msgstr "" #. Tag: para #: install-methods.xml:942 #, no-c-format msgid "initrd.gz (ramdisk image)" msgstr "" #. Tag: para #: install-methods.xml:949 #, no-c-format msgid "" "Finally, to configure the bootloader proceed to ." msgstr "" #. Tag: title #: install-methods.xml:959 #, no-c-format msgid "Hard Disk Installer Booting for OldWorld Macs" msgstr "" #. Tag: para #: install-methods.xml:960 #, no-c-format msgid "" "The boot-floppy-hfs floppy uses miBoot to launch Linux installation, but miBoot cannot easily be used for hard disk booting. " "BootX, launched from MacOS, supports booting from " "files placed on the hard disk. BootX can also be " "used to dual-boot MacOS and Linux after your Debian installation is " "complete. For the Performa 6360, it appears that quik " "cannot make the hard disk bootable. So BootX is " "required on that model." msgstr "" #. Tag: para #: install-methods.xml:973 #, no-c-format msgid "" "Download and unstuff the BootX distribution, " "available from , or in the " "dists/woody/main/disks-powerpc/current/powermac " "directory on Debian http/ftp mirrors and official Debian CDs. Use " "Stuffit Expander to extract it from its archive. " "Within the package, there is an empty folder called Linux Kernels. Download linux.bin and ramdisk." "image.gz from the disks-powerpc/current/powermac folder, and place them in the Linux Kernels " "folder. Then place the Linux Kernels folder in the " "active System Folder." msgstr "" #. Tag: title #: install-methods.xml:993 #, no-c-format msgid "Hard Disk Installer Booting for NewWorld Macs" msgstr "" #. Tag: para #: install-methods.xml:994 #, no-c-format msgid "" "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 yaboot, 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. BootX is not supported and must not be used on NewWorld PowerMacs." msgstr "" #. Tag: para #: install-methods.xml:1005 #, no-c-format msgid "" "Copy (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 option-dragging " "each file to the hard drive icon)." msgstr "" #. Tag: filename #: install-methods.xml:1015 #, no-c-format msgid "vmlinux" msgstr "" #. Tag: filename #: install-methods.xml:1020 #, no-c-format msgid "initrd.gz" msgstr "" #. Tag: filename #: install-methods.xml:1025 #, no-c-format msgid "yaboot" msgstr "" #. Tag: filename #: install-methods.xml:1030 #, no-c-format msgid "yaboot.conf" msgstr "" #. Tag: para #: install-methods.xml:1035 #, no-c-format msgid "" "Make a note of the partition number of the MacOS partition where you place " "these files. If you have the MacOS pdisk 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." msgstr "" #. Tag: para #: install-methods.xml:1043 #, no-c-format msgid "To boot the installer, proceed to ." msgstr "" #. Tag: title #: install-methods.xml:1056 #, no-c-format msgid "Preparing Files for TFTP Net Booting" msgstr "" #. Tag: para #: install-methods.xml:1057 #, no-c-format msgid "" "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." msgstr "" #. Tag: para #: install-methods.xml:1065 #, no-c-format msgid "" "You need to setup a TFTP server, and for many machines, a BOOTP server " ", or RARP server , or DHCP server." msgstr "" #. Tag: para #: install-methods.xml:1071 #, no-c-format msgid "" "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. BOOTP is an IP protocol that informs a computer of its IP " "address and where on the network to obtain a boot image. Yet another alternative exists on VMEbus systems: the IP " "address can be manually configured in boot ROM. The DHCP (Dynamic Host Configuration Protocol) is a more " "flexible, backwards-compatible extension of BOOTP. Some systems can only be " "configured via DHCP. " msgstr "" #. Tag: para #: install-methods.xml:1088 #, no-c-format msgid "" "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." msgstr "" #. Tag: para #: install-methods.xml:1094 #, no-c-format msgid "" "Unlike the Open Firmware found on Sparc and PowerPC machines, the SRM " "console will not use RARP to obtain its IP address, and " "therefore you must use BOOTP for net booting your Alpha " "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. . You can " "also enter the IP configuration for network interfaces directly in the SRM " "console." msgstr "" #. Tag: para #: install-methods.xml:1111 #, no-c-format msgid "" "Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. There " "is an rbootd package available in Debian." msgstr "" #. Tag: para #: install-methods.xml:1116 #, no-c-format msgid "" "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." msgstr "" #. Tag: para #: install-methods.xml:1124 #, no-c-format msgid "" "To use the Pre-boot Execution Environment (PXE) method of TFTP booting, you " "will need a TFTP server with tsize support. On a " "&debian; server, the atftpd and tftpd-hpa packages qualify; we recommend tftpd-hpa." msgstr "" #. Tag: title #: install-methods.xml:1142 #, no-c-format msgid "Setting up RARP server" msgstr "" #. Tag: para #: install-methods.xml:1143 #, no-c-format msgid "" "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 pick it off the initial " "OpenPROM boot messages, use the OpenBoot .enet-addr " "command, or boot into Rescue mode (e.g., from the " "rescue floppy) and use the command /sbin/ifconfig eth0." msgstr "" #. Tag: para #: install-methods.xml:1155 #, no-c-format msgid "" "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: " "\n" "# /sbin/rarp -s\n" "client-hostname\n" "client-enet-addr\n" "\n" "# /usr/sbin/arp -s\n" "client-ip\n" "client-enet-addr\n" " If you get \n" "SIOCSRARP: Invalid argument\n" " you probably need to load the RARP kernel module " "or else recompile the kernel to support RARP. Try modprobe rarp and then try the rarp command again." msgstr "" #. Tag: para #: install-methods.xml:1171 #, no-c-format msgid "" "On a RARP server system using a Linux 2.4.x kernel, there is no RARP module, " "and you should instead use the rarpd program. The " "procedure is similar to that used under SunOS in the following paragraph." msgstr "" #. Tag: para #: install-methods.xml:1179 #, no-c-format msgid "" "Under SunOS, you need to ensure that the Ethernet hardware address for the " "client is listed in the ethers database (either in the " "/etc/ethers file, or via NIS/NIS+) and in the " "hosts database. Then you need to start the RARP daemon. In " "SunOS 4, issue the command (as root): /usr/etc/rarpd -a; in SunOS 5, use /usr/sbin/rarpd -a." msgstr "" #. Tag: title #: install-methods.xml:1198 #, no-c-format msgid "Setting up BOOTP server" msgstr "" #. Tag: para #: install-methods.xml:1199 #, no-c-format msgid "" "There are two BOOTP servers available for GNU/Linux, the CMU " "bootpd and the other is actually a DHCP server, ISC " "dhcpd, which are contained in the bootp and dhcp packages in &debian;." msgstr "" #. Tag: para #: install-methods.xml:1207 #, no-c-format msgid "" "To use CMU bootpd, you must first uncomment (or add) the " "relevant line in /etc/inetd.conf. On &debian;, you can " "run update-inetd --enable bootps, then /" "etc/init.d/inetd reload to do so. Elsewhere, the line in " "question should look like: \n" "bootps dgram udp wait root /usr/sbin/bootpd bootpd -i -t 120\n" " Now, you must create an /etc/bootptab file. This has the same sort of familiar and cryptic format as the " "good old BSD printcap, termcap, " "and disktab files. See the bootptab manual page for more information. For CMU bootpd, you will need to know the hardware (MAC) address of the client. " "Here is an example /etc/bootptab: " "\n" "client:\\\n" " hd=/tftpboot:\\\n" " bf=tftpboot.img:\\\n" " ip=192.168.1.90:\\\n" " sm=255.255.255.0:\\\n" " sa=192.168.1.1:\\\n" " ha=0123456789AB:\n" " You will need to change at least the ha option, which specifies the hardware address of the client. The " "bf option specifies the file a client should retrieve via " "TFTP; see for more details. On SGI Indys you can just enter the command monitor and type " "printenv. The value of the eaddr variable is the machine's MAC address. " msgstr "" #. Tag: para #: install-methods.xml:1240 #, no-c-format msgid "" "By contrast, setting up BOOTP with ISC dhcpd 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 . Otherwise, you will probably be able to get away with simply " "adding the allow bootp directive to the configuration " "block for the subnet containing the client, and restart dhcpd with /etc/init.d/dhcpd restart." msgstr "" #. Tag: title #: install-methods.xml:1261 #, no-c-format msgid "Setting up a DHCP server" msgstr "" #. Tag: para #: install-methods.xml:1262 #, no-c-format msgid "" "One free software DHCP server is ISC dhcpd. In &debian;, " "this is available in the dhcp package. Here is a " "sample configuration file for it (usually /etc/dhcpd.conf): \n" "option domain-name \"example.com\";\n" "option domain-name-servers ns1.example.com;\n" "option subnet-mask 255.255.255.0;\n" "default-lease-time 600;\n" "max-lease-time 7200;\n" "server-name \"servername\";\n" "\n" "subnet 192.168.1.0 netmask 255.255.255.0 {\n" " range 192.168.1.200 192.168.1.253;\n" " option routers 192.168.1.1;\n" "}\n" "\n" "host clientname {\n" " filename \"/tftpboot/tftpboot.img\";\n" " server-name \"servername\";\n" " next-server servername;\n" " hardware ethernet 01:23:45:67:89:AB;\n" " fixed-address 192.168.1.90;\n" "}\n" " Note: the new (and preferred) dhcp3 package uses /etc/dhcp3/dhcpd.conf." msgstr "" #. Tag: para #: install-methods.xml:1274 #, no-c-format msgid "" "In this example, there is one server servername " "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 " "filename option should be the name of the file " "which will be retrieved via TFTP." msgstr "" #. Tag: para #: install-methods.xml:1284 #, no-c-format msgid "" "After you have edited the dhcpd configuration file, " "restart it with /etc/init.d/dhcpd restart." msgstr "" #. Tag: title #: install-methods.xml:1292 #, no-c-format msgid "Enabling PXE Booting in the DHCP configuration" msgstr "" #. Tag: para #: install-methods.xml:1293 #, no-c-format msgid "" "Here is another example for a dhcp.conf using the Pre-" "boot Execution Environment (PXE) method of TFTP. \n" "option domain-name \"example.com\";\n" "\n" "default-lease-time 600;\n" "max-lease-time 7200;\n" "\n" "allow booting;\n" "allow bootp;\n" "\n" "# The next paragraph needs to be modified to fit your case\n" "subnet 192.168.1.0 netmask 255.255.255.0 {\n" " range 192.168.1.200 192.168.1.253;\n" " option broadcast-address 192.168.1.255;\n" "# the gateway address which can be different\n" "# (access to the internet for instance)\n" " option routers 192.168.1.1;\n" "# indicate the dns you want to use\n" " option domain-name-servers 192.168.1.3;\n" "}\n" "\n" "group {\n" " next-server 192.168.1.3;\n" " host tftpclient {\n" "# tftp client hardware address\n" " hardware ethernet 00:10:DC:27:6C:15;\n" " filename \"/tftpboot/pxelinux.0\";\n" " }\n" "}\n" " Note that for PXE booting, the client filename " "pxelinux.0 is a boot loader, not a kernel image (see " " below)." msgstr "" #. Tag: title #: install-methods.xml:1309 #, no-c-format msgid "Enabling the TFTP Server" msgstr "" #. Tag: para #: install-methods.xml:1310 #, no-c-format msgid "" "To get the TFTP server ready to go, you should first make sure that " "tftpd is enabled. This is usually enabled by having " "something like the following line in /etc/inetd.conf: " "\n" "tftp dgram udp wait nobody /usr/sbin/tcpd in.tftpd /tftpboot\n" " Debian packages will in general set this up " "correctly by default when they are installed." msgstr "" #. Tag: para #: install-methods.xml:1321 #, no-c-format msgid "" "Look in that file and remember the directory which is used as the argument " "of in.tftpd; you'll need that below. The -l argument enables some versions of in.tftpd to " "log all requests to the system logs; this is useful for diagnosing boot " "errors. If you've had to change /etc/inetd.conf, you'll " "have to notify the running inetd process that the file " "has changed. On a Debian machine, run /etc/init.d/inetd reload; on other machines, find out the process ID for inetd, and run kill -HUP inetd-pid." msgstr "" #. Tag: para #: install-methods.xml:1335 #, no-c-format msgid "" "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: \n" "# echo 1 > /proc/sys/net/ipv4/ip_no_pmtu_disc\n" " 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 \n" "# echo \"2048 32767\" > /proc/sys/net/ipv4/ip_local_port_range\n" " to adjust the range of source ports the Linux " "TFTP server uses." msgstr "" #. Tag: title #: install-methods.xml:1357 #, no-c-format msgid "Move TFTP Images Into Place" msgstr "" #. Tag: para #: install-methods.xml:1358 #, no-c-format msgid "" "Next, place the TFTP boot image you need, as found in , in the tftpd boot image directory. Generally, " "this directory will be /tftpboot. You'll have to make a " "link from that file to the file which tftpd will use for " "booting a particular client. Unfortunately, the file name is determined by " "the TFTP client, and there are no strong standards." msgstr "" #. Tag: para #: install-methods.xml:1368 #, no-c-format msgid "" "On NewWorld Power Macintosh machines, you will need to set up the " "yaboot boot loader as the TFTP boot image. " "Yaboot will then retrieve the kernel and RAMdisk images " "via TFTP itself. For net booting, use the yaboot-netboot.conf. Just rename this to yaboot.conf in the TFTP " "directory." msgstr "" #. Tag: para #: install-methods.xml:1377 #, no-c-format msgid "" "For PXE booting, everything you should need is set up in the " "netboot/netboot.tar.gz tarball. Simply extract this " "tarball into the tftpd boot image directory. Make sure " "your dhcp server is configured to pass /pxelinux.0 to " "tftpd as the filename to boot." msgstr "" #. Tag: para #: install-methods.xml:1385 #, no-c-format msgid "" "For PXE booting, everything you should need is set up in the " "netboot/netboot.tar.gz tarball. Simply extract this " "tarball into the tftpd boot image directory. Make sure " "your dhcp server is configured to pass /debian-installer/ia64/" "elilo.efi to tftpd as the filename to boot." msgstr "" #. Tag: title #: install-methods.xml:1397 #, no-c-format msgid "DECstation TFTP Images" msgstr "" #. Tag: para #: install-methods.xml:1398 #, no-c-format msgid "" "For DECstations, there are tftpimage files for each subarchitecture, which " "contain both kernel and installer in one file. The naming convention is " "subarchitecture/netboot-boot.img. Copy the " "tftpimage file you would like to use to /tftpboot/tftpboot.img if you work with the example BOOTP/DHCP setups described above." msgstr "" #. Tag: para #: install-methods.xml:1407 #, no-c-format msgid "" "The DECstation firmware boots by TFTP with the command boot " "#/tftp, where # is the number of the TurboChannel device from which to boot. On " "most DECstations this is 3. 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:" msgstr "" #. Tag: userinput #: install-methods.xml:1419 #, no-c-format msgid "boot #/tftp/filename param1=value1 param2=value2 ..." msgstr "" #. Tag: para #: install-methods.xml:1421 #, no-c-format msgid "" "Several DECstation firmware revisions show a problem with regard to net " "booting: the transfer starts, but after some time it stops with an " "a.out err. This can have several reasons: " " 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 arp -s IP-address " "MAC-address as root on the machine " "acting as TFTP server. The MAC-address of the DECstation can be read out by " "entering cnfg at the DECstation firmware prompt. The firmware has a size limit on the files that " "can be booted by TFTP. 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: ." msgstr "" #. Tag: title #: install-methods.xml:1459 #, no-c-format msgid "Alpha TFTP Booting" msgstr "" #. Tag: para #: install-methods.xml:1460 #, no-c-format msgid "" "On Alpha, you must specify the filename (as a relative path to the boot " "image directory) using the -file argument to the SRM " "boot command, or by setting the BOOT_FILE environment variable. Alternatively, the filename can be given " "via BOOTP (in ISC dhcpd, use the filename directive). Unlike Open Firmware, there is no default " "filename on SRM, so you must specify a " "filename by either one of these methods." msgstr "" #. Tag: title #: install-methods.xml:1475 #, no-c-format msgid "SPARC TFTP Booting" msgstr "" #. Tag: para #: install-methods.xml:1476 #, no-c-format msgid "" "SPARC architectures for instance use the subarchitecture names, such as " "SUN4M or SUN4C; in some cases, the " "architecture is left blank, so the file the client looks for is just " "client-ip-in-hex. Thus, if your system subarchitecture " "is a SUN4C, and its IP is 192.168.1.3, the filename would be " "C0A80103.SUN4C. 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). \n" "$ printf '%.2x%.2x%.2x%.2x\\n' 10 0 0 4\n" " 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." msgstr "" #. Tag: para #: install-methods.xml:1493 #, no-c-format msgid "" "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 boot " "net my-sparc.image. This must still reside in the directory that " "the TFTP server looks in." msgstr "" #. Tag: title #: install-methods.xml:1504 #, no-c-format msgid "BVM/Motorola TFTP Booting" msgstr "" #. Tag: para #: install-methods.xml:1505 #, no-c-format msgid "" "For BVM and Motorola VMEbus systems copy the files &bvme6000-tftp-files; to " "/tftpboot/." msgstr "" #. Tag: para #: install-methods.xml:1510 #, no-c-format msgid "" "Next, configure your boot ROMs or BOOTP server to initially load the " "tftplilo.bvme or tftplilo.mvme " "files from the TFTP server. Refer to the tftplilo.txt " "file for your subarchitecture for additional system-specific configuration " "information." msgstr "" #. Tag: title #: install-methods.xml:1522 #, no-c-format msgid "SGI Indys TFTP Booting" msgstr "" #. Tag: para #: install-methods.xml:1523 #, no-c-format msgid "" "On SGI Indys you can rely on the bootpd to supply the " "name of the TFTP file. It is given either as the bf= " "in /etc/bootptab or as the filename= option in /etc/dhcpd.conf." msgstr "" #. Tag: title #: install-methods.xml:1535 #, no-c-format msgid "Broadcom BCM91250A TFTP Booting" msgstr "" #. Tag: para #: install-methods.xml:1536 #, no-c-format msgid "" "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." msgstr "" #. Tag: title #: install-methods.xml:1641 #, no-c-format msgid "Automatic Installation" msgstr "" #. Tag: para #: install-methods.xml:1642 #, no-c-format msgid "" "For installing on multiple computers it's possible to do fully automatic " "installations. Debian packages intended for this include fai (which uses an install server), replicator, systemimager, autoinstall, and the Debian Installer itself." msgstr "" #. Tag: title #: install-methods.xml:1655 #, no-c-format msgid "Automatic Installation Using the Debian Installer" msgstr "" #. Tag: para #: install-methods.xml:1656 #, no-c-format msgid "" "The Debian Installer supports automating installs via preconfiguration " "files. A preconfiguration file can be loaded from the network or from " "removable media, and used to fill in answers to questions asked during the " "installation process." msgstr "" #. Tag: para #: install-methods.xml:1663 #, no-c-format msgid "" "Full documentation on preseeding including a working example that you can " "edit is in ." msgstr ""