mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "ChristianK."@t-online.de (Christian Koenig)
To: Richard Todd <richardt@vzavenue.net>
Cc: linux-kernel@vger.kernel.org, richardt@vzavenue.net
Subject: Re: [PATCH] Making vmlinux Multiboot compliant and grub capable of loading modules at boot time. (1 Part)
Date: Sun, 9 Dec 2001 23:17:18 +0100	[thread overview]
Message-ID: <16DCEp-0PsFKCC@fwd01.sul.t-online.com> (raw)
In-Reply-To: <16ChzA-1vH6GWC@fwd01.sul.t-online.com> <20011210015114.A1003@localhost.localdomain>
In-Reply-To: <20011210015114.A1003@localhost.localdomain>

Hi,

On Monday 10 December 2001 02:51, Richard Todd wrote:
> On Sat, Dec 08, 2001 at 02:59:18PM +0100, Christian Koenig wrote:
> > The patch is for 2.4.14 Kernel Source, but it should patch well on other
> > Versions (at least the module loader).
>
> It patched 2.5.1-pre8 cleanly, except for a makefile.  I'm running
> 2.5.1-pre8 with this patch right now.
>
> > I know that vmlinux isn't compressed and contains unused elf-sections.
>
> Just 'gzip -9 vmlinux'  Grub will uncompress it for you.
> This actually makes for a smaller file than bzImage (on
> my machine, anyway).
>
> Are the unused sections taking up space at runtime?

No, its only the .note & .comment section.

objcopy -R .note -R .comment  -S vmlinux mImage
gzip -9 mImage

makes a very nice & small Kernel Image.

(This will always be smaller than bzImage, 
because the compression / bsetup and bootsector code isn't inside the Kernel).

> > Tell me what you thing about it.
>
> It's a cool hack!  I like grub's module loading mechanism
> better than the initrd solution.

:-)

>
> Unfortunately, grub doesn't run on all supported platforms.
> And the multiboot specification isn't an accepted standard.
> (grub docs just read like it is.....)

The Module loader isn't really grub specified, 
at least do you know any bootloader who works on every platform 
Linux supports ?

And what's wrong with the multiboot specification ?
OK it is highly i386 Specified, but it defines the minimal things a 
boot-loader should do for the kernel (multiple Kernel Modules, a commandline, 
a memorymap ....). 

The main problem with my patch for the moment is that the code I have copied 
from insmod is really ugly. 
For example obj_load.c allocates memory without freeing it after an error 
(i have fixed this, but i think it's only 1 of 100 memory leaks this code 
have).

This works in an elf-program quiet well, but you can't do that inside the 
Kernel.

Somebody with real god knowledge off elf-object files should take a look at 
this 

MfG, Christian König.

I can not promise you that this patch work, but i can promise you i will 
do my best to make it working. (Sorry for my poor English).

      reply	other threads:[~2001-12-09 22:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-08 13:59 Christian Koenig
2001-12-10  1:51 ` Richard Todd
2001-12-09 22:17   ` Christian Koenig [this message]

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=16DCEp-0PsFKCC@fwd01.sul.t-online.com \
    --to="christiank."@t-online.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richardt@vzavenue.net \
    /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

all inboxes | Powered by JetHome®