RFC: Alternate patch to have true new-style rc.d scripts inports (without touching localpkg)

[Garance A Drosihn]

At 2:32 PM +0200 7/31/04, Oliver Eikemeier wrote:
>Garance A Drosihn wrote:
>
>>>  > As stated above: everything users did before will
>>>  > continue to work.
>>>
>>>Except of course, disabling scripts by renaming them :)
>>
>>I seem to remember that the safe way to disable scripts was
>>to change the permissions on them so they were not executable.
>>This was considered better than renaming them, because the
>>file remained at the location it was installed at.  This
>>meant it would still be removed if the package was removed,
>>for instance.
>>
>>Is that no longer true?
>
>No, that is probably the best solution. But a)  [...]
>It will be not easy, and error-prone to hunt all those instances
>down. Of course it's doable, and would be somewhat `cleaner', but
>I believe it's better when we keep the previously documented
>behaviour as far as possible.

That is okay by me.  I was mainly wondering if it still true that a
person can disable a new-style script by changing the permissions
on it, after the script has been installed.  Just curious.

-- 
Garance Alistair Drosehn            =   gad at gilead.netel.rpi.edu
Senior Systems Programmer           or  gad at freebsd.org
Rensselaer Polytechnic Institute    or  drosih at rpi.edu