All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Pollard <pollard@admin.navo.hpc.mil>
To: "Alexandre Pires" <linux_kernel_br@yahoo.com.br>,
	<linux-kernel@vger.kernel.org>
Subject: Re: Modules and dll
Date: Thu, 12 Dec 2002 10:17:56 -0600	[thread overview]
Message-ID: <200212121017.56923.pollard@admin.navo.hpc.mil> (raw)
In-Reply-To: <03d501c2a1fe$7b371dd0$6400a8c0@sawamu>

On Thursday 12 December 2002 10:49 am, Alexandre Pires wrote:
> Hi,
>
>     We could compare the modules programs of linux with dlls of Windows ?
> Exist many differences between them (in relation to the functioning) ?

no. Windows DLLs are more like shared libraries. They are easily replaced (if
inactive), and do not directly destroy the system if missing.

DLLs are connected to applications via subroutine calls (Win DLL and shared 
libraries), modules are usually accessed via special files, or system calls. 
There is no direct linking (by memory mapping the module code to the user 
mode application). Shared libraries are done this way.

Modules are closer to the device drivers in windows, which is what most
modules support. They can also support extending the OS by adding
additional capabilities - TCP/IP, IPv4, and IPv6 come to mind as some of the
most used, followed by the loadable binary interpretation (elf vs a.out).

Another difference is the way they are used - modules are loaded into
kernel mapping either by a kernel resident loader, or a userspace tool that
does the same. Shared libraries and DLLs are just put on disk where the
applications have been linked to expect them (or use an environment
variable to provide a search list of places to look when the application is
run.

-- 
-------------------------------------------------------------------------
Jesse I Pollard, II
Email: pollard@navo.hpc.mil

Any opinions expressed are solely my own.

  reply	other threads:[~2002-12-12 16:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-12 16:49 Modules and dll Alexandre Pires
2002-12-12 16:17 ` Jesse Pollard [this message]
2002-12-12 16:23 ` Richard B. Johnson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200212121017.56923.pollard@admin.navo.hpc.mil \
    --to=pollard@admin.navo.hpc.mil \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux_kernel_br@yahoo.com.br \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.