The maintenance is what would get me. We will have a customised set of packages for each installation because each linux install will have a different task. For our setup the maintenance overhead alone seems like enough to keep me from exploring it too much. Besides, you make it sound so fun!!!!
>>> [EMAIL PROTECTED] 9/13/2004 12:11:14 PM >>> > I have a question about sharing /usr with multiple vm guests. Is this a > recommended acrchitecture? Are there any benefits to doing this other > than saving space. It seems to me this could be problematic when > applying fixes from yast. I welcome any input on this subject. I do this all the time (both PC class and mainframe class Linux). On the mainframe, you get some storage constraint relief which is theoretically important because you might be running thousands of Linux instances. In any case, you get tremendous installation and maint relief, with some substantial caveats. Any time you have shared filesystem storage (shared disks) and you then perform an installation or upgrade, there will be some pieces that fall into the shared storage and some that fall outside of the shared areas. Bringing these into sanity, between the "master" where you did the maint and the "slaves" (or ... give me a better term) :-S which access that shared storage, is a pain. You can re-run RPM on the sharers (the "slaves"), and you'll get a bazillion errors. You can probably ignore most of the errors. But are you really sure? Besides, it's inelegant. And what about customizations? You might need to distribute your own special config of whatever you installed or upgraded. Re-running RPM on all your sharers would probably not get your custom config kicked out to them. RPM does not deal with read-only volumes. IT WOULD BE NICE if it could/would check the file to be installed (into a R/O directory) and IFF the file to be placed there matches a file already there, ignore the fact that he (RPM) cannot write the file he wants to write. It's already there! Right? But if you can put up with stuff like this, then I recommend sharing /usr (and /opt). No sarcasm here: I really run this way all the time. It's great! -- R; ---------------------------------------------------------------------- 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 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
