From: Kevin Berry <deathsyn@gmail.com>
To: Steve Litt <slitt@troubleshooters.com>
Cc: dng@lists.dyne.org,
"supervision@list.skarnet.org" <supervision@list.skarnet.org>,
pape@smarden.org
Subject: Re: Why /command ?
Date: Sun, 2 Jul 2017 00:54:18 +0000 [thread overview]
Message-ID: <CAORb_gDeTmT2Ez+dgOptLbPJKmwvukNoqaBshm1VE8rvrDDsaQ@mail.gmail.com> (raw)
In-Reply-To: <20170701193759.2e000f5d@mydesk.domain.cxm>
[-- Attachment #1.1: Type: text/plain, Size: 1552 bytes --]
Steve,
Have you checked for the source package to runit-run? You may find trouble
getting the Devuan devs to accept a slackpackage install, since it doesn't
meet the FHS. runit-run is a package that used to exist in Debian (and
Ubuntu imported it until 12.04, I believe), that Gerrit made to fit in the
FHS. Some other De(bi|vu)an -run packages still exist that work in a
similar manner.
On Sat, Jul 1, 2017 at 11:37 PM, Steve Litt <slitt@troubleshooters.com>
wrote:
> Hi all,
>
> I'm writing a document on how to install runit on Devuan, with the hope
> that some day it will lead to a Devuan package that makes sense and to
> the best degree possible implements the goals of the software's author.
>
> Most of it's pretty straightforward, but the runit install scripts
> (package/upgrade to be specific) create /command right off the root,
> and the runit docs suggest I create /package right off the root. These
> are things that most distros would refuse to do.
>
> So I was wondering what the original intent was in having these two
> directories directly off the root? Is it so the init and supervision
> can proceed even before partition mounts are complete? Is there some
> other reason? Can anyone recommend setups that fulfill the reasons for
> the direct-off-root dirs without having direct-off-root dirs?
>
> By the way, if the runit docs go well, I'll do the same thing with s6.
>
> Thanks,
>
> SteveT
>
> Steve Litt
> June 2017 featured book: The Key to Everyday Excellence
> http://www.troubleshooters.com/key
>
--
Kevin Berry
[-- Attachment #1.2: Type: text/html, Size: 2230 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
next prev parent reply other threads:[~2017-07-02 0:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-01 23:37 Steve Litt
2017-07-02 0:54 ` Kevin Berry [this message]
2017-07-02 7:38 ` Andy Mender
2017-07-03 13:25 ` Laurent Bercot
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=CAORb_gDeTmT2Ez+dgOptLbPJKmwvukNoqaBshm1VE8rvrDDsaQ@mail.gmail.com \
--to=deathsyn@gmail.com \
--cc=dng@lists.dyne.org \
--cc=pape@smarden.org \
--cc=slitt@troubleshooters.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).