Re: Releasability of the kFreeBSD ports

2010-08-15 Thread Petr Salinger
So this (firewall/router requirement) is what brought me to kFreeBSD in the first place and I have to say that this is not without problems. First, I cannot run "netstat -rn" in kFreeBSD. I have yet to file a bug on this, but it just shows how elementary communication channels between userland an

Filter shekan Usa Nl

2010-08-15 Thread dani
Forosh Vpn ba gheymat monaseb va server haye Usa va Nl Jahate daryafte account test be addresss zir email konid email : Alborz33 @ gmail.com 1 Mahe (Usa , Nl) 3500 Toman . 3 Mahe (Usa , Nl) 9500 Toman . 6 Mahe (Usa , Nl) 17000 Toman . 12 Mahe (Usa , Nl) 29000 Toman . jahate daryafte shomare kart

Re: Releasability of the kFreeBSD ports

2010-08-15 Thread The Anarcat
On Wed, Aug 04, 2010 at 12:11:26PM -0400, Tuco wrote: > I intend to deploy Debian GNU/kFreeBSD as a backup / NAS server. I > think as a desktop it's still inmature but as a server it's very > usable and has wonderful capabilities in storage > area thanks to ZFS (for example http://www.ypass.net/sol

***UNCHECKED*** Re: puppet problem on the kFreeBSD ports

2010-08-15 Thread Stephen Gran
This one time, at band camp, Petr Salinger said: > In the provided kdump, the child calls rfork, > in linux it is named clone. The rest of child dump > looks like thread manager, it is needed to also know > trace of 7. > > >5 ruby1.8 CALL sigprocmask(SIG_SETMASK,0xbfbe3af0,0xbfbe3af0) >

Bug#593139: ruby1.9.1: FTBFS on kfreebsd: test suite segfaults

2010-08-15 Thread Lucas Nussbaum
Source: ruby1.9.1 Version: 1.9.2~svn28788-1 Severity: serious Ruby's test suite fails on kfreebsd-i386 and kfreebsd-amd64, and then hangs. i386: > Loaded suite ./test/runner > Started > /build/buildd-ruby1.9.1_1.9.2~svn28788-1-kfreebsd-i386-8LdWDu/ruby1.9.1-1.9.2~svn28788/lib/timeout.rb:50: > [B

Re: puppet problem on the kFreeBSD ports

2010-08-15 Thread Petr Salinger
(the short version - the parent forks and waitpids, and never gets a SIGCHLD or a return from waitpid. This appears to be because the child never exec's after the fork). Please could test patches from my previous mails: Date: Fri, 6 Aug 2010 13:31:14 +0200 (CEST) Date: Fri, 6 Aug 2010 18:45:06