All I can say is that it worked fine on my SuSE SLES7 2.4.7 system. "Only two things are infinite: the Universe and human stupidity, and I'm not so sure about the Universe." - Albert Einstein Gordon Wolfe, Ph.D. (425)865-5940 VM Technical Services, The Boeing Company
> ---------- > From: Kern, Thomas > Reply To: Linux on 390 Port > Sent: Friday, August 16, 2002 9:59 AM > To: [EMAIL PROTECTED] > Subject: Re: Can Linux disks on VM be shared read-only? > > I tried to add the (ro) flag to the parmfile, but it interfered with a > vdisk > that I had later in the parameter. I have a 205 minidisk as the last in my > list (dasd=591-597,205 for the maintenance server) and I tried > dasd=591-592,593(ro),594-597,205 for my production servers. This did get > an > extra message about 593 being flagged as read-only, but it also flagged > 205 > as read-only and stopped my ability to use it as swap. This is a > TurboLinux > 2.4.7 system. > > /Thomas Kern > /(301)903-2211 > > -----Original Message----- > From: Wolfe, Gordon W [mailto:[EMAIL PROTECTED]] > Sent: Friday, August 16, 2002 12:41 > To: [EMAIL PROTECTED] > Subject: Re: Can Linux disks on VM be shared read-only? > > > It is possible to share a disk r/o among multiple images. We're doing it > with 14 SUSE SLES7 images sharing a common /usr disk under VM. This is > the > 294 disk in our setup. > > There are several "gotcha's", though. > <...snipped...> > Also, each image should use this in the parmfile, or /etc/zipl.conf, or > whatever to ensure that the 294 is to be used r/o by Linux: > > ... dasd=293,292,294(ro),295-29F ... > <...snipped...> > >
