-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2008-06-16 at 15:26 -0700, John Andersen wrote:
Yes. You can build your own links in rc3.d and or rc5.d.
But I wouldn't recommend it.
No, you can't. The next time yast has a look at the services (when you install or remove an rpm with a service) all your symlinks will be removed. And, as a matter of fact, the symlinks are not decisive now, what matters is the contents of the .depend* files.
It was my understanding that the only symlinks managed by suse are those containing the ### BEGIN INIT INFO ### END INIT INFO Blocks.
And only those depend on .depend. files. All others (manually created ones) will be left alone and continue to work.
Are you saying thats wrong?
My understanding is that any symlink that is not "properly" managed will be deleted, or at least, it can be deleted. Maybe they are not deleted but overwritten with the new one according to its data. Maybe under some circumstances they may remain. I don't know. What I know is that there is no warranty that they are left alone, not even that they work. I understand that they are not executed if the start/stop sequence runs in parallel mode, but perhaps it is "make" mode. The OP poster found that out, that was his first problem: his scripts did not execute even though he had the correct symlinks. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIVvaTtTMYHG2NR9URAiwiAJ9PwJ9rA+1ZbQoLobDub0Ny+9iYMwCaAlv7 +djkMewSi93UZ3HtKNMTzng= =M1ad -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org