Alpine Linux - User contributions [en]

S390x/Installation

2021-02-02T09:37:31Z

Tmhoang:

{{TOC right}}

= 1. Known Issues =
1. Installation on 2 or more DASDs (either ECKD and FBA) on z/VM is not supported in the installer script (<code>setup-alpine</code>) at the moment. If you want to install/extend on more than 1 DASD, see [https://wiki.alpinelinux.org/wiki/S390x#Extending_LVM_volume "Extending LVM volume"]. However, installation on 2 or more virtio (SCSI) disks on KVM are supported just like other architectures.

= 2. The boot media =

For KVM, both ISO image and netboot media (kernel and initramfs) are supported.

For z/VM, netboot media is supported.

For LPAR, netboot media is supported. See [https://wiki.alpinelinux.org/wiki/S390x/Installation/LPAR "LPAR"] for more information.

Boot media are found at:

* http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/s390x/

== Kernel parameters (and parmfile) ==
The Alpine s390x boot media requires following kernel parameters to work: (Details at : <code>https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt</code>)

<code>ip=dhcp</code> : use DHCP for network configuration.

<code>ip=client-ip:server-ip:gw-ip:netmask:hostname:device:autoconf:dns1:dns2</code> : use static IP configuration, each field is separated by a colon <code>:</code>
* <code>client-ip</code> ip address of the guest VM where we are going to run the installer
* <code>server-ip</code> not used, leave blank or fill with <code>none</code>
* <code>gw-ip</code> the gateway ip address
* <code>netmask</code> the netmask
* <code>hostname</code> not used, leave blank or fill with <code>none</code>
* <code>device</code> the network interface of the guest VM, default is <code>eth0</code> if left blank
* <code>autoconf</code> not used, leave blank or fill with <code>none</code> or <code>off</code>
* <code>dns1</code> address of the DNS server
* <code>dns2</code> address of the 2nd DNS server

<code>alpine_repo=</code> : the location of the Alpine repository from which packages are downloaded.

:For stable release, use <code>http://dl-cdn.alpinelinux.org/alpine/v3.10/main</code>

:For rolling release, use <code>http://dl-cdn.alpinelinux.org/alpine/edge/main</code>

<code>modloop=</code> : the remote location of the image containing kernel's modules, required for LVM and raid setup.

:The remote location of the <code>modloop</code> image is the same as the kernel and initramfs (see below).

<code>ssh_key=</code> : the remote location of your SSH public key which is used to allow SSH connection into the installer. It will be downloaded and copied into <code>/root/.ssh/authorized_keys</code> in the installer.

{{Note|Fetching public keys from HTTP, HTTPS and FTPS are supported. HTTP should only be used in local development network where you own the network.}}

{{Note|Alpine Linux security policies are against using passwords for root access via SSH as we consider using public-private key pairs is a much better approach.}}

'''z/VM only'''

<code>dasd=</code> : the addresses of the DASD devices, either ECKD or FBA DASDs. Each device is separated with a comma.

<code>s390x_net=</code> : the network interface type and its subchannels. At the moment, only QETH layer 2 is supported, thus the name <code>qeth_l2</code> is used (see below).

= 3. Pre-installation =

== KVM ==
Create a virtual disk:
$ qemu-img create alpine_disk.qcow2 5G

==== Using iso image ====
Download latest iso image from : http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/s390x

Start qemu:

$ qemu-system-s390x -M s390-ccw-virtio \
-m 1024 -smp 2 -nographic -enable-kvm \
-net nic -net tap,ifname=tap0,script=no \
-hda alpine_disk.qcow2 \
-boot d -cdrom alpine-standard-3.10.0-s390x.iso

==== Using netboot media ====
Download the latest [http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/s390x/netboot/vmlinuz-vanilla kernel] and [http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/s390x/netboot/initramfs-vanilla initramfs].

Start qemu: (modify <code>ip=</code> <code>alpine_repo=</code> <code>ssh_key=</code> for your needs)

$ qemu-system-s390x -M s390-ccw-virtio \
-m 1024 -smp 2 -nographic -enable-kvm \
-net nic -net tap,ifname=tap0,script=no \
-hda alpine_disk.qcow2 \
-kernel vmlinuz-vanilla \
-initrd initramfs-vanilla \
-append "ip=192.168.1.2::192.168.1.1:255.255.255.0::::8.8.8.8:1.1.1.1 alpine_repo=http://dl-cdn.alpinelinux.org/alpine/v3.10/main modloop=http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/s390x/netboot/modloop-vanilla ssh_key=https://your-website.com/your-ssh-key.pub"

{{Note|If you have direct access to the qemu console, <code>ssh_key</code> might not be required.}}

== z/VM ==
To ease out the process of downloading the images, punch the readers, ipl, etc., [https://github.com/trothr/znetboot '''ZNETBOOT'''] is used.

{{Note|Using a FTP server to host the images and download them from x3270 console also works - thus no need to use ZNETBOOT. }}

==== Create the parm file ====
On your workstation/laptop, create a file named <code>alpine.znetboot</code> in your home directory with contents below (modify <code>dasd=</code><code>s390x_net=</code> <code>ip=</code> <code>alpine_repo=</code> <code>ssh_key=</code> for your needs)

<pre>
ZNETBOOT_KERNEL=http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/s390x/netboot/vmlinuz-vanilla
ZNETBOOT_INITRD=http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/s390x/netboot/initramfs-vanilla
ZNETBOOT_PROGRESS=1M

alpine_repo=http://dl-cdn.alpinelinux.org/alpine/v3.10/main
modloop=http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/s390x/netboot/modloop-vanilla

dasd=0.0.04c0,0.0.05d1
s390x_net=qeth_l2,0.0.0560,0.0.0561,0.0.0562
ip=192.168.1.2::192.168.1.1:255.255.255.0::::8.8.8.8:1.1.1.1

ssh_key=https://your-website.com/your-ssh-key.pub

</pre>

==== Upload to z/VM system via 3270 client ====
[[File:X3270-1.png|right|300px|thumb|Figure 1.]]
On your workstation/laptop, download 2 files [https://raw.githubusercontent.com/trothr/znetboot/master/znetboot.exec <code>znetboot.exec</code>], and [https://raw.githubusercontent.com/trothr/znetboot/master/curl.rexx <code>curl.rexx</code>] to your home directory.

Open 3270 client and log in the z/VM system with your z/VM username and password.

Upload 3 files <code>alpine.znetboot</code>, <code>znetboot.exec</code>, <code>curl.rexx</code> to the z/VM environment using the 3270 client (this tutorial uses x3270). On the top left corner, click "File", then "File Transfer". (Figure 1.)

Do following steps : (Figure 2.) [[File:X3270-2.png|right|300px|thumb|Figure 2.]]
* On "Local File Name" box, enter '''alpine.znetboot''' (the file in your laptop/workstation, at '''~/alpine.znetboot''')
* On "Host File Name" box, enter '''alpine znetboot''' (the file will be in z/VM console)

{{Note|Beware the difference between '''the dot <code>.</code>''' and '''the space <code> </code>''' characters in the file names.}}

* Choose '''Send to host'''
* Choose '''Host is VM/CMS'''
* Choose either '''Fixed''' or '''Variable''' for '''Record Format'''
:Enter a number for LRECL and BLKSIZE, respectively
{{Note|Any line in '''alpine.znetboot''' that has more 80 chars (columns) will be splitted into more than 1 line when uploaded to z/VM (CMS) console via 3270. Count the number of characters/column of the longest line in your '''alpine.znetboot''' and fill it in LRECL. There is no restriction for BLKSIZE but 80 is preferred.}}

* Click '''Transfer File''' box

Repeat the same steps with <code>znetboot.exec</code> and <code>curl.rexx</code> files.

==== (Optional) Check the configuration files ====
On 3270 client, enter following commands to check if the configuration files are correctly transferred:

<code>xedit alpine znetboot</code>

<code>xedit znetboot exec</code>

<code>xedit curl rex</code>

or <code>filel</code> and put <code>xedit</code> on CMD column to edit respective file.

==== Start ZNETBOOT ====
On 3270 client, type below command and wait till Figure 3.: [[File:X3270-3.png|right|300px|thumb|Figure 3.]]

<code>znetboot alpine</code>

= 4. Installation =
If you install on z/VM, steps in this part does not involve the interaction with the 3270 client anymore. Everything is done in the terminal with SSH client.

If you install on KVM, you can either SSH into the installer (below) or directly use the console starting qemu.

Either installing in KVM or z/VM environments, from your workstation/laptop, you will be able to run:
$ ssh root@192.168.1.2 (change ip address to what you specified earlier)

Remaining steps are similar to installing Alpine on other architectures (x86, arm, ppc, etc.), either on KVM (using virtio/SCSI disks) or on z/VM with FBA DASDs. Installing on ECKD DASDs requires an additional step, as described below.

== Example ==
Below is the detailed walkthrough of installing Alpine on a single ECKD DASD using LVM and extend that LVM to the second ECKD DASD.

After SSH-ing into the Alpine installer, run:
# setup-alpine

<code>Select keyboard layout [none]:</code>
:press Enter for none

<code>Enter system hostname (short form, e.g. 'foo') [localhost]:</code>
:enter your hostname

<pre>
Available interfaces are: eth0.
Enter '?' for help on bridges, bonding and vlans.
Which one do you want to initialize? (or '?' or 'done') [eth0]:</pre>
:type 'eth0' or press Enter

<code>Ip address for eth0? (or 'dhcp', 'none', '?') [192.168.1.2]</code>
:enter ip address or 'dhcp'

<code>Netmask? [255.255.255.0]</code>
:enter netmask
<code>Gateway? (or 'none') [192.168.1.1]</code>
:enter gateway's ip address

<code>Do you want to do any manual network configuration? [no]</code>
:enter 'no' or press Enter

<code>DNS domain name? (e.g 'bar.com') []</code>
:enter domain name or press Enter for none

<code>DNS nameserver(s)? [8.8.8.8 ]</code>
:enter DNS nameserver

<code>Changing password for root</code>
:enter root password

<code>Which timezone are you in? ('?' for list) [UTC]</code>
:enter timezone or '?' for list of timezones

<code>HTTP/FTP proxy URL? (e.g. 'http://proxy:8080', or 'none') [none]</code>
:enter proxy or press Enter for none

<code>Enter mirror number (1-27) or URL to add (or r/f/e/done) [f]:</code>
:enter a number or 'r' or 'f' or 'e' or 'done' as described

<code>Which SSH server? ('openssh', 'dropbear' or 'none') [openssh]</code>
:enter SSH server or press Enter for openssh

<code>Which NTP client to run? ('busybox', 'openntpd', 'chrony' or 'none') [chrony]</code>
:enter 'busybox' or press Enter for chrony

''' (next step is the additional step for ECKD DASDs on z/VM)'''
<pre>
Available ECKD DASD(s) are:
0.0.04c0 (3390/0c 3990/e9 IBM)
0.0.05d1 (3390/0c 3990/e9 IBM)
Which ECKD DASD(s) would you like to be formatted using dasdfmt? (enter '?' for help) [all]</pre>
:enter 'all' or '0.0.04c0 0.0.05d1' '''(separated by a space)''' to format all/both DASDs
:enter '0.0.04c0' or '0.0.05d1' to format respective DASD
:enter '?' for help

<code>WARNING: Erase ECKD DASD 0.0.04c0? [y/N]:</code>
:enter 'y' to format

<pre>
Available disks are:
dasda (2.5 GB IBM 0.0.04c0)
Which disk(s) would you like to use? (or '?' for help or 'none') [dasda]</pre>
:enter 'dasda' or press Enter

<pre>
The following disk is selected:
dasda (2.5 GB IBM 0.0.04c0)
How would you like to use it? ('sys', 'data', 'lvm' or '?' for help) [?]</pre>
:enter 'lvm'

<pre>
The following disk is selected (with LVM):
dasda (2.5 GB IBM 0.0.04c0)
How would you like to use it? ('sys', 'data' or '?' for help) [?]</pre>
:enter 'sys' to install Alpine on disk

<pre>
WARNING: The following disk(s) will be erased:
dasda (2.5 GB IBM 0.0.04c0)
WARNING: Erase the above disk(s) and continue? [y/N]:</pre>
:enter 'y'

<code>Installation is complete. Please reboot.</code>
:the installation is finished

At this point, don't poweroff the installer right away. Go to [https://wiki.alpinelinux.org/wiki/S390x#Copying_SSH_keys_to_new_Alpine_system "Copying SSH keys to new Alpine system"] (below) to have SSH access to your new Alpine system.

== Copying SSH keys to new Alpine system ==

By default, Alpine disables root login with a password via SSH. SSH keys are used instead.

After the installer's done running (<code>Installation is complete. Please reboot.</code>), there are 2 ways to copy your SSH key into the new Alpine system:
* Option 1: mount the installed disk and copy the SSH keys while still at the installer's terminal
* Option 2: poweroff the installer, start the new Alpine system and directly add the SSH keys
::: if you install on KVM, boot the new Alpine system on qemu, and copy the SSH keys
::: if you install on z/VM, use the 3270 client to ipl the new Alpine system and copy the SSH keys

'''Option 1'''

If you use 'lvm' + 'sys' installation (like in above example), do:

:<code> # mount /dev/vg0/lv_root /mnt</code>

:<code> # cp -ar /root/.ssh /mnt/root</code>

If you use 'sys' (without LVM) installation, do:

:<code> # mount /dev/dasda3 /mnt</code> (change dasda to dasdb or dasdc, etc. for whichever DASD you chose)

:<code> # cp -ar /root/.ssh /mnt/root</code>

{{Note|In 'sys' installation, 1st partition is boot, 2nd partition is swap, 3rd partition is root }}

Then run <code> # poweroff</code>.

Go to [https://wiki.alpinelinux.org/wiki/S390x#Login_to_new_Alpine_system "Login to new Alpine system"]

'''Option 2'''

Run <code> # poweroff</code>.

If you use KVM, start qemu with new Alpine system (removing <code>-kernel</code>, <code>-initrd</code>, <code>-append</code> options)

If you use z/VM, open the 3270 client, login with your z/VM username and password. You may need to run <code> ipl cms</code>. Then run <code> ipl 04c0</code> (or whichever DASD device you chose as root disk in earlier steps).

Wait for new Alpine system go up, then login as root user while in the qemu console (on KVM) or 3270 client (on z/VM). Then run:
::<code> # mkdir /root/.ssh</code>
::<code> # wget https://your-website.com/your-ssh-key.pub -O /root/.ssh/authorized_keys</code>
::<code> # chmod 700 /root/.ssh</code>
::<code> # chmod 600 /root/.ssh/authorized_keys</code>

Go to [https://wiki.alpinelinux.org/wiki/S390x#Login_to_new_Alpine_system "Login to new Alpine system"]

== Login to new Alpine system ==
On your workstation/laptop, use SSH client to login new Alpine system:
<code> $ ssh root@192.168.1.2</code> (or whichever ip address you used)

== Extending LVM volume ==
After logging in to your new Alpine system, run:
<pre>
# apk add -q util-linux e2fsprogs-extra

# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
dasda 94:0 0 2.3G 0 disk
├─dasda1 94:1 0 100M 0 part /boot
└─dasda2 94:2 0 2.2G 0 part
├─vg0-lv_swap 254:0 0 588M 0 lvm [SWAP]
└─vg0-lv_root 254:1 0 1.6G 0 lvm /
dasdb 94:4 0 2.3G 0 disk

# dasdfmt -b 4096 -d cdl -yp /dev/dasdb

# fdasd -a /dev/dasdb

# pvcreate /dev/dasdb1

# vgextend vg0 /dev/dasdb1

# lvextend -l +100%FREE /dev/vg0/lv_root

# resize2fs /dev/vg0/lv_root

# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
dasda 94:0 0 2.3G 0 disk
├─dasda1 94:1 0 100M 0 part /boot
└─dasda2 94:2 0 2.2G 0 part
├─vg0-lv_swap 254:0 0 588M 0 lvm [SWAP]
└─vg0-lv_root 254:1 0 3.9G 0 lvm /
dasdb 94:4 0 2.3G 0 disk
└─dasdb1 94:5 0 2.3G 0 part
└─vg0-lv_root 254:1 0 3.9G 0 lvm /
</pre>

= 5. Tips =
If you want to disable swap partition, after finishing NTP client step, quit the installer by pressing <code>Ctrl + C</code>. Then run following command to complete remaining steps:

<code># setup-disk -s 0</code>

{{Note|If you do 'sys' installation, there will be no swap partition anymore and 1st partition will be boot, 2nd partition will be root}}

[[category:IBM]]

S390x/Installation

2021-02-02T09:36:56Z

Tmhoang:

{{TOC right}}

= 1. Known Issues =
1. Installation on 2 or more DASDs (either ECKD and FBA) on z/VM is not supported in the installer script (<code>setup-alpine</code>) at the moment. If you want to install/extend on more than 1 DASD, see [https://wiki.alpinelinux.org/wiki/S390x#Extending_LVM_volume "Extending LVM volume"]. However, installation on 2 or more virtio (SCSI) disks on KVM are supported just like other architectures.

= 2. The boot media =

For KVM, both ISO image and netboot media (kernel and initramfs) are supported.

For z/VM, netboot media is supported.

For LPAR, netboot media is supported. See [https://wiki.alpinelinux.org/wiki/S390x/Installation/LPAR "LPAR"] for more information.

Boot media are found at:

* http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/s390x/

== Kernel parameters (and parmfile) ==
The Alpine s390x boot media requires following kernel parameters to work: (Details at : <code>https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt</code>)

<code>ip=dhcp</code> : use DHCP for network configuration.

<code>ip=client-ip:server-ip:gw-ip:netmask:hostname:device:autoconf:dns1:dns2</code> : use static IP configuration, each field is separated by a colon <code>:</code>
* <code>client-ip</code> ip address of the guest VM where we are going to run the installer
* <code>server-ip</code> not used, leave blank or fill with <code>none</code>
* <code>gw-ip</code> the gateway ip address
* <code>netmask</code> the netmask
* <code>hostname</code> not used, leave blank or fill with <code>none</code>
* <code>device</code> the network interface of the guest VM, default is <code>eth0</code> if left blank
* <code>autoconf</code> not used, leave blank or fill with <code>none</code> or <code>off</code>
* <code>dns1</code> address of the DNS server
* <code>dns2</code> address of the 2nd DNS server

<code>alpine_repo=</code> : the location of the Alpine repository from which packages are downloaded.

:For stable release, use <code>http://dl-cdn.alpinelinux.org/alpine/v3.10/main</code>

:For rolling release, use <code>http://dl-cdn.alpinelinux.org/alpine/edge/main</code>

<code>modloop=</code> : the remote location of the image containing kernel's modules, required for LVM and raid setup.

:The remote location of the <code>modloop</code> image is the same as the kernel and initramfs (see below).

<code>ssh_key=</code> : the remote location of your SSH public key which is used to allow SSH connection into the installer. It will be downloaded and copied into <code>/root/.ssh/authorized_keys</code> in the installer.

{{Note|Fetching public keys from HTTP, HTTPS and FTPS are supported. HTTP should only be used in local development network where you own the network.}}

{{Note|Alpine Linux security policies are against using passwords for root access via SSH as we consider using public-private key pairs is a much better approach.}}

'''z/VM only'''

<code>dasd=</code> : the addresses of the DASD devices, either ECKD or FBA DASDs. Each device is separated with a comma.

<code>s390x_net=</code> : the network interface type and its subchannels. At the moment, only QETH layer 2 is supported, thus the name <code>qeth_l2</code> is used (see below).

= 3. Pre-installation =

== KVM ==
Create a virtual disk:
$ qemu-img create alpine_disk.qcow2 5G

==== Using iso image ====
Download latest iso image from : http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/s390x

Start qemu:

$ qemu-system-s390x -M s390-ccw-virtio \
-m 1024 -smp 2 -nographic -enable-kvm \
-net nic -net tap,ifname=tap0,script=no \
-hda alpine_disk.qcow2 \
-boot d -cdrom alpine-standard-3.10.0-s390x.iso

==== Using netboot media ====
Download the latest [http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/s390x/netboot/vmlinuz-vanilla kernel] and [http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/s390x/netboot/initramfs-vanilla initramfs].

Start qemu: (modify <code>ip=</code> <code>alpine_repo=</code> <code>ssh_key=</code> for your needs)

$ qemu-system-s390x -M s390-ccw-virtio \
-m 1024 -smp 2 -nographic -enable-kvm \
-net nic -net tap,ifname=tap0,script=no \
-hda alpine_disk.qcow2 \
-kernel vmlinuz-vanilla \
-initrd initramfs-vanilla \
-append "ip=192.168.1.2::192.168.1.1:255.255.255.0::::8.8.8.8:1.1.1.1 alpine_repo=http://dl-cdn.alpinelinux.org/alpine/v3.10/main modloop=http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/s390x/netboot/modloop-vanilla ssh_key=https://your-website.com/your-ssh-key.pub"

{{Note|If you have direct access to the qemu console, <code>ssh_key</code> might not be required.}}

== z/VM ==
To ease out the process of downloading the images, punch the readers, ipl, etc., [https://github.com/trothr/znetboot '''ZNETBOOT'''] is used.

{{Note|Using a FTP server to host the images and download them from x3270 console also works.}}

==== Create the parm file ====
On your workstation/laptop, create a file named <code>alpine.znetboot</code> in your home directory with contents below (modify <code>dasd=</code><code>s390x_net=</code> <code>ip=</code> <code>alpine_repo=</code> <code>ssh_key=</code> for your needs)

<pre>
ZNETBOOT_KERNEL=http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/s390x/netboot/vmlinuz-vanilla
ZNETBOOT_INITRD=http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/s390x/netboot/initramfs-vanilla
ZNETBOOT_PROGRESS=1M

alpine_repo=http://dl-cdn.alpinelinux.org/alpine/v3.10/main
modloop=http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/s390x/netboot/modloop-vanilla

dasd=0.0.04c0,0.0.05d1
s390x_net=qeth_l2,0.0.0560,0.0.0561,0.0.0562
ip=192.168.1.2::192.168.1.1:255.255.255.0::::8.8.8.8:1.1.1.1

ssh_key=https://your-website.com/your-ssh-key.pub

</pre>

==== Upload to z/VM system via 3270 client ====
[[File:X3270-1.png|right|300px|thumb|Figure 1.]]
On your workstation/laptop, download 2 files [https://raw.githubusercontent.com/trothr/znetboot/master/znetboot.exec <code>znetboot.exec</code>], and [https://raw.githubusercontent.com/trothr/znetboot/master/curl.rexx <code>curl.rexx</code>] to your home directory.

Open 3270 client and log in the z/VM system with your z/VM username and password.

Upload 3 files <code>alpine.znetboot</code>, <code>znetboot.exec</code>, <code>curl.rexx</code> to the z/VM environment using the 3270 client (this tutorial uses x3270). On the top left corner, click "File", then "File Transfer". (Figure 1.)

Do following steps : (Figure 2.) [[File:X3270-2.png|right|300px|thumb|Figure 2.]]
* On "Local File Name" box, enter '''alpine.znetboot''' (the file in your laptop/workstation, at '''~/alpine.znetboot''')
* On "Host File Name" box, enter '''alpine znetboot''' (the file will be in z/VM console)

{{Note|Beware the difference between '''the dot <code>.</code>''' and '''the space <code> </code>''' characters in the file names.}}

* Choose '''Send to host'''
* Choose '''Host is VM/CMS'''
* Choose either '''Fixed''' or '''Variable''' for '''Record Format'''
:Enter a number for LRECL and BLKSIZE, respectively
{{Note|Any line in '''alpine.znetboot''' that has more 80 chars (columns) will be splitted into more than 1 line when uploaded to z/VM (CMS) console via 3270. Count the number of characters/column of the longest line in your '''alpine.znetboot''' and fill it in LRECL. There is no restriction for BLKSIZE but 80 is preferred.}}

* Click '''Transfer File''' box

Repeat the same steps with <code>znetboot.exec</code> and <code>curl.rexx</code> files.

==== (Optional) Check the configuration files ====
On 3270 client, enter following commands to check if the configuration files are correctly transferred:

<code>xedit alpine znetboot</code>

<code>xedit znetboot exec</code>

<code>xedit curl rex</code>

or <code>filel</code> and put <code>xedit</code> on CMD column to edit respective file.

==== Start ZNETBOOT ====
On 3270 client, type below command and wait till Figure 3.: [[File:X3270-3.png|right|300px|thumb|Figure 3.]]

<code>znetboot alpine</code>

= 4. Installation =
If you install on z/VM, steps in this part does not involve the interaction with the 3270 client anymore. Everything is done in the terminal with SSH client.

If you install on KVM, you can either SSH into the installer (below) or directly use the console starting qemu.

Either installing in KVM or z/VM environments, from your workstation/laptop, you will be able to run:
$ ssh root@192.168.1.2 (change ip address to what you specified earlier)

Remaining steps are similar to installing Alpine on other architectures (x86, arm, ppc, etc.), either on KVM (using virtio/SCSI disks) or on z/VM with FBA DASDs. Installing on ECKD DASDs requires an additional step, as described below.

== Example ==
Below is the detailed walkthrough of installing Alpine on a single ECKD DASD using LVM and extend that LVM to the second ECKD DASD.

After SSH-ing into the Alpine installer, run:
# setup-alpine

<code>Select keyboard layout [none]:</code>
:press Enter for none

<code>Enter system hostname (short form, e.g. 'foo') [localhost]:</code>
:enter your hostname

<pre>
Available interfaces are: eth0.
Enter '?' for help on bridges, bonding and vlans.
Which one do you want to initialize? (or '?' or 'done') [eth0]:</pre>
:type 'eth0' or press Enter

<code>Ip address for eth0? (or 'dhcp', 'none', '?') [192.168.1.2]</code>
:enter ip address or 'dhcp'

<code>Netmask? [255.255.255.0]</code>
:enter netmask
<code>Gateway? (or 'none') [192.168.1.1]</code>
:enter gateway's ip address

<code>Do you want to do any manual network configuration? [no]</code>
:enter 'no' or press Enter

<code>DNS domain name? (e.g 'bar.com') []</code>
:enter domain name or press Enter for none

<code>DNS nameserver(s)? [8.8.8.8 ]</code>
:enter DNS nameserver

<code>Changing password for root</code>
:enter root password

<code>Which timezone are you in? ('?' for list) [UTC]</code>
:enter timezone or '?' for list of timezones

<code>HTTP/FTP proxy URL? (e.g. 'http://proxy:8080', or 'none') [none]</code>
:enter proxy or press Enter for none

<code>Enter mirror number (1-27) or URL to add (or r/f/e/done) [f]:</code>
:enter a number or 'r' or 'f' or 'e' or 'done' as described

<code>Which SSH server? ('openssh', 'dropbear' or 'none') [openssh]</code>
:enter SSH server or press Enter for openssh

<code>Which NTP client to run? ('busybox', 'openntpd', 'chrony' or 'none') [chrony]</code>
:enter 'busybox' or press Enter for chrony

''' (next step is the additional step for ECKD DASDs on z/VM)'''
<pre>
Available ECKD DASD(s) are:
0.0.04c0 (3390/0c 3990/e9 IBM)
0.0.05d1 (3390/0c 3990/e9 IBM)
Which ECKD DASD(s) would you like to be formatted using dasdfmt? (enter '?' for help) [all]</pre>
:enter 'all' or '0.0.04c0 0.0.05d1' '''(separated by a space)''' to format all/both DASDs
:enter '0.0.04c0' or '0.0.05d1' to format respective DASD
:enter '?' for help

<code>WARNING: Erase ECKD DASD 0.0.04c0? [y/N]:</code>
:enter 'y' to format

<pre>
Available disks are:
dasda (2.5 GB IBM 0.0.04c0)
Which disk(s) would you like to use? (or '?' for help or 'none') [dasda]</pre>
:enter 'dasda' or press Enter

<pre>
The following disk is selected:
dasda (2.5 GB IBM 0.0.04c0)
How would you like to use it? ('sys', 'data', 'lvm' or '?' for help) [?]</pre>
:enter 'lvm'

<pre>
The following disk is selected (with LVM):
dasda (2.5 GB IBM 0.0.04c0)
How would you like to use it? ('sys', 'data' or '?' for help) [?]</pre>
:enter 'sys' to install Alpine on disk

<pre>
WARNING: The following disk(s) will be erased:
dasda (2.5 GB IBM 0.0.04c0)
WARNING: Erase the above disk(s) and continue? [y/N]:</pre>
:enter 'y'

<code>Installation is complete. Please reboot.</code>
:the installation is finished

At this point, don't poweroff the installer right away. Go to [https://wiki.alpinelinux.org/wiki/S390x#Copying_SSH_keys_to_new_Alpine_system "Copying SSH keys to new Alpine system"] (below) to have SSH access to your new Alpine system.

== Copying SSH keys to new Alpine system ==

By default, Alpine disables root login with a password via SSH. SSH keys are used instead.

After the installer's done running (<code>Installation is complete. Please reboot.</code>), there are 2 ways to copy your SSH key into the new Alpine system:
* Option 1: mount the installed disk and copy the SSH keys while still at the installer's terminal
* Option 2: poweroff the installer, start the new Alpine system and directly add the SSH keys
::: if you install on KVM, boot the new Alpine system on qemu, and copy the SSH keys
::: if you install on z/VM, use the 3270 client to ipl the new Alpine system and copy the SSH keys

'''Option 1'''

If you use 'lvm' + 'sys' installation (like in above example), do:

:<code> # mount /dev/vg0/lv_root /mnt</code>

:<code> # cp -ar /root/.ssh /mnt/root</code>

If you use 'sys' (without LVM) installation, do:

:<code> # mount /dev/dasda3 /mnt</code> (change dasda to dasdb or dasdc, etc. for whichever DASD you chose)

:<code> # cp -ar /root/.ssh /mnt/root</code>

{{Note|In 'sys' installation, 1st partition is boot, 2nd partition is swap, 3rd partition is root }}

Then run <code> # poweroff</code>.

Go to [https://wiki.alpinelinux.org/wiki/S390x#Login_to_new_Alpine_system "Login to new Alpine system"]

'''Option 2'''

Run <code> # poweroff</code>.

If you use KVM, start qemu with new Alpine system (removing <code>-kernel</code>, <code>-initrd</code>, <code>-append</code> options)

If you use z/VM, open the 3270 client, login with your z/VM username and password. You may need to run <code> ipl cms</code>. Then run <code> ipl 04c0</code> (or whichever DASD device you chose as root disk in earlier steps).

Wait for new Alpine system go up, then login as root user while in the qemu console (on KVM) or 3270 client (on z/VM). Then run:
::<code> # mkdir /root/.ssh</code>
::<code> # wget https://your-website.com/your-ssh-key.pub -O /root/.ssh/authorized_keys</code>
::<code> # chmod 700 /root/.ssh</code>
::<code> # chmod 600 /root/.ssh/authorized_keys</code>

Go to [https://wiki.alpinelinux.org/wiki/S390x#Login_to_new_Alpine_system "Login to new Alpine system"]

== Login to new Alpine system ==
On your workstation/laptop, use SSH client to login new Alpine system:
<code> $ ssh root@192.168.1.2</code> (or whichever ip address you used)

== Extending LVM volume ==
After logging in to your new Alpine system, run:
<pre>
# apk add -q util-linux e2fsprogs-extra

# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
dasda 94:0 0 2.3G 0 disk
├─dasda1 94:1 0 100M 0 part /boot
└─dasda2 94:2 0 2.2G 0 part
├─vg0-lv_swap 254:0 0 588M 0 lvm [SWAP]
└─vg0-lv_root 254:1 0 1.6G 0 lvm /
dasdb 94:4 0 2.3G 0 disk

# dasdfmt -b 4096 -d cdl -yp /dev/dasdb

# fdasd -a /dev/dasdb

# pvcreate /dev/dasdb1

# vgextend vg0 /dev/dasdb1

# lvextend -l +100%FREE /dev/vg0/lv_root

# resize2fs /dev/vg0/lv_root

# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
dasda 94:0 0 2.3G 0 disk
├─dasda1 94:1 0 100M 0 part /boot
└─dasda2 94:2 0 2.2G 0 part
├─vg0-lv_swap 254:0 0 588M 0 lvm [SWAP]
└─vg0-lv_root 254:1 0 3.9G 0 lvm /
dasdb 94:4 0 2.3G 0 disk
└─dasdb1 94:5 0 2.3G 0 part
└─vg0-lv_root 254:1 0 3.9G 0 lvm /
</pre>

= 5. Tips =
If you want to disable swap partition, after finishing NTP client step, quit the installer by pressing <code>Ctrl + C</code>. Then run following command to complete remaining steps:

<code># setup-disk -s 0</code>

{{Note|If you do 'sys' installation, there will be no swap partition anymore and 1st partition will be boot, 2nd partition will be root}}

[[category:IBM]]

S390x/Installation

2021-02-02T09:33:25Z

Tmhoang:

{{TOC right}}

= 1. Known Issues =
1. Installation on 2 or more DASDs (either ECKD and FBA) on z/VM is not supported in the installer script (<code>setup-alpine</code>) at the moment. If you want to install/extend on more than 1 DASD, see [https://wiki.alpinelinux.org/wiki/S390x#Extending_LVM_volume "Extending LVM volume"]. However, installation on 2 or more virtio (SCSI) disks on KVM are supported just like other architectures.

= 2. The boot media =

For KVM, both ISO image and netboot media (kernel and initramfs) are supported.

For z/VM, netboot media is supported.

For LPAR, netboot media is supported. See [https://wiki.alpinelinux.org/wiki/S390x/Installation/LPAR "LPAR"] for more information.

Boot media are found at:

* http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/s390x/

== Kernel parameters (and parmfile) ==
The Alpine s390x boot media requires following kernel parameters to work: (Details at : <code>https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt</code>)

<code>ip=dhcp</code> : use DHCP for network configuration.

<code>ip=client-ip:server-ip:gw-ip:netmask:hostname:device:autoconf:dns1:dns2</code> : use static IP configuration, each field is separated by a colon <code>:</code>
* <code>client-ip</code> ip address of the guest VM where we are going to run the installer
* <code>server-ip</code> not used, leave blank or fill with <code>none</code>
* <code>gw-ip</code> the gateway ip address
* <code>netmask</code> the netmask
* <code>hostname</code> not used, leave blank or fill with <code>none</code>
* <code>device</code> the network interface of the guest VM, default is <code>eth0</code> if left blank
* <code>autoconf</code> not used, leave blank or fill with <code>none</code> or <code>off</code>
* <code>dns1</code> address of the DNS server
* <code>dns2</code> address of the 2nd DNS server

<code>alpine_repo=</code> : the location of the Alpine repository from which packages are downloaded.

:For stable release, use <code>http://dl-cdn.alpinelinux.org/alpine/v3.10/main</code>

:For rolling release, use <code>http://dl-cdn.alpinelinux.org/alpine/edge/main</code>

<code>modloop=</code> : the remote location of the image containing kernel's modules, required for LVM and raid setup.

:The remote location of the <code>modloop</code> image is the same as the kernel and initramfs (see below).

<code>ssh_key=</code> : the remote location of your SSH public key which is used to allow SSH connection into the installer. It will be downloaded and copied into <code>/root/.ssh/authorized_keys</code> in the installer.

{{Note|Fetching public keys from HTTP, HTTPS and FTPS are supported. HTTP should only be used in local development network where you own the network.}}

{{Note|Alpine Linux security policies are against using passwords for root access via SSH as we consider using public-private key pairs is a much better approach.}}

'''z/VM only'''

<code>dasd=</code> : the addresses of the DASD devices, either ECKD or FBA DASDs. Each device is separated with a comma.

<code>s390x_net=</code> : the network interface type and its subchannels. At the moment, only QETH layer 2 is supported, thus the name <code>qeth_l2</code> is used (see below).

= 3. Pre-installation =

== KVM ==
Create a virtual disk:
$ qemu-img create alpine_disk.qcow2 5G

==== Using iso image ====
Download latest iso image from : http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/s390x

Start qemu:

$ qemu-system-s390x -M s390-ccw-virtio \
-m 1024 -smp 2 -nographic -enable-kvm \
-net nic -net tap,ifname=tap0,script=no \
-hda alpine_disk.qcow2 \
-boot d -cdrom alpine-standard-3.10.0-s390x.iso

==== Using netboot media ====
Download the latest [http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/s390x/netboot/vmlinuz-vanilla kernel] and [http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/s390x/netboot/initramfs-vanilla initramfs].

Start qemu: (modify <code>ip=</code> <code>alpine_repo=</code> <code>ssh_key=</code> for your needs)

$ qemu-system-s390x -M s390-ccw-virtio \
-m 1024 -smp 2 -nographic -enable-kvm \
-net nic -net tap,ifname=tap0,script=no \
-hda alpine_disk.qcow2 \
-kernel vmlinuz-vanilla \
-initrd initramfs-vanilla \
-append "ip=192.168.1.2::192.168.1.1:255.255.255.0::::8.8.8.8:1.1.1.1 alpine_repo=http://dl-cdn.alpinelinux.org/alpine/v3.10/main modloop=http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/s390x/netboot/modloop-vanilla ssh_key=https://your-website.com/your-ssh-key.pub"

{{Note|If you have direct access to the qemu console, <code>ssh_key</code> might not be required.}}

== z/VM ==
To ease out the process of downloading the images, punch the readers, ipl, etc., [https://github.com/trothr/znetboot '''ZNETBOOT'''] is used. '''Using a FTP server to host the images and download them from x3270 console also works.'''

==== Create the parm file ====
On your workstation/laptop, create a file named <code>alpine.znetboot</code> in your home directory with contents below (modify <code>dasd=</code><code>s390x_net=</code> <code>ip=</code> <code>alpine_repo=</code> <code>ssh_key=</code> for your needs)

<pre>
ZNETBOOT_KERNEL=http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/s390x/netboot/vmlinuz-vanilla
ZNETBOOT_INITRD=http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/s390x/netboot/initramfs-vanilla
ZNETBOOT_PROGRESS=1M

alpine_repo=http://dl-cdn.alpinelinux.org/alpine/v3.10/main
modloop=http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/s390x/netboot/modloop-vanilla

dasd=0.0.04c0,0.0.05d1
s390x_net=qeth_l2,0.0.0560,0.0.0561,0.0.0562
ip=192.168.1.2::192.168.1.1:255.255.255.0::::8.8.8.8:1.1.1.1

ssh_key=https://your-website.com/your-ssh-key.pub

</pre>

==== Upload to z/VM system via 3270 client ====
[[File:X3270-1.png|right|300px|thumb|Figure 1.]]
On your workstation/laptop, download 2 files [https://raw.githubusercontent.com/trothr/znetboot/master/znetboot.exec <code>znetboot.exec</code>], and [https://raw.githubusercontent.com/trothr/znetboot/master/curl.rexx <code>curl.rexx</code>] to your home directory.

Open 3270 client and log in the z/VM system with your z/VM username and password.

Upload 3 files <code>alpine.znetboot</code>, <code>znetboot.exec</code>, <code>curl.rexx</code> to the z/VM environment using the 3270 client (this tutorial uses x3270). On the top left corner, click "File", then "File Transfer". (Figure 1.)

Do following steps : (Figure 2.) [[File:X3270-2.png|right|300px|thumb|Figure 2.]]
* On "Local File Name" box, enter '''alpine.znetboot''' (the file in your laptop/workstation, at '''~/alpine.znetboot''')
* On "Host File Name" box, enter '''alpine znetboot''' (the file will be in z/VM console)

{{Note|Beware the difference between '''the dot <code>.</code>''' and '''the space <code> </code>''' characters in the file names.}}

* Choose '''Send to host'''
* Choose '''Host is VM/CMS'''
* Choose either '''Fixed''' or '''Variable''' for '''Record Format'''
:Enter a number for LRECL and BLKSIZE, respectively
{{Note|Any line in '''alpine.znetboot''' that has more 80 chars (columns) will be splitted into more than 1 line when uploaded to z/VM (CMS) console via 3270. Count the number of characters/column of the longest line in your '''alpine.znetboot''' and fill it in LRECL. There is no restriction for BLKSIZE but 80 is preferred.}}

* Click '''Transfer File''' box

Repeat the same steps with <code>znetboot.exec</code> and <code>curl.rexx</code> files.

==== (Optional) Check the configuration files ====
On 3270 client, enter following commands to check if the configuration files are correctly transferred:

<code>xedit alpine znetboot</code>

<code>xedit znetboot exec</code>

<code>xedit curl rex</code>

or <code>filel</code> and put <code>xedit</code> on CMD column to edit respective file.

==== Start ZNETBOOT ====
On 3270 client, type below command and wait till Figure 3.: [[File:X3270-3.png|right|300px|thumb|Figure 3.]]

<code>znetboot alpine</code>

= 4. Installation =
If you install on z/VM, steps in this part does not involve the interaction with the 3270 client anymore. Everything is done in the terminal with SSH client.

If you install on KVM, you can either SSH into the installer (below) or directly use the console starting qemu.

Either installing in KVM or z/VM environments, from your workstation/laptop, you will be able to run:
$ ssh root@192.168.1.2 (change ip address to what you specified earlier)

Remaining steps are similar to installing Alpine on other architectures (x86, arm, ppc, etc.), either on KVM (using virtio/SCSI disks) or on z/VM with FBA DASDs. Installing on ECKD DASDs requires an additional step, as described below.

== Example ==
Below is the detailed walkthrough of installing Alpine on a single ECKD DASD using LVM and extend that LVM to the second ECKD DASD.

After SSH-ing into the Alpine installer, run:
# setup-alpine

<code>Select keyboard layout [none]:</code>
:press Enter for none

<code>Enter system hostname (short form, e.g. 'foo') [localhost]:</code>
:enter your hostname

<pre>
Available interfaces are: eth0.
Enter '?' for help on bridges, bonding and vlans.
Which one do you want to initialize? (or '?' or 'done') [eth0]:</pre>
:type 'eth0' or press Enter

<code>Ip address for eth0? (or 'dhcp', 'none', '?') [192.168.1.2]</code>
:enter ip address or 'dhcp'

<code>Netmask? [255.255.255.0]</code>
:enter netmask
<code>Gateway? (or 'none') [192.168.1.1]</code>
:enter gateway's ip address

<code>Do you want to do any manual network configuration? [no]</code>
:enter 'no' or press Enter

<code>DNS domain name? (e.g 'bar.com') []</code>
:enter domain name or press Enter for none

<code>DNS nameserver(s)? [8.8.8.8 ]</code>
:enter DNS nameserver

<code>Changing password for root</code>
:enter root password

<code>Which timezone are you in? ('?' for list) [UTC]</code>
:enter timezone or '?' for list of timezones

<code>HTTP/FTP proxy URL? (e.g. 'http://proxy:8080', or 'none') [none]</code>
:enter proxy or press Enter for none

<code>Enter mirror number (1-27) or URL to add (or r/f/e/done) [f]:</code>
:enter a number or 'r' or 'f' or 'e' or 'done' as described

<code>Which SSH server? ('openssh', 'dropbear' or 'none') [openssh]</code>
:enter SSH server or press Enter for openssh

<code>Which NTP client to run? ('busybox', 'openntpd', 'chrony' or 'none') [chrony]</code>
:enter 'busybox' or press Enter for chrony

''' (next step is the additional step for ECKD DASDs on z/VM)'''
<pre>
Available ECKD DASD(s) are:
0.0.04c0 (3390/0c 3990/e9 IBM)
0.0.05d1 (3390/0c 3990/e9 IBM)
Which ECKD DASD(s) would you like to be formatted using dasdfmt? (enter '?' for help) [all]</pre>
:enter 'all' or '0.0.04c0 0.0.05d1' '''(separated by a space)''' to format all/both DASDs
:enter '0.0.04c0' or '0.0.05d1' to format respective DASD
:enter '?' for help

<code>WARNING: Erase ECKD DASD 0.0.04c0? [y/N]:</code>
:enter 'y' to format

<pre>
Available disks are:
dasda (2.5 GB IBM 0.0.04c0)
Which disk(s) would you like to use? (or '?' for help or 'none') [dasda]</pre>
:enter 'dasda' or press Enter

<pre>
The following disk is selected:
dasda (2.5 GB IBM 0.0.04c0)
How would you like to use it? ('sys', 'data', 'lvm' or '?' for help) [?]</pre>
:enter 'lvm'

<pre>
The following disk is selected (with LVM):
dasda (2.5 GB IBM 0.0.04c0)
How would you like to use it? ('sys', 'data' or '?' for help) [?]</pre>
:enter 'sys' to install Alpine on disk

<pre>
WARNING: The following disk(s) will be erased:
dasda (2.5 GB IBM 0.0.04c0)
WARNING: Erase the above disk(s) and continue? [y/N]:</pre>
:enter 'y'

<code>Installation is complete. Please reboot.</code>
:the installation is finished

At this point, don't poweroff the installer right away. Go to [https://wiki.alpinelinux.org/wiki/S390x#Copying_SSH_keys_to_new_Alpine_system "Copying SSH keys to new Alpine system"] (below) to have SSH access to your new Alpine system.

== Copying SSH keys to new Alpine system ==

By default, Alpine disables root login with a password via SSH. SSH keys are used instead.

After the installer's done running (<code>Installation is complete. Please reboot.</code>), there are 2 ways to copy your SSH key into the new Alpine system:
* Option 1: mount the installed disk and copy the SSH keys while still at the installer's terminal
* Option 2: poweroff the installer, start the new Alpine system and directly add the SSH keys
::: if you install on KVM, boot the new Alpine system on qemu, and copy the SSH keys
::: if you install on z/VM, use the 3270 client to ipl the new Alpine system and copy the SSH keys

'''Option 1'''

If you use 'lvm' + 'sys' installation (like in above example), do:

:<code> # mount /dev/vg0/lv_root /mnt</code>

:<code> # cp -ar /root/.ssh /mnt/root</code>

If you use 'sys' (without LVM) installation, do:

:<code> # mount /dev/dasda3 /mnt</code> (change dasda to dasdb or dasdc, etc. for whichever DASD you chose)

:<code> # cp -ar /root/.ssh /mnt/root</code>

{{Note|In 'sys' installation, 1st partition is boot, 2nd partition is swap, 3rd partition is root }}

Then run <code> # poweroff</code>.

Go to [https://wiki.alpinelinux.org/wiki/S390x#Login_to_new_Alpine_system "Login to new Alpine system"]

'''Option 2'''

Run <code> # poweroff</code>.

If you use KVM, start qemu with new Alpine system (removing <code>-kernel</code>, <code>-initrd</code>, <code>-append</code> options)

If you use z/VM, open the 3270 client, login with your z/VM username and password. You may need to run <code> ipl cms</code>. Then run <code> ipl 04c0</code> (or whichever DASD device you chose as root disk in earlier steps).

Wait for new Alpine system go up, then login as root user while in the qemu console (on KVM) or 3270 client (on z/VM). Then run:
::<code> # mkdir /root/.ssh</code>
::<code> # wget https://your-website.com/your-ssh-key.pub -O /root/.ssh/authorized_keys</code>
::<code> # chmod 700 /root/.ssh</code>
::<code> # chmod 600 /root/.ssh/authorized_keys</code>

Go to [https://wiki.alpinelinux.org/wiki/S390x#Login_to_new_Alpine_system "Login to new Alpine system"]

== Login to new Alpine system ==
On your workstation/laptop, use SSH client to login new Alpine system:
<code> $ ssh root@192.168.1.2</code> (or whichever ip address you used)

== Extending LVM volume ==
After logging in to your new Alpine system, run:
<pre>
# apk add -q util-linux e2fsprogs-extra

# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
dasda 94:0 0 2.3G 0 disk
├─dasda1 94:1 0 100M 0 part /boot
└─dasda2 94:2 0 2.2G 0 part
├─vg0-lv_swap 254:0 0 588M 0 lvm [SWAP]
└─vg0-lv_root 254:1 0 1.6G 0 lvm /
dasdb 94:4 0 2.3G 0 disk

# dasdfmt -b 4096 -d cdl -yp /dev/dasdb

# fdasd -a /dev/dasdb

# pvcreate /dev/dasdb1

# vgextend vg0 /dev/dasdb1

# lvextend -l +100%FREE /dev/vg0/lv_root

# resize2fs /dev/vg0/lv_root

# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
dasda 94:0 0 2.3G 0 disk
├─dasda1 94:1 0 100M 0 part /boot
└─dasda2 94:2 0 2.2G 0 part
├─vg0-lv_swap 254:0 0 588M 0 lvm [SWAP]
└─vg0-lv_root 254:1 0 3.9G 0 lvm /
dasdb 94:4 0 2.3G 0 disk
└─dasdb1 94:5 0 2.3G 0 part
└─vg0-lv_root 254:1 0 3.9G 0 lvm /
</pre>

= 5. Tips =
If you want to disable swap partition, after finishing NTP client step, quit the installer by pressing <code>Ctrl + C</code>. Then run following command to complete remaining steps:

<code># setup-disk -s 0</code>

{{Note|If you do 'sys' installation, there will be no swap partition anymore and 1st partition will be boot, 2nd partition will be root}}

[[category:IBM]]

S390x/Installation

2019-07-03T12:11:29Z

Tmhoang:

= 1. Known Issues =
1. Installation on 2 or more DASDs (either ECKD and FBA) on z/VM is not supported in the installer script (<code>setup-alpine</code>) at the moment. If you want to install/extend on more than 1 DASD, see [https://wiki.alpinelinux.org/wiki/S390x#Extending_LVM_volume "Extending LVM volume"]. However, installation on 2 or more virtio (SCSI) disks on KVM are supported just like other architectures.

= 2. The boot media =

For KVM, both ISO image and netboot media (kernel and initramfs) are supported.

For z/VM, netboot media is supported.

For LPAR, netboot media is supported. See [https://wiki.alpinelinux.org/wiki/S390x/Installation/LPAR "LPAR"] for more information.

Boot media are found at:

* http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/s390x/

== Kernel parameters (and parmfile) ==
The Alpine s390x boot media requires following kernel parameters to work: (Details at : <code>https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt</code>)

<code>ip=dhcp</code> : use DHCP for network configuration.

<code>ip=client-ip:server-ip:gw-ip:netmask:hostname:device:autoconf:dns1:dns2</code> : use static IP configuration, each field is separated by a colon <code>:</code>
* <code>client-ip</code> ip address of the guest VM where we are going to run the installer
* <code>server-ip</code> not used, leave blank or fill with <code>none</code>
* <code>gw-ip</code> the gateway ip address
* <code>netmask</code> the netmask
* <code>hostname</code> not used, leave blank or fill with <code>none</code>
* <code>device</code> the network interface of the guest VM, default is <code>eth0</code> if left blank
* <code>autoconf</code> not used, leave blank or fill with <code>none</code> or <code>off</code>
* <code>dns1</code> address of the DNS server
* <code>dns2</code> address of the 2nd DNS server

<code>alpine_repo=</code> : the location of the Alpine repository from which packages are downloaded.

:For stable release, use <code>http://dl-cdn.alpinelinux.org/alpine/v3.10/main</code>

:For rolling release, use <code>http://dl-cdn.alpinelinux.org/alpine/edge/main</code>

<code>modloop=</code> : the remote location of the image containing kernel's modules, required for LVM and raid setup.

:The remote location of the <code>modloop</code> image is the same as the kernel and initramfs (see below).

<code>ssh_key=</code> : the remote location of your SSH public key which is used to allow SSH connection into the installer. It will be downloaded and copied into <code>/root/.ssh/authorized_keys</code> in the installer.

{{Note|Fetching public keys from HTTP, HTTPS and FTPS are supported. HTTP should only be used in local development network where you own the network.}}

{{Note|Alpine Linux security policies are against using passwords for root access via SSH as we consider using public-private key pairs is a much better approach.}}

'''z/VM only'''

<code>dasd=</code> : the addresses of the DASD devices, either ECKD or FBA DASDs. Each device is separated with a comma.

<code>s390x_net=</code> : the network interface type and its subchannels. At the moment, only QETH layer 2 is supported, thus the name <code>qeth_l2</code> is used (see below).

= 3. Pre-installation =

== KVM ==
Create a virtual disk:
$ qemu-img create alpine_disk.qcow2 5G

==== Using iso image ====
Download latest iso image from : http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/s390x

Start qemu:

$ qemu-system-s390x -M s390-ccw-virtio \
-m 1024 -smp 2 -nographic -enable-kvm \
-net nic -net tap,ifname=tap0,script=no \
-hda alpine_disk.qcow2 \
-boot d -cdrom alpine-standard-3.10.0-s390x.iso

==== Using netboot media ====
Download the latest [http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/s390x/netboot/vmlinuz-vanilla kernel] and [http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/s390x/netboot/initramfs-vanilla initramfs].

Start qemu: (modify <code>ip=</code> <code>alpine_repo=</code> <code>ssh_key=</code> for your needs)

$ qemu-system-s390x -M s390-ccw-virtio \
-m 1024 -smp 2 -nographic -enable-kvm \
-net nic -net tap,ifname=tap0,script=no \
-hda alpine_disk.qcow2 \
-kernel vmlinuz-vanilla \
-initrd initramfs-vanilla \
-append "ip=192.168.1.2::192.168.1.1:255.255.255.0::::8.8.8.8:1.1.1.1 alpine_repo=http://dl-cdn.alpinelinux.org/alpine/v3.10/main modloop=http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/s390x/netboot/modloop-vanilla ssh_key=https://your-website.com/your-ssh-key.pub"

{{Note|If you have direct access to the qemu console, <code>ssh_key</code> might not be required.}}

== z/VM ==
To ease out the process of downloading the images, punch the readers, ipl, etc., [https://github.com/trothr/znetboot '''ZNETBOOT'''] is used.

==== Create the parm file ====
On your workstation/laptop, create a file named <code>alpine.znetboot</code> in your home directory with contents below (modify <code>dasd=</code><code>s390x_net=</code> <code>ip=</code> <code>alpine_repo=</code> <code>ssh_key=</code> for your needs)

<pre>
ZNETBOOT_KERNEL=http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/s390x/netboot/vmlinuz-vanilla
ZNETBOOT_INITRD=http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/s390x/netboot/initramfs-vanilla
ZNETBOOT_PROGRESS=1M

alpine_repo=http://dl-cdn.alpinelinux.org/alpine/v3.10/main
modloop=http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/s390x/netboot/modloop-vanilla

dasd=0.0.04c0,0.0.05d1
s390x_net=qeth_l2,0.0.0560,0.0.0561,0.0.0562
ip=192.168.1.2::192.168.1.1:255.255.255.0::::8.8.8.8:1.1.1.1

ssh_key=https://your-website.com/your-ssh-key.pub

</pre>

==== Upload to z/VM system via 3270 client ====
[[File:X3270-1.png|right|300px|thumb|Figure 1.]]
On your workstation/laptop, download 2 files [https://raw.githubusercontent.com/trothr/znetboot/master/znetboot.exec <code>znetboot.exec</code>], and [https://raw.githubusercontent.com/trothr/znetboot/master/curl.rexx <code>curl.rexx</code>] to your home directory.

Open 3270 client and log in the z/VM system with your z/VM username and password.

Upload 3 files <code>alpine.znetboot</code>, <code>znetboot.exec</code>, <code>curl.rexx</code> to the z/VM environment using the 3270 client (this tutorial uses x3270). On the top left corner, click "File", then "File Transfer". (Figure 1.)

Do following steps : (Figure 2.) [[File:X3270-2.png|right|300px|thumb|Figure 2.]]
* On "Local File Name" box, enter '''alpine.znetboot''' (the file in your laptop/workstation, at '''~/alpine.znetboot''')
* On "Host File Name" box, enter '''alpine znetboot''' (the file will be in z/VM console)

{{Note|Beware the difference between '''the dot <code>.</code>''' and '''the space <code> </code>''' characters in the file names.}}

* Choose '''Send to host'''
* Choose '''Host is VM/CMS'''
* Choose either '''Fixed''' or '''Variable''' for '''Record Format'''
:Enter a number for LRECL and BLKSIZE, respectively
{{Note|Any line in '''alpine.znetboot''' that has more 80 chars (columns) will be splitted into more than 1 line when uploaded to z/VM (CMS) console via 3270. Count the number of characters/column of the longest line in your '''alpine.znetboot''' and fill it in LRECL. There is no restriction for BLKSIZE but 80 is preferred.}}

* Click '''Transfer File''' box

Repeat the same steps with <code>znetboot.exec</code> and <code>curl.rexx</code> files.

==== (Optional) Check the configuration files ====
On 3270 client, enter following commands to check if the configuration files are correctly transferred:

<code>xedit alpine znetboot</code>

<code>xedit znetboot exec</code>

<code>xedit curl rex</code>

or <code>filel</code> and put <code>xedit</code> on CMD column to edit respective file.

==== Start ZNETBOOT ====
On 3270 client, type below command and wait till Figure 3.: [[File:X3270-3.png|right|300px|thumb|Figure 3.]]

<code>znetboot alpine</code>

= 4. Installation =
If you install on z/VM, steps in this part does not involve the interaction with the 3270 client anymore. Everything is done in the terminal with SSH client.

If you install on KVM, you can either SSH into the installer (below) or directly use the console starting qemu.

Either installing in KVM or z/VM environments, from your workstation/laptop, you will be able to run:
$ ssh root@192.168.1.2 (change ip address to what you specified earlier)

Remaining steps are similar to installing Alpine on other architectures (x86, arm, ppc, etc.), either on KVM (using virtio/SCSI disks) or on z/VM with FBA DASDs. Installing on ECKD DASDs requires an additional step, as described below.

== Example ==
Below is the detailed walkthrough of installing Alpine on a single ECKD DASD using LVM and extend that LVM to the second ECKD DASD.

After SSH-ing into the Alpine installer, run:
# setup-alpine

<code>Select keyboard layout [none]:</code>
:press Enter for none

<code>Enter system hostname (short form, e.g. 'foo') [localhost]:</code>
:enter your hostname

<pre>
Available interfaces are: eth0.
Enter '?' for help on bridges, bonding and vlans.
Which one do you want to initialize? (or '?' or 'done') [eth0]:</pre>
:type 'eth0' or press Enter

<code>Ip address for eth0? (or 'dhcp', 'none', '?') [192.168.1.2]</code>
:enter ip address or 'dhcp'

<code>Netmask? [255.255.255.0]</code>
:enter netmask
<code>Gateway? (or 'none') [192.168.1.1]</code>
:enter gateway's ip address

<code>Do you want to do any manual network configuration? [no]</code>
:enter 'no' or press Enter

<code>DNS domain name? (e.g 'bar.com') []</code>
:enter domain name or press Enter for none

<code>DNS nameserver(s)? [8.8.8.8 ]</code>
:enter DNS nameserver

<code>Changing password for root</code>
:enter root password

<code>Which timezone are you in? ('?' for list) [UTC]</code>
:enter timezone or '?' for list of timezones

<code>HTTP/FTP proxy URL? (e.g. 'http://proxy:8080', or 'none') [none]</code>
:enter proxy or press Enter for none

<code>Enter mirror number (1-27) or URL to add (or r/f/e/done) [f]:</code>
:enter a number or 'r' or 'f' or 'e' or 'done' as described

<code>Which SSH server? ('openssh', 'dropbear' or 'none') [openssh]</code>
:enter SSH server or press Enter for openssh

<code>Which NTP client to run? ('busybox', 'openntpd', 'chrony' or 'none') [chrony]</code>
:enter 'busybox' or press Enter for chrony

''' (next step is the additional step for ECKD DASDs on z/VM)'''
<pre>
Available ECKD DASD(s) are:
0.0.04c0 (3390/0c 3990/e9 IBM)
0.0.05d1 (3390/0c 3990/e9 IBM)
Which ECKD DASD(s) would you like to be formatted using dasdfmt? (enter '?' for help) [all]</pre>
:enter 'all' or '0.0.04c0 0.0.05d1' '''(separated by a space)''' to format all/both DASDs
:enter '0.0.04c0' or '0.0.05d1' to format respective DASD
:enter '?' for help

<code>WARNING: Erase ECKD DASD 0.0.04c0? [y/N]:</code>
:enter 'y' to format

<pre>
Available disks are:
dasda (2.5 GB IBM 0.0.04c0)
Which disk(s) would you like to use? (or '?' for help or 'none') [dasda]</pre>
:enter 'dasda' or press Enter

<pre>
The following disk is selected:
dasda (2.5 GB IBM 0.0.04c0)
How would you like to use it? ('sys', 'data', 'lvm' or '?' for help) [?]</pre>
:enter 'lvm'

<pre>
The following disk is selected (with LVM):
dasda (2.5 GB IBM 0.0.04c0)
How would you like to use it? ('sys', 'data' or '?' for help) [?]</pre>
:enter 'sys' to install Alpine on disk

<pre>
WARNING: The following disk(s) will be erased:
dasda (2.5 GB IBM 0.0.04c0)
WARNING: Erase the above disk(s) and continue? [y/N]:</pre>
:enter 'y'

<code>Installation is complete. Please reboot.</code>
:the installation is finished

At this point, don't poweroff the installer right away. Go to [https://wiki.alpinelinux.org/wiki/S390x#Copying_SSH_keys_to_new_Alpine_system "Copying SSH keys to new Alpine system"] (below) to have SSH access to your new Alpine system.

== Copying SSH keys to new Alpine system ==

By default, Alpine disables root login with a password via SSH. SSH keys are used instead.

After the installer's done running (<code>Installation is complete. Please reboot.</code>), there are 2 ways to copy your SSH key into the new Alpine system:
* Option 1: mount the installed disk and copy the SSH keys while still at the installer's terminal
* Option 2: poweroff the installer, start the new Alpine system and directly add the SSH keys
::: if you install on KVM, boot the new Alpine system on qemu, and copy the SSH keys
::: if you install on z/VM, use the 3270 client to ipl the new Alpine system and copy the SSH keys

'''Option 1'''

If you use 'lvm' + 'sys' installation (like in above example), do:

:<code> # mount /dev/vg0/lv_root /mnt</code>

:<code> # cp -ar /root/.ssh /mnt/root</code>

If you use 'sys' (without LVM) installation, do:

:<code> # mount /dev/dasda3 /mnt</code> (change dasda to dasdb or dasdc, etc. for whichever DASD you chose)

:<code> # cp -ar /root/.ssh /mnt/root</code>

{{Note|In 'sys' installation, 1st partition is boot, 2nd partition is swap, 3rd partition is root }}

Then run <code> # poweroff</code>.

Go to [https://wiki.alpinelinux.org/wiki/S390x#Login_to_new_Alpine_system "Login to new Alpine system"]

'''Option 2'''

Run <code> # poweroff</code>.

If you use KVM, start qemu with new Alpine system (removing <code>-kernel</code>, <code>-initrd</code>, <code>-append</code> options)

If you use z/VM, open the 3270 client, login with your z/VM username and password. You may need to run <code> ipl cms</code>. Then run <code> ipl 04c0</code> (or whichever DASD device you chose as root disk in earlier steps).

Wait for new Alpine system go up, then login as root user while in the qemu console (on KVM) or 3270 client (on z/VM). Then run:
::<code> # mkdir /root/.ssh</code>
::<code> # wget https://your-website.com/your-ssh-key.pub -O /root/.ssh/authorized_keys</code>
::<code> # chmod 700 /root/.ssh</code>
::<code> # chmod 600 /root/.ssh/authorized_keys</code>

Go to [https://wiki.alpinelinux.org/wiki/S390x#Login_to_new_Alpine_system "Login to new Alpine system"]

== Login to new Alpine system ==
On your workstation/laptop, use SSH client to login new Alpine system:
<code> $ ssh root@192.168.1.2</code> (or whichever ip address you used)

== Extending LVM volume ==
After logging in to your new Alpine system, run:
<pre>
# apk add -q util-linux e2fsprogs-extra

# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
dasda 94:0 0 2.3G 0 disk
├─dasda1 94:1 0 100M 0 part /boot
└─dasda2 94:2 0 2.2G 0 part
├─vg0-lv_swap 254:0 0 588M 0 lvm [SWAP]
└─vg0-lv_root 254:1 0 1.6G 0 lvm /
dasdb 94:4 0 2.3G 0 disk

# dasdfmt -b 4096 -d cdl -yp /dev/dasdb

# fdasd -a /dev/dasdb

# pvcreate /dev/dasdb1

# vgextend vg0 /dev/dasdb1

# lvextend -l +100%FREE /dev/vg0/lv_root

# resize2fs /dev/vg0/lv_root

# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
dasda 94:0 0 2.3G 0 disk
├─dasda1 94:1 0 100M 0 part /boot
└─dasda2 94:2 0 2.2G 0 part
├─vg0-lv_swap 254:0 0 588M 0 lvm [SWAP]
└─vg0-lv_root 254:1 0 3.9G 0 lvm /
dasdb 94:4 0 2.3G 0 disk
└─dasdb1 94:5 0 2.3G 0 part
└─vg0-lv_root 254:1 0 3.9G 0 lvm /
</pre>

= 5. Tips =
If you want to disable swap partition, after finishing NTP client step, quit the installer by pressing <code>Ctrl + C</code>. Then run following command to complete remaining steps:

<code># setup-disk -s 0</code>

{{Note|If you do 'sys' installation, there will be no swap partition anymore and 1st partition will be boot, 2nd partition will be root}}

S390x/Installation

2019-07-03T12:10:43Z

Tmhoang: update to v3.10

= 1. Known Issues =
1. Installation on 2 or more DASDs (either ECKD and FBA) on z/VM is not supported in the installer script (<code>setup-alpine</code>) at the moment. If you want to install/extend on more than 1 DASD, see [https://wiki.alpinelinux.org/wiki/S390x#Extending_LVM_volume "Extending LVM volume"]. However, installation on 2 or more virtio (SCSI) disks on KVM are supported just like other architectures.

= 2. The boot media =

For KVM, both ISO image and netboot media (kernel and initramfs) are supported.

For z/VM, netboot media is supported.

For LPAR, netboot media is supported. See [https://wiki.alpinelinux.org/wiki/S390x/Installation/LPAR "LPAR"] for more information.

Boot media are found at:

* http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/s390x/

== Kernel parameters (and parmfile) ==
The Alpine s390x boot media requires following kernel parameters to work: (Details at : <code>https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt</code>)

<code>ip=dhcp</code> : use DHCP for network configuration.

<code>ip=client-ip:server-ip:gw-ip:netmask:hostname:device:autoconf:dns1:dns2</code> : use static IP configuration, each field is separated by a colon <code>:</code>
* <code>client-ip</code> ip address of the guest VM where we are going to run the installer
* <code>server-ip</code> not used, leave blank or fill with <code>none</code>
* <code>gw-ip</code> the gateway ip address
* <code>netmask</code> the netmask
* <code>hostname</code> not used, leave blank or fill with <code>none</code>
* <code>device</code> the network interface of the guest VM, default is <code>eth0</code> if left blank
* <code>autoconf</code> not used, leave blank or fill with <code>none</code> or <code>off</code>
* <code>dns1</code> address of the DNS server
* <code>dns2</code> address of the 2nd DNS server

<code>alpine_repo=</code> : the location of the Alpine repository from which packages are downloaded.

:For stable release, use <code>http://dl-cdn.alpinelinux.org/alpine/v3.10/main</code>

:For rolling release, use <code>http://dl-cdn.alpinelinux.org/alpine/edge/main</code>

<code>modloop=</code> : the remote location of the image containing kernel's modules, required for LVM and raid setup.

:The remote location of the <code>modloop</code> image is the same as the kernel and initramfs (see below).

<code>ssh_key=</code> : the remote location of your SSH public key which is used to allow SSH connection into the installer. It will be downloaded and copied into <code>/root/.ssh/authorized_keys</code> in the installer.

{{Note|Fetching public keys from HTTP, HTTPS and FTPS are supported. HTTP should only be used in local development network where you own the network.}}

{{Note|Alpine Linux security policies are against using passwords for root access via SSH as we consider using public-private key pairs is a much better approach.}}

'''z/VM only'''

<code>dasd=</code> : the addresses of the DASD devices, either ECKD or FBA DASDs. Each device is separated with a comma.

<code>s390x_net=</code> : the network interface type and its subchannels. At the moment, only QETH layer 2 is supported, thus the name <code>qeth_l2</code> is used (see below).

= 3. Pre-installation =

== KVM ==
Create a virtual disk:
$ qemu-img create alpine_disk.qcow2 5G

==== Using iso image ====
Download latest iso image from : http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/s390x

Start qemu:

$ qemu-system-s390x -M s390-ccw-virtio \
-m 1024 -smp 2 -nographic -enable-kvm \
-net nic -net tap,ifname=tap0,script=no \
-hda alpine_disk.qcow2 \
-boot d -cdrom alpine-standard-3.9.0-s390x.iso

==== Using netboot media ====
Download the latest [http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/s390x/netboot/vmlinuz-vanilla kernel] and [http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/s390x/netboot/initramfs-vanilla initramfs].

Start qemu: (modify <code>ip=</code> <code>alpine_repo=</code> <code>ssh_key=</code> for your needs)

$ qemu-system-s390x -M s390-ccw-virtio \
-m 1024 -smp 2 -nographic -enable-kvm \
-net nic -net tap,ifname=tap0,script=no \
-hda alpine_disk.qcow2 \
-kernel vmlinuz-vanilla \
-initrd initramfs-vanilla \
-append "ip=192.168.1.2::192.168.1.1:255.255.255.0::::8.8.8.8:1.1.1.1 alpine_repo=http://dl-cdn.alpinelinux.org/alpine/v3.10/main modloop=http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/s390x/netboot/modloop-vanilla ssh_key=https://your-website.com/your-ssh-key.pub"

{{Note|If you have direct access to the qemu console, <code>ssh_key</code> might not be required.}}

== z/VM ==
To ease out the process of downloading the images, punch the readers, ipl, etc., [https://github.com/trothr/znetboot '''ZNETBOOT'''] is used.

==== Create the parm file ====
On your workstation/laptop, create a file named <code>alpine.znetboot</code> in your home directory with contents below (modify <code>dasd=</code><code>s390x_net=</code> <code>ip=</code> <code>alpine_repo=</code> <code>ssh_key=</code> for your needs)

<pre>
ZNETBOOT_KERNEL=http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/s390x/netboot/vmlinuz-vanilla
ZNETBOOT_INITRD=http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/s390x/netboot/initramfs-vanilla
ZNETBOOT_PROGRESS=1M

alpine_repo=http://dl-cdn.alpinelinux.org/alpine/v3.10/main
modloop=http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/s390x/netboot/modloop-vanilla

dasd=0.0.04c0,0.0.05d1
s390x_net=qeth_l2,0.0.0560,0.0.0561,0.0.0562
ip=192.168.1.2::192.168.1.1:255.255.255.0::::8.8.8.8:1.1.1.1

ssh_key=https://your-website.com/your-ssh-key.pub

</pre>

==== Upload to z/VM system via 3270 client ====
[[File:X3270-1.png|right|300px|thumb|Figure 1.]]
On your workstation/laptop, download 2 files [https://raw.githubusercontent.com/trothr/znetboot/master/znetboot.exec <code>znetboot.exec</code>], and [https://raw.githubusercontent.com/trothr/znetboot/master/curl.rexx <code>curl.rexx</code>] to your home directory.

Open 3270 client and log in the z/VM system with your z/VM username and password.

Upload 3 files <code>alpine.znetboot</code>, <code>znetboot.exec</code>, <code>curl.rexx</code> to the z/VM environment using the 3270 client (this tutorial uses x3270). On the top left corner, click "File", then "File Transfer". (Figure 1.)

Do following steps : (Figure 2.) [[File:X3270-2.png|right|300px|thumb|Figure 2.]]
* On "Local File Name" box, enter '''alpine.znetboot''' (the file in your laptop/workstation, at '''~/alpine.znetboot''')
* On "Host File Name" box, enter '''alpine znetboot''' (the file will be in z/VM console)

{{Note|Beware the difference between '''the dot <code>.</code>''' and '''the space <code> </code>''' characters in the file names.}}

* Choose '''Send to host'''
* Choose '''Host is VM/CMS'''
* Choose either '''Fixed''' or '''Variable''' for '''Record Format'''
:Enter a number for LRECL and BLKSIZE, respectively
{{Note|Any line in '''alpine.znetboot''' that has more 80 chars (columns) will be splitted into more than 1 line when uploaded to z/VM (CMS) console via 3270. Count the number of characters/column of the longest line in your '''alpine.znetboot''' and fill it in LRECL. There is no restriction for BLKSIZE but 80 is preferred.}}

* Click '''Transfer File''' box

Repeat the same steps with <code>znetboot.exec</code> and <code>curl.rexx</code> files.

==== (Optional) Check the configuration files ====
On 3270 client, enter following commands to check if the configuration files are correctly transferred:

<code>xedit alpine znetboot</code>

<code>xedit znetboot exec</code>

<code>xedit curl rex</code>

or <code>filel</code> and put <code>xedit</code> on CMD column to edit respective file.

==== Start ZNETBOOT ====
On 3270 client, type below command and wait till Figure 3.: [[File:X3270-3.png|right|300px|thumb|Figure 3.]]

<code>znetboot alpine</code>

= 4. Installation =
If you install on z/VM, steps in this part does not involve the interaction with the 3270 client anymore. Everything is done in the terminal with SSH client.

If you install on KVM, you can either SSH into the installer (below) or directly use the console starting qemu.

Either installing in KVM or z/VM environments, from your workstation/laptop, you will be able to run:
$ ssh root@192.168.1.2 (change ip address to what you specified earlier)

Remaining steps are similar to installing Alpine on other architectures (x86, arm, ppc, etc.), either on KVM (using virtio/SCSI disks) or on z/VM with FBA DASDs. Installing on ECKD DASDs requires an additional step, as described below.

== Example ==
Below is the detailed walkthrough of installing Alpine on a single ECKD DASD using LVM and extend that LVM to the second ECKD DASD.

After SSH-ing into the Alpine installer, run:
# setup-alpine

<code>Select keyboard layout [none]:</code>
:press Enter for none

<code>Enter system hostname (short form, e.g. 'foo') [localhost]:</code>
:enter your hostname

<pre>
Available interfaces are: eth0.
Enter '?' for help on bridges, bonding and vlans.
Which one do you want to initialize? (or '?' or 'done') [eth0]:</pre>
:type 'eth0' or press Enter

<code>Ip address for eth0? (or 'dhcp', 'none', '?') [192.168.1.2]</code>
:enter ip address or 'dhcp'

<code>Netmask? [255.255.255.0]</code>
:enter netmask
<code>Gateway? (or 'none') [192.168.1.1]</code>
:enter gateway's ip address

<code>Do you want to do any manual network configuration? [no]</code>
:enter 'no' or press Enter

<code>DNS domain name? (e.g 'bar.com') []</code>
:enter domain name or press Enter for none

<code>DNS nameserver(s)? [8.8.8.8 ]</code>
:enter DNS nameserver

<code>Changing password for root</code>
:enter root password

<code>Which timezone are you in? ('?' for list) [UTC]</code>
:enter timezone or '?' for list of timezones

<code>HTTP/FTP proxy URL? (e.g. 'http://proxy:8080', or 'none') [none]</code>
:enter proxy or press Enter for none

<code>Enter mirror number (1-27) or URL to add (or r/f/e/done) [f]:</code>
:enter a number or 'r' or 'f' or 'e' or 'done' as described

<code>Which SSH server? ('openssh', 'dropbear' or 'none') [openssh]</code>
:enter SSH server or press Enter for openssh

<code>Which NTP client to run? ('busybox', 'openntpd', 'chrony' or 'none') [chrony]</code>
:enter 'busybox' or press Enter for chrony

''' (next step is the additional step for ECKD DASDs on z/VM)'''
<pre>
Available ECKD DASD(s) are:
0.0.04c0 (3390/0c 3990/e9 IBM)
0.0.05d1 (3390/0c 3990/e9 IBM)
Which ECKD DASD(s) would you like to be formatted using dasdfmt? (enter '?' for help) [all]</pre>
:enter 'all' or '0.0.04c0 0.0.05d1' '''(separated by a space)''' to format all/both DASDs
:enter '0.0.04c0' or '0.0.05d1' to format respective DASD
:enter '?' for help

<code>WARNING: Erase ECKD DASD 0.0.04c0? [y/N]:</code>
:enter 'y' to format

<pre>
Available disks are:
dasda (2.5 GB IBM 0.0.04c0)
Which disk(s) would you like to use? (or '?' for help or 'none') [dasda]</pre>
:enter 'dasda' or press Enter

<pre>
The following disk is selected:
dasda (2.5 GB IBM 0.0.04c0)
How would you like to use it? ('sys', 'data', 'lvm' or '?' for help) [?]</pre>
:enter 'lvm'

<pre>
The following disk is selected (with LVM):
dasda (2.5 GB IBM 0.0.04c0)
How would you like to use it? ('sys', 'data' or '?' for help) [?]</pre>
:enter 'sys' to install Alpine on disk

<pre>
WARNING: The following disk(s) will be erased:
dasda (2.5 GB IBM 0.0.04c0)
WARNING: Erase the above disk(s) and continue? [y/N]:</pre>
:enter 'y'

<code>Installation is complete. Please reboot.</code>
:the installation is finished

At this point, don't poweroff the installer right away. Go to [https://wiki.alpinelinux.org/wiki/S390x#Copying_SSH_keys_to_new_Alpine_system "Copying SSH keys to new Alpine system"] (below) to have SSH access to your new Alpine system.

== Copying SSH keys to new Alpine system ==

By default, Alpine disables root login with a password via SSH. SSH keys are used instead.

After the installer's done running (<code>Installation is complete. Please reboot.</code>), there are 2 ways to copy your SSH key into the new Alpine system:
* Option 1: mount the installed disk and copy the SSH keys while still at the installer's terminal
* Option 2: poweroff the installer, start the new Alpine system and directly add the SSH keys
::: if you install on KVM, boot the new Alpine system on qemu, and copy the SSH keys
::: if you install on z/VM, use the 3270 client to ipl the new Alpine system and copy the SSH keys

'''Option 1'''

If you use 'lvm' + 'sys' installation (like in above example), do:

:<code> # mount /dev/vg0/lv_root /mnt</code>

:<code> # cp -ar /root/.ssh /mnt/root</code>

If you use 'sys' (without LVM) installation, do:

:<code> # mount /dev/dasda3 /mnt</code> (change dasda to dasdb or dasdc, etc. for whichever DASD you chose)

:<code> # cp -ar /root/.ssh /mnt/root</code>

{{Note|In 'sys' installation, 1st partition is boot, 2nd partition is swap, 3rd partition is root }}

Then run <code> # poweroff</code>.

Go to [https://wiki.alpinelinux.org/wiki/S390x#Login_to_new_Alpine_system "Login to new Alpine system"]

'''Option 2'''

Run <code> # poweroff</code>.

If you use KVM, start qemu with new Alpine system (removing <code>-kernel</code>, <code>-initrd</code>, <code>-append</code> options)

If you use z/VM, open the 3270 client, login with your z/VM username and password. You may need to run <code> ipl cms</code>. Then run <code> ipl 04c0</code> (or whichever DASD device you chose as root disk in earlier steps).

Wait for new Alpine system go up, then login as root user while in the qemu console (on KVM) or 3270 client (on z/VM). Then run:
::<code> # mkdir /root/.ssh</code>
::<code> # wget https://your-website.com/your-ssh-key.pub -O /root/.ssh/authorized_keys</code>
::<code> # chmod 700 /root/.ssh</code>
::<code> # chmod 600 /root/.ssh/authorized_keys</code>

Go to [https://wiki.alpinelinux.org/wiki/S390x#Login_to_new_Alpine_system "Login to new Alpine system"]

== Login to new Alpine system ==
On your workstation/laptop, use SSH client to login new Alpine system:
<code> $ ssh root@192.168.1.2</code> (or whichever ip address you used)

== Extending LVM volume ==
After logging in to your new Alpine system, run:
<pre>
# apk add -q util-linux e2fsprogs-extra

# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
dasda 94:0 0 2.3G 0 disk
├─dasda1 94:1 0 100M 0 part /boot
└─dasda2 94:2 0 2.2G 0 part
├─vg0-lv_swap 254:0 0 588M 0 lvm [SWAP]
└─vg0-lv_root 254:1 0 1.6G 0 lvm /
dasdb 94:4 0 2.3G 0 disk

# dasdfmt -b 4096 -d cdl -yp /dev/dasdb

# fdasd -a /dev/dasdb

# pvcreate /dev/dasdb1

# vgextend vg0 /dev/dasdb1

# lvextend -l +100%FREE /dev/vg0/lv_root

# resize2fs /dev/vg0/lv_root

# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
dasda 94:0 0 2.3G 0 disk
├─dasda1 94:1 0 100M 0 part /boot
└─dasda2 94:2 0 2.2G 0 part
├─vg0-lv_swap 254:0 0 588M 0 lvm [SWAP]
└─vg0-lv_root 254:1 0 3.9G 0 lvm /
dasdb 94:4 0 2.3G 0 disk
└─dasdb1 94:5 0 2.3G 0 part
└─vg0-lv_root 254:1 0 3.9G 0 lvm /
</pre>

= 5. Tips =
If you want to disable swap partition, after finishing NTP client step, quit the installer by pressing <code>Ctrl + C</code>. Then run following command to complete remaining steps:

<code># setup-disk -s 0</code>

{{Note|If you do 'sys' installation, there will be no swap partition anymore and 1st partition will be boot, 2nd partition will be root}}

S390x/Installation

2019-06-06T22:53:10Z

Tmhoang:

= 1. Known Issues =
1. Installation on 2 or more DASDs (either ECKD and FBA) on z/VM is not supported in the installer script (<code>setup-alpine</code>) at the moment. If you want to install/extend on more than 1 DASD, see [https://wiki.alpinelinux.org/wiki/S390x#Extending_LVM_volume "Extending LVM volume"]. However, installation on 2 or more virtio (SCSI) disks on KVM are supported just like other architectures.

= 2. The boot media =

For KVM, both ISO image and netboot media (kernel and initramfs) are supported.

For z/VM, netboot media is supported.

For LPAR, netboot media is supported. See [https://wiki.alpinelinux.org/wiki/S390x/Installation/LPAR "LPAR"] for more information.

Boot media are found at:

* http://dl-cdn.alpinelinux.org/alpine/v3.9/releases/s390x/

== Kernel parameters (and parmfile) ==
The Alpine s390x boot media requires following kernel parameters to work: (Details at : <code>https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt</code>)

<code>ip=dhcp</code> : use DHCP for network configuration.

<code>ip=client-ip:server-ip:gw-ip:netmask:hostname:device:autoconf:dns1:dns2</code> : use static IP configuration, each field is separated by a colon <code>:</code>
* <code>client-ip</code> ip address of the guest VM where we are going to run the installer
* <code>server-ip</code> not used, leave blank or fill with <code>none</code>
* <code>gw-ip</code> the gateway ip address
* <code>netmask</code> the netmask
* <code>hostname</code> not used, leave blank or fill with <code>none</code>
* <code>device</code> the network interface of the guest VM, default is <code>eth0</code> if left blank
* <code>autoconf</code> not used, leave blank or fill with <code>none</code> or <code>off</code>
* <code>dns1</code> address of the DNS server
* <code>dns2</code> address of the 2nd DNS server

<code>alpine_repo=</code> : the location of the Alpine repository from which packages are downloaded.

:For stable release, use <code>http://dl-cdn.alpinelinux.org/alpine/v3.9/main</code>

:For rolling release, use <code>http://dl-cdn.alpinelinux.org/alpine/edge/main</code>

<code>modloop=</code> : the remote location of the image containing kernel's modules, required for LVM and raid setup.

:The remote location of the <code>modloop</code> image is the same as the kernel and initramfs (see below).

<code>ssh_key=</code> : the remote location of your SSH public key which is used to allow SSH connection into the installer. It will be downloaded and copied into <code>/root/.ssh/authorized_keys</code> in the installer.

{{Note|Fetching public keys from HTTP, HTTPS and FTPS are supported. HTTP should only be used in local development network where you own the network.}}

{{Note|Alpine Linux security policies are against using passwords for root access via SSH as we consider using public-private key pairs is a much better approach.}}

'''z/VM only'''

<code>dasd=</code> : the addresses of the DASD devices, either ECKD or FBA DASDs. Each device is separated with a comma.

<code>s390x_net=</code> : the network interface type and its subchannels. At the moment, only QETH layer 2 is supported, thus the name <code>qeth_l2</code> is used (see below).

= 3. Pre-installation =

== KVM ==
Create a virtual disk:
$ qemu-img create alpine_disk.qcow2 5G

==== Using iso image ====
Download latest iso image from : http://dl-cdn.alpinelinux.org/alpine/v3.9/releases/s390x

Start qemu:

$ qemu-system-s390x -M s390-ccw-virtio \
-m 1024 -smp 2 -nographic -enable-kvm \
-net nic -net tap,ifname=tap0,script=no \
-hda alpine_disk.qcow2 \
-boot d -cdrom alpine-standard-3.9.0-s390x.iso

==== Using netboot media ====
Download the latest [http://dl-cdn.alpinelinux.org/alpine/v3.9/releases/s390x/netboot/vmlinuz-vanilla kernel] and [http://dl-cdn.alpinelinux.org/alpine/v3.9/releases/s390x/netboot/initramfs-vanilla initramfs].

Start qemu: (modify <code>ip=</code> <code>alpine_repo=</code> <code>ssh_key=</code> for your needs)

$ qemu-system-s390x -M s390-ccw-virtio \
-m 1024 -smp 2 -nographic -enable-kvm \
-net nic -net tap,ifname=tap0,script=no \
-hda alpine_disk.qcow2 \
-kernel vmlinuz-vanilla \
-initrd initramfs-vanilla \
-append "ip=192.168.1.2::192.168.1.1:255.255.255.0::::8.8.8.8:1.1.1.1 alpine_repo=http://dl-cdn.alpinelinux.org/alpine/v3.9/main modloop=http://dl-cdn.alpinelinux.org/alpine/v3.9/releases/s390x/netboot/modloop-vanilla ssh_key=https://your-website.com/your-ssh-key.pub"

{{Note|If you have direct access to the qemu console, <code>ssh_key</code> might not be required.}}

== z/VM ==
To ease out the process of downloading the images, punch the readers, ipl, etc., [https://github.com/trothr/znetboot '''ZNETBOOT'''] is used.

==== Create the parm file ====
On your workstation/laptop, create a file named <code>alpine.znetboot</code> in your home directory with contents below (modify <code>dasd=</code><code>s390x_net=</code> <code>ip=</code> <code>alpine_repo=</code> <code>ssh_key=</code> for your needs)

<pre>
ZNETBOOT_KERNEL=http://dl-cdn.alpinelinux.org/alpine/v3.9/releases/s390x/netboot/vmlinuz-vanilla
ZNETBOOT_INITRD=http://dl-cdn.alpinelinux.org/alpine/v3.9/releases/s390x/netboot/initramfs-vanilla
ZNETBOOT_PROGRESS=1M

alpine_repo=http://dl-cdn.alpinelinux.org/alpine/v3.9/main
modloop=http://dl-cdn.alpinelinux.org/alpine/v3.9/releases/s390x/netboot/modloop-vanilla

dasd=0.0.04c0,0.0.05d1
s390x_net=qeth_l2,0.0.0560,0.0.0561,0.0.0562
ip=192.168.1.2::192.168.1.1:255.255.255.0::::8.8.8.8:1.1.1.1

ssh_key=https://your-website.com/your-ssh-key.pub

</pre>

==== Upload to z/VM system via 3270 client ====
[[File:X3270-1.png|right|300px|thumb|Figure 1.]]
On your workstation/laptop, download 2 files [https://raw.githubusercontent.com/trothr/znetboot/master/znetboot.exec <code>znetboot.exec</code>], and [https://raw.githubusercontent.com/trothr/znetboot/master/curl.rexx <code>curl.rexx</code>] to your home directory.

Open 3270 client and log in the z/VM system with your z/VM username and password.

Upload 3 files <code>alpine.znetboot</code>, <code>znetboot.exec</code>, <code>curl.rexx</code> to the z/VM environment using the 3270 client (this tutorial uses x3270). On the top left corner, click "File", then "File Transfer". (Figure 1.)

Do following steps : (Figure 2.) [[File:X3270-2.png|right|300px|thumb|Figure 2.]]
* On "Local File Name" box, enter '''alpine.znetboot''' (the file in your laptop/workstation, at '''~/alpine.znetboot''')
* On "Host File Name" box, enter '''alpine znetboot''' (the file will be in z/VM console)

{{Note|Beware the difference between '''the dot <code>.</code>''' and '''the space <code> </code>''' characters in the file names.}}

* Choose '''Send to host'''
* Choose '''Host is VM/CMS'''
* Choose either '''Fixed''' or '''Variable''' for '''Record Format'''
:Enter a number for LRECL and BLKSIZE, respectively
{{Note|Any line in '''alpine.znetboot''' that has more 80 chars (columns) will be splitted into more than 1 line when uploaded to z/VM (CMS) console via 3270. Count the number of characters/column of the longest line in your '''alpine.znetboot''' and fill it in LRECL. There is no restriction for BLKSIZE but 80 is preferred.}}

* Click '''Transfer File''' box

Repeat the same steps with <code>znetboot.exec</code> and <code>curl.rexx</code> files.

==== (Optional) Check the configuration files ====
On 3270 client, enter following commands to check if the configuration files are correctly transferred:

<code>xedit alpine znetboot</code>

<code>xedit znetboot exec</code>

<code>xedit curl rex</code>

or <code>filel</code> and put <code>xedit</code> on CMD column to edit respective file.

==== Start ZNETBOOT ====
On 3270 client, type below command and wait till Figure 3.: [[File:X3270-3.png|right|300px|thumb|Figure 3.]]

<code>znetboot alpine</code>

= 4. Installation =
If you install on z/VM, steps in this part does not involve the interaction with the 3270 client anymore. Everything is done in the terminal with SSH client.

If you install on KVM, you can either SSH into the installer (below) or directly use the console starting qemu.

Either installing in KVM or z/VM environments, from your workstation/laptop, you will be able to run:
$ ssh root@192.168.1.2 (change ip address to what you specified earlier)

Remaining steps are similar to installing Alpine on other architectures (x86, arm, ppc, etc.), either on KVM (using virtio/SCSI disks) or on z/VM with FBA DASDs. Installing on ECKD DASDs requires an additional step, as described below.

== Example ==
Below is the detailed walkthrough of installing Alpine on a single ECKD DASD using LVM and extend that LVM to the second ECKD DASD.

After SSH-ing into the Alpine installer, run:
# setup-alpine

<code>Select keyboard layout [none]:</code>
:press Enter for none

<code>Enter system hostname (short form, e.g. 'foo') [localhost]:</code>
:enter your hostname

<pre>
Available interfaces are: eth0.
Enter '?' for help on bridges, bonding and vlans.
Which one do you want to initialize? (or '?' or 'done') [eth0]:</pre>
:type 'eth0' or press Enter

<code>Ip address for eth0? (or 'dhcp', 'none', '?') [192.168.1.2]</code>
:enter ip address or 'dhcp'

<code>Netmask? [255.255.255.0]</code>
:enter netmask
<code>Gateway? (or 'none') [192.168.1.1]</code>
:enter gateway's ip address

<code>Do you want to do any manual network configuration? [no]</code>
:enter 'no' or press Enter

<code>DNS domain name? (e.g 'bar.com') []</code>
:enter domain name or press Enter for none

<code>DNS nameserver(s)? [8.8.8.8 ]</code>
:enter DNS nameserver

<code>Changing password for root</code>
:enter root password

<code>Which timezone are you in? ('?' for list) [UTC]</code>
:enter timezone or '?' for list of timezones

<code>HTTP/FTP proxy URL? (e.g. 'http://proxy:8080', or 'none') [none]</code>
:enter proxy or press Enter for none

<code>Enter mirror number (1-27) or URL to add (or r/f/e/done) [f]:</code>
:enter a number or 'r' or 'f' or 'e' or 'done' as described

<code>Which SSH server? ('openssh', 'dropbear' or 'none') [openssh]</code>
:enter SSH server or press Enter for openssh

<code>Which NTP client to run? ('busybox', 'openntpd', 'chrony' or 'none') [chrony]</code>
:enter 'busybox' or press Enter for chrony

''' (next step is the additional step for ECKD DASDs on z/VM)'''
<pre>
Available ECKD DASD(s) are:
0.0.04c0 (3390/0c 3990/e9 IBM)
0.0.05d1 (3390/0c 3990/e9 IBM)
Which ECKD DASD(s) would you like to be formatted using dasdfmt? (enter '?' for help) [all]</pre>
:enter 'all' or '0.0.04c0 0.0.05d1' '''(separated by a space)''' to format all/both DASDs
:enter '0.0.04c0' or '0.0.05d1' to format respective DASD
:enter '?' for help

<code>WARNING: Erase ECKD DASD 0.0.04c0? [y/N]:</code>
:enter 'y' to format

<pre>
Available disks are:
dasda (2.5 GB IBM 0.0.04c0)
Which disk(s) would you like to use? (or '?' for help or 'none') [dasda]</pre>
:enter 'dasda' or press Enter

<pre>
The following disk is selected:
dasda (2.5 GB IBM 0.0.04c0)
How would you like to use it? ('sys', 'data', 'lvm' or '?' for help) [?]</pre>
:enter 'lvm'

<pre>
The following disk is selected (with LVM):
dasda (2.5 GB IBM 0.0.04c0)
How would you like to use it? ('sys', 'data' or '?' for help) [?]</pre>
:enter 'sys' to install Alpine on disk

<pre>
WARNING: The following disk(s) will be erased:
dasda (2.5 GB IBM 0.0.04c0)
WARNING: Erase the above disk(s) and continue? [y/N]:</pre>
:enter 'y'

<code>Installation is complete. Please reboot.</code>
:the installation is finished

At this point, don't poweroff the installer right away. Go to [https://wiki.alpinelinux.org/wiki/S390x#Copying_SSH_keys_to_new_Alpine_system "Copying SSH keys to new Alpine system"] (below) to have SSH access to your new Alpine system.

== Copying SSH keys to new Alpine system ==

By default, Alpine disables root login with a password via SSH. SSH keys are used instead.

After the installer's done running (<code>Installation is complete. Please reboot.</code>), there are 2 ways to copy your SSH key into the new Alpine system:
* Option 1: mount the installed disk and copy the SSH keys while still at the installer's terminal
* Option 2: poweroff the installer, start the new Alpine system and directly add the SSH keys
::: if you install on KVM, boot the new Alpine system on qemu, and copy the SSH keys
::: if you install on z/VM, use the 3270 client to ipl the new Alpine system and copy the SSH keys

'''Option 1'''

If you use 'lvm' + 'sys' installation (like in above example), do:

:<code> # mount /dev/vg0/lv_root /mnt</code>

:<code> # cp -ar /root/.ssh /mnt/root</code>

If you use 'sys' (without LVM) installation, do:

:<code> # mount /dev/dasda3 /mnt</code> (change dasda to dasdb or dasdc, etc. for whichever DASD you chose)

:<code> # cp -ar /root/.ssh /mnt/root</code>

{{Note|In 'sys' installation, 1st partition is boot, 2nd partition is swap, 3rd partition is root }}

Then run <code> # poweroff</code>.

Go to [https://wiki.alpinelinux.org/wiki/S390x#Login_to_new_Alpine_system "Login to new Alpine system"]

'''Option 2'''

Run <code> # poweroff</code>.

If you use KVM, start qemu with new Alpine system (removing <code>-kernel</code>, <code>-initrd</code>, <code>-append</code> options)

If you use z/VM, open the 3270 client, login with your z/VM username and password. You may need to run <code> ipl cms</code>. Then run <code> ipl 04c0</code> (or whichever DASD device you chose as root disk in earlier steps).

Wait for new Alpine system go up, then login as root user while in the qemu console (on KVM) or 3270 client (on z/VM). Then run:
::<code> # mkdir /root/.ssh</code>
::<code> # wget https://your-website.com/your-ssh-key.pub -O /root/.ssh/authorized_keys</code>
::<code> # chmod 700 /root/.ssh</code>
::<code> # chmod 600 /root/.ssh/authorized_keys</code>

Go to [https://wiki.alpinelinux.org/wiki/S390x#Login_to_new_Alpine_system "Login to new Alpine system"]

== Login to new Alpine system ==
On your workstation/laptop, use SSH client to login new Alpine system:
<code> $ ssh root@192.168.1.2</code> (or whichever ip address you used)

== Extending LVM volume ==
After logging in to your new Alpine system, run:
<pre>
# apk add -q util-linux e2fsprogs-extra

# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
dasda 94:0 0 2.3G 0 disk
├─dasda1 94:1 0 100M 0 part /boot
└─dasda2 94:2 0 2.2G 0 part
├─vg0-lv_swap 254:0 0 588M 0 lvm [SWAP]
└─vg0-lv_root 254:1 0 1.6G 0 lvm /
dasdb 94:4 0 2.3G 0 disk

# dasdfmt -b 4096 -d cdl -yp /dev/dasdb

# fdasd -a /dev/dasdb

# pvcreate /dev/dasdb1

# vgextend vg0 /dev/dasdb1

# lvextend -l +100%FREE /dev/vg0/lv_root

# resize2fs /dev/vg0/lv_root

# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
dasda 94:0 0 2.3G 0 disk
├─dasda1 94:1 0 100M 0 part /boot
└─dasda2 94:2 0 2.2G 0 part
├─vg0-lv_swap 254:0 0 588M 0 lvm [SWAP]
└─vg0-lv_root 254:1 0 3.9G 0 lvm /
dasdb 94:4 0 2.3G 0 disk
└─dasdb1 94:5 0 2.3G 0 part
└─vg0-lv_root 254:1 0 3.9G 0 lvm /
</pre>

= 5. Tips =
If you want to disable swap partition, after finishing NTP client step, quit the installer by pressing <code>Ctrl + C</code>. Then run following command to complete remaining steps:

<code># setup-disk -s 0</code>

{{Note|If you do 'sys' installation, there will be no swap partition anymore and 1st partition will be boot, 2nd partition will be root}}

S390x/Known Issues

2019-05-09T20:29:21Z

Tmhoang: Blanked the page

S390x/Installation

2019-05-09T20:16:19Z

Tmhoang: /* z/VM */

= 1. Known Issues =
1. Installation on 2 or more DASDs (either ECKD and FBA) on z/VM is not supported in the installer script (<code>setup-alpine</code>) at the moment. If you want to install/extend on more than 1 DASD, see [https://wiki.alpinelinux.org/wiki/S390x#Extending_LVM_volume "Extending LVM volume"]. However, installation on 2 or more virtio (SCSI) disks on KVM are supported just like other architectures.

= 2. The boot media =

For KVM, both ISO image and netboot media (kernel and initramfs) are supported.

For z/VM, netboot media is supported.

For LPAR, not yet supported.

Boot media are found at:

* http://dl-cdn.alpinelinux.org/alpine/v3.9/releases/s390x/

== Kernel parameters (and parmfile) ==
The Alpine s390x boot media requires following kernel parameters to work: (Details at : <code>https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt</code>)

<code>ip=dhcp</code> : use DHCP for network configuration.

<code>ip=client-ip:server-ip:gw-ip:netmask:hostname:device:autoconf:dns1:dns2</code> : use static IP configuration, each field is separated by a colon <code>:</code>
* <code>client-ip</code> ip address of the guest VM where we are going to run the installer
* <code>server-ip</code> not used, leave blank or fill with <code>none</code>
* <code>gw-ip</code> the gateway ip address
* <code>netmask</code> the netmask
* <code>hostname</code> not used, leave blank or fill with <code>none</code>
* <code>device</code> the network interface of the guest VM, default is <code>eth0</code> if left blank
* <code>autoconf</code> not used, leave blank or fill with <code>none</code> or <code>off</code>
* <code>dns1</code> address of the DNS server
* <code>dns2</code> address of the 2nd DNS server

<code>alpine_repo=</code> : the location of the Alpine repository from which packages are downloaded.

:For stable release, use <code>http://dl-cdn.alpinelinux.org/alpine/v3.9/main</code>

:For rolling release, use <code>http://dl-cdn.alpinelinux.org/alpine/edge/main</code>

<code>modloop=</code> : the remote location of the image containing kernel's modules, required for LVM and raid setup.

:The remote location of the <code>modloop</code> image is the same as the kernel and initramfs (see below).

<code>ssh_key=</code> : the remote location of your SSH public key which is used to allow SSH connection into the installer. It will be downloaded and copied into <code>/root/.ssh/authorized_keys</code> in the installer.

{{Note|Fetching public keys from HTTP, HTTPS and FTPS are supported. HTTP should only be used in local development network where you own the network.}}

{{Note|Alpine Linux security policies are against using passwords for root access via SSH as we consider using public-private key pairs is a much better approach.}}

'''z/VM only'''

<code>dasd=</code> : the addresses of the DASD devices, either ECKD or FBA DASDs. Each device is separated with a comma.

<code>s390x_net=</code> : the network interface type and its subchannels. At the moment, only QETH layer 2 is supported, thus the name <code>qeth_l2</code> is used (see below).

= 3. Pre-installation =

== KVM ==
Create a virtual disk:
$ qemu-img create alpine_disk.qcow2 5G

==== Using iso image ====
Download latest iso image from : http://dl-cdn.alpinelinux.org/alpine/v3.9/releases/s390x

Start qemu:

$ qemu-system-s390x -M s390-ccw-virtio \
-m 1024 -smp 2 -nographic -enable-kvm \
-net nic -net tap,ifname=tap0,script=no \
-hda alpine_disk.qcow2 \
-boot d -cdrom alpine-standard-3.9.0-s390x.iso

==== Using netboot media ====
Download the latest [http://dl-cdn.alpinelinux.org/alpine/v3.9/releases/s390x/netboot/vmlinuz-vanilla kernel] and [http://dl-cdn.alpinelinux.org/alpine/v3.9/releases/s390x/netboot/initramfs-vanilla initramfs].

Start qemu: (modify <code>ip=</code> <code>alpine_repo=</code> <code>ssh_key=</code> for your needs)

$ qemu-system-s390x -M s390-ccw-virtio \
-m 1024 -smp 2 -nographic -enable-kvm \
-net nic -net tap,ifname=tap0,script=no \
-hda alpine_disk.qcow2 \
-kernel vmlinuz-vanilla \
-initrd initramfs-vanilla \
-append "ip=192.168.1.2::192.168.1.1:255.255.255.0::::8.8.8.8:1.1.1.1 alpine_repo=http://dl-cdn.alpinelinux.org/alpine/v3.9/main modloop=http://dl-cdn.alpinelinux.org/alpine/v3.9/releases/s390x/netboot/modloop-vanilla ssh_key=https://your-website.com/your-ssh-key.pub"

{{Note|If you have direct access to the qemu console, <code>ssh_key</code> might not be required.}}

== z/VM ==
To ease out the process of downloading the images, punch the readers, ipl, etc., [https://github.com/trothr/znetboot '''ZNETBOOT'''] is used.

==== Create the parm file ====
On your workstation/laptop, create a file named <code>alpine.znetboot</code> in your home directory with contents below (modify <code>dasd=</code><code>s390x_net=</code> <code>ip=</code> <code>alpine_repo=</code> <code>ssh_key=</code> for your needs)

<pre>
ZNETBOOT_KERNEL=http://dl-cdn.alpinelinux.org/alpine/v3.9/releases/s390x/netboot/vmlinuz-vanilla
ZNETBOOT_INITRD=http://dl-cdn.alpinelinux.org/alpine/v3.9/releases/s390x/netboot/initramfs-vanilla
ZNETBOOT_PROGRESS=1M

alpine_repo=http://dl-cdn.alpinelinux.org/alpine/v3.9/main
modloop=http://dl-cdn.alpinelinux.org/alpine/v3.9/releases/s390x/netboot/modloop-vanilla

dasd=0.0.04c0,0.0.05d1
s390x_net=qeth_l2,0.0.0560,0.0.0561,0.0.0562
ip=192.168.1.2::192.168.1.1:255.255.255.0::::8.8.8.8:1.1.1.1

ssh_key=https://your-website.com/your-ssh-key.pub

</pre>

==== Upload to z/VM system via 3270 client ====
[[File:X3270-1.png|right|300px|thumb|Figure 1.]]
On your workstation/laptop, download 2 files [https://raw.githubusercontent.com/trothr/znetboot/master/znetboot.exec <code>znetboot.exec</code>], and [https://raw.githubusercontent.com/trothr/znetboot/master/curl.rexx <code>curl.rexx</code>] to your home directory.

Open 3270 client and log in the z/VM system with your z/VM username and password.

Upload 3 files <code>alpine.znetboot</code>, <code>znetboot.exec</code>, <code>curl.rexx</code> to the z/VM environment using the 3270 client (this tutorial uses x3270). On the top left corner, click "File", then "File Transfer". (Figure 1.)

Do following steps : (Figure 2.) [[File:X3270-2.png|right|300px|thumb|Figure 2.]]
* On "Local File Name" box, enter '''alpine.znetboot''' (the file in your laptop/workstation, at '''~/alpine.znetboot''')
* On "Host File Name" box, enter '''alpine znetboot''' (the file will be in z/VM console)

{{Note|Beware the difference between '''the dot <code>.</code>''' and '''the space <code> </code>''' characters in the file names.}}

* Choose '''Send to host'''
* Choose '''Host is VM/CMS'''
* Choose either '''Fixed''' or '''Variable''' for '''Record Format'''
:Enter a number for LRECL and BLKSIZE, respectively
{{Note|Any line in '''alpine.znetboot''' that has more 80 chars (columns) will be splitted into more than 1 line when uploaded to z/VM (CMS) console via 3270. Count the number of characters/column of the longest line in your '''alpine.znetboot''' and fill it in LRECL. There is no restriction for BLKSIZE but 80 is preferred.}}

* Click '''Transfer File''' box

Repeat the same steps with <code>znetboot.exec</code> and <code>curl.rexx</code> files.

==== (Optional) Check the configuration files ====
On 3270 client, enter following commands to check if the configuration files are correctly transferred:

<code>xedit alpine znetboot</code>

<code>xedit znetboot exec</code>

<code>xedit curl rex</code>

or <code>filel</code> and put <code>xedit</code> on CMD column to edit respective file.

==== Start ZNETBOOT ====
On 3270 client, type below command and wait till Figure 3.: [[File:X3270-3.png|right|300px|thumb|Figure 3.]]

<code>znetboot alpine</code>

= 4. Installation =
If you install on z/VM, steps in this part does not involve the interaction with the 3270 client anymore. Everything is done in the terminal with SSH client.

If you install on KVM, you can either SSH into the installer (below) or directly use the console starting qemu.

Either installing in KVM or z/VM environments, from your workstation/laptop, you will be able to run:
$ ssh root@192.168.1.2 (change ip address to what you specified earlier)

Remaining steps are similar to installing Alpine on other architectures (x86, arm, ppc, etc.), either on KVM (using virtio/SCSI disks) or on z/VM with FBA DASDs. Installing on ECKD DASDs requires an additional step, as described below.

== Example ==
Below is the detailed walkthrough of installing Alpine on a single ECKD DASD using LVM and extend that LVM to the second ECKD DASD.

After SSH-ing into the Alpine installer, run:
# setup-alpine

<code>Select keyboard layout [none]:</code>
:press Enter for none

<code>Enter system hostname (short form, e.g. 'foo') [localhost]:</code>
:enter your hostname

<pre>
Available interfaces are: eth0.
Enter '?' for help on bridges, bonding and vlans.
Which one do you want to initialize? (or '?' or 'done') [eth0]:</pre>
:type 'eth0' or press Enter

<code>Ip address for eth0? (or 'dhcp', 'none', '?') [192.168.1.2]</code>
:enter ip address or 'dhcp'

<code>Netmask? [255.255.255.0]</code>
:enter netmask
<code>Gateway? (or 'none') [192.168.1.1]</code>
:enter gateway's ip address

<code>Do you want to do any manual network configuration? [no]</code>
:enter 'no' or press Enter

<code>DNS domain name? (e.g 'bar.com') []</code>
:enter domain name or press Enter for none

<code>DNS nameserver(s)? [8.8.8.8 ]</code>
:enter DNS nameserver

<code>Changing password for root</code>
:enter root password

<code>Which timezone are you in? ('?' for list) [UTC]</code>
:enter timezone or '?' for list of timezones

<code>HTTP/FTP proxy URL? (e.g. 'http://proxy:8080', or 'none') [none]</code>
:enter proxy or press Enter for none

<code>Enter mirror number (1-27) or URL to add (or r/f/e/done) [f]:</code>
:enter a number or 'r' or 'f' or 'e' or 'done' as described

<code>Which SSH server? ('openssh', 'dropbear' or 'none') [openssh]</code>
:enter SSH server or press Enter for openssh

<code>Which NTP client to run? ('busybox', 'openntpd', 'chrony' or 'none') [chrony]</code>
:enter 'busybox' or press Enter for chrony

''' (next step is the additional step for ECKD DASDs on z/VM)'''
<pre>
Available ECKD DASD(s) are:
0.0.04c0 (3390/0c 3990/e9 IBM)
0.0.05d1 (3390/0c 3990/e9 IBM)
Which ECKD DASD(s) would you like to be formatted using dasdfmt? (enter '?' for help) [all]</pre>
:enter 'all' or '0.0.04c0 0.0.05d1' '''(separated by a space)''' to format all/both DASDs
:enter '0.0.04c0' or '0.0.05d1' to format respective DASD
:enter '?' for help

<code>WARNING: Erase ECKD DASD 0.0.04c0? [y/N]:</code>
:enter 'y' to format

<pre>
Available disks are:
dasda (2.5 GB IBM 0.0.04c0)
Which disk(s) would you like to use? (or '?' for help or 'none') [dasda]</pre>
:enter 'dasda' or press Enter

<pre>
The following disk is selected:
dasda (2.5 GB IBM 0.0.04c0)
How would you like to use it? ('sys', 'data', 'lvm' or '?' for help) [?]</pre>
:enter 'lvm'

<pre>
The following disk is selected (with LVM):
dasda (2.5 GB IBM 0.0.04c0)
How would you like to use it? ('sys', 'data' or '?' for help) [?]</pre>
:enter 'sys' to install Alpine on disk

<pre>
WARNING: The following disk(s) will be erased:
dasda (2.5 GB IBM 0.0.04c0)
WARNING: Erase the above disk(s) and continue? [y/N]:</pre>
:enter 'y'

<code>Installation is complete. Please reboot.</code>
:the installation is finished

At this point, don't poweroff the installer right away. Go to [https://wiki.alpinelinux.org/wiki/S390x#Copying_SSH_keys_to_new_Alpine_system "Copying SSH keys to new Alpine system"] (below) to have SSH access to your new Alpine system.

== Copying SSH keys to new Alpine system ==

By default, Alpine disables root login with a password via SSH. SSH keys are used instead.

After the installer's done running (<code>Installation is complete. Please reboot.</code>), there are 2 ways to copy your SSH key into the new Alpine system:
* Option 1: mount the installed disk and copy the SSH keys while still at the installer's terminal
* Option 2: poweroff the installer, start the new Alpine system and directly add the SSH keys
::: if you install on KVM, boot the new Alpine system on qemu, and copy the SSH keys
::: if you install on z/VM, use the 3270 client to ipl the new Alpine system and copy the SSH keys

'''Option 1'''

If you use 'lvm' + 'sys' installation (like in above example), do:

:<code> # mount /dev/vg0/lv_root /mnt</code>

:<code> # cp -ar /root/.ssh /mnt/root</code>

If you use 'sys' (without LVM) installation, do:

:<code> # mount /dev/dasda3 /mnt</code> (change dasda to dasdb or dasdc, etc. for whichever DASD you chose)

:<code> # cp -ar /root/.ssh /mnt/root</code>

{{Note|In 'sys' installation, 1st partition is boot, 2nd partition is swap, 3rd partition is root }}

Then run <code> # poweroff</code>.

Go to [https://wiki.alpinelinux.org/wiki/S390x#Login_to_new_Alpine_system "Login to new Alpine system"]

'''Option 2'''

Run <code> # poweroff</code>.

If you use KVM, start qemu with new Alpine system (removing <code>-kernel</code>, <code>-initrd</code>, <code>-append</code> options)

If you use z/VM, open the 3270 client, login with your z/VM username and password. You may need to run <code> ipl cms</code>. Then run <code> ipl 04c0</code> (or whichever DASD device you chose as root disk in earlier steps).

Wait for new Alpine system go up, then login as root user while in the qemu console (on KVM) or 3270 client (on z/VM). Then run:
::<code> # mkdir /root/.ssh</code>
::<code> # wget https://your-website.com/your-ssh-key.pub -O /root/.ssh/authorized_keys</code>
::<code> # chmod 700 /root/.ssh</code>
::<code> # chmod 600 /root/.ssh/authorized_keys</code>

Go to [https://wiki.alpinelinux.org/wiki/S390x#Login_to_new_Alpine_system "Login to new Alpine system"]

== Login to new Alpine system ==
On your workstation/laptop, use SSH client to login new Alpine system:
<code> $ ssh root@192.168.1.2</code> (or whichever ip address you used)

== Extending LVM volume ==
After logging in to your new Alpine system, run:
<pre>
# apk add -q util-linux e2fsprogs-extra

# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
dasda 94:0 0 2.3G 0 disk
├─dasda1 94:1 0 100M 0 part /boot
└─dasda2 94:2 0 2.2G 0 part
├─vg0-lv_swap 254:0 0 588M 0 lvm [SWAP]
└─vg0-lv_root 254:1 0 1.6G 0 lvm /
dasdb 94:4 0 2.3G 0 disk

# dasdfmt -b 4096 -d cdl -yp /dev/dasdb

# fdasd -a /dev/dasdb

# pvcreate /dev/dasdb1

# vgextend vg0 /dev/dasdb1

# lvextend -l +100%FREE /dev/vg0/lv_root

# resize2fs /dev/vg0/lv_root

# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
dasda 94:0 0 2.3G 0 disk
├─dasda1 94:1 0 100M 0 part /boot
└─dasda2 94:2 0 2.2G 0 part
├─vg0-lv_swap 254:0 0 588M 0 lvm [SWAP]
└─vg0-lv_root 254:1 0 3.9G 0 lvm /
dasdb 94:4 0 2.3G 0 disk
└─dasdb1 94:5 0 2.3G 0 part
└─vg0-lv_root 254:1 0 3.9G 0 lvm /
</pre>

= 5. Tips =
If you want to disable swap partition, after finishing NTP client step, quit the installer by pressing <code>Ctrl + C</code>. Then run following command to complete remaining steps:

<code># setup-disk -s 0</code>

{{Note|If you do 'sys' installation, there will be no swap partition anymore and 1st partition will be boot, 2nd partition will be root}}

S390x/Installation

2019-05-09T20:11:44Z

Tmhoang: /* Using netboot media */

= 1. Known Issues =
1. Installation on 2 or more DASDs (either ECKD and FBA) on z/VM is not supported in the installer script (<code>setup-alpine</code>) at the moment. If you want to install/extend on more than 1 DASD, see [https://wiki.alpinelinux.org/wiki/S390x#Extending_LVM_volume "Extending LVM volume"]. However, installation on 2 or more virtio (SCSI) disks on KVM are supported just like other architectures.

= 2. The boot media =

For KVM, both ISO image and netboot media (kernel and initramfs) are supported.

For z/VM, netboot media is supported.

For LPAR, not yet supported.

Boot media are found at:

* http://dl-cdn.alpinelinux.org/alpine/v3.9/releases/s390x/

== Kernel parameters (and parmfile) ==
The Alpine s390x boot media requires following kernel parameters to work: (Details at : <code>https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt</code>)

<code>ip=dhcp</code> : use DHCP for network configuration.

<code>ip=client-ip:server-ip:gw-ip:netmask:hostname:device:autoconf:dns1:dns2</code> : use static IP configuration, each field is separated by a colon <code>:</code>
* <code>client-ip</code> ip address of the guest VM where we are going to run the installer
* <code>server-ip</code> not used, leave blank or fill with <code>none</code>
* <code>gw-ip</code> the gateway ip address
* <code>netmask</code> the netmask
* <code>hostname</code> not used, leave blank or fill with <code>none</code>
* <code>device</code> the network interface of the guest VM, default is <code>eth0</code> if left blank
* <code>autoconf</code> not used, leave blank or fill with <code>none</code> or <code>off</code>
* <code>dns1</code> address of the DNS server
* <code>dns2</code> address of the 2nd DNS server

<code>alpine_repo=</code> : the location of the Alpine repository from which packages are downloaded.

:For stable release, use <code>http://dl-cdn.alpinelinux.org/alpine/v3.9/main</code>

:For rolling release, use <code>http://dl-cdn.alpinelinux.org/alpine/edge/main</code>

<code>modloop=</code> : the remote location of the image containing kernel's modules, required for LVM and raid setup.

:The remote location of the <code>modloop</code> image is the same as the kernel and initramfs (see below).

<code>ssh_key=</code> : the remote location of your SSH public key which is used to allow SSH connection into the installer. It will be downloaded and copied into <code>/root/.ssh/authorized_keys</code> in the installer.

{{Note|Fetching public keys from HTTP, HTTPS and FTPS are supported. HTTP should only be used in local development network where you own the network.}}

{{Note|Alpine Linux security policies are against using passwords for root access via SSH as we consider using public-private key pairs is a much better approach.}}

'''z/VM only'''

<code>dasd=</code> : the addresses of the DASD devices, either ECKD or FBA DASDs. Each device is separated with a comma.

<code>s390x_net=</code> : the network interface type and its subchannels. At the moment, only QETH layer 2 is supported, thus the name <code>qeth_l2</code> is used (see below).

= 3. Pre-installation =

== KVM ==
Create a virtual disk:
$ qemu-img create alpine_disk.qcow2 5G

==== Using iso image ====
Download latest iso image from : http://dl-cdn.alpinelinux.org/alpine/v3.9/releases/s390x

Start qemu:

$ qemu-system-s390x -M s390-ccw-virtio \
-m 1024 -smp 2 -nographic -enable-kvm \
-net nic -net tap,ifname=tap0,script=no \
-hda alpine_disk.qcow2 \
-boot d -cdrom alpine-standard-3.9.0-s390x.iso

==== Using netboot media ====
Download the latest [http://dl-cdn.alpinelinux.org/alpine/v3.9/releases/s390x/netboot/vmlinuz-vanilla kernel] and [http://dl-cdn.alpinelinux.org/alpine/v3.9/releases/s390x/netboot/initramfs-vanilla initramfs].

Start qemu: (modify <code>ip=</code> <code>alpine_repo=</code> <code>ssh_key=</code> for your needs)

$ qemu-system-s390x -M s390-ccw-virtio \
-m 1024 -smp 2 -nographic -enable-kvm \
-net nic -net tap,ifname=tap0,script=no \
-hda alpine_disk.qcow2 \
-kernel vmlinuz-vanilla \
-initrd initramfs-vanilla \
-append "ip=192.168.1.2::192.168.1.1:255.255.255.0::::8.8.8.8:1.1.1.1 alpine_repo=http://dl-cdn.alpinelinux.org/alpine/v3.9/main modloop=http://dl-cdn.alpinelinux.org/alpine/v3.9/releases/s390x/netboot/modloop-vanilla ssh_key=https://your-website.com/your-ssh-key.pub"

{{Note|If you have direct access to the qemu console, <code>ssh_key</code> might not be required.}}

== z/VM ==
To ease out the process of downloading the images, punch the readers, ipl, etc., [https://github.com/trothr/znetboot '''ZNETBOOT'''] is used.

==== Create the parm file ====
On your workstation/laptop, create a file named <code>alpine.znetboot</code> in your home directory with contents below (modify <code>dasd=</code><code>s390x_net=</code> <code>ip=</code> <code>alpine_repo=</code> <code>ssh_key=</code> for your needs)

<pre>
ZNETBOOT_KERNEL=http://dl-cdn.alpinelinux.org/alpine/v3.9/releases/s390x/netboot/vmlinuz-vanilla
ZNETBOOT_INITRD=http://dl-cdn.alpinelinux.org/alpine/v3.9/releases/s390x/netboot/initramfs-vanilla
ZNETBOOT_PROGRESS=1M

alpine_repo=http://dl-cdn.alpinelinux.org/alpine/v3.9/main
modloop=http://dl-cdn.alpinelinux.org/alpine/v3.9/releases/s390x/netboot/modloop-vanilla

dasd=0.0.04c0,0.0.05d1
s390x_net=qeth_l2,0.0.0560,0.0.0561,0.0.0562
ip=192.168.1.2::192.168.1.1:255.255.255.0:none:eth0:none:8.8.8.8

ssh_key=https://your-website.com/your-ssh-key.pub

</pre>

==== Upload to z/VM system via 3270 client ====
[[File:X3270-1.png|right|300px|thumb|Figure 1.]]
On your workstation/laptop, download 2 files [https://raw.githubusercontent.com/trothr/znetboot/master/znetboot.exec <code>znetboot.exec</code>], and [https://raw.githubusercontent.com/trothr/znetboot/master/curl.rexx <code>curl.rexx</code>] to your home directory.

Open 3270 client and log in the z/VM system with your z/VM username and password.

Upload 3 files <code>alpine.znetboot</code>, <code>znetboot.exec</code>, <code>curl.rexx</code> to the z/VM environment using the 3270 client (this tutorial uses x3270). On the top left corner, click "File", then "File Transfer". (Figure 1.)

Do following steps : (Figure 2.) [[File:X3270-2.png|right|300px|thumb|Figure 2.]]
* On "Local File Name" box, enter '''alpine.znetboot''' (the file in your laptop/workstation, at '''~/alpine.znetboot''')
* On "Host File Name" box, enter '''alpine znetboot''' (the file will be in z/VM console)

{{Note|Beware the difference between '''the dot <code>.</code>''' and '''the space <code> </code>''' characters in the file names.}}

* Choose '''Send to host'''
* Choose '''Host is VM/CMS'''
* Choose either '''Fixed''' or '''Variable''' for '''Record Format'''
:Enter a number for LRECL and BLKSIZE, respectively
{{Note|Any line in '''alpine.znetboot''' that has more 80 chars (columns) will be splitted into more than 1 line when uploaded to z/VM (CMS) console via 3270. Count the number of characters/column of the longest line in your '''alpine.znetboot''' and fill it in LRECL. There is no restriction for BLKSIZE but 80 is preferred.}}

* Click '''Transfer File''' box

Repeat the same steps with <code>znetboot.exec</code> and <code>curl.rexx</code> files.

==== (Optional) Check the configuration files ====
On 3270 client, enter following commands to check if the configuration files are correctly transferred:

<code>xedit alpine znetboot</code>

<code>xedit znetboot exec</code>

<code>xedit curl rex</code>

or <code>filel</code> and put <code>xedit</code> on CMD column to edit respective file.

==== Start ZNETBOOT ====
On 3270 client, type below command and wait till Figure 3.: [[File:X3270-3.png|right|300px|thumb|Figure 3.]]

<code>znetboot alpine</code>

= 4. Installation =
If you install on z/VM, steps in this part does not involve the interaction with the 3270 client anymore. Everything is done in the terminal with SSH client.

If you install on KVM, you can either SSH into the installer (below) or directly use the console starting qemu.

Either installing in KVM or z/VM environments, from your workstation/laptop, you will be able to run:
$ ssh root@192.168.1.2 (change ip address to what you specified earlier)

Remaining steps are similar to installing Alpine on other architectures (x86, arm, ppc, etc.), either on KVM (using virtio/SCSI disks) or on z/VM with FBA DASDs. Installing on ECKD DASDs requires an additional step, as described below.

== Example ==
Below is the detailed walkthrough of installing Alpine on a single ECKD DASD using LVM and extend that LVM to the second ECKD DASD.

After SSH-ing into the Alpine installer, run:
# setup-alpine

<code>Select keyboard layout [none]:</code>
:press Enter for none

<code>Enter system hostname (short form, e.g. 'foo') [localhost]:</code>
:enter your hostname

<pre>
Available interfaces are: eth0.
Enter '?' for help on bridges, bonding and vlans.
Which one do you want to initialize? (or '?' or 'done') [eth0]:</pre>
:type 'eth0' or press Enter

<code>Ip address for eth0? (or 'dhcp', 'none', '?') [192.168.1.2]</code>
:enter ip address or 'dhcp'

<code>Netmask? [255.255.255.0]</code>
:enter netmask
<code>Gateway? (or 'none') [192.168.1.1]</code>
:enter gateway's ip address

<code>Do you want to do any manual network configuration? [no]</code>
:enter 'no' or press Enter

<code>DNS domain name? (e.g 'bar.com') []</code>
:enter domain name or press Enter for none

<code>DNS nameserver(s)? [8.8.8.8 ]</code>
:enter DNS nameserver

<code>Changing password for root</code>
:enter root password

<code>Which timezone are you in? ('?' for list) [UTC]</code>
:enter timezone or '?' for list of timezones

<code>HTTP/FTP proxy URL? (e.g. 'http://proxy:8080', or 'none') [none]</code>
:enter proxy or press Enter for none

<code>Enter mirror number (1-27) or URL to add (or r/f/e/done) [f]:</code>
:enter a number or 'r' or 'f' or 'e' or 'done' as described

<code>Which SSH server? ('openssh', 'dropbear' or 'none') [openssh]</code>
:enter SSH server or press Enter for openssh

<code>Which NTP client to run? ('busybox', 'openntpd', 'chrony' or 'none') [chrony]</code>
:enter 'busybox' or press Enter for chrony

''' (next step is the additional step for ECKD DASDs on z/VM)'''
<pre>
Available ECKD DASD(s) are:
0.0.04c0 (3390/0c 3990/e9 IBM)
0.0.05d1 (3390/0c 3990/e9 IBM)
Which ECKD DASD(s) would you like to be formatted using dasdfmt? (enter '?' for help) [all]</pre>
:enter 'all' or '0.0.04c0 0.0.05d1' '''(separated by a space)''' to format all/both DASDs
:enter '0.0.04c0' or '0.0.05d1' to format respective DASD
:enter '?' for help

<code>WARNING: Erase ECKD DASD 0.0.04c0? [y/N]:</code>
:enter 'y' to format

<pre>
Available disks are:
dasda (2.5 GB IBM 0.0.04c0)
Which disk(s) would you like to use? (or '?' for help or 'none') [dasda]</pre>
:enter 'dasda' or press Enter

<pre>
The following disk is selected:
dasda (2.5 GB IBM 0.0.04c0)
How would you like to use it? ('sys', 'data', 'lvm' or '?' for help) [?]</pre>
:enter 'lvm'

<pre>
The following disk is selected (with LVM):
dasda (2.5 GB IBM 0.0.04c0)
How would you like to use it? ('sys', 'data' or '?' for help) [?]</pre>
:enter 'sys' to install Alpine on disk

<pre>
WARNING: The following disk(s) will be erased:
dasda (2.5 GB IBM 0.0.04c0)
WARNING: Erase the above disk(s) and continue? [y/N]:</pre>
:enter 'y'

<code>Installation is complete. Please reboot.</code>
:the installation is finished

At this point, don't poweroff the installer right away. Go to [https://wiki.alpinelinux.org/wiki/S390x#Copying_SSH_keys_to_new_Alpine_system "Copying SSH keys to new Alpine system"] (below) to have SSH access to your new Alpine system.

== Copying SSH keys to new Alpine system ==

By default, Alpine disables root login with a password via SSH. SSH keys are used instead.

After the installer's done running (<code>Installation is complete. Please reboot.</code>), there are 2 ways to copy your SSH key into the new Alpine system:
* Option 1: mount the installed disk and copy the SSH keys while still at the installer's terminal
* Option 2: poweroff the installer, start the new Alpine system and directly add the SSH keys
::: if you install on KVM, boot the new Alpine system on qemu, and copy the SSH keys
::: if you install on z/VM, use the 3270 client to ipl the new Alpine system and copy the SSH keys

'''Option 1'''

If you use 'lvm' + 'sys' installation (like in above example), do:

:<code> # mount /dev/vg0/lv_root /mnt</code>

:<code> # cp -ar /root/.ssh /mnt/root</code>

If you use 'sys' (without LVM) installation, do:

:<code> # mount /dev/dasda3 /mnt</code> (change dasda to dasdb or dasdc, etc. for whichever DASD you chose)

:<code> # cp -ar /root/.ssh /mnt/root</code>

{{Note|In 'sys' installation, 1st partition is boot, 2nd partition is swap, 3rd partition is root }}

Then run <code> # poweroff</code>.

Go to [https://wiki.alpinelinux.org/wiki/S390x#Login_to_new_Alpine_system "Login to new Alpine system"]

'''Option 2'''

Run <code> # poweroff</code>.

If you use KVM, start qemu with new Alpine system (removing <code>-kernel</code>, <code>-initrd</code>, <code>-append</code> options)

If you use z/VM, open the 3270 client, login with your z/VM username and password. You may need to run <code> ipl cms</code>. Then run <code> ipl 04c0</code> (or whichever DASD device you chose as root disk in earlier steps).

Wait for new Alpine system go up, then login as root user while in the qemu console (on KVM) or 3270 client (on z/VM). Then run:
::<code> # mkdir /root/.ssh</code>
::<code> # wget https://your-website.com/your-ssh-key.pub -O /root/.ssh/authorized_keys</code>
::<code> # chmod 700 /root/.ssh</code>
::<code> # chmod 600 /root/.ssh/authorized_keys</code>

Go to [https://wiki.alpinelinux.org/wiki/S390x#Login_to_new_Alpine_system "Login to new Alpine system"]

== Login to new Alpine system ==
On your workstation/laptop, use SSH client to login new Alpine system:
<code> $ ssh root@192.168.1.2</code> (or whichever ip address you used)

== Extending LVM volume ==
After logging in to your new Alpine system, run:
<pre>
# apk add -q util-linux e2fsprogs-extra

# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
dasda 94:0 0 2.3G 0 disk
├─dasda1 94:1 0 100M 0 part /boot
└─dasda2 94:2 0 2.2G 0 part
├─vg0-lv_swap 254:0 0 588M 0 lvm [SWAP]
└─vg0-lv_root 254:1 0 1.6G 0 lvm /
dasdb 94:4 0 2.3G 0 disk

# dasdfmt -b 4096 -d cdl -yp /dev/dasdb

# fdasd -a /dev/dasdb

# pvcreate /dev/dasdb1

# vgextend vg0 /dev/dasdb1

# lvextend -l +100%FREE /dev/vg0/lv_root

# resize2fs /dev/vg0/lv_root

# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
dasda 94:0 0 2.3G 0 disk
├─dasda1 94:1 0 100M 0 part /boot
└─dasda2 94:2 0 2.2G 0 part
├─vg0-lv_swap 254:0 0 588M 0 lvm [SWAP]
└─vg0-lv_root 254:1 0 3.9G 0 lvm /
dasdb 94:4 0 2.3G 0 disk
└─dasdb1 94:5 0 2.3G 0 part
└─vg0-lv_root 254:1 0 3.9G 0 lvm /
</pre>

= 5. Tips =
If you want to disable swap partition, after finishing NTP client step, quit the installer by pressing <code>Ctrl + C</code>. Then run following command to complete remaining steps:

<code># setup-disk -s 0</code>

{{Note|If you do 'sys' installation, there will be no swap partition anymore and 1st partition will be boot, 2nd partition will be root}}

S390x/Installation

2019-05-09T20:05:27Z

Tmhoang: /* Kernel parameters (and parmfile) */

= 1. Known Issues =
1. Installation on 2 or more DASDs (either ECKD and FBA) on z/VM is not supported in the installer script (<code>setup-alpine</code>) at the moment. If you want to install/extend on more than 1 DASD, see [https://wiki.alpinelinux.org/wiki/S390x#Extending_LVM_volume "Extending LVM volume"]. However, installation on 2 or more virtio (SCSI) disks on KVM are supported just like other architectures.

= 2. The boot media =

For KVM, both ISO image and netboot media (kernel and initramfs) are supported.

For z/VM, netboot media is supported.

For LPAR, not yet supported.

Boot media are found at:

* http://dl-cdn.alpinelinux.org/alpine/v3.9/releases/s390x/

== Kernel parameters (and parmfile) ==
The Alpine s390x boot media requires following kernel parameters to work: (Details at : <code>https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt</code>)

<code>ip=dhcp</code> : use DHCP for network configuration.

<code>ip=client-ip:server-ip:gw-ip:netmask:hostname:device:autoconf:dns1:dns2</code> : use static IP configuration, each field is separated by a colon <code>:</code>
* <code>client-ip</code> ip address of the guest VM where we are going to run the installer
* <code>server-ip</code> not used, leave blank or fill with <code>none</code>
* <code>gw-ip</code> the gateway ip address
* <code>netmask</code> the netmask
* <code>hostname</code> not used, leave blank or fill with <code>none</code>
* <code>device</code> the network interface of the guest VM, default is <code>eth0</code> if left blank
* <code>autoconf</code> not used, leave blank or fill with <code>none</code> or <code>off</code>
* <code>dns1</code> address of the DNS server
* <code>dns2</code> address of the 2nd DNS server

<code>alpine_repo=</code> : the location of the Alpine repository from which packages are downloaded.

:For stable release, use <code>http://dl-cdn.alpinelinux.org/alpine/v3.9/main</code>

:For rolling release, use <code>http://dl-cdn.alpinelinux.org/alpine/edge/main</code>

<code>modloop=</code> : the remote location of the image containing kernel's modules, required for LVM and raid setup.

:The remote location of the <code>modloop</code> image is the same as the kernel and initramfs (see below).

<code>ssh_key=</code> : the remote location of your SSH public key which is used to allow SSH connection into the installer. It will be downloaded and copied into <code>/root/.ssh/authorized_keys</code> in the installer.

{{Note|Fetching public keys from HTTP, HTTPS and FTPS are supported. HTTP should only be used in local development network where you own the network.}}

{{Note|Alpine Linux security policies are against using passwords for root access via SSH as we consider using public-private key pairs is a much better approach.}}

'''z/VM only'''

<code>dasd=</code> : the addresses of the DASD devices, either ECKD or FBA DASDs. Each device is separated with a comma.

<code>s390x_net=</code> : the network interface type and its subchannels. At the moment, only QETH layer 2 is supported, thus the name <code>qeth_l2</code> is used (see below).

= 3. Pre-installation =

== KVM ==
Create a virtual disk:
$ qemu-img create alpine_disk.qcow2 5G

==== Using iso image ====
Download latest iso image from : http://dl-cdn.alpinelinux.org/alpine/v3.9/releases/s390x

Start qemu:

$ qemu-system-s390x -M s390-ccw-virtio \
-m 1024 -smp 2 -nographic -enable-kvm \
-net nic -net tap,ifname=tap0,script=no \
-hda alpine_disk.qcow2 \
-boot d -cdrom alpine-standard-3.9.0-s390x.iso

==== Using netboot media ====
Download the latest [http://dl-cdn.alpinelinux.org/alpine/v3.9/releases/s390x/netboot/vmlinuz-vanilla kernel] and [http://dl-cdn.alpinelinux.org/alpine/v3.9/releases/s390x/netboot/initramfs-vanilla initramfs].

Start qemu: (modify <code>ip=</code> <code>alpine_repo=</code> <code>ssh_key=</code> for your needs)

$ qemu-system-s390x -M s390-ccw-virtio \
-m 1024 -smp 2 -nographic -enable-kvm \
-net nic -net tap,ifname=tap0,script=no \
-hda alpine_disk.qcow2 \
-kernel vmlinuz-vanilla \
-initrd initramfs-vanilla \
-append "ip=192.168.1.2::192.168.1.1:255.255.255.0:none:eth0:none:8.8.8.8 alpine_repo=http://dl-cdn.alpinelinux.org/alpine/v3.9/main modloop=http://dl-cdn.alpinelinux.org/alpine/v3.9/releases/s390x/netboot/modloop-vanilla ssh_key=https://your-website.com/your-ssh-key.pub"

{{Note|If you have direct access to the qemu console, <code>ssh_key</code> might not be required.}}

== z/VM ==
To ease out the process of downloading the images, punch the readers, ipl, etc., [https://github.com/trothr/znetboot '''ZNETBOOT'''] is used.

==== Create the parm file ====
On your workstation/laptop, create a file named <code>alpine.znetboot</code> in your home directory with contents below (modify <code>dasd=</code><code>s390x_net=</code> <code>ip=</code> <code>alpine_repo=</code> <code>ssh_key=</code> for your needs)

<pre>
ZNETBOOT_KERNEL=http://dl-cdn.alpinelinux.org/alpine/v3.9/releases/s390x/netboot/vmlinuz-vanilla
ZNETBOOT_INITRD=http://dl-cdn.alpinelinux.org/alpine/v3.9/releases/s390x/netboot/initramfs-vanilla
ZNETBOOT_PROGRESS=1M

alpine_repo=http://dl-cdn.alpinelinux.org/alpine/v3.9/main
modloop=http://dl-cdn.alpinelinux.org/alpine/v3.9/releases/s390x/netboot/modloop-vanilla

dasd=0.0.04c0,0.0.05d1
s390x_net=qeth_l2,0.0.0560,0.0.0561,0.0.0562
ip=192.168.1.2::192.168.1.1:255.255.255.0:none:eth0:none:8.8.8.8

ssh_key=https://your-website.com/your-ssh-key.pub

</pre>

==== Upload to z/VM system via 3270 client ====
[[File:X3270-1.png|right|300px|thumb|Figure 1.]]
On your workstation/laptop, download 2 files [https://raw.githubusercontent.com/trothr/znetboot/master/znetboot.exec <code>znetboot.exec</code>], and [https://raw.githubusercontent.com/trothr/znetboot/master/curl.rexx <code>curl.rexx</code>] to your home directory.

Open 3270 client and log in the z/VM system with your z/VM username and password.

Upload 3 files <code>alpine.znetboot</code>, <code>znetboot.exec</code>, <code>curl.rexx</code> to the z/VM environment using the 3270 client (this tutorial uses x3270). On the top left corner, click "File", then "File Transfer". (Figure 1.)

Do following steps : (Figure 2.) [[File:X3270-2.png|right|300px|thumb|Figure 2.]]
* On "Local File Name" box, enter '''alpine.znetboot''' (the file in your laptop/workstation, at '''~/alpine.znetboot''')
* On "Host File Name" box, enter '''alpine znetboot''' (the file will be in z/VM console)

{{Note|Beware the difference between '''the dot <code>.</code>''' and '''the space <code> </code>''' characters in the file names.}}

* Choose '''Send to host'''
* Choose '''Host is VM/CMS'''
* Choose either '''Fixed''' or '''Variable''' for '''Record Format'''
:Enter a number for LRECL and BLKSIZE, respectively
{{Note|Any line in '''alpine.znetboot''' that has more 80 chars (columns) will be splitted into more than 1 line when uploaded to z/VM (CMS) console via 3270. Count the number of characters/column of the longest line in your '''alpine.znetboot''' and fill it in LRECL. There is no restriction for BLKSIZE but 80 is preferred.}}

* Click '''Transfer File''' box

Repeat the same steps with <code>znetboot.exec</code> and <code>curl.rexx</code> files.

==== (Optional) Check the configuration files ====
On 3270 client, enter following commands to check if the configuration files are correctly transferred:

<code>xedit alpine znetboot</code>

<code>xedit znetboot exec</code>

<code>xedit curl rex</code>

or <code>filel</code> and put <code>xedit</code> on CMD column to edit respective file.

==== Start ZNETBOOT ====
On 3270 client, type below command and wait till Figure 3.: [[File:X3270-3.png|right|300px|thumb|Figure 3.]]

<code>znetboot alpine</code>

= 4. Installation =
If you install on z/VM, steps in this part does not involve the interaction with the 3270 client anymore. Everything is done in the terminal with SSH client.

If you install on KVM, you can either SSH into the installer (below) or directly use the console starting qemu.

Either installing in KVM or z/VM environments, from your workstation/laptop, you will be able to run:
$ ssh root@192.168.1.2 (change ip address to what you specified earlier)

Remaining steps are similar to installing Alpine on other architectures (x86, arm, ppc, etc.), either on KVM (using virtio/SCSI disks) or on z/VM with FBA DASDs. Installing on ECKD DASDs requires an additional step, as described below.

== Example ==
Below is the detailed walkthrough of installing Alpine on a single ECKD DASD using LVM and extend that LVM to the second ECKD DASD.

After SSH-ing into the Alpine installer, run:
# setup-alpine

<code>Select keyboard layout [none]:</code>
:press Enter for none

<code>Enter system hostname (short form, e.g. 'foo') [localhost]:</code>
:enter your hostname

<pre>
Available interfaces are: eth0.
Enter '?' for help on bridges, bonding and vlans.
Which one do you want to initialize? (or '?' or 'done') [eth0]:</pre>
:type 'eth0' or press Enter

<code>Ip address for eth0? (or 'dhcp', 'none', '?') [192.168.1.2]</code>
:enter ip address or 'dhcp'

<code>Netmask? [255.255.255.0]</code>
:enter netmask
<code>Gateway? (or 'none') [192.168.1.1]</code>
:enter gateway's ip address

<code>Do you want to do any manual network configuration? [no]</code>
:enter 'no' or press Enter

<code>DNS domain name? (e.g 'bar.com') []</code>
:enter domain name or press Enter for none

<code>DNS nameserver(s)? [8.8.8.8 ]</code>
:enter DNS nameserver

<code>Changing password for root</code>
:enter root password

<code>Which timezone are you in? ('?' for list) [UTC]</code>
:enter timezone or '?' for list of timezones

<code>HTTP/FTP proxy URL? (e.g. 'http://proxy:8080', or 'none') [none]</code>
:enter proxy or press Enter for none

<code>Enter mirror number (1-27) or URL to add (or r/f/e/done) [f]:</code>
:enter a number or 'r' or 'f' or 'e' or 'done' as described

<code>Which SSH server? ('openssh', 'dropbear' or 'none') [openssh]</code>
:enter SSH server or press Enter for openssh

<code>Which NTP client to run? ('busybox', 'openntpd', 'chrony' or 'none') [chrony]</code>
:enter 'busybox' or press Enter for chrony

''' (next step is the additional step for ECKD DASDs on z/VM)'''
<pre>
Available ECKD DASD(s) are:
0.0.04c0 (3390/0c 3990/e9 IBM)
0.0.05d1 (3390/0c 3990/e9 IBM)
Which ECKD DASD(s) would you like to be formatted using dasdfmt? (enter '?' for help) [all]</pre>
:enter 'all' or '0.0.04c0 0.0.05d1' '''(separated by a space)''' to format all/both DASDs
:enter '0.0.04c0' or '0.0.05d1' to format respective DASD
:enter '?' for help

<code>WARNING: Erase ECKD DASD 0.0.04c0? [y/N]:</code>
:enter 'y' to format

<pre>
Available disks are:
dasda (2.5 GB IBM 0.0.04c0)
Which disk(s) would you like to use? (or '?' for help or 'none') [dasda]</pre>
:enter 'dasda' or press Enter

<pre>
The following disk is selected:
dasda (2.5 GB IBM 0.0.04c0)
How would you like to use it? ('sys', 'data', 'lvm' or '?' for help) [?]</pre>
:enter 'lvm'

<pre>
The following disk is selected (with LVM):
dasda (2.5 GB IBM 0.0.04c0)
How would you like to use it? ('sys', 'data' or '?' for help) [?]</pre>
:enter 'sys' to install Alpine on disk

<pre>
WARNING: The following disk(s) will be erased:
dasda (2.5 GB IBM 0.0.04c0)
WARNING: Erase the above disk(s) and continue? [y/N]:</pre>
:enter 'y'

<code>Installation is complete. Please reboot.</code>
:the installation is finished

At this point, don't poweroff the installer right away. Go to [https://wiki.alpinelinux.org/wiki/S390x#Copying_SSH_keys_to_new_Alpine_system "Copying SSH keys to new Alpine system"] (below) to have SSH access to your new Alpine system.

== Copying SSH keys to new Alpine system ==

By default, Alpine disables root login with a password via SSH. SSH keys are used instead.

After the installer's done running (<code>Installation is complete. Please reboot.</code>), there are 2 ways to copy your SSH key into the new Alpine system:
* Option 1: mount the installed disk and copy the SSH keys while still at the installer's terminal
* Option 2: poweroff the installer, start the new Alpine system and directly add the SSH keys
::: if you install on KVM, boot the new Alpine system on qemu, and copy the SSH keys
::: if you install on z/VM, use the 3270 client to ipl the new Alpine system and copy the SSH keys

'''Option 1'''

If you use 'lvm' + 'sys' installation (like in above example), do:

:<code> # mount /dev/vg0/lv_root /mnt</code>

:<code> # cp -ar /root/.ssh /mnt/root</code>

If you use 'sys' (without LVM) installation, do:

:<code> # mount /dev/dasda3 /mnt</code> (change dasda to dasdb or dasdc, etc. for whichever DASD you chose)

:<code> # cp -ar /root/.ssh /mnt/root</code>

{{Note|In 'sys' installation, 1st partition is boot, 2nd partition is swap, 3rd partition is root }}

Then run <code> # poweroff</code>.

Go to [https://wiki.alpinelinux.org/wiki/S390x#Login_to_new_Alpine_system "Login to new Alpine system"]

'''Option 2'''

Run <code> # poweroff</code>.

If you use KVM, start qemu with new Alpine system (removing <code>-kernel</code>, <code>-initrd</code>, <code>-append</code> options)

If you use z/VM, open the 3270 client, login with your z/VM username and password. You may need to run <code> ipl cms</code>. Then run <code> ipl 04c0</code> (or whichever DASD device you chose as root disk in earlier steps).

Wait for new Alpine system go up, then login as root user while in the qemu console (on KVM) or 3270 client (on z/VM). Then run:
::<code> # mkdir /root/.ssh</code>
::<code> # wget https://your-website.com/your-ssh-key.pub -O /root/.ssh/authorized_keys</code>
::<code> # chmod 700 /root/.ssh</code>
::<code> # chmod 600 /root/.ssh/authorized_keys</code>

Go to [https://wiki.alpinelinux.org/wiki/S390x#Login_to_new_Alpine_system "Login to new Alpine system"]

== Login to new Alpine system ==
On your workstation/laptop, use SSH client to login new Alpine system:
<code> $ ssh root@192.168.1.2</code> (or whichever ip address you used)

== Extending LVM volume ==
After logging in to your new Alpine system, run:
<pre>
# apk add -q util-linux e2fsprogs-extra

# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
dasda 94:0 0 2.3G 0 disk
├─dasda1 94:1 0 100M 0 part /boot
└─dasda2 94:2 0 2.2G 0 part
├─vg0-lv_swap 254:0 0 588M 0 lvm [SWAP]
└─vg0-lv_root 254:1 0 1.6G 0 lvm /
dasdb 94:4 0 2.3G 0 disk

# dasdfmt -b 4096 -d cdl -yp /dev/dasdb

# fdasd -a /dev/dasdb

# pvcreate /dev/dasdb1

# vgextend vg0 /dev/dasdb1

# lvextend -l +100%FREE /dev/vg0/lv_root

# resize2fs /dev/vg0/lv_root

# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
dasda 94:0 0 2.3G 0 disk
├─dasda1 94:1 0 100M 0 part /boot
└─dasda2 94:2 0 2.2G 0 part
├─vg0-lv_swap 254:0 0 588M 0 lvm [SWAP]
└─vg0-lv_root 254:1 0 3.9G 0 lvm /
dasdb 94:4 0 2.3G 0 disk
└─dasdb1 94:5 0 2.3G 0 part
└─vg0-lv_root 254:1 0 3.9G 0 lvm /
</pre>

= 5. Tips =
If you want to disable swap partition, after finishing NTP client step, quit the installer by pressing <code>Ctrl + C</code>. Then run following command to complete remaining steps:

<code># setup-disk -s 0</code>

{{Note|If you do 'sys' installation, there will be no swap partition anymore and 1st partition will be boot, 2nd partition will be root}}

S390x/Tips

2019-04-05T09:42:40Z

Tmhoang: Redirected page to S390x/tips

#REDIRECT [[S390x/tips]]

S390x

2019-04-05T09:41:08Z

Tmhoang:

= Installation guide =
Visit: https://wiki.alpinelinux.org/wiki/S390x/Installation

= Docker with Alpine =
Running Alpine s390x containers on Docker: https://wiki.alpinelinux.org/wiki/S390x/Docker

= Known Issues =
https://wiki.alpinelinux.org/wiki/S390x/Known_Issues

= s390-tools =
https://wiki.alpinelinux.org/wiki/S390x/s390-tools

= Tips =
https://wiki.alpinelinux.org/wiki/S390x/Tips

S390x

2019-04-05T09:36:05Z

Tmhoang:

S390x

2019-03-18T16:04:24Z

Tmhoang:

S390x/s390-tools

2019-03-18T16:04:05Z

Tmhoang: Created page with "Place holder."

Place holder.

S390X

2019-03-18T16:03:29Z

Tmhoang: Created page with "https://wiki.alpinelinux.org/wiki/s390x"

https://wiki.alpinelinux.org/wiki/s390x

User:Tmhoang

2019-03-18T13:56:22Z

Tmhoang:

Personal notes

https://pi3g.com/2019/01/10/alpine-boot-process-on-the-raspberry-pi/

https://wiki.alpinelinux.org/wiki/Setting_up_a_OpenVPN_server

https://wiki.alpinelinux.org/wiki/Running_Alpine_Linux_As_a_QEMU_networked_Guest

https://wiki.alpinelinux.org/wiki/Installing_Alpine_Linux_in_a_chroot

https://lists.strace.io/pipermail/strace-devel/2019-March/008662.html

https://bugs.alpinelinux.org/issues/9504

User:Tmhoang

2019-03-18T13:55:30Z

Tmhoang:

User:Tmhoang

2019-03-18T13:55:25Z

Tmhoang:

Personal notes
https://pi3g.com/2019/01/10/alpine-boot-process-on-the-raspberry-pi/

https://wiki.alpinelinux.org/wiki/Setting_up_a_OpenVPN_server

https://wiki.alpinelinux.org/wiki/Running_Alpine_Linux_As_a_QEMU_networked_Guest

https://wiki.alpinelinux.org/wiki/Installing_Alpine_Linux_in_a_chroot

User:Tmhoang

2019-03-18T13:55:17Z

Tmhoang: Created page with "Personal notes https://pi3g.com/2019/01/10/alpine-boot-process-on-the-raspberry-pi/ https://wiki.alpinelinux.org/wiki/Setting_up_a_OpenVPN_server https://wiki.alpinelinux.org/..."

Personal notes
https://pi3g.com/2019/01/10/alpine-boot-process-on-the-raspberry-pi/
https://wiki.alpinelinux.org/wiki/Setting_up_a_OpenVPN_server
https://wiki.alpinelinux.org/wiki/Running_Alpine_Linux_As_a_QEMU_networked_Guest
https://wiki.alpinelinux.org/wiki/Installing_Alpine_Linux_in_a_chroot

S390x/Installation

2019-02-20T13:29:41Z

Tmhoang: update to 3.9.0

= 1. Known Issues =
1. Installation on 2 or more DASDs (either ECKD and FBA) on z/VM is not supported in the installer script (<code>setup-alpine</code>) at the moment. If you want to install/extend on more than 1 DASD, see [https://wiki.alpinelinux.org/wiki/S390x#Extending_LVM_volume "Extending LVM volume"]. However, installation on 2 or more virtio (SCSI) disks on KVM are supported just like other architectures.

= 2. The boot media =

For KVM, both ISO image and netboot media (kernel and initramfs) are supported.

For z/VM, netboot media is supported.

For LPAR, not yet supported.

Boot media are found at:

* http://dl-cdn.alpinelinux.org/alpine/v3.9/releases/s390x/

== Kernel parameters (and parmfile) ==
The Alpine s390x boot media requires following kernel parameters to work:

<code>ip=dhcp</code> : use DHCP for network configuration.

<code>ip=client-ip:server-ip:gw-ip:netmask:hostname:device:autoconf:dns1:dns2</code> : use static IP configuration, each field is separated by a colon <code>:</code>
* <code>client-ip</code> ip address of the guest VM where we are going to run the installer
* <code>server-ip</code> not used, leave blank or fill with <code>none</code>
* <code>gw-ip</code> the gateway ip address
* <code>netmask</code> the netmask
* <code>hostname</code> not used, leave blank or fill with <code>none</code>
* <code>device</code> the network interface of the guest VM, default is <code>eth0</code> if left blank
* <code>autoconf</code> not used, leave blank or fill with <code>none</code> or <code>off</code>
* <code>dns1</code> address of the DNS server
* <code>dns2</code> address of the 2nd DNS server

<code>alpine_repo=</code> : the location of the Alpine repository from which packages are downloaded.

:For stable release, use <code>http://dl-cdn.alpinelinux.org/alpine/v3.9/main</code>

:For rolling release, use <code>http://dl-cdn.alpinelinux.org/alpine/edge/main</code>

<code>modloop=</code> : the remote location of the image containing kernel's modules, required for LVM and raid setup.

:The remote location of the <code>modloop</code> image is the same as the kernel and initramfs (see below).

<code>ssh_key=</code> : the remote location of your SSH public key which is used to allow SSH connection into the installer. It will be downloaded and copied into <code>/root/.ssh/authorized_keys</code> in the installer.

{{Note|Fetching public keys from HTTP, HTTPS and FTPS are supported. HTTP should only be used in local development network where you own the network.}}

{{Note|Alpine Linux security policies are against using passwords for root access via SSH as we consider using public-private key pairs is a much better approach.}}

'''z/VM only'''

<code>dasd=</code> : the addresses of the DASD devices, either ECKD or FBA DASDs. Each device is separated with a comma.

<code>s390x_net=</code> : the network interface type and its subchannels. At the moment, only QETH layer 2 is supported, thus the name <code>qeth_l2</code> is used (see below).

= 3. Pre-installation =

== KVM ==
Create a virtual disk:
$ qemu-img create alpine_disk.qcow2 5G

==== Using iso image ====
Download latest iso image from : http://dl-cdn.alpinelinux.org/alpine/v3.9/releases/s390x

Start qemu:

$ qemu-system-s390x -M s390-ccw-virtio \
-m 1024 -smp 2 -nographic -enable-kvm \
-net nic -net tap,ifname=tap0,script=no \
-hda alpine_disk.qcow2 \
-boot d -cdrom alpine-standard-3.9.0-s390x.iso

==== Using netboot media ====
Download the latest [http://dl-cdn.alpinelinux.org/alpine/v3.9/releases/s390x/netboot/vmlinuz-vanilla kernel] and [http://dl-cdn.alpinelinux.org/alpine/v3.9/releases/s390x/netboot/initramfs-vanilla initramfs].

Start qemu: (modify <code>ip=</code> <code>alpine_repo=</code> <code>ssh_key=</code> for your needs)

$ qemu-system-s390x -M s390-ccw-virtio \
-m 1024 -smp 2 -nographic -enable-kvm \
-net nic -net tap,ifname=tap0,script=no \
-hda alpine_disk.qcow2 \
-kernel vmlinuz-vanilla \
-initrd initramfs-vanilla \
-append "ip=192.168.1.2::192.168.1.1:255.255.255.0:none:eth0:none:8.8.8.8 alpine_repo=http://dl-cdn.alpinelinux.org/alpine/v3.9/main modloop=http://dl-cdn.alpinelinux.org/alpine/v3.9/releases/s390x/netboot/modloop-vanilla ssh_key=https://your-website.com/your-ssh-key.pub"

{{Note|If you have direct access to the qemu console, <code>ssh_key</code> might not be required.}}

== z/VM ==
To ease out the process of downloading the images, punch the readers, ipl, etc., [https://github.com/trothr/znetboot '''ZNETBOOT'''] is used.

==== Create the parm file ====
On your workstation/laptop, create a file named <code>alpine.znetboot</code> in your home directory with contents below (modify <code>dasd=</code><code>s390x_net=</code> <code>ip=</code> <code>alpine_repo=</code> <code>ssh_key=</code> for your needs)

<pre>
ZNETBOOT_KERNEL=http://dl-cdn.alpinelinux.org/alpine/v3.9/releases/s390x/netboot/vmlinuz-vanilla
ZNETBOOT_INITRD=http://dl-cdn.alpinelinux.org/alpine/v3.9/releases/s390x/netboot/initramfs-vanilla
ZNETBOOT_PROGRESS=1M

alpine_repo=http://dl-cdn.alpinelinux.org/alpine/v3.9/main
modloop=http://dl-cdn.alpinelinux.org/alpine/v3.9/releases/s390x/netboot/modloop-vanilla

dasd=0.0.04c0,0.0.05d1
s390x_net=qeth_l2,0.0.0560,0.0.0561,0.0.0562
ip=192.168.1.2::192.168.1.1:255.255.255.0:none:eth0:none:8.8.8.8

ssh_key=https://your-website.com/your-ssh-key.pub

</pre>

==== Upload to z/VM system via 3270 client ====
[[File:X3270-1.png|right|300px|thumb|Figure 1.]]
On your workstation/laptop, download 2 files [https://raw.githubusercontent.com/trothr/znetboot/master/znetboot.exec <code>znetboot.exec</code>], and [https://raw.githubusercontent.com/trothr/znetboot/master/curl.rexx <code>curl.rexx</code>] to your home directory.

Open 3270 client and log in the z/VM system with your z/VM username and password.

Upload 3 files <code>alpine.znetboot</code>, <code>znetboot.exec</code>, <code>curl.rexx</code> to the z/VM environment using the 3270 client (this tutorial uses x3270). On the top left corner, click "File", then "File Transfer". (Figure 1.)

Do following steps : (Figure 2.) [[File:X3270-2.png|right|300px|thumb|Figure 2.]]
* On "Local File Name" box, enter '''alpine.znetboot''' (the file in your laptop/workstation, at '''~/alpine.znetboot''')
* On "Host File Name" box, enter '''alpine znetboot''' (the file will be in z/VM console)

{{Note|Beware the difference between '''the dot <code>.</code>''' and '''the space <code> </code>''' characters in the file names.}}

* Choose '''Send to host'''
* Choose '''Host is VM/CMS'''
* Choose either '''Fixed''' or '''Variable''' for '''Record Format'''
:Enter a number for LRECL and BLKSIZE, respectively
{{Note|Any line in '''alpine.znetboot''' that has more 80 chars (columns) will be splitted into more than 1 line when uploaded to z/VM (CMS) console via 3270. Count the number of characters/column of the longest line in your '''alpine.znetboot''' and fill it in LRECL. There is no restriction for BLKSIZE but 80 is preferred.}}

* Click '''Transfer File''' box

Repeat the same steps with <code>znetboot.exec</code> and <code>curl.rexx</code> files.

==== (Optional) Check the configuration files ====
On 3270 client, enter following commands to check if the configuration files are correctly transferred:

<code>xedit alpine znetboot</code>

<code>xedit znetboot exec</code>

<code>xedit curl rex</code>

or <code>filel</code> and put <code>xedit</code> on CMD column to edit respective file.

==== Start ZNETBOOT ====
On 3270 client, type below command and wait till Figure 3.: [[File:X3270-3.png|right|300px|thumb|Figure 3.]]

<code>znetboot alpine</code>

= 4. Installation =
If you install on z/VM, steps in this part does not involve the interaction with the 3270 client anymore. Everything is done in the terminal with SSH client.

If you install on KVM, you can either SSH into the installer (below) or directly use the console starting qemu.

Either installing in KVM or z/VM environments, from your workstation/laptop, you will be able to run:
$ ssh root@192.168.1.2 (change ip address to what you specified earlier)

Remaining steps are similar to installing Alpine on other architectures (x86, arm, ppc, etc.), either on KVM (using virtio/SCSI disks) or on z/VM with FBA DASDs. Installing on ECKD DASDs requires an additional step, as described below.

== Example ==
Below is the detailed walkthrough of installing Alpine on a single ECKD DASD using LVM and extend that LVM to the second ECKD DASD.

After SSH-ing into the Alpine installer, run:
# setup-alpine

<code>Select keyboard layout [none]:</code>
:press Enter for none

<code>Enter system hostname (short form, e.g. 'foo') [localhost]:</code>
:enter your hostname

<pre>
Available interfaces are: eth0.
Enter '?' for help on bridges, bonding and vlans.
Which one do you want to initialize? (or '?' or 'done') [eth0]:</pre>
:type 'eth0' or press Enter

<code>Ip address for eth0? (or 'dhcp', 'none', '?') [192.168.1.2]</code>
:enter ip address or 'dhcp'

<code>Netmask? [255.255.255.0]</code>
:enter netmask
<code>Gateway? (or 'none') [192.168.1.1]</code>
:enter gateway's ip address

<code>Do you want to do any manual network configuration? [no]</code>
:enter 'no' or press Enter

<code>DNS domain name? (e.g 'bar.com') []</code>
:enter domain name or press Enter for none

<code>DNS nameserver(s)? [8.8.8.8 ]</code>
:enter DNS nameserver

<code>Changing password for root</code>
:enter root password

<code>Which timezone are you in? ('?' for list) [UTC]</code>
:enter timezone or '?' for list of timezones

<code>HTTP/FTP proxy URL? (e.g. 'http://proxy:8080', or 'none') [none]</code>
:enter proxy or press Enter for none

<code>Enter mirror number (1-27) or URL to add (or r/f/e/done) [f]:</code>
:enter a number or 'r' or 'f' or 'e' or 'done' as described

<code>Which SSH server? ('openssh', 'dropbear' or 'none') [openssh]</code>
:enter SSH server or press Enter for openssh

<code>Which NTP client to run? ('busybox', 'openntpd', 'chrony' or 'none') [chrony]</code>
:enter 'busybox' or press Enter for chrony

''' (next step is the additional step for ECKD DASDs on z/VM)'''
<pre>
Available ECKD DASD(s) are:
0.0.04c0 (3390/0c 3990/e9 IBM)
0.0.05d1 (3390/0c 3990/e9 IBM)
Which ECKD DASD(s) would you like to be formatted using dasdfmt? (enter '?' for help) [all]</pre>
:enter 'all' or '0.0.04c0 0.0.05d1' '''(separated by a space)''' to format all/both DASDs
:enter '0.0.04c0' or '0.0.05d1' to format respective DASD
:enter '?' for help

<code>WARNING: Erase ECKD DASD 0.0.04c0? [y/N]:</code>
:enter 'y' to format

<pre>
Available disks are:
dasda (2.5 GB IBM 0.0.04c0)
Which disk(s) would you like to use? (or '?' for help or 'none') [dasda]</pre>
:enter 'dasda' or press Enter

<pre>
The following disk is selected:
dasda (2.5 GB IBM 0.0.04c0)
How would you like to use it? ('sys', 'data', 'lvm' or '?' for help) [?]</pre>
:enter 'lvm'

<pre>
The following disk is selected (with LVM):
dasda (2.5 GB IBM 0.0.04c0)
How would you like to use it? ('sys', 'data' or '?' for help) [?]</pre>
:enter 'sys' to install Alpine on disk

<pre>
WARNING: The following disk(s) will be erased:
dasda (2.5 GB IBM 0.0.04c0)
WARNING: Erase the above disk(s) and continue? [y/N]:</pre>
:enter 'y'

<code>Installation is complete. Please reboot.</code>
:the installation is finished

At this point, don't poweroff the installer right away. Go to [https://wiki.alpinelinux.org/wiki/S390x#Copying_SSH_keys_to_new_Alpine_system "Copying SSH keys to new Alpine system"] (below) to have SSH access to your new Alpine system.

== Copying SSH keys to new Alpine system ==

By default, Alpine disables root login with a password via SSH. SSH keys are used instead.

After the installer's done running (<code>Installation is complete. Please reboot.</code>), there are 2 ways to copy your SSH key into the new Alpine system:
* Option 1: mount the installed disk and copy the SSH keys while still at the installer's terminal
* Option 2: poweroff the installer, start the new Alpine system and directly add the SSH keys
::: if you install on KVM, boot the new Alpine system on qemu, and copy the SSH keys
::: if you install on z/VM, use the 3270 client to ipl the new Alpine system and copy the SSH keys

'''Option 1'''

If you use 'lvm' + 'sys' installation (like in above example), do:

:<code> # mount /dev/vg0/lv_root /mnt</code>

:<code> # cp -ar /root/.ssh /mnt/root</code>

If you use 'sys' (without LVM) installation, do:

:<code> # mount /dev/dasda3 /mnt</code> (change dasda to dasdb or dasdc, etc. for whichever DASD you chose)

:<code> # cp -ar /root/.ssh /mnt/root</code>

{{Note|In 'sys' installation, 1st partition is boot, 2nd partition is swap, 3rd partition is root }}

Then run <code> # poweroff</code>.

Go to [https://wiki.alpinelinux.org/wiki/S390x#Login_to_new_Alpine_system "Login to new Alpine system"]

'''Option 2'''

Run <code> # poweroff</code>.

If you use KVM, start qemu with new Alpine system (removing <code>-kernel</code>, <code>-initrd</code>, <code>-append</code> options)

If you use z/VM, open the 3270 client, login with your z/VM username and password. You may need to run <code> ipl cms</code>. Then run <code> ipl 04c0</code> (or whichever DASD device you chose as root disk in earlier steps).

Wait for new Alpine system go up, then login as root user while in the qemu console (on KVM) or 3270 client (on z/VM). Then run:
::<code> # mkdir /root/.ssh</code>
::<code> # wget https://your-website.com/your-ssh-key.pub -O /root/.ssh/authorized_keys</code>
::<code> # chmod 700 /root/.ssh</code>
::<code> # chmod 600 /root/.ssh/authorized_keys</code>

Go to [https://wiki.alpinelinux.org/wiki/S390x#Login_to_new_Alpine_system "Login to new Alpine system"]

== Login to new Alpine system ==
On your workstation/laptop, use SSH client to login new Alpine system:
<code> $ ssh root@192.168.1.2</code> (or whichever ip address you used)

== Extending LVM volume ==
After logging in to your new Alpine system, run:
<pre>
# apk add -q util-linux e2fsprogs-extra

# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
dasda 94:0 0 2.3G 0 disk
├─dasda1 94:1 0 100M 0 part /boot
└─dasda2 94:2 0 2.2G 0 part
├─vg0-lv_swap 254:0 0 588M 0 lvm [SWAP]
└─vg0-lv_root 254:1 0 1.6G 0 lvm /
dasdb 94:4 0 2.3G 0 disk

# dasdfmt -b 4096 -d cdl -yp /dev/dasdb

# fdasd -a /dev/dasdb

# pvcreate /dev/dasdb1

# vgextend vg0 /dev/dasdb1

# lvextend -l +100%FREE /dev/vg0/lv_root

# resize2fs /dev/vg0/lv_root

# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
dasda 94:0 0 2.3G 0 disk
├─dasda1 94:1 0 100M 0 part /boot
└─dasda2 94:2 0 2.2G 0 part
├─vg0-lv_swap 254:0 0 588M 0 lvm [SWAP]
└─vg0-lv_root 254:1 0 3.9G 0 lvm /
dasdb 94:4 0 2.3G 0 disk
└─dasdb1 94:5 0 2.3G 0 part
└─vg0-lv_root 254:1 0 3.9G 0 lvm /
</pre>

= 5. Tips =
If you want to disable swap partition, after finishing NTP client step, quit the installer by pressing <code>Ctrl + C</code>. Then run following command to complete remaining steps:

<code># setup-disk -s 0</code>

{{Note|If you do 'sys' installation, there will be no swap partition anymore and 1st partition will be boot, 2nd partition will be root}}

S390x/Known Issues

2019-02-05T10:25:41Z

Tmhoang:

When running the 3.9 netboot installer, you might face this problem mostly '''z/VM hypervisor''' (common among architectures without a RTC clock like armhf, aarch64, s390x) :
<pre>
Which NTP client to run? ('busybox', 'openntpd', 'chrony' or 'none') [chrony] busybox
\* service ntpd added to runlevel default
\* Starting busybox ntpd ... [ ok ]
ssl_client: mirrors.alpinelinux.org: ocsp verify failed: ocsp response not current
wget: error getting response: Connection reset by peer
r) Add random from the above list
f) Detect and add fastest mirror from above list
e) Edit /etc/apk/repositories with text editor

Enter mirror number (1-0) or URL to add (or r/f/e/done) [f]:
</pre>

This is because the clocksource on s390x was not yet detected. There is a pull request to make this work (would be available on 3.9.1 release):
<pre>
https://github.com/alpinelinux/aports/pull/6183
https://github.com/alpinelinux/aports/pull/6184
</pre>

In the mean time, to overcome this problem, you need to update the system time, either manullay using <code> date </code> command or using NTP then start the installer as bellow:

<pre>
# setup-interfaces
# setup-dns
# service networking start
# ntpd -qn -p pool.ntp.org
# setup-alpine
</pre>

S390x/Known Issues

2019-02-04T15:24:25Z

Tmhoang:

When running the 3.9 installer, you might face this problem (common among architectures without a RTC clock like armhf, aarch64, s390x) :
<pre>
Which NTP client to run? ('busybox', 'openntpd', 'chrony' or 'none') [chrony] busybox
\* service ntpd added to runlevel default
\* Starting busybox ntpd ... [ ok ]
ssl_client: mirrors.alpinelinux.org: ocsp verify failed: ocsp response not current
wget: error getting response: Connection reset by peer
r) Add random from the above list
f) Detect and add fastest mirror from above list
e) Edit /etc/apk/repositories with text editor

Enter mirror number (1-0) or URL to add (or r/f/e/done) [f]:
</pre>

This is because the clocksource on s390x was not yet detected. There is a pull request to make this work (would be available on 3.9.1 release):
<pre>
https://github.com/alpinelinux/aports/pull/6183
https://github.com/alpinelinux/aports/pull/6184
</pre>

In the mean time, to overcome this problem, you need to update the system time, either manullay using <code> date </code> command or using NTP then start the installer as bellow:

<pre>
# setup-interfaces
# setup-dns
# service networking start
# ntpd -qn -p pool.ntp.org
# setup-alpine
</pre>

S390x/Known Issues

2019-01-31T14:40:51Z

Tmhoang:

When running the 3.9 installer, you might face this problem (common among architectures without a RTC clock like armhf, aarch64, s390x) :
<pre>
Which NTP client to run? ('busybox', 'openntpd', 'chrony' or 'none') [chrony] busybox
\* service ntpd added to runlevel default
\* Starting busybox ntpd ... [ ok ]
ssl_client: mirrors.alpinelinux.org: ocsp verify failed: ocsp response not current
wget: error getting response: Connection reset by peer
r) Add random from the above list
f) Detect and add fastest mirror from above list
e) Edit /etc/apk/repositories with text editor

Enter mirror number (1-0) or URL to add (or r/f/e/done) [f]:
</pre>

This is because the clocksource on s390x was not yet detected. There is a pull request to make this work (would be available on 3.9.1 release):
<pre>
https://github.com/alpinelinux/aports/pull/6184
https://github.com/alpinelinux/aports/pull/6184
</pre>

In the mean time, to overcome this problem, you need to update the system time, either manullay using <code> date </code> command or using NTP then start the installer as bellow:

<pre>
# setup-interfaces
# setup-dns
# service networking start
# ntpd -qn -p pool.ntp.org
# setup-alpine
</pre>

S390x/Known Issues

2019-01-31T14:27:40Z

Tmhoang: Created page with "= 1 = <code> Which NTP client to run? ('busybox', 'openntpd', 'chrony' or 'none') [chrony] busybox * service ntpd added to runlevel default * Starting busybox ntpd ......"

= 1 =
<code>
Which NTP client to run? ('busybox', 'openntpd', 'chrony' or 'none') [chrony] busybox
* service ntpd added to runlevel default
* Starting busybox ntpd ... [ ok ]
ssl_client: mirrors.alpinelinux.org: ocsp verify failed: ocsp response not current
wget: error getting response: Connection reset by peer
r) Add random from the above list
f) Detect and add fastest mirror from above list
e) Edit /etc/apk/repositories with text editor

Enter mirror number (1-0) or URL to add (or r/f/e/done) [f]:
</code>

This is because the clocksource on s390x was not yet detected. There is a pull request to make it work
<code>
https://github.com/alpinelinux/aports/pull/6184
https://github.com/alpinelinux/aports/pull/6184
</code>

In the mean time, please run below command before running <code> # setup-alpine </code> for the installer:
<code>
# ntpd -qn -p pool.ntp.org
# setup-alpine
</code>

S390x

2019-01-31T14:22:37Z

Tmhoang:

S390x

2019-01-29T21:18:49Z

Tmhoang: Replaced content with " = Installation guide = Visit: https://wiki.alpinelinux.org/wiki/S390x/Installation = Docker with Alpine = Running Alpine s390x containers on Docker: https://wiki.alpinel..."

= Installation guide =
Visit: https://wiki.alpinelinux.org/wiki/S390x/Installation

= Docker with Alpine =
Running Alpine s390x containers on Docker: https://wiki.alpinelinux.org/wiki/S390x/Docker

S390x/Installation

2019-01-29T21:18:22Z

Tmhoang: Created page with " = 1. Known Issues = 1. Installation on 2 or more DASDs (either ECKD and FBA) on z/VM is not supported in the installer script (<code>setup-alpine</code>) at the moment. If yo..."

= 1. Known Issues =
1. Installation on 2 or more DASDs (either ECKD and FBA) on z/VM is not supported in the installer script (<code>setup-alpine</code>) at the moment. If you want to install/extend on more than 1 DASD, see [https://wiki.alpinelinux.org/wiki/S390x#Extending_LVM_volume "Extending LVM volume"]. However, installation on 2 or more virtio (SCSI) disks on KVM are supported just like other architectures.

= 2. The boot media =

For KVM, both ISO image and netboot media (kernel and initramfs) are supported.

For z/VM, netboot media is supported.

For LPAR, not yet supported.

Boot media are found at:

* http://dl-cdn.alpinelinux.org/alpine/v3.8/releases/s390x/

== Kernel parameters (and parmfile) ==
The Alpine s390x boot media requires following kernel parameters to work:

<code>ip=dhcp</code> : use DHCP for network configuration.

<code>ip=client-ip:server-ip:gw-ip:netmask:hostname:device:autoconf:dns1:dns2</code> : use static IP configuration, each field is separated by a colon <code>:</code>
* <code>client-ip</code> ip address of the guest VM where we are going to run the installer
* <code>server-ip</code> not used, leave blank or fill with <code>none</code>
* <code>gw-ip</code> the gateway ip address
* <code>netmask</code> the netmask
* <code>hostname</code> not used, leave blank or fill with <code>none</code>
* <code>device</code> the network interface of the guest VM, default is <code>eth0</code> if left blank
* <code>autoconf</code> not used, leave blank or fill with <code>none</code> or <code>off</code>
* <code>dns1</code> address of the DNS server
* <code>dns2</code> address of the 2nd DNS server

<code>alpine_repo=</code> : the location of the Alpine repository from which packages are downloaded.

:For stable release, use <code>http://dl-cdn.alpinelinux.org/alpine/v3.8/main</code>

:For rolling release, use <code>http://dl-cdn.alpinelinux.org/alpine/edge/main</code>

<code>modloop=</code> : the remote location of the image containing kernel's modules, required for LVM and raid setup.

:The remote location of the <code>modloop</code> image is the same as the kernel and initramfs (see below).

<code>ssh_key=</code> : the remote location of your SSH public key which is used to allow SSH connection into the installer. It will be downloaded and copied into <code>/root/.ssh/authorized_keys</code> in the installer.

{{Note|Fetching public keys from HTTP, HTTPS and FTPS are supported. HTTP should only be used in local development network where you own the network.}}

{{Note|Alpine Linux security policies are against using passwords for root access via SSH as we consider using public-private key pairs is a much better approach.}}

'''z/VM only'''

<code>dasd=</code> : the addresses of the DASD devices, either ECKD or FBA DASDs. Each device is separated with a comma.

<code>s390x_net=</code> : the network interface type and its subchannels. At the moment, only QETH layer 2 is supported, thus the name <code>qeth_l2</code> is used (see below).

= 3. Pre-installation =

== KVM ==
Create a virtual disk:
$ qemu-img create alpine_disk.qcow2 5G

==== Using iso image ====
Download latest iso image from : http://dl-cdn.alpinelinux.org/alpine/v3.8/releases/s390x

Start qemu:

$ qemu-system-s390x -M s390-ccw-virtio \
-m 1024 -smp 2 -nographic -enable-kvm \
-net nic -net tap,ifname=tap0,script=no \
-hda alpine_disk.qcow2 \
-boot d -cdrom alpine-standard-3.8.2-s390x.iso

==== Using netboot media ====
Download the latest [http://dl-cdn.alpinelinux.org/alpine/v3.8/releases/s390x/netboot-3.8.2/vmlinuz-vanilla kernel] and [http://dl-cdn.alpinelinux.org/alpine/v3.8/releases/s390x/netboot-3.8.2/initramfs-vanilla initramfs].

Start qemu: (modify <code>ip=</code> <code>alpine_repo=</code> <code>ssh_key=</code> for your needs)

$ qemu-system-s390x -M s390-ccw-virtio \
-m 1024 -smp 2 -nographic -enable-kvm \
-net nic -net tap,ifname=tap0,script=no \
-hda alpine_disk.qcow2 \
-kernel vmlinuz-vanilla \
-initrd initramfs-vanilla \
-append "ip=192.168.1.2::192.168.1.1:255.255.255.0:none:eth0:none:8.8.8.8 alpine_repo=http://dl-cdn.alpinelinux.org/alpine/v3.8/main modloop=http://dl-cdn.alpinelinux.org/alpine/v3.8/releases/s390x/netboot-3.8.2/modloop-vanilla ssh_key=https://your-website.com/your-ssh-key.pub"

{{Note|If you have direct access to the qemu console, <code>ssh_key</code> might not be required.}}

== z/VM ==
To ease out the process of downloading the images, punch the readers, ipl, etc., [https://github.com/trothr/znetboot '''ZNETBOOT'''] is used.

==== Create the parm file ====
On your workstation/laptop, create a file named <code>alpine.znetboot</code> in your home directory with contents below (modify <code>dasd=</code><code>s390x_net=</code> <code>ip=</code> <code>alpine_repo=</code> <code>ssh_key=</code> for your needs)

<pre>
ZNETBOOT_KERNEL=http://dl-cdn.alpinelinux.org/alpine/v3.8/releases/s390x/netboot-3.8.2/vmlinuz-vanilla
ZNETBOOT_INITRD=http://dl-cdn.alpinelinux.org/alpine/v3.8/releases/s390x/netboot-3.8.2/initramfs-vanilla
ZNETBOOT_PROGRESS=1M

alpine_repo=http://dl-cdn.alpinelinux.org/alpine/v3.8/main
modloop=http://dl-cdn.alpinelinux.org/alpine/v3.8/releases/s390x/netboot-3.8.2/modloop-vanilla

dasd=0.0.04c0,0.0.05d1
s390x_net=qeth_l2,0.0.0560,0.0.0561,0.0.0562
ip=192.168.1.2::192.168.1.1:255.255.255.0:none:eth0:none:8.8.8.8

ssh_key=https://your-website.com/your-ssh-key.pub

</pre>

==== Upload to z/VM system via 3270 client ====
[[File:X3270-1.png|right|300px|thumb|Figure 1.]]
On your workstation/laptop, download 2 files [https://raw.githubusercontent.com/trothr/znetboot/master/znetboot.exec <code>znetboot.exec</code>], and [https://raw.githubusercontent.com/trothr/znetboot/master/curl.rexx <code>curl.rexx</code>] to your home directory.

Open 3270 client and log in the z/VM system with your z/VM username and password.

Upload 3 files <code>alpine.znetboot</code>, <code>znetboot.exec</code>, <code>curl.rexx</code> to the z/VM environment using the 3270 client (this tutorial uses x3270). On the top left corner, click "File", then "File Transfer". (Figure 1.)

Do following steps : (Figure 2.) [[File:X3270-2.png|right|300px|thumb|Figure 2.]]
* On "Local File Name" box, enter '''alpine.znetboot''' (the file in your laptop/workstation, at '''~/alpine.znetboot''')
* On "Host File Name" box, enter '''alpine znetboot''' (the file will be in z/VM console)

{{Note|Beware the difference between '''the dot <code>.</code>''' and '''the space <code> </code>''' characters in the file names.}}

* Choose '''Send to host'''
* Choose '''Host is VM/CMS'''
* Choose either '''Fixed''' or '''Variable''' for '''Record Format'''
:Enter a number for LRECL and BLKSIZE, respectively
{{Note|Any line in '''alpine.znetboot''' that has more 80 chars (columns) will be splitted into more than 1 line when uploaded to z/VM (CMS) console via 3270. Count the number of characters/column of the longest line in your '''alpine.znetboot''' and fill it in LRECL. There is no restriction for BLKSIZE but 80 is preferred.}}

* Click '''Transfer File''' box

Repeat the same steps with <code>znetboot.exec</code> and <code>curl.rexx</code> files.

==== (Optional) Check the configuration files ====
On 3270 client, enter following commands to check if the configuration files are correctly transferred:

<code>xedit alpine znetboot</code>

<code>xedit znetboot exec</code>

<code>xedit curl rex</code>

or <code>filel</code> and put <code>xedit</code> on CMD column to edit respective file.

==== Start ZNETBOOT ====
On 3270 client, type below command and wait till Figure 3.: [[File:X3270-3.png|right|300px|thumb|Figure 3.]]

<code>znetboot alpine</code>

= 4. Installation =
If you install on z/VM, steps in this part does not involve the interaction with the 3270 client anymore. Everything is done in the terminal with SSH client.

If you install on KVM, you can either SSH into the installer (below) or directly use the console starting qemu.

Either installing in KVM or z/VM environments, from your workstation/laptop, you will be able to run:
$ ssh root@192.168.1.2 (change ip address to what you specified earlier)

Remaining steps are similar to installing Alpine on other architectures (x86, arm, ppc, etc.), either on KVM (using virtio/SCSI disks) or on z/VM with FBA DASDs. Installing on ECKD DASDs requires an additional step, as described below.

== Example ==
Below is the detailed walkthrough of installing Alpine on a single ECKD DASD using LVM and extend that LVM to the second ECKD DASD.

After SSH-ing into the Alpine installer, run:
# setup-alpine

<code>Select keyboard layout [none]:</code>
:press Enter for none

<code>Enter system hostname (short form, e.g. 'foo') [localhost]:</code>
:enter your hostname

<pre>
Available interfaces are: eth0.
Enter '?' for help on bridges, bonding and vlans.
Which one do you want to initialize? (or '?' or 'done') [eth0]:</pre>
:type 'eth0' or press Enter

<code>Ip address for eth0? (or 'dhcp', 'none', '?') [192.168.1.2]</code>
:enter ip address or 'dhcp'

<code>Netmask? [255.255.255.0]</code>
:enter netmask
<code>Gateway? (or 'none') [192.168.1.1]</code>
:enter gateway's ip address

<code>Do you want to do any manual network configuration? [no]</code>
:enter 'no' or press Enter

<code>DNS domain name? (e.g 'bar.com') []</code>
:enter domain name or press Enter for none

<code>DNS nameserver(s)? [8.8.8.8 ]</code>
:enter DNS nameserver

<code>Changing password for root</code>
:enter root password

<code>Which timezone are you in? ('?' for list) [UTC]</code>
:enter timezone or '?' for list of timezones

<code>HTTP/FTP proxy URL? (e.g. 'http://proxy:8080', or 'none') [none]</code>
:enter proxy or press Enter for none

<code>Enter mirror number (1-27) or URL to add (or r/f/e/done) [f]:</code>
:enter a number or 'r' or 'f' or 'e' or 'done' as described

<code>Which SSH server? ('openssh', 'dropbear' or 'none') [openssh]</code>
:enter SSH server or press Enter for openssh

<code>Which NTP client to run? ('busybox', 'openntpd', 'chrony' or 'none') [chrony]</code>
:enter 'busybox' or press Enter for chrony

''' (next step is the additional step for ECKD DASDs on z/VM)'''
<pre>
Available ECKD DASD(s) are:
0.0.04c0 (3390/0c 3990/e9 IBM)
0.0.05d1 (3390/0c 3990/e9 IBM)
Which ECKD DASD(s) would you like to be formatted using dasdfmt? (enter '?' for help) [all]</pre>
:enter 'all' or '0.0.04c0 0.0.05d1' '''(separated by a space)''' to format all/both DASDs
:enter '0.0.04c0' or '0.0.05d1' to format respective DASD
:enter '?' for help

<code>WARNING: Erase ECKD DASD 0.0.04c0? [y/N]:</code>
:enter 'y' to format

<pre>
Available disks are:
dasda (2.5 GB IBM 0.0.04c0)
Which disk(s) would you like to use? (or '?' for help or 'none') [dasda]</pre>
:enter 'dasda' or press Enter

<pre>
The following disk is selected:
dasda (2.5 GB IBM 0.0.04c0)
How would you like to use it? ('sys', 'data', 'lvm' or '?' for help) [?]</pre>
:enter 'lvm'

<pre>
The following disk is selected (with LVM):
dasda (2.5 GB IBM 0.0.04c0)
How would you like to use it? ('sys', 'data' or '?' for help) [?]</pre>
:enter 'sys' to install Alpine on disk

<pre>
WARNING: The following disk(s) will be erased:
dasda (2.5 GB IBM 0.0.04c0)
WARNING: Erase the above disk(s) and continue? [y/N]:</pre>
:enter 'y'

<code>Installation is complete. Please reboot.</code>
:the installation is finished

At this point, don't poweroff the installer right away. Go to [https://wiki.alpinelinux.org/wiki/S390x#Copying_SSH_keys_to_new_Alpine_system "Copying SSH keys to new Alpine system"] (below) to have SSH access to your new Alpine system.

== Copying SSH keys to new Alpine system ==

By default, Alpine disables root login with a password via SSH. SSH keys are used instead.

After the installer's done running (<code>Installation is complete. Please reboot.</code>), there are 2 ways to copy your SSH key into the new Alpine system:
* Option 1: mount the installed disk and copy the SSH keys while still at the installer's terminal
* Option 2: poweroff the installer, start the new Alpine system and directly add the SSH keys
::: if you install on KVM, boot the new Alpine system on qemu, and copy the SSH keys
::: if you install on z/VM, use the 3270 client to ipl the new Alpine system and copy the SSH keys

'''Option 1'''

If you use 'lvm' + 'sys' installation (like in above example), do:

:<code> # mount /dev/vg0/lv_root /mnt</code>

:<code> # cp -ar /root/.ssh /mnt/root</code>

If you use 'sys' (without LVM) installation, do:

:<code> # mount /dev/dasda3 /mnt</code> (change dasda to dasdb or dasdc, etc. for whichever DASD you chose)

:<code> # cp -ar /root/.ssh /mnt/root</code>

{{Note|In 'sys' installation, 1st partition is boot, 2nd partition is swap, 3rd partition is root }}

Then run <code> # poweroff</code>.

Go to [https://wiki.alpinelinux.org/wiki/S390x#Login_to_new_Alpine_system "Login to new Alpine system"]

'''Option 2'''

Run <code> # poweroff</code>.

If you use KVM, start qemu with new Alpine system (removing <code>-kernel</code>, <code>-initrd</code>, <code>-append</code> options)

If you use z/VM, open the 3270 client, login with your z/VM username and password. You may need to run <code> ipl cms</code>. Then run <code> ipl 04c0</code> (or whichever DASD device you chose as root disk in earlier steps).

Wait for new Alpine system go up, then login as root user while in the qemu console (on KVM) or 3270 client (on z/VM). Then run:
::<code> # mkdir /root/.ssh</code>
::<code> # wget https://your-website.com/your-ssh-key.pub -O /root/.ssh/authorized_keys</code>
::<code> # chmod 700 /root/.ssh</code>
::<code> # chmod 600 /root/.ssh/authorized_keys</code>

Go to [https://wiki.alpinelinux.org/wiki/S390x#Login_to_new_Alpine_system "Login to new Alpine system"]

== Login to new Alpine system ==
On your workstation/laptop, use SSH client to login new Alpine system:
<code> $ ssh root@192.168.1.2</code> (or whichever ip address you used)

== Extending LVM volume ==
After logging in to your new Alpine system, run:
<pre>
# apk add -q util-linux e2fsprogs-extra

# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
dasda 94:0 0 2.3G 0 disk
├─dasda1 94:1 0 100M 0 part /boot
└─dasda2 94:2 0 2.2G 0 part
├─vg0-lv_swap 254:0 0 588M 0 lvm [SWAP]
└─vg0-lv_root 254:1 0 1.6G 0 lvm /
dasdb 94:4 0 2.3G 0 disk

# dasdfmt -b 4096 -d cdl -yp /dev/dasdb

# fdasd -a /dev/dasdb

# pvcreate /dev/dasdb1

# vgextend vg0 /dev/dasdb1

# lvextend -l +100%FREE /dev/vg0/lv_root

# resize2fs /dev/vg0/lv_root

# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
dasda 94:0 0 2.3G 0 disk
├─dasda1 94:1 0 100M 0 part /boot
└─dasda2 94:2 0 2.2G 0 part
├─vg0-lv_swap 254:0 0 588M 0 lvm [SWAP]
└─vg0-lv_root 254:1 0 3.9G 0 lvm /
dasdb 94:4 0 2.3G 0 disk
└─dasdb1 94:5 0 2.3G 0 part
└─vg0-lv_root 254:1 0 3.9G 0 lvm /
</pre>

= 5. Tips =
If you want to disable swap partition, after finishing NTP client step, quit the installer by pressing <code>Ctrl + C</code>. Then run following command to complete remaining steps:

<code># setup-disk -s 0</code>

{{Note|If you do 'sys' installation, there will be no swap partition anymore and 1st partition will be boot, 2nd partition will be root}}

S390x

2019-01-18T08:47:15Z

Tmhoang:

= The boot media =

For KVM, both ISO image and netboot media (kernel and initramfs) are supported.

For z/VM, netboot media is supported.

For LPAR, not yet supported.

Boot media are found at:

* http://dl-cdn.alpinelinux.org/alpine/v3.8/releases/s390x/

== Kernel parameters (and parmfile) ==
The Alpine s390x boot media requires following kernel parameters to work:

<code>ip=dhcp</code> : use DHCP for network configuration.

<code>ip=client-ip:server-ip:gw-ip:netmask:hostname:device:autoconf:dns1:dns2</code> : use static IP configuration, each field is separated by a colon <code>:</code>
* <code>client-ip</code> ip address of the guest VM where we are going to run the installer
* <code>server-ip</code> not used, leave blank or fill with <code>none</code>
* <code>gw-ip</code> the gateway ip address
* <code>netmask</code> the netmask
* <code>hostname</code> not used, leave blank or fill with <code>none</code>
* <code>device</code> the network interface of the guest VM, default is <code>eth0</code> if left blank
* <code>autoconf</code> not used, leave blank or fill with <code>none</code> or <code>off</code>
* <code>dns1</code> address of the DNS server
* <code>dns2</code> address of the 2nd DNS server

<code>alpine_repo=</code> : the location of the Alpine repository from which packages are downloaded.

:For stable release, use <code>http://dl-cdn.alpinelinux.org/alpine/v3.8/main</code>

:For rolling release, use <code>http://dl-cdn.alpinelinux.org/alpine/edge/main</code>

<code>modloop=</code> : the remote location of the image containing kernel's modules, required for LVM and raid setup.

:The remote location of the <code>modloop</code> image is the same as the kernel and initramfs (see below).

<code>ssh_key=</code> : the remote location of your SSH public key which is used to allow SSH connection into the installer. It will be downloaded and copied into <code>/root/.ssh/authorized_keys</code> in the installer.

{{Note|Fetching public keys from HTTP, HTTPS and FTPS are supported. HTTP should only be used in local development network where you own the network.}}

{{Note|Alpine Linux security policies are against using passwords for root access via SSH as we consider using public-private key pairs is a much better approach.}}

'''z/VM only'''

<code>dasd=</code> : the addresses of the DASD devices, either ECKD or FBA DASDs. Each device is separated with a comma.

<code>s390x_net=</code> : the network interface type and its subchannels. At the moment, only QETH layer 2 is supported, thus the name <code>qeth_l2</code> is used (see below).

= Pre-installation =

== KVM ==
Create a virtual disk:
$ qemu-img create alpine_disk.qcow2 5G

==== Using iso image ====
Download latest iso image from : http://dl-cdn.alpinelinux.org/alpine/v3.8/releases/s390x

Start qemu:

$ qemu-system-s390x -M s390-ccw-virtio \
-m 1024 -smp 2 -nographic -enable-kvm \
-net nic -net tap,ifname=tap0,script=no \
-hda alpine_disk.qcow2 \
-boot d -cdrom alpine-standard-3.8.2-s390x.iso

==== Using netboot media ====
Download the latest [http://dl-cdn.alpinelinux.org/alpine/v3.8/releases/s390x/netboot-3.8.2/vmlinuz-vanilla kernel] and [http://dl-cdn.alpinelinux.org/alpine/v3.8/releases/s390x/netboot-3.8.2/initramfs-vanilla initramfs].

Start qemu: (modify <code>ip=</code> <code>alpine_repo=</code> <code>ssh_key=</code> for your needs)

$ qemu-system-s390x -M s390-ccw-virtio \
-m 1024 -smp 2 -nographic -enable-kvm \
-net nic -net tap,ifname=tap0,script=no \
-hda alpine_disk.qcow2 \
-kernel vmlinuz-vanilla \
-initrd initramfs-vanilla \
-append "ip=192.168.1.2::192.168.1.1:255.255.255.0:none:eth0:none:8.8.8.8 alpine_repo=http://dl-cdn.alpinelinux.org/alpine/v3.8/main modloop=http://dl-cdn.alpinelinux.org/alpine/v3.8/releases/s390x/netboot-3.8.2/modloop-vanilla ssh_key=https://your-website.com/your-ssh-key.pub"

{{Note|If you have direct access to the qemu console, <code>ssh_key</code> might not be required.}}

== z/VM ==
To ease out the process of downloading the images, punch the readers, ipl, etc., [https://github.com/trothr/znetboot '''ZNETBOOT'''] is used.

==== Create the parm file ====
On your workstation/laptop, create a file named <code>alpine.znetboot</code> in your home directory with contents below (modify <code>dasd=</code><code>s390x_net=</code> <code>ip=</code> <code>alpine_repo=</code> <code>ssh_key=</code> for your needs)

<pre>
ZNETBOOT_KERNEL=http://dl-cdn.alpinelinux.org/alpine/v3.8/releases/s390x/netboot-3.8.2/vmlinuz-vanilla
ZNETBOOT_INITRD=http://dl-cdn.alpinelinux.org/alpine/v3.8/releases/s390x/netboot-3.8.2/initramfs-vanilla
ZNETBOOT_PROGRESS=1M

alpine_repo=http://dl-cdn.alpinelinux.org/alpine/v3.8/main
modloop=http://dl-cdn.alpinelinux.org/alpine/v3.8/releases/s390x/netboot-3.8.2/modloop-vanilla

dasd=0.0.04c0,0.0.05d1
s390x_net=qeth_l2,0.0.0560,0.0.0561,0.0.0562
ip=192.168.1.2::192.168.1.1:255.255.255.0:none:eth0:none:8.8.8.8

ssh_key=https://your-website.com/your-ssh-key.pub

</pre>

==== Upload to z/VM system via 3270 client ====
[[File:X3270-1.png|right|300px|thumb|Figure 1.]]
On your workstation/laptop, download 2 files [https://raw.githubusercontent.com/trothr/znetboot/master/znetboot.exec <code>znetboot.exec</code>], and [https://raw.githubusercontent.com/trothr/znetboot/master/curl.rexx <code>curl.rexx</code>] to your home directory.

Open 3270 client and log in the z/VM system with your z/VM username and password.

Upload 3 files <code>alpine.znetboot</code>, <code>znetboot.exec</code>, <code>curl.rexx</code> to the z/VM environment using the 3270 client (this tutorial uses x3270). On the top left corner, click "File", then "File Transfer". (Figure 1.)

Do following steps : (Figure 2.) [[File:X3270-2.png|right|300px|thumb|Figure 2.]]
* On "Local File Name" box, enter '''alpine.znetboot''' (the file in your laptop/workstation, at '''~/alpine.znetboot''')
* On "Host File Name" box, enter '''alpine znetboot''' (the file will be in z/VM console)

{{Note|Beware the difference between '''the dot <code>.</code>''' and '''the space <code> </code>''' characters in the file names.}}

* Choose '''Send to host'''
* Choose '''Host is VM/CMS'''
* Choose either '''Fixed''' or '''Variable''' for '''Record Format'''
:Enter a number for LRECL and BLKSIZE, respectively
{{Note|Any line in '''alpine.znetboot''' that has more 80 chars (columns) will be splitted into more than 1 line when uploaded to z/VM (CMS) console via 3270. Count the number of characters/column of the longest line in your '''alpine.znetboot''' and fill it in LRECL. There is no restriction for BLKSIZE but 80 is preferred.}}

* Click '''Transfer File''' box

Repeat the same steps with <code>znetboot.exec</code> and <code>curl.rexx</code> files.

==== (Optional) Check the configuration files ====
On 3270 client, enter following commands to check if the configuration files are correctly transferred:

<code>xedit alpine znetboot</code>

<code>xedit znetboot exec</code>

<code>xedit curl rex</code>

or <code>filel</code> and put <code>xedit</code> on CMD column to edit respective file.

==== Start ZNETBOOT ====
On 3270 client, type below command and wait till Figure 3.: [[File:X3270-3.png|right|300px|thumb|Figure 3.]]

<code>znetboot alpine</code>

= Installation =
If you install on z/VM, steps in this part does not involve the interaction with the 3270 client anymore. Everything is done in the terminal with SSH client.

If you install on KVM, you can either SSH into the installer (below) or directly use the console starting qemu.

Either installing in KVM or z/VM environments, from your workstation/laptop, you will be able to run:
$ ssh root@192.168.1.2 (change ip address to what you specified earlier)

Remaining steps are similar to installing Alpine on other architectures (x86, arm, ppc, etc.), either on KVM (using virtio/SCSI disks) or on z/VM with FBA DASDs. Installing on ECKD DASDs requires an additional step, as described below.

== Example ==
Below is the detailed walkthrough of installing Alpine on a single ECKD DASD using LVM and extend that LVM to the second ECKD DASD.

After SSH-ing into the Alpine installer, run:
# setup-alpine

<code>Select keyboard layout [none]:</code>
:press Enter for none

<code>Enter system hostname (short form, e.g. 'foo') [localhost]:</code>
:enter your hostname

<pre>
Available interfaces are: eth0.
Enter '?' for help on bridges, bonding and vlans.
Which one do you want to initialize? (or '?' or 'done') [eth0]:</pre>
:type 'eth0' or press Enter

<code>Ip address for eth0? (or 'dhcp', 'none', '?') [192.168.1.2]</code>
:enter ip address or 'dhcp'

<code>Netmask? [255.255.255.0]</code>
:enter netmask
<code>Gateway? (or 'none') [192.168.1.1]</code>
:enter gateway's ip address

<code>Do you want to do any manual network configuration? [no]</code>
:enter 'no' or press Enter

<code>DNS domain name? (e.g 'bar.com') []</code>
:enter domain name or press Enter for none

<code>DNS nameserver(s)? [8.8.8.8 ]</code>
:enter DNS nameserver

<code>Changing password for root</code>
:enter root password

<code>Which timezone are you in? ('?' for list) [UTC]</code>
:enter timezone or '?' for list of timezones

<code>HTTP/FTP proxy URL? (e.g. 'http://proxy:8080', or 'none') [none]</code>
:enter proxy or press Enter for none

<code>Enter mirror number (1-27) or URL to add (or r/f/e/done) [f]:</code>
:enter a number or 'r' or 'f' or 'e' or 'done' as described

<code>Which SSH server? ('openssh', 'dropbear' or 'none') [openssh]</code>
:enter SSH server or press Enter for openssh

<code>Which NTP client to run? ('busybox', 'openntpd', 'chrony' or 'none') [chrony]</code>
:enter 'busybox' or press Enter for chrony

''' (next step is the additional step for ECKD DASDs on z/VM)'''
<pre>
Available ECKD DASD(s) are:
0.0.04c0 (3390/0c 3990/e9 IBM)
0.0.05d1 (3390/0c 3990/e9 IBM)
Which ECKD DASD(s) would you like to be formatted using dasdfmt? (enter '?' for help) [all]</pre>
:enter 'all' or '0.0.04c0 0.0.05d1' '''(separated by a space)''' to format all/both DASDs
:enter '0.0.04c0' or '0.0.05d1' to format respective DASD
:enter '?' for help

<code>WARNING: Erase ECKD DASD 0.0.04c0? [y/N]:</code>
:enter 'y' to format

<pre>
Available disks are:
dasda (2.5 GB IBM 0.0.04c0)
Which disk(s) would you like to use? (or '?' for help or 'none') [dasda]</pre>
:enter 'dasda' or press Enter

<pre>
The following disk is selected:
dasda (2.5 GB IBM 0.0.04c0)
How would you like to use it? ('sys', 'data', 'lvm' or '?' for help) [?]</pre>
:enter 'lvm'

<pre>
The following disk is selected (with LVM):
dasda (2.5 GB IBM 0.0.04c0)
How would you like to use it? ('sys', 'data' or '?' for help) [?]</pre>
:enter 'sys' to install Alpine on disk

<pre>
WARNING: The following disk(s) will be erased:
dasda (2.5 GB IBM 0.0.04c0)
WARNING: Erase the above disk(s) and continue? [y/N]:</pre>
:enter 'y'

<code>Installation is complete. Please reboot.</code>
:the installation is finished

At this point, don't poweroff the installer right away. Go to [https://wiki.alpinelinux.org/wiki/S390x#Copying_SSH_keys_to_new_Alpine_system "Copying SSH keys to new Alpine system"] (below) to have SSH access to your new Alpine system.

== Copying SSH keys to new Alpine system ==

By default, Alpine disables root login with a password via SSH. SSH keys are used instead.

After the installer's done running (<code>Installation is complete. Please reboot.</code>), there are 2 ways to copy your SSH key into the new Alpine system:
* Option 1: mount the installed disk and copy the SSH keys while still at the installer's terminal
* Option 2: poweroff the installer, start the new Alpine system and directly add the SSH keys
::: if you install on KVM, boot the new Alpine system on qemu, and copy the SSH keys
::: if you install on z/VM, use the 3270 client to ipl the new Alpine system and copy the SSH keys

'''Option 1'''

If you use 'lvm' + 'sys' installation (like in above example), do:

:<code> # mount /dev/vg0/lv_root /mnt</code>

:<code> # cp -ar /root/.ssh /mnt/root</code>

If you use 'sys' (without LVM) installation, do:

:<code> # mount /dev/dasda3 /mnt</code> (change dasda to dasdb or dasdc, etc. for whichever DASD you chose)

:<code> # cp -ar /root/.ssh /mnt/root</code>

{{Note|In 'sys' installation, 1st partition is boot, 2nd partition is swap, 3rd partition is root }}

Then run <code> # poweroff</code>.

Go to [https://wiki.alpinelinux.org/wiki/S390x#Login_to_new_Alpine_system "Login to new Alpine system"]

'''Option 2'''

Run <code> # poweroff</code>.

If you use KVM, start qemu with new Alpine system (removing <code>-kernel</code>, <code>-initrd</code>, <code>-append</code> options)

If you use z/VM, open the 3270 client, login with your z/VM username and password. You may need to run <code> ipl cms</code>. Then run <code> ipl 04c0</code> (or whichever DASD device you chose as root disk in earlier steps).

Wait for new Alpine system go up, then login as root user while in the qemu console (on KVM) or 3270 client (on z/VM). Then run:
::<code> # mkdir /root/.ssh</code>
::<code> # wget https://your-website.com/your-ssh-key.pub -O /root/.ssh/authorized_keys</code>
::<code> # chmod 700 /root/.ssh</code>
::<code> # chmod 600 /root/.ssh/authorized_keys</code>

Go to [https://wiki.alpinelinux.org/wiki/S390x#Login_to_new_Alpine_system "Login to new Alpine system"]

== Login to new Alpine system ==
On your workstation/laptop, use SSH client to login new Alpine system:
<code> $ ssh root@192.168.1.2</code> (or whichever ip address you used)

== Extending LVM volume ==
After logging in to your new Alpine system, run:
<pre>
# apk add -q util-linux e2fsprogs-extra

# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
dasda 94:0 0 2.3G 0 disk
├─dasda1 94:1 0 100M 0 part /boot
└─dasda2 94:2 0 2.2G 0 part
├─vg0-lv_swap 254:0 0 588M 0 lvm [SWAP]
└─vg0-lv_root 254:1 0 1.6G 0 lvm /
dasdb 94:4 0 2.3G 0 disk

# dasdfmt -b 4096 -d cdl -yp /dev/dasdb

# fdasd -a /dev/dasdb

# pvcreate /dev/dasdb1

# vgextend vg0 /dev/dasdb1

# lvextend -l +100%FREE /dev/vg0/lv_root

# resize2fs /dev/vg0/lv_root

# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
dasda 94:0 0 2.3G 0 disk
├─dasda1 94:1 0 100M 0 part /boot
└─dasda2 94:2 0 2.2G 0 part
├─vg0-lv_swap 254:0 0 588M 0 lvm [SWAP]
└─vg0-lv_root 254:1 0 3.9G 0 lvm /
dasdb 94:4 0 2.3G 0 disk
└─dasdb1 94:5 0 2.3G 0 part
└─vg0-lv_root 254:1 0 3.9G 0 lvm /
</pre>

= Tips =
If you want to disable swap partition, after finishing NTP client step, quit the installer by pressing <code>Ctrl + C</code>. Then run following command to complete remaining steps:

<code># setup-disk -s 0</code>

{{Note|If you do 'sys' installation, there will be no swap partition anymore and 1st partition will be boot, 2nd partition will be root}}

= Known Issues =
1. Installation on 2 or more DASDs (either ECKD and FBA) on z/VM is not supported in the installer script (<code>setup-alpine</code>) at the moment. If you want to install/extend on more than 1 DASD, see [https://wiki.alpinelinux.org/wiki/S390x#Extending_LVM_volume "Extending LVM volume"]. However, installation on 2 or more virtio (SCSI) disks on KVM are supported just like other architectures.

= See more =
Running Alpine s390x containers on Docker: https://wiki.alpinelinux.org/wiki/S390x/Docker

S390x

2019-01-18T08:33:19Z

Tmhoang:

= The boot media =

For KVM, both ISO image and netboot media (kernel and initramfs) are supported.

For z/VM, netboot media is supported.

For LPAR, not yet supported.

Boot media are found at:

* http://dl-cdn.alpinelinux.org/alpine/v3.8/releases/s390x/

== Kernel parameters (and parmfile) ==
The Alpine s390x boot media requires following kernel parameters to work:

<code>ip=dhcp</code> : use DHCP for network configuration.

<code>ip=client-ip:server-ip:gw-ip:netmask:hostname:device:autoconf:dns1:dns2</code> : use static IP configuration, each field is separated by a colon <code>:</code>
* <code>client-ip</code> ip address of the guest VM where we are going to run the installer
* <code>server-ip</code> not used, leave blank or fill with <code>none</code>
* <code>gw-ip</code> the gateway ip address
* <code>netmask</code> the netmask
* <code>hostname</code> not used, leave blank or fill with <code>none</code>
* <code>device</code> the network interface of the guest VM, default is <code>eth0</code> if left blank
* <code>autoconf</code> not used, leave blank or fill with <code>none</code> or <code>off</code>
* <code>dns1</code> address of the DNS server
* <code>dns2</code> address of the 2nd DNS server

<code>alpine_repo=</code> : the location of the Alpine repository from which packages are downloaded.

:For stable release, use <code>http://dl-cdn.alpinelinux.org/alpine/v3.8/main</code>

:For rolling release, use <code>http://dl-cdn.alpinelinux.org/alpine/edge/main</code>

<code>modloop=</code> : the remote location of the image containing kernel's modules, required for LVM and raid setup.

:The remote location of the <code>modloop</code> image is the same as the kernel and initramfs (see below).

<code>ssh_key=</code> : the remote location of your SSH public key which is used to allow SSH connection into the installer. It will be downloaded and copied into <code>/root/.ssh/authorized_keys</code> in the installer.

{{Note|Fetching public keys from HTTP, HTTPS and FTPS are supported. HTTP should only be used in local development network where you own the network.}}

{{Note|Alpine Linux security policies are against using passwords for root access via SSH as we consider using public-private key pairs is a much better approach.}}

'''z/VM only'''

<code>dasd=</code> : the addresses of the DASD devices, either ECKD or FBA DASDs. Each device is separated with a comma.

<code>s390x_net=</code> : the network interface type and its subchannels. At the moment, only QETH layer 2 is supported, thus the name <code>qeth_l2</code> is used (see below).

= Pre-installation =

== KVM ==
Create a virtual disk:
$ qemu-img create alpine_disk.qcow2 5G

==== Using iso image ====
Download latest iso image from : http://dl-cdn.alpinelinux.org/alpine/v3.8/releases/s390x

Start qemu:

$ qemu-system-s390x -M s390-ccw-virtio \
-m 1024 -smp 2 -nographic -enable-kvm \
-net nic -net tap,ifname=tap0,script=no' \
-hda alpine_disk.qcow2 \
-boot d -cdrom alpine-standard-3.8.2-s390x.iso

==== Using netboot media ====
Download the latest [http://dl-cdn.alpinelinux.org/alpine/v3.8/releases/s390x/netboot-3.8.2/vmlinuz-vanilla kernel] and [http://dl-cdn.alpinelinux.org/alpine/v3.8/releases/s390x/netboot-3.8.2/initramfs-vanilla initramfs].

Start qemu: (modify <code>ip=</code> <code>alpine_repo=</code> <code>ssh_key=</code> for your needs)

$ qemu-system-s390x -M s390-ccw-virtio \
-m 1024 -smp 2 -nographic -enable-kvm \
-net nic -net tap,ifname=tap0,script=no' \
-hda alpine_disk.qcow2 \
-kernel vmlinuz-vanilla \
-initrd initramfs-vanilla \
-append "ip=192.168.1.2::192.168.1.1:255.255.255.0:none:eth0:none:8.8.8.8 alpine_repo=http://dl-cdn.alpinelinux.org/alpine/v3.8/main modloop=http://dl-cdn.alpinelinux.org/alpine/v3.8/releases/s390x/netboot-3.8.2/modloop-vanilla ssh_key=https://your-website.com/your-ssh-key.pub"

{{Note|If you have direct access to the qemu console, <code>ssh_key</code> might not be required.}}

== z/VM ==
To ease out the process of downloading the images, punch the readers, ipl, etc., [https://github.com/trothr/znetboot '''ZNETBOOT'''] is used.

==== Create the parm file ====
On your workstation/laptop, create a file named <code>alpine.znetboot</code> in your home directory with contents below (modify <code>dasd=</code><code>s390x_net=</code> <code>ip=</code> <code>alpine_repo=</code> <code>ssh_key=</code> for your needs)

<pre>
ZNETBOOT_KERNEL=http://dl-cdn.alpinelinux.org/alpine/v3.8/releases/s390x/netboot-3.8.2/vmlinuz-vanilla
ZNETBOOT_INITRD=http://dl-cdn.alpinelinux.org/alpine/v3.8/releases/s390x/netboot-3.8.2/initramfs-vanilla
ZNETBOOT_PROGRESS=1M

alpine_repo=http://dl-cdn.alpinelinux.org/alpine/v3.8/main
modloop=http://dl-cdn.alpinelinux.org/alpine/v3.8/releases/s390x/netboot-3.8.2/modloop-vanilla

dasd=0.0.04c0,0.0.05d1
s390x_net=qeth_l2,0.0.0560,0.0.0561,0.0.0562
ip=192.168.1.2::192.168.1.1:255.255.255.0:none:eth0:none:8.8.8.8

ssh_key=https://your-website.com/your-ssh-key.pub

</pre>

==== Upload to z/VM system via 3270 client ====
[[File:X3270-1.png|right|300px|thumb|Figure 1.]]
On your workstation/laptop, download 2 files [https://raw.githubusercontent.com/trothr/znetboot/master/znetboot.exec <code>znetboot.exec</code>], and [https://raw.githubusercontent.com/trothr/znetboot/master/curl.rexx <code>curl.rexx</code>] to your home directory.

Open 3270 client and log in the z/VM system with your z/VM username and password.

Upload 3 files <code>alpine.znetboot</code>, <code>znetboot.exec</code>, <code>curl.rexx</code> to the z/VM environment using the 3270 client (this tutorial uses x3270). On the top left corner, click "File", then "File Transfer". (Figure 1.)

Do following steps : (Figure 2.) [[File:X3270-2.png|right|300px|thumb|Figure 2.]]
* On "Local File Name" box, enter '''alpine.znetboot''' (the file in your laptop/workstation, at '''~/alpine.znetboot''')
* On "Host File Name" box, enter '''alpine znetboot''' (the file will be in z/VM console)

{{Note|Beware the difference between '''the dot <code>.</code>''' and '''the space <code> </code>''' characters in the file names.}}

* Choose '''Send to host'''
* Choose '''Host is VM/CMS'''
* Choose either '''Fixed''' or '''Variable''' for '''Record Format'''
:Enter a number for LRECL and BLKSIZE, respectively
{{Note|Any line in '''alpine.znetboot''' that has more 80 chars (columns) will be splitted into more than 1 line when uploaded to z/VM (CMS) console via 3270. Count the number of characters/column of the longest line in your '''alpine.znetboot''' and fill it in LRECL. There is no restriction for BLKSIZE but 80 is preferred.}}

* Click '''Transfer File''' box

Repeat the same steps with <code>znetboot.exec</code> and <code>curl.rexx</code> files.

==== (Optional) Check the configuration files ====
On 3270 client, enter following commands to check if the configuration files are correctly transferred:

<code>xedit alpine znetboot</code>

<code>xedit znetboot exec</code>

<code>xedit curl rex</code>

or <code>filel</code> and put <code>xedit</code> on CMD column to edit respective file.

==== Start ZNETBOOT ====
On 3270 client, type below command and wait till Figure 3.: [[File:X3270-3.png|right|300px|thumb|Figure 3.]]

<code>znetboot alpine</code>

= Installation =
If you install on z/VM, steps in this part does not involve the interaction with the 3270 client anymore. Everything is done in the terminal with SSH client.

If you install on KVM, you can either SSH into the installer (below) or directly use the console starting qemu.

Either installing in KVM or z/VM environments, from your workstation/laptop, you will be able to run:
$ ssh root@192.168.1.2 (change ip address to what you specified earlier)

Remaining steps are similar to installing Alpine on other architectures (x86, arm, ppc, etc.), either on KVM (using virtio/SCSI disks) or on z/VM with FBA DASDs. Installing on ECKD DASDs requires an additional step, as described below.

== Example ==
Below is the detailed walkthrough of installing Alpine on a single ECKD DASD using LVM and extend that LVM to the second ECKD DASD.

After SSH-ing into the Alpine installer, run:
# setup-alpine

<code>Select keyboard layout [none]:</code>
:press Enter for none

<code>Enter system hostname (short form, e.g. 'foo') [localhost]:</code>
:enter your hostname

<pre>
Available interfaces are: eth0.
Enter '?' for help on bridges, bonding and vlans.
Which one do you want to initialize? (or '?' or 'done') [eth0]:</pre>
:type 'eth0' or press Enter

<code>Ip address for eth0? (or 'dhcp', 'none', '?') [192.168.1.2]</code>
:enter ip address or 'dhcp'

<code>Netmask? [255.255.255.0]</code>
:enter netmask
<code>Gateway? (or 'none') [192.168.1.1]</code>
:enter gateway's ip address

<code>Do you want to do any manual network configuration? [no]</code>
:enter 'no' or press Enter

<code>DNS domain name? (e.g 'bar.com') []</code>
:enter domain name or press Enter for none

<code>DNS nameserver(s)? [8.8.8.8 ]</code>
:enter DNS nameserver

<code>Changing password for root</code>
:enter root password

<code>Which timezone are you in? ('?' for list) [UTC]</code>
:enter timezone or '?' for list of timezones

<code>HTTP/FTP proxy URL? (e.g. 'http://proxy:8080', or 'none') [none]</code>
:enter proxy or press Enter for none

<code>Enter mirror number (1-27) or URL to add (or r/f/e/done) [f]:</code>
:enter a number or 'r' or 'f' or 'e' or 'done' as described

<code>Which SSH server? ('openssh', 'dropbear' or 'none') [openssh]</code>
:enter SSH server or press Enter for openssh

<code>Which NTP client to run? ('busybox', 'openntpd', 'chrony' or 'none') [chrony]</code>
:enter 'busybox' or press Enter for chrony

''' (next step is the additional step for ECKD DASDs on z/VM)'''
<pre>
Available ECKD DASD(s) are:
0.0.04c0 (3390/0c 3990/e9 IBM)
0.0.05d1 (3390/0c 3990/e9 IBM)
Which ECKD DASD(s) would you like to be formatted using dasdfmt? (enter '?' for help) [all]</pre>
:enter 'all' or '0.0.04c0 0.0.05d1' '''(separated by a space)''' to format all/both DASDs
:enter '0.0.04c0' or '0.0.05d1' to format respective DASD
:enter '?' for help

<code>WARNING: Erase ECKD DASD 0.0.04c0? [y/N]:</code>
:enter 'y' to format

<pre>
Available disks are:
dasda (2.5 GB IBM 0.0.04c0)
Which disk(s) would you like to use? (or '?' for help or 'none') [dasda]</pre>
:enter 'dasda' or press Enter

<pre>
The following disk is selected:
dasda (2.5 GB IBM 0.0.04c0)
How would you like to use it? ('sys', 'data', 'lvm' or '?' for help) [?]</pre>
:enter 'lvm'

<pre>
The following disk is selected (with LVM):
dasda (2.5 GB IBM 0.0.04c0)
How would you like to use it? ('sys', 'data' or '?' for help) [?]</pre>
:enter 'sys' to install Alpine on disk

<pre>
WARNING: The following disk(s) will be erased:
dasda (2.5 GB IBM 0.0.04c0)
WARNING: Erase the above disk(s) and continue? [y/N]:</pre>
:enter 'y'

<code>Installation is complete. Please reboot.</code>
:the installation is finished

At this point, don't poweroff the installer right away. Go to [https://wiki.alpinelinux.org/wiki/S390x#Copying_SSH_keys_to_new_Alpine_system "Copying SSH keys to new Alpine system"] (below) to have SSH access to your new Alpine system.

== Copying SSH keys to new Alpine system ==

By default, Alpine disables root login with a password via SSH. SSH keys are used instead.

After the installer's done running (<code>Installation is complete. Please reboot.</code>), there are 2 ways to copy your SSH key into the new Alpine system:
* Option 1: mount the installed disk and copy the SSH keys while still at the installer's terminal
* Option 2: poweroff the installer, start the new Alpine system and directly add the SSH keys
::: if you install on KVM, boot the new Alpine system on qemu, and copy the SSH keys
::: if you install on z/VM, use the 3270 client to ipl the new Alpine system and copy the SSH keys

'''Option 1'''

If you use 'lvm' + 'sys' installation (like in above example), do:

:<code> # mount /dev/vg0/lv_root /mnt</code>

:<code> # cp -ar /root/.ssh /mnt/root</code>

If you use 'sys' (without LVM) installation, do:

:<code> # mount /dev/dasda3 /mnt</code> (change dasda to dasdb or dasdc, etc. for whichever DASD you chose)

:<code> # cp -ar /root/.ssh /mnt/root</code>

{{Note|In 'sys' installation, 1st partition is boot, 2nd partition is swap, 3rd partition is root }}

Then run <code> # poweroff</code>.

Go to [https://wiki.alpinelinux.org/wiki/S390x#Login_to_new_Alpine_system "Login to new Alpine system"]

'''Option 2'''

Run <code> # poweroff</code>.

If you use KVM, start qemu with new Alpine system (removing <code>-kernel</code>, <code>-initrd</code>, <code>-append</code> options)

If you use z/VM, open the 3270 client, login with your z/VM username and password. You may need to run <code> ipl cms</code>. Then run <code> ipl 04c0</code> (or whichever DASD device you chose as root disk in earlier steps).

Wait for new Alpine system go up, then login as root user while in the qemu console (on KVM) or 3270 client (on z/VM). Then run:
::<code> # mkdir /root/.ssh</code>
::<code> # wget https://your-website.com/your-ssh-key.pub -O /root/.ssh/authorized_keys</code>
::<code> # chmod 700 /root/.ssh</code>
::<code> # chmod 600 /root/.ssh/authorized_keys</code>

Go to [https://wiki.alpinelinux.org/wiki/S390x#Login_to_new_Alpine_system "Login to new Alpine system"]

== Login to new Alpine system ==
On your workstation/laptop, use SSH client to login new Alpine system:
<code> $ ssh root@192.168.1.2</code> (or whichever ip address you used)

== Extending LVM volume ==
After logging in to your new Alpine system, run:
<pre>
# apk add -q util-linux e2fsprogs-extra

# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
dasda 94:0 0 2.3G 0 disk
├─dasda1 94:1 0 100M 0 part /boot
└─dasda2 94:2 0 2.2G 0 part
├─vg0-lv_swap 254:0 0 588M 0 lvm [SWAP]
└─vg0-lv_root 254:1 0 1.6G 0 lvm /
dasdb 94:4 0 2.3G 0 disk

# dasdfmt -b 4096 -d cdl -yp /dev/dasdb

# fdasd -a /dev/dasdb

# pvcreate /dev/dasdb1

# vgextend vg0 /dev/dasdb1

# lvextend -l +100%FREE /dev/vg0/lv_root

# resize2fs /dev/vg0/lv_root

# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
dasda 94:0 0 2.3G 0 disk
├─dasda1 94:1 0 100M 0 part /boot
└─dasda2 94:2 0 2.2G 0 part
├─vg0-lv_swap 254:0 0 588M 0 lvm [SWAP]
└─vg0-lv_root 254:1 0 3.9G 0 lvm /
dasdb 94:4 0 2.3G 0 disk
└─dasdb1 94:5 0 2.3G 0 part
└─vg0-lv_root 254:1 0 3.9G 0 lvm /
</pre>

= Tips =
If you want to disable swap partition, after finishing NTP client step, quit the installer by pressing <code>Ctrl + C</code>. Then run following command to complete remaining steps:

<code># setup-disk -s 0</code>

{{Note|If you do 'sys' installation, there will be no swap partition anymore and 1st partition will be boot, 2nd partition will be root}}

= Known Issues =
1. Installation on 2 or more DASDs (either ECKD and FBA) on z/VM is not supported in the installer script (<code>setup-alpine</code>) at the moment. If you want to install/extend on more than 1 DASD, see [https://wiki.alpinelinux.org/wiki/S390x#Extending_LVM_volume "Extending LVM volume"]. However, installation on 2 or more virtio (SCSI) disks on KVM are supported just like other architectures.

= See more =
Running Alpine s390x containers on Docker: https://wiki.alpinelinux.org/wiki/S390x/Docker

Tutorials and Howtos

2019-01-18T08:30:38Z

Tmhoang:

[[Image:package_edutainment.svg|right|link=]]
{{TOC left}}
'''Welcome to Tutorials and Howtos, a place of basic and advanced configuration tasks for your Alpine Linux.'''

The tutorials are hands-on and the reader is expected to try and achieve the goals described in each step, possibly with the help of a good example. The output in one step is the starting point for the following step.

Howtos are smaller articles explaining how to perform a particular task with Alpine Linux.

We encourage people to send in both complete articles as well as requesting topics to be covered. If you think you have the skills and knowledge to write an Alpine Linux related article please do so on this Wiki. If you want to request a topic, please add your request in this page's [[Talk:Tutorials_and_Howtos|Discussion]].

{{Clear}}
== Storage ==

* [[Alpine local backup|Alpine local backup (lbu)]] ''(Permanently store your modifications in case your box needs reboot)'' 
** [[Back Up a Flash Memory Installation]] 
** [[Manually editing a existing apkovl]]

* [[Setting up disks manually]] 
* [[Setting up a software RAID array]]

* [[Raid Administration]]
* [[Setting up encrypted volumes with LUKS]]
* [[Setting up LVM on LUKS]]
* [[Setting up Logical Volumes with LVM]]
** [[Setting up LVM on GPT-labeled disks]]
** [[Installing on GPT LVM]]
* [[Filesystems|Formatting HD/Floppy/Other]] 

* [[Setting up iSCSI]]
** [[iSCSI Raid and Clustered File Systems]]
* [[Setting up NBD]]
* [[Setting up ZFS on LUKS]]
* [[High performance SCST iSCSI Target on Linux software Raid]] ''(deprecated)'' 
* [[Linux iSCSI Target (TCM)]]
* [[Disk Replication with DRBD]] 

* [[Burning ISOs]] 
* [[Partitioning and Bootmanagers]]
* [[Migrating data]]
* [[Create a bootable SDHC from a Mac]]
* [[Alpine on ARM]]

== Networking ==

* [[Configure Networking]]
* [[Connecting to a wireless access point]]
* [[Bonding]]
* [[Vlan]]
* [[Bridge]]
* [[OpenVSwitch]]
* [[How to configure static routes]]

* [[Alpine Wall]] - [[How-To Alpine Wall]] - [[Alpine Wall User's Guide]] ''(a new firewall management framework)''

* [[PXE boot]]

* [[Using serial modem]]
* [[Using HSDPA modem]]
* [[Setting up Satellite Internet Connection]]
* [[Using Alpine on Windows domain with IPSEC isolation]]

* [[Setting up a ssh-server]] ''(Using ssh is a good way to administer your box remotely)'' 
* [[How to setup a wireless access point]] ''(Setting up Secure Wireless AP w/ WPA encryption with bridge to wired network)''
* [[Setting up a OpenVPN server with Alpine]] ''(Allowing single users or devices to remotely connect to your network)''

* [[Experiences with OpenVPN-client on ALIX.2D3]] 

* [[Generating SSL certs with ACF]] 
* [[Setting up unbound DNS server]]
* [[Setting up nsd DNS server]]
* [[TinyDNS Format]]
* [[Fault Tolerant Routing with Alpine Linux]] 
* [[Freeradius Active Directory Integration]]
* [[Multi_ISP]] ''(Dual-ISP setup with load-balancing and automatic failover)''
* [[OwnCloud]] ''(Installing OwnCloud)''

* [[Seafile: setting up your own private cloud]]

== Post-Install ==


* [[Alpine Linux package management|Package Management (apk)]] ''(How to add/remove packages on your Alpine)''

** [[Comparison with other distros]]
* [[Alpine local backup|Alpine local backup (lbu)]] ''(Permanently store your modifications in case your box needs reboot)''
** [[Back Up a Flash Memory Installation]] 
** [[Manually editing a existing apkovl]]
* [[Alpine Linux Init System|Init System (OpenRC)]] ''(Configure a service to automatically boot at next reboot)''
** [[Multiple Instances of Services]]

* [[Alpine setup scripts#setup-xorg-base|Setting up Xorg]]
* [[Upgrading Alpine]]


* [[Setting up a ssh-server]] ''(Using ssh is a good way to administer your box remotely)''
* [[setup-acf]] ''(Configures ACF (webconfiguration) so you can manage your box through https)''
* [[Changing passwords for ACF|Changing passwords]]
* [[Ansible]] ''(Configuration management)''

* [[Enable Serial Console on Boot]]

* [[How to get regular stuff working]] ''some notes on need-to-know topics''
* [[Installing Oracle Java]]
* [[Rsnapshot|Setting up periodic backups with <samp>rsnapshot</samp>]]

== Virtualization==

* [[Xen Dom0]] ''(Setting up Alpine as a dom0 for Xen hypervisor)''
* [[Xen Dom0 on USB or SD]]
* [[Create Alpine Linux PV DomU]]
* [[Xen PCI Passthrough]]
* [[Xen LiveCD]]
* [[qemu]]
* [[KVM]] ''(Setting up Alpine as a KVM hypervisor)''
* [[LXC]] ''(Setting up a Linux container in Alpine Linux)''
* [[Docker]]
* [[Install_Alpine_on_VirtualBox]]

== Desktop Environment ==

* [[Awesome(wm) Setup]]
* [[EyeOS]] ''(Cloud Computing Desktop)''
* [[Gnome Setup]]
* [[MATE|MATE Setup]]
* [[Oneye]] ''(Cloud Computing Desktop - Dropbox Alternative)''
* [[Owncloud]] ''(Cloud Computing Desktop - Dropbox Alternative)''
** (to be merged with [[OwnCloud]] ''(Your personal Cloud for storing and sharing your data on-line)'')
* [[Remote Desktop Server]]
* [[Suspend on LID close]]
* [[Sway]]
* [[XFCE Setup]] and [[Xfce Desktop|Desktop Ideas]]
* [[Installing Adobe flash player for Firefox]]
* [[Sound Setup]]
* [[Printer Setup]]
* [[Default applications]]

== Raspberry Pi ==

* [[Raspberry Pi|Raspberry Pi (Installation)]]
* [[Classic install or sys mode on Raspberry Pi]]
* [[RPI Video Receiver]] ''(network video decoder using Rasperry Pi and omxplayer)''
* [[Linux Router with VPN on a Raspberry Pi]]
* [[Linux Router with VPN on a Raspberry Pi (IPv6)]]
* [[Raspberry Pi 3 - Configuring it as wireless access point -AP Mode]]
* [[Raspberry Pi 3 - Setting Up Bluetooth]]

== PowerPC ==

* [[Ppc64le|Powepc64le (Installation)]]

== IBM Z (IBM z Systems) ==

* [[s390x|s390x (Installation)]]

== Applications ==

=== Telephony ===
* [[Setting up Zaptel/Asterisk on Alpine]]
** [[Setting up Streaming an Asterisk Channel]]
* [[Freepbx on Alpine Linux]]
* [[FreePBX_V3]] ''(FreeSWITCH, Asterisk GUI web acces tool)''
* [[2600hz]] ''(FreeSWITCH, Asterisk GUI web access tool)''
* [[Kamailio]] ''(SIP Server, formerly OpenSER)''

=== Mail ===
* [[Hosting services on Alpine]] ''(Hosting mail, webservices and other services)''
** [[Hosting Web/Email services on Alpine]]
* [[ISP Mail Server HowTo]] 
** [[ISP Mail Server Upgrade 2.x]]
** [[ISP Mail Server 2.x HowTo]] ''(Beta, please test)''
** [[ISP Mail Server 3.x HowTo]]
* [[Roundcube]] ''(Webmail system)''
* [[Setting up postfix with virtual domains]]
* [[Protecting your email server with Alpine]]
* [[Setting up clamsmtp]]
* [[Setting up dovecot with imap and ssl]]
* [[relay email to gmail (msmtp, mailx, sendmail]]

=== HTTP ===
* [[Lighttpd]]
** [[Lighttpd Https access]]
** [[Setting Up Lighttpd with PHP]]
** [[Setting Up Lighttpd With FastCGI]]
* [[Cherokee]]
* [[Nginx]]
** [[Nginx_with_PHP#Nginx_with_PHP|Nginx with PHP]]
** [[Nginx as reverse proxy with acme (letsencrypt)]]
* [[Apache]]
** [[Apache with php-fpm]]
** [[Setting Up Apache with PHP]]
** [[Apache authentication: NTLM Single Signon]]

* [[High Availability High Performance Web Cache]] ''(uCarp + HAProxy for High Availability Services such as Squid web proxy)'' 

* [[Setting up Transparent Squid Proxy]] 
** [[SqStat]] ''(Script to look at active squid users connections)''
** [[Obtaining user information via SNMP]] ''(Using squark-auth-snmp as a Squid authentication helper)'' 
* [[Setting up Explicit Squid Proxy]]

* [[Drupal]] ''(Content Management System (CMS) written in PHP)''
* [[WordPress]] ''(Web software to create website or blog)''
* [[MediaWiki]] ''(Free web-based wiki software application)''
* [[DokuWiki]]
* [[Darkhttpd]]
* [[Tomcat]]

=== Other Servers ===
* [[Setting up a ssh-server]] ''(Using ssh is a good way to administer your box remotely)''

* [[Setting up a nfs-server]]
* [[Setting up a samba-server]] ''(standard file sharing)''
* [[Setting up a samba-ad-dc]] ''(Active Directory compatible domain controller)''
* [[Phpizabi]] ''(Social Networking Platform)''
* [[Statusnet]] ''(Microblogging Platform)''
* [[Pastebin]] ''(Pastebin software application)''
* [[Setting up Transmission (bittorrent) with Clutch WebUI]]

* [[Patchwork]] ''(Patch review management system)''
* [[Redmine]] ''(Project management system)''
* [[Request-Tracker]] ''(Ticket system)''
* [[OsTicket]] ''(Ticket system)''
* [[Setting up trac wiki|Trac]] ''(Enhanced wiki and issue tracking system for software development projects)''

* [[Cgit]]
** [[Setting up a git repository server with gitolite and cgit]] 
* [[Roundcube]] ''(Webmail system)''
* [[Glpi]] ''(Manage inventory of technical resources)''

* [[How to setup a Alpine Linux mirror]]
* [[Cups]]
* [[NgIRCd]] ''(Server for Internet Relay Chat/IRC)''
* [[How To Setup Your Own IRC Network]] ''(Using {{Pkg|charybdis}} and {{Pkg|atheme-iris}})''
* [[OpenVCP]] ''(VServer Control Panel)''
* [[Mahara]] ''(E-portfolio and social networking system)''
* [[Chrony and GPSD | Using chrony, gpsd, and a garmin LVC 18 as a Stratum 1 NTP source ]]
* [[Sending SMS using gnokii]]
* [[IPTV How To|Internet Protocol television (IPTV)]]
* [[UniFi_Controller]]

=== Monitoring ===
* Setting up [[collectd]]
* [[Traffic monitoring]] 
* [[Setting up traffic monitoring using rrdtool (and snmp)]] 
* [[Setting up monitoring using rrdtool (and rrdcollect)]]
* [[Setting up Cacti|Cacti]] ''(Front-end for rrdtool networking monitor)''
* [[LTTng]] ''(Kernel and userspace tracing)''
* [[Setting up Zabbix|Zabbix]] ''(Monitor and track the status of network services and hardware)''
* [[Setting up A Network Monitoring and Inventory System]] ''(Nagios + OpenAudit and related components)'' 
** [[Setting up NRPE daemon]] ''(Performs remote Nagios checks)'' 
* [[Setting up Smokeping|Smokeping]] ''(Network latency monitoring)'' 
** [[Setting up MRTG and Smokeping to Monitor Bandwidth Usage and Network Latency]]
* [[Setting Up Fprobe And Ntop|Ntop]] ''(NetFlow collection and analysis using a remote fprobe instance)'' 
* [[Cvechecker]] ''(Compare installed packages for Common Vulnerabilities Exposure)'' 

* [[IP Accounting]] 
* [[Obtaining user information via SNMP]] ''(Using squark-auth-snmp as a Squid authentication helper)'' 
* [[SqStat]] ''(Script to look at active squid users connections)''

* [[Piwik]] ''(A real time web analytics software program)''
* [[Awstats]] ''(Free log file analyzer)''
* [[Intrusion Detection using Snort]]
** [[Intrusion Detection using Snort, Sguil, Barnyard and more]]
* [[Dglog]] ''(Log analyzer for the web content filter DansGuardian)''

* [[Webmin]] ''(A web-based interface for Linux system)''
* [[PhpPgAdmin]] ''(Web-based administration tool for PostgreSQL)''
* [[PhpMyAdmin]] ''(Web-based administration tool for MYSQL)''
* [[PhpSysInfo]] ''(A simple application that displays information about the host it's running on)''
* [[Linfo]]

* [[Setting up lm_sensors]]

* [[ZoneMinder video camera security and surveillance]]

== Misc ==

* [[:Category:Shell]]
* [[:Category:Programming]]
* [[Running glibc programs]]
* [[:Category:Drivers]]
* [[:Category:Multimedia]]
* [[Kernel Modesetting]]
* [[CPU frequency scaling]]

== Complete Solutions ==
* [[DIY Fully working Alpine Linux for Allwinner and Other ARM SOCs]]
* [[Replacing non-Alpine Linux with Alpine remotely]]
* [[High performance SCST iSCSI Target on Linux software Raid]]
* [[Fault Tolerant Routing with Alpine Linux]]
* [[Experiences with OpenVPN-client on ALIX.2D3]]
* [[Building a cloud with Alpine Linux]]

* [[ISP Mail Server HowTo]] ''(Postfix+PostfixAdmin+DoveCot+Roundcube+ClamAV+Spamd - A full-serivce ISP mail server)''
** [[ISP Mail Server Upgrade 2.x]]
** [[ISP Mail Server 2.x HowTo]] ''(Beta, please test)''
* [[High Availability High Performance Web Cache]] ''(uCarp + HAProxy for High Availability Services such as Squid web proxy)''
* [[Setting up A Network Monitoring and Inventory System]] ''(Nagios + OpenAudit and related components)'' 
* [[Streaming Security Camera Video with VLC]]
* [[Dynamic Multipoint VPN (DMVPN)]] combined with [[Small_Office_Services]]