Dear Serge, thank you for pushing this patch. My five cents on it:
* I ever attempt to use "just one name for it"; therefore I would suggest to call the file ".pin_rootfs". * Maybe this should be configurable (label lxc.rootfs.pinfile ?), with the above as a default. * Maybe it should be switchable. If it is configurable as above, maybe choosing a empty value will disable it. As an outlook for further development, the file might be filled with some "usefull information"(tm); what's about the hostname of the host as a reference information for the container? But maybe this should be realized as a procfs extension inside the container. Or act as a FIFO between the host and the container to attach a small userland command daemon inside the container to it -- to my knowledge Ulrich Horlacher uses such. Guido ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ Lxc-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lxc-devel
