Re: install_initd clobbers system init symlinks
Thorsten Kukuk <[email protected]>
| Newsgroups | gmane.linux.lsb.discuss |
|---|---|
| Organization | SuSE Linux AG, Nuernberg, Germany |
| Message-ID | <[email protected]> |
On Mon, Jul 14, Bart Whiteley wrote: > insserv is not an option. install_initrd might someday > be an option. Currently, if you want your app to run on > multiple distros, explicitly creating symlinks in postinstall > is the best way to go. No, it is the wrong way to go. If you use explicitly created symlinks, you assume that the numbers of the symlinks for the other scripts you need are always the same on all Distributions. This is plain wrong and will never happen. Instead you could add a LSB conform header to the third party init script, which has the correct requirements. It is easy (only cut&paste from a skeleton or another script) and you solved the problem the correct way. The script will even work after an update of the distribution. Thorsten -- Thorsten Kukuk http://www.suse.de/~kukuk/ [email protected] SuSE Linux AG Deutschherrnstr. 15-19 D-90429 Nuernberg -------------------------------------------------------------------- Key fingerprint = A368 676B 5E1B 3E46 CFCE 2D97 F8FD 4E23 56C6 FB4B
signature.asc
(application/pgp-signature, 189 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE/Es6u+P1OI1bG+0sRAvMpAJ0X9k58xX3W0ndyw2XqGnNLTtK/OQCeL9v3 U0qwQl2b2SXSvlLnIz9BALk= =K0Cb -----END PGP SIGNATURE-----