Alberto: I don't agree here that running this in the kernel postinst is going to increase the likelihood of nvidia-common helping transition users. The order that the nvidia-common postisnt and kernel postinst would trigger is irrelevant, because the message will be displayed either way, and the user can't react to it until apt is done anyway.
If you are thinking that by trigger in the kernel postinst because of changed filed in a modalias package to catch it before nvidia-common's postinst, you should /really/ be doing that in the modalias postinst. That's just a hack to have it run in the kernel's. The kernel hasn't changed these modaliases at *all*. Alberto Milone wrote: > @Mario > the kernel postinst exists because it can happen that the nvidia-common > postinst is triggered before the installation of the new (or updated) > modalias files takes place thus preventing nvidia-common from helping users > with the transition to a new driver. > > The kernel postinst gives nvidia-common a better chance to do its job by > making sure that the postinst is triggered sooner or later during the > upgrade. > > -- Mario Limonciello *Dell | Linux Engineering* mario_limoncie...@dell.com -- dkms - error when installing custom kernel https://bugs.launchpad.net/bugs/292606 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
