Message-ID: <417FE922.7080009@ece.northwestern.edu>
Date: Wed, 27 Oct 2004 13:29:54 -0500
From: Lei Yang <lya755@ece.northwestern.edu>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.2) Gecko/20040921
MIME-Version: 1.0
To: linux-kernel@vger.kernel.org
Cc: Lei Yang <lya755@ece.northwestern.edu>
Subject: Re: loopback on block device
References: <417FE703.3070608@ece.northwestern.edu>
In-Reply-To: <417FE703.3070608@ece.northwestern.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 936
Lines: 29

Please cc me if you have answers to this, I am not on the list. Thanks a 
lot!

Lei Yang wrote:

> Hello,
>
> Here is a question for loopback device. As far as I understand,  the 
> loopback device is used to mount files as if they were block devices.
>
> Then Why I could do "losetup -e XOR /dev/loop0 /dev/ram0" ? Notice 
> that ram0 is not mounted anywhere and does not have a filesystem on 
> it. I've tried that command and there seems to be no error. I got 
> confused and looked into loop.c, it seems to me that a loopback device 
> should be associated with a "backing file", why would it work on a 
> block device anyway?
>
> I'd appreciate your comments greatly!
>
> TIA,
> Lei
>


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/