public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Canek Peláez Valdés" <caneko@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Custom ebuilds for CoreOS
Date: Mon, 1 Dec 2014 16:32:55 -0600	[thread overview]
Message-ID: <CADPrc83cv8bCOL9TGsmbYqQjM5YKxewcXHHcEMYFPNk9dCGW8A@mail.gmail.com> (raw)
In-Reply-To: <20141201215618.035399ed@digimed.co.uk>

On Mon, Dec 1, 2014 at 3:56 PM, Neil Bothwick <neil@digimed.co.uk> wrote:
> On Mon, 1 Dec 2014 20:46:54 +0000 (UTC), James wrote:
>
>> I guess my take is that eventually, linux will be very small, embedded
>> and a cluster/cloud environment is where most systems will plug in,
>> kinda like most modern cell phones. Hopefully, there'll be a systemd
>> centric version so that enables individuals and small companies can
>> remain "in the game".
>
> Given that CoreOS have sponsored some systemd development
> (systemd-networkd), I think it is reasonable to assume they plan to stick
> with systemd for the foreseeable future.

More importantly, CoreOS uses systemd to monitor/control the instances
inside containers like systemd-nspawn does, only in a more general and
powerful way.

I don't think you can currently run the CoreOS host with anything
other than systemd, and to make it so it would be a lot of work. From
[2]:

"""
Within the CoreOS world, you will almost exclusively use systemd to
manage the lifecycle of your Docker containers.
"""

Regards.

[2] https://coreos.com/docs/launching-containers/launching/getting-started-with-systemd/
-- 
Canek Peláez Valdés
Profesor de asignatura, Facultad de Ciencias
Universidad Nacional Autónoma de México


  reply	other threads:[~2014-12-01 22:33 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-01 20:46 [gentoo-user] Custom ebuilds for CoreOS James
2014-12-01 21:24 ` Rich Freeman
2014-12-01 22:10   ` [gentoo-user] " James
2014-12-01 21:56 ` [gentoo-user] " Neil Bothwick
2014-12-01 22:32   ` Canek Peláez Valdés [this message]
2014-12-03  4:13   ` Saifi Khan
2014-12-02 12:36 ` Andreas K. Huettel
2014-12-02 13:35   ` Rich Freeman
2014-12-02 15:35     ` [gentoo-user] " James
2014-12-02 16:31       ` Rich Freeman
     [not found]       ` <CAGfcS_mQP9@mail.gmail.com>
2014-12-02 17:37         ` James
2014-12-02 18:39           ` Mark David Dumlao
2014-12-03 12:41             ` J. Roeleveld
2014-12-03 14:28               ` Mark David Dumlao
2014-12-03 14:55                 ` Rich Freeman
2014-12-03 17:16                   ` Saifi Khan
2014-12-03 15:17                 ` James
2014-12-10 19:20                   ` Tom H
2014-12-02 18:55           ` Rich Freeman
2014-12-03  4:17   ` [gentoo-user] " Saifi Khan

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=CADPrc83cv8bCOL9TGsmbYqQjM5YKxewcXHHcEMYFPNk9dCGW8A@mail.gmail.com \
    --to=caneko@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