Mercurial > docs > s390-linux
changeset 12:e5ab4d0d4407
zvm-centos4: finished the first version
author | Josef 'Jeff' Sipek <jeffpc@josefsipek.net> |
---|---|
date | Fri, 07 Nov 2008 12:51:45 -0500 |
parents | 43f87a840ead |
children | 82b4c40a4f5c 4e9e8eede5dd |
files | body-zvm-centos4.html |
diffstat | 1 files changed, 57 insertions(+), 24 deletions(-) [+] |
line wrap: on
line diff
--- a/body-zvm-centos4.html Wed Sep 03 14:32:37 2008 -0400 +++ b/body-zvm-centos4.html Fri Nov 07 12:51:45 2008 -0500 @@ -10,7 +10,7 @@ <p> The following howto assumes, that you know at least a little bit of: <ul> - <li>CentOS/RHEL familiarity</li> + <li>CentOS/RHEL installer familiarity on non s390</li> <li>General networking knowledge</li> </ul> </p> @@ -36,13 +36,11 @@ </p> <p> -So, point your browser to the mirror nearest you, navigate to this rather -long path: +So, point your browser to the mirror nearest you, navigate to this path: <pre>/centos-4/4.6/os/s390/images/</pre> and grab these files: <pre> -redhat.exec kernel.img initrd.img generic.prm @@ -52,7 +50,23 @@ as well.<br/> <br/> Note: If you want a 64-bit system, you'll want to use <strong>s390x</strong> -in the path instead. +in the path instead.<br/> +<br/> +I used this REXX script as to make my life easier. I called it +redhat.exec (you'll notice that some of the files are called redhat or rhel, +that's because I based my install steps on scripts/config files used to +install RHEL on s390):<br/> +<pre> +/* */ +'CL RDR' +'PURGE RDR ALL' +'SPOOL PUNCH * RDR' +'PUNCH KERNEL IMG A (NOH' +'PUNCH REDHAT PARM A (NOH' +'PUNCH INITRD IMG A (NOH' +'CH RDR ALL KEEP NOHOLD' +'I 00C' +</pre> </p> <p> @@ -60,9 +74,9 @@ files you got to your A minidisk. You can either use FTP, or IND$FILE through your 3270 terminal emulator. I used the IND$FILE method via c3270.<br/> <br/> -<b>Note:</b> The .img files should be transfered as binaries, and the other two -need to be converted to EBCDIC. Both, FTP and IND$FILE support converting -between ASCII and EBCDIC.<br/> +<b>Note:</b> The .img files should be transfered as binaries, and the other +two need to be converted to EBCDIC. Both, FTP and IND$FILE support +converting between ASCII and EBCDIC.<br/> <br/> I used the following commands in c3270 to do the transfers:<br/> @@ -86,10 +100,32 @@ this:<br/> <img src="zvm-centos4/install1.png" alt="CMS listing the files on A" /><br/> <br/> -The RHEL5.CONF file contains configuration options for the installer. +The RHEL5.CONF file contains configuration options for the installer. Here's +an example config file from the CentOS install docs: + <pre> -FIXME: example conf file +DASD=200 +HOSTNAME=client.z900.example.com +NETTYPE=ctc +IPADDR=192.168.0.10 +SUBCHANNELS=0.0.0150,0.0.0151 +NETWORK=192.168.0.0 +NETMASK=255.255.255.0 +SEARCHDNS=example.com:dns.example.com:z900.example.com +BROADCAST=192.168.0.255 +GATEWAY=192.168.0.1 +DNS=192.168.0.254 +MTU=1492 +CTCPROT=0 </pre> + +You will want to change the DASD to list all your DASDs that Linux should +bring online. The HOSTNAME, IPADDR, NETWORK, NETMASK, SEARCHDNS, BROADCAST, +GATEWAY, DNS, and MTU need to be changed to match your network config. And +chances are that you'll want to change NETTYPE to qeth, or something other +than ctc (possible values are: ctc, qeth, iucv, lcs). Go read the +<a href="http://www.centos.org/docs/4/4.5/rhel-ig-s390-multi-en-4/ch-parmfiles.html">CentOS documentation</a> +to figure out what are all the options you can use in the config file. </p> <p> @@ -100,7 +136,6 @@ </p> <p> -FIXME: do I need to IPL by hand?<br/> Shortly after, you'll see the kernel banner displayed. Since I installed CentOS 4.x, the kernel version is 2.6.9. If you use 5.x, the version will be obviously different.<br/> @@ -108,24 +143,19 @@ </p> <p> -After a few screen-fulls of output, you should be prompted for ... FIXME. -FIXME: Include a screenshot. -</p> - -<p> Some more scrolling later, you'll see a message prompting you to telnet or ssh into the system, and continue with the installation process:<br/> <img src="zvm-centos4/install5.png" alt="SSH/telnet prompt" /><br/> SSH or telnet in as root. The password is the empty string, so when -prompted, simply press the enter key.<br/> +prompted for it, simply press the enter key.<br/> <br/> At this point, the install process is much like network install on any other architecture. </p> <p> -The regular CentOS installer will kicks. It'll prompt you for the type of -install (http, ftp, nfs - FIXME: verify + image). I went with HTTP.<br/> +The regular CentOS installer will kick in. It'll prompt you for the type of +install (http, ftp, nfs). I went with HTTP.<br/> <br/> The next screen prompts you for the hostname and path on the HTTP server that contains the CentOS packages:<br/> @@ -135,13 +165,15 @@ </p> <p> -FIXME: partitions +Partition your DASDs whichever way you want. It's a good idea to use LVM, +since DASDs are limited to about 2.2GB (3338 cylinders). On my setup, I made +/home a logical volume of 5 3390-3 DASDs. </p> <p> Most of the questions the installer normally asks you get answered by the -options in the RHEL5.CONF file (FIXME: rename). And before long, you'll see -the install process doing its thing:<br/> +options in the RHEL5.CONF file. And before long, you'll see the install +process doing its thing:<br/> <img src="zvm-centos4/install9.png" alt="Install!" /> </p> @@ -151,8 +183,9 @@ <li> installing a 64-bit version should be the same process...just use the <i>s390x</i> directories on the mirror instead of <i>s390</i>.</li> - <li> installing RHEL 4.x should be the same process; just point the - installer at a server with RHEL4 RPMS.</li> + <li> installing RHEL 4.x should be the same process; just grab the + right kernel/initrd files, and then point the installer at a server + with RHEL4 RPMS.</li> </ul> </p>