On Mar 4, 2005, at 2:31 PM, James Melin wrote:
My boss is asking me what parts of a Linux file system can be shared.
My somewhat generic answer was 'The parts that can be guaranteed to only ever be read only'.
He countered that he read it could be done. I said that if we designing for that from the word go, it would be significantly easier to do than to retrofit it into a dozen guests.
So the question is, whom on the list has had experience with trying to share as much of the file system as is possible, and what did you choose to share? Was it worth the hassle of backfitting it or did you go forward with that design in mind. If you retrofitted it, what did you learn, and what should we avoid should we choose to do this?
Sharing /usr is easy and gets you 80% of the benefit. Using basevol/guestvol overlays gets you the rest of the way but is significantly more complicated. The hard part is applying service in a consistent manner across guests.
Adam
---------------------------------------------------------------------- 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
