From mint-bounce@lists.fishpool.fi Thu Dec 24 05:27:20 2009 X-Auth-Info: KwrV1lXPTr3TXAqi/qGYaxYDFOPddy6dXDqSRZNQHFI= From: Andreas Schwab To: Vincent =?utf-8?Q?Rivi=C3=A8re?= Cc: mint Subject: Re: [MiNT] patch:MiNT:KM_FREE References: <876828.589567111-sendEmail@descaro> <1261608023.16683.593.camel@jetpack.demon.co.uk> <4B32A4C5.7030905@freesbee.fr> X-Yow: PARDON me, am I speaking ENGLISH? Date: Thu, 24 Dec 2009 11:04:30 +0100 In-Reply-To: <4B32A4C5.7030905@freesbee.fr> ("Vincent =?utf-8?Q?Rivi=C3=A8?= =?utf-8?Q?re=22's?= message of "Thu, 24 Dec 2009 00:16:21 +0100") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.90 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: schwab@linux-m68k.org Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.sparemint.org id nBOARE99024126 Vincent Rivière writes: > For loading modules, the modprobe command takes the basename of a > module (filename without extension) and search for it in a well-known > directory, if it has not already been loaded. Direct use of modprobe with a module name is rare these days. Normally a module is located via matching aliases stored in a special section of the module so that the name does not matter. > What happens on Linux if some pervert renames a module and tries to > load it 2 times ? You'll probably get a resource conflict (since the loaded module is already claiming it) and the module will not load. Andreas. -- Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."