From mint-bounce@lists.fishpool.fi Thu May 5 01:10:32 2005 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de Message-ID: <42795536.90405@seznam.cz> Date: Wed, 04 May 2005 19:05:26 -0400 From: Standa Opichal User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: mint@fishpool.com Subject: Re: [MiNT] Loopback device for MiNT, request for comments References: <20050429203536.75299a02.mandin.patrice@wanadoo.fr> <20050430112745.4f25da2b.mandin.patrice@wanadoo.fr> <2005 In-Reply-To: <1115229765.4007.25.camel@taro.coolrunningconcepts.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-To: mint-bounce@lists.fishpool.fi X-original-sender: opichals@seznam.cz Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: X-Virus-Scanned: by amavisd-new at relay.boerde.de X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on relay.boerde.de X-Spam-Status: No, hits=-0.5 tagged_above=-50.5 required=7.0 tests=AWL, BAYES_00 X-Spam-Level: Hi! Well, Frank probably thought that it is not possible to mount a filesystem over a block device at the moment. But the work is in progress. So please, don't give up. Regards STanda Evan Langlois wrote: > On Wed, 2005-05-04 at 17:26 +0200, Patrice Mandin wrote: > > >>>>If not, how can I access the kernel_* functions from a xdd ? >>> >>>You are right, they are only exported to the new style kernel >>>interface (not the old one as still used by xfs/xdd). Anyway, before >>>you can write a loopback driver we require block device support in >>>the kernel too. >> >>Even putting the loop device in the core kernel (like /kern, /shm, >>etc...) would not work without this block device ? So, I'm stuck with my >>idea, no loopback device for MiNT. > > > MiNT probably needs a block device driver eventually. We may even be > able to gain a slight speed improvement. However, doing it right might > require a certain integration with the as-yet-unwritten virtual address > space / virtual-memory system. > > >