On Tue, Sep 27, 2011 at 12:45 PM, Warpme <span dir="ltr"><<a href="mailto:warpme@o2.pl">warpme@o2.pl</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Direct reason for so huge image file that I have is RAM based root<br>
file system containing frontend+all needed environment (Qt, perl, py,<br>
etc) + mplayer.<br>
<br>
I chose this approach intentionally as for me important was:<br>
<br>
1.minimalistic relation between master server and FE (ideally only myth<br>
protocol)<br>
<br>
2.simplest maintenance (ideally if fe upgrade by simple upgrade of one<br>
file)<br>
<br>
3.easy decoupling between boot infrastructure (home DHCP/tftp)&<br>
software repo (http based so I can have it on any location - if speed is<br>
reasonable).<br></blockquote><div><br>I tried PXE (both Minimyth and Fedora on the frontends), but I was never happy with some of the NFS issues you mention. It seemed to add lag to an already slower system (Nvidia ION). I then used an 8GB USB stick for a while and while it removed the NFS issues, the USB stick was not very fast.<br>
<br>I recently found some Crucial m4 SSD's on sale for around $85 and bought two of them for my frontends. I've never seen the ION be so responsive moving through the menus, etc. What I thought was IR lag in the past was proven incorrect. The ION was slow because of the crappy OS media (PXE+NFS or USB). So far I've been happy with the local SSD in each frontend.<br>
<br>/Brian/ <br></div></div>