From: Andrew Savchenko <bircoph@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [openrc] [systemd] make `service` common for both OpenRC and SystemD (like Debian/Ubuntu/whatever did)
Date: Sun, 17 Sep 2017 18:44:11 +0300 [thread overview]
Message-ID: <20170917184411.49bb1d5af5326468a3b66b0b@gentoo.org> (raw)
In-Reply-To: <1505642707.1554.1.camel@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 2381 bytes --]
On Sun, 17 Sep 2017 12:05:07 +0200 Michał Górny wrote:
> W dniu nie, 17.09.2017 o godzinie 12∶12 +0300, użytkownik Andrew
> Savchenko napisał:
> > On Sun, 17 Sep 2017 02:56:08 +0700 Vadim A. Misbakh-Soloviov wrote:
> > > Hi there!
> > >
> > > Every time I switch from mastering service on my work (Ubuntu-powered) to my
> > > own server farm (Gentoo powered) I'm going a bit frustrated: Ubuntu (with all
> > > my hate to many other things in it) has nice user-friendly way of managing
> > > services: you can freely call any of `service <servicename> action` irrelevant
> > > to which init-system is currently in use. Will it be systemd, or (whatever
> > > there is alternative there). `service` wrapper will detect it anyway and will
> > > do the proper things (forward it to either systemd or another service
> > > manager).
> > >
> > > I'd like to suggest to remove `service` widget from openrc and make it the
> > > part of (which package? baselayout?)? Here is a pseudocode of how I see it:
> > >
> > > ```
> > > servicename=${1}
> > > action=${2}
> > >
> > > if in_systemd; then
> > > systemctl "${action}" "${servicename}"
> > > else
> > > rc-service "${servicename}" "${action}"
> > > fi
> > > ```
> > >
> > > Well, actually, there may be some more logic (for example, instance units
> > > (`unit@instance` in `systemd` vs `unit.instance` in openrc), "enable" action
> > > (forward it to `rc-update add` for `openrc`, probably) and maybe some more.
> > > But anyway, the conception is something like that.
> > >
> > >
> > > What do you think about that?
> >
> > https://xkcd.com/927/
> >
> > We will create even more confusion for Gentoo users with one more
> > tool to do the same stuff.
> >
> > Of course you are free to implement some separate wrapper package,
> > but it must be completely optional, since some users will have no
> > use for it including myself.
> >
> > Really, unifying distributions is futile. We will have either the
> > same and only distribution (to rule them all) or an attempt will
> > fail. The same way you can try to unify emerge and apt tools via
> > some wrapper manager.
>
> Fun fact: systemd was created to unify distributions in one init system.
Exactly. This case is perfectly covered by https://xkcd.com/927/ :)
Best regards,
Andrew Savchenko
[-- Attachment #2: Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-09-17 15:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-16 19:56 [gentoo-dev] [openrc] [systemd] make `service` common for both OpenRC and SystemD (like Debian/Ubuntu/whatever did) Vadim A. Misbakh-Soloviov
2017-09-16 20:09 ` Rich Freeman
2017-09-17 9:12 ` Andrew Savchenko
2017-09-17 10:05 ` Michał Górny
2017-09-17 15:44 ` Andrew Savchenko [this message]
2017-09-18 2:22 ` [gentoo-dev] " Duncan
2017-09-18 9:32 ` Vadim A. Misbakh-Soloviov
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=20170917184411.49bb1d5af5326468a3b66b0b@gentoo.org \
--to=bircoph@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