Nullifying requirement to reboot after kernel update

[Petter Adsen]

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

-- 
"I'm ionized"
"Are you sure?"
"I'm positive."
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 213 bytes
Desc: OpenPGP digital signature
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20150414/7b1ffab9/attachment.sig>