public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: EXPORT_NO_SYMBOLS vs. (null) ?
Date: Sat, 18 Nov 2000 18:40:13 +1100	[thread overview]
Message-ID: <21341.974533213@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Sat, 18 Nov 2000 00:15:35 CDT." <3A161077.7C94EC6E@mandrakesoft.com>

On Sat, 18 Nov 2000 00:15:35 -0500, 
Jeff Garzik <jgarzik@mandrakesoft.com> wrote:
>What is the difference between a module that exports no symbols and
>includes EXPORT_NO_SYMBOLS reference, and such a module that lacks
>EXPORT_NO_SYMBOLS?

When modules were first introduced, all symbols were automatically
exported.  For kernel 2.0 compatibility, a module without
EXPORT_NO_SYMBOLS actually exports everything.  There are flags on
insmod to override this default.  modutils 2.5 will remove this
backwards compatibility, no module will export symbols unless they are
explicitly exported.  If you are feeling brave, add
  insmod_opt=-x
to your modules.conf and see what breaks in 2.4.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-11-18  8:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-18  5:15 EXPORT_NO_SYMBOLS vs. (null) ? Jeff Garzik
2000-11-18  7:40 ` Keith Owens [this message]
2000-11-18 17:12 ` Alan Cox
2000-11-18 17:40   ` Rogier Wolff
2000-11-18 17:45     ` Jeff Garzik
2000-11-18 17:50       ` Rogier Wolff
2000-11-18 18:44         ` Jeff Garzik
2000-11-19  8:12         ` Keith Owens

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=21341.974533213@ocs3.ocs-net \
    --to=kaos@ocs.com.au \
    --cc=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox