>>> grep -l THISISMINE /etc/rc.d/*
>> Besides being able to tell which are mine, I don't like new invented
>> system files overwriting my local extensions with the same name by
>> pure chance (or bad naming conventions).

> That sounds like a good idea at first glance, but imagine a situation
> where you want to stop/start/restart a subsystem.  Now you'll have to
> first remember if it's a system-delivered system, or a package, or a
> "local" one, [...]

> That's not a good thing.

Neither is having your localisms destroyed by a system "upgrade" that
happens to provide something with the same name as what you picked.

> Though it may seem less elegant at first, putting them all into
> /etc/rc.d is the best idea.

Which way is "best" depends on whether you consider the inconvenience
of having to remember the list of script directories and searching
through them worse than the inconvenience of having localisms destroyed
by an upgrade due to name clashes.

Personally, I consider the latter worse.  Thus, of these alternatives,
I favor separate directories for localisms and packages.  (Not that I
like either one, myself; I use, and will continue to use, monolithic
scripts.)

					der Mouse

			       mouse@rodents.montreal.qc.ca
		     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B