Bug#453106: There is no way to avoid inserting runit /etc/inittab entry

2017-01-06 Thread Dmitry Bogatov
[2011-01-16 17:28] Jonathan Nieder > > part text/plain1183 > unarchive 453106 > found 453106 runit/2.1.1-6.2 > quit > [resending now that the bug is unarchived; sorry for the noise.] > > Abhijit Hoskeri wrote: > > > The runit package does not have any way ( ex. a debconf var

Bug#453106: There is no way to avoid inserting runit /etc/inittab entry

2011-01-16 Thread Jonathan Nieder
unarchive 453106 found 453106 runit/2.1.1-6.2 quit [resending now that the bug is unarchived; sorry for the noise.] Abhijit Hoskeri wrote: > The runit package does not have any way ( ex. a debconf variable) to > avoid inserting the runit entry into inittab. This means that when runit > is install

Bug#453106: There is no way to avoid inserting runit /etc/inittab entry

2009-09-06 Thread Jameson Rollins
I agree that there should probably be a debconf questions that asks if the /etc/inittab line should be inserted. I'm of the opinion that *all* daemons should have such a question to ask if they should be started on installation. There are many instances when one would want to install a package th

Bug#453106: There is no way to avoid inserting runit /etc/inittab entry

2007-11-27 Thread Abhijit Hoskeri
Package: runit Version: 1.3.3-1 Severity: wishlist The runit package does not have any way ( ex. a debconf variable) to avoid inserting the runit entry into inittab. This means that when runit is installed in a non-active environment like a CD installation, the runit /etc/inittab entry will immedi