Trying to put together a TINY seed debian to allow us to *background* chroot - thus enabling the newer libc and libm dependant apps to have access to "newer" versions of this things.

In the end I am hoping to dynamically run this from a squash or cram fs.
(Yup just re-using your ideas in a different context as usual)

Could be a fools errand. (thus I chose to walk the road alone until I was sure it wasn't)

I'm retrying with wheezy now. see if I can get something a bit more "stable" going. Also SID is a huge (250mb) pull lately. wheezy can be trimmed I am hoping to something a bit more sensible with love and sticky tape

I would dearly love to know where to track the version bumps though.

If I had to guess: the patches tracker for debian. probably the libc stuff (but as you know I am no expert)

@twobob: the kernel requirement is the libc's job (excluding fun stuff like an init system/udev/systemd for a "real" system). If you're building the libc yourself, you're the one choosing the min kernel version. No idea what Debian does, but for an nptl libc the default is still 2.6.16 IIRC.

Where to find the information:
Look in the C library ./configuration file - there will be a test for the minimum kernel header version required.
It will be using an m4 macro, but should be easy to spot.

The minimum version was bumped to 2.6.20.x over time for some feature(s) - I don't recall what, or if we need those features.
(I will not swear to that, haven't had my head in the building of the C library for a long time.)