On Apr 13, 2015 8:48 AM, "Chris" <<a href="mailto:cpollock@embarqmail.com">cpollock@embarqmail.com</a>> wrote: > > On Mon, 2015-04-13 at 09:25 -0400, Tom H wrote: > > On Mon, Apr 13, 2015 at 8:24 AM, Chris <<a href="mailto:cpollock@embarqmail.com">cpollock@embarqmail.com</a>> wrote: > > > On Mon, 2015-04-13 at 01:23 -0400, Gene Heskett wrote: > > >> On Sunday 12 April 2015 22:21:52 Chris wrote: > > >>> > > >>> The subject says it all. Based upon the fact that I'm running a > > >>> non-standard kernel from here - > > >>> <a href="http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/">http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/</a> whenever > > >>> a support Ubuntu kernel comes down the pike such as 3.13* I'd like to > > >>> go ahead and install it but not go through the reboot process because > > >>> I'll continue to run the kernel shown below or a newer version is > > >>> required. Is there a setting where I can comment out the reboot nag? > > >> > > >> If it tells you to reboot, it does so because that is the only way to get > > >> the bug or security fixed version of the software it just updated into > > >> operation and your machine then armored against the security exploit. > > >> > > >> If you do not reboot, you will be leaving your system in a buggy or > > >> vulnerable condition. > > > > > > That's why I mentioned in my initial post above Gene that I'm not > > > running the 'standard' kernel but an updated drm-intel kernel from the > > > link I provided. I'm running this kernel because of the video lockups > > > I'd been getting and the bug report I made here - > > > <a href="https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1402331">https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1402331</a> and I'm > > > also running an updated xf86-video-intel driver. So far this combination > > > has worked. In order to track how long this combination will go without > > > a lockup I need to be able to ignore the mandatory reboot after a > > > standard Ubuntu kernel update. > > > > AFAIK, the message about rebooting after a kernel's installed is > > triggered by "/etc/kernel/postinst.d/update-notifier". > > > Thanks Tom, I see what it does, runs a small script which puts this > in /var/run > > echo "*** $(eval_gettext "System restart required") ***" > > /var/run/reboot-required > echo "$DPKG_MAINTSCRIPT_PACKAGE" >> /var/run/reboot-required.pkgs > > Hmm, wonder what would break if I just removed the script link in > /etc/kernel/postinst.d/update-notifier and the actual script > in /usr/share/update-notifier probably break the system or maybe it > would be regenerated. I wouldn't actually remove it anyway just move to > another folder within the main folder it's in now. It's a shell script, so just edit it to add 'exit 0' at the top of the script. Then, you can always chattr +I the script to prevent an update from reverting your change. Any update to the package that maintains it will fail, but that's ok, since you can simply update that package seperately and readd your modification after removing the i bit with chattr if you ever need to update that specific package.