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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
