Okay I have some problems with the support committed to flash-kernel, namely
* it doesn't differentiate between kernel versions, so uImage and uInitrd will overwrite any older uImage and uInitrd version. This is unfriendly and it is impossible to tell at a glance (without using mkimage to list the details) what version of the kernel it is * generating boot.scr from boot.script is fine enough for the above, and allows users to edit options, but.. see above * if uInitrd doesn't already exist, it will not be created as the entire creation part is wrapped in an if [ -f /boot/uInitrd ]. What should happen is if [ -f /boot/uInitrd ]; then cp /boot/uInitrd /boot/uInitrd.bak fi # create uInitrd here regardless Actually, apart from the last one I'm willing to live with what happens here, as it makes cleanup of kernels much easier. But, it does beg a question, if I dpkg --purge a kernel image, update-initramfs will remove the initrd.img-${kver} - why can't flash-kernel remove kernel files? Also why can't we ship a boot.script which you can use sed to insert the kernel version (cp boot.script /tmp/boot.script; sed -i -e's/KVERSION/${kver}/' /tmp/boot.script; mkimage blah -d /tmp/boot.script /boot/boot.scr; rm -f /tmp/boot.script), and create versioned uInitrd and uImage files? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/671027 Title: Add Efika MX Smartbook/Smarttop support -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs