From: "H. Peter Anvin" <hpa@zytor.com>
To: Jeff Bailey <jbailey@ubuntu.com>
Cc: Michael Neuling <mikey@neuling.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
klibc@zytor.com, "miltonm@bga.com" <miltonm@bga.com>,
Al Viro <viro@ftp.linux.org.uk>
Subject: Re: [klibc] [PATCH] initramfs: multiple CPIO unpacking fix
Date: Tue, 21 Feb 2006 18:17:35 -0800 [thread overview]
Message-ID: <43FBC9BF.2020407@zytor.com> (raw)
In-Reply-To: <1140574441.5304.37.camel@localhost.localdomain>
Jeff Bailey wrote:
>
> I've tended to think of this as a feature, actually. In Ubuntu, for
> instance, we might have 2.6.15-8 and 2.6.15-9 which represent different
> ABIs from security updates or other changes. If I have a module that is
> intended to be compatible with both, I might setup /lib/modules/generic
> to be a symlink to /lib/modules/2.6.15-9/ and unpack the modules after
> the symlink is expected to be there.
>
This is pretty broken for a bunch of other reasons, though. In
particular, it prevents the very useful behaviour of providing a symlink
in entry A that can be overridden by a file in entry B.
> (I don't think we use this feature right now, but I had tested it and
> noted it before. It's very convenient, since it's the exact same
> behaviour that dpkg itself has)
I would personally consider that a bug in dpkg :-/
-hpa
next prev parent reply other threads:[~2006-02-22 2:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-16 7:37 [PATCH] Chained CPIOs writing to the same file bug Michael Neuling
[not found] ` <20060217160621.99b0ffd4.mikey@neuling.org>
2006-02-21 23:45 ` [PATCH] initramfs: multiple CPIO unpacking fix Michael Neuling
2006-02-22 2:14 ` [klibc] " Jeff Bailey
2006-02-22 2:17 ` H. Peter Anvin [this message]
2006-03-22 6:12 ` [PATCH] initramfs: " Michael Neuling
2006-03-22 7:14 ` Jeff Garzik
2006-03-22 16:05 ` [klibc] " H. Peter Anvin
2006-03-22 22:23 ` Rob Landley
2006-03-22 23:22 ` Jeff Garzik
2006-04-07 17:33 ` H. Peter Anvin
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=43FBC9BF.2020407@zytor.com \
--to=hpa@zytor.com \
--cc=jbailey@ubuntu.com \
--cc=klibc@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikey@neuling.org \
--cc=miltonm@bga.com \
--cc=viro@ftp.linux.org.uk \
/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