Nullifying requirement to reboot after kernel update

[Chris]

On Tue, 2015-04-14 at 11:34 -0400, Dave Woyciesjes wrote:
> On 04/14/2015 11:09 AM, Chris wrote:
> > On Tue, 2015-04-14 at 16:04 +0200, Petter Adsen wrote:
> >> On Tue, 14 Apr 2015 08:48:59 -0500
> >> Chris <cpollock at embarqmail.com> wrote:
> >>
> >>> On Tue, 2015-04-14 at 09:14 -0400, Dave Woyciesjes wrote:
> >>>> On 04/13/2015 10:28 PM, Chris wrote:
> >>>>> On Mon, 2015-04-13 at 20:22 -0400, Dave Woyciesjes wrote:
> >>>>>> On 4/13/15 8:24 AM, Chris 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 -
> >>>>>>>>> http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/
> >>>>>>>>> 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?
> >>>>>>>>>
> >>>>>>>>> Chris
> >>>>>>>>
> >>>>>>>> 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.
> >>>>>>>>
> >>>>>>>> Cheers, Gene Heskett
> >>>>>>> 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 -
> >>>>>>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1402331
> >>>>>>> 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.
> >>>>>>>
> >>>>>>
> >>>>>> 	It's simple then, Chris. Don't apply any update that
> >>>>>> needs a reboot. You only said you don't want to get nagged about
> >>>>>> reboot; so obviously you don't care about getting all of the
> >>>>>> fixes.
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>> True in a sense Dave, at some given point I 'may' want to boot
> >>>>> into the latest 3.13.* or 3.14.* kernel, whichever is the latest
> >>>>> Ubuntu one, and by just removing the symlink I've removed the
> >>>>> nagging of a reboot required (hopefully) and with the latest
> >>>>> supported kernel installed I can always boot into it if needed.
> >>>>>
> >>>>
> >>>> 	Problem with that, however, is if someone trips over your
> >>>> power cord, you end up in the new kernel before you are ready...
> >>>>
> >>>>
> >>> Not really Dave as I have this line in my /etc/default/grub file
> >>>
> >>> GRUB_CMDLINE_LINUX_DEFAULT=""
> >>>
> >>> which replaces
> >>>
> >>> GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
> >>>
> >>> which gets me the grub menu where I can pick and choose whichever
> >>> kernel I want to boot into.
> >>
> >> The removal of "quiet splash" does not drop you into a menu, it removes
> >> the splash screen (I believe it's called "plymouth") and enables showing
> >> kernel messages on boot.
> >>
> >> Petter
> >>
> > My mistake, this is the line I commented out which I 'believe' allows
> > showing of the grub menu allowing me to choose which kernel to use.
> >
> > # GRUB_HIDDEN_TIMEOUT=0
> > GRUB_HIDDEN_TIMEOUT_QUIET=true
> > GRUB_TIMEOUT=30
> >
>    That would be a good safety catch, then... :) I assume then that you 
> have it set to default to your custom kernel?
> 
No, when the grub menu comes up I just scroll down to the custom drm
intel kernel and boot. That way if for some odd reason I'm asked by the
folks in the Intel Gfx list to try another one I can easily do that.

-- 
Chris
KeyID 0xE372A7DA98E6705C
31.11°N 97.89°W (Elev. 1092 ft)
11:29:30 up 5 days, 19:06, 1 user, load average: 0.17, 0.15, 0.14
Ubuntu 14.04.2 LTS, kernel 4.0.0-997-generic #201503310205 SMP Tue Mar
31 02:07:04 UTC 2015