Date: Sun, 24 Jan 2016 22:07:40 +0100 From: Terje Elde <terje@elde.net> To: Tim Daneliuk <tundra@tundraware.com> Cc: FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: [installworld] Do We need /usr/obj Message-ID: <9D1058C8-6599-44B7-9C20-1A0F3DA48FE0@elde.net> In-Reply-To: <56A53AA1.1010405@tundraware.com> References: <56A532AC.3050803@tundraware.com> <B352D17C-E1F5-44C6-A530-2CF37BFF09E7@elde.net> <56A53AA1.1010405@tundraware.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 24 Jan 2016, at 21:57, Tim Daneliuk <tundra@tundraware.com> wrote: >> Why build on the machine then? Why not just build on and install from ano= ther? >=20 > Because this machine is many networks away and installation over the wire w= ould take > quite a while, I think. Well, yes, it would take time, but surely not more than compiling everything= on it? There's multiple ways you could do this: - nfs-mount /usr/src and obj - copy them over only if needed - do a binary-upgrade, with sources you compiled They're all quite workable. I've done the first with nfs over IPSec, about 5= 0ms. latency. Not fast, I'll give you that, but practical and fast enough (f= or my use at the time at least).=20 >> Well, that's where your built stuff goes, so it's where you'd install fil= es from if you upgrade. >=20 > So you DO need /usr/obj for the installs then? Yes.=20 >> Also, it wouldn't really help you to delete it. With your current setup, y= ou'd need the space again the next night, wouldn't you? >=20 > The idea would be to have the rebuild scripts clean out /usr/obj when they= are done ... if it were no longer needed. Yes, but whatever space that frees up for you, you couldn't really use freel= y anyway, since you'd need that space again for the next build? Terje
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9D1058C8-6599-44B7-9C20-1A0F3DA48FE0>