Re: nut package freeze exception request (dependency based boot)
On Sunday 21 September 2008 01:12:34 Anton Martchukov wrote:
> On Thu, Sep 18, 2008 at 11:19:15PM +1000, Kel Modderman wrote:
> > Is the link just there to be a "virtual/persistent" link to whatever service
> > which is installed and provides the functionality?
> > Inspection of the nut package leads me to believe this may be the case, so
> > I wrote a patch for insserv which ignores any symlink in /etc/init.d/ which
> > points to another script in /etc/init.d/, as I am not aware of any cases where
> As for ups-monitor that yes, it's the case.
I looked at a couple of the packages you identified and this was also the case.
The nut package should reinstate the symlink then, and new insserv uploaded
with modification to handle /etc/init.d/symlink -> script case.
> As for symlinks
> I only heared about debian-edu earlier in this thread:
> > Petter Reinhold:
> >> 2) Changhe insserv to not count symlinks at all (do not know about
> >> possible affects about it)
> >This will break debian-edu (which symlink in a script used for the
> >first boot after installation, and remove it after the boot). I am
> >not sure about other effects.
> But I guess it's realted to ignoring symlinks at all.
Yeah, the patch committed would ignore symlinks to a relative path which
contain no path separator, which can only be scripts in the same dir that
insserv is reading scripts from (/etc/init.d/).
> Can you fill a bug to push this patch to unstable?