Frank Küster schrieb:
> [EMAIL PROTECTED]:~$ apt-cache show file-rc
I found this in a slashdot comment:
"Init Replacements: simpleinit [csiro.au], minit [www.fefe.de], jinit
[fremlin.de], runit, daemontools [cr.yp.to], serel [fastboot.org]. Progeny
[progeny.org] also has their own system based on
Frank Küster schrieb:
> [EMAIL PROTECTED]:~$ apt-cache show file-rc
I found this in a slashdot comment:
"Init Replacements: simpleinit [csiro.au], minit [www.fefe.de], jinit
[fremlin.de], runit, daemontools [cr.yp.to], serel [fastboot.org]. Progeny
[progeny.org] also has their own system based on
Replying to myself. What a shame.
Anyway, this whole thread really belongs in debian-devel.
On Thu, 20 Nov 2003, Henrique de Moraes Holschuh wrote:
> On Thu, 20 Nov 2003, Marc A. Pelletier wrote:
> > Hmm; I can see how to make it work if packages register /either/ static
> > ordering or dependen
Replying to myself. What a shame.
Anyway, this whole thread really belongs in debian-devel.
On Thu, 20 Nov 2003, Henrique de Moraes Holschuh wrote:
> On Thu, 20 Nov 2003, Marc A. Pelletier wrote:
> > Hmm; I can see how to make it work if packages register /either/ static
> > ordering or dependen
On Thu, 20 Nov 2003, Marc A. Pelletier wrote:
> Hmm; I can see how to make it work if packages register /either/ static
> ordering or dependencies, but not both.
It must, for backwards compatibility. Once the package has BOTH information
registered, dependencies would take precedence (as in disa
On Thu, 20 Nov 2003, Marc A. Pelletier wrote:
> Hmm; I can see how to make it work if packages register /either/ static
> ordering or dependencies, but not both.
It must, for backwards compatibility. Once the package has BOTH information
registered, dependencies would take precedence (as in disa
"Marc A. Pelletier" <[EMAIL PROTECTED]> schrieb:
> On Wednesday 19 November 2003 16:43, you wrote:
>> We already have at least one very good dependency-based initscript system
>> in Debian, so daemond is not alone in its troubles.
>
> Oh? Don't know it. Care to point me to it?
I did already:
[E
"Marc A. Pelletier" <[EMAIL PROTECTED]> schrieb:
> On Wednesday 19 November 2003 16:43, you wrote:
>> We already have at least one very good dependency-based initscript system
>> in Debian, so daemond is not alone in its troubles.
>
> Oh? Don't know it. Care to point me to it?
I did already:
[E
On Wednesday 19 November 2003 16:43, you wrote:
> On Tue, 18 Nov 2003, Marc A. Pelletier wrote:
> > Now /that/ is interresting and smart and is indeed likely the most
> > promising avenue for quick and dirty daemond integration in debian; the
> > problem is that from what I have understood, update-
On Wednesday 19 November 2003 16:43, you wrote:
> On Tue, 18 Nov 2003, Marc A. Pelletier wrote:
> > Now /that/ is interresting and smart and is indeed likely the most
> > promising avenue for quick and dirty daemond integration in debian; the
> > problem is that from what I have understood, update-
On Tue, 18 Nov 2003, Marc A. Pelletier wrote:
> Now /that/ is interresting and smart and is indeed likely the most promising
> avenue for quick and dirty daemond integration in debian; the problem is that
> from what I have understood, update-rc.d suffers from, by design, exactly the
> same prob
On Tue, 18 Nov 2003, Marc A. Pelletier wrote:
> Now /that/ is interresting and smart and is indeed likely the most promising
> avenue for quick and dirty daemond integration in debian; the problem is that
> from what I have understood, update-rc.d suffers from, by design, exactly the
> same prob
On Tuesday 18 November 2003 10:35, Frank Küster wrote:
> I generally agree with what Joachim said. But note that for the package
> to be integrated into debian, you would need to write a daemond version
> of update-rc.d, which is the generic interface packages use to add
> themselves to the init p
On Tuesday 18 November 2003 10:35, Frank Küster wrote:
> I generally agree with what Joachim said. But note that for the package
> to be integrated into debian, you would need to write a daemond version
> of update-rc.d, which is the generic interface packages use to add
> themselves to the init p
"Marc A. Pelletier" <[EMAIL PROTECTED]> wrote:
> In the case of (b) and (c) above, things are complicated by the fact that I
> don't personally use debian. (b) would be possible if someone would give me
> a tarball of the set of all possible boot time scripts from a sid install,
> although tes
"Marc A. Pelletier" <[EMAIL PROTECTED]> wrote:
> In the case of (b) and (c) above, things are complicated by the fact that I
> don't personally use debian. (b) would be possible if someone would give me
> a tarball of the set of all possible boot time scripts from a sid install,
> although tes
Hi,
if you don't use debian, I don't think )c makes any sense. Also, with b)
you don't give much help to your prospective maintainer, since he has to
take over a package he does not know yet. I guess it's the best to use
way a). Of course nobody can guarantee that you will find someone to
package
Hello.
I'm not entirely sure this is the best place for me to ask this, but it seemed
like a reasonable guess.
I am the author of daemond, an init replacement which
is blindingly fast and flexible. I would like to allow it to work for
debian but I am unsure how to proceed. Should I:
(a) Ask
Hi,
if you don't use debian, I don't think )c makes any sense. Also, with b)
you don't give much help to your prospective maintainer, since he has to
take over a package he does not know yet. I guess it's the best to use
way a). Of course nobody can guarantee that you will find someone to
package
Hello.
I'm not entirely sure this is the best place for me to ask this, but it seemed
like a reasonable guess.
I am the author of daemond, an init replacement which
is blindingly fast and flexible. I would like to allow it to work for
debian but I am unsure how to proceed. Should I:
(a) Ask
20 matches
Mail list logo
