Re: install_initd clobbers system init symlinks

Then I would also have to also remove their symlinks
that contain the upper-case letters.  This might cause their
documentation to be invalid, and possibly jepardize the users
support contract.  It could even break their product if the number
on their original symlink was carefully chosen for some reason. 

Changing someone else's product is just philisophically bad. 

Currently there are zero LSB compliant applications.  Distros
should be more tolerant of non-LSB compliant add on packages
until that changes. 

On Monday 14 July 2003 09:39 am, Thorsten Kukuk wrote:
> 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

-- 
Bart Whiteley <[email protected]>
Novell, Inc., the leading provider of information solutions
http://www.novell.com/