| 1 |
On Mon, 2011-01-17 at 12:38 +0000, Neil Bothwick wrote: |
| 2 |
> On Mon, 17 Jan 2011 19:40:15 +0800, William Kenworthy wrote: |
| 3 |
> |
| 4 |
> > > If it's diskless, where are /tmp and /var/tmp mounted? If they use |
| 5 |
> > > tmpfs the "memory" usage is understandable. If they use NFS the |
| 6 |
> > > emerges must be unbearably slow. |
| 7 |
> |
| 8 |
> > For normal usage, they are in tmpfs along with portage but I mount them |
| 9 |
> > over nfs for larger packages as memory is too constrained (just comment |
| 10 |
> > out the lines in fstab) - most packages take much less than a hundred mb |
| 11 |
> > or so for the storage unless its glibc or the like. After a reboot they |
| 12 |
> > are using no space (of course) and it just takes a sync to replace |
| 13 |
> > portage and I use http-replicator on the network so distfiles are not a |
| 14 |
> > problem. |
| 15 |
> |
| 16 |
> So root is on another (more powerful?) machine and mounted over NFS? Why |
| 17 |
> not chroot into the root on the host machine and run the emerge there? |
| 18 |
> |
| 19 |
> |
| 20 |
The root is on a core2 duo, while the mythbackend and myth NFS mounts |
| 21 |
are on an old athlon. I did try and build the system there in a chroot |
| 22 |
but its a 32 bit install and I went with 64bit for the atom. Result was |
| 23 |
it didnt work - cant remember the details (was nearly a year ago :) but |
| 24 |
some packages were ok, others not - I was expecting it to work and had |
| 25 |
planned on managing upgrades via chroot. 64 bit was an experiment to |
| 26 |
see if it was worth migrating the rest of the systems over and this has |
| 27 |
been the only 32/64 hiccup so far but a mythtv frontend is not overly |
| 28 |
complex. |
| 29 |
|
| 30 |
The initial install was then done using gentoo on an 8G usb stick |
| 31 |
plugged into the machine and everything nfs mounted or on the usb stick. |
| 32 |
Worked a treat! For the new 4G machine I just copied it to a new |
| 33 |
directory and set it to PXE boot the new copy. |
| 34 |
|
| 35 |
The 3G machine is a Zotac ION N330 atom, while the 4G one is a Jetway |
| 36 |
ION-TOP N330 "bare bones" system - very similar hardware except for the |
| 37 |
3G/4G memory difference. Only grief is getting the odd-ball CIR working |
| 38 |
on the ION-TOP. |
| 39 |
|
| 40 |
BillK |
Archives