More seriously, with a truly stripped down free software solution (be that Linux or *bsd founded), you can have a pretty good idea of exactly what code you are running.
Current Linux might actually be a pretty poor choice, given the high rate of change in the kernel (which tends to drag a lesser, but noticeable change in userland). A few years ago 1.3 kernel might have seemed a sane choice to build such a system on (along with busybox, minimal init etc).
Anyway, the idea would be to get a reasonably audited core system (mostly userland) and a kernel - and then only ever update drivers, and/or add functionality.
Personally I'd be a lot more confident doing that on Linux (or bsd) than on Windows XP, even if given source access (would you really want to compile the needed bits of XP kernel+userland to run on your embedded stuff? The thought scares the beejeezes out of me)).
Well then don't they have the exact same problem as they do now with MS? Or more general: are the update cycles from a typical linux distro that different from Window's? I.e. can you really get security updates for such distro 20 years after it was released? That would mean the only benefit for choosing linux is that there are possibly less securit issues to begin with, while the article seems to claim the problem is all with the update cycle.