Re: Bulk buils space requirements

[Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxx>]

:ok, is there a problem if a build is stopped in between? Can it resume
:from that point later.
:I won't be able to keep this system up for a week continously :-(

    Once you've done the initial setup you can set it up to pickup where
    it left off, yah.

:...
:> unintentionally by performing multiple builds.
:>
:
:Is it possible to mount the /bulk pfs i made for it with "nohistory" ?
:Other wise I guess I will have to run "hammer cleanup /bulk" occassionally ?
:
:thanks :-)
:
:--Siju

    Just setting the retention to a few days in 'hammer viconfig /bulk'
    and giving it a good 25 minutes to prune should do it:

	snapshots 1d 2d
	prune 1d 30m

    Even better, run a tmpfs for your /bulk/pbulk_chroot/usr/pkg, because
    that is the directory tree that the bulk build continuously tears down
    and rebuilds for each package.  Once you've done the initial setup
    and it has created the chroot, then you can do the mount_tmpfs.

    If you are going to use tmpfs then configure at least 16G of
    swap space.  Up to 32G of swap can be configured with a default
    i386 kernel (and up to 512G for a x86-64 kernel by default).

    It will take some time to get used to the scripts, during which
    you will probably be telling it to do it from scratch quite a bit.
    But once you get used to the script you can get an incremental
    build/rebuild going fairly easily.

					-Matt
					Matthew Dillon 
					<dillon@backplane.com>