Hello all,
I am setting up our university lab machines to image via system imager. The
image is around 7 GB, and on every attempt to install the image, I end up
running out of RAM (2 GB) on each client machine.
I am running system imager 4.1.6, from the apt repository on Ubuntu 10.04
amd64. I am using the default rsync mechanism, and using netboot to initiate
installs.
I have set option-144 to "n" in my dhcp server (which is separate to my
image server), and have passed TMPFS_STAGING=no as a kernel boot parameter,
either of which I believe should disable tmpfs staging. I also believe that
tmpfs staging is meant to be disabled by default, though the docs are
somewhat fuzzy on that particular issue.
Is there anything I am likely to have done wrong which is causing tmpfs to
be on in all cases? And anything I can do to remedy this?
I am happy to post configuration/logs/etc. if it will be of any help.
Thanks,
--
Tristam MacDonald
http://swiftcoder.wordpress.com/
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users
