From owner-freebsd-emulation Wed Feb 9 18:53:11 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from fb01.eng00.mindspring.net (fb01.eng00.mindspring.net [207.69.229.19]) by builder.freebsd.org (Postfix) with ESMTP id 2552C4183 for ; Wed, 9 Feb 2000 18:53:06 -0800 (PST) Received: from mindspring.com (user-2iveaib.dialup.mindspring.com [165.247.42.75]) by fb01.eng00.mindspring.net (8.9.3/8.8.5) with ESMTP id VAA30411; Wed, 9 Feb 2000 21:52:20 -0500 (EST) Received: (from vsilyaev@localhost) by mindspring.com (8.9.3/8.9.3) id VAA00719; Wed, 9 Feb 2000 21:52:30 -0500 (EST) (envelope-from vsilyaev) Date: Wed, 9 Feb 2000 21:52:29 -0500 From: "Vladimir N. Silyaev" To: Nick Sayer Cc: "Vladimir N. Silyaev" , freebsd-emulation@freebsd.org Subject: Re: VMWare: booting existing device ... Message-ID: <20000209215229.A600@jupiter.delta.ny.us> References: <20000208235718.A607@jupiter.delta.ny.us> <38A11E0A.25D0EF3A@quack.kfu.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <38A11E0A.25D0EF3A@quack.kfu.com>; from nsayer@quack.kfu.com on Wed, Feb 09, 2000 at 07:58:02AM +0000 Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Feb 09, 2000 at 07:58:02AM +0000, Nick Sayer wrote: > > >> Is there something that I have to do in order to allow a `normal user` to > > >> be able to access that file system? > > > 1. It is a security hole, but if you`re willing to put up with it, you can > > > chgrp g+w the device and then make sure you`re a member of the `operator` > > > group. > > Probably last sentence about group membership doesn't required, because > > wizard launched from the setuid'ed vmware. > > Except that it relinquishes those privileges when opening the device. > If you don't have write access to the device as your own UID, you can't > use it. May be I can open it in read-only mode? I'm sure that it's more than enough for vmware-wizard. > > > [...] > > In 1.1.x release vmware configuration panel and vmware-wizard doesn't concerned > > about type of device. Probably a type of device is checked at a time when > > guest booted. I think that doesn't changed in 2.0 version. > > It must have. Using a character device for hda fails. I was tested right now, in vmware configuration panel you are can specify /dev/da0 as a device name and this is working pretty fine. But vmware complained at the time when guest started. > > > > About FreeBSD and block devices, right now new-ATA driver doesn't have > > a differences between character and block devices and working pretty > > well with inode marked as block device, but as block devices > > going to be deprecated may be good solution will be remove a sense of > > a device type, and in the kernel don't pay attention to the state > > of device type in the inode. > > I do admit that I was using a block device with the major number of the > character device for ata. Perhaps ata has a different major number for > block devices than character devices. I haven't checked this out. Yes, you are right. A block device use major number 0 (why ??), but real ad0 has other numbers, and when specify major number from an ad0 device, generated error 'device not configured'. -- Vladimir Silyaev To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message