All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Spray <john.spray@redhat.com>
To: Owen Synge <osynge@suse.com>, ceph-devel@vger.kernel.org
Subject: Re: autodetecting init system.
Date: Mon, 11 May 2015 17:37:30 +0100	[thread overview]
Message-ID: <5550DACA.4070504@redhat.com> (raw)
In-Reply-To: <5550D903.8000802@suse.com>

On 11/05/2015 17:29, Owen Synge wrote:
> Dear all,
>
> Many init systems are used in linux now. Some ceph code needs to know
> the init system. (I must admit I have not looked into Solaris, MacOS and
> BSD and probably should have)
>
> It would be nice to have one function that detects the init system
>
> Since the init system can be specified in ceph and ceph-deploy
> explicitly it seems to be its reasonable to fail clearly to detect init
> system.
I think I'm missing some background here.  I was under the impression 
that distros generally had a preferred init system (even if they let you 
switch), and if another is in use then compatibility links are usually 
provided (e.g. sysv-style calling through to systemd or vice versa).  
Given that, the distro packaging then uses whatever the "right" way to 
start a service is for that distro, and it's up to the distro to make 
sure that command is available.

Otherwise don't we descend into a kind of madness where a package 
post-install script can't start a service, because it doesn't know what 
command to run?

Cheers,
John


  reply	other threads:[~2015-05-11 16:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-11 16:29 autodetecting init system Owen Synge
2015-05-11 16:37 ` John Spray [this message]
2015-05-11 17:26   ` Owen Synge
2015-05-11 17:34   ` Sage Weil
2015-05-12  7:25     ` Owen Synge
2015-05-11 17:28 ` Owen Synge
2015-05-11 21:45 ` Loic Dachary
2015-05-12  7:56   ` Owen Synge
2015-05-12  9:45     ` Loic Dachary
2015-05-12 10:27       ` Owen Synge
2015-05-12 12:34         ` Loic Dachary

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=5550DACA.4070504@redhat.com \
    --to=john.spray@redhat.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=osynge@suse.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.