Hi Jim, please consider reading the howto on our developerworks page on this topic: http://awlinux1.alphaworks.ibm.com/developerworks/linux390/docu/lx26dcss00.pdf
Also, this howto is going to appear in a reworked version soon.... with kind regards Carsten Otte IBM Linux Technology Center / Boeblingen lab -- omnis enim res, quae dando non deficit, dum habetur et non datur, nondum habetur, quomodo habenda est James Melin <[EMAIL PROTECTED]> Sent by: Linux on 390 Port <[email protected]> 04.03.2005 13:31 Please respond to Linux on 390 Port To: [email protected] cc: Subject: Shared file systems and conversion pain..... 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? ---------------------------------------------------------------------- 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
