From owner-freebsd-emulation Fri Oct 4 13:46: 2 2002 Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 95AF937B401 for ; Fri, 4 Oct 2002 13:46:01 -0700 (PDT) Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id A4C9F43E6A for ; Fri, 4 Oct 2002 13:46:00 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.12.1/8.12.1) with ESMTP id g94Kjr20108100; Fri, 4 Oct 2002 16:45:53 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20021004100436.GA1888@laptop.6bone.nl> References: <200210030904.aa81031@salmon.maths.tcd.ie> <20021003081152.GB584@laptop.6bone.nl> <20021004100436.GA1888@laptop.6bone.nl> Date: Fri, 4 Oct 2002 16:45:53 -0400 To: Mark Santcroos From: Garance A Drosihn Subject: Re: vmware reads disk on non-sector boundary Cc: emulation@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: MIMEDefang 2.3 (www dot roaringpenguin dot com slash mimedefang) Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org At 12:04 PM +0200 10/4/02, Mark Santcroos wrote: >On Thu, Oct 03, 2002, Garance A Drosihn wrote: > > Hmm. I might not be any good for the raw-disk testing. All I use >> are virtual disks. (I have a 32-gig disk with a bunch of 2-gig >> virtual-disks on it. With that many systems, it's much easier for >> me to deal with files than a whole bunch of "small" partitions on >> the raw disk). > >But how do you manage your virtual disks? AFAIK you can only access >them from within vmware. Or is that just enough for you? Yes, that works fine for my vmware needs. Much of my vmware usage is just to fire up some version of unix to do a quick test of some user-land code that I'm writing. So, I'm not really "managing" the systems, in the sense of doing system upgrades and stuff. They are meant to be a frozen snapshot of some system release, and the only times I need to access any files on them is while the virtual-system is up and running. In addition, I found that there was enough of a difference between my real hardware and the VMware virtual hardware that it was practically impossible to get a single system image which worked right in both settings (at least for windows). Every time I switched between "real" and "virtual", Windows would discover new hardware and have to reboot a few extra times. It was more of a hassle than it was worth. I tried to do that for awhile, but eventually I reformatted that drive to be all freebsd partitions. [I need Windows for one STUPID web-application which ONLY works with IE on Windows. As long as I can get to that app via vmware, then I can keep my dual-processor office PC running FreeBSD] -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message