From: Jeff Garzik <jgarzik@pobox.com>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: Thierry Vignaud <tvignaud@mandrakesoft.com>,
Rusty Russell <rusty@rustcorp.com.au>,
kaos@ocs.com.au, Petr Vandrovec <VANDROVE@vc.cvut.cz>,
linux-kernel@vger.kernel.org
Subject: Re: Modules in 2.5.47-bk...
Date: Sat, 16 Nov 2002 16:08:17 -0500 [thread overview]
Message-ID: <3DD6B3C1.70900@pobox.com> (raw)
In-Reply-To: <20021114042738.2091E2C080@lists.samba.org>
Adrian Bunk wrote:
> On Thu, Nov 14, 2002 at 04:45:16PM +0100, Thierry Vignaud wrote:
>
> >Rusty Russell writes:
> >
> >
> >>>The backward compat thing is really a hack, and not system
> >>>software done right :( modutils should not need to rename all its
> >>>binaries *.old -- and have that be the default that users see when
> >>>installing the rpm. No company worth its shareholders would
> >>>release a package full of "*.old" binaries. Come on...
> >>
> >>OK, would calling it "*-2.4" or something help?
> >
> >most distros come with some alternative system (at lest, debian, mdk &
> >rh), so this problem can legally be left to vendors.
>
>
> The alternative system doesn't work in this case because it doesn't help
> you when you want to switch between 2.4 and 2.6 kernels. You need some
> kind of wrapper.
Agreed. The alternatives stuff I am familiar with does not changes
symlinks based on the version of booted kernel, AFAIK.
Jeff
next prev parent reply other threads:[~2002-11-16 21:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-13 18:36 Modules in 2.5.47-bk Petr Vandrovec
2002-11-13 21:06 ` Jeff Garzik
2002-11-14 3:53 ` Rusty Russell
2002-11-14 4:06 ` Jeff Garzik
2002-11-14 5:22 ` Rusty Russell
2002-11-14 15:45 ` Thierry Vignaud
2002-11-16 13:50 ` Adrian Bunk
2002-11-16 21:08 ` Jeff Garzik [this message]
2002-11-14 10:50 ` Christoph Hellwig
2002-11-14 17:53 ` Rusty Russell
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=3DD6B3C1.70900@pobox.com \
--to=jgarzik@pobox.com \
--cc=VANDROVE@vc.cvut.cz \
--cc=bunk@fs.tum.de \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=tvignaud@mandrakesoft.com \
/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