public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Safe way to test a new kernel?
Date: Sat, 25 Feb 2012 12:18:49 +0000	[thread overview]
Message-ID: <201202251218.59928.michaelkintzios@gmail.com> (raw)
In-Reply-To: <CAA2qdGVre0BM5nzHj-PHunv1ZdvAEp7vDUOrkNctkd3mwMDGmQ@mail.gmail.com>

[-- Attachment #1: Type: Text/Plain, Size: 1396 bytes --]

On Saturday 25 Feb 2012 02:32:49 Pandu Poluan wrote:
> On Feb 25, 2012 9:14 AM, "Grant" <emailgrant@gmail.com> wrote:
> > >> I need to test a kernel config change on a remote system.  Is there a
> > >> safe way to do this?  The fallback thing in grub has never worked for
> > >> me.  When does that ever work?
> > > 
> > > You can press ESC in the Grub screen and it will take you to text-only
> 
> mode.
> 
> > >  There, you select an entry, press "e" and edit it.  Press ENTER when
> 
> you're
> 
> > > finished, and then press "b" to boot your modified entry.
> > > 
> > > That way, you can boot whatever kernel you want if the current one
> 
> doesn't
> 
> > > work.
> > 
> > I can't do that remotely though.  I'm probably asking for something
> > that doesn't exist.
> > 
> > - Grant
> 
> Situations like these that made me decide with great conviction to always
> deploy my servers virtualized, even if the box in question will only host a
> single VM.
> 
> Now, if I lost my intelligence for a couple of seconds and somehow ended up
> with a VM that's no longer accessible remotely, I just connect to the
> virtual console.
> 
> The flip side? Now I'm getting too daring/careless, and the uptime now
> drops below my (self-imposed) target of 99.99% :-P

What do you do when you need to upgrade the host, rather than the guest?

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2012-02-25 12:20 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-25  2:00 [gentoo-user] Safe way to test a new kernel? Grant
2012-02-25  2:05 ` [gentoo-user] " Nikos Chantziaras
2012-02-25  2:08   ` Grant
2012-02-25  2:17     ` Michael Mol
2012-02-25  2:26     ` Dale
2012-02-25 12:46       ` Francisco Ares
2012-02-25  2:32     ` Pandu Poluan
2012-02-25 12:18       ` Mick [this message]
2012-02-25 12:33         ` Nilesh Govindrajan
2012-02-25 18:35           ` Grant
2012-02-25 13:52         ` Pandu Poluan
2012-02-25 18:33         ` Grant
2012-02-25  8:57     ` Robert David
2012-02-25 18:32       ` Grant
2012-02-25 19:03         ` Robert David
2012-02-25 19:25           ` Grant
2012-02-25 19:50           ` Pandu Poluan
2012-02-25 20:44             ` Robert David
2012-02-26  5:33             ` Alan McKinnon
2012-02-25  2:10 ` Nikos Chantziaras
2012-02-25 14:04   ` Alan Mackenzie
2012-02-25 15:23     ` Nikos Chantziaras
2012-02-25 18:30   ` Grant
2012-02-26  7:16     ` Grant
2012-02-26 13:19       ` Alex Schuster
2012-02-26 14:35         ` Grant
2012-02-26 15:12           ` Alex Schuster
2012-02-26 15:20           ` Nilesh Govindrajan
2012-02-25 13:47 ` Nikos Chantziaras
2012-02-27 14:39 ` James

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201202251218.59928.michaelkintzios@gmail.com \
    --to=michaelkintzios@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox