From mint-bounce@lists.fishpool.fi Wed May 4 17:28:07 2005 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de X-ME-UUID: 20050504152550241.3AD7E2800153@mwinf1007.wanadoo.fr Date: Wed, 4 May 2005 17:26:57 +0200 From: Patrice Mandin To: Mint list Subject: Re: [MiNT] Loopback device for MiNT, request for comments Message-Id: <20050504172657.20fca75b.mandin.patrice@wanadoo.fr> In-Reply-To: References: <20050429203536.75299a02.mandin.patrice@wanadoo.fr> <20050430112745.4f25da2b.mandin.patrice@wanadoo.fr> Organization: Chez moi X-Mailer: Sylpheed version 1.0.0 (GTK+ 1.2.10; i586-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-To: mint-bounce@lists.fishpool.fi X-original-sender: mandin.patrice@wanadoo.fr 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=2.0 tagged_above=-50.5 required=7.0 tests=AWL, BAYES_00, RCVD_IN_SORBS X-Spam-Level: ** Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by wh58-508.st.uni-magdeburg.de id j44FS7oJ016764 Le Wed, 4 May 2005 14:39:22 +0200 (CEST) Frank Naumann a écrit: > As I said, this don't work as the syscalls are context dependant, e.g. > > the syscalls operate in a process context and only modify the process > context. So if you open a file in the context of process A you can > only access the file from process A. Process B don't know anything > about these open file. Damn, the kernel can not open any file for itself ? > > 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. -- Patrice Mandin WWW: http://membres.lycos.fr/pmandin/ Programmeur Linux, Atari Spécialité: Développement, jeux