On Tue, 6 Nov 2007, Douglas A. Tutty wrote:
> While you're at it: the install docs cover the absolute minimum to run
> a basic system (I think they describe it as a basic home system
> connected to the internet). Could you include an example of the same
> thing but the minimum to be able to compile patches?
Include the compXX file set during installation.
Install src.tar.gz after installation.
That's it. (Add xenocara and ports if you like.)
Then you have a basic system connected to the internet and set up
for development and maintenance by AnonCVS of the source tree,
or for applying autonomous patches.
I will not relate the misery getting to this point on a certain
unnamed Linux "distro", whose release tag rhymes with "large".
> OpenBSD runs on old hardware. Old hardware doesn't have 20 GB disks.
> At best, I may have a PII with an 8 GB drive with perhaps a second 1 GB
> drive.
Indeed.
Here is a df from a bare, fresh 4.2 system, all install sets including X,
ports.tgz, and a (very) few smaller packages: (this is an i386 system,
other architectures will have different sizes, but should be close).
[EMAIL PROTECTED] root 0:1]# df
Filesystem 1K-blocks Used Avail Capacity Mounted on
/dev/sd0a 510168 57312 427348 12% /
mfs:31119 506407 3 481084 0% /tmp
/dev/sd0d 6190742 2123778 3757428 36% /usr
of the 2123778K in /usr, 1127960K is under /usr/src (including
xenocara source).
Total about 2.25GB, not counting swap. Another 2 GB might be needed
to compile a complete system in one go. ("make release"). Clever
use of NFS could be made. (Mount /usr/src from NFS, have /usr/obj
local, for example). You only need one /usr/src tree per LAN, and
it need not be on an OpenBSD host, just one capable of serving NFS.
An 8 GB disk would be quite ample, as has been my experience in the past,
and as you can conclude from the df output.
If you wish to compile only patches (say openssl is patched, and
you wish to recompile only openssl's subtree of /usr/src), then a
4GB disk would suffice, including a half G or whatever for swap.
OpenBSD doesn't really eat disk until you start building lots of
packages from source, i.e. through the /usr/ports infrastructure.
Dave
