[head tinderbox] failure on i386/pc98

2010-09-05 Thread FreeBSD Tinderbox
TB --- 2010-09-05 07:50:00 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-09-05 07:50:00 - starting HEAD tinderbox run for i386/pc98
TB --- 2010-09-05 07:50:00 - cleaning the object tree
TB --- 2010-09-05 07:50:47 - cvsupping the source tree
TB --- 2010-09-05 07:50:47 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca 
/tinderbox/HEAD/i386/pc98/supfile
TB --- 2010-09-05 08:27:30 - WARNING: /usr/bin/csup returned exit code  1 
TB --- 2010-09-05 08:27:30 - ERROR: unable to cvsup the source tree
TB --- 2010-09-05 08:27:30 - 0.94 user 28.07 system 2249.74 real


http://tinderbox.freebsd.org/tinderbox-head-HEAD-i386-pc98.full
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


[head tinderbox] failure on arm/arm

2010-09-05 Thread FreeBSD Tinderbox
TB --- 2010-09-05 07:50:00 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-09-05 07:50:00 - starting HEAD tinderbox run for arm/arm
TB --- 2010-09-05 07:50:00 - cleaning the object tree
TB --- 2010-09-05 07:50:26 - cvsupping the source tree
TB --- 2010-09-05 07:50:26 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca 
/tinderbox/HEAD/arm/arm/supfile
TB --- 2010-09-05 08:27:57 - WARNING: /usr/bin/csup returned exit code  1 
TB --- 2010-09-05 08:27:57 - ERROR: unable to cvsup the source tree
TB --- 2010-09-05 08:27:57 - 0.55 user 18.15 system 2277.28 real


http://tinderbox.freebsd.org/tinderbox-head-HEAD-arm-arm.full
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


[head tinderbox] failure on amd64/amd64

2010-09-05 Thread FreeBSD Tinderbox
TB --- 2010-09-05 07:50:00 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-09-05 07:50:00 - starting HEAD tinderbox run for amd64/amd64
TB --- 2010-09-05 07:50:00 - cleaning the object tree
TB --- 2010-09-05 07:50:51 - cvsupping the source tree
TB --- 2010-09-05 07:50:51 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca 
/tinderbox/HEAD/amd64/amd64/supfile
TB --- 2010-09-05 08:28:21 - WARNING: /usr/bin/csup returned exit code  1 
TB --- 2010-09-05 08:28:21 - ERROR: unable to cvsup the source tree
TB --- 2010-09-05 08:28:21 - 1.12 user 31.12 system 2301.14 real


http://tinderbox.freebsd.org/tinderbox-head-HEAD-amd64-amd64.full
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


[head tinderbox] failure on i386/i386

2010-09-05 Thread FreeBSD Tinderbox
TB --- 2010-09-05 07:50:00 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-09-05 07:50:00 - starting HEAD tinderbox run for i386/i386
TB --- 2010-09-05 07:50:00 - cleaning the object tree
TB --- 2010-09-05 07:50:40 - cvsupping the source tree
TB --- 2010-09-05 07:50:40 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca 
/tinderbox/HEAD/i386/i386/supfile
TB --- 2010-09-05 08:30:29 - WARNING: /usr/bin/csup returned exit code  1 
TB --- 2010-09-05 08:30:29 - ERROR: unable to cvsup the source tree
TB --- 2010-09-05 08:30:29 - 0.78 user 23.25 system 2429.09 real


http://tinderbox.freebsd.org/tinderbox-head-HEAD-i386-i386.full
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


[head tinderbox] failure on ia64/ia64

2010-09-05 Thread FreeBSD Tinderbox
TB --- 2010-09-05 08:27:30 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-09-05 08:27:30 - starting HEAD tinderbox run for ia64/ia64
TB --- 2010-09-05 08:27:30 - cleaning the object tree
TB --- 2010-09-05 08:27:42 - cvsupping the source tree
TB --- 2010-09-05 08:27:42 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca 
/tinderbox/HEAD/ia64/ia64/supfile
TB --- 2010-09-05 09:02:15 - WARNING: /usr/bin/csup returned exit code  1 
TB --- 2010-09-05 09:02:15 - ERROR: unable to cvsup the source tree
TB --- 2010-09-05 09:02:15 - 0.48 user 8.05 system 2084.73 real


http://tinderbox.freebsd.org/tinderbox-head-HEAD-ia64-ia64.full
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


[head tinderbox] failure on mips/mips

2010-09-05 Thread FreeBSD Tinderbox
TB --- 2010-09-05 08:27:57 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-09-05 08:27:57 - starting HEAD tinderbox run for mips/mips
TB --- 2010-09-05 08:27:57 - cleaning the object tree
TB --- 2010-09-05 08:28:07 - cvsupping the source tree
TB --- 2010-09-05 08:28:07 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca 
/tinderbox/HEAD/mips/mips/supfile
TB --- 2010-09-05 09:06:35 - WARNING: /usr/bin/csup returned exit code  1 
TB --- 2010-09-05 09:06:35 - ERROR: unable to cvsup the source tree
TB --- 2010-09-05 09:06:35 - 0.38 user 4.78 system 2317.50 real


http://tinderbox.freebsd.org/tinderbox-head-HEAD-mips-mips.full
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


[head tinderbox] failure on powerpc/powerpc

2010-09-05 Thread FreeBSD Tinderbox
TB --- 2010-09-05 08:28:21 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-09-05 08:28:21 - starting HEAD tinderbox run for powerpc/powerpc
TB --- 2010-09-05 08:28:21 - cleaning the object tree
TB --- 2010-09-05 08:28:38 - cvsupping the source tree
TB --- 2010-09-05 08:28:38 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca 
/tinderbox/HEAD/powerpc/powerpc/supfile
TB --- 2010-09-05 09:07:46 - WARNING: /usr/bin/csup returned exit code  1 
TB --- 2010-09-05 09:07:46 - ERROR: unable to cvsup the source tree
TB --- 2010-09-05 09:07:46 - 0.54 user 7.96 system 2364.96 real


http://tinderbox.freebsd.org/tinderbox-head-HEAD-powerpc-powerpc.full
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


[head tinderbox] failure on powerpc64/powerpc

2010-09-05 Thread FreeBSD Tinderbox
TB --- 2010-09-05 08:30:29 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-09-05 08:30:29 - starting HEAD tinderbox run for powerpc64/powerpc
TB --- 2010-09-05 08:30:29 - cleaning the object tree
TB --- 2010-09-05 08:30:44 - cvsupping the source tree
TB --- 2010-09-05 08:30:44 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca 
/tinderbox/HEAD/powerpc64/powerpc/supfile
TB --- 2010-09-05 09:08:32 - WARNING: /usr/bin/csup returned exit code  1 
TB --- 2010-09-05 09:08:32 - ERROR: unable to cvsup the source tree
TB --- 2010-09-05 09:08:32 - 0.62 user 10.23 system 2282.43 real


http://tinderbox.freebsd.org/tinderbox-head-HEAD-powerpc64-powerpc.full
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


[head tinderbox] failure on sparc64/sparc64

2010-09-05 Thread FreeBSD Tinderbox
TB --- 2010-09-05 09:02:15 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-09-05 09:02:15 - starting HEAD tinderbox run for sparc64/sparc64
TB --- 2010-09-05 09:02:15 - cleaning the object tree
TB --- 2010-09-05 09:02:26 - cvsupping the source tree
TB --- 2010-09-05 09:02:26 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca 
/tinderbox/HEAD/sparc64/sparc64/supfile
TB --- 2010-09-05 09:37:05 - WARNING: /usr/bin/csup returned exit code  1 
TB --- 2010-09-05 09:37:05 - ERROR: unable to cvsup the source tree
TB --- 2010-09-05 09:37:05 - 0.53 user 7.72 system 2090.15 real


http://tinderbox.freebsd.org/tinderbox-head-HEAD-sparc64-sparc64.full
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


[head tinderbox] failure on sparc64/sun4v

2010-09-05 Thread FreeBSD Tinderbox
TB --- 2010-09-05 09:06:35 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-09-05 09:06:35 - starting HEAD tinderbox run for sparc64/sun4v
TB --- 2010-09-05 09:06:35 - cleaning the object tree
TB --- 2010-09-05 09:06:44 - cvsupping the source tree
TB --- 2010-09-05 09:06:44 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca 
/tinderbox/HEAD/sparc64/sun4v/supfile
TB --- 2010-09-05 09:42:58 - WARNING: /usr/bin/csup returned exit code  1 
TB --- 2010-09-05 09:42:58 - ERROR: unable to cvsup the source tree
TB --- 2010-09-05 09:42:58 - 0.39 user 6.42 system 2183.11 real


http://tinderbox.freebsd.org/tinderbox-head-HEAD-sparc64-sun4v.full
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: Using ipfw table names instead of numbers.

2010-09-05 Thread Luigi Rizzo
On Sat, Sep 04, 2010 at 10:58:44AM -0300, Anderson Eduardo wrote:
 Hello developers,
 
 I use the ipfw firewall with many tables and, I would like of able to 
 use it with name/alias instead of just numbers.
 
 E.g:
 
 lab# ipfw table 1 name lanetwork
 Setting table 1 to lanetwork
 lab# ipfw table lanetwork add 192.168.0.0/24
 lab# ipfw table lanetwork list
 192.168.0.0/24 0
 lab#
 
 I think a good idea a patch to do that.

if you have a patch feel free to post it.
the main issue is that internally, for efficiency reason,
the name must be translated to a number anyways, so before implementing
it one must decide where the name-number translation table is stored
and how it is managed
The same applies to any name vs. number issue in ipfw/dummynet
Service, protocol and host names solve these issues because there
is a well defined place for the translation table.  But, for instance,
hostname mappings are static (translated at rule insertion time)
whereas one might want a more dynamic behaviour (e.g. refresh
whenever the DNS response expires).

cheers
luigi
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: ZFS v28 is ready for wider testing.

2010-09-05 Thread Anonymous
Pawel Jakub Dawidek p...@freebsd.org writes:

 Hello.

 I'd like to give you ZFS v28 for testing. If you are neither brave nor
 mad, you can stop here.
[...]
 So test whatever you can and report back. Look for regressions,

 strange behaviour,

I wonder why new files tend to have different ACLs than old ones.

  $ ls -lh foo
  -rw-r--r--  1 holo  holo17K Aug 19 11:43 foo
  $ cp foo bar
  $ ls -lh bar
  -rw-r--r--+ 1 holo  holo17K Sep  5 21:20 bar
  $ getfacl foo bar
  # file: foo
  # owner: holo
  # group: holo
  owner@:--x---:--:deny
  owner@:rw-p---A-W-Co-:--:allow
  group@:-wxp--:--:deny
  group@:r-:--:allow
   everyone@:-wxp---A-W-Co-:--:deny
   everyone@:r-a-R-c--s:--:allow

  # file: bar
  # owner: holo
  # group: holo
  owner@:rw-p--aARWcCos:--:allow
  group@:r-a-R-c--s:--:allow
   everyone@:r-a-R-c--s:--:allow
  $ zfs get aclinherit h$PWD
  NAME PROPERTYVALUE  SOURCE
  h/home/holo  aclinherit  restricted default

Note, I didn't upgrade the pool to v28.

 missing features, deadlocks, livelocks, preformance degradation, etc.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: ports/150265: [patch] print/ghostscript8 disable bogus port conflicts in make release

2010-09-05 Thread Rob Farmer
On Sun, Sep 5, 2010 at 10:15,  v...@freebsd.org wrote:

 Rob,

 IMO the question is not if the problem _can_ be solved in the base build
 system. I doubt you'll find many src committers willing to break other
 peoples machines by using DISABLE_CONFLICTS as a general problem solver.

 It may well work for your machine and you're free to do that.

 The maintainer of ghostscript8 may check the issue but is free to close the
 PR as WONTFIX (I suspect that will most likely happen).

 Instead of filing a PR for such problems, a discussion on our fine mailing
 lists might be good.

 Thanks!


[adding a mailing list per your suggestion]

I think you are misunderstanding the issue here.

This is not a ghostscript issue and the maintainer of ghostscript
isn't the right person to look at it. The same issue can appear with
other ports used by make release, such as perl. In fact, there isn't
any way for this to be solved in the ports tree short of removing the
CONFLICTS handling (which is not what I am suggesting).

What happens is the release building process uses certain ports to
generate the HTML documentation (release notes, etc.) on the CDs. To
insure a clean build environment, these ports are built and installed
in a chroot away from the main system. However, prior to entering the
chroot, the distfiles for these ports are fetched and checksummed with
make checksum-recursive. This process occurs outside the chroot, so
the ports system looks for conflicts with what is installed in
/usr/local, assuming that these distfiles are for ports to be
installed in /usr/local.

This assumption is flawed, since they will not be installed there and
thus will not conflict. My patch runs the make checksum-recursive
target with -DDISABLE_CONFLICTS to avoid these false positives.

This will not break other people's machines as you state because the
absolute worst case scenario with my patch is having a couple
duplicate distfiles (such as perl5.10 and perl5.12). Nothing is built
or installed with the DISABLE_CONFLICTS flag.

What I'm asking you to do is revert the description, category, and
assignment of the PR so that someone who is familiar with the release
building process will see it.

-- 
Rob Farmer
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: Using ipfw table names instead of numbers.

2010-09-05 Thread jhell
On 09/05/2010 11:53, Luigi Rizzo wrote:
 whereas one might want a more dynamic behaviour (e.g. refresh
 whenever the DNS response expires).

Lord that would be nice! if only PF had this ;)

-- 

 jhell,v
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org