public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mark Pariente <markpariente@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] systemd - are we forced to switch?
Date: Mon, 22 Jul 2013 21:24:36 -0700	[thread overview]
Message-ID: <1374553476.25784.8.camel@siegeengine> (raw)
In-Reply-To: <CAGK8UzCHYqgdMWfo=Fav2wcYMRy2uUTKTFUOpSFD0M79itJj+Q@mail.gmail.com>

On Mon, 2013-07-22 at 17:14 +0200, Volker Armin Hemmann wrote:
> yeah, because it is so great to have that monster systemd on your box.
> Because xml configs are awesome and binary logs even more and I always
> wanted an init with builtin webbrowser. Security? bah, not needed. 
> 
> 
> So when do I have to install mysql to use it? How long until some crap
> ala windows-registry is forced down my throat?

Nobody is forcing you to use anything. These are all upstream (GNOME,
freedestkop) decisions, you can't expect them to maintain code that
doesn't follow their technical direction. If you don't like it you can
fork or go use/contribute to other projects all you want. This is the
power of open source, no one can take choice away from you, they can
just make your choice a lot harder to realize.

--Mark




  parent reply	other threads:[~2013-07-23  4:24 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-22  7:03 [gentoo-user] systemd - are we forced to switch? Helmut Jarausch
2013-07-22  8:51 ` Volker Armin Hemmann
2013-07-22 11:33 ` Samuli Suominen
2013-07-22 12:53   ` Pandu Poluan
2013-07-22 13:35 ` Philip Webb
2013-07-22 13:39   ` András Csányi
2013-07-22 13:40     ` Alan McKinnon
2013-07-22 18:17   ` Bruce Hill
2013-07-22 15:02 ` Canek Peláez Valdés
2013-07-22 15:14   ` Volker Armin Hemmann
2013-07-22 22:10     ` Mark David Dumlao
2013-07-23  4:24     ` Mark Pariente [this message]
2013-07-22 16:57   ` Samuli Suominen
2013-07-22 19:57   ` Michael Hampicke
2013-07-22 20:55     ` Volker Armin Hemmann
2013-07-22 21:59       ` Mark David Dumlao
2013-07-23  2:58         ` covici
2013-07-23  3:09           ` Canek Peláez Valdés
2013-07-23  9:31             ` covici
2013-07-23  9:41               ` Alan McKinnon
2013-07-23 16:31                 ` gottlieb
2013-07-23 18:19                   ` Canek Peláez Valdés
2013-07-26 13:39                     ` gottlieb
2013-07-27 16:55                       ` [gentoo-user] " walt
2013-07-27 22:24                         ` covici
2013-07-27 22:30                           ` Mark David Dumlao
2013-07-27 23:14                             ` covici
2013-07-23 18:07               ` [gentoo-user] " Canek Peláez Valdés
2013-07-23  6:11     ` András Csányi
2013-07-23  6:24       ` Samuli Suominen
2013-07-23 13:56       ` Michael Hampicke
2013-07-23 17:49     ` Pavel Volkov
     [not found]   ` <CAG2nJkOzec3hDfYg7+R5n+iWdzBJ=WPpcK8YbALjNLe03n2L_w@mail.gmail.com>
     [not found]     ` <CAG2nJkOFBaru-yOcrOrNjX-r8Rf+gtKTNdW+4nUndfv2766wTg@mail.gmail.com>
2013-07-22 21:46       ` Mark David Dumlao
2013-07-23  5:43         ` Samuli Suominen
2013-07-23  6:54           ` [gentoo-user] " Nikos Chantziaras
2013-07-23  7:04             ` András Csányi
2013-07-23 18:11               ` Canek Peláez Valdés
2013-07-24 17:28                 ` covici
2013-07-24 17:38                   ` Canek Peláez Valdés
2013-07-24 20:30                     ` covici
2013-07-23  7:15             ` Samuli Suominen

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=1374553476.25784.8.camel@siegeengine \
    --to=markpariente@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