On Friday, March 18, 2016 at 6:39:33 PM UTC+1, William wrote: > > 3. More generally, for SMC, it's useful, for the sake of Sage > development, to have a way to setup a sage dev environment as quickly > as possible for user experience reasons, and as efficiently as > possible to better make use of resources.
There is precisely one way to do that right. Build Sage with a fixed path (say, /sage-7.1) and then mount that as the lower filesystem of an overlayfs inside the cgroup (with the same path obviously). And yes, thats basically what docker is (plus some networking stuff). None of the user-space hacks like copying the Sage directory tree come close. Also, why just mount one version. You could easily have lots of different versions mounted in. Adds to disk usage only if users make changes, and then only the changed files. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
