mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bjorn Ekwall <bj0rn@blox.se>
To: linux-kernel@vger.rutgers.edu
Cc: rth@piglet.twiddle.net (Richard Hendersson),
	jack@solucorp.qc.ca (Jacques Gelinas)
Subject: New snapshot of modutils
Date: Sun, 14 Feb 1999 22:40:08 +0100 (CET)	[thread overview]
Message-ID: <199902142140.WAA06554@lix.blox.se> (raw)

Hi all,

Richard Hendersson is extremely busy at the moment.
After talking to him, Richard and I have agreed that I will help with
creating an updated release of the module support utilities.

So, for a snapshot of the current state, please look at:
	<http://www.pi.se/blox/modutils/>
You will find the latest snapshot as "modutils-snap990214.tar.gz"

It is quite possible that the development will by accessible via cvs
very soon; I'll keep you posted.

Please note that the depmod and modprobe utilities are back to C++.
This is a result of a discussion in linux-kernel last week, and
this is the way it has to be, in consideration of all involved.

I have verified that the current snapshot compiles, at least, but I haven't
done anything like a full-scale testing.  For the future, your suggestions
for improvements and restructuring are definitely welcome.
Send your input to <bj0rn@blox.se> and I will start upgrading even faster...

Here is part of the TODO-file:
- Upgrade modprobe and depmod with things that happened since modutils-2.1.23
- Verify that the current patches didn't break too much...
- Prepare for merging modprobe with insmod (too much duplication right now)
- Cleaner handling of multiple invocations of insmod
- Collect and merge more patches


Cheers,

Björn Ekwall <bj0rn@blox.se>

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

                 reply	other threads:[~1999-02-14 20:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=199902142140.WAA06554@lix.blox.se \
    --to=bj0rn@blox.se \
    --cc=jack@solucorp.qc.ca \
    --cc=linux-kernel@vger.rutgers.edu \
    --cc=rth@piglet.twiddle.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®