Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 11 Mar 2001 22:06:04 -0500
From:      The Babbler <bts@babbleon.org>
To:        Josef Karthauser <joe@tao.org.uk>, John Sellens <jsellens@generalconcepts.com>, emulation@freebsd.org
Subject:   Re: vmware networking & sysmouse
Message-ID:  <3AAC3D1C.FB6FA0EB@babbleon.org>
References:  <200103112208.f2BM88L85365@gc0.generalconcepts.com> <20010311221123.B1541@tao.org.uk> <3AABF9DF.5E3C6E1F@babbleon.org>

next in thread | previous in thread | raw e-mail | index | archive | help
The Babbler wrote:
> 
> Josef Karthauser wrote:
> >
> > On Sun, Mar 11, 2001 at 05:08:08PM -0500, John Sellens wrote:
> > > I had the same /dev/sysmouse complaint, and then I adjusted my
> > > configuration (based on someone else's config), and all was
> > > happy happy.
> > >
> > > I have a laptop with a ps/2 mouse.  My mouse configuration in vmware is:
> > >   type ps/2
> > >   specify
> > >   /dev/sysmouse
> > > My /dev/sysmouse is this:
> > >     crw-------  1 root  wheel   12, 128 Dec 31 05:36 /dev/sysmouse
> > > I don't appear to have any mouse-related deviced in /compat/linux/dev,
> > > and I'm not running moused.  My XF86Config has PS/2 and /dev/psm0
> > > for the pointer.
> >
> > I'm sure that it will work if I change to /dev/psm0, but I do use moused
> > and therefore my X11 is configured to use sysmouse.
> >
> > Joe
> >
> >   ------------------------------------------------------------------------
> >    Part 1.2Type: application/pgp-signature
> 
> I changed mine to use /dev/pcm0 and I still get the complaints.  Not
> that big a deal, just a minor annoyance. The fact that I can't get
> networking working is more of a problem . . .

I should have tried this before my previous mail, but . . . I changed it
to type ps/2; chose device as /dev/mouse (this is the same as
/dev/sysmouse but seems more sensible since I'm not running moused), and
sure enough, it got rid of the requester.  Thanks.

As for my networking, I reverted to the older port of vmware (the one
from the 4.2-RELEASE), and that fixed my problem with not being able to
network to the host _at_all_.  I'm just going to do this the
"old-fashioned way" and set up IP forwarding rules on the host myself. 
My experimentation with bridging and all that has been a disaster and a
*huge* waste of time, so I'll just do the way I did it on Linux.

And I gather that nobody's figued out how to turn off /dev/rtc by
default?  I tried denying non-root users read permission, or granting
them write permission, to /compat/linux/dev/rtc, but that didn't stop
the 100% CPU problem.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-emulation" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3AAC3D1C.FB6FA0EB>