The Linux file names shown in the table are not part of the AD system. Rather, they are the names we decided to use when installing these devices on our ThinkPad/EFS system. They are shown here for completeness. A important factor in our setup is to have an IPLable system on the primary ThinkPad hard disk. Although we will later install a second hard disk, we want to be able to IPL OS/390 without the second disk installed.
At the system level, we defined a S/390 system with 256 MB central storage and 64 MB expanded storage. The expanded storage size was completely arbitrary. We wanted our total system definition to be small enough to avoid Linux paging. We could have defined larger central storage, or no expanded storage, or a different combination of storage sizes.
3.2.4 An unzip program
A
3.2.5 Installation tasks
We needed to perform the following tasks to install our OS/390 system:
1.Decide where to place the files containing the emulated volumes.
2.Unzip the required
These steps are described in some detail in the following sections.
Unzipping and installing AWSCKD CD-ROM files
The installation of AD
We found that the easiest way to do the following process is to open two
One window for the unzip and ckdconvaws commands, as userid flexes
One window for mount commands and other utility commands, with an su to root
Having separate windows for the two major commands is convenient because root authority is needed for mount while the other functions should be under userid flexes.
Mount CD
Mount the first AD CD-ROM:
# | mount /dev/cdrom /mnt/cdrom | (issue from root) |
$ | ls /mnt/cdrom/os390 |
|
devmap.mvs ickdsf.ipl os39ra.zip sadss.ipl devmap.nme migrate.doc readme.mvs
Unzip and convert a volume
The output of the unzip command can be piped directly to the ckdconvaws command:
$unzip
FSIDC180 cylinder nnn Completed in mmm milliseconds
FSIDC190 CKD conversion completed (3339 cyls copied, 0 cyl ignored)
24S/390 PID: ThinkPad Enabled for S/390