From owner-freebsd-emulation Wed Feb 9 1: 9:13 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from quack.kfu.com (quack.kfu.com [170.1.70.2]) by builder.freebsd.org (Postfix) with ESMTP id 1AF334447 for ; Tue, 8 Feb 2000 23:58:38 -0800 (PST) Received: from icarus.kfu.com (icarus.kfu.com [170.1.70.17]) by quack.kfu.com (8.9.2/8.9.3) with ESMTP id XAA44272; Tue, 8 Feb 2000 23:58:03 -0800 (PST) (envelope-from nsayer@quack.kfu.com) Received: from quack.kfu.com by icarus.kfu.com with ESMTP (8.9.3//ident-1.0) id XAA16960; Tue, 8 Feb 2000 23:58:02 -0800 (PST) Message-ID: <38A11E0A.25D0EF3A@quack.kfu.com> Date: Wed, 09 Feb 2000 07:58:02 +0000 From: Nick Sayer X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Vladimir N. Silyaev" Cc: freebsd-emulation@freebsd.org Subject: Re: VMWare: booting existing device ... References: <20000208235718.A607@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: > > >> Went into Wizard Configuration, choose `Existing Device`, and choose the > >> right partition (/dev/hda1), but it tells me `permission denied` to this > >> ... > > > >> 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. > [...] > 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. > > 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. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message