diff options
Diffstat (limited to 'fi/preparing/bios-setup')
-rw-r--r-- | fi/preparing/bios-setup/i386.xml | 10 | ||||
-rw-r--r-- | fi/preparing/bios-setup/powerpc.xml | 5 | ||||
-rw-r--r-- | fi/preparing/bios-setup/s390.xml | 4 | ||||
-rw-r--r-- | fi/preparing/bios-setup/sparc.xml | 8 |
4 files changed, 14 insertions, 13 deletions
diff --git a/fi/preparing/bios-setup/i386.xml b/fi/preparing/bios-setup/i386.xml index 668d4ed20..224945c26 100644 --- a/fi/preparing/bios-setup/i386.xml +++ b/fi/preparing/bios-setup/i386.xml @@ -1,5 +1,5 @@ <!-- retain these comments for translator revision tracking --> -<!-- original version: 28997 untranslated --> +<!-- original version: 36732 untranslated --> <sect2 arch="i386" id="bios-setup"><title>Invoking the BIOS Set-Up Menu</title> @@ -124,10 +124,10 @@ controller. </para><para> -Other popular option is to boot from a USB storage (also called USB -memory stick or USB key). Some BIOSes can boot USB storage directly, -and some cannot. You may need to configure your BIOS to boot from -a <quote>Removable drive</quote> or even a <quote>USB-ZIP</quote> to +Another popular option is to boot from a USB storage device (also called +a USB memory stick or USB key). Some BIOSes can boot directly from a USB +storage device, but some cannot. You may need to configure your BIOS to boot +from a <quote>Removable drive</quote> or even from <quote>USB-ZIP</quote> to get it to boot from the USB device. </para><para> diff --git a/fi/preparing/bios-setup/powerpc.xml b/fi/preparing/bios-setup/powerpc.xml index 2368a0853..f170eb172 100644 --- a/fi/preparing/bios-setup/powerpc.xml +++ b/fi/preparing/bios-setup/powerpc.xml @@ -1,5 +1,5 @@ <!-- retain these comments for translator revision tracking --> -<!-- original version: 28672 untranslated --> +<!-- original version: 36732 untranslated --> <sect2 arch="powerpc" id="invoking-openfirmware"> @@ -46,7 +46,8 @@ 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. +<guibutton>Save button</guibutton> to have the firmware patches +installed to nvram. </para> </sect2> diff --git a/fi/preparing/bios-setup/s390.xml b/fi/preparing/bios-setup/s390.xml index b2ed18855..5ac12ce19 100644 --- a/fi/preparing/bios-setup/s390.xml +++ b/fi/preparing/bios-setup/s390.xml @@ -1,5 +1,5 @@ <!-- retain these comments for translator revision tracking --> -<!-- original version: 28672 untranslated --> +<!-- original version: 36732 untranslated --> <sect2 arch="s390"><title>BIOS Setup</title> @@ -94,7 +94,7 @@ FTP. </para><para> The installation server needs to copy the exact directory structure -from any &debian; mirror but of only the s390 and +from any &debian; mirror, but only the s390 and architecture-independent files are required. You can also copy the contents of all installation CDs into such a directory tree. diff --git a/fi/preparing/bios-setup/sparc.xml b/fi/preparing/bios-setup/sparc.xml index 591ea1415..e10786eb6 100644 --- a/fi/preparing/bios-setup/sparc.xml +++ b/fi/preparing/bios-setup/sparc.xml @@ -1,5 +1,5 @@ <!-- retain these comments for translator revision tracking --> -<!-- original version: 28997 untranslated --> +<!-- original version: 36732 untranslated --> <sect2 arch="sparc" id="invoking-openboot"><title>Invoking OpenBoot</title> @@ -10,7 +10,7 @@ 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. +with your machine, such as diagnostics and simple scripts. </para><para> @@ -41,7 +41,7 @@ emulator if you are using a different program. 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 +about how OpenBoot names devices; it's considerably 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 @@ -49,7 +49,7 @@ the <ulink url="&url-openboot;">Sun OpenBoot Reference</ulink>. </para><para> -Typically, with newer revisions, you can use OpenBoot device such as +Typically, with newer revisions, you can use OpenBoot devices 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. |