From owner-freebsd-emulation Mon Sep 4 14:48:40 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from tigerdyr.candid.dk (tigerdyr.candid.dk [193.162.142.120]) by hub.freebsd.org (Postfix) with ESMTP id 92EED37B424 for ; Mon, 4 Sep 2000 14:48:37 -0700 (PDT) Received: by tigerdyr.candid.dk (Postfix, from userid 1001) id D70EF98B9; Mon, 4 Sep 2000 23:48:36 +0200 (CEST) Date: Mon, 4 Sep 2000 23:48:36 +0200 From: =?iso-8859-1?Q?Michael_Lyngb=F8l?= To: freebsd-emulation@FreeBSD.ORG Subject: How to make vmware+networking working? Message-ID: <20000904234836.A85754@tigerdyr.candid.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD/i386 4.1-STABLE Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, The last couple of days I've been trying to setup networking the vmware2-port. No luck so far. Here's what I've done: - cvsup'ed and "make world" of 4.1-STABLE - compiled a kernel including "options BRIDGE" - installed the latest vmware2 port (vmware2/Makefile,v 1.22) I'm using 192.168.0/24 on my local lan. Using user-ppp to connect to internet. Configured "xl0": xl0: flags=8943 mtu 1500 inet 192.168.0.10 netmask 0xffffff00 broadcast 192.168.0.255 ... Configured "vmnet1": vmnet1: flags=8843 mtu 1500 inet 192.168.0.20 netmask 0xffffff00 broadcast 192.168.0.255 ... Started ppp with the -nat option: "# ppp -auto -nat " Enabled ip forwarding: root@bla: sysctl -w net.inet.ip.forwarding=1 net.inet.ip.forwarding: 1 -> 1 I'm running Windows 95 under vmware. Configured win95 to use ip address 192.168.0.20 (same as vmnet1 - is this correct?) and setup default gateway to 192.168.0.10 (is this correct?) Under FreeBSD I'm able to ping my Win95 machine (running under vmware): lyngbol@bla ~$ ping 192.168.0.20 PING 192.168.0.20 (192.168.0.20): 56 data bytes 64 bytes from 192.168.0.20: icmp_seq=0 ttl=32 time=32.030 ms ... And in Win95 I'm able to ping my FreeBSD box: ping 192.168.0.10 But I'm _not_ able to connect to anything outside my lan from Win95?!? What am I doing wrong? Thank you! - Michael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Mon Sep 4 22:21: 3 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from ods.ods.net (ip-216-145-173-167.idcnet.com [216.145.173.167]) by hub.freebsd.org (Postfix) with SMTP id D7F7137B423 for ; Mon, 4 Sep 2000 22:21:00 -0700 (PDT) Received: from [216.145.173.163] by ods.ods.net id 2a30.wrk; Tue, 5 Sep 2000 00:21:06 CDT Date: Tue, 5 Sep 2000 00:21:23 -0500 (CDT) From: Scotty Klement X-Sender: scotty@klement.dstorm.net To: =?X-UNKNOWN?Q?Michael_Lyngb=F8l?= Cc: freebsd-emulation@FreeBSD.ORG Subject: Re: How to make vmware+networking working? In-Reply-To: <20000904234836.A85754@tigerdyr.candid.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I dont know if this is (AT ALL) helpful, but: I've managed to get vmware to work with the typical (non-bridged) host-only networking without any problems. I set up a seperate subnet for vmware (I used 192.168.254/24) and just had my FreeBSD box act as a gateway. This required me to set up a seperate IP for the vmnet1 interface, and the Windows Network configuration, and to set my vmnet1 IP as the default gateway in windows. Then, I enabled bridging by putting "options BRIDGE" in my kernel, and I changed my Windows IP (but not vmnet1) to be on my LAN's subnet, and this allowed me to see/talk to other machines on the LAN without problems, but I could no longer access the Internet. I also tried various different IP's for the vmnet1 interface, but to no avail. So, if you find a solution, please pass it along to me. :) If you need help/specifics on getting one of the two scenarios above to work, please reply, and I'll do my best :) On Mon, 4 Sep 2000, Michael Lyngb=F8l wrote: > Hi, >=20 > The last couple of days I've been trying to setup networking the > vmware2-port. No luck so far. >=20 > Here's what I've done: >=20 > - cvsup'ed and "make world" of 4.1-STABLE > - compiled a kernel including "options BRIDGE" > - installed the latest vmware2 port (vmware2/Makefile,v 1.22) >=20 > I'm using 192.168.0/24 on my local lan. Using user-ppp to connect to > internet. >=20 > Configured "xl0": >=20 > xl0: flags=3D8943 mtu 150= 0 > inet 192.168.0.10 netmask 0xffffff00 broadcast 192.168.0.255 > ... >=20 > Configured "vmnet1": >=20 > vmnet1: flags=3D8843 mtu 1500 > inet 192.168.0.20 netmask 0xffffff00 broadcast 192.168.0.255 > ... >=20 > Started ppp with the -nat option: "# ppp -auto -nat " >=20 > Enabled ip forwarding: >=20 > root@bla: sysctl -w net.inet.ip.forwarding=3D1 > net.inet.ip.forwarding: 1 -> 1 >=20 >=20 > I'm running Windows 95 under vmware. Configured win95 to use ip address > 192.168.0.20 (same as vmnet1 - is this correct?) and setup default > gateway to 192.168.0.10 (is this correct?) >=20 > Under FreeBSD I'm able to ping my Win95 machine (running under vmware): >=20 > lyngbol@bla ~$ ping 192.168.0.20 > PING 192.168.0.20 (192.168.0.20): 56 data bytes > 64 bytes from 192.168.0.20: icmp_seq=3D0 ttl=3D32 time=3D32.030 ms > ... >=20 > And in Win95 I'm able to ping my FreeBSD box: >=20 > ping 192.168.0.10 >=20 >=20 > But I'm _not_ able to connect to anything outside my lan from Win95?!? >=20 >=20 > What am I doing wrong? >=20 >=20 > Thank you! >=20 > - Michael >=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Tue Sep 5 15: 2:35 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from server.azur.cx (11dyn25.delft.casema.net [212.64.18.25]) by hub.freebsd.org (Postfix) with ESMTP id CAB0537B423 for ; Tue, 5 Sep 2000 15:02:22 -0700 (PDT) Received: from localhost (ewout@localhost) by server.azur.cx (8.9.3/8.9.3) with ESMTP id AAA00592 for ; Wed, 6 Sep 2000 00:01:21 +0200 (CEST) (envelope-from ewout@azur.cx) Date: Wed, 6 Sep 2000 00:01:21 +0200 (CEST) From: Ewout Vonk To: freebsd-emulation@FreeBSD.ORG Subject: Parallelport use in VMware Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I read on Vladimir's website that parallel ports are still untested. I have tried to get those working, that is a bi-directional port. But when I run the vm with it, it says: 'Device or resource busy. parallel0 will start disconnected' No matter if I use my first or second parallel port (lpt0 is used by lpd, lpt1 is used by my scanner, but only under w98 when I get VMware running..) I have linked to /dev/lpt0 and to /dev/ppi0 from /compat/linux/dev/ but both refuse to work.. Does anyone know how to fix this? BTW, I am not on this list, but I do keep track of lists.openresources.com.. Any help will be appreciated! Best regards, Ewout Vonk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Tue Sep 5 18:42:52 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from granger.mail.mindspring.net (granger.mail.mindspring.net [207.69.200.148]) by hub.freebsd.org (Postfix) with ESMTP id 4FB0237B423 for ; Tue, 5 Sep 2000 18:42:50 -0700 (PDT) Received: from vtpr5 (user-33qtiit.dialup.mindspring.com [199.174.202.93]) by granger.mail.mindspring.net (8.9.3/8.8.5) with SMTP id VAA28517; Tue, 5 Sep 2000 21:41:58 -0400 (EDT) Message-ID: <000501c017a3$b1995ce0$e40ffea9@vt.ny.us> From: "Vladimir Silyaev" To: "Michael Harnois" Cc: "Brian Beattie" , Subject: RE: vmware2 networking question Date: Tue, 5 Sep 2000 18:42:17 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org You have just enable 'option BRIDGE' in your kernel. And after that your 'hostonly' networking in VMware guest becoming really bridged. And that bridged connection has the same features [and problems] as regular FreeBSD bridge. -------- Vladimir Date: 02 Sep 2000 15:35:02 -0500 From: Michael Harnois To: freebsd-emulation@FreeBSD.ORG Subject: Re: vmware2 networking question Date: 02 Sep 2000 15:35:02 -0500 From: Michael Harnois To: freebsd-emulation@FreeBSD.ORG Subject: Re: vmware2 networking questiond Date: 02 Sep 2000 15:35:02 -0500 From: Michael Harnois To: freebsd-emulation@FreeBSD.ORG Subject: Re: vmware2 networking questiond Date: 02 Sep 2000 15:35:02 -0500 From: Michael Harnois To: freebsd-emulation@FreeBSD.ORG Subject: Re: vmware2 networking question Date: 02 Sep 2000 15:35:02 -0500 From: Michael Harnois To: freebsd-emulation@FreeBSD.ORG Subject: Re: vmware2 networking question On Sat, 26 Aug 2000 11:05:06 -0700 (PDT), Brian Beattie said: > I have vmware2 running under 4-Stable using host-only > networking. I have seen some trafic indicating that > bridged-networking can be made to work. Is this true? The port maintainer has done some work at enabling vmware2 to use FreeBSD's bridged networking. However, he seems to have fallen off the face of the earth in the last month or so. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Tue Sep 5 19:44:28 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 6389537B422 for ; Tue, 5 Sep 2000 19:44:25 -0700 (PDT) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id WAA01657; Tue, 5 Sep 2000 22:44:14 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.0/8.9.1) id e862iEM24144; Tue, 5 Sep 2000 22:44:14 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 5 Sep 2000 22:44:14 -0400 (EDT) To: marcel@cup.hp.com Cc: freebsd-emulation@freebsd.org Subject: IBM JDK fails due to lack of SA_SIGINFO support X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14773.43466.744621.411519@grasshopper.cs.duke.edu> Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Currently the IBM jdk & jvm don't run under our linux abi. This had previously been attributed to the "sigaltstack: Cannot allocate memory" message one sees when running it. Upon further investigation, this appears to be a red herring. The "real" problem is as simple (or, rather, complex) as the fact that we don't support SA_SIGINFO style signal handlers under the linux abi. The program installs signal handlers for just about everything. One thread sends another a SIGUSR2, which is caught. As soon as the handler tries to dereference sip, it SEGV's. It proceeds to catch that, then gets caught in an infinate loop of catching SEGV's & SEGV'ing in the handler. The appended program demonstrates the problem when its built on a linux system & run on a FreeBSD one. Run it in the background & send it SIGUSR2. Notice it faults as soon as it deref's sip. I've been trying to whip up a linux_rt_sendsig() that could handle SA_SIGINFO style signal handlers. However, I've been failing miserably. Any help from x86 savy people would be appreciated -- I'm mainly an alpha guy :-( Cheers, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 #include #include #include static void kill_handler(int sig, siginfo_t *sip, void *context) { printf("\n"); printf("&sig = %p\n", &sig); printf("&sip = %p\n", &sip); printf("sip = %p\n", sip); printf("context = %p\n", context); printf("sip->si_signo = 0x%lx\n", sip->si_signo); /* KABOOM!*/ exit(0); } main(int argc, char *argv[]) { sigset_t sigset; struct sigaction sa; int i, ret; volatile int bar; int *array; bzero((char*)& (sa.sa_mask), sizeof(sigset_t)); sa.sa_flags = SA_SIGINFO; sa.sa_sigaction = kill_handler; sigaction(SIGUSR2, &sa, NULL); while (1); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Tue Sep 5 20: 0:32 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.242]) by hub.freebsd.org (Postfix) with ESMTP id 0E94E37B424 for ; Tue, 5 Sep 2000 20:00:30 -0700 (PDT) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel1.hp.com (Postfix) with ESMTP id 04B62C60; Tue, 5 Sep 2000 20:00:29 -0700 (PDT) Received: from cup.hp.com (p1000180.nsr.hp.com [15.109.0.180]) by adlmail.cup.hp.com (8.9.3 (PHNE_18546)/8.9.3 SMKit7.02) with ESMTP id UAA23944; Tue, 5 Sep 2000 20:00:28 -0700 (PDT) Message-ID: <39B5B34C.C23D4E55@cup.hp.com> Date: Tue, 05 Sep 2000 20:00:28 -0700 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Andrew Gallatin Cc: freebsd-emulation@freebsd.org Subject: Re: IBM JDK fails due to lack of SA_SIGINFO support References: <14773.43466.744621.411519@grasshopper.cs.duke.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Andrew Gallatin wrote: > > The appended program demonstrates the problem when its built on a > linux system & run on a FreeBSD one. Run it in the background & send > it SIGUSR2. Notice it faults as soon as it deref's sip. Thanks, Drew! If you don't mind, I prefer to work on this after we have the Linuxlator on Alpha. That way anything we do can be tested on Alpha as well. It also avoids that I'm thrashing (ie swapping too much work between my plate and my brain too quickly :-) -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Tue Sep 5 20:34:53 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from c1030098-a.wtrlo1.ia.home.com (c1030098-a.wtrlo1.ia.home.com [24.14.126.45]) by hub.freebsd.org (Postfix) with ESMTP id CA22A37B422 for ; Tue, 5 Sep 2000 20:34:50 -0700 (PDT) Received: (from mdharnois@localhost) by c1030098-a.wtrlo1.ia.home.com (8.11.0/8.11.0) id e863Yn209192; Tue, 5 Sep 2000 22:34:49 -0500 (CDT) (envelope-from mdharnois@home.com) X-Authentication-Warning: mharnois.workgroup.net: mdharnois set sender to mdharnois@home.com using -f To: "Vladimir Silyaev" Cc: "Brian Beattie" , Subject: Re: vmware2 networking question References: <000501c017a3$b1995ce0$e40ffea9@vt.ny.us> From: Michael Harnois Date: 05 Sep 2000 22:34:49 -0500 In-Reply-To: "Vladimir Silyaev"'s message of "Tue, 5 Sep 2000 18:42:17 -0700" Message-ID: <86lmx6yyzq.fsf@mharnois.workgroup.net> Lines: 18 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.2 (Nike) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 5 Sep 2000 18:42:17 -0700, "Vladimir Silyaev" said: > You have just enable 'option BRIDGE' in your kernel. And after > that your 'hostonly' networking in VMware guest becoming really > bridged. Except it doesn't work. Perhaps it works for you, but vmware2 networking on my machine stops working entirely until I disable the bridge. In addition, having bridging enabled causes loops in the bridge topology when one has more than one ethernet card in the machine. -- Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA mdharnois@home.com aa0bt@aa0bt.ampr.org The opposite of a correct statement is a false statement. The opposite of a profound truth may well be another profound truth. -- Niels Bohr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Tue Sep 5 21:50:16 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id 1F27F37B423 for ; Tue, 5 Sep 2000 21:50:14 -0700 (PDT) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.123.131]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id WAA13409; Tue, 5 Sep 2000 22:47:28 -0600 (MDT) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id WAA23183; Tue, 5 Sep 2000 22:47:21 -0600 (MDT) (envelope-from nate) Date: Tue, 5 Sep 2000 22:47:21 -0600 (MDT) Message-Id: <200009060447.WAA23183@nomad.yogotech.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Andrew Gallatin Cc: marcel@cup.hp.com, freebsd-emulation@FreeBSD.ORG Subject: Re: IBM JDK fails due to lack of SA_SIGINFO support In-Reply-To: <14773.43466.744621.411519@grasshopper.cs.duke.edu> References: <14773.43466.744621.411519@grasshopper.cs.duke.edu> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Currently the IBM jdk & jvm don't run under our linux abi. This had > previously been attributed to the "sigaltstack: Cannot allocate > memory" message one sees when running it. Upon further investigation, > this appears to be a red herring. Umm, I'd believe this except that someone sent me a patch (which I've forwarded to Marcel) that fixes this and is related to the sigalstack error above. At least the author of the patch claims that the IBM JDK now runs successfully on his box, running some version of FreeBSD. :) > The "real" problem is as simple > (or, rather, complex) as the fact that we don't support SA_SIGINFO > style signal handlers under the linux abi. [ Great explanation deleted ] Hmm, I'm at a loss. I've heard that things work fine with the signalstack issues fixed, so maybe the java program that he is running doesn't tickle the bug, although I find that rather difficult to believe given that almost every Java program known to man is multi-threaded. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Tue Sep 5 23:44:51 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from gilgamesch.bik-gmbh.de (T1-Hansenet.BIK-GmbH.de [192.76.134.246]) by hub.freebsd.org (Postfix) with ESMTP id 336B637B422 for ; Tue, 5 Sep 2000 23:44:48 -0700 (PDT) Received: (from cracauer@localhost) by gilgamesch.bik-gmbh.de (8.9.3/8.7.3) id IAA06318; Wed, 6 Sep 2000 08:39:57 +0200 (MET DST) Date: Wed, 6 Sep 2000 08:39:57 +0200 From: Martin Cracauer To: Nate Williams Cc: Andrew Gallatin , marcel@cup.hp.com, freebsd-emulation@FreeBSD.ORG Subject: Re: IBM JDK fails due to lack of SA_SIGINFO support Message-ID: <20000906083957.A5530@cons.org> References: <14773.43466.744621.411519@grasshopper.cs.duke.edu> <200009060447.WAA23183@nomad.yogotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200009060447.WAA23183@nomad.yogotech.com>; from nate@yogotech.com on Tue, Sep 05, 2000 at 10:47:21PM -0600 Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In <200009060447.WAA23183@nomad.yogotech.com>, Nate Williams wrote: > > Currently the IBM jdk & jvm don't run under our linux abi. This had > > previously been attributed to the "sigaltstack: Cannot allocate > > memory" message one sees when running it. Upon further investigation, > > this appears to be a red herring. > > Umm, I'd believe this except that someone sent me a patch (which I've > forwarded to Marcel) that fixes this and is related to the sigalstack > error above. At least the author of the patch claims that the IBM JDK > now runs successfully on his box, running some version of FreeBSD. :) > > > The "real" problem is as simple > > (or, rather, complex) as the fact that we don't support SA_SIGINFO > > style signal handlers under the linux abi. > > [ Great explanation deleted ] > > Hmm, I'm at a loss. I've heard that things work fine with the > signalstack issues fixed, so maybe the java program that he is running > doesn't tickle the bug, although I find that rather difficult to believe > given that almost every Java program known to man is multi-threaded. Maybe the patch that someone sent you just adds SA_SIGINFO arguments to every signal handler? That should make SA_SIGINOF using programs work and not break applications just using 1 argument. It would break non-SA_SIGNINFO arguemnts using handler, expecting a second argument: void hand(int s, struct sigcontext_struct context); Could you send me the patch or verify that it break the latter kind of applications? Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ BSD User Group Hamburg, Germany http://www.bsdhh.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Tue Sep 5 23:58: 4 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id 3751D37B424 for ; Tue, 5 Sep 2000 23:58:02 -0700 (PDT) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.123.131]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id AAA15523; Wed, 6 Sep 2000 00:55:22 -0600 (MDT) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id AAA24730; Wed, 6 Sep 2000 00:55:17 -0600 (MDT) (envelope-from nate) Date: Wed, 6 Sep 2000 00:55:17 -0600 (MDT) Message-Id: <200009060655.AAA24730@nomad.yogotech.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Martin Cracauer Cc: Nate Williams , Andrew Gallatin , marcel@cup.hp.com, freebsd-emulation@FreeBSD.ORG Subject: Re: IBM JDK fails due to lack of SA_SIGINFO support In-Reply-To: <20000906083957.A5530@cons.org> References: <14773.43466.744621.411519@grasshopper.cs.duke.edu> <200009060447.WAA23183@nomad.yogotech.com> <20000906083957.A5530@cons.org> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > Currently the IBM jdk & jvm don't run under our linux abi. This had > > > previously been attributed to the "sigaltstack: Cannot allocate > > > memory" message one sees when running it. Upon further investigation, > > > this appears to be a red herring. > > > > Umm, I'd believe this except that someone sent me a patch (which I've > > forwarded to Marcel) that fixes this and is related to the sigalstack > > error above. At least the author of the patch claims that the IBM JDK > > now runs successfully on his box, running some version of FreeBSD. :) > > > > > The "real" problem is as simple > > > (or, rather, complex) as the fact that we don't support SA_SIGINFO > > > style signal handlers under the linux abi. > > > > [ Great explanation deleted ] > > > > Hmm, I'm at a loss. I've heard that things work fine with the > > signalstack issues fixed, so maybe the java program that he is running > > doesn't tickle the bug, although I find that rather difficult to believe > > given that almost every Java program known to man is multi-threaded. > > Maybe the patch that someone sent you just adds SA_SIGINFO arguments > to every signal handler? Nope, it just bumps up the signal stack size. A slightly modified version of it was just committed to -current my Marcel, so try it out. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Wed Sep 6 1:12:29 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from tigerdyr.candid.dk (tigerdyr.candid.dk [193.162.142.120]) by hub.freebsd.org (Postfix) with ESMTP id 3655537B423 for ; Wed, 6 Sep 2000 01:12:26 -0700 (PDT) Received: by tigerdyr.candid.dk (Postfix, from userid 1001) id E956B98E5; Wed, 6 Sep 2000 10:12:24 +0200 (CEST) Date: Wed, 6 Sep 2000 10:12:24 +0200 From: =?iso-8859-1?Q?Michael_Lyngb=F8l?= To: Scotty Klement Cc: freebsd-emulation@FreeBSD.ORG Subject: Re: How to make vmware+networking working? Message-ID: <20000906101224.A71726@tigerdyr.candid.dk> References: <20000904234836.A85754@tigerdyr.candid.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: ; from scotty@ods.ods.net on Tue, Sep 05, 2000 at 12:21:23AM -0500 X-Operating-System: FreeBSD/i386 4.1-STABLE Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Sep 05, 2000 at 12:21:23AM -0500, Scotty Klement wrote: Hi, > I've managed to get vmware to work with the typical (non-bridged) > host-only networking without any problems. I set up a seperate subnet > for vmware (I used 192.168.254/24) and just had my FreeBSD box act as > a gateway. This required me to set up a seperate IP for the vmnet1 > interface, and the Windows Network configuration, and to set my vmnet1 > IP as the default gateway in windows. Jubii! Disabling "options BRIDGE", using a different/seperate subnet (192.168.254/24), make my FreeBSD box do NAT (ppp -nat ...), and use my vmnet1 IP as default gateway in Windows made it work. This is quite fine for me right now. > Then, I enabled bridging by putting "options BRIDGE" in my kernel, and > I changed my Windows IP (but not vmnet1) to be on my LAN's subnet, and > this allowed me to see/talk to other machines on the LAN without problems, > but I could no longer access the Internet. I also tried various different > IP's for the vmnet1 interface, but to no avail. Same thing here. Using a kernel compiled with "options BRIDGE" wont work. Haven't figured out why?! > So, if you find a solution, please pass it along to me. :) If you need > help/specifics on getting one of the two scenarios above to work, please > reply, and I'll do my best :) Thanks! :) - Michael > > > > On Mon, 4 Sep 2000, Michael Lyngbøl wrote: > > > Hi, > > > > The last couple of days I've been trying to setup networking the > > vmware2-port. No luck so far. > > > > Here's what I've done: > > > > - cvsup'ed and "make world" of 4.1-STABLE > > - compiled a kernel including "options BRIDGE" > > - installed the latest vmware2 port (vmware2/Makefile,v 1.22) > > > > I'm using 192.168.0/24 on my local lan. Using user-ppp to connect to > > internet. > > > > Configured "xl0": > > > > xl0: flags=8943 mtu 1500 > > inet 192.168.0.10 netmask 0xffffff00 broadcast 192.168.0.255 > > ... > > > > Configured "vmnet1": > > > > vmnet1: flags=8843 mtu 1500 > > inet 192.168.0.20 netmask 0xffffff00 broadcast 192.168.0.255 > > ... > > > > Started ppp with the -nat option: "# ppp -auto -nat " > > > > Enabled ip forwarding: > > > > root@bla: sysctl -w net.inet.ip.forwarding=1 > > net.inet.ip.forwarding: 1 -> 1 > > > > > > I'm running Windows 95 under vmware. Configured win95 to use ip address > > 192.168.0.20 (same as vmnet1 - is this correct?) and setup default > > gateway to 192.168.0.10 (is this correct?) > > > > Under FreeBSD I'm able to ping my Win95 machine (running under vmware): > > > > lyngbol@bla ~$ ping 192.168.0.20 > > PING 192.168.0.20 (192.168.0.20): 56 data bytes > > 64 bytes from 192.168.0.20: icmp_seq=0 ttl=32 time=32.030 ms > > ... > > > > And in Win95 I'm able to ping my FreeBSD box: > > > > ping 192.168.0.10 > > > > > > But I'm _not_ able to connect to anything outside my lan from Win95?!? > > > > > > What am I doing wrong? > > > > > > Thank you! > > > > - Michael > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Wed Sep 6 6: 3:36 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from server26.ilap.com (server26-main.ilap.com [216.223.128.41]) by hub.freebsd.org (Postfix) with ESMTP id 0563C37B423 for ; Wed, 6 Sep 2000 06:03:34 -0700 (PDT) Received: from horechup (server11.docucom.ca [216.223.156.11]) by server26.ilap.com (Pro-8.9.3/8.9.3/ILAP.COM Internet Light and Power Inc.) with SMTP id JAA17159 for ; Wed, 6 Sep 2000 09:03:26 -0400 (EDT) Message-ID: <029201c01802$957751c0$73f8d7a5@docucom.ca> Reply-To: "Paul Horechuk" From: "Paul Horechuk" To: Subject: Amiga SDK Date: Wed, 6 Sep 2000 09:01:31 -0400 Organization: DocuCom Imaging Solutions MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Has anyone had any success with the Amiga SDK under FreeBSD? The requirements are XFree86 running under RedHat 6.1. I know RedHat forms the basis of the linux-base emulation, yet there are functions that fail. I get an error regarding an unsupported protocol. The installation program requires a network card to obtain a MAC address. Although the card does exists (Netgear FX310), and it is configured and working under FreeBSD 4.1, the error still appears and detection fails. Please let me know if any further info is required. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Wed Sep 6 7:13:45 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from blount.mail.mindspring.net (blount.mail.mindspring.net [207.69.200.226]) by hub.freebsd.org (Postfix) with ESMTP id F00A137B423 for ; Wed, 6 Sep 2000 07:13:42 -0700 (PDT) Received: from vtpr5 (user-33qti64.dialup.mindspring.com [199.174.200.196]) by blount.mail.mindspring.net (8.9.3/8.8.5) with SMTP id KAA24159; Wed, 6 Sep 2000 10:13:05 -0400 (EDT) Message-ID: <000501c0180c$a0431940$e40ffea9@vt.ny.us> From: "Vladimir Silyaev" To: "Michael Harnois" Cc: "Brian Beattie" , References: <000501c017a3$b1995ce0$e40ffea9@vt.ny.us> <86lmx6yyzq.fsf@mharnois.workgroup.net> Subject: Re: vmware2 networking question Date: Wed, 6 Sep 2000 07:13:25 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ok. But those problem doesn't caused by vmware/vmnet, isn't it? I knew that such configuration works for some network cards/network drivers, in rest cases the network drivers and/or FreeBSD BRIDGE code should be fixed. Vladimir ----- Original Message ----- From: Michael Harnois To: Vladimir Silyaev Cc: Brian Beattie ; Sent: Tuesday, September 05, 2000 8:34 PM Subject: Re: vmware2 networking question > On Tue, 5 Sep 2000 18:42:17 -0700, "Vladimir Silyaev" said: > > > You have just enable 'option BRIDGE' in your kernel. And after > > that your 'hostonly' networking in VMware guest becoming really > > bridged. > > Except it doesn't work. Perhaps it works for you, but vmware2 > networking on my machine stops working entirely until I disable the > bridge. In addition, having bridging enabled causes loops in the > bridge topology when one has more than one ethernet card in the > machine. > > -- > Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA > mdharnois@home.com aa0bt@aa0bt.ampr.org > The opposite of a correct statement is a false statement. > The opposite of a profound truth may well be another profound truth. > -- Niels Bohr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Wed Sep 6 8:21:31 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from c1030098-a.wtrlo1.ia.home.com (c1030098-a.wtrlo1.ia.home.com [24.14.126.45]) by hub.freebsd.org (Postfix) with ESMTP id 8428137B422 for ; Wed, 6 Sep 2000 08:21:26 -0700 (PDT) Received: (from mdharnois@localhost) by c1030098-a.wtrlo1.ia.home.com (8.11.0/8.11.0) id e86FLPt20443; Wed, 6 Sep 2000 10:21:25 -0500 (CDT) (envelope-from mdharnois@home.com) X-Authentication-Warning: mharnois.workgroup.net: mdharnois set sender to mdharnois@home.com using -f To: "Vladimir Silyaev" Cc: "Brian Beattie" , Subject: Re: vmware2 networking question References: <000501c017a3$b1995ce0$e40ffea9@vt.ny.us> <86lmx6yyzq.fsf@mharnois.workgroup.net> <000501c0180c$a0431940$e40ffea9@vt.ny.us> From: Michael Harnois Date: 06 Sep 2000 10:21:25 -0500 In-Reply-To: "Vladimir Silyaev"'s message of "Wed, 6 Sep 2000 07:13:25 -0700" Message-ID: <86zolly2a2.fsf@mharnois.workgroup.net> Lines: 18 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.2 (Nike) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 6 Sep 2000 07:13:25 -0700, "Vladimir Silyaev" said: > Ok. But those problem doesn't caused by vmware/vmnet, isn't it? No, but the fact that vmware networking doesn't work at all under some situations with bridging enabled is. > I knew that such configuration works for some network > cards/network drivers, in rest cases the network drivers and/or > FreeBSD BRIDGE code should be fixed. I saw no reports on the list of situations where it works. -- Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA mdharnois@home.com aa0bt@aa0bt.ampr.org OPTIMIST, n. A proponent of the doctrine that black is white. --Ambrose Bierce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Wed Sep 6 9:59:38 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 9095B37B422 for ; Wed, 6 Sep 2000 09:59:34 -0700 (PDT) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id MAA15617; Wed, 6 Sep 2000 12:48:12 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.0/8.9.1) id e86GmCd25472; Wed, 6 Sep 2000 12:48:12 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 6 Sep 2000 12:48:11 -0400 (EDT) To: nate@yogotech.com (Nate Williams) Cc: marcel@cup.hp.com, freebsd-emulation@FreeBSD.ORG Subject: Re: IBM JDK fails due to lack of SA_SIGINFO support In-Reply-To: <200009060447.WAA23183@nomad.yogotech.com> References: <14773.43466.744621.411519@grasshopper.cs.duke.edu> <200009060447.WAA23183@nomad.yogotech.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14774.29608.353021.688597@grasshopper.cs.duke.edu> Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Nate Williams writes: > > Currently the IBM jdk & jvm don't run under our linux abi. This had > > previously been attributed to the "sigaltstack: Cannot allocate > > memory" message one sees when running it. Upon further investigation, > > this appears to be a red herring. > > Umm, I'd believe this except that someone sent me a patch (which I've > forwarded to Marcel) that fixes this and is related to the sigalstack > error above. At least the author of the patch claims that the IBM JDK > now runs successfully on his box, running some version of FreeBSD. :) Perhaps he's using a different version of the IBM java stuff? I'm using the "IBMJava2-SDK-13.tgz" that I downloaded last week. On a linux box, (where I can actually get version info) : java version "1.3.0" Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0) Classic VM (build 1.3.0, J2RE 1.3.0 IBM build cx130-20000815 (JIT enabled: jitc)) The change you're referring to isn't all that much different that what I'd been doing previously (setting MINSIGSTKSZ to 2048 in sys/signal.h). I tried the change, and it doesn't seem to help at all. > > The "real" problem is as simple > > (or, rather, complex) as the fact that we don't support SA_SIGINFO > > style signal handlers under the linux abi. > > [ Great explanation deleted ] > > Hmm, I'm at a loss. I've heard that things work fine with the > signalstack issues fixed, so maybe the java program that he is running > doesn't tickle the bug, although I find that rather difficult to believe > given that almost every Java program known to man is multi-threaded. Maybe IBM moved to using SA_SIGINFO handlers for their thread coordination? Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Wed Sep 6 10: 4:46 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id EF9D237B440 for ; Wed, 6 Sep 2000 10:04:42 -0700 (PDT) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.123.131]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id LAA25446; Wed, 6 Sep 2000 11:00:50 -0600 (MDT) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id LAA28404; Wed, 6 Sep 2000 11:00:46 -0600 (MDT) (envelope-from nate) Date: Wed, 6 Sep 2000 11:00:46 -0600 (MDT) Message-Id: <200009061700.LAA28404@nomad.yogotech.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Andrew Gallatin Cc: nate@yogotech.com (Nate Williams), marcel@cup.hp.com, freebsd-emulation@FreeBSD.ORG Subject: Re: IBM JDK fails due to lack of SA_SIGINFO support In-Reply-To: <14774.29608.353021.688597@grasshopper.cs.duke.edu> References: <14773.43466.744621.411519@grasshopper.cs.duke.edu> <200009060447.WAA23183@nomad.yogotech.com> <14774.29608.353021.688597@grasshopper.cs.duke.edu> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > Currently the IBM jdk & jvm don't run under our linux abi. This had > > > previously been attributed to the "sigaltstack: Cannot allocate > > > memory" message one sees when running it. Upon further investigation, > > > this appears to be a red herring. > > > > Umm, I'd believe this except that someone sent me a patch (which I've > > forwarded to Marcel) that fixes this and is related to the sigalstack > > error above. At least the author of the patch claims that the IBM JDK > > now runs successfully on his box, running some version of FreeBSD. :) > > Perhaps he's using a different version of the IBM java stuff? I'm > using the "IBMJava2-SDK-13.tgz" that I downloaded last week. On a > linux box, (where I can actually get version info) : Possibly. > > Hmm, I'm at a loss. I've heard that things work fine with the > > signalstack issues fixed, so maybe the java program that he is running > > doesn't tickle the bug, although I find that rather difficult to believe > > given that almost every Java program known to man is multi-threaded. > > Maybe IBM moved to using SA_SIGINFO handlers for their thread > coordination? Maybe. I'm just the man in the middle. :( Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Wed Sep 6 10: 6:53 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (Postfix) with ESMTP id CEA2B37B43F for ; Wed, 6 Sep 2000 10:06:46 -0700 (PDT) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel3.hp.com (Postfix) with ESMTP id F3E1075B; Wed, 6 Sep 2000 10:06:44 -0700 (PDT) Received: from cup.hp.com (gauss.cup.hp.com [15.28.97.152]) by adlmail.cup.hp.com (8.9.3 (PHNE_18546)/8.9.3 SMKit7.02) with ESMTP id KAA14432; Wed, 6 Sep 2000 10:06:44 -0700 (PDT) Message-ID: <39B679A4.2DBEA4FF@cup.hp.com> Date: Wed, 06 Sep 2000 13:06:44 -0400 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Andrew Gallatin Cc: Nate Williams , freebsd-emulation@FreeBSD.ORG Subject: Re: IBM JDK fails due to lack of SA_SIGINFO support References: <14773.43466.744621.411519@grasshopper.cs.duke.edu> <200009060447.WAA23183@nomad.yogotech.com> <14774.29608.353021.688597@grasshopper.cs.duke.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Andrew Gallatin wrote: > > The change you're referring to isn't all that much different that what > I'd been doing previously (setting MINSIGSTKSZ to 2048 in sys/signal.h). This is what I like to do, but with a different value on the Alpha. Did you had any problems with it? -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Wed Sep 6 10:23:25 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 8684637B423 for ; Wed, 6 Sep 2000 10:23:22 -0700 (PDT) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id NAA16460; Wed, 6 Sep 2000 13:23:14 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.0/8.9.1) id e86HNEb25521; Wed, 6 Sep 2000 13:23:14 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 6 Sep 2000 13:23:14 -0400 (EDT) To: Marcel Moolenaar Cc: Nate Williams , freebsd-emulation@FreeBSD.ORG Subject: Re: IBM JDK fails due to lack of SA_SIGINFO support In-Reply-To: <39B679A4.2DBEA4FF@cup.hp.com> References: <14773.43466.744621.411519@grasshopper.cs.duke.edu> <200009060447.WAA23183@nomad.yogotech.com> <14774.29608.353021.688597@grasshopper.cs.duke.edu> <39B679A4.2DBEA4FF@cup.hp.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14774.32070.832013.155864@grasshopper.cs.duke.edu> Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Marcel Moolenaar writes: > Andrew Gallatin wrote: > > > > The change you're referring to isn't all that much different that what > > I'd been doing previously (setting MINSIGSTKSZ to 2048 in sys/signal.h). > > This is what I like to do, but with a different value on the Alpha. Did > you had any problems with it? > No, but I haven't really tested it all that much.. FWIW, the IBM JDK was trying to set its sig stack size to 8168 or something like that.. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Wed Sep 6 10:32: 9 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 560EF37B42C for ; Wed, 6 Sep 2000 10:32:03 -0700 (PDT) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id NAA16695; Wed, 6 Sep 2000 13:32:01 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.0/8.9.1) id e86HW1i25541; Wed, 6 Sep 2000 13:32:01 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 6 Sep 2000 13:32:01 -0400 (EDT) To: Marcel Moolenaar Cc: freebsd-emulation@freebsd.org Subject: Re: IBM JDK fails due to lack of SA_SIGINFO support In-Reply-To: <39B5B34C.C23D4E55@cup.hp.com> References: <14773.43466.744621.411519@grasshopper.cs.duke.edu> <39B5B34C.C23D4E55@cup.hp.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14774.32224.318381.176390@grasshopper.cs.duke.edu> Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Marcel Moolenaar writes: > Andrew Gallatin wrote: > > > > The appended program demonstrates the problem when its built on a > > linux system & run on a FreeBSD one. Run it in the background & send > > it SIGUSR2. Notice it faults as soon as it deref's sip. > > Thanks, Drew! > > If you don't mind, I prefer to work on this after we have the Linuxlator > on Alpha. That way anything we do can be tested on Alpha as well. It This is totally i386 specific & is pretty much orthogonal to the alpha merge. > also avoids that I'm thrashing (ie swapping too much work between my > plate and my brain too quickly :-) I understand, but I really need this to work ASAP, or I may be forced to convert some FreeBSD boxes to linux. I guess I'm going to keep beating my head against the wall until I get tired of the squishy sound. :-( Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Wed Sep 6 10:33:42 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id C7F7037B422 for ; Wed, 6 Sep 2000 10:33:38 -0700 (PDT) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id NAA16418; Wed, 6 Sep 2000 13:22:03 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.0/8.9.1) id e86HM3Z25516; Wed, 6 Sep 2000 13:22:03 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 6 Sep 2000 13:22:03 -0400 (EDT) To: nate@yogotech.com (Nate Williams) Cc: marcel@cup.hp.com, freebsd-emulation@FreeBSD.ORG Subject: Re: IBM JDK fails due to lack of SA_SIGINFO support In-Reply-To: <200009061700.LAA28404@nomad.yogotech.com> References: <14773.43466.744621.411519@grasshopper.cs.duke.edu> <200009060447.WAA23183@nomad.yogotech.com> <14774.29608.353021.688597@grasshopper.cs.duke.edu> <200009061700.LAA28404@nomad.yogotech.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14774.31221.183770.594341@grasshopper.cs.duke.edu> Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Nate Williams writes: > > Maybe. I'm just the man in the middle. :( I hear ya.. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Wed Sep 6 12: 1:59 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from c1030098-a.wtrlo1.ia.home.com (c1030098-a.wtrlo1.ia.home.com [24.14.126.45]) by hub.freebsd.org (Postfix) with ESMTP id C5F6237B424 for ; Wed, 6 Sep 2000 12:01:57 -0700 (PDT) Received: (from mdharnois@localhost) by c1030098-a.wtrlo1.ia.home.com (8.11.0/8.11.0) id e86J1hR03431; Wed, 6 Sep 2000 14:01:43 -0500 (CDT) (envelope-from mdharnois@home.com) X-Authentication-Warning: mharnois.workgroup.net: mdharnois set sender to mdharnois@home.com using -f To: Michael =?iso-8859-1?q?Lyngb=F8l?= Cc: Scotty Klement , freebsd-emulation@FreeBSD.ORG Subject: Re: How to make vmware+networking working? References: <20000904234836.A85754@tigerdyr.candid.dk> <20000906101224.A71726@tigerdyr.candid.dk> From: Michael Harnois Date: 06 Sep 2000 14:01:43 -0500 In-Reply-To: Michael =?iso-8859-1?q?Lyngb=F8l's?= message of "Wed, 6 Sep 2000 10:12:24 +0200" Message-ID: <86wvgpmjjc.fsf@mharnois.workgroup.net> Lines: 12 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.2 (Nike) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 6 Sep 2000 10:12:24 +0200, Michael Lyngb=F8l sa= id: > Same thing here. Using a kernel compiled with "options BRIDGE" > wont work. Same here. --=20 Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA=20 mdharnois@home.com aa0bt@aa0bt.ampr.org=20 OPTIMIST, n. A proponent of the doctrine that black is white. --Ambrose Bierce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Wed Sep 6 13:48:47 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id E205037B423 for ; Wed, 6 Sep 2000 13:48:42 -0700 (PDT) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id QAA21784; Wed, 6 Sep 2000 16:38:58 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.0/8.9.1) id e86KcwZ25776; Wed, 6 Sep 2000 16:38:58 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 6 Sep 2000 16:38:58 -0400 (EDT) To: Martin Cracauer Cc: Nate Williams , marcel@cup.hp.com, freebsd-emulation@FreeBSD.ORG Subject: Re: IBM JDK fails due to lack of SA_SIGINFO support In-Reply-To: <20000906083957.A5530@cons.org> References: <14773.43466.744621.411519@grasshopper.cs.duke.edu> <200009060447.WAA23183@nomad.yogotech.com> <20000906083957.A5530@cons.org> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14774.42905.390753.70408@grasshopper.cs.duke.edu> Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm getting closer. I'd really appreciate some help from x86 people.... I think its coming down to my lack of knowledge about x86 assembly :-( So far, I've created a linux_rt_sendsig, which pushes out a linux_rt_sigframe, rather than a normal linux_sigframe. I've padded out the linux_sigframe struct by 164 bytes so that the sizes match. I have diffs for what I've done so far at http://www.cs.duke.edu/~gallatin/linux_sa_siginfo/diff This makes the linux sa_siginfo handler "sorta" work. Right now, my toy test program works after a fashion (prints out garbage for the sending uid & pid, but doesn't crash). The IBM jdk _does_ still crash. If I modify my test code (appended) to return from the signal handler, my code crashes too. If I print out the faulting PC from within the kernel, its at 0xbfbfffe3. According to a uprintf, the sigtramp code starts at 0xbfbfffd8. I suppose this means that the current sigtramp code won't work for linux SA_SIGINFO style handlers Can some x86 guru explain the sigtramp code to me? included it for reference: NON_GPROF_ENTRY(linux_sigcode) call *LINUX_SIGF_HANDLER(%esp) leal LINUX_SIGF_SC(%esp),%ebx /* linux scp */ movl LINUX_SC_GS(%ebx),%gs push %eax /* fake ret addr */ movl $LINUX_SYS_linux_sigreturn,%eax /* linux_sigreturn() */ int $0x80 /* enter kernel with args */ 0: jmp 0b ALIGN_TEXT _linux_esigcode: .data .globl _linux_szsigcode _linux_szsigcode: .long _linux_esigcode-_linux_sigcode .text Here's my current test code: #include #include #include int foo = 0; static void kill_handler(int sig, siginfo_t *sip, void *context) { int siginfo_size; int *p; printf("\n"); printf("&sig = %p\n", &sig); printf("&sip = %p\n", &sip); printf("sip = %p\n", sip); printf("context = %p\n", context); printf("sip->si_signo = %d\n", sip->si_signo); printf("sip->si_uid = %d\n", sip->si_uid); printf("sip->si_pid = %d\n", sip->si_pid); siginfo_size = (unsigned long )context - (unsigned long) sip; printf("sizeof(siginfo_t) = %ld\n", siginfo_size); for (p = (int *)sip; p != (int *)context; p++) printf("%p: 0x%x\n", p, *p); foo = 1; } main(int argc, char *argv[]) { sigset_t sigset; struct sigaction sa; int i, ret; volatile int bar; int *array; bzero((char*)& (sa.sa_mask), sizeof(sigset_t)); sa.sa_flags = SA_SIGINFO; sa.sa_sigaction = kill_handler; sigaction(45, &sa, NULL); sigaction(SIGUSR2, &sa, NULL); printf("installed handler at %p\n", kill_handler); while (!foo); } Cheers, Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Wed Sep 6 19:47: 5 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from blount.mail.mindspring.net (blount.mail.mindspring.net [207.69.200.226]) by hub.freebsd.org (Postfix) with ESMTP id 39FCC37B422 for ; Wed, 6 Sep 2000 19:47:03 -0700 (PDT) Received: from vtpr5 (user-33qtifl.dialup.mindspring.com [199.174.201.245]) by blount.mail.mindspring.net (8.9.3/8.8.5) with SMTP id WAA20386; Wed, 6 Sep 2000 22:46:24 -0400 (EDT) Message-ID: <000c01c01875$dfca6f00$f5c9aec7@vt.ny.us> From: "Vladimir Silyaev" To: "Michael Harnois" Cc: "Brian Beattie" , References: <000501c017a3$b1995ce0$e40ffea9@vt.ny.us><86lmx6yyzq.fsf@mharnois.workgroup.net><000501c0180c$a0431940$e40ffea9@vt.ny.us> <86zolly2a2.fsf@mharnois.workgroup.net> Subject: Re: vmware2 networking question Date: Wed, 6 Sep 2000 19:46:45 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Could you describe [hardware] configuration in which vmware guest works without enabled bridiging, and doesn't work at all with enabled bridged. I did a testing with 3COM card with xl driver. It works without any problems. Regards, Vladimir ----- Original Message ----- From: Michael Harnois To: Vladimir Silyaev Cc: Brian Beattie ; Sent: Wednesday, September 06, 2000 8:21 AM Subject: Re: vmware2 networking question > On Wed, 6 Sep 2000 07:13:25 -0700, "Vladimir Silyaev" said: > > > Ok. But those problem doesn't caused by vmware/vmnet, isn't it? > > No, but the fact that vmware networking doesn't work at all under some > situations with bridging enabled is. > > > I knew that such configuration works for some network > > cards/network drivers, in rest cases the network drivers and/or > > FreeBSD BRIDGE code should be fixed. > > I saw no reports on the list of situations where it works. > > -- > Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA > mdharnois@home.com aa0bt@aa0bt.ampr.org > OPTIMIST, n. A proponent of the doctrine that black is white. > --Ambrose Bierce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Wed Sep 6 19:53:40 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from c1030098-a.wtrlo1.ia.home.com (c1030098-a.wtrlo1.ia.home.com [24.14.126.45]) by hub.freebsd.org (Postfix) with ESMTP id 0C6CC37B422 for ; Wed, 6 Sep 2000 19:53:38 -0700 (PDT) Received: (from mdharnois@localhost) by c1030098-a.wtrlo1.ia.home.com (8.11.0/8.11.0) id e872rZo15635; Wed, 6 Sep 2000 21:53:35 -0500 (CDT) (envelope-from mdharnois@home.com) X-Authentication-Warning: mharnois.workgroup.net: mdharnois set sender to mdharnois@home.com using -f To: "Vladimir Silyaev" Cc: "Brian Beattie" , Subject: Re: vmware2 networking question References: <000501c017a3$b1995ce0$e40ffea9@vt.ny.us> <86lmx6yyzq.fsf@mharnois.workgroup.net> <000501c0180c$a0431940$e40ffea9@vt.ny.us> <86zolly2a2.fsf@mharnois.workgroup.net> <000c01c01875$dfca6f00$f5c9aec7@vt.ny.us> From: Michael Harnois Date: 06 Sep 2000 21:53:35 -0500 In-Reply-To: "Vladimir Silyaev"'s message of "Wed, 6 Sep 2000 19:46:45 -0700" Message-ID: <868zt4lxow.fsf@mharnois.workgroup.net> Lines: 64 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.2 (Nike) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 6 Sep 2000 19:46:45 -0700, "Vladimir Silyaev" said: > Could you describe [hardware] configuration in which vmware > guest works without enabled bridiging, and doesn't work at all > with enabled bridged. dc0: flags=8943 mtu 1500 inet 24.14.126.45 netmask 0xffffff00 broadcast 24.14.126.255 ether 00:a0:cc:3d:00:ae media: autoselect (10baseT/UTP) status: active supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP none dc1: flags=8943 mtu 1500 inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255 ether 00:20:78:04:35:83 media: autoselect (100baseTX) status: active supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP none lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 ppp0: flags=8010 mtu 1500 faith0: flags=8000 mtu 1500 gif0: flags=8010 mtu 1280 gif1: flags=8010 mtu 1280 gif2: flags=8010 mtu 1280 gif3: flags=8010 mtu 1280 vmnet1: flags=8943 mtu 1500 inet 192.168.254.1 netmask 0xffffff00 broadcast 192.168.254.255 ether 00:bd:4d:05:00:01 with bridging enabled, the syslog produces multiple entries like -- loop (0) 00.10.a4.f4.a5.73 to dc0 from dc1 (active) -- loop (0) 00.10.a4.f4.a5.73 to dc0 from dc1 (active) -- loop (0) 00.10.a4.f4.a5.73 to dc0 from dc1 (active) -- loop (0) 00.10.a4.f4.a5.73 to dc0 from dc1 (active) -- loop (0) 00.40.d0.0e.75.a2 to dc0 from dc1 (active) -- loop (1) 00.40.d0.0e.75.a2 to dc1 from dc0 (active) -- loop (0) 00.40.d0.0e.75.a2 to dc0 from dc1 (active) -- loop (0) 00.40.d0.0e.75.a2 to dc1 from dc0 (active) -- loop (0) 00.40.d0.0e.75.a2 to dc0 from dc1 (active) -- loop (0) 00.10.a4.f4.a5.73 to dc0 from dc1 (active) -- loop (1) 00.10.a4.f4.a5.73 to dc1 from dc0 (active) -- loop (0) 00.10.a4.f4.a5.73 to dc0 from dc1 (active) -- loop (0) 00.40.d0.0e.75.a2 to dc0 from dc1 (active) -- loop (0) 00.40.d0.0e.75.a2 to dc0 from dc1 (active) -- loop (0) 00.10.a4.f4.a5.73 to dc0 from dc1 (active) -- loop (0) 00.10.a4.f4.a5.73 to dc0 from dc1 (active) -- loop (0) 00.10.a4.f4.a5.73 to dc0 from dc1 (active) -- loop (0) 00.40.d0.0e.75.a2 to dc0 from dc1 (active) -- loop (1) 00.40.d0.0e.75.a2 to dc1 from dc0 (active) These messages cease with bridging disabled. > I did a testing with 3COM card with xl driver. It works without > any problems. Then perhaps there is something in your software configuration which has not been explained to the rest of us. -- Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA mdharnois@home.com aa0bt@aa0bt.ampr.org Paranoids are people, too; they have their own problems. It's easy to criticize, but if everybody hated you, you'd be paranoid too. -- D. J. Hicks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Wed Sep 6 20:19:41 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id BC31B37B422 for ; Wed, 6 Sep 2000 20:19:37 -0700 (PDT) Received: (qmail 20483 invoked from network); 7 Sep 2000 03:19:34 -0000 Received: from unknown (HELO bde.zeta.org.au) (203.2.228.102) by gidora.zeta.org.au with SMTP; 7 Sep 2000 03:19:34 -0000 Date: Thu, 7 Sep 2000 14:19:30 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Andrew Gallatin Cc: Nate Williams , marcel@cup.hp.com, freebsd-emulation@FreeBSD.ORG Subject: Re: IBM JDK fails due to lack of SA_SIGINFO support In-Reply-To: <14774.29608.353021.688597@grasshopper.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 6 Sep 2000, Andrew Gallatin wrote: > Nate Williams writes: > > Umm, I'd believe this except that someone sent me a patch (which I've > > forwarded to Marcel) that fixes this and is related to the sigalstack > > error above. At least the author of the patch claims that the IBM JDK > > now runs successfully on his box, running some version of FreeBSD. :) > The change you're referring to isn't all that much different that what > I'd been doing previously (setting MINSIGSTKSZ to 2048 in sys/signal.h). It is quite different. You change is not incorrect, but the committed versions of Nate's patch results in memory beyond the end of the stack being clobbered if the stack is actually use. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Thu Sep 7 7: 1: 0 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 07E3C37B423 for ; Thu, 7 Sep 2000 07:00:58 -0700 (PDT) Received: (from mwlucas@localhost) by blackhelicopters.org (8.9.3/8.9.3) id KAA27056 for emulation@freebsd.org; Thu, 7 Sep 2000 10:00:57 -0400 (EDT) (envelope-from mwlucas) From: Michael Lucas Message-Id: <200009071400.KAA27056@blackhelicopters.org> Subject: when "kldload linux" = "halt" To: emulation@freebsd.org Date: Thu, 7 Sep 2000 10:00:57 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I have something I'm not sure is a feature, a bug, or ignorance. It might be interesting to someone, or you might tell me I'm an idiot. I have a hard drive partitioned with a 2gig Linux install and a 6gig FreeBSD install. Rather than suck up even more space with /compat/linux, I thought I'd try to mount the Linux partition there. Other people reported that they've done similar things. First of all, I have /usr/compat/linux mounted ro, as the archives suggest bad things can happen to that partition otherwise. It mounts just fine, but when I type "kldload linux" the system stops. I get the "waiting for bufdaemon to stop" message just as if I'd rebooted the system. No panic, no warning, no kernel messages, nothing. It doesn't unmount the file systems, for all intents and purposes acting like "halt -q". Fortunately it reboots fine, auto-fscking itself. The system is current, as of last night just before the SMP patchset. The Linux partition is RedHat 6.2. Any thoughts? Places to look? Things that people would like me to check? Pointy hats you'd like me to wear? Thanks, Michael -- Michael Lucas mwlucas@blackhelicopters.org http://www.blackhelicopters.org/~mwlucas/ Big Scary Daemons: http://www.oreillynet.com/pub/q/Big_Scary_Daemons To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Thu Sep 7 7:50:35 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from blount.mail.mindspring.net (blount.mail.mindspring.net [207.69.200.226]) by hub.freebsd.org (Postfix) with ESMTP id BCD1B37B423 for ; Thu, 7 Sep 2000 07:50:30 -0700 (PDT) Received: from vtpr5 (user-33qtkdn.dialup.mindspring.com [199.174.209.183]) by blount.mail.mindspring.net (8.9.3/8.8.5) with SMTP id KAA00574; Thu, 7 Sep 2000 10:49:52 -0400 (EDT) Message-ID: <001201c018da$efa9e580$f5c9aec7@vt.ny.us> From: "Vladimir Silyaev" To: "Michael Harnois" Cc: "Brian Beattie" , References: <000501c017a3$b1995ce0$e40ffea9@vt.ny.us><86lmx6yyzq.fsf@mharnois.workgroup.net><000501c0180c$a0431940$e40ffea9@vt.ny.us><86zolly2a2.fsf@mharnois.workgroup.net><000c01c01875$dfca6f00$f5c9aec7@vt.ny.us> <868zt4lxow.fsf@mharnois.workgroup.net> Subject: Re: vmware2 networking question Date: Thu, 7 Sep 2000 07:50:13 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I think that in you case you will be have the same output from syslog even with nonactive vmnet. And the second point when you are have a bridging better to have IP address assigned only at one adapter. But again that problems doesn't have any relation to VMware. Regards, Vladimir ----- Original Message ----- From: Michael Harnois To: Vladimir Silyaev Cc: Brian Beattie ; Sent: Wednesday, September 06, 2000 7:53 PM Subject: Re: vmware2 networking question > On Wed, 6 Sep 2000 19:46:45 -0700, "Vladimir Silyaev" said: > > > Could you describe [hardware] configuration in which vmware > > guest works without enabled bridiging, and doesn't work at all > > with enabled bridged. > > dc0: flags=8943 mtu 1500 > inet 24.14.126.45 netmask 0xffffff00 broadcast 24.14.126.255 > ether 00:a0:cc:3d:00:ae > media: autoselect (10baseT/UTP) status: active > supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP none > dc1: flags=8943 mtu 1500 > inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255 > ether 00:20:78:04:35:83 > media: autoselect (100baseTX) status: active > supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP none > lo0: flags=8049 mtu 16384 > inet 127.0.0.1 netmask 0xff000000 > ppp0: flags=8010 mtu 1500 > faith0: flags=8000 mtu 1500 > gif0: flags=8010 mtu 1280 > gif1: flags=8010 mtu 1280 > gif2: flags=8010 mtu 1280 > gif3: flags=8010 mtu 1280 > vmnet1: flags=8943 mtu 1500 > inet 192.168.254.1 netmask 0xffffff00 broadcast 192.168.254.255 > ether 00:bd:4d:05:00:01 > > with bridging enabled, the syslog produces multiple entries like > > -- loop (0) 00.10.a4.f4.a5.73 to dc0 from dc1 (active) > -- loop (0) 00.10.a4.f4.a5.73 to dc0 from dc1 (active) > -- loop (0) 00.10.a4.f4.a5.73 to dc0 from dc1 (active) > -- loop (0) 00.10.a4.f4.a5.73 to dc0 from dc1 (active) > -- loop (0) 00.40.d0.0e.75.a2 to dc0 from dc1 (active) > -- loop (1) 00.40.d0.0e.75.a2 to dc1 from dc0 (active) > -- loop (0) 00.40.d0.0e.75.a2 to dc0 from dc1 (active) > -- loop (0) 00.40.d0.0e.75.a2 to dc1 from dc0 (active) > -- loop (0) 00.40.d0.0e.75.a2 to dc0 from dc1 (active) > -- loop (0) 00.10.a4.f4.a5.73 to dc0 from dc1 (active) > -- loop (1) 00.10.a4.f4.a5.73 to dc1 from dc0 (active) > -- loop (0) 00.10.a4.f4.a5.73 to dc0 from dc1 (active) > -- loop (0) 00.40.d0.0e.75.a2 to dc0 from dc1 (active) > -- loop (0) 00.40.d0.0e.75.a2 to dc0 from dc1 (active) > -- loop (0) 00.10.a4.f4.a5.73 to dc0 from dc1 (active) > -- loop (0) 00.10.a4.f4.a5.73 to dc0 from dc1 (active) > -- loop (0) 00.10.a4.f4.a5.73 to dc0 from dc1 (active) > -- loop (0) 00.40.d0.0e.75.a2 to dc0 from dc1 (active) > -- loop (1) 00.40.d0.0e.75.a2 to dc1 from dc0 (active) > > These messages cease with bridging disabled. > > > I did a testing with 3COM card with xl driver. It works without > > any problems. > > Then perhaps there is something in your software configuration which > has not been explained to the rest of us. > > -- > Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA > mdharnois@home.com aa0bt@aa0bt.ampr.org > Paranoids are people, too; they have their own problems. > It's easy to criticize, but if everybody hated you, > you'd be paranoid too. -- D. J. Hicks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Thu Sep 7 8: 7:30 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from c1030098-a.wtrlo1.ia.home.com (c1030098-a.wtrlo1.ia.home.com [24.14.126.45]) by hub.freebsd.org (Postfix) with ESMTP id 48B6837B422 for ; Thu, 7 Sep 2000 08:07:26 -0700 (PDT) Received: (from mdharnois@localhost) by c1030098-a.wtrlo1.ia.home.com (8.11.0/8.11.0) id e87F7EI38792; Thu, 7 Sep 2000 10:07:14 -0500 (CDT) (envelope-from mdharnois@home.com) X-Authentication-Warning: mharnois.workgroup.net: mdharnois set sender to mdharnois@home.com using -f To: "Vladimir Silyaev" Cc: "Brian Beattie" , Subject: Re: vmware2 networking question References: <000501c017a3$b1995ce0$e40ffea9@vt.ny.us> <86lmx6yyzq.fsf@mharnois.workgroup.net> <000501c0180c$a0431940$e40ffea9@vt.ny.us> <86zolly2a2.fsf@mharnois.workgroup.net> <000c01c01875$dfca6f00$f5c9aec7@vt.ny.us> <868zt4lxow.fsf@mharnois.workgroup.net> <001201c018da$efa9e580$f5c9aec7@vt.ny.us> From: Michael Harnois Date: 07 Sep 2000 10:07:08 -0500 In-Reply-To: "Vladimir Silyaev"'s message of "Thu, 7 Sep 2000 07:50:13 -0700" Message-ID: <86em2ws0kj.fsf@mharnois.workgroup.net> Lines: 108 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.2 (Nike) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Yes, but you asked for a situation where vmware does not work with bridging enabled and does work when it's not. This is such a situation, and that *does* have to do with vmware. Furthermore, you can't possibly have an ip address assigned only at one adapter. That negates the entire point of having two ethernet cards, which is, in turn, the point of bridging. Numerous authors on the list have pointed out the problem with your use of bridging, not just me. Just continuing to point the finger elsewhere does the community no good. On Thu, 7 Sep 2000 07:50:13 -0700, "Vladimir Silyaev" said: > I think that in you case you will be have the same output from > syslog even with nonactive vmnet. And the second point when you > are have a bridging better to have IP address assigned only at > one adapter. But again that problems doesn't have any relation > to VMware. > Regards, Vladimir > ----- Original Message ----- From: Michael Harnois > To: Vladimir Silyaev > Cc: Brian Beattie > ; Sent: > Wednesday, September 06, 2000 7:53 PM Subject: Re: vmware2 > networking question >> On Wed, 6 Sep 2000 19:46:45 -0700, "Vladimir Silyaev" > said: >> > Could you describe [hardware] configuration in which vmware > >> guest works without enabled bridiging, and doesn't work at all >> > with enabled bridged. >> >> dc0: flags=8943 >> mtu 1500 inet 24.14.126.45 netmask 0xffffff00 broadcast >> 24.14.126.255 ether 00:a0:cc:3d:00:ae media: autoselect >> (10baseT/UTP) status: active supported media: autoselect >> 100baseTX 100baseTX > 10baseT/UTP 10baseT/UTP none >> dc1: flags=8943 >> mtu 1500 inet 192.168.0.1 netmask 0xffffff00 broadcast >> 192.168.0.255 ether 00:20:78:04:35:83 media: autoselect >> (100baseTX) status: active supported media: autoselect >> 100baseTX 100baseTX > 10baseT/UTP 10baseT/UTP none >> lo0: flags=8049 mtu 16384 inet >> 127.0.0.1 netmask 0xff000000 ppp0: >> flags=8010 mtu 1500 faith0: >> flags=8000 mtu 1500 gif0: >> flags=8010 mtu 1280 gif1: >> flags=8010 mtu 1280 gif2: >> flags=8010 mtu 1280 gif3: >> flags=8010 mtu 1280 vmnet1: >> flags=8943 mtu > 1500 >> inet 192.168.254.1 netmask 0xffffff00 broadcast 192.168.254.255 >> ether 00:bd:4d:05:00:01 >> >> with bridging enabled, the syslog produces multiple entries >> like >> >> -- loop (0) 00.10.a4.f4.a5.73 to dc0 from dc1 (active) -- loop >> (0) 00.10.a4.f4.a5.73 to dc0 from dc1 (active) -- loop (0) >> 00.10.a4.f4.a5.73 to dc0 from dc1 (active) -- loop (0) >> 00.10.a4.f4.a5.73 to dc0 from dc1 (active) -- loop (0) >> 00.40.d0.0e.75.a2 to dc0 from dc1 (active) -- loop (1) >> 00.40.d0.0e.75.a2 to dc1 from dc0 (active) -- loop (0) >> 00.40.d0.0e.75.a2 to dc0 from dc1 (active) -- loop (0) >> 00.40.d0.0e.75.a2 to dc1 from dc0 (active) -- loop (0) >> 00.40.d0.0e.75.a2 to dc0 from dc1 (active) -- loop (0) >> 00.10.a4.f4.a5.73 to dc0 from dc1 (active) -- loop (1) >> 00.10.a4.f4.a5.73 to dc1 from dc0 (active) -- loop (0) >> 00.10.a4.f4.a5.73 to dc0 from dc1 (active) -- loop (0) >> 00.40.d0.0e.75.a2 to dc0 from dc1 (active) -- loop (0) >> 00.40.d0.0e.75.a2 to dc0 from dc1 (active) -- loop (0) >> 00.10.a4.f4.a5.73 to dc0 from dc1 (active) -- loop (0) >> 00.10.a4.f4.a5.73 to dc0 from dc1 (active) -- loop (0) >> 00.10.a4.f4.a5.73 to dc0 from dc1 (active) -- loop (0) >> 00.40.d0.0e.75.a2 to dc0 from dc1 (active) -- loop (1) >> 00.40.d0.0e.75.a2 to dc1 from dc0 (active) >> >> These messages cease with bridging disabled. >> >> > I did a testing with 3COM card with xl driver. It works >> without > any problems. >> >> Then perhaps there is something in your software configuration >> which has not been explained to the rest of us. >> >> -- Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA >> mdharnois@home.com aa0bt@aa0bt.ampr.org Paranoids are people, >> too; they have their own problems. It's easy to criticize, but >> if everybody hated you, you'd be paranoid too. -- D. J. Hicks > To Unsubscribe: send mail to majordomo@FreeBSD.org with > "unsubscribe freebsd-emulation" in the body of the message -- Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA mdharnois@home.com aa0bt@aa0bt.ampr.org When the stomach is satisfied, and lust is spent, man spares a little time for God. -- Will Durant To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Thu Sep 7 8:37:14 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id A002137B422 for ; Thu, 7 Sep 2000 08:37:09 -0700 (PDT) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.123.131]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id JAA18238; Thu, 7 Sep 2000 09:33:58 -0600 (MDT) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id JAA05353; Thu, 7 Sep 2000 09:33:56 -0600 (MDT) (envelope-from nate) Date: Thu, 7 Sep 2000 09:33:56 -0600 (MDT) Message-Id: <200009071533.JAA05353@nomad.yogotech.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Bruce Evans Cc: Andrew Gallatin , Nate Williams , marcel@cup.hp.com, freebsd-emulation@FreeBSD.ORG Subject: Re: IBM JDK fails due to lack of SA_SIGINFO support In-Reply-To: References: <14774.29608.353021.688597@grasshopper.cs.duke.edu> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > Umm, I'd believe this except that someone sent me a patch (which I've > > > forwarded to Marcel) that fixes this and is related to the sigalstack > > > error above. At least the author of the patch claims that the IBM JDK > > > now runs successfully on his box, running some version of FreeBSD. :) > > > The change you're referring to isn't all that much different that what > > I'd been doing previously (setting MINSIGSTKSZ to 2048 in sys/signal.h). > > It is quite different. You change is not incorrect, but the committed > versions of Nate's patch results in memory beyond the end of the stack > being clobbered if the stack is actually use. Ouch. Why is that? I would have thought that the signalstack's were 'essentially' unallocated space, so by bumping up the size, we were giving the application more space to work with, not less. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Thu Sep 7 9: 9:27 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from mother.ludd.luth.se (mother.ludd.luth.se [130.240.16.3]) by hub.freebsd.org (Postfix) with ESMTP id 3668037B422 for ; Thu, 7 Sep 2000 09:09:25 -0700 (PDT) Received: from speedy.ludd.luth.se (speedy.ludd.luth.se [130.240.16.164]) by mother.ludd.luth.se (8.9.3+Sun/8.9.3) with ESMTP id SAA07463; Thu, 7 Sep 2000 18:09:19 +0200 (MEST) Message-Id: <200009071609.SAA07463@mother.ludd.luth.se> X-Mailer: exmh version 2.1.1 10/15/1999 To: Michael Harnois Cc: "Vladimir Silyaev" , emulation@FreeBSD.ORG Subject: Re: vmware2 networking question In-Reply-To: Message from Michael Harnois of "07 Sep 2000 10:07:08 CDT." <86em2ws0kj.fsf@mharnois.workgroup.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 07 Sep 2000 18:09:19 +0200 From: Mattias Pantzare Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Yes, but you asked for a situation where vmware does not work with > bridging enabled and does work when it's not. This is such a > situation, and that *does* have to do with vmware. > > Furthermore, you can't possibly have an ip address assigned only at > one adapter. That negates the entire point of having two ethernet > cards, which is, in turn, the point of bridging. No, you do not have to have an ip adressed assigned to both adapters if you are doing bridging. You do not need to assign any ip address at all to do bridging. A normal ethernet switch is doing bridging. The problem is simply that the vmware port enables bridging among all your adapters, even if you do not use bridging normaly. That is very wrong. The vmware port shoud ask the user for the adapter that is to be used for vmware and enable bridging only between that adapter and the vmware-adapter. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Thu Sep 7 14:46:53 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id 94DBE37B43E for ; Thu, 7 Sep 2000 14:46:45 -0700 (PDT) Received: (qmail 16250 invoked from network); 7 Sep 2000 21:46:41 -0000 Received: from unknown (HELO bde.zeta.org.au) (203.2.228.102) by gidora.zeta.org.au with SMTP; 7 Sep 2000 21:46:41 -0000 Date: Fri, 8 Sep 2000 08:46:36 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Nate Williams Cc: Andrew Gallatin , marcel@cup.hp.com, freebsd-emulation@FreeBSD.ORG Subject: Re: IBM JDK fails due to lack of SA_SIGINFO support In-Reply-To: <200009071533.JAA05353@nomad.yogotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 7 Sep 2000, Nate Williams wrote: > > > The change you're referring to isn't all that much different that what > > > I'd been doing previously (setting MINSIGSTKSZ to 2048 in sys/signal.h). > > > > It is quite different. You change is not incorrect, but the committed > > versions of Nate's patch results in memory beyond the end of the stack > > being clobbered if the stack is actually use. > > Ouch. Why is that? I would have thought that the signalstack's were > 'essentially' unallocated space, so by bumping up the size, we were > giving the application more space to work with, not less. Alternative signal stacks are allocated by the application. Bumping the size in the kernel corresponds to using unallocated space beyond the end of the space allocated by the application. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Thu Sep 7 14:51:35 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 179DC37B423 for ; Thu, 7 Sep 2000 14:51:33 -0700 (PDT) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id RAA19994; Thu, 7 Sep 2000 17:43:44 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.0/8.9.1) id e87LhiK28036; Thu, 7 Sep 2000 17:43:44 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 7 Sep 2000 17:43:44 -0400 (EDT) To: freebsd-emulation@FreeBSD.ORG Cc: Martin Cracauer , Nate Williams , marcel@cup.hp.com Subject: Re: IBM JDK fails due to lack of SA_SIGINFO support In-Reply-To: <14774.42905.390753.70408@grasshopper.cs.duke.edu> References: <14773.43466.744621.411519@grasshopper.cs.duke.edu> <200009060447.WAA23183@nomad.yogotech.com> <20000906083957.A5530@cons.org> <14774.42905.390753.70408@grasshopper.cs.duke.edu> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14776.2365.362350.29260@grasshopper.cs.duke.edu> Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Andrew Gallatin writes: > > > > I'm getting closer. I'd really appreciate some help from x86 > people.... I think its coming down to my lack of knowledge about x86 > assembly :-( I'm getting even closer. My toy program now works & I can get the JDK to run long enough to spit out a version number: <5:27pm>dragonfly/gallatin:IBMJava2-13>/compat/linux/bin/sh bin/java -version java version "1.3.0" Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0) Classic VM (build 1.3.0, J2RE 1.3.0 IBM build cx130-20000815 (JIT enabled: jitc)) (woo-hoo!) To get this far, I corrected my implementation of linux_rt_sendsig, implemented new sigtramp code for the "rt" (eg, SA_SIGINFO) handlers and then implemented a linux_rt_sigreturn(). So much for the good news.. When I actually try to run an applet, the application SEGV's on a stack address. Given that the address it faults on is almost reasonable, I'm wondering if there's something funky going on wrt our "MAP_GROWSDOWN" mmap code. Latest patches at http://www.cs.duke.edu/~gallatin/linux_sa_siginfo/diff Again, I could really use some help here. Thanks, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Thu Sep 7 15:12:11 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id B175437B42C for ; Thu, 7 Sep 2000 15:12:08 -0700 (PDT) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.123.131]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id QAA25143; Thu, 7 Sep 2000 16:09:30 -0600 (MDT) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id QAA06661; Thu, 7 Sep 2000 16:09:28 -0600 (MDT) (envelope-from nate) Date: Thu, 7 Sep 2000 16:09:28 -0600 (MDT) Message-Id: <200009072209.QAA06661@nomad.yogotech.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Bruce Evans Cc: Nate Williams , Andrew Gallatin , marcel@cup.hp.com, freebsd-emulation@FreeBSD.ORG Subject: Re: IBM JDK fails due to lack of SA_SIGINFO support In-Reply-To: References: <200009071533.JAA05353@nomad.yogotech.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > > The change you're referring to isn't all that much different that what > > > > I'd been doing previously (setting MINSIGSTKSZ to 2048 in sys/signal.h). > > > > > > It is quite different. You change is not incorrect, but the committed > > > versions of Nate's patch results in memory beyond the end of the stack > > > being clobbered if the stack is actually use. > > > > Ouch. Why is that? I would have thought that the signalstack's were > > 'essentially' unallocated space, so by bumping up the size, we were > > giving the application more space to work with, not less. > > Alternative signal stacks are allocated by the application. And the size is allocated inside the application's space? I thought the size was allocated inside the kernel, hence the need for the system call. > Bumping the size in the kernel corresponds to using unallocated space > beyond the end of the space allocated by the application. So how would you propose fixing this? In Linux, the minimum size is << FreeBSD's minimum size. Either we decrease FreeBSD's minimum size or we abort the request, causing these applications to fail. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Thu Sep 7 15:21:30 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 4AA7D37B422 for ; Thu, 7 Sep 2000 15:21:28 -0700 (PDT) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id SAA20656; Thu, 7 Sep 2000 18:13:50 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.0/8.9.1) id e87MDoA28085; Thu, 7 Sep 2000 18:13:50 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 7 Sep 2000 18:13:50 -0400 (EDT) To: nate@yogotech.com (Nate Williams) Cc: Bruce Evans , marcel@cup.hp.com, freebsd-emulation@FreeBSD.ORG Subject: Re: IBM JDK fails due to lack of SA_SIGINFO support In-Reply-To: <200009072209.QAA06661@nomad.yogotech.com> References: <200009071533.JAA05353@nomad.yogotech.com> <200009072209.QAA06661@nomad.yogotech.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14776.4695.816482.749092@grasshopper.cs.duke.edu> Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Nate Williams writes: > > And the size is allocated inside the application's space? I thought the > size was allocated inside the kernel, hence the need for the system > call. The system call sets a flag and sets the sigstat stack pointer in the process struct. Look at the code for "allocating" space for the signal handler context in the various sendsig() functions. > > Bumping the size in the kernel corresponds to using unallocated space > > beyond the end of the space allocated by the application. > > So how would you propose fixing this? In Linux, the minimum size is << > FreeBSD's minimum size. Either we decrease FreeBSD's minimum size or we > abort the request, causing these applications to fail. I'd suggest reducing FreeBSD's minimum size. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Thu Sep 7 15:36: 6 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id 37E3C37B42C for ; Thu, 7 Sep 2000 15:36:03 -0700 (PDT) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.123.131]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id QAA25573; Thu, 7 Sep 2000 16:33:25 -0600 (MDT) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id QAA06837; Thu, 7 Sep 2000 16:33:24 -0600 (MDT) (envelope-from nate) Date: Thu, 7 Sep 2000 16:33:24 -0600 (MDT) Message-Id: <200009072233.QAA06837@nomad.yogotech.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Andrew Gallatin Cc: nate@yogotech.com (Nate Williams), Bruce Evans , marcel@cup.hp.com, freebsd-emulation@FreeBSD.ORG Subject: Re: IBM JDK fails due to lack of SA_SIGINFO support In-Reply-To: <14776.4695.816482.749092@grasshopper.cs.duke.edu> References: <200009071533.JAA05353@nomad.yogotech.com> <200009072209.QAA06661@nomad.yogotech.com> <14776.4695.816482.749092@grasshopper.cs.duke.edu> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > And the size is allocated inside the application's space? I thought the > > size was allocated inside the kernel, hence the need for the system > > call. > > The system call sets a flag and sets the sigstat stack pointer in the > process struct. Look at the code for "allocating" space for the > signal handler context in the various sendsig() functions. > > > > Bumping the size in the kernel corresponds to using unallocated space > > > beyond the end of the space allocated by the application. > > > > So how would you propose fixing this? In Linux, the minimum size is << > > FreeBSD's minimum size. Either we decrease FreeBSD's minimum size or we > > abort the request, causing these applications to fail. > > I'd suggest reducing FreeBSD's minimum size. Is that acceptable (Bruce)? This is what Marcel suggested, and I argued against, but in the end he was right, but I'm not aware of what effect this would have on the system. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Thu Sep 7 16:21: 2 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from mail.imp.ch (mail.imp.ch [157.161.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 946A837B443; Thu, 7 Sep 2000 16:20:57 -0700 (PDT) Received: from levais.imp.ch (levais.imp.ch [157.161.4.66]) by mail.imp.ch (8.9.3/8.9.3b) with SMTP id BAA34047; Fri, 8 Sep 2000 01:20:51 +0200 (CEST) Date: Fri, 8 Sep 2000 01:24:39 +0200 (CEST) From: Martin Blapp To: ports@freebsd.org Cc: freebsd-emulation@freebsd.org Subject: Staroffice 5.2 and network - broken ? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi all, As the maintainer of staroffice5.2 for FreeBSD I've seen that everything network-related like staroffice-web, mail, news is not working under the linux ABI. It is working with the . In version 5.1 everything worked as is should. Anyone does know something about this ? Maybe Marcel ? Martin Martin Blapp, mb@imp.ch ------------------------------------------------ Improware AG, UNIX solution and service provider Zurlindenstrasse 29, 4133 Pratteln, Switzerland Phone: +41 79 370 26 05, Fax: +41 61 826 93 01 ------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Thu Sep 7 17:50:20 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.242]) by hub.freebsd.org (Postfix) with ESMTP id 27B8F37B422 for ; Thu, 7 Sep 2000 17:50:19 -0700 (PDT) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel1.hp.com (Postfix) with ESMTP id CE39FC42; Thu, 7 Sep 2000 17:50:18 -0700 (PDT) Received: from cup.hp.com (p1000180.nsr.hp.com [15.109.0.180]) by adlmail.cup.hp.com (8.9.3 (PHNE_18546)/8.9.3 SMKit7.02) with ESMTP id RAA21498; Thu, 7 Sep 2000 17:50:18 -0700 (PDT) Message-ID: <39B837C9.F8660137@cup.hp.com> Date: Thu, 07 Sep 2000 17:50:17 -0700 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Nate Williams Cc: Andrew Gallatin , Bruce Evans , freebsd-emulation@FreeBSD.ORG Subject: Re: MINSIGSTKSZ [was Re: IBM JDK fails due to lack of SA_SIGINFO support] References: <200009071533.JAA05353@nomad.yogotech.com> <200009072209.QAA06661@nomad.yogotech.com> <14776.4695.816482.749092@grasshopper.cs.duke.edu> <200009072233.QAA06837@nomad.yogotech.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Nate Williams wrote: > > > I'd suggest reducing FreeBSD's minimum size. > > Is that acceptable (Bruce)? This is what Marcel suggested, and I argued > against, but in the end he was right, but I'm not aware of what effect > this would have on the system. As long as MINSIGSTKSZ is larger than what the kernel actually needs to implement the feature, we are fine. I want to look at how large this is for different OSes that we are "close" with to determine an acceptable value. Surely we need 2K as a high limit for Linux compatibility, but if another OS (say SVR4) has 1K, we need to take that into account. Also, I don't want to drive this value too low -- we can't raise it without breaking backward compatibility. -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Thu Sep 7 18:16:25 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 860C437B422 for ; Thu, 7 Sep 2000 18:16:23 -0700 (PDT) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id VAA23739; Thu, 7 Sep 2000 21:16:11 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.0/8.9.1) id e881GBr30904; Thu, 7 Sep 2000 21:16:11 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 7 Sep 2000 21:16:11 -0400 (EDT) To: Marcel Moolenaar Cc: Nate Williams , Bruce Evans , freebsd-emulation@FreeBSD.ORG Subject: Re: MINSIGSTKSZ [was Re: IBM JDK fails due to lack of SA_SIGINFO support] In-Reply-To: <39B837C9.F8660137@cup.hp.com> References: <200009071533.JAA05353@nomad.yogotech.com> <200009072209.QAA06661@nomad.yogotech.com> <14776.4695.816482.749092@grasshopper.cs.duke.edu> <200009072233.QAA06837@nomad.yogotech.com> <39B837C9.F8660137@cup.hp.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14776.15770.446766.141186@grasshopper.cs.duke.edu> Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Marcel Moolenaar writes: > As long as MINSIGSTKSZ is larger than what the kernel actually needs to > implement the feature, we are fine. I want to look at how large this is > for different OSes that we are "close" with to determine an acceptable > value. Surely we need 2K as a high limit for Linux compatibility, but if > another OS (say SVR4) has 1K, we need to take that into account. Also, I > don't want to drive this value too low -- we can't raise it without > breaking backward compatibility. FWIW, Tru64 (aka OSF/1)'s MINSIGSTKSZ is 4k, as is Linux/alpha's Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Thu Sep 7 18:24:38 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 81A5437B422 for ; Thu, 7 Sep 2000 18:24:35 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id MAA27344; Fri, 8 Sep 2000 12:14:36 +1100 Date: Fri, 8 Sep 2000 12:14:32 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Nate Williams Cc: Andrew Gallatin , marcel@cup.hp.com, freebsd-emulation@FreeBSD.ORG Subject: Re: IBM JDK fails due to lack of SA_SIGINFO support In-Reply-To: <200009072209.QAA06661@nomad.yogotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 7 Sep 2000, Nate Williams wrote: > > Alternative signal stacks are allocated by the application. > > And the size is allocated inside the application's space? I thought the Yes. > size was allocated inside the kernel, hence the need for the system > call. It couldn't be. The kernel would have no idea where to allocate user stack(s). > > Bumping the size in the kernel corresponds to using unallocated space > > beyond the end of the space allocated by the application. > > So how would you propose fixing this? In Linux, the minimum size is << > FreeBSD's minimum size. Either we decrease FreeBSD's minimum size or we > abort the request, causing these applications to fail. Actually implement MINSIGSTKSZ as documented in the man page. It should be sizeof(struct sigframe), where struct sigframe is the relevant frame (which depends on more than the machine; for i386's we currently have 2 native frames and 1 Linux frame and are missing the Linux SA_SIGINFO frame). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Thu Sep 7 19:27:49 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from maynard.mail.mindspring.net (maynard.mail.mindspring.net [207.69.200.243]) by hub.freebsd.org (Postfix) with ESMTP id 4B94A37B424 for ; Thu, 7 Sep 2000 19:27:47 -0700 (PDT) Received: from vtpr5 (user-33qti7o.dialup.mindspring.com [199.174.200.248]) by maynard.mail.mindspring.net (8.9.3/8.8.5) with SMTP id WAA06605; Thu, 7 Sep 2000 22:27:42 -0400 (EDT) Message-ID: <001b01c0193c$6be3d780$e40ffea9@vt.ny.us> From: "Vladimir Silyaev" To: "Michael Harnois" , "Mattias Pantzare" Cc: References: <200009071609.SAA07463@mother.ludd.luth.se> Subject: Re: vmware2 networking question Date: Thu, 7 Sep 2000 19:28:04 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It's not so hard to get a bridging bettween only two ethernet adapters - you have just to specify so called 'bridge groups'. See bridge(4) for more info. If you could test how FreeBSD bridging works in such configuration it'll be just great. ---- Vladimir ----- Original Message ----- From: Mattias Pantzare To: Michael Harnois Cc: Vladimir Silyaev ; Sent: Thursday, September 07, 2000 9:09 AM Subject: Re: vmware2 networking question > > Yes, but you asked for a situation where vmware does not work with > > bridging enabled and does work when it's not. This is such a > > situation, and that *does* have to do with vmware. > > > > Furthermore, you can't possibly have an ip address assigned only at > > one adapter. That negates the entire point of having two ethernet > > cards, which is, in turn, the point of bridging. > > No, you do not have to have an ip adressed assigned to both adapters if you are > doing bridging. You do not need to assign any ip address at all to do > bridging. A normal ethernet switch is doing bridging. > > The problem is simply that the vmware port enables bridging among all your > adapters, even if you do not use bridging normaly. That is very wrong. > > The vmware port shoud ask the user for the adapter that is to be used for > vmware and enable bridging only between that adapter and the vmware-adapter. > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Thu Sep 7 19:57:47 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from c1030098-a.wtrlo1.ia.home.com (c1030098-a.wtrlo1.ia.home.com [24.14.126.45]) by hub.freebsd.org (Postfix) with ESMTP id 7B39237B42C for ; Thu, 7 Sep 2000 19:57:45 -0700 (PDT) Received: (from mdharnois@localhost) by c1030098-a.wtrlo1.ia.home.com (8.11.0/8.11.0) id e882vid00351; Thu, 7 Sep 2000 21:57:44 -0500 (CDT) (envelope-from mdharnois@home.com) X-Authentication-Warning: mharnois.workgroup.net: mdharnois set sender to mdharnois@home.com using -f To: "Vladimir Silyaev" Cc: "Mattias Pantzare" , Subject: Re: vmware2 networking question References: <200009071609.SAA07463@mother.ludd.luth.se> <001b01c0193c$6be3d780$e40ffea9@vt.ny.us> From: Michael Harnois Date: 07 Sep 2000 21:57:43 -0500 In-Reply-To: "Vladimir Silyaev"'s message of "Thu, 7 Sep 2000 19:28:04 -0700" Message-ID: <86bsxzoajc.fsf@mharnois.workgroup.net> Lines: 13 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.2 (Nike) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 7 Sep 2000 19:28:04 -0700, "Vladimir Silyaev" said: > It's not so hard to get a bridging bettween only two ethernet > adapters - you have just to specify so called 'bridge groups'. > See bridge(4) for more info. I am using current, and that manpage has no reference to groups. -- Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA mdharnois@home.com aa0bt@aa0bt.ampr.org CYNIC, n. A blackguard whose faulty vision sees things as they are, not as they ought to be. -- Ambrose Bierce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Fri Sep 8 6:25:27 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (Postfix) with ESMTP id E232837B424; Fri, 8 Sep 2000 06:25:21 -0700 (PDT) Received: from v-ger.we.lc.ehu.es (v-ger [158.227.6.179]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id PAA15135; Fri, 8 Sep 2000 15:25:15 +0200 (MET DST) Received: from we.lc.ehu.es (localhost [127.0.0.1]) by v-ger.we.lc.ehu.es (8.9.3/8.9.3) with ESMTP id PAA04635; Fri, 8 Sep 2000 15:24:11 +0200 (CEST) (envelope-from jose@we.lc.ehu.es) Message-ID: <39B8E87A.73A1187@we.lc.ehu.es> Date: Fri, 08 Sep 2000 15:24:10 +0200 From: "Jose M. Alcaide" Organization: Universidad del Pais Vasco - Dpto. de Electricidad y Electronica X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: es-ES, es, en-US, en MIME-Version: 1.0 To: Martin Blapp Cc: ports@FreeBSD.ORG, freebsd-emulation@FreeBSD.ORG Subject: Re: Staroffice 5.2 and network - broken ? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Martin Blapp wrote: > > As the maintainer of staroffice5.2 for FreeBSD I've seen that everything > network-related like staroffice-web, mail, news is not working under > the linux ABI. It is working with the . In version 5.1 everything worked > as is should. > > Anyone does know something about this ? Maybe Marcel ? > Same here. But a "netstat -f inet" shows that there is a TCP connection established just after trying to open an URL. And Netscape for Linux works fine. What do you mean with "it is working with the ."? I tried full qualified host names to no avail. -- JMA ****** Jose M. Alcaide // jose@we.lc.ehu.es // jmas@FreeBSD.org ****** ** "Beware of Programmers who carry screwdrivers" -- Leonard Brandwein ** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Fri Sep 8 6:30:23 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from mail.imp.ch (mail.imp.ch [157.161.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 8C62637B42C; Fri, 8 Sep 2000 06:30:15 -0700 (PDT) Received: from levais.imp.ch (levais.imp.ch [157.161.4.66]) by mail.imp.ch (8.9.3/8.9.3b) with SMTP id PAA62008; Fri, 8 Sep 2000 15:30:09 +0200 (CEST) Date: Fri, 8 Sep 2000 15:33:57 +0200 (CEST) From: Martin Blapp To: "Jose M. Alcaide" Cc: ports@FreeBSD.ORG, freebsd-emulation@FreeBSD.ORG Subject: Re: Staroffice 5.2 and network - broken ? In-Reply-To: <39B8E87A.73A1187@we.lc.ehu.es> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, It works with native Linux I ment. I also discovered that it works with localhost. If you install a squid-proxy on localhost, web-pages are working, but not the rest. A very strange problem ... Martin Martin Blapp, mb@imp.ch ------------------------------------------------ Improware AG, UNIX solution and service provider Zurlindenstrasse 29, 4133 Pratteln, Switzerland Phone: +41 79 370 26 05, Fax: +41 61 826 93 01 ------------------------------------------------ On Fri, 8 Sep 2000, Jose M. Alcaide wrote: > Martin Blapp wrote: > > > > As the maintainer of staroffice5.2 for FreeBSD I've seen that everything > > network-related like staroffice-web, mail, news is not working under > > the linux ABI. It is working with the . In version 5.1 everything worked > > as is should. > > > > Anyone does know something about this ? Maybe Marcel ? > > > > Same here. But a "netstat -f inet" shows that there is a TCP connection > established just after trying to open an URL. And Netscape for Linux > works fine. What do you mean with "it is working with the ."? I tried > full qualified host names to no avail. > > -- JMA > ****** Jose M. Alcaide // jose@we.lc.ehu.es // jmas@FreeBSD.org ****** > ** "Beware of Programmers who carry screwdrivers" -- Leonard Brandwein ** > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Fri Sep 8 8: 8:19 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from smtp10.atl.mindspring.net (smtp10.atl.mindspring.net [207.69.200.246]) by hub.freebsd.org (Postfix) with ESMTP id 39C7B37B43E; Fri, 8 Sep 2000 08:08:15 -0700 (PDT) Received: from vtpr5 (user-33qticd.dialup.mindspring.com [199.174.201.141]) by smtp10.atl.mindspring.net (8.9.3/8.8.5) with SMTP id LAA02266; Fri, 8 Sep 2000 11:08:08 -0400 (EDT) Message-ID: <001401c019a6$a7e45b00$e40ffea9@vt.ny.us> From: "Vladimir Silyaev" To: "Michael Harnois" Cc: "Mattias Pantzare" , , References: <200009071609.SAA07463@mother.ludd.luth.se><001b01c0193c$6be3d780$e40ffea9@vt.ny.us> <86bsxzoajc.fsf@mharnois.workgroup.net> Subject: Re: vmware2 networking question Date: Fri, 8 Sep 2000 08:08:31 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hmm, strange. I'm pretty sure that I seen somewhere description about clusters on FreeBSD bridge. This is some points: - you have to set sysctl net.ether.bridge.bridge_cfg, with list of supported interfaces (a clue how to specify interfaces list you can get from state of the same sysctl after enabling bridge) - you can get futher information from /sys/net/bridge.c file - or contact Luigi Rizzo --- Vladimir ----- Original Message ----- From: Michael Harnois To: Vladimir Silyaev Cc: Mattias Pantzare ; Sent: Thursday, September 07, 2000 7:57 PM Subject: Re: vmware2 networking question > On Thu, 7 Sep 2000 19:28:04 -0700, "Vladimir Silyaev" said: > > > It's not so hard to get a bridging bettween only two ethernet > > adapters - you have just to specify so called 'bridge groups'. > > See bridge(4) for more info. > > I am using current, and that manpage has no reference to groups. > > -- > Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA > mdharnois@home.com aa0bt@aa0bt.ampr.org > CYNIC, n. A blackguard whose faulty vision sees things as they are, > not as they ought to be. -- Ambrose Bierce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Fri Sep 8 8:13:51 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from c1030098-a.wtrlo1.ia.home.com (c1030098-a.wtrlo1.ia.home.com [24.14.126.45]) by hub.freebsd.org (Postfix) with ESMTP id 2F82037B43F; Fri, 8 Sep 2000 08:13:46 -0700 (PDT) Received: (from mdharnois@localhost) by c1030098-a.wtrlo1.ia.home.com (8.11.0/8.11.0) id e88FDjA01153; Fri, 8 Sep 2000 10:13:45 -0500 (CDT) (envelope-from mdharnois@home.com) X-Authentication-Warning: mharnois.workgroup.net: mdharnois set sender to mdharnois@home.com using -f To: "Vladimir Silyaev" Cc: "Mattias Pantzare" , , Subject: Re: vmware2 networking question References: <200009071609.SAA07463@mother.ludd.luth.se> <001b01c0193c$6be3d780$e40ffea9@vt.ny.us> <86bsxzoajc.fsf@mharnois.workgroup.net> <001401c019a6$a7e45b00$e40ffea9@vt.ny.us> From: Michael Harnois Date: 08 Sep 2000 10:13:45 -0500 In-Reply-To: "Vladimir Silyaev"'s message of "Fri, 8 Sep 2000 08:08:31 -0700" Message-ID: <86hf7q532u.fsf@mharnois.workgroup.net> Lines: 16 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.2 (Nike) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 8 Sep 2000 08:08:31 -0700, "Vladimir Silyaev" said: > This is some points: - you have to set sysctl > net.ether.bridge.bridge_cfg, with list of supported interfaces > (a clue how to specify interfaces list you can get from state of > the same sysctl after enabling bridge) - you can get futher > information from /sys/net/bridge.c file - or contact Luigi Rizzo Yes, I figured out how to do it manually, as I mentioned several notes upstream. It still doesn't work with vmware, however. -- Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA mdharnois@home.com aa0bt@aa0bt.ampr.org "It's not what we don't know that hurts us, it's what we know for certain that just ain't so." -- Mark Twain To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Fri Sep 8 9:35: 7 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 69EB037B43E; Fri, 8 Sep 2000 09:35:02 -0700 (PDT) Received: from whistle.com (crab.whistle.com [207.76.205.112]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id JAA79560; Fri, 8 Sep 2000 09:23:13 -0700 (PDT) Received: (from ambrisko@localhost) by whistle.com (8.9.3/8.9.1) id JAA63625; Fri, 8 Sep 2000 09:22:59 -0700 (PDT) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200009081622.JAA63625@whistle.com> Subject: Re: vmware2 networking question In-Reply-To: <86hf7q532u.fsf@mharnois.workgroup.net> from Michael Harnois at "Sep 8, 2000 10:13:45 am" To: Michael Harnois Date: Fri, 8 Sep 2000 09:22:59 -0700 (PDT) Cc: Vladimir Silyaev , Mattias Pantzare , emulation@FreeBSD.ORG, net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Michael Harnois writes: | On Fri, 8 Sep 2000 08:08:31 -0700, "Vladimir Silyaev" said: | | > This is some points: - you have to set sysctl | > net.ether.bridge.bridge_cfg, with list of supported interfaces | > (a clue how to specify interfaces list you can get from state of | > the same sysctl after enabling bridge) - you can get futher | > information from /sys/net/bridge.c file - or contact Luigi Rizzo | | Yes, I figured out how to do it manually, as I mentioned several notes | upstream. It still doesn't work with vmware, however. BTW I ran into this problem with multiple ethernet devices. The clustering didn't work and it caused the machine to reboot etc. So I asked our resident netgraph expert if we could use netgraph to just physical wire the vmware interface to a hardware interface. He said we could but then the TCP/IP stack wouldn't see any traffic on the FreeBSD machine. I said that is exactly what I wanted. I only wanted to see vmware interface to see the traffic. Here is the script I put into /usr/local/etc/rc.d/vmware_help.sh Note that dc0 is the physical interface and vmnet0 is the vmware interface -------------------------------------------------------------- #!/bin/sh dd if=/compat/linux/dev/vmnet0 bs=1 count=0 > /dev/null kldstat -v | grep -w ng_ether -q || kldload ng_ether ifconfig dc0 up ifconfig vmnet0 up ngctl connect dc0: vmnet0: lower lower ngctl msg dc0: setautosrc 0 ngctl msg dc0: setpromisc 1 ngctl msg vmnet0: setautosrc 0 ngctl msg vmnet0: setpromisc 1 -------------------------------------------------------------- If you do this you can remove the bridge stuff from your kernel etc. I don't have bridge in my kernel and this works just fine. Infact in my test environment I have the dc0 interface connected to a router and some jail sessions running on the this same machine tied to other interfaces. When I telnet to the jail from the vmware session it goes out to the router and then the router routes it back into the interface connected to the jail. The jail does the same thing. If the TCP/IP stack was involved then the stack would have directly routed the traffic back into the jail without going through the external router. Also we did not configure any IP address on either dc0 or vmnet0. This is on 4.1-stable, here are my dev entries: m25% ls -l /compat/linux/dev/vmnet* crw-rw-rw- 1 root wheel 149, 0x00010000 Aug 25 15:51 /compat/linux/dev/vmnet0 crw-rw-rw- 1 root wheel 149, 0x00010001 Aug 24 08:47 /compat/linux/dev/vmnet1 m25% Also I haven't had to deal with reboots etc. This may not met everyones needs but it works great for me. There is work under way for a real netgraph bridging node so it could also plug into the hosts TCP/IP stack etc. Doug A. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message