> Yes, there is, but you run into data integrity problems, and data > synchronization problems. If you make /usr read-only to all the systems > sharing it, you can avoid both of those problems, until it comes time to > add/change/remove something. Then, you're looking at methods to circumvent > the problems that can cause, or re-booting all the systems at the same time > to pick up the changes. (You may not need to reboot, but taking the system > down to single user mode so that the file system can be unmounted and > re-mounted is as close as you can get without actually rebooting.) One > possibility would be to have multiple copies of /usr, and update the VM > guest's CP directories to point to the most recent one so that when the > system is shutdown, logged off, and back on again, it will pick up the new > file system. Unless you're talking about enough images being run that DASD > space is still conserved, it's kind of pointless. I don't think three > images would qualify for me to deal with that hassle. NFS/GFS/XFS start > looking a lot better at this point.
Could someone with /usr mounted ro try this? mount /usr -o remount,ro I think it will work; if not it will fail gracefully. I was going to boot the possum and try it, but I've taken to putting everything into one partition these days. -- Cheers John Summerfield Microsoft's most solid OS: http://www.geocities.com/rcwoolley/ Note: mail delivered to me is deemed to be intended for me, for my disposition.
