[viseztrance]

> The /bin/true (or /usr/bin/true) command is now nearly obsolete, because most extant shells now have a builtin "true" command. But it's still useful occasionally, for various silly reasons [...]

This make it sound like this is useless, but I disagree. For example, recently I had some games crash because they couldn't find pulseaudio, and making a symlink from pulseaudio to /bin/true fixed my issue (and yes, they had sound). So there are certainly legitimate uses for it.

[jzwinck]

Instead of a symlink to true you could have made an empty script.

[michaelt]

And violate AT&T's copyright? Perish the thought!

[viseztrance]

Well the symlink command was also easier to share with others having the same issue, whereas a one liner that creates an executable script which returns 0 is less ideal.

[cmeacham98]

An empty script returns 0 by default, thus `touch /path/to/missing/library` is a sufficient (and shorter!) one-liner fix to this problem.

[viseztrance]

I know, but you still have to make it executable, hence it's not as convenient.

And on top of this, an unlink is less error prone than a rm -f.