Pat Maddox [EMAIL PROTECTED] writes:
Yep, that's pretty much right. Use one of the systems to build
everything as packages, and then install all those packages onto your
other machines.
Or share them (e.g., by NFS), and build them on the individual machines.
Or share them (e.g., by NFS),
hi lowell,
The recommended path is to do a binary upgrade. 5.4 will be out in a
few weeks, and release candidate builds are available now.
to what extent does building the sources on my machine affect the resulting
binaries? to be more specific:
i read the freebsd handbook section on
Yep, that's pretty much right. Use one of the systems to build
everything as packages, and then install all those packages onto your
other machines.
You'll still need to compile the kernel and source on each individual machine.
On Apr 6, 2005 4:18 PM, Iain Dooley [EMAIL PROTECTED] wrote:
hi
Iain Dooley [EMAIL PROTECTED] writes:
do i need to edit the Makefiles? how can i cvsup only those programs
in contrib that i need? my aim here is to have a compact source tree
that i can use cvsup to keep current, but only takes up a couple of
hundred meg.
Doing this is not supported. One
hi there, i'm currently running FreeBSD 4.10-RELEASE on a Thinkpad 586, with
a 1GB HDD and something like 48 MB of ram, with a pentium 133 processor.
there is no CD drive, so i installed from floppies via FTP and selected
'minimal' installation, and didn't install any of the ports or src.
i
