From: Daniel Jacobowitz <dan@debian.org>
To: "Bradley D. LaRonde" <brad@ltc.com>
Cc: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>,
"MIPS/Linux List (SGI)" <linux-mips@oss.sgi.com>
Subject: Re: Can modules be stripped?
Date: Fri, 12 Apr 2002 20:27:46 -0400 [thread overview]
Message-ID: <20020412202746.A14017@nevyn.them.org> (raw)
In-Reply-To: <012f01c1e250$c93fb0a0$4c00a8c0@prefect>
On Fri, Apr 12, 2002 at 02:35:13PM -0400, Bradley D. LaRonde wrote:
> ----- Original Message -----
> From: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
> To: "Bradley D. LaRonde" <brad@ltc.com>
> Cc: "MIPS/Linux List (SGI)" <linux-mips@oss.sgi.com>
> Sent: Friday, April 12, 2002 2:05 PM
> Subject: Re: Can modules be stripped?
>
>
> > On Fri, 12 Apr 2002, Bradley D. LaRonde wrote:
> >
> > > OK, you can't strip kernel modules (news to me, then again how often do
> I
> > > use modules?), but it can't be because they "are relocatables". I
> routinely
> > > strip libraries without problem, and those are relocatables too.
> >
> > What kind of libraries? Shared libraries are shared objects and not
> > relocatables.
>
> Oh, oops. :-P Now I see what you mean. I confused shared object
> w/relocatable. My bad.
>
> Did I know that kernel modules were "object files" i.e. relocatables. Yes.
> But I've always referred to them as object files (.o), not relocatables,
> hence the confusion.
>
> Which brings up an interesting question - why doesn't the kernel use .so
> files for modules?
If you're really curious, compare the gunk in insmod (quite a bit) with
the gunk in ld.so (unspeakable). Shared libraries are a great deal
more complicated than modules need to be.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-04-13 0:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-12 17:41 Can modules be stripped? Scott A McConnell
2002-04-12 16:56 ` Stuart Hughes
2002-04-13 0:40 ` Ian Chilton
2002-04-12 16:57 ` Maciej W. Rozycki
2002-04-12 17:48 ` Bradley D. LaRonde
2002-04-12 18:05 ` Maciej W. Rozycki
2002-04-12 18:35 ` Bradley D. LaRonde
2002-04-12 18:44 ` Maciej W. Rozycki
2002-04-13 0:27 ` Daniel Jacobowitz [this message]
2002-04-13 1:14 ` Keith Owens
2002-04-15 14:21 ` Maciej W. Rozycki
2002-04-15 14:50 ` Keith Owens
2002-04-15 15:32 ` Maciej W. Rozycki
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=20020412202746.A14017@nevyn.them.org \
--to=dan@debian.org \
--cc=brad@ltc.com \
--cc=linux-mips@oss.sgi.com \
--cc=macro@ds2.pg.gda.pl \
/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