Re: Bug#545691: diverting telinit
On Mon, Oct 26, 2009 at 07:23:12AM -0500, Manoj Srivastava wrote:
> On Mon, Oct 26 2009, Bastian Blank wrote:
>
> > On Mon, Oct 26, 2009 at 10:40:56AM +0100, Bastian Blank wrote:
> >> On Fri, Oct 23, 2009 at 12:43:18PM -0500, Manoj Srivastava wrote:
> >> > I created a elaborate test case tos ee if we are in a chroot, if
> >> > not if /proc/1 is actually /sbin/init, and that telinit exists (example
> >> > below).
> >> Why are they not able to ignore the errors from telinit? All checked
> >> packages uses this to ask init to reexecute itself and free old library
> >> references. Nothing in this is critical to the usability of the packages
> >> themself or the system.
> >
> > Oh, and this could be made even easier by defining file-based triggers
> > in the package providing init instead of doing it in all the
> > dependencies.
>
> In which case it definitely deserves discussion, some
> coordination, and perhaps a policy proposal, as well as a more generic
> solution. Which files would we be triggering on?
No file would. Instead packages postint would use dpkg-trigger to activate
the trigger and let the package providing the trigger deal with it.
Cheers,
--
Bill. <ballombe@debian.org>
Imagine a large red swirl here.
Reply to: