From: "David Kaufman" <david@gigawatt.com>
Subject: runit-run install failed - conflict w/unofficial daemontools-run?
Date: Mon, 13 Nov 2006 15:13:26 -0500 [thread overview]
Message-ID: <00eb01c70760$2f2ece80$020010ac@cylon> (raw)
Hi,
I just tried to install runit and runit-run on a Debian sarge setup
which already has var-qmail, qmail-run, djbdns and daemontools installed
from http://smarden.org/pape/Debian/
I was using dselect, and this was the output:
This package diverts sysvinit's /sbin/init binary. Use
# /sbin/init.sysv 6
to reboot the system with runit as process no 1 after installing this
package.
Please read the runit documentation before proceeding:
http://smarden.org/runit/
Press ENTER to continue, press Ctrl-C to abort...
Adding `diversion of /sbin/init to /sbin/init.sysv by runit-run'
Adding `diversion of /usr/share/man/man8/init.8.gz to
/usr/share/man/man8/init.sysv.8.gz by runit-run'
Setting up runit (1.0.5-3) ...
There already is an SV entry in /etc/inittab. In order to have
this package add an entry with the name SV to have runit's service
supervision started by sysvinit, you need to remove or rename the
current SV entry first.
Installation failed.
0;10m
dpkg: error processing runit (--configure):
subprocess post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of runit-run:
runit-run depends on runit (>> 1.0.5-0); however:
Package runit is not configured yet.
dpkg: error processing runit-run (--configure):
dependency problems - leaving unconfigured
"There already is an SV entry in /etc/inittab" seemed to be the problem,
so I looked in there and found:
#-- daemontools-run begin
SV:123456:respawn:/command/svscanboot
#-- daemontools-run end
...which I assume is from my previous daemontools-run installation.
Should I just rename the old SV entry in there? I'm not familiar with
editing /etc/inittab entries. If so, does it matter what I rename it
to?
I sure hope the unofficial daemontools-run and runit-run are compatible
with one another!
BTW Here are my apt sources:
===[/etc/apt/sources.list]===
deb http://http.us.debian.org/debian stable main contrib non-free
deb http://non-us.debian.org/debian-non-US stable/non-US main contrib
non-free
deb http://security.debian.org stable/updates main contrib non-free
deb http://www.backports.org/debian/ sarge-backports main
deb http://smarden.org/pape/Debian/ sarge unofficial
=============================
Thanks for any suggestion anyone might have to offer!
-dave
next reply other threads:[~2006-11-13 20:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-13 20:13 David Kaufman [this message]
2006-11-14 3:47 ` David Kaufman
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='00eb01c70760$2f2ece80$020010ac@cylon' \
--to=david@gigawatt.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 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).