From owner-freebsd-emulation Sun Jul 30 9:46: 5 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from bastuba.partitur.se (bastuba.partitur.se [193.219.246.194]) by hub.freebsd.org (Postfix) with ESMTP id 2E26437B677 for ; Sun, 30 Jul 2000 09:45:55 -0700 (PDT) (envelope-from girgen@partitur.se) Received: from stordatan.palle.se (c193.150.250.87.cm-upc.chello.se [193.150.250.87]) by bastuba.partitur.se (8.9.3/8.9.3) with ESMTP id SAA20990; Sun, 30 Jul 2000 18:45:44 +0200 (CEST) (envelope-from girgen@partitur.se) Received: from partitur.se (localhost [127.0.0.1]) by stordatan.palle.se (8.9.3/8.9.3) with ESMTP id SAA01289; Sun, 30 Jul 2000 18:45:44 +0200 (CEST) (envelope-from girgen@partitur.se) Message-ID: <39845BB8.EAA54B58@partitur.se> Date: Sun, 30 Jul 2000 18:45:44 +0200 From: Palle Girgensohn Organization: Partitur X-Mailer: Mozilla 4.74 [en] (X11; U; FreeBSD 4.1-STABLE i386) X-Accept-Language: sv, en MIME-Version: 1.0 To: A G F Keahan Cc: John Reynolds , emulation@freebsd.org Subject: Re: Some VMware progress. More questions (was Re: latest VMware port dumping core. ) References: <14716.26696.719757.828831@hip186.ch.intel.com> <200007250002.UAA00521@jupiter.delta.ny.us> <14717.14343.423191.404139@whale.home-net> <397D5A03.74EC2582@freenet.co.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org A G F Keahan wrote: {snip...] > VMWare creates a > large file in /tmp (slightly larger than the amount of RAM you > specified), which you can't see because it's unlink()ed. You could try > symlinking /tmp to /var/tmp or another location that has more disk > space, and see if the problem persists. Better still, add this to the /usr/local/bin/vmware shell script: TMPDIR=/var/tmp export TMPDIR This is more or less a must, especially if you have a small root partition or you are using mfs_mount for /tmp. -- Palle To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Sun Jul 30 18: 4:34 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 900DA37B8A4 for ; Sun, 30 Jul 2000 18:04:31 -0700 (PDT) (envelope-from vsilyaev@mindspring.com) Received: from jupiter.delta.ny.us (nyf-ny13-34.ix.netcom.com [198.211.19.34]) by smtp10.atl.mindspring.net (8.9.3/8.8.5) with ESMTP id VAA28557 for ; Sun, 30 Jul 2000 21:04:29 -0400 (EDT) Received: (from vsilyaev@localhost) by jupiter.delta.ny.us (8.9.3/8.9.3) id VAA05463 for emulation@freebsd.org; Sun, 30 Jul 2000 21:04:27 -0400 (EDT) (envelope-from vsilyaev) Date: Sun, 30 Jul 2000 21:04:26 -0400 From: "Vladimir N. Silyaev" To: emulation@freebsd.org Subject: New vmware port Message-ID: <20000730210426.A5429@jupiter.delta.ny.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org New vmware port avaliable for beta testing at: http://www.mindspring.com/~vsilyaev/vmware/vmware.tar.gz Most significant changes it's a merging vmnet and if_tap functionality. So for using networking staff with new port you should have a post 4.1-Release system. -- Vladimir To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Sun Jul 30 18:57: 2 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from bastuba.partitur.se (bastuba.partitur.se [193.219.246.194]) by hub.freebsd.org (Postfix) with ESMTP id 10D5A37B95C for ; Sun, 30 Jul 2000 18:56:58 -0700 (PDT) (envelope-from girgen@partitur.se) Received: from stordatan.palle.se (c193.150.250.87.cm-upc.chello.se [193.150.250.87]) by bastuba.partitur.se (8.9.3/8.9.3) with ESMTP id DAA23835; Mon, 31 Jul 2000 03:56:51 +0200 (CEST) (envelope-from girgen@partitur.se) Received: from partitur.se (localhost [127.0.0.1]) by stordatan.palle.se (8.9.3/8.9.3) with ESMTP id DAA03928; Mon, 31 Jul 2000 03:56:51 +0200 (CEST) (envelope-from girgen@partitur.se) Message-ID: <3984DCDF.B9E9521F@partitur.se> Date: Mon, 31 Jul 2000 03:56:47 +0200 From: Palle Girgensohn Organization: Partitur X-Mailer: Mozilla 4.74 [en] (X11; U; FreeBSD 4.1-STABLE i386) X-Accept-Language: sv, en MIME-Version: 1.0 To: "Vladimir N. Silyaev" Cc: emulation@freebsd.org Subject: Re: New vmware port References: <20000730210426.A5429@jupiter.delta.ny.us> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Vladimir N. Silyaev" wrote: > > New vmware port avaliable for beta testing at: > http://www.mindspring.com/~vsilyaev/vmware/vmware.tar.gz How come the new 2.0.2-621 version isn't used by beta port? Just a mistake, or will it fail? -- Palle To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Sun Jul 30 19: 0:47 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from bastuba.partitur.se (bastuba.partitur.se [193.219.246.194]) by hub.freebsd.org (Postfix) with ESMTP id 7256537B933 for ; Sun, 30 Jul 2000 19:00:43 -0700 (PDT) (envelope-from girgen@partitur.se) Received: from stordatan.palle.se (c193.150.250.87.cm-upc.chello.se [193.150.250.87]) by bastuba.partitur.se (8.9.3/8.9.3) with ESMTP id EAA23864; Mon, 31 Jul 2000 04:00:41 +0200 (CEST) (envelope-from girgen@partitur.se) Received: from partitur.se (localhost [127.0.0.1]) by stordatan.palle.se (8.9.3/8.9.3) with ESMTP id EAA04295; Mon, 31 Jul 2000 04:00:41 +0200 (CEST) (envelope-from girgen@partitur.se) Message-ID: <3984DDC9.5B0F7F2F@partitur.se> Date: Mon, 31 Jul 2000 04:00:41 +0200 From: Palle Girgensohn Organization: Partitur X-Mailer: Mozilla 4.74 [en] (X11; U; FreeBSD 4.1-STABLE i386) X-Accept-Language: sv, en MIME-Version: 1.0 To: John Reynolds Cc: emulation@freebsd.org Subject: Re: sysmouse type of mouse not supported? References: <14719.55204.532906.371631@gargle.gargle.HOWL> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org John Reynolds wrote: [snip...] > > However, right as I go into VMware I get a dialog box that says: > > unsupported host mouse type "sysmouse" > unable to open mouse device for full-screen VGA. > Full-screen VGA will not be supported. I get the message as you describe (I've always had it), but it doesn't give me any problems. I can run full screen and mouse is fine. Is that odd? :) -- Palle To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Mon Jul 31 6: 7:35 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from matrix.eurocontrol.fr (matrix.eurocontrol.fr [147.196.254.254]) by hub.freebsd.org (Postfix) with ESMTP id ECA5D37BAD1 for ; Mon, 31 Jul 2000 06:07:21 -0700 (PDT) (envelope-from roberto@eurocontrol.fr) Received: from caerdonn.eurocontrol.fr (caerdonn.eurocontrol.fr [147.196.51.214]) by matrix.eurocontrol.fr (Postfix) with ESMTP id 3F4EB5A59; Mon, 31 Jul 2000 15:07:20 +0200 (CEST) Received: by caerdonn.eurocontrol.fr (Postfix, from userid 1193) id 89F1B4E5C; Mon, 31 Jul 2000 15:07:19 +0200 (CEST) Date: Mon, 31 Jul 2000 15:07:19 +0200 From: Ollivier Robert To: Nick Sayer Cc: freebsd-emulation@freebsd.org Subject: Re: Bridged networking with vmware Message-ID: <20000731150719.C19666@caerdonn.eurocontrol.fr> References: <3981C35F.85C5B821@sftw.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <3981C35F.85C5B821@sftw.com>; from nsayer@sftw.com on Fri, Jul 28, 2000 at 10:31:11AM -0700 X-Operating-System: FreeBSD 5.0-CURRENT Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org According to Nick Sayer: > it's best to make sure it's happening right. Rhaaaaa. After taking the latest port from Vladimir, patching it to use the latest VMware and following your instructions, IT WORKS !!! /me is happy, thanks folks. -- Ollivier ROBERT -=- Eurocontrol EEC/ITM -=- Ollivier.Robert@eurocontrol.fr The Postman hits! The Postman hits! You have new mail. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Mon Jul 31 14:11:54 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from baynet.baynetworks.com (ns1.BayNetworks.COM [134.177.3.20]) by hub.freebsd.org (Postfix) with ESMTP id 35CBF37B553 for ; Mon, 31 Jul 2000 14:11:50 -0700 (PDT) (envelope-from bwithrow@BayNetworks.COM) Received: from mailhost.BayNetworks.COM (h8754.s84f5.BayNetworks.COM [132.245.135.84]) by baynet.baynetworks.com (8.9.1/8.9.1) with ESMTP id OAA21063; Mon, 31 Jul 2000 14:09:40 -0700 (PDT) Received: from pobox.engeast.BayNetworks.COM (pobox.engeast.baynetworks.com [192.32.61.6]) by mailhost.BayNetworks.COM (8.9.1/8.8.8) with ESMTP id RAA15721; Mon, 31 Jul 2000 17:11:11 -0400 (EDT) Received: from baynetworks.com (kyzyl [192.32.150.103]) by pobox.engeast.BayNetworks.COM (SMI-8.6/BNET-97/04/24-S) with ESMTP id RAA00472; Mon, 31 Jul 2000 17:11:09 -0400 for Message-Id: <200007312111.RAA00472@pobox.engeast.BayNetworks.COM> X-Mailer: exmh version 2.1.1 10/15/1999 To: Nick Sayer Cc: freebsd-emulation@freebsd.org, bwithrow@engeast.BayNetworks.COM Subject: Re: Bridged networking with vmware Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 31 Jul 2000 17:11:10 -0400 From: Robert Withrow Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi: :- After loading the module (either vmnet_bridge.ko or if_tap.ko) In what port does vmnet_bridge.ko exist? I'm running the "standard" FreeBSD port of VMWARE (/usr/ports/.../vmware1) with the Makefile having version 1.19, and there doesn't seem to be any vmnet_bridge.ko built. It is very confusing there being all these different ports. Also, it would be a lot more *user friendly* if whatever ports there are, that they all support 4.0 REL as well as newer stuff. It takes us a while to qual new releases. Thanks! -- Robert Withrow -- (+1 978 288 8256) BWithrow@BayNetworks.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Mon Jul 31 14:52:17 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from baynet.baynetworks.com (ns1.BayNetworks.COM [134.177.3.20]) by hub.freebsd.org (Postfix) with ESMTP id 15BC937BD22 for ; Mon, 31 Jul 2000 14:52:14 -0700 (PDT) (envelope-from bwithrow@BayNetworks.COM) Received: from mailhost.BayNetworks.COM (h8754.s84f5.BayNetworks.COM [132.245.135.84]) by baynet.baynetworks.com (8.9.1/8.9.1) with ESMTP id OAA22531 for ; Mon, 31 Jul 2000 14:50:40 -0700 (PDT) Received: from pobox.engeast.BayNetworks.COM (pobox.engeast.baynetworks.com [192.32.61.6]) by mailhost.BayNetworks.COM (8.9.1/8.8.8) with ESMTP id RAA16666 for ; Mon, 31 Jul 2000 17:52:11 -0400 (EDT) Received: from baynetworks.com (kyzyl [192.32.150.103]) by pobox.engeast.BayNetworks.COM (SMI-8.6/BNET-97/04/24-S) with ESMTP id RAA03118; Mon, 31 Jul 2000 17:52:10 -0400 for Message-Id: <200007312152.RAA03118@pobox.engeast.BayNetworks.COM> X-Mailer: exmh version 2.1.1 10/15/1999 To: freebsd-emulation@freebsd.org Cc: bwithrow@engeast.BayNetworks.COM Subject: Host-only networking and NAT? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 31 Jul 2000 17:52:10 -0400 From: Robert Withrow Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Suppose you want to run VMWARE on your FreeBSD 4.0 system and have it "share" your system's IP address. Or suppose you want to have VMWARE use a static address on the same lan as your FBSD system, but you can't use bridged networking (because FBSD4.0 doesn't support it.) Seems like you should be able to use NAT for this, right? But I've followed the instructions: - Re-build the ipfw module with -DIPDIVERT - Turned on forwarding - Config IPFW with: /sbin/ipfw -f flush /sbin/ipfw add divert natd all from any to any via xl0 /sbin/ipfw add pass all from any to any - Start natd with the -n xl0 option. And *no* traffic moves, not even normal xl0 traffic destined to adjacent nodes. If I delete the divert rule, traffic starts moving again (but, of course, no nat happens). It seems like this should work somehow, but I'm obviously confused. Does anyone do this sort of thing with VMWare? -- Robert Withrow -- (+1 978 288 8256) BWithrow@BayNetworks.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Mon Jul 31 15: 9:59 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from ms.tokyo.jcom.ne.jp (ms.tokyo.jcom.ne.jp [210.234.123.18]) by hub.freebsd.org (Postfix) with ESMTP id E9EDE37B689 for ; Mon, 31 Jul 2000 15:09:56 -0700 (PDT) (envelope-from knu@idaemons.org) Received: from daemon.local.idaemons.org (203-165-77-17.sugnm1.kt.home.ne.jp [203.165.77.17]) by ms.tokyo.jcom.ne.jp (8.9.3/3.7W 04/27/00) with ESMTP id HAA04270; Tue, 1 Aug 2000 07:09:14 +0900 (JST) Received: by daemon.local.idaemons.org (8.9.3/3.7W) id HAA07944; Tue, 1 Aug 2000 07:08:42 +0900 (JST) Date: Tue, 01 Aug 2000 07:08:41 +0900 Message-ID: <86og3e7y1i.wl@localhost.local.idaemons.org> From: "Akinori -Aki- MUSHA" To: Palle Girgensohn Cc: "Vladimir N. Silyaev" , emulation@FreeBSD.ORG Subject: Re: New vmware port In-Reply-To: In your message of "Mon, 31 Jul 2000 03:56:47 +0200" <3984DCDF.B9E9521F@partitur.se> References: <20000730210426.A5429@jupiter.delta.ny.us> <3984DCDF.B9E9521F@partitur.se> User-Agent: Wanderlust/2.3.0 (Roam) EMIKO/1.13.12 (Euglena sociabilis) FLIM/1.13.2 (Kasanui) APEL/10.2 MULE XEmacs/21.1 (patch 10) (Capitol Reef) (i386--freebsd) Organization: Associated I. Daemons X-PGP-Public-Key: finger knu@FreeBSD.org X-PGP-Fingerprint: 1BEF D9B2 BABD 25D7 659A FD08 89C2 F3BE E981 4E16 MIME-Version: 1.0 (generated by EMIKO 1.13.12 - "Euglena sociabilis") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At Mon, 31 Jul 2000 03:56:47 +0200, Palle Girgensohn wrote: > "Vladimir N. Silyaev" wrote: > > > > New vmware port avaliable for beta testing at: > > http://www.mindspring.com/~vsilyaev/vmware/vmware.tar.gz > > How come the new 2.0.2-621 version isn't used by beta port? > Just a mistake, or will it fail? Actually vmmon/vmnet modules weren't changed at all in Build 621 update, and it works without changes. I tested a while and have just merged Vladimir's latest version into the official port. Enjoy. :) ToDo: Update Hints.FreeBSD (about TMPDIR and Bridging) -- / /__ __ / ) ) ) ) / Akinori -Aki- MUSHA aka / (_ / ( (__( @ idaemons.org / FreeBSD.org "We're only at home when we're on the run, on the wing, on the fly" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Mon Jul 31 15:10:49 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from ms.tokyo.jcom.ne.jp (ms.tokyo.jcom.ne.jp [210.234.123.18]) by hub.freebsd.org (Postfix) with ESMTP id 2FC0D37B689 for ; Mon, 31 Jul 2000 15:10:46 -0700 (PDT) (envelope-from knu@idaemons.org) Received: from daemon.local.idaemons.org (203-165-77-17.sugnm1.kt.home.ne.jp [203.165.77.17]) by ms.tokyo.jcom.ne.jp (8.9.3/3.7W 04/27/00) with ESMTP id HAA04431; Tue, 1 Aug 2000 07:10:43 +0900 (JST) Received: by daemon.local.idaemons.org (8.9.3/3.7W) id HAA07966; Tue, 1 Aug 2000 07:10:11 +0900 (JST) Date: Tue, 01 Aug 2000 07:10:09 +0900 Message-ID: <86n1iy7xz2.wl@localhost.local.idaemons.org> From: "Akinori -Aki- MUSHA" To: "Vladimir N. Silyaev" Cc: emulation@FreeBSD.ORG Subject: Re: New vmware port In-Reply-To: In your message of "Sun, 30 Jul 2000 21:04:26 -0400" <20000730210426.A5429@jupiter.delta.ny.us> References: <20000730210426.A5429@jupiter.delta.ny.us> User-Agent: Wanderlust/2.3.0 (Roam) EMIKO/1.13.12 (Euglena sociabilis) FLIM/1.13.2 (Kasanui) APEL/10.2 MULE XEmacs/21.1 (patch 10) (Capitol Reef) (i386--freebsd) Organization: Associated I. Daemons X-PGP-Public-Key: finger knu@FreeBSD.org X-PGP-Fingerprint: 1BEF D9B2 BABD 25D7 659A FD08 89C2 F3BE E981 4E16 MIME-Version: 1.0 (generated by EMIKO 1.13.12 - "Euglena sociabilis") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At Sun, 30 Jul 2000 21:04:26 -0400, Vladimir N. Silyaev wrote: > New vmware port avaliable for beta testing at: > http://www.mindspring.com/~vsilyaev/vmware/vmware.tar.gz > > Most significant changes it's a merging vmnet and if_tap functionality. > So for using networking staff with new port you should have a post > 4.1-Release system. This is GREAT! It works perfectly with or without bridging as far as I tested. Thanks for your work, as always! :) -- / /__ __ / ) ) ) ) / Akinori -Aki- MUSHA aka / (_ / ( (__( @ idaemons.org / FreeBSD.org "We're only at home when we're on the run, on the wing, on the fly" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Mon Jul 31 16: 8: 0 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 F313E37B729 for ; Mon, 31 Jul 2000 16:07:47 -0700 (PDT) (envelope-from vsilyaev@mindspring.com) Received: from jupiter.delta.ny.us (nyf-ny11-47.ix.netcom.com [198.211.18.175]) by smtp10.atl.mindspring.net (8.9.3/8.8.5) with ESMTP id TAA14952; Mon, 31 Jul 2000 19:07:40 -0400 (EDT) Received: (from vsilyaev@localhost) by jupiter.delta.ny.us (8.9.3/8.9.3) id TAA00409; Mon, 31 Jul 2000 19:07:38 -0400 (EDT) (envelope-from vsilyaev) Date: Mon, 31 Jul 2000 19:07:37 -0400 From: "Vladimir N. Silyaev" To: Akinori -Aki- MUSHA Cc: Palle Girgensohn , emulation@FreeBSD.ORG Subject: Re: New vmware port Message-ID: <20000731190737.B371@jupiter.delta.ny.us> References: <20000730210426.A5429@jupiter.delta.ny.us> <3984DCDF.B9E9521F@partitur.se> <86og3e7y1i.wl@localhost.local.idaemons.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <86og3e7y1i.wl@localhost.local.idaemons.org>; from knu@idaemons.org on Tue, Aug 01, 2000 at 07:08:41AM +0900 Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Aug 01, 2000 at 07:08:41AM +0900, Akinori -Aki- MUSHA wrote: > > How come the new 2.0.2-621 version isn't used by beta port? > > Just a mistake, or will it fail? > > Actually vmmon/vmnet modules weren't changed at all in Build 621 > update, and it works without changes. > > I tested a while and have just merged Vladimir's latest version into > the official port. Enjoy. :) > > ToDo: > Update Hints.FreeBSD (about TMPDIR and Bridging) BTW, new vmware script point, set value for TMPDIR to /var/tmp, unless TMPDIR already defined. -- Vladimir To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Mon Jul 31 16:34:47 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from mail.yourfit.com (28.wxfr1.xdsl.nauticom.net [209.195.150.61]) by hub.freebsd.org (Postfix) with ESMTP id 15EB737B729 for ; Mon, 31 Jul 2000 16:34:39 -0700 (PDT) (envelope-from behanna@zbzoom.net) Received: from armani.yourfit.com (armani.yourfit.com [192.168.1.120]) by mail.yourfit.com (8.9.3/8.9.3) with ESMTP id TAA02460 for ; Mon, 31 Jul 2000 19:34:34 -0400 Date: Mon, 31 Jul 2000 19:34:34 -0400 (Eastern Daylight Time) From: Chris BeHanna Reply-To: Chris BeHanna To: emulation@freebsd.org Subject: Re: New vmware port In-Reply-To: <86og3e7y1i.wl@localhost.local.idaemons.org> 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 Tue, 1 Aug 2000, Akinori -Aki- MUSHA wrote: > At Mon, 31 Jul 2000 03:56:47 +0200, > Palle Girgensohn wrote: > > "Vladimir N. Silyaev" wrote: > > > > > > New vmware port avaliable for beta testing at: > > > http://www.mindspring.com/~vsilyaev/vmware/vmware.tar.gz > > > > How come the new 2.0.2-621 version isn't used by beta port? > > Just a mistake, or will it fail? > > Actually vmmon/vmnet modules weren't changed at all in Build 621 > update, and it works without changes. > > I tested a while and have just merged Vladimir's latest version into > the official port. Enjoy. :) After finally getting networking working, I am. What's left is getting Samba to work, and getting the guest win2k instance to see the samba-fied partitions on the host. Oh, and sound. :-/ It seems that my VMWare instance doesn't like /dev/pcm--I get a "Device cannot be configured" error. -- Chris BeHanna Software Engineer (at yourfit.com) behanna@zbzoom.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Mon Jul 31 17:13:59 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id B5C5937BD69 for ; Mon, 31 Jul 2000 17:13:49 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id UAA24188; Mon, 31 Jul 2000 20:13:40 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <200007312111.RAA00472@pobox.engeast.BayNetworks.COM> References: <200007312111.RAA00472@pobox.engeast.BayNetworks.COM> Date: Mon, 31 Jul 2000 20:13:46 -0400 To: Robert Withrow , Nick Sayer From: Garance A Drosihn Subject: Re: Bridged networking with vmware Cc: freebsd-emulation@FreeBSD.ORG, bwithrow@engeast.BayNetworks.COM Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 5:11 PM -0400 7/31/00, Robert Withrow wrote: >Hi: > >:- After loading the module (either vmnet_bridge.ko or if_tap.ko) > >In what port does vmnet_bridge.ko exist? > >I'm running the "standard" FreeBSD port of VMWARE (/usr/ports/.../vmware1) >with the Makefile having version 1.19, and there doesn't seem to be >any vmnet_bridge.ko built. > >It is very confusing there being all these different ports. I think vmware1 is just there for people who have bought the vmware1 license, and who have not wanted to buy a license for vmware2 (not yet, at least). Which is to say, vmware1 is pretty much frozen in time, just there for historical purposes. It's the vmware2 port which is seeing all the activity, as near as I can tell. As for vmware2, that seems to be moving so fast that it almost always requires that you're running 4-stable. (I just upgraded to the latest vmware port on my machine, which broke vmware2 because my OS level is a 4-stable from about three weeks ago). A little frustrating, to be sure, but I do appreciate all the improvements which are being made. I *was* going to run linux to use vmware, but redhat 6.2 seems to have trouble with my hardware. freebsd works fine on the hardware, so the better vmware2 port works, the happier I am... :-) --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Mon Jul 31 17:19:36 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 7691E37B512 for ; Mon, 31 Jul 2000 17:19:20 -0700 (PDT) (envelope-from vns@mindspring.com) Received: from jupiter.delta.ny.us (nyf-ny11-47.ix.netcom.com [198.211.18.175]) by maynard.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id UAA17726; Mon, 31 Jul 2000 20:19:12 -0400 (EDT) Received: (from vsilyaev@localhost) by jupiter.delta.ny.us (8.9.3/8.9.3) id UAA00641; Mon, 31 Jul 2000 20:19:09 -0400 (EDT) (envelope-from vns) Date: Mon, 31 Jul 2000 20:19:09 -0400 (EDT) From: "Vladimir N.Silyaev" Message-Id: <200008010019.UAA00641@jupiter.delta.ny.us> To: bwithrow@nortelnetworks.com Cc: emulation@freebsd.org Subject: Re: Bridged networking with vmware In-Reply-To: <200007312111.RAA00472@pobox.engeast.BayNetworks.COM> References: <200007312111.RAA00472@pobox.engeast.BayNetworks.COM> Reply-To: vns@delta.odessa.ua Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 31 Jul 2000 17:11:10 -0400, Robert Withrow wrote: >In what port does vmnet_bridge.ko exist? It was existed in beta version, announce about beta testing was postet to this list couple weeks ago. >I'm running the "standard" FreeBSD port of VMWARE (/usr/ports/.../vmware1) >with the Makefile having version 1.19, and there doesn't seem to be >any vmnet_bridge.ko built. If you are have 4.1 system or latter, you are have just to start: sysctl -w net.link.ether.bridge_refresh=1 sysctl -w net.link.ether.bridge=1 If you are have errors on that way, you should build kernel with BRIDGE option. > >It is very confusing there being all these different ports. It's only two of them - one in FreeBSD port tree, and second one, for testing available from my page. > >Also, it would be a lot more *user friendly* if whatever ports there >are, that they all support 4.0 REL as well as newer stuff. It takes >us a while to qual new releases. 4.0-Release was just testing release, if I don't miss something. And bridge options will be not supported on it. -- Vladimir To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Mon Jul 31 18:58:37 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from tisch.mail.mindspring.net (tisch.mail.mindspring.net [207.69.200.157]) by hub.freebsd.org (Postfix) with ESMTP id E574437BB0D for ; Mon, 31 Jul 2000 18:58:28 -0700 (PDT) (envelope-from vns@mindspring.com) Received: from jupiter.delta.ny.us (nyf-ny11-47.ix.netcom.com [198.211.18.175]) by tisch.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id VAA30203; Mon, 31 Jul 2000 21:58:26 -0400 (EDT) Received: (from vsilyaev@localhost) by jupiter.delta.ny.us (8.9.3/8.9.3) id VAA00865; Mon, 31 Jul 2000 21:58:23 -0400 (EDT) (envelope-from vns) Date: Mon, 31 Jul 2000 21:58:23 -0400 (EDT) From: "Vladimir N.Silyaev" Message-Id: <200008010158.VAA00865@jupiter.delta.ny.us> To: behanna@zbzoom.net Cc: emulation@freebsd.org Subject: Re: New vmware port In-Reply-To: References: Reply-To: vns@delta.odessa.ua Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In muc.lists.freebsd.emulation, you wrote: [skipped] > After finally getting networking working, I am. What's left is >getting Samba to work, and getting the guest win2k instance to see >the samba-fied partitions on the host. > > Oh, and sound. :-/ It seems that my VMWare instance doesn't >like /dev/pcm--I get a "Device cannot be configured" error. Probably, it's better to use moused and /dev/sysmouse. -- Vladimir To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Tue Aug 1 0:35:35 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from topperwein.dyndns.org (acs-24-154-5-187.zoominternet.net [24.154.5.187]) by hub.freebsd.org (Postfix) with ESMTP id F40C737B7A7 for ; Tue, 1 Aug 2000 00:35:29 -0700 (PDT) (envelope-from behanna@mail.zbzoom.net) Received: from mail.zbzoom.net (localhost [127.0.0.1]) by topperwein.zbzoom.net (8.9.3/8.9.3) with ESMTP id CAA73912; Tue, 1 Aug 2000 02:34:38 -0400 (EDT) (envelope-from behanna@mail.zbzoom.net) Message-ID: <39866F7E.27F7198E@mail.zbzoom.net> Date: Tue, 01 Aug 2000 02:34:38 -0400 From: Chris BeHanna Reply-To: behanna@zbzoom.net Organization: Western Pennsylvania Pizza Disposal Unit X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Robert Withrow Cc: freebsd-emulation@freebsd.org, bwithrow@engeast.BayNetworks.COM Subject: Re: Host-only networking and NAT? References: <200007312152.RAA03118@pobox.engeast.BayNetworks.COM> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Robert Withrow wrote: > Suppose you want to run VMWARE on your FreeBSD 4.0 system > and have it "share" your system's IP address. Or suppose you want to > have VMWARE use a static address on the same lan as your FBSD system, > but you can't use bridged networking (because FBSD4.0 doesn't support > it.) I have exactly this working, today (but no joy with Samba as of yet). See below. > Seems like you should be able to use NAT for this, right? But I've > followed the instructions: > > - Re-build the ipfw module with -DIPDIVERT > > - Turned on forwarding > > - Config IPFW with: > > /sbin/ipfw -f flush > /sbin/ipfw add divert natd all from any to any via xl0 > /sbin/ipfw add pass all from any to any > > - Start natd with the -n xl0 option. > > And *no* traffic moves, not even normal xl0 traffic destined to > adjacent nodes. If I delete the divert rule, traffic starts moving > again (but, of course, no nat happens). > > It seems like this should work somehow, but I'm obviously confused. > > Does anyone do this sort of thing with VMWare? I do (VMWare 2.02-621 on 4.1-RC #0, built Thu Jul 27 09:44:57 EDT 2000 after cvsupping the night before and building the world). Here's the relevant portion of my kernel config file: options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about # dropped packets options IPFIREWALL_FORWARD #enable transparent proxy support options IPFIREWALL_VERBOSE_LIMIT=10 #limit verbosity #options IPFIREWALL_DEFAULT_TO_ACCEPT #allow everything by default options IPV6FIREWALL #firewall for IPv6 options IPV6FIREWALL_VERBOSE options IPV6FIREWALL_VERBOSE_LIMIT=100 #options IPV6FIREWALL_DEFAULT_TO_ACCEPT options IPDIVERT #divert sockets options IPFILTER #ipfilter support options IPFILTER_LOG #ipfilter logging options IPSTEALTH #support for stealth forwarding Here's the relevant portion of /etc/rc.conf.local: natd_enable="YES" natd_interface="xl0" natd_flags="-dynamic -same_ports" With that set, you should be able to (as root) execute sh /etc/rc.firewall open and have nat work. If you don't like things open, make sure you build up your custom config a little bit of a time from a copy of the open case, and keep testing to make sure the last change didn't break it. (Rest assured, *I'm* not running open!) Here's the relevant portion of /etc/dhcpd.conf (well, actually, the whole thing): # --- begin dhcpd.conf --- # # 1 day in seconds # default-lease-time 86400; # # 3 days in seconds # max-lease-time 259200; subnet 192.168.254.0 netmask 255.255.255.0 { range 192.168.254.128 192.168.254.254; option broadcast-address 192.168.254.255; # # These are my ISP's nameservers. Replace them with your own. # option domain-name-servers 208.236.36.3, 208.236.38.3; # # This is my ISP's domain name. Replace it with your own. # option domain-name "zbzoom.net"; # # The address bound to your vmnet1 interface # option routers 192.168.254.1; } # # Static IP addresses for named hosts # group { use-host-decl-names true; # # The hardware ethernet must match the "network address" you set # for your virtual ethernet adaptor in your guest Windows # instance. # host win2k { hardware ethernet 00:50:56:C2:0C:69 ; fixed-address 192.168.254.128 ; } } # # Replace this with the class C that usually gets bound to your # external network interface (e.g., xl0), otherwise, dhcpd will # bitch about it. # subnet 24.154.5.0 netmask 255.255.255.0 {} # --- end dhcpd.conf --- Note that I specify that interface vmnet1 will always have address 192.168.254.1 (the default address for VMWare). This specification goes into /etc/vmware/config. Here are the relevant lines of /etc/vmware/config: vmnet1.HostOnlyAddress = "192.168.254.1" vmnet1.HostOnlyNetMask = "255.255.255.0" I also added entries for vmware and win2k in my /etc/hosts: 192.168.254.1 vmware 192.168.254.128 win2k Once you've done all of that, start dhcpd as root: dhcpd -cf /etc/dhcpd.conf Launch VMWare as yourself. Go to "Settings" and pick host-only networking. Boot your Windows guest. Open the device settings for your network adaptor, and choose Properties on the adaptor itself. Set its network address to the same MAC address you specified in your dhcpd.conf. Click Ok. Now select TCP/IP in the listbox, and click the Properties button below it. Select "Obtain automatically" for everything, then click Ok. Now, pop up a command window and type ipconfig /renew And that should be it. The directions may be slightly different if you've cvsupped more recently than I and if you've picked up Vladimir's latest changes (which include the if_tap.ko module, which I'm not currently using). Regards, Chris BeHanna Software Engineer (at yourfit.com) behanna@zbzoom.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Tue Aug 1 1: 4:31 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from topperwein.dyndns.org (acs-24-154-5-187.zoominternet.net [24.154.5.187]) by hub.freebsd.org (Postfix) with ESMTP id D0F0E37BB56 for ; Tue, 1 Aug 2000 01:04:24 -0700 (PDT) (envelope-from behanna@topperwein.dyndns.org) Received: (from root@localhost) by topperwein.dyndns.org (8.9.3/8.9.3) id EAA74576; Tue, 1 Aug 2000 04:03:46 -0400 (EDT) (envelope-from behanna) Received: from mail.zbzoom.net (localhost [127.0.0.1]) by topperwein.zbzoom.net (8.9.3/8.9.3) with ESMTP id CAA73912; Tue, 1 Aug 2000 02:34:38 -0400 (EDT) (envelope-from behanna@mail.zbzoom.net) Message-ID: <39866F7E.27F7198E@mail.zbzoom.net> Date: Tue, 01 Aug 2000 02:34:38 -0400 From: Chris BeHanna Reply-To: behanna@zbzoom.net Organization: Western Pennsylvania Pizza Disposal Unit X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Robert Withrow Cc: freebsd-emulation@freebsd.org, bwithrow@engeast.BayNetworks.COM Subject: Re: Host-only networking and NAT? References: <200007312152.RAA03118@pobox.engeast.BayNetworks.COM> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Robert Withrow wrote: > Suppose you want to run VMWARE on your FreeBSD 4.0 system > and have it "share" your system's IP address. Or suppose you want to > have VMWARE use a static address on the same lan as your FBSD system, > but you can't use bridged networking (because FBSD4.0 doesn't support > it.) I have exactly this working, today (but no joy with Samba as of yet). See below. > Seems like you should be able to use NAT for this, right? But I've > followed the instructions: > > - Re-build the ipfw module with -DIPDIVERT > > - Turned on forwarding > > - Config IPFW with: > > /sbin/ipfw -f flush > /sbin/ipfw add divert natd all from any to any via xl0 > /sbin/ipfw add pass all from any to any > > - Start natd with the -n xl0 option. > > And *no* traffic moves, not even normal xl0 traffic destined to > adjacent nodes. If I delete the divert rule, traffic starts moving > again (but, of course, no nat happens). > > It seems like this should work somehow, but I'm obviously confused. > > Does anyone do this sort of thing with VMWare? I do (VMWare 2.02-621 on 4.1-RC #0, built Thu Jul 27 09:44:57 EDT 2000 after cvsupping the night before and building the world). Here's the relevant portion of my kernel config file: options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about # dropped packets options IPFIREWALL_FORWARD #enable transparent proxy support options IPFIREWALL_VERBOSE_LIMIT=10 #limit verbosity #options IPFIREWALL_DEFAULT_TO_ACCEPT #allow everything by default options IPV6FIREWALL #firewall for IPv6 options IPV6FIREWALL_VERBOSE options IPV6FIREWALL_VERBOSE_LIMIT=100 #options IPV6FIREWALL_DEFAULT_TO_ACCEPT options IPDIVERT #divert sockets options IPFILTER #ipfilter support options IPFILTER_LOG #ipfilter logging options IPSTEALTH #support for stealth forwarding Here's the relevant portion of /etc/rc.conf.local: natd_enable="YES" natd_interface="xl0" natd_flags="-dynamic -same_ports" With that set, you should be able to (as root) execute sh /etc/rc.firewall open and have nat work. If you don't like things open, make sure you build up your custom config a little bit of a time from a copy of the open case, and keep testing to make sure the last change didn't break it. (Rest assured, *I'm* not running open!) Here's the relevant portion of /etc/dhcpd.conf (well, actually, the whole thing): # --- begin dhcpd.conf --- # # 1 day in seconds # default-lease-time 86400; # # 3 days in seconds # max-lease-time 259200; subnet 192.168.254.0 netmask 255.255.255.0 { range 192.168.254.128 192.168.254.254; option broadcast-address 192.168.254.255; # # These are my ISP's nameservers. Replace them with your own. # option domain-name-servers 208.236.36.3, 208.236.38.3; # # This is my ISP's domain name. Replace it with your own. # option domain-name "zbzoom.net"; # # The address bound to your vmnet1 interface # option routers 192.168.254.1; } # # Static IP addresses for named hosts # group { use-host-decl-names true; # # The hardware ethernet must match the "network address" you set # for your virtual ethernet adaptor in your guest Windows # instance. # host win2k { hardware ethernet 00:50:56:C2:0C:69 ; fixed-address 192.168.254.128 ; } } # # Replace this with the class C that usually gets bound to your # external network interface (e.g., xl0), otherwise, dhcpd will # bitch about it. # subnet 24.154.5.0 netmask 255.255.255.0 {} # --- end dhcpd.conf --- Note that I specify that interface vmnet1 will always have address 192.168.254.1 (the default address for VMWare). This specification goes into /etc/vmware/config. Here are the relevant lines of /etc/vmware/config: vmnet1.HostOnlyAddress = "192.168.254.1" vmnet1.HostOnlyNetMask = "255.255.255.0" I also added entries for vmware and win2k in my /etc/hosts: 192.168.254.1 vmware 192.168.254.128 win2k Once you've done all of that, start dhcpd as root: dhcpd -cf /etc/dhcpd.conf Launch VMWare as yourself. Go to "Settings" and pick host-only networking. Boot your Windows guest. Open the device settings for your network adaptor, and choose Properties on the adaptor itself. Set its network address to the same MAC address you specified in your dhcpd.conf. Click Ok. Now select TCP/IP in the listbox, and click the Properties button below it. Select "Obtain automatically" for everything, then click Ok. Now, pop up a command window and type ipconfig /renew And that should be it. The directions may be slightly different if you've cvsupped more recently than I and if you've picked up Vladimir's latest changes (which include the if_tap.ko module, which I'm not currently using). Regards, Chris BeHanna Software Engineer (at yourfit.com) behanna@zbzoom.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Tue Aug 1 6:23:53 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from southpass.baynetworks.com (ns2.BayNetworks.COM [134.177.3.16]) by hub.freebsd.org (Postfix) with ESMTP id 5407C37B6F6 for ; Tue, 1 Aug 2000 06:23:35 -0700 (PDT) (envelope-from bwithrow@BayNetworks.COM) Received: from mailhost.BayNetworks.COM (h8754.s84f5.BayNetworks.COM [132.245.135.84]) by southpass.baynetworks.com (8.9.1/8.9.1) with ESMTP id GAA21660; Tue, 1 Aug 2000 06:13:39 -0700 (PDT) Received: from pobox.engeast.BayNetworks.COM (pobox.engeast.baynetworks.com [192.32.61.6]) by mailhost.BayNetworks.COM (8.9.1/8.8.8) with ESMTP id JAA24900; Tue, 1 Aug 2000 09:21:34 -0400 (EDT) Received: from baynetworks.com (kyzyl [192.32.150.103]) by pobox.engeast.BayNetworks.COM (SMI-8.6/BNET-97/04/24-S) with ESMTP id JAA14859; Tue, 1 Aug 2000 09:21:32 -0400 for Message-Id: <200008011321.JAA14859@pobox.engeast.BayNetworks.COM> X-Mailer: exmh version 2.1.1 10/15/1999 To: vns@delta.odessa.ua Cc: emulation@freebsd.org, bwithrow@engeast.BayNetworks.COM Subject: Re: Bridged networking with vmware In-Reply-To: Message from "Vladimir N.Silyaev" of "Mon, 31 Jul 2000 20:19:09 EDT." <200008010019.UAA00641@jupiter.delta.ny.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 01 Aug 2000 09:21:33 -0400 From: Robert Withrow Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org vns@mindspring.com said: :- 4.0-Release was just testing release, if I don't miss something. And :- bridge options will be not supported on it. If at all possible, could you please make sure that 4.1-RELEASE stays supported? It is absolutely impossible (for operational reasons) for us to run -STABLE. Also, could you modify your port so that it issues an error message if it is installed on a version that it doesn't support. Your latest port merrily installs on 4.0-RELEASE, but it doesn't run on 4.0-RELEASE. It would also be good to change the DESCRIPTION file to mention OS version dependencies. A final suggestion: it would be great to maintain a version that *does* work on 4.0-RELEASE, even if it doesn't support bridging. I'm sure there are other sites like ours that can't jump on new FreeBSD releases immediately. Thanks! -- Robert Withrow -- (+1 978 288 8256) BWithrow@BayNetworks.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Tue Aug 1 9:13:40 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from venus.cs.put.poznan.pl (vega.cs.put.poznan.pl [150.254.30.30]) by hub.freebsd.org (Postfix) with ESMTP id 28F3D37B767; Tue, 1 Aug 2000 09:13:34 -0700 (PDT) (envelope-from piotr.wozniak@cs.put.poznan.pl) Received: from cs.put.poznan.pl (dcs-430x-pw.cs.put.poznan.pl [150.254.31.188]) by venus.cs.put.poznan.pl (8.10.2/8.10.2) with ESMTP id e71G7lZ09659; Tue, 1 Aug 2000 18:07:51 +0200 (CEST) Message-ID: <3986F72A.84D87E6@cs.put.poznan.pl> Date: Tue, 01 Aug 2000 18:13:30 +0200 From: Piotr =?iso-8859-1?Q?Wo=9Fniak?= X-Mailer: Mozilla 4.73 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-emulation@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: DOS emulation Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I have to run programs in Clipper/DOS under FreeBSD. Does exist a good DOS-emulator or other solving of this problem? (for example compiling source code in Clipper under FreeBSD..) Piotr Wozniak To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Tue Aug 1 9:40:12 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id C49FB37BE66; Tue, 1 Aug 2000 09:40:07 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e71FksP14872; Tue, 1 Aug 2000 08:46:54 -0700 (PDT) Date: Tue, 1 Aug 2000 08:46:53 -0700 From: Alfred Perlstein To: Piotr Wo?niak Cc: freebsd-emulation@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: DOS emulation Message-ID: <20000801084653.O4854@fw.wintelcom.net> References: <3986F72A.84D87E6@cs.put.poznan.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <3986F72A.84D87E6@cs.put.poznan.pl>; from piotr.wozniak@cs.put.poznan.pl on Tue, Aug 01, 2000 at 06:13:30PM +0200 Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * Piotr Wo?niak [000801 08:21] wrote: > Hi, > I have to run programs in Clipper/DOS under FreeBSD. > Does exist a good DOS-emulator or other solving of this problem? > (for example compiling source code in Clipper under FreeBSD..) Maybe 'doscmd'? Let us know. :) -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Tue Aug 1 9:52:43 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from mail-in-02.piro.net (mail-out-01.piro.net [194.64.31.11]) by hub.freebsd.org (Postfix) with ESMTP id 99B6E37BE12; Tue, 1 Aug 2000 09:52:35 -0700 (PDT) (envelope-from marc.vanwoerkom@science-factory.com) Received: from nil.science-factory.com (ScienceFactory-atm1-153.piro.net [195.135.137.205]) by mail-in-02.piro.net (8.9.3/8.9.3/PN-991208) with ESMTP id SAA25907; Tue, 1 Aug 2000 18:52:21 +0200 Received: by nil.science-factory.com (Postfix, from userid 501) id 92FCF200C; Tue, 1 Aug 2000 18:45:46 +0200 (CEST) From: Marc van Woerkom To: piotr.wozniak@cs.put.poznan.pl Cc: freebsd-emulation@FreeBSD.ORG, freebsd-current@FreeBSD.ORG In-reply-to: <3986F72A.84D87E6@cs.put.poznan.pl> (message from Piotr =?iso-8859-1?Q?Wo=9Fniak?= on Tue, 01 Aug 2000 18:13:30 +0200) Subject: Re: DOS emulation References: <3986F72A.84D87E6@cs.put.poznan.pl> Message-Id: <20000801164546.92FCF200C@nil.science-factory.com> Date: Tue, 1 Aug 2000 18:45:46 +0200 (CEST) Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I have to run programs in Clipper/DOS under FreeBSD. > Does exist a good DOS-emulator or other solving of this problem? Bochs and Wine both do a good job. Check your /usr/ports/emulators or the FreeBSD web site. There are a couple of strange uses for both programs. Today we needed a DOS boot disk for some BIOS update in our shop which couldn't be created under Windows 2000. My colleague did it with Bochs. :) A bizarre use for Wine is this http://people.freebsd.org/~3d/wine Regards, Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Tue Aug 1 10:20:49 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from zmail6.easynet.fr (email.easynet.fr [195.114.64.207]) by hub.freebsd.org (Postfix) with SMTP id A47BD37BFA4 for ; Tue, 1 Aug 2000 10:20:44 -0700 (PDT) (envelope-from fonvi@easynet.fr) Received: (qmail 88460 invoked from network); 1 Aug 2000 17:20:42 -0000 Received: from mailgate3.easynet.fr (192.168.1.4) by mailserver.easynet.fr with QMQP; 1 Aug 2000 17:20:42 -0000 Received: from adsl-92-1-170.pops.easynet.fr (HELO marduk.styx.org) (212.11.34.170) by mrelay3.easynet.fr with SMTP; 1 Aug 2000 17:22:14 -0000 Received: (from marc@localhost) by marduk.styx.org (8.9.3/8.9.3/ - 6/08/98) id TAA02347; Tue, 1 Aug 2000 19:18:38 +0200 (CEST) (envelope-from marc) Date: Tue, 1 Aug 2000 19:18:38 +0200 From: Marc Fonvieille To: Piotr Wo?niak Cc: freebsd-emulation@freebsd.org Subject: Re: DOS emulation Message-ID: <20000801191838.B979@marduk.styx.org> References: <3986F72A.84D87E6@cs.put.poznan.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <3986F72A.84D87E6@cs.put.poznan.pl>; from piotr.wozniak@cs.put.poznan.pl on Tue, Aug 01, 2000 at 06:13:30PM +0200 X-Useless-Header: Black Metal inc. X-Operating-System: FreeBSD 4.1-STABLE Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Aug 01, 2000 at 06:13:30PM +0200, Piotr Wo?niak wrote: > Hi, > I have to run programs in Clipper/DOS under FreeBSD. > Does exist a good DOS-emulator or other solving of this problem? > (for example compiling source code in Clipper under FreeBSD..) I don't know clipper, but if it's a text program you can use doscmd. Bochs is the better choice for graphic application : i obtain better results than with vmware. Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Tue Aug 1 11: 3:36 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id E18DB37C1BD; Tue, 1 Aug 2000 11:03:30 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id LAA03713; Tue, 1 Aug 2000 11:03:17 -0700 (PDT) (envelope-from obrien) Date: Tue, 1 Aug 2000 11:03:17 -0700 From: "David O'Brien" To: Piotr Wo?niak Cc: freebsd-emulation@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: DOS emulation Message-ID: <20000801110317.A3666@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <3986F72A.84D87E6@cs.put.poznan.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <3986F72A.84D87E6@cs.put.poznan.pl>; from piotr.wozniak@cs.put.poznan.pl on Tue, Aug 01, 2000 at 06:13:30PM +0200 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Aug 01, 2000 at 06:13:30PM +0200, Piotr Wo?niak wrote: > I have to run programs in Clipper/DOS under FreeBSD. If this is character based, I have the best luck running Quicken for MS-DOS using the ``pcemu'' port. Bochs is way much slower, and doscmd also would work for me with this application. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Tue Aug 1 12:26:17 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id C0A8F37BA8D; Tue, 1 Aug 2000 12:26:12 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id PAA79293; Tue, 1 Aug 2000 15:25:50 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Tue, 1 Aug 2000 15:25:48 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Piotr =?iso-8859-1?Q?Wo=9Fniak?= Cc: freebsd-emulation@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: DOS emulation In-Reply-To: <3986F72A.84D87E6@cs.put.poznan.pl> Message-ID: 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 I've been using vmware with great success under -STABLE. Take a look at /usr/ports/emulators/vmware2. It's commercial, but works a lot better than all the alternatives. I've had decent success with pcemu for DOS-based programs, although there are a few quirks. I found bochs also worked pretty well (fewer quirks, more features) but much slower. On Tue, 1 Aug 2000, Piotr Wo=9Fniak wrote: > Hi, > I have to run programs in Clipper/DOS under FreeBSD. > Does exist a good DOS-emulator or other solving of this problem? > (for example compiling source code in Clipper under FreeBSD..) > Piotr Wozniak >=20 >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message >=20 Robert N M Watson=20 robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Tue Aug 1 16: 9: 9 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 26A7237B678 for ; Tue, 1 Aug 2000 16:09:04 -0700 (PDT) (envelope-from vsilyaev@mindspring.com) Received: from jupiter.delta.ny.us (nyf-ny2-39.ix.netcom.com [198.211.16.103]) by blount.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id TAA01243; Tue, 1 Aug 2000 19:08:26 -0400 (EDT) Received: (from vsilyaev@localhost) by jupiter.delta.ny.us (8.9.3/8.9.3) id TAA00339; Tue, 1 Aug 2000 19:08:24 -0400 (EDT) (envelope-from vsilyaev) Date: Tue, 1 Aug 2000 19:08:23 -0400 From: "Vladimir N. Silyaev" To: Robert Withrow Cc: emulation@freebsd.org, bwithrow@engeast.BayNetworks.COM Subject: Re: Bridged networking with vmware Message-ID: <20000801190823.A298@jupiter.delta.ny.us> References: <200008011321.JAA14859@pobox.engeast.BayNetworks.COM> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200008011321.JAA14859@pobox.engeast.BayNetworks.COM>; from bwithrow@nortelnetworks.com on Tue, Aug 01, 2000 at 09:21:33AM -0400 Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Aug 01, 2000 at 09:21:33AM -0400, Robert Withrow wrote: > :- 4.0-Release was just testing release, if I don't miss something. And > :- bridge options will be not supported on it. > > If at all possible, could you please make sure that 4.1-RELEASE stays > supported? I can't guarantee nothing, sorry guys. > It is absolutely impossible (for operational reasons) for > us to run -STABLE. But for me it's impossible to do a testing on a spread range platforms. > > Also, could you modify your port so that it issues an error message if > it is installed on a version that it doesn't support. Your latest port > merrily installs on 4.0-RELEASE, but it doesn't run on 4.0-RELEASE. I don't think that it doesn't run, it should run, but without networking stuff. > > It would also be good to change the DESCRIPTION file to mention OS version > dependencies. Unfortunately I don't have ability to do a testing. > > A final suggestion: it would be great to maintain a version that *does* work > on 4.0-RELEASE, even if it doesn't support bridging. I'm sure there are > other sites like ours that can't jump on new FreeBSD releases immediately. If you have -RELEASE just use port from /usr/ports tree what is coming with you release. And you will be guaranteed to have the same result as for date when release was published, not less, not more. -- Vladimir To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Tue Aug 1 16:17:49 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 1725437B678; Tue, 1 Aug 2000 16:17:42 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id RAA61281; Tue, 1 Aug 2000 17:17:39 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id RAA87007; Tue, 1 Aug 2000 17:17:22 -0600 (MDT) Message-Id: <200008012317.RAA87007@harmony.village.org> To: Piotr =?iso-8859-1?Q?Wo=9Fniak?= Subject: Re: DOS emulation Cc: freebsd-emulation@FreeBSD.ORG, freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Tue, 01 Aug 2000 18:13:30 +0200." <3986F72A.84D87E6@cs.put.poznan.pl> References: <3986F72A.84D87E6@cs.put.poznan.pl> Date: Tue, 01 Aug 2000 17:17:22 -0600 From: Warner Losh Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <3986F72A.84D87E6@cs.put.poznan.pl> Piotr =?iso-8859-1?Q?Wo=9Fniak?= writes: : I have to run programs in Clipper/DOS under FreeBSD. : Does exist a good DOS-emulator or other solving of this problem? : (for example compiling source code in Clipper under FreeBSD..) dosemu works OK. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Tue Aug 1 19: 1:25 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 10D7A37B5B6 for ; Tue, 1 Aug 2000 19:01:20 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id WAA105638; Tue, 1 Aug 2000 22:01:13 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20000801190823.A298@jupiter.delta.ny.us> References: <200008011321.JAA14859@pobox.engeast.BayNetworks.COM> <20000801190823.A298@jupiter.delta.ny.us> Date: Tue, 1 Aug 2000 22:01:26 -0400 To: "Vladimir N. Silyaev" , Robert Withrow From: Garance A Drosihn Subject: VMware port stability Cc: emulation@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 7:08 PM -0400 8/1/00, Vladimir N. Silyaev wrote: >On Tue, Aug 01, 2000 at 09:21:33AM -0400, Robert Withrow wrote: > > Also, could you modify your port so that it issues an error > > message if it is installed on a version that it doesn't support. > > Your latest port merrily installs on 4.0-RELEASE, but it > > doesn't run on 4.0-RELEASE. > >I don't think that it doesn't run, it should run, but without >networking stuff. I am running 4.0-20000625-STABLE, and had vmware working. I noticed the port was updated with a newer version of vmware, and a number of improvements that seemed nice. So, I updated my ports tree, rebuilt vmware2, and it installed fine without any complaint. It was not until I rebooted that I got some messages about "can't load if_tap.ko" and "cannot create /compat/linux/dev/vmnet1". My previously-working vmware2 setup is now gone, apparently, because of that upgrade. I don't mind too much, because I wanted to rebuild with the 4.1-RELEASE.iso image anyway, but I hope you can understand that this would get mighty frustrating mighty fast. The result is that vmware runs, but if I try to start any previously-working virtual machine I get a new error about "could not open /dev/vmnet1", and the virtual machine just stops at that point. It sure seems like I can not run any machine which I previously had working, and I was given no helpful warning of this until it was too late. > > A final suggestion: it would be great to maintain a > > version that *does* work on 4.0-RELEASE, even if it > > doesn't support bridging. I'm sure there are other > > sites like ours that can't jump on new FreeBSD releases > > immediately. > > If you have -RELEASE just use port from /usr/ports tree > what is coming with you release. And you will be guaranteed > to have the same result as for date when release was > published, not less, not more. I understand that vmware2, by necessity, was a fast-moving target which depended on new features installed in the "stable" system. However, I think it would now be a good idea to do something to recognize that many people are actually USING the port right now, and can not update to the up-to-the-second version of 'stable' just to get some minor changes to vmware2 (such as a new bug-fix release of the base linux-based vmware from vmware.com itself). I don't know what the best suggestion would be, but almost all the other ports have a higher standard of compatibility with previous freebsd releases than you have described for vmware2. My guess is that we maybe need a "vmware2" port, and a "vmware2-devel" port. The first would hopefully remain compatible with freebsd-4.1-release at the very LEAST. It still might be updated for assorted reasons (such as a new vmware release from vmware.com), but not in ways where people trying the port for the first time have to dig up their original copy of the 4.1-release CD's. You could then have the bleeding-edge "vmware2-devel" port, where it is explicitly stated that you must be running "the absolutely most recent snapshot of 4-current" to use, and it would even have some check in it to indicate what that minimum version level is. Please note that I do very much appreciate all this work you have been doing to get vmware working so well on freebsd. In my case, I got vmware2 for linux, and then managed to buy new hardware which redhat linux seems to get confused by. So it is REALLY great for me that you've done so much to get vmware2 working as well as it does under freebsd (freebsd seems to have no trouble with my new hardware...). At the same time, it is mighty painful to have a port which may completely break without notice, and that it is somehow "my fault" for treating the vmware2 port exactly the same as I treat every other port I use in the ports collection. --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Tue Aug 1 19:58:36 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 3E6A637BF6A for ; Tue, 1 Aug 2000 19:58:32 -0700 (PDT) (envelope-from vsilyaev@mindspring.com) Received: from jupiter.delta.ny.us (nyf-ny2-39.ix.netcom.com [198.211.16.103]) by granger.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id WAA15065; Tue, 1 Aug 2000 22:58:28 -0400 (EDT) Received: (from vsilyaev@localhost) by jupiter.delta.ny.us (8.9.3/8.9.3) id WAA01804; Tue, 1 Aug 2000 22:58:25 -0400 (EDT) (envelope-from vsilyaev) Date: Tue, 1 Aug 2000 22:58:24 -0400 From: "Vladimir N. Silyaev" To: Garance A Drosihn Cc: Robert Withrow , emulation@FreeBSD.ORG Subject: Re: VMware port stability Message-ID: <20000801225824.A1751@jupiter.delta.ny.us> References: <200008011321.JAA14859@pobox.engeast.BayNetworks.COM> <20000801190823.A298@jupiter.delta.ny.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from drosih@rpi.edu on Tue, Aug 01, 2000 at 10:01:26PM -0400 Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Aug 01, 2000 at 10:01:26PM -0400, Garance A Drosihn wrote: > >I don't think that it doesn't run, it should run, but without > >networking stuff. > > I am running 4.0-20000625-STABLE, and had vmware working. I > noticed the port was updated with a newer version of vmware, > and a number of improvements that seemed nice. So, I updated > my ports tree, rebuilt vmware2, and it installed fine without > any complaint. It was not until I rebooted that I got some > messages about "can't load if_tap.ko" and "cannot create > /compat/linux/dev/vmnet1". My previously-working vmware2 > setup is now gone, apparently, because of that upgrade. I > don't mind too much, because I wanted to rebuild with the > 4.1-RELEASE.iso image anyway, but I hope you can understand > that this would get mighty frustrating mighty fast. > > The result is that vmware runs, but if I try to start any > previously-working virtual machine I get a new error about > "could not open /dev/vmnet1", and the virtual machine just > stops at that point. It sure seems like I can not run any > machine which I previously had working, and I was given no > helpful warning of this until it was too late. Ok. All of this stuff only about networking, isn't it? > > > A final suggestion: it would be great to maintain a > > > version that *does* work on 4.0-RELEASE, even if it > > > doesn't support bridging. I'm sure there are other > > > sites like ours that can't jump on new FreeBSD releases > > > immediately. > > > > If you have -RELEASE just use port from /usr/ports tree > > what is coming with you release. And you will be guaranteed > > to have the same result as for date when release was > > published, not less, not more. > > I understand that vmware2, by necessity, was a fast-moving > target which depended on new features installed in the > "stable" system. However, I think it would now be a good > idea to do something to recognize that many people are > actually USING the port right now, and can not update to > the up-to-the-second version of 'stable' just to get some > minor changes to vmware2 (such as a new bug-fix release > of the base linux-based vmware from vmware.com itself). > > I don't know what the best suggestion would be, but almost > all the other ports have a higher standard of compatibility > with previous freebsd releases than you have described for > vmware2. The problem is that all other ports don't include inside kernel modules. BTW in -STABLE branch interfaces for ethernet drivers was changed two times for last two months. And new source code don't compiled with old kernel and vise versa. > My guess is that we maybe need a "vmware2" port, > and a "vmware2-devel" port. The first would hopefully > remain compatible with freebsd-4.1-release at the very LEAST. The one of purposes to exclude vmnet stuff from the current port and move that functionality into the tap driver it was to move kernel depended code into the main FreeBSD kernel source tree. > It still might be updated for assorted reasons (such as a new > vmware release from vmware.com) In such way you are may just to use old port with corrected filename for vmware tarball and use make NOCHECKSUM=yes reinstall. > but not in ways where people > trying the port for the first time have to dig up their > original copy of the 4.1-release CD's. You could then have > the bleeding-edge "vmware2-devel" port, where it is explicitly > stated that you must be running "the absolutely most recent > snapshot of 4-current" to use, and it would even have some > check in it to indicate what that minimum version level is. Ok, let's put in that way, anything located at http://www.mindspring.com/~vsilyaev/vmware/vmware.tar.gz it's a bleeding-edge, and in to an announce I including special requirements to use it, i.e. from the latest one -=-=-=-=-=-=-=-=-= So for using networking stuff with new port you should have a post 4.1-Release system. -=-=-=-=-=-=-=-=-= Official port you should get from FreeBSD ports tree, or what's better from snapshot of ports tree from yours release/snapshot. -- Vladimir To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Tue Aug 1 20:26: 8 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from quack.kfu.com (quack.kfu.com [205.178.90.194]) by hub.freebsd.org (Postfix) with ESMTP id 17DE537BF6A for ; Tue, 1 Aug 2000 20:26:04 -0700 (PDT) (envelope-from nsayer@quack.kfu.com) Received: from medusa.kfu.com (medusa.kfu.com [205.178.90.222]) by quack.kfu.com (8.9.3/8.9.3) with ESMTP id UAA40825; Tue, 1 Aug 2000 20:26:02 -0700 (PDT) (envelope-from nsayer@quack.kfu.com) Received: from icarus.kfu.com (ssmail@localhost) by medusa.kfu.com (8.9.3/8.8.8) with ESMTP id UAA56238; Tue, 1 Aug 2000 20:26:02 -0700 (PDT) (envelope-from nsayer@quack.kfu.com) X-Authentication-Warning: medusa.kfu.com: ssmail owned process doing -bs Received: from quack.kfu.com by icarus.kfu.com with ESMTP (8.9.3//ident-1.0) id UAA13481; Tue, 1 Aug 2000 20:26:01 -0700 (PDT) Message-ID: <398794C9.AE29D2E9@quack.kfu.com> Date: Tue, 01 Aug 2000 20:26:01 -0700 From: Nick Sayer X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: emulation@FreeBSD.ORG Cc: "Vladimir N. Silyaev" , Robert Withrow , bwithrow@engeast.BayNetworks.COM Subject: Re: Bridged networking with vmware References: <200008011321.JAA14859@pobox.engeast.BayNetworks.COM> <20000801190823.A298@jupiter.delta.ny.us> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Vladimir N. Silyaev" wrote: > > On Tue, Aug 01, 2000 at 09:21:33AM -0400, Robert Withrow wrote: > > :- 4.0-Release was just testing release, if I don't miss something. And > > :- bridge options will be not supported on it. > > > > If at all possible, could you please make sure that 4.1-RELEASE stays > > supported? > I can't guarantee nothing, sorry guys. If you use the current vmware port, it will run just fine on 4.1-RELEASE if you merely add /modules/if_tap.ko. That's the only thing that didn't make it into RELENG_4 in time for 4.1 (besides, obviously, the updated vmware2 port). If you wish, you can make if_tap.ko by just checking out the module makefile and /sys/net/if_tap* from RELENG_4. From your operational perspective, if you're willing to kldload vmmon and vmnet, if_tap shouldn't give you any trouble. :-) That advise may not hold forever. But it is certainly true now. It's my fault that tap didn't make it into 4.1. Sorry. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Tue Aug 1 21: 4:14 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 1A31B37B546 for ; Tue, 1 Aug 2000 21:04:10 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id AAA379430; Wed, 2 Aug 2000 00:04:05 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20000801225824.A1751@jupiter.delta.ny.us> References: <200008011321.JAA14859@pobox.engeast.BayNetworks.COM> <20000801190823.A298@jupiter.delta.ny.us> <20000801225824.A1751@jupiter.delta.ny.us> Date: Wed, 2 Aug 2000 00:04:08 -0400 To: "Vladimir N. Silyaev" From: Garance A Drosihn Subject: Re: VMware port stability Cc: Robert Withrow , emulation@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 10:58 PM -0400 8/1/00, Vladimir N. Silyaev wrote: >On Tue, Aug 01, 2000 at 10:01:26PM -0400, Garance A Drosihn wrote: > > I am running 4.0-20000625-STABLE, and had vmware working. I > > noticed the port was updated with a newer version of vmware, > > and a number of improvements that seemed nice. So, I updated > > my ports tree, rebuilt vmware2, and it installed fine without > > any complaint. > > > > The result is that vmware runs, but if I try to start any > > previously-working virtual machine I get a new error about > > "could not open /dev/vmnet1", and the virtual machine just > > stops at that point. It sure seems like I can not run any > > machine which I previously had working, and I was given no > > helpful warning of this until it was too late. > >Ok. All of this stuff only about networking, isn't it? My virtual machines no longer work at all. Vmware complains about /dev/vmnet1, and then stops. It will not let the virtual machine continue to boot up. Apparently I can not start up any of my previously-working vmware systems (unless perhaps I fiddle around with their configurations?). Previously, those virtual systems worked (they were using virtual disks, and bridging for networking). > > I don't know what the best suggestion would be, but almost > > all the other ports have a higher standard of compatibility > > with previous freebsd releases than you have described for > > vmware2. > >The problem is that all other ports don't include inside kernel >modules. BTW in -STABLE branch interfaces for ethernet drivers >was changed two times for last two months. And new source code >don't compiled with old kernel and vise versa. Well, then, there is still something wrong in the way things are split between "the port" of vmware, and "the system code" which vmware is taking advantage of. You're saying that people should not rebuild the vmware2 port unless they are also doing a 'make buildworld' at the same time. > > but not in ways where people > > trying the port for the first time have to dig up their > > original copy of the 4.1-release CD's. > >-=-=-=-=-=-=-=-=-= >So for using networking stuff with new port you should have a >post 4.1-Release system. >-=-=-=-=-=-=-=-=-= It requires a POST-4.1-release system? Already? The ISO image for 4.1 was just released today, and the vmware2 port is ALREADY incompatible with it? The 4.1-release CD's have not even been pressed yet. Can you see that this situation might be a bit painful for people interested in vmware? >Official port you should get from FreeBSD ports tree, or what's >better from snapshot of ports tree from yours release/snapshot. When I install freebsd (any release of freebsd), my standard operating practice is to: 1) install a minimal system, including the cvsup package. 2) cvsup the ports tree 3) install the ports I am interested in Step #2 is a perfectly reasonable step for anyone to do, and I would even argue that it is advisable. Ignoring the vmware2 port for the moment, there are many other ports which may have received important security patches since the release of the CD I am installing from (if I am installing from a CD). You're saying that if I do step #2, because maybe I want the latest bug-fixes to Bind or Sendmail or whatever program that evil forces have recently broken into, then I will immediately be in the position of an unworkable vmware2 port. This is somewhat problematic. Again, let me say that all this vmware-related work is very excellent, and very much appreciated. I'm just finding that the port for it needs to behave a bit more like other ports, or it gets very frustrating for anyone to try to use. It is the very fact that this vmware work is so useful which makes it increasingly important that the port pays a little more attention to being compatible with a wider range of freebsd releases. (instead of constantly requiring "freebsd-today" for today's vmware2 port to work). --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Tue Aug 1 23:26:46 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 9598737BC89 for ; Tue, 1 Aug 2000 23:26:42 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id CAA94228; Wed, 2 Aug 2000 02:26:40 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <398794C9.AE29D2E9@quack.kfu.com> References: <200008011321.JAA14859@pobox.engeast.BayNetworks.COM> <20000801190823.A298@jupiter.delta.ny.us> <398794C9.AE29D2E9@quack.kfu.com> Date: Wed, 2 Aug 2000 02:26:44 -0400 To: Nick Sayer , emulation@FreeBSD.ORG From: Garance A Drosihn Subject: Re: Bridged networking with vmware Cc: "Vladimir N. Silyaev" Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 8:26 PM -0700 8/1/00, Nick Sayer wrote: >If you use the current vmware port, it will run just fine on >4.1-RELEASE if you merely add /modules/if_tap.ko. That's the >only thing that didn't make it into RELENG_4 in time for 4.1 >(besides, obviously, the updated vmware2 port). If you wish, >you can make if_tap.ko by just checking out the module makefile >and /sys/net/if_tap* from RELENG_4. From your operational >perspective, if you're willing to kldload vmmon and vmnet, >if_tap shouldn't give you any trouble. :-) Well, I think I've done this right, and it wasn't too hard once I sorted it out. I won't know for sure until I get a few other things built (I'm building 4.1-release from scratch using the new ISO image). If this does work OK, I think it will be a common enough issue that the port itself should check for this and give some helpful pointers/advice/whatever. I'll try to write up something useful to add to the port for this, hopefully this coming weekend. --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Wed Aug 2 5:24:25 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from southpass.baynetworks.com (ns2.BayNetworks.COM [134.177.3.16]) by hub.freebsd.org (Postfix) with ESMTP id 6151237B71E for ; Wed, 2 Aug 2000 05:24:12 -0700 (PDT) (envelope-from bwithrow@BayNetworks.COM) Received: from mailhost.BayNetworks.COM (h8754.s84f5.BayNetworks.COM [132.245.135.84]) by southpass.baynetworks.com (8.9.1/8.9.1) with ESMTP id FAA05089; Wed, 2 Aug 2000 05:16:02 -0700 (PDT) Received: from pobox.engeast.BayNetworks.COM (pobox.engeast.baynetworks.com [192.32.61.6]) by mailhost.BayNetworks.COM (8.9.1/8.8.8) with ESMTP id IAA22203; Wed, 2 Aug 2000 08:23:58 -0400 (EDT) Received: from baynetworks.com (kyzyl [192.32.150.103]) by pobox.engeast.BayNetworks.COM (SMI-8.6/BNET-97/04/24-S) with ESMTP id IAA08126; Wed, 2 Aug 2000 08:23:57 -0400 for Message-Id: <200008021223.IAA08126@pobox.engeast.BayNetworks.COM> X-Mailer: exmh version 2.1.1 10/15/1999 To: Garance A Drosihn Cc: "Vladimir N. Silyaev" , emulation@FreeBSD.ORG, bwithrow@engeast.BayNetworks.COM Subject: Re: VMware port stability In-Reply-To: Message from Garance A Drosihn of "Wed, 02 Aug 2000 00:04:08 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 02 Aug 2000 08:23:57 -0400 From: Robert Withrow Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Nothing worse than complaining users, right? ;-) I also am *ecstatic* about the work you have done to get VMWare running. I think you deserver to be awarded, at least, a free (large) Chuck doll! (Actually, I think VMWare should hire you to do *official* FBSD support!) The latest VMWare port in the ports tree (the one with the Makefile with version 1.19) runs *fine* on 4.0 REL *with* host-only networking. Using NAT one can get that to look just like bridged networking, or (as I use it) you can have the VM share your host OSs address. I think this is a valuable thing to support! There will be a number of users who will want to run VMWare who will not be upgrading to 4.n (n > 0) for some time, for whatever reason. It would be a real shame to unnecessarily remove VMWare from the list of things they can run. Now, your suggestion to just update the port to fetch the newer bits from VMWare when they change is a reasonable one, except that it is possible that future VMWare changes might require changes to your OS shim layer code. Likewise there might be bug fixes or other stuff in your shim code (vmmon) that would help 4.0 REL users if they were made available. So I guess what I am suggesting would be best for the users is: 1) have just *one* port that works for all versions of FreeBSD with v >= 4.0 Rel. Looking at the makefile it seems like this should relatively straightforward, although the vmnet part would be a pain. 2) Have a designated and labeled 4.0 port that would track changes in VMWare and fix bugs in the underlying support code. I know that this would make extra work for you, and that you don't have resources (machines, time, etc) to do this all yourself. I'll volunteer to test releases on 4.0 Rel (since we will have 4.0 machines running here for at least the next 6 months), and help with debugging etc. I'm guessing other users would be willing to help out also. Again, thanks for all your good work. This tool is an incredible FreeBSD productivity enhancer! -- Robert Withrow -- (+1 978 288 8256) BWithrow@BayNetworks.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Wed Aug 2 11:30:51 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from osiris.ipform.ru (osiris.ipform.ru [212.158.165.98]) by hub.freebsd.org (Postfix) with ESMTP id 6383C37C263 for ; Wed, 2 Aug 2000 11:30:27 -0700 (PDT) (envelope-from matrix@ipform.ru) Received: from wp2 (wp2 [192.168.0.12]) by osiris.ipform.ru (8.9.3/8.9.3) with SMTP id WAA19078 for ; Wed, 2 Aug 2000 22:30:23 +0400 (MSD) (envelope-from matrix@ipform.ru) Message-ID: <005901bffcaf$29ec6da0$0c00a8c0@ipform.ru> From: "Artem Koutchine" To: Subject: VMWare2 networking does not work (cannot access internet from vm) Date: Wed, 2 Aug 2000 22:26:13 +0400 Organization: IP Form MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" 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 have big problem with VMWare accessing internet from virtual machine. here is the layout: 1. GATEWAY MACHINE WITH REAL IP USING NAT TO GIVE ACCESS TO OTHER MACHINES 2. Client machines using gateway machine as a gatway to internet 3. VMWare on the client machine using 192.168.253.1 as a vmnet interface and 192.168.253.2 for the windows 98 os. Client machines work fine. I can access internet from vmware on the gateway machine. But if VMWare started on the client machine the internet is inacessible from the virtual machine, though it can ping the other client machines. NAT is configured for all unregistered address (i guess it is 192.168.x.x) All machines 4.1-stable with the same hardware and kernel config. For example: gateway: 192.168.0.1 client 192.168.0.13 vmnet: 192.168.253.1 win98: 192.168.253.2 uses 192.168.253.1 as a gateway from win98 i can ping 192.168.253.1 AND 192.168.0.13 but cannot ping 192.168.0.1 Any ideas? Artem To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Wed Aug 2 12:50: 2 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 548D537BAB6 for ; Wed, 2 Aug 2000 12:49:57 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA65732 for ; Wed, 2 Aug 2000 13:49:55 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA94212 for ; Wed, 2 Aug 2000 13:49:35 -0600 (MDT) Message-Id: <200008021949.NAA94212@harmony.village.org> To: emulation@freebsd.org Subject: Quick question: NetBSD/i386 binaries? Date: Wed, 02 Aug 2000 13:49:35 -0600 From: Warner Losh Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Can one run NetBSD/i386 binaries (elf I think, but they might be aout, I'm downloading them now) on FreeBSD/i386? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Wed Aug 2 16:20:40 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 76F9937B70F for ; Wed, 2 Aug 2000 16:20:36 -0700 (PDT) (envelope-from vsilyaev@mindspring.com) Received: from jupiter.delta.ny.us (nyf-ny3-32.ix.netcom.com [198.211.16.160]) by granger.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id TAA11075; Wed, 2 Aug 2000 19:20:32 -0400 (EDT) Received: (from vsilyaev@localhost) by jupiter.delta.ny.us (8.9.3/8.9.3) id TAA00361; Wed, 2 Aug 2000 19:20:30 -0400 (EDT) (envelope-from vsilyaev) Date: Wed, 2 Aug 2000 19:20:30 -0400 From: "Vladimir N. Silyaev" To: Robert Withrow Cc: emulation@freebsd.org Subject: Re: VMware port stability Message-ID: <20000802192030.B312@jupiter.delta.ny.us> References: <200008021223.IAA08126@pobox.engeast.BayNetworks.COM> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200008021223.IAA08126@pobox.engeast.BayNetworks.COM>; from bwithrow@nortelnetworks.com on Wed, Aug 02, 2000 at 08:23:57AM -0400 Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Aug 02, 2000 at 08:23:57AM -0400, Robert Withrow wrote: [skipped] > The latest VMWare port in the ports tree (the one with the Makefile > with version 1.19) runs *fine* on 4.0 REL *with* host-only networking. Actually latest is 1.20, and it's almost same as in my page, so it doesn't support nor 4.0 REL, nor 4.1 REL. > Using NAT one can get that to look just like bridged networking, or > (as I use it) you can have the VM share your host OSs address. > > I think this is a valuable thing to support! There will be a number > of users who will want to run VMWare who will not be upgrading to > 4.n (n > 0) for some time, for whatever reason. It would be a real > shame to unnecessarily remove VMWare from the list of things they > can run. > > Now, your suggestion to just update the port to fetch the newer bits > from VMWare when they change is a reasonable one, except that it is > possible that future VMWare changes might require changes to your > OS shim layer code. Likewise there might be bug fixes or other > stuff in your shim code (vmmon) that would help 4.0 REL users if > they were made available. I don't think that VMWARE will be put something new in the Linux kernel driver. > > So I guess what I am suggesting would be best for the users is: > > 1) have just *one* port that works for all versions of FreeBSD with > v >= 4.0 Rel. Looking at the makefile it seems like this should > relatively straightforward, although the vmnet part would be a pain. From 4.0 to 4.1 was several changes in the all ethernet drivers, so it's not so easy to include support 4.0 Rel, due this reason. > > 2) Have a designated and labeled 4.0 port that would track changes > in VMWare and fix bugs in the underlying support code. Actually I have everything in CVS tree, so I can just produce any snapshot ;-). > > I know that this would make extra work for you, and that you don't have > resources (machines, time, etc) to do this all yourself. I'll volunteer > to test releases on 4.0 Rel (since we will have 4.0 machines running > here for at least the next 6 months), and help with debugging etc. I'm > guessing other users would be willing to help out also. I hope so. -- Vladimir To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Wed Aug 2 16:22:32 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from ns2.destek.net (ns2.Destek.Net [192.156.97.61]) by hub.freebsd.org (Postfix) with ESMTP id E7AEC37B5CB for ; Wed, 2 Aug 2000 16:22:29 -0700 (PDT) (envelope-from marc@destek.net) Received: from ns2.Destek.Net (ns2.Destek.Net [192.156.97.61]) by ns2.destek.net (8.10.0/8.10.0) with ESMTP id e72NMRc63751 for ; Wed, 2 Aug 2000 19:22:28 -0400 (EDT) Date: Wed, 2 Aug 2000 19:22:25 -0400 (EDT) From: Marc Evans To: freebsd-emulation@freebsd.org Subject: WebTrends on FreeBSD 4.1 (Linux Emulation) 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 Hello - I am desperately in need of getting WebTrends for Linux operational on FreeBSD 4.1. In tryin to run the daemons I am finding that they are failing the Linux Emulation code with this: /kernel: linux: syscall rt_sigtimedwait is obsoleted or not implemented Sure enough, looking through the kernel code I see that the syscall is in the linux_dummy.c file. Scouring around a bit more I also see that the same decision was made in the SVR4 emulation. I have done some searches on the prior e-mail on the lists and I am not finding any discussion about 1) Is there a good workaround? 2) What was the basis of decision resulting in some syscalls not being implemented? I am considering trying to implement the function, but if there is already a good workaround then please let me know. Also, if there is good reason not to bother trying to implement this, I would really appreciate knowing... Thanks in advance - Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Wed Aug 2 16:52:40 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 936C037B75F for ; Wed, 2 Aug 2000 16:52:37 -0700 (PDT) (envelope-from marcel@cup.hp.com) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel3.hp.com (Postfix) with ESMTP id E860C5FB; Wed, 2 Aug 2000 16:52:28 -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 QAA27309; Wed, 2 Aug 2000 16:52:25 -0700 (PDT) Message-ID: <3988B438.F4ADB5F7@cup.hp.com> Date: Wed, 02 Aug 2000 16:52:24 -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: Marc Evans Cc: freebsd-emulation@FreeBSD.ORG Subject: Re: WebTrends on FreeBSD 4.1 (Linux Emulation) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Marc Evans wrote: > > /kernel: linux: syscall rt_sigtimedwait is obsoleted or not implemented > > I have done some searches on the prior e-mail on the lists and I am not > finding any discussion about 1) Is there a good workaround? 2) What was > the basis of decision resulting in some syscalls not being implemented? 1) Implementing the syscall is the best "workaround" :-) 2) This is not so much a decision. So far nothing depended on the syscall. Implementation of syscalls is primarily based on available time and how often Linux binaries fail because it isnt implemented. > I am considering trying to implement the function, but if there is already > a good workaround then please let me know. Also, if there is good reason > not to bother trying to implement this, I would really appreciate > knowing... I think that implementing the syscall is the best approach. -- 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 Fri Aug 4 13:45: 4 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from pan.salford.ac.uk (pan.salford.ac.uk [146.87.255.104]) by hub.freebsd.org (Postfix) with SMTP id 295D837BB88 for ; Fri, 4 Aug 2000 13:44:41 -0700 (PDT) (envelope-from M.S.Powell@salford.ac.uk) Received: (qmail 32125 invoked by alias); 4 Aug 2000 20:44:35 -0000 Received: (qmail 32119 invoked from network); 4 Aug 2000 20:44:35 -0000 Received: from unknown (HELO plato.salford.ac.uk) (146.87.255.76) by pan.salford.ac.uk with SMTP; 4 Aug 2000 20:44:35 -0000 Received: (qmail 1778 invoked by uid 141); 4 Aug 2000 20:44:35 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 4 Aug 2000 20:44:35 -0000 Date: Fri, 4 Aug 2000 21:44:35 +0100 (BST) From: Mark Powell To: freebsd-emulation@freebsd.org Subject: UT under FreeBSD 4.1-S 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 I've been following the instructions at: http://www.doctorschwa.com/ut/freebsd_server.html Very informative. However, I'm still getting a problem. I'm using 4.1-STABLE cvsupped today. I've installed linux_base 6.1 and the glib-1.2.6 and xdelta-1.1.1 described. When I start UT it looks good: rust:/compat/linux/usr/local/games/UnrealTournament/System # ./ucc server DM-Turbine Executing Class Engine.ServerCommandlet Unreal engine initialized Browse: DM-Turbine?Name=Player?Class=Botpack.TMale2?team=255?skin=SoldierSkins.blkt?Face=SoldierSkins.Othello LoadMap: DM-Turbine?Name=Player?Class=Botpack.TMale2?team=255?skin=SoldierSkins.blkt?Face=SoldierSkins.Othello Loading: Package DM-Turbine Loading: Package UTtech1 Loading: Package Detail Bound to Fire.so However, it breaks down further on: Loading: Package Liquids Loading: Package AmbModern Case-insensitive search: utcrypt -> ../Textures/UTcrypt.utx Loading: Package utcrypt Loading: Package AmbOutside Loading: Package Run Illegal instruction (core dumped) A ktrace shows: 16756 ucc RET read 4057/0xfd9 16756 ucc CALL open(0xbfbfcf30,0,0x1b6) 16756 ucc NAMI "DM-Turbine.int" 16756 ucc RET open JUSTRETURN 16756 ucc CALL open(0xbfbfcf30,0,0x1b6) 16756 ucc NAMI "DM-Turbine.int" 16756 ucc RET open JUSTRETURN 16756 ucc CALL open(0xbfbfcf30,0,0x1b6) 16756 ucc NAMI "DM-Turbine.int" 16756 ucc RET open JUSTRETURN 16756 ucc CALL open(0xbfbfcf30,0,0x1b6) 16756 ucc NAMI "DM-Turbine.int" 16756 ucc RET open JUSTRETURN 16756 ucc CALL open(0xbfbfcf30,0,0x1b6) 16756 ucc NAMI "DM-Turbine.int" 16756 ucc RET open JUSTRETURN 16756 ucc PSIG SIGSEGV caught handler=0x280b0460 mask=0x80000000 code=0x0 16756 ucc PSIG SIGSEGV caught handler=0x280b0460 mask=0x80000400 code=0x0 16756 ucc PSIG SIGILL SIG_DFL 16756 ucc NAMI "ucc.core" I've tried this on two machines cvsupped today and also made sure I've followed the instructions exactly, but still the same on both. Anyone seen this or anyone with better Linux emulation knowledge than me know what's up? Cheers. Mark Powell - UNIX System Administrator - Clifford Whitworth Building A.I.S., University of Salford, Salford, Manchester, UK. Tel: +44 161 295 5936 Fax: +44 161 295 5888 www.pgp.com for PGP key M.S.Powell@salfrd.ac.uk (spell salford correctly to reply to me) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Sat Aug 5 2:40:29 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from pan.salford.ac.uk (pan.salford.ac.uk [146.87.255.104]) by hub.freebsd.org (Postfix) with SMTP id D028237B658 for ; Sat, 5 Aug 2000 02:40:24 -0700 (PDT) (envelope-from M.S.Powell@salford.ac.uk) Received: (qmail 36171 invoked by alias); 5 Aug 2000 09:40:23 -0000 Received: (qmail 36165 invoked from network); 5 Aug 2000 09:40:22 -0000 Received: from unknown (HELO plato.salford.ac.uk) (146.87.255.76) by pan.salford.ac.uk with SMTP; 5 Aug 2000 09:40:22 -0000 Received: (qmail 4969 invoked by uid 141); 5 Aug 2000 09:40:22 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 5 Aug 2000 09:40:22 -0000 Date: Sat, 5 Aug 2000 10:40:22 +0100 (BST) From: Mark Powell To: freebsd-emulation@freebsd.org Subject: Re: UT under FreeBSD 4.1-S In-Reply-To: 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 I pin-pointed this down to a bad patching of the UT to v4.13a. Sorry. Anyone managed to get UT playing under FreeBSD as a game, rather than a server? Or am I going to have to install RedHat? Also, has anyone managed to get the UT v4.25 patch to apply. It's heavily Linux based and seems to core dump. Cheers. Mark Powell - UNIX System Administrator - Clifford Whitworth Building A.I.S., University of Salford, Salford, Manchester, UK. Tel: +44 161 295 5936 Fax: +44 161 295 5888 www.pgp.com for PGP key M.S.Powell@salfrd.ac.uk (spell salford correctly to reply to me) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Sat Aug 5 7: 8:30 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from mta01-svc.ntlworld.com (mta01-svc.ntlworld.com [62.253.162.41]) by hub.freebsd.org (Postfix) with ESMTP id 5A71F37B627 for ; Sat, 5 Aug 2000 07:08:26 -0700 (PDT) (envelope-from mark@ukug.uk.freebsd.org) Received: from parish.my.domain ([62.253.84.226]) by mta01-svc.ntlworld.com (InterMail vM.4.01.02.27 201-229-119-110) with ESMTP id <20000805140823.ZWBP26680.mta01-svc.ntlworld.com@parish.my.domain>; Sat, 5 Aug 2000 15:08:23 +0100 Received: (from mark@localhost) by parish.my.domain (8.9.3/8.9.3) id PAA00445; Sat, 5 Aug 2000 15:08:15 +0100 (BST) (envelope-from mark) Date: Sat, 5 Aug 2000 15:08:15 +0100 From: Mark Ovens To: Robert Withrow Cc: John Reynolds , emulation@freebsd.org Subject: Re: FreeBSD/VMWare setup for dummies? Message-ID: <20000805150815.C254@parish> References: <200007271242.IAA16126@pobox.engeast.BayNetworks.COM> 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: <200007271242.IAA16126@pobox.engeast.BayNetworks.COM>; from bwithrow@nortelnetworks.com on Thu, Jul 27, 2000 at 08:42:30AM -0400 Organization: Total lack of Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Jul 27, 2000 at 08:42:30AM -0400, Robert Withrow wrote: > Thanks for the info. Actually, late last night I actually flopped in > the correct direction (probably accidentally). I'll note where your > stuff differs from mine: > > :- First off, is the NT/BSD boot disk an IDE disk? I hope so. Even VMware > :- themselves say booting a VM from scsi is at best experimental. I would > :- seriously doubt it would work under FreeBSD, but maybe > > It's scsi, and it seems to work. > I've been following this thread and learnt quite a bit from it, thanks guys, however I *still* can't get vmware to run :( It starts up but as soon as I click the Power On button the vmware window turns black and the whole machine locks solid (no keyboard or mouse response, and the desktop clock and xtimer stop) and after ~15 secs the machine spontaneously reboots (which is a PITA as it fsck's the disks every time). There is no clue in the vmware log, or /var/adm/messages, as to the cause. I've tried using a virtual disk and (currently) a plain disk (SCSI). I've set up with no CD-ROM and floppy (to minimize possible causes) but still it won't run. I originally built it with the latest port (Makefile rev 1.20) but in another thread here it implied/suggested that the previous Makefile (rev 1.19) may be better, so I grabbed that and tried it - no different. Can anyone shed any light on the cause of these crashes? Also, I have no .nvram file. Is it supposed to be created by hand? If so, what goes in it? # uname -a FreeBSD parish 4.1-RC FreeBSD 4.1-RC #0: Thu Jul 20 20:54:53 BST 2000 root@parish:/usr/obj/usr/src/sys/PARISH i386 # cat win95.{cfg,hba} #!/usr/local/lib/vmware/bin/vmware config.version = 2 # No cdrom installed # Disk Drive Info scsi0:0.present = TRUE scsi0:0.deviceType = "plainDisk" scsi0:0.fileName = "win95.hba" scsi0.present = TRUE # No floppy installed floppy0.present = FALSE # No networking installed # Memory size memsize = 32 # Nvram nvram = /usr/marko/.vmware/win95/win95.nvram # Log file log.fileName = /usr/marko/.vmware/win95/win95.log # Hints guestOS = win95 DRIVETYPE scsi CYLINDERS 527 HEADS 255 SECTORS 63 ACCESS "disk.mbr" 0 63 ACCESS "/dev/rda0s1" 63 1044162 ACCESS "/dev/null" 1044225 7422030 -- If I buy a copy of WinDelete, and it doesn't delete Windows, am I entitled to my money back? ________________________________________________________________ 51.44°N FreeBSD - The Power To Serve http://www.freebsd.org 2.057°W My Webpage http://ukug.uk.freebsd.org/~mark mailto:marko@freebsd.org http://www.radan.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Sat Aug 5 15: 8: 5 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from wop21.wop.wtb.tue.nl (wop21.wop.wtb.tue.nl [131.155.56.216]) by hub.freebsd.org (Postfix) with ESMTP id 0513637BB31 for ; Sat, 5 Aug 2000 15:07:57 -0700 (PDT) (envelope-from karelj@wop21.wop.wtb.tue.nl) Received: (from karelj@localhost) by wop21.wop.wtb.tue.nl (8.9.3/8.9.3) id AAA27613; Sun, 6 Aug 2000 00:07:40 +0200 (CEST) (envelope-from karelj) Date: Sun, 6 Aug 2000 00:07:40 +0200 From: "Karel J. Bosschaart" To: Mark Powell Cc: freebsd-emulation@FreeBSD.ORG Subject: Re: UT under FreeBSD 4.1-S Message-ID: <20000806000740.A27573@wop21.wop.wtb.tue.nl> Reply-To: K.J.Bosschaart@tue.nl References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from M.S.Powell@salford.ac.uk on Sat, Aug 05, 2000 at 10:40:22AM +0100 Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Aug 05, 2000 at 10:40:22AM +0100, Mark Powell wrote: > > I pin-pointed this down to a bad patching of the UT to v4.13a. Sorry. > > Anyone managed to get UT playing under FreeBSD as a game, rather than a > server? Or am I going to have to install RedHat? > Yes, I'm playing UT 4.13 as a game in FreeBSD 4.0-Stable :-). As a funny side note, I also have RedHat 6.1 on the same machine and it doesn't work there, because I don't know how to get the 3dfx thing going. It complains that it can't find the voodoo card... I had the exact same problem in FBSD 3.4 but it went away after upgrading to 4.0. However, I recently tried a network game and that didn't work :-(, though I'm sure that I once played a network game, most probably it was UT 4.00. > Also, has anyone managed to get the UT v4.25 patch to apply. It's heavily > Linux based and seems to core dump. > No, I didn't try yet... but I'll certainly do when I have time for it, which is in one or two weeks. How did you go from 4.00 to 4.13? I used the xdiff from the FreeBSD ports collection and used it on the linux binaries which seems to have worked. Karel. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Sat Aug 5 16:59:56 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 228D737B77C; Sat, 5 Aug 2000 16:59:54 -0700 (PDT) (envelope-from vsilyaev@mindspring.com) Received: from jupiter.delta.ny.us (nyf-ny5-27.ix.netcom.com [198.211.17.27]) by blount.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id TAA26614; Sat, 5 Aug 2000 19:59:51 -0400 (EDT) Received: (from vsilyaev@localhost) by jupiter.delta.ny.us (8.9.3/8.9.3) id TAA00434; Sat, 5 Aug 2000 19:59:49 -0400 (EDT) (envelope-from vsilyaev) Date: Sat, 5 Aug 2000 19:59:49 -0400 (EDT) From: "Vladimir N. Silyaev" Message-Id: <200008052359.TAA00434@jupiter.delta.ny.us> To: marko@FreeBSD.ORG Cc: emulation@FreeBSD.ORG Subject: Re: FreeBSD/VMWare setup for dummies? In-Reply-To: <20000805150815.C254@parish> References: <200007271242.IAA16126@pobox.engeast.BayNetworks.COM> <20000805150815.C254@parish> Reply-To: vns@delta.odessa.ua Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In muc.lists.freebsd.emulation, you wrote: >I've been following this thread and learnt quite a bit from it, thanks >guys, however I *still* can't get vmware to run :( > >It starts up but as soon as I click the Power On button the vmware >window turns black and the whole machine locks solid (no keyboard or >mouse response, and the desktop clock and xtimer stop) and after ~15 >secs the machine spontaneously reboots (which is a PITA as it fsck's >the disks every time). 1. Checks date of the kernel, linux.ko and vmmon.ko, it should be in descended order. 2. Create new dummy configuration, without any hardware, and try it. It useless, but at least you should see a Phoenix BIOS logo. If it doesn't help, that means you are have incompatible hardware (never heard before about that). -- Regards, Vladimir To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Sat Aug 5 17: 4:59 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from pan.salford.ac.uk (pan.salford.ac.uk [146.87.255.104]) by hub.freebsd.org (Postfix) with SMTP id D372637BBB2 for ; Sat, 5 Aug 2000 17:04:52 -0700 (PDT) (envelope-from M.S.Powell@salford.ac.uk) Received: (qmail 38082 invoked by alias); 6 Aug 2000 00:04:50 -0000 Received: (qmail 38076 invoked from network); 6 Aug 2000 00:04:50 -0000 Received: from unknown (HELO plato.salford.ac.uk) (146.87.255.76) by pan.salford.ac.uk with SMTP; 6 Aug 2000 00:04:50 -0000 Received: (qmail 6370 invoked by uid 141); 6 Aug 2000 00:04:46 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 6 Aug 2000 00:04:46 -0000 Date: Sun, 6 Aug 2000 01:04:46 +0100 (BST) From: Mark Powell To: K.J.Bosschaart@tue.nl Cc: freebsd-emulation@FreeBSD.ORG Subject: Re: UT under FreeBSD 4.1-S In-Reply-To: <20000806000740.A27573@wop21.wop.wtb.tue.nl> 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 Sun, 6 Aug 2000, Karel J. Bosschaart wrote: > Yes, I'm playing UT 4.13 as a game in FreeBSD 4.0-Stable :-). As a funny > side note, I also have RedHat 6.1 on the same machine and it doesn't work > there, because I don't know how to get the 3dfx thing going. It complains > that it can't find the voodoo card... I had the exact same problem in FBSD 3.4 > but it went away after upgrading to 4.0. Interesting. 20 questions... Uses the Voodoo card too? Nice. Does it work with a V3? That would require XFree86 4? It is slower than Win98? Any problems with mouse focusing. I seem to remember back in the days I ran quake2 under FreeBSD that was a problem. > However, I recently tried a network game and that didn't work :-(, though I'm > sure that I once played a network game, most probably it was UT 4.00. Oh dear. That's quite an important part of it :( > > Also, has anyone managed to get the UT v4.25 patch to apply. It's heavily > > Linux based and seems to core dump. > > > No, I didn't try yet... but I'll certainly do when I have time for it, > which is in one or two weeks. How did you go from 4.00 to 4.13? I used > the xdiff from the FreeBSD ports collection and used it on the linux binaries > which seems to have worked. The previous patches were easy to apply. Extract the 4.13a .tar.gz, make sure the UT CD is mounted at /mnt/cdrom, then run the install-sh script. Does it all no problem. The 4.25 patch is a little trickier. Uses binaries and X interface to do the install. Haven't been able to get that working yet. Let me know if you succeed. I'm going to look at it again. You could quite easily patch it up under Linux and copy the filesystem across. Any chance of making the changes it makes available somewhere? I realise this will be a largish tar file as it'll probably modifiy those 40MB files a little. Downloading something that big is no problem, if you could put it up somewhere? Cheers. Mark Powell - UNIX System Administrator - Clifford Whitworth Building A.I.S., University of Salford, Salford, Manchester, UK. Tel: +44 161 295 5936 Fax: +44 161 295 5888 www.pgp.com for PGP key M.S.Powell@salfrd.ac.uk (spell salford correctly to reply to me) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Sat Aug 5 17:29:20 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from mta03-svc.ntlworld.com (mta03-svc.ntlworld.com [62.253.162.43]) by hub.freebsd.org (Postfix) with ESMTP id 65BE037B646 for ; Sat, 5 Aug 2000 17:29:17 -0700 (PDT) (envelope-from mark@ukug.uk.freebsd.org) Received: from parish.my.domain ([62.255.99.41]) by mta03-svc.ntlworld.com (InterMail vM.4.01.02.27 201-229-119-110) with ESMTP id <20000806002914.EDYH16423.mta03-svc.ntlworld.com@parish.my.domain>; Sun, 6 Aug 2000 01:29:14 +0100 Received: (from mark@localhost) by parish.my.domain (8.9.3/8.9.3) id BAA04622; Sun, 6 Aug 2000 01:29:22 +0100 (BST) (envelope-from mark) Date: Sun, 6 Aug 2000 01:29:22 +0100 From: Mark Ovens To: vns@delta.odessa.ua Cc: emulation@FreeBSD.ORG Subject: Re: FreeBSD/VMWare setup for dummies? Message-ID: <20000806012922.P254@parish> References: <200007271242.IAA16126@pobox.engeast.BayNetworks.COM> <20000805150815.C254@parish> <200008052359.TAA00434@jupiter.delta.ny.us> 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: <200008052359.TAA00434@jupiter.delta.ny.us>; from vsilyaev@mindspring.com on Sat, Aug 05, 2000 at 07:59:49PM -0400 Organization: Total lack of Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Aug 05, 2000 at 07:59:49PM -0400, Vladimir N. Silyaev wrote: > In muc.lists.freebsd.emulation, you wrote: > >I've been following this thread and learnt quite a bit from it, thanks > >guys, however I *still* can't get vmware to run :( > > > >It starts up but as soon as I click the Power On button the vmware > >window turns black and the whole machine locks solid (no keyboard or > >mouse response, and the desktop clock and xtimer stop) and after ~15 > >secs the machine spontaneously reboots (which is a PITA as it fsck's > >the disks every time). > 1. Checks date of the kernel, linux.ko and vmmon.ko, it should be in > descended order. thanks for the reply. % ls -lrt /kernel /modules/linux.ko /usr/local/lib/vmware/lib/modules/vmmon* -r-xr-xr-x 1 root wheel 2179331 20 Jul 21:02 /kernel -r-xr-xr-x 1 root wheel 79935 20 Jul 21:03 /modules/linux.ko -r-xr-xr-x 1 root wheel 36639 5 Aug 13:39 /usr/local/lib/vmware/lib/modules/vmmon_up.ko -r-xr-xr-x 1 root wheel 36800 5 Aug 13:39 /usr/local/lib/vmware/lib/modules/vmmon_smp.ko % I don't have vmmon.ko, only vmmon_smp.ko and vmmon_up.ko. Is this correct? (I built vmware with Makefile rev 1.19) > 2. Create new dummy configuration, without any hardware, and try it. It > useless, but at least you should see a Phoenix BIOS logo. > I'll give this a try. > If it doesn't help, that means you are have incompatible hardware > (never heard before about that). :( > > -- > Regards, > Vladimir -- If I buy a copy of WinDelete, and it doesn't delete Windows, am I entitled to my money back? ________________________________________________________________ 51.44°N FreeBSD - The Power To Serve http://www.freebsd.org 2.057°W My Webpage http://ukug.uk.freebsd.org/~mark mailto:marko@freebsd.org http://www.radan.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Sat Aug 5 17:46:50 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from mta01-svc.ntlworld.com (mta01-svc.ntlworld.com [62.253.162.41]) by hub.freebsd.org (Postfix) with ESMTP id D74B037B5FE for ; Sat, 5 Aug 2000 17:46:47 -0700 (PDT) (envelope-from mark@ukug.uk.freebsd.org) Received: from parish.my.domain ([62.253.84.77]) by mta01-svc.ntlworld.com (InterMail vM.4.01.02.27 201-229-119-110) with ESMTP id <20000806004646.CJCR26680.mta01-svc.ntlworld.com@parish.my.domain>; Sun, 6 Aug 2000 01:46:46 +0100 Received: (from mark@localhost) by parish.my.domain (8.9.3/8.9.3) id BAA00310; Sun, 6 Aug 2000 01:46:36 +0100 (BST) (envelope-from mark) Date: Sun, 6 Aug 2000 01:46:35 +0100 From: Mark Ovens To: vns@delta.odessa.ua Cc: emulation@FreeBSD.ORG Subject: Re: FreeBSD/VMWare setup for dummies? Message-ID: <20000806014635.A255@parish> References: <200007271242.IAA16126@pobox.engeast.BayNetworks.COM> <20000805150815.C254@parish> <200008052359.TAA00434@jupiter.delta.ny.us> 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: <200008052359.TAA00434@jupiter.delta.ny.us>; from vsilyaev@mindspring.com on Sat, Aug 05, 2000 at 07:59:49PM -0400 Organization: Total lack of Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Aug 05, 2000 at 07:59:49PM -0400, Vladimir N. Silyaev wrote: > > 2. Create new dummy configuration, without any hardware, and try it. It > useless, but at least you should see a Phoenix BIOS logo. > OK, I tried and it just rebooted again. This is the config file I was using: #!/usr/local/lib/vmware/bin/vmware config.version = 2 # No cdrom installed # Disk Drive Info # scsi0:0.present = TRUE # scsi0:0.deviceType = "plainDisk" # scsi0:0.fileName = "win95.hba" # scsi0.present = TRUE # No floppy installed # floppy0.present = FALSE # No networking installed # Memory size memsize = 32 # Nvram nvram = /usr/marko/.vmware/win95/win95.nvram # Log file log.fileName = /usr/marko/.vmware/win95/win95.log # Hints guestOS = win95 Is the win95.nvram file supposed to exist? I haven't got one on my system/ > If it doesn't help, that means you are have incompatible hardware > (never heard before about that). It's a K6-233 (original K6, not a -2 or -3) Gigabyte 430TX based motherboard, Award 4.51-PGM BIOS 64MB RAM 2 x 4.5GB IBM UW-SCSI on a Diamond Fireport 40 (Symbios 53c875j chip) controller. > > -- > Regards, > Vladimir -- If I buy a copy of WinDelete, and it doesn't delete Windows, am I entitled to my money back? ________________________________________________________________ 51.44°N FreeBSD - The Power To Serve http://www.freebsd.org 2.057°W My Webpage http://ukug.uk.freebsd.org/~mark mailto:marko@freebsd.org http://www.radan.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Sat Aug 5 19: 9:32 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from wop21.wop.wtb.tue.nl (wop21.wop.wtb.tue.nl [131.155.56.216]) by hub.freebsd.org (Postfix) with ESMTP id 38CB037B7C4 for ; Sat, 5 Aug 2000 19:09:29 -0700 (PDT) (envelope-from karelj@wop21.wop.wtb.tue.nl) Received: (from karelj@localhost) by wop21.wop.wtb.tue.nl (8.9.3/8.9.3) id EAA28238; Sun, 6 Aug 2000 04:09:18 +0200 (CEST) (envelope-from karelj) Date: Sun, 6 Aug 2000 04:08:57 +0200 From: "Karel J. Bosschaart" To: Mark Powell Cc: freebsd-emulation@FreeBSD.ORG Subject: Re: UT under FreeBSD 4.1-S Message-ID: <20000806040857.A28191@wop21.wop.wtb.tue.nl> Reply-To: K.J.Bosschaart@tue.nl References: <20000806000740.A27573@wop21.wop.wtb.tue.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from M.S.Powell@salford.ac.uk on Sun, Aug 06, 2000 at 01:04:46AM +0100 Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Aug 06, 2000 at 01:04:46AM +0100, Mark Powell wrote: > > Interesting. 20 questions... > Uses the Voodoo card too? Nice. Does it work with a V3? That would require > XFree86 4? It is slower than Win98? Any problems with mouse focusing. I > seem to remember back in the days I ran quake2 under FreeBSD that was a > problem. > I'm running UT with a Voodoo2 card and XFree 3.3.6, using the linux driver for the card and the tdfx device driver by Coleman Kane. I don't know how it works with a V3. On my machine, it's slower than in Win98. A quick comparison some while ago showed that in FBSD I had 18-19 FPS, in Win98 24-25. I tried to have everything (level, nr of bots, skill level of bots) the same but I might have overlooked things. Also, I should try running UT in twm instead of Windowmaker, with some dockapps that might consume CPU cycles. However, I doubt that I ever could reach the performance of Win98; The 24-25 was on the last few days of my Windows installation, being very crippled like is usual when you don't reinstall every three months. I remember that I usually had 29-30 on the same machine when the installation was a bit younger. Mouse focusing: no problems actually. > > However, I recently tried a network game and that didn't work :-(, though I'm > > sure that I once played a network game, most probably it was UT 4.00. > > Oh dear. That's quite an important part of it :( > Yep it is. Definitely. > Does it all no problem. The 4.25 patch is a little trickier. Uses binaries > and X interface to do the install. Haven't been able to get that working > yet. Let me know if you succeed. I'm going to look at it again. You could > quite easily patch it up under Linux and copy the filesystem across. Any > chance of making the changes it makes available somewhere? I realise this Got curious and tried it. Woowwie, what a wacky setup program. It must be very userfriendly and plug'n'play and such *grin*. I extracted the binaries in a separate directory and brandelf'ed the one that the setup program was complaining about, in some obscure subdirectory. Than run it manually, it says: ----====== Unreal Tournament for Linux installation program ======---- You are running a x86 machine with glibc-2.1 Hit Control-C anytime to cancel this installation program. Please mount the ut CDROM. Choose Yes to retry, No to cancel [N/y] ...and I'm stuck. I mounted the UT-CD on /cdrom, /mnt/cdrom and even run the program in a chroot'ed linux bash shell with the contents of the cd copied in /cdrom but it keeps complaining that it wants the cdrom mounted. > will be a largish tar file as it'll probably modifiy those 40MB files a > little. Downloading something that big is no problem, if you could put it > up somewhere? If I succeed in getting it running... Enough for now, need some sleep, Karel. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message