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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1367241 Title: Incorrect udev-fallback-graphics.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1367241/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
