From: "W.Kenworthy" <billk@iinet.net.au>
To: gentoo-server@lists.gentoo.org
Subject: Re: [gentoo-server] Challenging Update Question
Date: Tue, 12 Feb 2008 16:13:07 +0900 [thread overview]
Message-ID: <1202800387.20052.19.camel@localhost> (raw)
In-Reply-To: <20080211233002.p71xacark0wwoggg@webmail.collinstarkweather.com>
Rebuild/upgrade on the redundant drive in a chroot
Rebuild elsewhere (local to you) on similar hardware and copy OS over.
I suspect though, that building a new system, getting it working and
shipping it as a black box would be the most low risk/effective
strategy.
Hint:
Setup grub to boot either os so local support only has to select which
disk to boot from if there is a failure.
BillK
On Mon, 2008-02-11 at 23:30 -0700, Collin Starkweather wrote:
> I have a server that is in need of a significant update, but it's
> proving a challenge. I have a big picture question, then provide some
> details below.
--
gentoo-server@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-02-12 7:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-12 6:30 [gentoo-server] Challenging Update Question Collin Starkweather
2008-02-12 6:38 ` RijilV
2008-02-12 7:13 ` W.Kenworthy [this message]
2008-02-12 12:00 ` Collin Starkweather
2008-02-12 12:17 ` Andrew Gaffney
2008-02-12 12:18 ` William Kenworthy
2008-02-12 13:13 ` Benjamen R. Meyer
2008-02-12 19:44 ` Randy Barlow
2008-02-12 20:34 ` RijilV
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=1202800387.20052.19.camel@localhost \
--to=billk@iinet.net.au \
--cc=gentoo-server@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