Hi Drew, These questions are targeted at the wider audience, not just specifically you :-)
Just a couple of questions regarding BEs. Sorry I have not responded sooner. It is not clear to me at this point what the intended use for the BE element is. If I want to determine the root filesystem, ie 'the '/' mounted filesysetm of the boot environment how do I go about determining this? Should I use the libbe ctype to extract further info? Are there scenarios where this could be different than what the transfer module will install to as the root of the new system/environment? Also any idea on how I might figure out where the root filesystem of the about to be installed system is and where it is temporarily mounted at? I presume the transfer module is going to need this info also. WRT to placing the BE element directly under the Zpool element, I wonder would it be more concise association to place it under a Filesystem element instead? Thanks, Niall > - BE elements are absent > <br> > <br> > I realized that we have a DOC class for BEs but > no schema > definition for them. Do we need one? > If so, what attributes > would be needed? If a schema definition IS > needed, I propose it > be a sub-element of <zpool> (so BEs can be > associated with > the zpool they are a part of) with an "action" > and "name" > attribute. "action" would use the typical > "create"|"destroy" > model as zpools currently do:<br> > <br> > <!ELEMENT be EMPTY><br> > <!ATTLIST be name CDATA #REQUIRED><br> > <!ATTLIST be action (create|destroy) > "create"><br> > <br> -- This message posted from opensolaris.org _______________________________________________ caiman-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
