| ▲ | Quarrelsome 10 hours ago | |||||||
this is satire, right? | ||||||||
| ▲ | usefulcat 10 hours ago | parent | next [-] | |||||||
It may be a bit uncommon, but it's not at all new. For example, on a Linux system I have, there are several files in /usr/bin that use hard links to refer to the same file (inode) by different names: bunzip2 / bzcat / bzip2 gunzip / uncompress unzip / zipinfo pigz / unpigz pkg-config / x86_64-pc-linux-gnu-pkg-config perlbug / perlthanks Use ls -li to show the inode number for each file or directory. For example: | ||||||||
| ||||||||
| ▲ | belkinpower 10 hours ago | parent | prev | next [-] | |||||||
This is already how busybox works. These examples are taking it to a more extreme level but it's not _that_ crazy. | ||||||||
| ||||||||
| ▲ | frizlab 5 hours ago | parent | prev | next [-] | |||||||
I have used that in a project of my own[0] for convenience (avoid duplicated code), but it is uncommon, yes. I truly think it should be avoided in general, especially when what you actually want (in OP’s article) is a config file. [0] https://github.com/Frizlab/frizlabs-conf/blob/44030f4123e683... (w/ that, also see the aliases in the folder of the script) | ||||||||
| ▲ | Cthulhu_ 8 hours ago | parent | prev [-] | |||||||
I'd say "kind of", because it's ridiculous on the surface but could be a handy trick. If only to be aware that an executable gets told its own name. | ||||||||