From: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
To: David Ford <david@linux.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] modutils 2.3.20 and beyond
Date: Sun, 26 Nov 2000 19:46:43 -0700 [thread overview]
Message-ID: <20001126194643.E2265@vger.timpanogas.org> (raw)
In-Reply-To: <20001126163655.A1637@vger.timpanogas.org> <E140AZB-0002Qh-00@the-village.bc.nu> <20001126164556.B1665@vger.timpanogas.org> <3A21968B.5CDB12BF@haque.net> <20001126170334.B1787@vger.timpanogas.org> <3A21A7D9.9CE7077B@linux.com>
In-Reply-To: <3A21A7D9.9CE7077B@linux.com>; from david@linux.com on Sun, Nov 26, 2000 at 04:16:26PM -0800
On Sun, Nov 26, 2000 at 04:16:26PM -0800, David Ford wrote:
> "Jeff V. Merkey" wrote:
>
> > On Sun, Nov 26, 2000 at 06:02:35PM -0500, Mohammad A. Haque wrote:
> > > I'd rather have Anaconda changed rather than special casing standard
> > > utils to account for distro handling.
> >
> > Great. Then tell RedHat to rewrite it without the need for these switches.
> > They will say NO. It's a trivial change, and would save me a lot of hours
> > rewriting scripts. I did it once, but if RedHat has standardized on this
> > set of switches, why not add them as alias commands? It's a trivial
> > patch.
>
> Then let RedHat maintain their version of modutils. RedHat isn't the
> standard, nor should RedHat dictate to authors, nor should other distributions
> and persons be affected by RedHat's methods.
>
> If you don't like it, replace your depmod with a script that strips that flag
> before calling the original depmod.
Anaconda is open sourced, so it's not technically tied to any one
distributor any more....
Jeff
>
> -d
>
Content-Description: Card for David Ford
-
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:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-26 23:36 [PATCH] modutils 2.3.20 and beyond 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 [this message]
2000-11-27 1:58 ` Tom Rini
2000-11-27 0:13 ` David Ford
2000-11-27 2:11 ` Alan Cox
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=20001126194643.E2265@vger.timpanogas.org \
--to=jmerkey@vger.timpanogas.org \
--cc=david@linux.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