Re: Bulk buils space requirements
: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
Re: Bulk buils space requirements
On Fri, Oct 22, 2010 at 1:10 AM, Justin C. Sherrill wrote: > On Thu, October 21, 2010 2:36 am, Siju George wrote: >> HI, >> >> I got around 250 GB free on my desktop. >> >> I would like to try out a bulkbuild of pkgsrc ;-) >> >> will that space be enough? > > I have some scripts that work as a wrapper around the bulk builds I do; > this may be more than you need, but I'd like to see if they make sense to > someone who is not me: > > http://www.shiningsilence.com/simplepbulk/ > Ok thanks :-) > The two caveats for you: > > - Bulk builds take a week on decent hardware; you're building over 10,000 > packages, after all. The limited_list option in the pbulk config can let > you limit it to certain packages, which you may want to do. > 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 :-( > - If you're doing this on Hammer, keep an eye on disk usage. It generates > a huge amount of disk activity if you build everything, and Hammer will > happily keep track of all those changes. I've filled terabyte disks > 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
2.8 release schedule - tentitively Wednesday 27 October.
We are still scheduled to officially release mid-next week. I will be doing the final the MFCs from master on Sunday (as a lot of fixes have gone in since the branch). All of the big-ticket bugs have been squashed. There are still a few medium-ticket bugs (e.g. Rumko's listen/connect issue) which I am looking at now. Justin is making progress on pkgsrc though I do not know what the state of the KDE stuff is. I think Wednesday is a good target to have it all on the servers ready to go. -Matt Matthew Dillon
Re: hammering the drive
Time tends to wear out drives more than the seeking. Dust and grime from outside that gets through the filter and material from inside the drive itself. Basically just time. You do want to make sure the drive is well anchored (screwed into) the machine, and doesn't experience any undo shock while operating. The only major mechanical limitation that can cause a drive to fail other than time is in wear and tear from hard parking and spindowns/spinups. Basically any time the head has to land in the parking area. Drives, of course, can fail for a variety of reasons due to defects in manufacturer, using the wrong lubricant, etc etc. Seeking is not usually a contributor though. -Matt
Re: Bulk buils space requirements
On Thu, October 21, 2010 2:36 am, Siju George wrote: > HI, > > I got around 250 GB free on my desktop. > > I would like to try out a bulkbuild of pkgsrc ;-) > > will that space be enough? I have some scripts that work as a wrapper around the bulk builds I do; this may be more than you need, but I'd like to see if they make sense to someone who is not me: http://www.shiningsilence.com/simplepbulk/ The two caveats for you: - Bulk builds take a week on decent hardware; you're building over 10,000 packages, after all. The limited_list option in the pbulk config can let you limit it to certain packages, which you may want to do. - If you're doing this on Hammer, keep an eye on disk usage. It generates a huge amount of disk activity if you build everything, and Hammer will happily keep track of all those changes. I've filled terabyte disks unintentionally by performing multiple builds.
Re: No package installation method works
Dylan Reinhold writes: On 10/20/2010 11:30 PM, Torbjorn Granlund wrote: > Someone replied privately: > >The problem here is that you are using make instead of bmake (which >needs to be used for pkgsrc things). > > Ah, this indeed work. I'll try to remember this when I, in some months, > need to install some additional pacage. > > Thanks to all who replied! > What if make gave a 'hint' when run in /usr/pkgsrc. Something like # make make called in /usr/pkgsrc/www/zope, did you mean bmake? make: no target to make. I am not a DragonflyBSD hacker, but I think your approach is a little bit ugly, if I may say so. It would be neater to have /usr/Makefile identify make and write a message: .INIT: @if [ `basename $(MAKE)` != bmake ]; then echo "Use bmake stupid"; exit 1; fi all:.INIT blah blah anothertarget: .INIT blah blah (Not too neat either, but this will at least work even with pkgsrc in a a non-standard place.) -- Torbjörn
Re: hammering the drive
On 21/10/10 11:05, Pierre Abbat wrote: > dogla# dschedctl -l > dschedctl: open(/dev/dsched): No such file or directory > > Am I missing something? > Yes. dschedctl doesn't exist anymore. Please take a look at the manpage. The right way to do it now is via sysctl. Regards, Alex
Re: hammering the drive
On Thursday 21 October 2010 02:32:43 Alex Hornung wrote: > On 21/10/10 04:44, Pierre Abbat wrote: > I can't say much about the wear and tear of the drive. Regarding the > unresponsiveness when Hammmer functions are running I'd suggest you give > dsched_fq a try, the fair-queuing disk scheduling policy. It should > improve interactivity during heavy I/O. dogla# dschedctl -l dschedctl: open(/dev/dsched): No such file or directory Am I missing something? Pierre -- Don't buy a French car in Holland. It may be a citroen.
Re: No package installation method works
Hi, * Dylan Reinhold wrote: > > What if make gave a 'hint' when run in /usr/pkgsrc. > > Something like > # make > make called in /usr/pkgsrc/www/zope, did you mean bmake? > make: no target to make. While I like the idea of your patch, it will not work if someone uses another location to store the pkgsrc tree (e.g. I tend to store it under /build/pkgsrc). I think we should better fix the documentation then adding seatbelts to the code. Cheers Matthias
Re: Bulk buils space requirements
* Siju George wrote: > HI, > > I got around 250 GB free on my desktop. > > I would like to try out a bulkbuild of pkgsrc ;-) > > will that space be enough? > is reading > > http://www.netbsd.org/docs/pkgsrc/bulk.html > > enough or should I be knowing some dfly specific things? This is clearly enough. The official document speaks about roughly 35GB, so if you add another 10GB you should be fine. Cheers Matthias
Re: No package installation method works
On 10/20/2010 11:30 PM, Torbjorn Granlund wrote:
Someone replied privately:
The problem here is that you are using make instead of bmake (which
needs to be used for pkgsrc things).
Ah, this indeed work. I'll try to remember this when I, in some months,
need to install some additional pacage.
Thanks to all who replied!
What if make gave a 'hint' when run in /usr/pkgsrc.
Something like
# make
make called in /usr/pkgsrc/www/zope, did you mean bmake?
make: no target to make.
diff --git a/usr.bin/make/main.c b/usr.bin/make/main.c
index 5294f03..2f744a9 100644
--- a/usr.bin/make/main.c
+++ b/usr.bin/make/main.c
@@ -887,6 +887,7 @@ main(int argc, char **argv)
charcurdir[MAXPATHLEN]; /* startup directory */
charobjdir[MAXPATHLEN]; /* where we chdir'ed to */
const char *make_flags;
+ const char *bmake_hint_path = "/usr/pkgsrc";
/**
* This section initializes stuff that require no input.
@@ -953,6 +954,8 @@ main(int argc, char **argv)
Var_SetGlobal(".CURDIR", curdir);
Var_SetGlobal(".OBJDIR", objdir);
+ if(strspn(bmake_hint_path,curdir) == strlen(bmake_hint_path))
+ fprintf(stderr,"make called in %s, did you mean
bmake?\n",curdir);
/*
* Set up the .TARGETS variable to contain the list of targets
to be
* created. If none specified, make the variable empty -- the
parser
Re: OpenOffice is not available from pkgsrc for dragonfly and binary package errors
* Siju George wrote: > > What version of pango have you got installed? > > mine is > > pango-1.28.1 = I have the same version installed. Cheers Matthias
