| 1 |
On Tue, Dec 2, 2014 at 7:36 AM, Andreas K. Huettel <dilfridge@g.o> wrote: |
| 2 |
> Am Montag 01 Dezember 2014, 20:46:54 schrieb James: |
| 3 |
>> Anyone know anything about coreos? |
| 4 |
>> |
| 5 |
>> Lookie lookie, they have "ebuilds"? |
| 6 |
>> |
| 7 |
> |
| 8 |
> According to wikipedia, CoreOS is a fork of ChromeOS [1]. |
| 9 |
> |
| 10 |
> ChromeOS is most definitely a Gentoo derivative [2,3,4], even though that fact |
| 11 |
> is not really well known (and not really publicised). |
| 12 |
|
| 13 |
Interesting. Talk about a march of init systems. You have Gentoo |
| 14 |
which defaults to openrc and supports systemd, to ChromeOS which only |
| 15 |
supports upstart, to CoreOS which uses systemd. |
| 16 |
|
| 17 |
In any case, the whole point of both ChromeOS and CoreOS is that |
| 18 |
they're hosts for running applications completely outside of the usual |
| 19 |
unix-y approach of sticking stuff in /usr. Applications on ChromeOS |
| 20 |
are Chrome extensions and the like, and applications on CoreOS are |
| 21 |
containers. The whole point of both is to abstract away all the guts |
| 22 |
of how the OS operates, so the choice of init really shouldn't matter |
| 23 |
much to anybody using either. If you really want to stick stuff in |
| 24 |
/usr and interact with host processes directly, then you really should |
| 25 |
find a distro which isn't designed to be a black box in this regard. |
| 26 |
|
| 27 |
-- |
| 28 |
Rich |
Archives