On 5/11/2025 1:20 PM, Michael wrote:
2. Or if you want to compile it locally, you can consider 'mount --bind' to a new directory on any other local fs, which has a large enough partition for this job. Or you if you run out of fs space altogether, or RAM isn't enough and therefore you can't use tmpfs for /var/tmp/portage and/or it swaps continuously, you can configure and load zram, and/or set a lower number of jobs in /etc/portage/package.env for rust to allow it to fit within available fs and RAM. Sure, it will take for ever to emerge on say a PC with 4G of RAM, but if you *must* emerge it locally you should be able to get there.
Can just compile some place else. See: PORTAGE_TMPDIR="/ramfs" PORTAGE_TMPFS="/ramfs" Can place it in make.conf or per package in package.env. Don't need to compile in /var.
3. You can even use NFS and mount a fs over the network for this purpose, but this is rather more complicated than the above options and I expect it will be slow.
Just to be clear... this is prolly a bad idea. IF you HAVE TO go this over NFS, it would be better to just mount -o loop a nfs shared image instead of a directory. That way, your local kernel manages the file system (permissions and all that), instead of trying to relay all that info to a remote kernel over nfs.
