On 31 Jan 2022 09:56, Alan Altmark wrote: > On Monday, 01/31/2022 at 08:20 GMT, "Rob van der Heij" wrote: > > And since you may not be able to do much repairing on a R/O disk of a dead > > Linux guest, why not make it MRD so you can get a R/W link when you have > > to, but not when you shouldn't. > > I recommend against that unless you're actively repairing the disk. User > A should not have access to User B's data unless there is a reason (e.g. > open repair ticket), as it creates an unnecessary and unauditable (by User > B) data access path to User B's data. > > As usual, you have to balance convenience against security. Granting > access is a minor effort for the sysprog, not justifying "just in case" > access rights.
in this case, it's a single person (me) with multiple VMs and they're all dedicated to the same task (testing OSS), so sharing the disks as normal thing shouldn't be a problem. we've been sharing resources via network layers, but maybe we should see about doing a read-only DASD share from one into the other. at any rate, our admin added RR & W passwords, and i was able to link the disks in, and fixup the rootfs. thanks for the tip. it was a lot easier than trying to netboot install media. -mike ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
signature.asc
Description: PGP signature
