Difference between revisions of "Cluster: Sage Chroot"
Jump to navigation
Jump to search
Line 5: | Line 5: | ||
* http://groups.google.com/group/sage-support/msg/849e906146b41d28?pli=1 | * http://groups.google.com/group/sage-support/msg/849e906146b41d28?pli=1 | ||
* http://www.mail-archive.com/sage-devel@googlegroups.com/msg03545.html | * http://www.mail-archive.com/sage-devel@googlegroups.com/msg03545.html | ||
+ | |||
+ | == Chroot == | ||
+ | The image itself is at /mounts/bobsced/sage_chroot.image (aka /cluster/bobscednew/sage_chroot.image). It gets mounted in the same directory as sage_chroot. It has an ext3 filesystem. |
Revision as of 10:14, 10 September 2009
In order to chroot the Sage notebook, I used a mix of steps from the following guides:
- http://www.msri.org/about/computing/docs/sage/inst/node4.html
- http://www.mail-archive.com/sage-support@googlegroups.com/msg01201.html
- http://groups.google.com/group/sage-support/msg/849e906146b41d28?pli=1
- http://www.mail-archive.com/sage-devel@googlegroups.com/msg03545.html
Chroot
The image itself is at /mounts/bobsced/sage_chroot.image (aka /cluster/bobscednew/sage_chroot.image). It gets mounted in the same directory as sage_chroot. It has an ext3 filesystem.