This is an awesome idea. Two ways to do it: bind mount RO over existing /bin and friends, or let /bin and friends be sym-links into "the system", wherever it gets mounted.
Need to be aware of hiding files under the RO mounts. If customers are PAYING for RW space, and you have content there for bootstrapping, but that stuff gets overlaid ... it's a drag. It is possible to boot an 'init' which fixes things and then does a 'pivot_root' to get the RW root they want. -- R; <>< On Tue, Aug 10, 2010 at 20:50, Thomas Kern <[email protected]> wrote: > I like the writable / with RO /bin, /sbin, /lib, /lib64, /usr. This way if > you do get > around to charging (yeah old school) for disk space, the customer pays for > the writable > areas, not the shared RO areas. If the customer needs more space, break out > other > directories to their own disks (/home, /srv, /var/log, etc). And /usr/local > is a symlink > to /local so it is their space to write on. > > Now if I can get this done in VMWare or OVM. > > /Tom Kern > > Leland Lucius wrote: >> Edmund R. MacKenty wrote: >>> BTW: We ended up doing shared-root a bit differently, because we >>> wanted to >>> have shared filesystems but also wanted / itself to be writable so we >>> could >>> create mount-points for new filesystems as needed. So we made the >>> filesystem >>> containing / writable, and put all of /bin, /boot, /lib, /lib64, /sbin >>> on a >>> read-only filesystem and bind-mounted those directories onto the writable >>> filesystem. This gives us more flexibility to make changes as user needs >>> evolve over time. But it's the same basic idea. >> >> Yepper, I gave that a try as well. I'd set up a small 8MB / and did all >> of the bind mounts as appropriate. I may still go this route, but it >> does add a tad bit more complexity to the setup. No biggie, just trying >> to keep it as simple as possible for my initial go round. >> >> Leland > > ---------------------------------------------------------------------- > 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 more information on Linux on System z, visit > http://wiki.linuxvm.org/ > ---------------------------------------------------------------------- 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 more information on Linux on System z, visit http://wiki.linuxvm.org/
