linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fang Han <dfbb@linux.net.cn>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: RFC: modules and 2.5
Date: Tue, 3 Jul 2001 15:48:00 +0800	[thread overview]
Message-ID: <20010703154759.A1409@dfbbb.cn.mvd> (raw)
In-Reply-To: <3B415489.77425364@mandrakesoft.com> <20010703075050.B15457@dev.sportingbet.com>
In-Reply-To: <20010703075050.B15457@dev.sportingbet.com>; from sean@dev.sportingbet.com on Tue, Jul 03, 2001 at 07:50:50AM +0100

> If you build the drivers in, but forget to comment out the initrd line in
> /etc/lilo.conf, the machine panics because it tries to load the module for
> something that is already a builtin.
> 
The only way to solve it smothly need to modify the bootloader, When the 
bootloader like lilo or grub ( it is more powerful ) can read the module from the root partition directly. Your problem will be sloved.

BTW: Is there any system or tools can patch kernel in binary level, It means
     that user doesn't need download the whole kernel RPM or TGZ, It just need
     an patch to patch the current kernel's binary. I think it is useful for
     novice & end user.

Regards

dfbb


  parent reply	other threads:[~2001-07-03  9:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-03  5:13 RFC: modules and 2.5 Jeff Garzik
2001-07-03  6:50 ` Sean Hunter
2001-07-03  7:05   ` Jeff Garzik
2001-07-03  7:16   ` Keith Owens
2001-07-03  7:24     ` Jeff Garzik
2001-07-03  7:39       ` Keith Owens
2001-07-03  7:44         ` Jeff Garzik
2001-07-03  7:48   ` Fang Han [this message]
2001-07-03  7:18 ` Keith Owens
2001-07-03 12:15 ` jlnance
2001-07-06 10:34 ` Rusty Russell
2001-07-07 14:12   ` Jeff Garzik
2001-07-08  7:40     ` Rusty Russell
2001-07-11 22:04       ` Pavel Machek
2001-07-03 17:35 Andrzej Krzysztofowicz
2001-07-03 17:39 ` Jeff Garzik

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=20010703154759.A1409@dfbbb.cn.mvd \
    --to=dfbb@linux.net.cn \
    --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;
as well as URLs for NNTP newsgroup(s).