public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Volker Armin Hemmann <volkerarmin@googlemail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: gigabyte mobo latency
Date: Tue, 21 Oct 2014 19:41:15 +0200	[thread overview]
Message-ID: <54469ABB.7050308@googlemail.com> (raw)
In-Reply-To: <CAGfcS_=Z_iq-gkP-j3-L3MKXec-bCMHdVNOzO5S_C3uFEkG69g@mail.gmail.com>

Am 20.10.2014 um 01:34 schrieb Rich Freeman:
> On Sun, Oct 19, 2014 at 5:45 PM, Volker Armin Hemmann
> <volkerarmin@googlemail.com> wrote:
>> Am 19.10.2014 um 20:56 schrieb Rich Freeman:
>>> On Sun, Oct 19, 2014 at 12:41 PM, James <wireless@tampabay.rr.com> wrote:
>>> As far as docs go - what specifically is unclear? Systemd is rapidly
>>> evolving so things do get out of date, but for the most part stuff
>>> like this can be found in man systemd.exec and such. Lennart's series
>>> of blog posts on system administration using systemd is a very good
>>> place to start. -- Rich
>> and you are fine with that? That the package that becomes Pid1 is such
>> an unstable, ever involving mess that not even the docs are keeping up
>> with it?
> If I wasn't fine with it I'd hardly be running Gentoo.  :)  You just
> described half of the distro, though it isn't changing as rapidly as
> it used to.
>
> Most of the issues are in the init scripts, which technically aren't
> really part of systemd.  It is fairly immature everywhere.  If you
> want a really stable experience then you should probably stick with
> RHEL or Debian Stable.  :)
>
>> You just gave me another reason not to use systemd.
>>
> Sounds like you didn't really need one.  It is a free country - you're
> no more required to run systemd than any Gentoo developer is required
> to fix openrc init scripts or systemd units...
>
> --
> Rich
>
> .
>

you make that sound like a threat. But that does not work with me ;)

I have dealt with Slackware in the past. Had no probs back then, why
should I be scared now?


  reply	other threads:[~2014-10-21 17:41 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-18 15:49 [gentoo-user] gigabyte mobo latency James
2014-10-18 16:00 ` Volker Armin Hemmann
2014-10-18 16:26   ` [gentoo-user] " James
2014-10-18 19:27     ` Philip Webb
2014-10-18 20:24       ` Volker Armin Hemmann
2014-10-18 20:34         ` Neil Bothwick
2014-10-18 21:39         ` James
2014-10-19 11:25           ` Dale
2014-10-18 21:25 ` [gentoo-user] " thegeezer
2014-10-18 21:51   ` [gentoo-user] " James
2014-10-18 23:02     ` thegeezer
2014-10-19  3:15       ` James
2014-10-19 12:02         ` thegeezer
2014-10-19 16:41           ` James
2014-10-19 17:03             ` Dale
2014-10-19 20:03               ` James
2014-10-20  3:13                 ` Dale
2014-10-19 18:56             ` Rich Freeman
2014-10-19 20:40               ` James
2014-10-19 20:57                 ` Alan McKinnon
2014-10-19 21:35                 ` Rich Freeman
2014-10-19 21:45               ` Volker Armin Hemmann
2014-10-19 23:34                 ` Rich Freeman
2014-10-21 17:41                   ` Volker Armin Hemmann [this message]
2014-10-22  1:35 ` Nikos Chantziaras

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=54469ABB.7050308@googlemail.com \
    --to=volkerarmin@googlemail.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