Thanks for the link.

I'm a little bit disappointed by how the SSU process has turned out (I may have mis-spelled the 3-letter name, but hopefully you understand what I mean - the upgrade process that was supposed to be implemented by Diablo).

What I expected was that it would unleash the power of ATP, the Debian Package management system. I didn't expect something that simply replaced the flashing method with something doing pretty much exactly the same, only with more risks to the user (ref e.g. the discussion about mis-calculating how much space would be needed during the upgrade).

I expected to be able to simply apt-get update, apt-get upgrade, (well, through the application manager equivalent), and fixes and upgrades would trickle in package-by-package. It would just be that one of those packages could be the kernel itself. This is how my desktop Debian system works, and it's a delight.

Instead fixes seem to only be made available for a 'next release', which is of course a full release, which to me is a very old-fashioned way of thinking: To upgrade you have to go through a major, singular process instead of using a safe, small, low-risk iterative process. I've been there, and I'm never going back to that kind of monstrous process on my desktop. Thus, I'm not particularly keen on having to do that on my NIT either.