As Louis A. Mamakos wrote ...
> > >The console complaints about the ioctl are gone now. Unfortunately VMware
> > >still complains. I'll try to findout why.
> >
> > Try to load new vmware port from:
> > http://www.mindspring.com/~vsilyaev/vmware/files/vmware.tar.gz
> >
> > And reinstall it. I think this may fix the problem.
> >
>
> I'm trying the new port now. I seem to have a problem with the
> vmware emulator program dying due to some panic caused by an
> uncaught signal whenever I try to save a configuration.
Same here. But that also happened with the pre-Dec 1, 1999 version.
Does not happen always, sometimes it works. I have not yet found
a pattern.
> Right now, I opted to not save the configuration, and have proceeded
> on to booting a FreeBSD-3.3 release CDROM, and installing it in a
> VMware virtual machine. This is great. I dunno if it's just me,
> but this seems to provoke manical laughter from time to time.
Well, no manical laughter here yet. I still get "does not
appear to be a cdrom device". Looks like I have some kind of config
mistake here. What do people use for the /dev entry? /dev/wcd0a ?
> Next up: how long to do a 'make world' of the 3.3 system inside the
> emulator.
Blurk.. ;-)
> So, is there a working network interface for the virtual machine? That
> would be very nifty, indeed.
Vladimir's web page they don't work:
"
- All networking
This require FreeBSD version of vmnet driver
"
Wilko
--
| / o / / _ Arnhem, The Netherlands - Powered by FreeBSD -
|/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
