Applied, built, and posted to the website.
On Sat, 21 Jun 2003, Tobias Burnus wrote:
> Hi,
>
> I just realized that currenty the behaviour of /usr/lib/lsb/install_initd
> and /usr/lib/lsb/removed_initd is undefined if no the dependencies are not
> fulfilled or will be broken, respectively.
>
> The attached patch adds these rules:
>
> a) install_initd
> (i) successful installation: exit 0
> (ii) already installed: exit 0
> (iii) missing required boot facility: exit 1
> (iv) other errors (cannot access init script database etc.):
> undefined/ignored by this patch (an exit status != 0 is useful!)
>
> b) remove_initd
> (i) successfully removed: exit 0
> (ii) not installed: exit 0
> (iii) other init script depends on this one: exit 1 and not removed
> (iv) other problems: not defined/ignored by this patch
> (an exit status != 0 is useful in this case!)
>
> Especially the wording of the remove_initd paragraph is a bit clumsy. If
> you find better word, go ahead!
>
> The described behaviour is implemented that way in
> SuSE 8.2/UnitedLinux 1.0 and with restrictions in Debian.
> (Debian gives these exit status codes but it will install/remove a package
> nevertheless.)
>
> Don't forget to run "make" in lsb/spec/wip/sysinit/ after applying this
> patch.
>
>
> Tobias
>
Stuart
[email protected] Free Standards Group
Lead Developer, Written Specification Linux Standard Base
1024D/37A79149: 0791 D3B8 9A4C 2CDC A31F
BD03 0A62 E534 37A7 9149
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.