Yes, this is how we do here. We have SWAPGEN in the PROFILE EXEC of the guest or a common disk that all guests read and each time the guest is logged on the SWAP VDISKS are defined and allocated. Works like a charm!
Thank You, Terry Martin Lockheed Martin CMS - CITIC 3300 Lord Baltimore Drive, Suite 200, 21244 Engineering Computing Mainframe Support Cell - 443 632-4191 -----Original Message----- From: Linux on 390 Port [mailto:[email protected]] On Behalf Of David Boyes Sent: Wednesday, April 20, 2011 11:43 AM To: [email protected] Subject: Re: vdisk > Since it's a fresh disk every time, you'd have to do the mkswap every > time > you log in, so my guess is that's why you'd need the mkswap and > subsequent > swapon in the boot.local. The vdisk wouldn't be formatted when you get > it at > each fresh logon. I'll point out that running SWAPGEN before Linux IPL is intended to solve this problem. IPL CMS in the Linux guest at boot, and run SWAPGEN in the PROFILE EXEC. The swap disk is formatted and marked as a swap disk, and Linux "just works" from release to release, without having to do local mods inside the Linux system. --d b ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/ ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
