Von: "Ian Campbell" <i...@debian.org> > There is one other option, which is to ask people to adjust their u- > boot boot scripts as Robert has done, however the QNAP systems are > often run headless and without access to the serial console (it's a > special cable which only a minority of users will have access to) so > that really is a last resort.
Note that it is possible to modify the u-boot environment without the serial console, using the "fw_setenv" command in a running debian system. So one possibility would indeed be to modify the flash-kernel scripts to use fw_printenv, "parse" the environment to detect affected systems and, if needed, use fw_setenv to make the necessary changes. That's not really a "pretty" solution, though, and any bugs in that function could easily brick the device. Then again, there have been "bricking" changes in the past, so it wouldn't be an entirely new risk ;-) At least making the change _without_ flashing a new kernel should not be harmful as the moved initramfs location appears to be backwards compatible (though I've tried only 4.9 in practice). Best regards, -Robert