Date: Fri, 26 Sep 2003 18:06:20 -0500 From: "Andrew L. Gould" <algould@datawok.com> To: "Timms, Simon" <STimms@petro-canada.ca>, 'Kris Kennaway' <kris@obsecurity.org>, Adam McLaurin <blueeskimo@gmx.net> Cc: freebsd-questions@freebsd.org Subject: Re: FreeBSD in Windows..... Message-ID: <200309261806.20319.algould@datawok.com> In-Reply-To: <BB28669D4974D311B4A00008C75D1CF910FB88BB@pcaxs02.pcacorp.net> References: <BB28669D4974D311B4A00008C75D1CF910FB88BB@pcaxs02.pcacorp.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday 26 September 2003 04:51 pm, Timms, Simon wrote: > -----Original Message----- > From: Kris Kennaway [mailto:kris@obsecurity.org] > Sent: Friday, September 26, 2003 3:41 PM > To: Adam McLaurin > Cc: freebsd-questions@freebsd.org > Subject: Re: FreeBSD in Windows..... > > >On Fri, Sep 26, 2003 at 05:32:40PM -0400, Adam McLaurin wrote: > >> On Fri, 2003-09-26 at 17:17, Kris Kennaway wrote: > >> > That won't help the OP. He's asking how to access a FreeBSD UFS _on > >> > the same computer_ while running Windows. Unless you can purchase a > >> > Windows UFS driver somewhere out there, this is not possible. The > >> > recommended way to share files from FreeBSD to Windows on a dual-boot > >> > OS is to use a FAT partition which can be mounted on both OSes. > >> > >> What about installing vmware (on XP), then install FreeBSD in vmware, > >> and mounting it that way? Maybe a lot of trouble, but at least he'd be > >> able to get at the data. > > > >Yeah, that might work. > > > >Kris > > If my understanding of vmware is correct that shouldn't work, couldn't > work. Vmware is just an x86 emulator which sits on top of windows, the OS > working in > VMware should be unaware that it is running in an emulator and shouldn't > have > direct access to any of the host computer's resources. If the host system > is unable to mount a file system then the operating system in vmware should > also be unable to mount it. First because it is unaware that it exists and > second because vmware uses the host system's resources and anything which > is inaccessible to the host system would also be inaccessible to the > emulated system. > Actually, I worked around that problem once running Win98 via Virtual PC on Mac OS X on an iBook. I had to network the operating systems using 2 ethernet ports. The looped cable made my ibook look funny; but MS Access could link to the databases in OS X via ODBC through the connection. Samba shouldn't be any different. Each operating system had a different ethernet interface configured to the same network so they can communicate with each other. Since Win98 insisted on recognizing both ethernet interfaces at bootup, the Win98 side of the ethernet interface used by OS X had to be configured to a different network. Clear as mud? Have fun, Andrew Gould
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200309261806.20319.algould>