CMS doesn¹t need a writable 191, as others have already said. Also, Linux doesn¹t use the 191 at all, so the only moment that the 191 needs to be stable is when the guest(s) login. This means that you can likely grab it r/w to add things like kickstart files without affecting any of the guests.
-- Robert P. Nix Mayo Foundation .~. RO-OE-5-55 200 First Street SW /V\ 507-284-0844 Rochester, MN 55905 /( )\ ----- ^^-^^ "In theory, theory and practice are the same, but in practice, theory and practice are different." On 10/28/08 11:50 AM, "Mary Anne Matyaz" <[EMAIL PROTECTED]> wrote: > Well, two things. I thought you had to have a writable A disk for CMS? And we > do need > a redhat.conf file on there when we kickstart the linux, not so much > afterwards. > MA > > On Tue, Oct 28, 2008 at 12:45 PM, RPN01 <[EMAIL PROTECTED]> wrote: >> If you're just IPLing CMS to set things up and then IPL Linux, is there >> really a reason to have multiple 191 minidisks? We share a single read/only >> 191 minidisk among all the Linux guests, in both LPARs. They all end up >> IPLing 391, and we've added a piece to the profile that looks for userid() >> exec, and executes it, if found, as part of the process, allowing for the >> more odd of the Linux images to still share the one 191 minidisk. >> >> If you can do it with one, it seems a shame to have all those one cyl >> minidisks hanging around everywhere. Plus, if you need to make a change to >> something in the way they're brought up, you can do it in one place, instead >> of having to link and fix hundreds of them.
