From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: Thilo Bangert <bangert@gentoo.org>
Subject: Re: [gentoo-dev] Re: The future of sys-apps/openrc in Gentoo
Date: Tue, 24 Aug 2010 12:19:12 -0400 [thread overview]
Message-ID: <201008241219.12983.vapier@gentoo.org> (raw)
In-Reply-To: <201008241457.49173.bangert@gentoo.org>
[-- Attachment #1: Type: Text/Plain, Size: 872 bytes --]
On Tuesday, August 24, 2010 08:57:45 Thilo Bangert wrote:
> > , efficient, known-good solution
> > that does what you'd expect it to do and replace it with a new thingy
> > that doesn't provide all the features, is harder to debug etc. etc.? I
> > just don't see any *advantage* from it apart from saying "OMG HAZ NEW
> > FEATRUES" :)
>
> one feature of systemd is, that it has an active upstream.
... and so does openrc
> no, i dont think it would be a good idea to switch to systemd, just yet.
> but like the original baselayout was breaking new ground back when it
> first was developed, so is systemd. it does things differently and may not
> have all features yet, but from the outset it appears to be vastly
> superior to sysv-style inits, upstart and openrc.
nothing is stopping you or anyone else from making systemd work under Gentoo
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2010-08-24 16:16 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-04 14:29 [gentoo-dev] The future of sys-apps/openrc in Gentoo Lars Wendler
2010-07-04 15:01 ` [gentoo-dev] " Nikos Chantziaras
2010-07-04 18:23 ` Daniel Schömer
2010-07-04 15:17 ` [gentoo-dev] " Fabio Erculiani
2010-07-04 18:35 ` Markos Chandras
2010-07-04 19:39 ` [gentoo-dev] " Ryan Hill
2010-07-04 20:09 ` Jory A. Pratt
2010-07-05 2:23 ` Richard Freeman
2010-07-05 3:32 ` Nirbheek Chauhan
2010-07-05 8:57 ` Duncan
2010-08-23 15:05 ` Gilles Dartiguelongue
2010-08-23 15:16 ` Jory A. Pratt
2010-08-23 16:25 ` Mike Frysinger
2010-08-23 17:26 ` Olivier Crête
2010-08-23 18:09 ` Mike Auty
2010-08-23 18:28 ` Olivier Crête
2010-08-23 18:43 ` Patrick McLean
2010-08-24 9:19 ` Patrick Lauer
2010-08-24 12:57 ` Thilo Bangert
2010-08-24 14:30 ` Richard Freeman
2010-08-24 16:38 ` Joshua Saddler
2010-08-24 17:18 ` Christian Faulhammer
2010-08-25 3:21 ` Joshua Saddler
2010-08-25 3:57 ` Nathan Zachary
2010-08-25 4:14 ` Joshua Saddler
2010-08-25 16:37 ` Richard Freeman
2010-08-25 19:06 ` Mike Frysinger
2010-08-25 20:16 ` Richard Freeman
2010-08-26 0:29 ` Duncan
2010-08-26 17:02 ` Richard Freeman
2010-08-26 18:29 ` Mike Frysinger
2010-08-27 1:55 ` Duncan
2010-08-24 16:19 ` Mike Frysinger [this message]
2010-08-24 19:07 ` Thilo Bangert
2010-07-05 13:03 ` Anthony G. Basile
2010-07-04 16:28 ` [gentoo-dev] " Pacho Ramos
2010-07-04 21:02 ` Mike Frysinger
2010-07-04 22:04 ` Lars Wendler
2010-07-04 22:15 ` Mike Frysinger
2010-07-04 23:23 ` Lars Wendler
2010-07-05 1:03 ` Olivier Crête
2010-07-05 1:30 ` Brian Harring
2010-07-05 16:11 ` Enrico Weigelt
2010-07-05 3:23 ` Mike Frysinger
2010-07-05 4:13 ` Nirbheek Chauhan
2010-07-05 16:13 ` Enrico Weigelt
2010-07-07 0:56 ` Doug Goldstein
2010-07-05 7:29 ` Patrick Lauer
2010-08-23 14:17 ` Jon Portnoy
2010-08-23 20:21 ` Luca Barbato
2010-08-23 20:30 ` Anthony G. Basile
2010-08-23 21:07 ` Mike Frysinger
2010-08-24 9:08 ` Luca Barbato
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=201008241219.12983.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=bangert@gentoo.org \
--cc=gentoo-dev@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