In data Saturday 12 February 2011 05:55:16, Joachim Breitner ha scritto:
I included some patches to have nodm gracefully uses the upstart job.
Since those patches permits to have both init scripts in the system, no
matter if upstart or sysvinit is used, a little more effort is required
to
[Marco Amadori]
I think it would be interesting for wheezy to easely permit an Admin
to choose an alternate init system
Sound like a good idea, if it do not give the Debian project a lot of
unneeded work.
and to permit to package maintainer to carefully provide init script
tailored for a
Hi,
Am Montag, den 14.02.2011, 13:57 +0100 schrieb Petter Reinholdtsen:
I believe we need to come up with a way where most or all package
maintainers (perhaps those handling kernel events and early boot stuff
should be expected) only need to maintain one boot setup for their
package, and this
]] Petter Reinholdtsen
| I believe we need to come up with a way where most or all package
| maintainers (perhaps those handling kernel events and early boot stuff
| should be expected) only need to maintain one boot setup for their
| package, and this boot setup should be used by all the
On Mon, Feb 14, 2011 at 3:38 PM, Tollef Fog Heen tfh...@err.no wrote:
]] Petter Reinholdtsen
| I believe we need to come up with a way where most or all package
| maintainers (perhaps those handling kernel events and early boot stuff
| should be expected) only need to maintain one boot setup
On Mon, 14 Feb 2011, Tollef Fog Heen wrote:
That would mean limiting each init system to the limitations of the most
limited init system, which would be a sad state of affairs. Also, I
Yes. So, we also have to set where we want the low bar.
don't believe there's a 1:1 correspondence between
a way like metainit? http://wiki.debian.org/MetaInit
The project died some two or three years ago and anyone is welcome to
try to revive it.
Mh it claims it would work only for simple scripts, not for any kind of
scripts, so not all the packages could be converted.
Bye
--
Salvo Tomaselli
On Mon, Feb 14, 2011 at 11:17:20AM +0100, Marco Amadori wrote:
In data Saturday 12 February 2011 05:55:16, Joachim Breitner ha scritto:
I included some patches to have nodm gracefully uses the upstart job.
Since those patches permits to have both init scripts in the system, no
matter if
On Feb 14, Tollef Fog Heen tfh...@err.no wrote:
That would mean limiting each init system to the limitations of the most
limited init system, which would be a sad state of affairs. Also, I
don't believe there's a 1:1 correspondence between the semantics of all
the different init systems,
On Monday 14 February 2011 20:55:06 Tollef Fog Heen wrote:
| I believe we need to come up with a way where most or all package
| maintainers (perhaps those handling kernel events and early boot stuff
| should be expected) only need to maintain one boot setup for their
| package, and this boot
On Monday 14 February 2011 21:00:09 Olaf van der Spek wrote:
On Mon, Feb 14, 2011 at 3:38 PM, Tollef Fog Heen tfh...@err.no wrote:
]] Petter Reinholdtsen
| I believe we need to come up with a way where most or all package
| maintainers (perhaps those handling kernel events and early boot
On Monday 14 February 2011 21:07:57 Steve Langasek wrote:
if [ -e /etc/init/${NAME}.conf ] /sbin/telinit --version /dev/null
21
| grep -qs upstart
then
exit 0
fi
inside the sysvinit init script.
This does not appear to be consistent with
]] Henrique de Moraes Holschuh
| On Mon, 14 Feb 2011, Tollef Fog Heen wrote:
| That would mean limiting each init system to the limitations of the most
| limited init system, which would be a sad state of affairs. Also, I
|
| Yes. So, we also have to set where we want the low bar.
I'd
Hi,
Am Montag, den 14.02.2011, 15:38 +0100 schrieb Tollef Fog Heen:
]] Petter Reinholdtsen
| I believe we need to come up with a way where most or all package
| maintainers (perhaps those handling kernel events and early boot stuff
| should be expected) only need to maintain one boot setup
14 matches
Mail list logo
