Using tmpfs for /tmp enables the kernel to share RAM between /tmp and
executing processs. The lstp_core-3.0.x uses /dev/ram1, which permanently
reserves the RAM for /tmp, and does not share the ununsed space with
processes. Sharing the default 1MB space for /tmp, most of which is
usually unused, will noticeably help a low-RAM client (any client with
less than 64MB RAM). A client with lots of RAM also can benefit
because the maximum space used for /tmp can be reallocated dynamically,
while the size of /dev/ram* is fixed at creation.
To use tmpfs, you must enable "Virtual memory file system support
(former shm fs)" in the kernel configuration under File systems.
Then in ltspserver:etc/rc.local, replace
/sbin/mke2fs -q -m0 /dev/ram1 ${RAMDISK_SIZE}
mount -n /dev/ram1 /tmp
with
mount -t tmpfs -o size=${RAMDISK_SIZE}k,nr_inodes=200,mode=777 tmpfs /tmp
Mounting tmpfs is faster than mke2fs+mount on /dev/ram1, so clients
boot faster using tmpfs.
Read the linux Documentation/filesystems/tmpfs.txt . tmpfs does not
support "mount -o loop" with a destination mount point in tmpfs.
[This has nothing to do with the "lo" loopback network device.]
When I combine the use of tmpfs with successful umount of initrd and
custom minimal kernel, then my very small client with only 4.6MB RAM
avoids paging in terminal mode (ncurses), so it is actually usable.
-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
