Michael Biebl <[EMAIL PROTECTED]> writes:
> Marc 'HE' Brockschmidt wrote:
>> | What about a simple solution: Ask dpkg if sysvrc is installed. If not:
>> | Do the update-rc.d remove/start dance as currently implemented. If it
>> | used, check the current state of /etc/rc?.d/ and insert the new links
Marc 'HE' Brockschmidt wrote:
> Michael Biebl <[EMAIL PROTECTED]> writes:
>
>> Marc 'HE' Brockschmidt wrote:
>>> Petter Reinholdtsen <[EMAIL PROTECTED]> writes:
[Marc Brockschmidt]
> I don't see how this is relevant to detect in which runlevels avahi
> should be started. My basic idea
Michael Biebl <[EMAIL PROTECTED]> writes:
> Marc 'HE' Brockschmidt wrote:
>> Petter Reinholdtsen <[EMAIL PROTECTED]> writes:
>>> [Marc Brockschmidt]
I don't see how this is relevant to detect in which runlevels avahi
should be started. My basic idea:
>>> I agree. I believe this approach
Marc 'HE' Brockschmidt wrote:
> Petter Reinholdtsen <[EMAIL PROTECTED]> writes:
>> [Marc Brockschmidt]
>>> I don't see how this is relevant to detect in which runlevels avahi
>>> should be started. My basic idea:
>> I agree. I believe this approach should work just fine for any
>> sysv-based boot
Petter Reinholdtsen <[EMAIL PROTECTED]> writes:
> [Marc Brockschmidt]
>> I don't see how this is relevant to detect in which runlevels avahi
>> should be started. My basic idea:
> I agree. I believe this approach should work just fine for any
> sysv-based boot system, independend of the use of ins
[Marc Brockschmidt]
> I don't see how this is relevant to detect in which runlevels avahi
> should be started. My basic idea:
I agree. I believe this approach should work just fine for any
sysv-based boot system, independend of the use of insserv. The reason
I mention it, is that several patches
Petter Reinholdtsen <[EMAIL PROTECTED]> writes:
> [Marc Brockschmidt]
>> What about a simple solution: Ask dpkg if sysvrc is installed. If
>> not: Do the update-rc.d remove/start dance as currently
>> implemented. If it used, check the current state of /etc/rc?.d/ and
>> insert the new links accord
[Steve Langasek]
> Why do sequence numbers matter for *dependency*-based boot sequences?
Ah, I thought this was common knowledge, and forgot to make it clear.
See
http://lists.debian.org/debian-devel-announce/2008/01/msg4.html>
and my talk at FOSDEM 2008 (linked inn from
http://wiki.debian.org
On Sun, Sep 07, 2008 at 07:13:15PM +0200, Petter Reinholdtsen wrote:
> [Marc Brockschmidt]
> > What about a simple solution: Ask dpkg if sysvrc is installed. If
> > not: Do the update-rc.d remove/start dance as currently
> > implemented. If it used, check the current state of /etc/rc?.d/ and
> > in
[Marc Brockschmidt]
> What about a simple solution: Ask dpkg if sysvrc is installed. If
> not: Do the update-rc.d remove/start dance as currently
> implemented. If it used, check the current state of /etc/rc?.d/ and
> insert the new links accordingly to that. Would you be willing to
> implement thi
Petter Reinholdtsen <[EMAIL PROTECTED]> writes:
> [Michael Biebl]
>> Been there, done that. There is no way to satisfy everyone.
> Yes, it suck to have to remove all start and stop symlinks to modify
> the current settings. The proper solution is to add a update-rc.d API
> to change individual set
Steve Langasek wrote:
> On Sat, Aug 23, 2008 at 03:52:00AM +0200, Petter Reinholdtsen wrote:
>
> Well, so the current solution breaks all of file-rc, sysv-rc, and insserv;
> is unnecessary for insserv (because the sequence numbers don't need to be
> reset for a dependency-based init system); and
On Sat, Aug 23, 2008 at 03:52:00AM +0200, Petter Reinholdtsen wrote:
> [Steve Langasek]
> > So it's not at all true that it's "not an option" in Debian - it
> > just happens to not be the option you prefer. I, OTOH, think it's
> > the better option;
> Just for the record, I would prefer Debian t
[Steve Langasek]
> So it's not at all true that it's "not an option" in Debian - it
> just happens to not be the option you prefer. I, OTOH, think it's
> the better option;
Just for the record, I would prefer Debian to drop file-rc, and avoid
the complexity of having two different systems manipu
On Fri, Aug 22, 2008 at 11:39:41AM +0200, Petter Reinholdtsen wrote:
> I do not have any better solutions. The only bad alternative I have
> seen used is to remove known symlinks directly in /etc/rcX.d/, and
> this do not work with file-rc and insserv. It is done in Ubuntu,
> because they have dr
On Fri, Aug 22, 2008 at 11:39:41AM +0200, Petter Reinholdtsen wrote:
> > Question is, if there are more users out there that use file-rc /
> > insserv or have disabled/modified avahi-daemon start symlinks (which
> > usually only knowledgeable users will do).
> > Please keep in mind that insserv was
[Michael Biebl]
> Been there, done that. There is no way to satisfy everyone.
Yes, it suck to have to remove all start and stop symlinks to modify
the current settings. The proper solution is to add a update-rc.d API
to change individual settings, and Kel Modderman has made a proposal
for this, b
Steve Langasek wrote:
> On Fri, Aug 22, 2008 at 10:10:36AM +0200, Michael Biebl wrote:
>> Marc 'HE' Brockschmidt wrote:
>>> Michael Biebl <[EMAIL PROTECTED]> writes:
Marc 'HE' Brockschmidt wrote:
>
The diff for the debian related changes is in debian.diff.gz
>
>>> +# update init scr
On Fri, Aug 22, 2008 at 10:10:36AM +0200, Michael Biebl wrote:
> Marc 'HE' Brockschmidt wrote:
> > Michael Biebl <[EMAIL PROTECTED]> writes:
> >> Marc 'HE' Brockschmidt wrote:
> >> The diff for the debian related changes is in debian.diff.gz
> > +# update init script symlinks for new runlevel
Marc 'HE' Brockschmidt wrote:
> Michael Biebl <[EMAIL PROTECTED]> writes:
>> Marc 'HE' Brockschmidt wrote:
>> The diff for the debian related changes is in debian.diff.gz
>
> +# update init script symlinks for new runlevels and priorities for
> upgrades
> +# from older versions
> +if
Michael Biebl <[EMAIL PROTECTED]> writes:
> Marc 'HE' Brockschmidt wrote:
>> Could you please provide a cleaned up diff (without this and the autofoo
>> crap) for review?
> No problem.
> I created a diff (avahi.diff.gz) between 0.6.22 and 0.6.23 using the git
> repository. As most of the changes ar
Marc 'HE' Brockschmidt wrote:
Michael Biebl <[EMAIL PROTECTED]> writes:
one of the many bug fixes in avahi between 0.6.22-3 and 0.6.23-2 has
been, to start the daemon earlier in the boot sequence, so other
services can make use of it.
OK, the diff is simply horrible, due to a few hundred occur
Michael Biebl <[EMAIL PROTECTED]> writes:
> one of the many bug fixes in avahi between 0.6.22-3 and 0.6.23-2 has
> been, to start the daemon earlier in the boot sequence, so other
> services can make use of it.
OK, the diff is simply horrible, due to a few hundred occurences of
this:
-# $Id: autog
Hi,
one of the many bug fixes in avahi between 0.6.22-3 and 0.6.23-2 has
been, to start the daemon earlier in the boot sequence, so other
services can make use of it.
As we now have a cups version in testing which uses avahi, it would be a
good idea to have avahi 0.6.23-2 in lenny, so the cu
On Wed, Mar 14, 2007 at 12:09:11AM +0100, Sjoerd Simons wrote:
> Last week i uploaded a new avahi, which fixes delays of a few seconds on
> ifup/ifdown because of the checking the avahi package does. I didn't mail
> for
> an freeze exception earlier because i wanted to get some feedback fi
Sjoerd Simons a écrit :
Hi,
Last week i uploaded a new avahi, which fixes delays of a few seconds on
ifup/ifdown because of the checking the avahi package does. I didn't mail for
an freeze exception earlier because i wanted to get some feedback first and i
didn't think we were in a big hu
Hi,
Last week i uploaded a new avahi, which fixes delays of a few seconds on
ifup/ifdown because of the checking the avahi package does. I didn't mail for
an freeze exception earlier because i wanted to get some feedback first and i
didn't think we were in a big hurry :)
Now with toda
* Loïc Minier ([EMAIL PROTECTED]) [070113 09:39]:
> Hi,
>
> On Sat, Jan 13, 2007, Andreas Barth wrote:
> > I approved avahi now - for nss-mdns, you are sure the RC bugs are
> > actually in Etch, and weren't introduced during the changes in sid?
>
> The dependency on zeroconf, the use of
Hi,
On Sat, Jan 13, 2007, Andreas Barth wrote:
> I approved avahi now - for nss-mdns, you are sure the RC bugs are
> actually in Etch, and weren't introduced during the changes in sid?
The dependency on zeroconf, the use of the legacy mode, the export of
too many symbols (causing crashe
* Loïc Minier ([EMAIL PROTECTED]) [070112 10:45]:
> Please review and unblock avahi/0.6.16-2 and nss-mdns/0.9-0.1 as these
> carry plenty of RC bug fixes. Changelogs below:
I approved avahi now - for nss-mdns, you are sure the RC bugs are
actually in Etch, and weren't introduced during the chan
Hi,
Please review and unblock avahi/0.6.16-2 and nss-mdns/0.9-0.1 as these
carry plenty of RC bug fixes. Changelogs below:
avahi (0.6.16-2) unstable; urgency=low
* debian/patches/02_avahi-daemon-init-unicast-disable.patch
- Renamed to 03_avahi-daemon-init-unicast-disable.patch
31 matches
Mail list logo
