Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-Id: <5.2.0.9.2.20030224225919.02dcc990@pop3.cris.com> X-Sender: rrschulz AT pop3 DOT cris DOT com Date: Tue, 25 Feb 2003 08:06:17 -0800 To: cygwin AT cygwin DOT com From: Randall R Schulz Subject: Re: loopback devise (was Re: mknod implementation? ... ) In-Reply-To: <3.0.5.32.20030225004921.00f3b760@mail.earthlink.net> References: <20030225013751 DOT GB24688 AT redhat DOT com> <5 DOT 2 DOT 0 DOT 9 DOT 2 DOT 20030224134817 DOT 0299ae90 AT pop3 DOT cris DOT com> <5 DOT 2 DOT 0 DOT 9 DOT 2 DOT 20030224130818 DOT 01dae398 AT pop3 DOT cris DOT com> <5 DOT 2 DOT 0 DOT 9 DOT 2 DOT 20030224134817 DOT 0299ae90 AT pop3 DOT cris DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Robert, I don't think a loopback device in Cygwin would get you anywhere. Cygwin doesn't implement file systems. It's notion of "mounting" is very different from that of Unix or even Windows. A Cygwin mount is just a kind of name mapping, really (with a few options attached to the mount such as default file access mode, in the text vs. binary sense). Even if you had a file system image in a file (even if it was a file system format supported by Windows), a loopback device supported by Cygwin wouldn't get you anywhere. Possibly Windows itself would be amenable to this concept of a loopback driver, but the loopback driver would have to be a Windows driver. If you had a Windows loopback driver and a Linux file system image file, you'd still be stuck, since Windows includes no file system driver for non-Windows file systems (though there may well be 3rd-party drivers for that purpose). Randall Schulz At 22:49 2003-02-24, Robert Citek wrote: >At 08:37 PM 2/24/2003 -0500, Christopher Faylor wrote: > >On Mon, Feb 24, 2003 at 01:52:15PM -0800, Randall R Schulz wrote: > >>Does Cygwin have a loopback block device? > > > >No. > > > >As Randall correctly points out, the existence of the mknod command has > >no bearing on the existence of functionality like a loopback device. > >Are there plans to include the functionality of a loopback device in future >releases of Cygwin? If so, what can I do to help that process along? Keep >in mind I am not a systems programer. > >Regards, >- Robert -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/