Re: pkgsrc 2009Q2 DragonFly 2.3.1/i386 2009-07-08 12:25

-Build start: 2009-07-07 04:48 +Build start: 2009-07-08 12:25 - Successfully built: 8081 - Failed to build: 355 - Depending on failed package:95 + Successfully built: 8088 + Failed to build: 350 + Depending on failed package:93 -devel/

pkgsrc 2009Q2 DragonFly 2.3.1/i386 2009-07-08 12:25

pkgsrc bulk build report DragonFly 2.3.1/i386 Compiler: gcc Build start: 2009-07-08 12:25 Build end: 2009-07-08 19:34 Full report: http://leaf.dragonflybsd.org/~hasso/pbulk-logs/20090708.1225/meta/report.html Machine readable version: http://leaf.dragonflybsd.org/~ha

Re: amd64 - invitation to test

The master development branch in the our main repo now has all of Jordan's AMD64 work, plus additional work in the last few days which gets SMP working and which stabilizes native buildworlds and installworlds done from a 64 bit environment, including the boot code. Modules wil

Re: pkgsrc-HEAD DragonFly 2.3.1/i386 2009-07-07 04:48

-Build start: 2009-07-04 02:33 +Build start: 2009-07-07 04:48 -Total number of packages: 8855 - Successfully built: 8064 - Failed to build: 358 - Depending on failed package: 107 +Total number of packages: 8857 + Successfully built: 8081 + Faile

pkgsrc-HEAD DragonFly 2.3.1/i386 2009-07-07 04:48

pkgsrc bulk build report DragonFly 2.3.1/i386 Compiler: gcc Build start: 2009-07-07 04:48 Build end: 2009-07-08 11:53 Full report: http://leaf.dragonflybsd.org/~hasso/pbulk-logs/20090707.0448/meta/report.html Machine readable version: http://leaf.dragonflybsd.org/~ha

Re: hammer mirror shows differrent results from differrent terminals

:Thanks a lot for your reply Matt :-) : :Could you please tell how mirror-stream actually works? :Does it work sequentially or as changes happen? : :By sequentially I mean If there are 100 files in the master then :mirror-stream copies from file 1 to 100 to the slave so if mirror has :passed from

Re: vfsync_bp skipping dirty buffer

: :Hi, : :I have these errors thrown to the console. : :Warning: vfsync_bp skipping dirty buffer 0xc2c87c98 :Warning: vfsync_bp skipping dirty buffer 0xc2e157ec :Warning: vfsync_bp skipping dirty buffer 0xc2cc869c :Warning: vfsync_bp skipping dirty buffer 0xc2c519e0 : :What do they mean? :Are they

vfsync_bp skipping dirty buffer

Hi, I have these errors thrown to the console. Warning: vfsync_bp skipping dirty buffer 0xc2c87c98 Warning: vfsync_bp skipping dirty buffer 0xc2e157ec Warning: vfsync_bp skipping dirty buffer 0xc2cc869c Warning: vfsync_bp skipping dirty buffer 0xc2c519e0 What do they mean? Are they serious? tha

Re: hammer mirror shows differrent results from differrent terminals

On Wed, Jul 8, 2009 at 12:00 AM, Matthew Dillon wrote: > >    That work is still in kernel memory.  It hasn't been flushed to the >    media yet.  Mirroring operations only work on data flushed to the media. >    This will occur automatically every 30-60 seconds or when you sync. >    sync runs asy