3 ms·
I'd note that Tru64 unix kept its rc.d in /sbin instead of /etc. I'd also note that the first time I had to debug a Tru64 networking problem it took me quite s
by mst 6y ago
I'd note that Tru64 unix kept its rc.d in /sbin instead of /etc.
I'd also note that the first time I had to debug a Tru64 networking problem it took me quite some time to find the bloody things.
I mean, once I did my first thought was "honestly if anything that makes more sense than /etc would".
But argh.
Then in the end it turned out the network configuration had been fine all along and one of the developers had stolen the switch port it was using for something else.
(being a sysadmin at a software house tends to involve the developers getting to do wtf they want since their work is revenue critical and yours isn't perceived to be so much, though I still mostly enjoyed the job because my director was understanding and let me yell at developers for doing stupid shit so long as he didn't get too many complaints ;)
- segfaultbuserr 6y agoI'm never a fan of mixing runscripts that come with the package and runscripts written by the user. If rc.d is a libexec, it enables the perfect solution - /usr/local. It even allows one to potentially override a runscript in the most natural way, too bad it never gained the traction.
- mst 6y agoYou can actually have a /usr/local/sbin directory too, you know.