Am 18.04.2011 10:12, schrieb Neil Bothwick: > On Mon, 18 Apr 2011 09:52:56 +0200, Florian Philipp wrote: > >>> it's tedious to install things >>> through an intermediary system all the time. The fullsize laptop, when >>> it gets its rebuild over the next week (it's been a windows 2k3 server >>> development system lately) > >> My strategy for getting Gentoo on a netbook with an SSD is to use NFS >> for PORTAGE_TMPDIR. Works nicely and makes less work than building >> everything remote. > > Doesn't using NFS slow compilation right down. I have a script on > the build host that enters the chroot and runs emerge -uD --changed-use > world, right after cron does emerge --sync, so the packages are > automatically available. Ass --usepkg to EMERGE_DEFAULT_OPTS on the > netbook and everything is transparent and no work at all (apart from a > couple of packages that won't build in the chroot). > >
I haven't noticed any slowdown. I use a 100 MBit/s connection. That's nearly 12 MiB/s. The SSD has a write-speed of maybe 4-8 MiB/s. Actual throughput (monitored with iftop) was usually lower that 40 Mbit/s. Maybe latency was a bit higher and NFSv4 could have helped with that but I think it was negligible compared to the compiling performance of the Atom processor. Sure, a build host would have been better but it also meant more work. I also thought about using ATAoE, iSCSI or something alike to mount the SSD from a more powerful computer (using a live-system to avoid obvious problems when mounting the FS twice). Again - too much fuss. I usually just do security updates and then a full update every six months or so. Regards, Florian Philipp
signature.asc
Description: OpenPGP digital signature
