There¹s still an advantage to starting CMS before Linux. We have a standard
profile (indeed, all our Linux images share a 191 minidisk read-only) that
checks which LPAR the image was last IPLed in, and checks for an image-named
exec to do any non-standard setup required. I¹m looking at adding the vdisk
setup to this profile. Once all this is done, CP IPLs the image, and Linux
starts up.
I don¹t see CMS first as a ³caper². It¹s a tool which has many uses, and
serves some of the same purposes as the available BIOS menus in the Intel
world, except with much greater flexibility.
--
.~. Robert P. Nix Mayo Foundation
/V\ RO-OC-1-13 200 First Street SW
/ ( ) \ 507-284-0844 Rochester, MN 55905
^^-^^ -----
"In theory, theory and practice are the same, but
in practice, theory and practice are different."
> From: John Summerfield <[EMAIL PROTECTED]>
> David Boyes wrote:
>
>> 5) Set your Linux guests up to IPL CMS first, then put a call to SWAPGEN
>> into their PROFILE EXEC. The syntax of SWAPGEN is documented in the
>> comments in the exec.
>>
>
> It shouldn't be hard to hook a mkswap command into /etc/inittab, to run
> before (almost) everything else and do away with this "ipl cms first" caper.
>
> or even in /linuxrc (in the initial ram disk).
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
