public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Fasheh <mark.fasheh@oracle.com>
To: Emmett Pate <emmett@epate.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Status of Modules?
Date: Mon, 27 Jan 2003 12:45:07 -0800	[thread overview]
Message-ID: <20030127204507.GA17737@ca-server1.us.oracle.com> (raw)
In-Reply-To: <200301270743.15588.emmett@epate.com>

Along with Rustys new module-init-tools (required to get started - I
downloaded mine from
ftp://ftp.kernel.org/pub/linux/kernel/people/rusty/modules/ ) I had to apply
this patch:
http://marc.theaimsgroup.com/?l=linux-kernel&m=104284883805276&w=2 to make
modules on 2.5.59 load without hard locking my kernel. I believe there's
newer/better versions of this fix on the list -- you might want to check the
archives.
	--Mark

On Mon, Jan 27, 2003 at 07:43:15AM -0500, Emmett Pate wrote:
> What's the status of the module loading code?  I've been compiling them into 
> the kernel since something around 2.5.3x when the code was rewritten.  I'd 
> like to begin using a few modules again (especially some PCMCIA stuff).  Is 
> there any documentation explaining what will be necessary for 2.5 to use 
> modules?
> 
> Thanks for the help,
> Emmett Pate
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
--
Mark Fasheh
Software Developer, Oracle Corp
mark.fasheh@oracle.com

      parent reply	other threads:[~2003-01-27 20:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-27 12:43 Status of Modules? Emmett Pate
2003-01-27 14:49 ` Kevin Puetz
2003-01-27 20:45 ` Mark Fasheh [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=20030127204507.GA17737@ca-server1.us.oracle.com \
    --to=mark.fasheh@oracle.com \
    --cc=emmett@epate.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