Building vesafb as a module should still be possible.
Trusty had vesafb build in the kernel from the very first release, so I believe the assumption is safe here.
Regarding precise:
Instead of removing the script I could leave it but alter it to check the feature (e.g. kernel version number or the option in /boot/config-`uname-r`) and undertake no actions in the script if we have this module compiled in.
Building vesafb as a module should still be possible.
Trusty had vesafb build in the kernel from the very first release, so I believe the assumption is safe here.
Regarding precise: `uname- r`) and undertake no actions in the script if we have this module compiled in.
Instead of removing the script I could leave it but alter it to check the feature (e.g. kernel version number or the option in /boot/config-