diff options
author | Joey Hess <joeyh@debian.org> | 2005-10-07 19:51:38 +0000 |
---|---|---|
committer | Joey Hess <joeyh@debian.org> | 2005-10-07 19:51:38 +0000 |
commit | 1ea73eea5ecc6a8ed901316049259aee737ee554 (patch) | |
tree | 03a077f0b1b1548f3c806bd1c5795964fba0fb52 /eu/preparing/bios-setup/s390.xml | |
download | installation-guide-1ea73eea5ecc6a8ed901316049259aee737ee554.zip |
move manual to top-level directory, split out of debian-installer package
Diffstat (limited to 'eu/preparing/bios-setup/s390.xml')
-rw-r--r-- | eu/preparing/bios-setup/s390.xml | 106 |
1 files changed, 106 insertions, 0 deletions
diff --git a/eu/preparing/bios-setup/s390.xml b/eu/preparing/bios-setup/s390.xml new file mode 100644 index 000000000..369b51873 --- /dev/null +++ b/eu/preparing/bios-setup/s390.xml @@ -0,0 +1,106 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 12756 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>vmrdr</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> |