From: Charlie Brady <charlieb-supervision@budge.apana.org.au>
Cc: supervision <supervision@list.skarnet.org>
Subject: Re: runit integration
Date: Tue, 30 May 2006 10:23:04 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.61.0605301020500.2477@e-smith.charlieb.ott.istop.com> (raw)
In-Reply-To: <J02JGG$CDDA2E0A143EE193321C00E5BEA706C5@scarlet.be>
On Tue, 30 May 2006, depuis wrote:
> The global idea would thus to provide some substitue for start-stop-daemon,
> with some wrapper permitting to use the /etc/init.d script "as is".
...
> This way, runit would be a replacement for sysvinit, minimising the migration
> and maintenance burden.
>
> I am not subscribed to this list, but I'll follow this discussion through the
> archive.
It appears to me that your discussion topic concerns specifically Debian,
and you should be discussing it with Debian architects or package
integrators. I don't think you are proposing any change to runit.
---
Charlie
next prev parent reply other threads:[~2006-05-30 14:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-30 7:57 depuis
2006-05-30 14:23 ` Charlie Brady [this message]
2006-05-30 23:40 ` Alex Efros
2006-05-31 5:04 ` Roy Lanek
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=Pine.LNX.4.61.0605301020500.2477@e-smith.charlieb.ott.istop.com \
--to=charlieb-supervision@budge.apana.org.au \
--cc=supervision@list.skarnet.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;
as well as URLs for NNTP newsgroup(s).