Adrian Bunk wrote:
> Why is this "sid chroot on a stable system" usecase so important?
I don't write the policies.
More to the point, what I was trying to say is that the package
manager will not help you with this. To get reasonable behavior on
what really is a common configuration, you need to be able to cope
with an older kernel, at least enough to print a meaningful error
message and exit.
> And how are you currently ensuring that perf is working in your
> "sid chroot on a stable system" usecase?
$ cat /usr/bin/perf
#!/bin/bash
# Execute the right version of perf for the current kernel.
version="$(uname -r)"
version="${version%%-*}"
shopt -s execfail
exec "perf_$version" "$@"
# Not found? Tell the user which package to install.
echo >&2 "E: linux-tools-$version is not installed."
exit 1
Anyway, if you believe that lockstep upgrades of the kernel and
userspace are something the Debian project should support, I am
guessing this bug log isn't the right place to discuss it. Maybe
debian-devel.
Regards,
Jonathan
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110718200238.ga6...@elie.gateway.2wire.net
