kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: anyone aware of a high availability setup that relies on fully redundant install?
Date: Mon, 18 Apr 2016 06:17:43 +0900	[thread overview]
Message-ID: <20160417211743.GA29746@kroah.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1604171308130.14259@localhost.localdomain>

On Sun, Apr 17, 2016 at 01:16:10PM -0400, Robert P. J. Day wrote:
> On Sun, 17 Apr 2016, Greg KH wrote:
> 
> > On Sun, Apr 17, 2016 at 10:47:55AM -0400, Robert P. J. Day wrote:
> > >
> > >   i figure this is as good a place as any to ask ... is anyone here
> > > aware of anyone using a linux config and install that, for the
> > > purposes of reliability or high availability or whatever you want to
> > > call it, relies on a second, completely independent installation of
> > > linux on the same hard drive?
> >
> > ChromeOS and CoreOS do this.  There's lots of documentation on the
> > ChromeOS site for how this works and what is involved.
> 
>   interesting ... does the CoreOS functionality depend on containers?

Nope, not at all, it's the same design as ChromeOS.

> what little i know about CoreOS, i would think there's no way to use
> it *without* containers.

Not true at all, you can use it without containers, it's just not all
that useful as odds are, the application you want to use isn't included
in it so you need a container for that.

greg k-h

  reply	other threads:[~2016-04-17 21:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-17 14:47 anyone aware of a high availability setup that relies on fully redundant install? Robert P. J. Day
2016-04-17 15:23 ` Res: " Daniel
2016-04-17 16:02 ` Greg KH
2016-04-17 17:16   ` Robert P. J. Day
2016-04-17 21:17     ` Greg KH [this message]
2016-04-18  4:48 ` Valdis.Kletnieks at vt.edu
2016-04-18 10:29   ` Robert P. J. Day
2016-04-18 14:43     ` Valdis.Kletnieks at vt.edu
2016-04-18 19:49   ` Miles Fidelman
2016-05-12 16:06 ` Andrew Bradford

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=20160417211743.GA29746@kroah.com \
    --to=greg@kroah.com \
    --cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).