Re: FreeBSD 1.x Binaries Work Except under Chroot

2012-08-10 Thread Warner Losh
On Aug 10, 2012, at 6:10 PM, George Mitchell wrote: > On 08/10/12 18:49, Julian H. Stacey wrote: >>> Try to ktrace the binaries to see what is going on. I suspect that >>> sources for 1.1.5 are not in our cvs/svn, so it is troublesome to >>> say anuthing without ktrace dump. >> >> Not that I nee

Re: FreeBSD 1.x Binaries Work Except under Chroot

2012-08-10 Thread George Mitchell
On 08/10/12 18:49, Julian H. Stacey wrote: Try to ktrace the binaries to see what is going on. I suspect that sources for 1.1.5 are not in our cvs/svn, so it is troublesome to say anuthing without ktrace dump. Not that I need it, but I looked to see how old we go. (Sometimes its nice to have ol

Re: FreeBSD 1.x Binaries Work Except under Chroot

2012-08-10 Thread Dan Plassche
On Fri, Aug 10, 2012 at 1:07 PM, Konstantin Belousov wrote: > Try to ktrace the binaries to see what is going on. I suspect that > sources for 1.1.5 are not in our cvs/svn, so it is troublesome to > say anuthing without ktrace dump. Ok, below is the kdump from running basename as a simple exampl

Re: FreeBSD 1.x Binaries Work Except under Chroot

2012-08-10 Thread Julian H. Stacey
> Try to ktrace the binaries to see what is going on. I suspect that > sources for 1.1.5 are not in our cvs/svn, so it is troublesome to > say anuthing without ktrace dump. Not that I need it, but I looked to see how old we go. (Sometimes its nice to have old stuff, eg to defeat patent claims) I

Re: FreeBSD 1.x Binaries Work Except under Chroot

2012-08-10 Thread Konstantin Belousov
On Fri, Aug 10, 2012 at 12:06:46PM -0400, Dan Plassche wrote: > Hello, > > I'm successfully running FreeBSD 1.1.5.1 binaries from a > directory on an 8.2 system. The goal is to ultimately setup a > chroot build environment targeting 1.x for an old 386. However, > whenever I chroot to the /freebs

FreeBSD 1.x Binaries Work Except under Chroot

2012-08-10 Thread Dan Plassche
Hello, I'm successfully running FreeBSD 1.1.5.1 binaries from a directory on an 8.2 system. The goal is to ultimately setup a chroot build environment targeting 1.x for an old 386. However, whenever I chroot to the /freebsd-1.1.5.1 directory tree, the old binaries suddenly start failing with lin

Re: strange things happening with ping - am I hacked?

2012-08-10 Thread Bob Bishop
Hi, On 10 Aug 2012, at 15:47, Christoph P.U. Kukulies wrote: > I have some machines in a companys' network that are interconnected > with a piece of coaxial cable (ethernet 10base2). This trunk goes through a > switch that acts also as a media converter and connects to the Internet > router. >

strange things happening with ping - am I hacked?

2012-08-10 Thread Christoph P.U. Kukulies
I have some machines in a companys' network that are interconnected with a piece of coaxial cable (ethernet 10base2). This trunk goes through a switch that acts also as a media converter and connects to the Internet router. For a while now I'm having trouble with this 10base2 trunk and I droppe

Re: FreeBSD 9.0-R em0 issues? - update...

2012-08-10 Thread Karl Pielorz
The last time it hung, 'netstat -n -i' showed: " NameMtu Network Address Ipkts Ierrs IdropOpkts Oerrs Coll em01500 00:25:90:31:82:46 355482 10612864185945 0 291109 3032246910270 1516123455135 " That's from about 30 seconds after the interface 'stoppe

Re: system() using vfork() or posix_spawn() and libthr

2012-08-10 Thread Konstantin Belousov
On Thu, Aug 09, 2012 at 02:08:50PM +0300, Konstantin Belousov wrote: > Third alternative, which seems to be even better, is to restore > single-threading of the parent for vfork(). I mean this patch. diff --git a/sys/kern/kern_fork.c b/sys/kern/kern_fork.c index 6cb95cd..e59ee21 100644 --- a/sys

FreeBSD 9.0-R em0 issues?

2012-08-10 Thread Karl Pielorz
Hi, I've got a SuperMicro X8DTL-IF based server (with Intel L5630), 6Gb of RAM and two onboard Intel NIC's. afaik this is running the stock FreeBSD 9.0-R GENERIC kernel. em0: port 0xdc00-0xdc1f mem 0xfbce-0xfbcf,0xfbcdc000-0xfbcd irq 16 at device 0.0 on pci6 em0: Using MSIX in