From: Charlie Brady <charlieb-supervision@budge.apana.org.au>
To: Amrish Purohit <amrish.purohit@elitecore.com>
Cc: supervision@list.skarnet.org
Subject: Re: endless loop at stage 2 of runit of run scripts of each service directories.
Date: Tue, 12 Aug 2008 09:01:06 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0808120859360.1029@e-smith.charlieb.ott.istop.com> (raw)
In-Reply-To: <48A12057.6050309@elitecore.com>
On Tue, 12 Aug 2008, Amrish Purohit wrote:
> Thanks for your kind suggestion.This help me a lot. i
> think this matter is not described in runit webpage.
> currently i am working on runit to customize it on fedora.
Try
http://opensourcethis.com/fedora-fast-boot-using-runit.html
http://www.gotidea.net/Linux/bootfast.html
http://fedorafastboot.wiki.sourceforge.net/
prev parent reply other threads:[~2008-08-12 13:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-11 6:28 Amrish Purohit
2008-08-11 14:13 ` Charlie Brady
2008-08-12 5:32 ` Amrish Purohit
2008-08-12 13:01 ` Charlie Brady [this message]
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.64.0808120859360.1029@e-smith.charlieb.ott.istop.com \
--to=charlieb-supervision@budge.apana.org.au \
--cc=amrish.purohit@elitecore.com \
--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).