From owner-freebsd-emulation Tue Dec 7 21:20: 5 1999 Delivered-To: freebsd-emulation@freebsd.org Received: from smtp6.mindspring.com (smtp6.mindspring.com [207.69.200.110]) by hub.freebsd.org (Postfix) with ESMTP id 18F8014FB7 for ; Tue, 7 Dec 1999 21:20:02 -0800 (PST) (envelope-from vsilyaev@mindspring.com) Received: from mindspring.com (user-2iniie3.dialup.mindspring.com [165.121.73.195]) by smtp6.mindspring.com (8.9.3/8.8.5) with ESMTP id AAA06068; Wed, 8 Dec 1999 00:19:59 -0500 (EST) Received: (from vsilyaev@localhost) by mindspring.com (8.9.3/8.9.3) id AAA07048; Wed, 8 Dec 1999 00:19:57 -0500 (EST) (envelope-from vsilyaev) Date: Wed, 8 Dec 1999 00:19:56 -0500 From: "Vladimir N. Silyaev" To: Alex Cc: "Vladimir N. Silyaev" , freebsd-emulation@FreeBSD.ORG Subject: Re: VMware and CDROM was (Re: Linux ioctl not implemented error) Message-ID: <19991208001955.F6719@jupiter.delta.ny.us> References: <19991204210435.D881@jupiter.delta.ny.us> <199912051018.LAA66515@yedi.iaf.nl> <19991205110930.A469@jupiter.delta.ny.us> <384ACA77.9EFC2391@freenet.co.uk> <384AFF3A.B2773CB7@freenet.co.uk> <19991206000007.B1918@jupiter.delta.ny.us> <384D5090.6F70CAD@freenet.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <384D5090.6F70CAD@freenet.co.uk>; from ak@freenet.co.uk on Tue, Dec 07, 1999 at 06:23:12PM +0000 Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Dec 07, 1999 at 06:23:12PM +0000, Alex wrote: > There's one odd thing, though. Every time I start VMware, it complains > about not being able to lock the file: > > "An error occurred while attempting to lock disk /usr/solaris. VMware [skipped] Yes. I think it's because before locking file, vmware tried to guess filesystem type, and when it's don't like this type, the vmware ever don't try to locking. I have such means, because vmware said more information, when tried to lock serial tty's. > > Oh no, don't do such things. When you use raw device it must be > > a real IDE drive and (probably) block, not character device. > > I don't see why not. In fact, I used the vn0c device to mount a boot > floppy image, and specifying /dev/vn0c instead of /dev/fd0 in VMware > seems to work. I'm also don't know. Just a fact, vmware like block wd0, and don't like character ad0 or rwd0. And I think vmware don't have such testing about floppy driver, or at the time when loaded partition table from IDE drive. -- Vladimir Silyaev To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message