On Fri, Mar 03, 2006 at 09:58:20AM +0000, Darren J Moffat wrote: > Edward Pilatowicz wrote: > >because it's much cleaner than doing pathmapping. ;) > > > >this is for brandz and the application is a solaris daemon running in > >a linux branded zone. > > So this is a specific application rather than a general problem. > > Which Solaris daemon is this ? The reason I ask is that I had
lockd and statd. > some very long discussions with the then Janus team around how > to deal with some of the cases where they wanted a Solaris daemon > in an otherwise pure Linux zone. > i'm confused. the janus team didn't use zones for running linux processes. the brandz project is the follow on to janus and it introduces the concept of a linux branded zone. > Building chroot's are evil they destroy all the benefits of patching > and effectively bring back so many of the bad things about static > linking. Now if you chroot to the "real" patchable bits thats okay > but chroot'ing to something you have build isn't nice. > i'm not sure i understand your concern here. in a linux branded zone we have parts of the global zone filesystem read only loopback mounted to /native. (this is necessary for just running normal linux applications since we need access to solaris libraries, soalris /proc, etc.) when i want to run lockd and statd, i use and LD_PRELOADed library to cause these applications to chroot to /native so i don't have to worry about remapping paths that the daemons try to access. ed
