From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: david@linux.com (David Ford)
Cc: linux-kernel@vger.kernel.org (LKML),
jmerkey@vger.timpanogas.org (Jeff V. Merkey)
Subject: Re: [PATCH] modutils 2.3.20 and beyond
Date: Mon, 27 Nov 2000 02:11:49 +0000 (GMT) [thread overview]
Message-ID: <E140Dlm-0002bT-00@the-village.bc.nu> (raw)
In-Reply-To: <3A21A720.75A4EEB1@linux.com> from "David Ford" at Nov 26, 2000 04:13:20 PM
> > Anaconda will barf and require over 850+ changes to the scripts without
> > it. If you look at the patch, you will note that it's a silent switch
> > that's only there to avoid a noisy error message from depmod. It
> > actually does nothing other than set a flag that also does nothing.
> > -m simply maps to -F.
>
> It's still a bad precedent. Anaconda should have been written correctly in
> the first place.
I don't know if its an Anaconda issue or a limitation in the tools. Keith is
the modutils maintainer and its up to the Anaconda hackers to prove to him that
he has a problem so I think he is absolutely right in refusing to change it
until that is proven
-
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/
next prev parent reply other threads:[~2000-11-27 2:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-26 23:36 Jeff V. Merkey
2000-11-26 22:46 ` Alan Cox
2000-11-26 23:27 ` H. Peter Anvin
2000-11-26 23:45 ` Jeff V. Merkey
2000-11-26 23:02 ` Mohammad A. Haque
2000-11-27 0:03 ` Jeff V. Merkey
2000-11-26 23:15 ` Tom Rini
2000-11-27 2:39 ` Jeff V. Merkey
2000-11-27 0:16 ` David Ford
2000-11-27 2:46 ` Jeff V. Merkey
2000-11-27 1:58 ` Tom Rini
2000-11-27 0:13 ` David Ford
2000-11-27 2:11 ` Alan Cox [this message]
2000-11-27 3:33 ` Jeff V. Merkey
2000-11-26 23:23 ` Keith Owens
2000-11-27 2:43 ` Jeff V. Merkey
2000-11-27 16:48 ` Jes Sorensen
2000-11-27 16:59 ` Jakub Jelinek
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=E140Dlm-0002bT-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=david@linux.com \
--cc=jmerkey@vger.timpanogas.org \
--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
all inboxes | Powered by JetHome®