And how it is related? If you use anything kernel-dependent (thumb), you would be screwed, anyway. Unless you, for once, "read manual" and discover, that in such cases, U-boot can run things from SD card (via u-boot console). Or you can use rescue Os from flasher. Or...

Well, I do not see any reason to use u-boot image *with* kernel attached But thats OK - everyone haw own favorite ways. That's why I asked to make genbootmenu script respect lack of attached kernel, and stop creating non-working menu entries for it.

This way, someone who use attached kernel is happy, and people who prefer otherwise, doesn't "suffer", too.

As for patch - I don't have it, AFAIK, kerio send it to you, personally. As per his IRC'ing, you haven't had time to look into it. Probably, he should submit it to some git or whatsnot, if you don't have it, it means he didn't.

Anyway, putting kerio aside (I can easily imagine, that his patch was less than ideal and could cause some problems you vaguely remember), *if* it's doable and doesn't cost you too much time, it would be nice, to have u-boot menu generator, that doesn't enforce non-working menu entry for attached kernel.

It could be as simple as parameter given to generate script, like --no-attached, which would disable - at user responsibility - that menu entry. This way, whole heuristic to determine things, would be spared.

If you don't see it as feasible, I can easily live with it. I just though that, while updating generating script anyway, it may be good to fix two nuisances at the same time. Killing two deer with one spear, or something like that...

/Estel