From mint-bounce@lists.fishpool.fi  Mon Dec 14 01:26:17 2009
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:received:in-reply-to:references
         :date:message-id:subject:from:to:content-type;
        bh=+D/EQTg6bLJpyommoySRWpc6WuGh+7e1RIk5JrZF+xc=;
        b=kK5R8+/3x3TrX4a9h/AUwiCjwCNnOCbBMu1AoVPKBP/8PGcXBK306ntPka5zju8vs/
         LMN4ePSGoB3uSxYonbWLl38GeBtNGsT0DBPT+2ebJDtH4EONL8xcUnS2m6jf98pyAfOV
         gE10m+rgCBA0ib3px2MspaPw6uK2sIWKJoAuk=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=gf6KJhH663s5MPXs9JRtv7EXd2DdBcJnsunFon9ZRXli4aaKA450yVDuhABTuMuW1M
         9IFrla3rLwWZYVDIpO28xcl3TksQrOxYjkGM7Fu/2Y0k+7zW2R6rbm/KHvmUrdud4YIZ
         x7IyWmzFZKB8/8VH3HFb0Yu0fG6AF6AeCJn6I=
MIME-Version: 1.0
In-Reply-To: <op.u4wzj2y943ni9l@descaro.cpe.ish>
References: <733893.001775385-sendEmail@descaro>
	 <1260743976.20336.1266.camel@jetpack.demon.co.uk>
	 <op.u4wzj2y943ni9l@descaro.cpe.ish>
Date: Mon, 14 Dec 2009 17:24:10 +1100
Message-ID: <11a6f2b10912132224pd7cd8ag19eebe55fb24cd6f@mail.gmail.com>
Subject: Re: [MiNT] patch:MiNT:KM_FREE
From: Paul Wratt <paul.wratt@gmail.com>
To: mint <mint@lists.fishpool.fi>
Content-Type: text/plain; charset=ISO-8859-1
X-ecartis-version: Ecartis v1.0.0
Sender: mint-bounce@lists.fishpool.fi
Errors-to: mint-bounce@lists.fishpool.fi
X-original-sender: paul.wratt@gmail.com
Precedence: bulk
List-help: <mailto:ecartis@lists.fishpool.fi?Subject=help>
List-unsubscribe: <mailto:mint-request@lists.fishpool.fi?Subject=unsubscribe>
List-Id: <mint.lists.fishpool.fi>
X-List-ID: <mint.lists.fishpool.fi>
List-subscribe: <mailto:mint-request@lists.fishpool.fi?Subject=subscribe>
List-owner: <mailto:tjhukkan@fishpool.fi>
List-post: <mailto:mint@lists.fishpool.fi>

On Mon, Dec 14, 2009 at 5:13 PM, Helmut Karlowski <hk10@gmx.de> wrote:
> Am 13.12.2009, 23:39 Uhr, schrieb Alan Hourihane <alanh@fairlite.co.uk>:
>
>> What happens if you just rename a module a try to load it ?
>
> Then the renamed one is loaded.
>
>> I'd like something a little more robust than just using a filename.
>
> I've mentioned this in my first posting - but this is how it's implemented.
>
> -Helmut
>
is this one part of the KM that need to be reworked. I would say a
file pointer should be enough, but only if its "siganure" says its not
already loaded. Can the filename be used in combo with app_id, or is
that strictly AES only..

What circumstance should it be possible to load two modules that are
the same. Certain other kernels do allow this if the KM handles
multiple "things".

I thing there may be a need for a functioning KM skeleton (or similar)
to allow co-exist, order and unload testing, including km reloading

would a modprobe type tool for MiNT be of any use?

Paul