All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jeff V. Merkey" <jmerkey@timpanogas.org>
To: Keith Owens <kaos@ocs.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: modutils 2.3.20 not backward compatible
Date: Tue, 21 Nov 2000 22:12:19 -0700	[thread overview]
Message-ID: <3A1B55B3.FE866C14@timpanogas.org> (raw)
In-Reply-To: <5038.974864798@kao2.melbourne.sgi.com>



Keith Owens wrote:
> 
> On Tue, 21 Nov 2000 20:17:47 -0700,
> "Jeff V. Merkey" <jmerkey@timpanogas.org> wrote:
> >Was there a reason we removed the -i and -m options from newer modutils
> >and broke backwards caompatibility?  I'm re-writing our module build
> >scripts for the installer, and I discovered after upgrading to 2.3.20,
> >that all the build scripts (about 10MB worth) are now busted and I have
> >been spending most of this evening rewriting them so they work again.
> 
> -i and -m have never been in the base code.  -i in depmod is a Redhat
> add on, only in their distribution.  I have no idea what -m does, apart
> from -m in insmod which is supported.  Blame the distributors.

Thanks for clarifying.  -i ignores certain dependency failures, and is
very dangerous.  -m lets you use a map file.  If what you say is
correct, then it was an erstwhile exercise rewriting these scripts,
since they will now take generic parameters.  

Jeff

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

  reply	other threads:[~2000-11-22  5:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-22  3:17 modutils 2.3.20 not backward compatible Jeff V. Merkey
2000-11-22  3:46 ` Keith Owens
2000-11-22  5:12   ` Jeff V. Merkey [this message]
2000-11-22 11:47   ` Igmar Palsenberg

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=3A1B55B3.FE866C14@timpanogas.org \
    --to=jmerkey@timpanogas.org \
    --cc=kaos@ocs.com.au \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.