After using BusyBox for a long time in several custom Linux projects (BusyBox/Linux), one question kept coming back to me: How can a single executable transform into many others, simply by changing its name?
Let me explain: If you rename the busybox binary to ls, it behaves like the ls command. Rename it to cat? It does cat. Same for echo, mkdir, etc. In /bin, all these tools are actually just symbolic links pointing to a single binary:
| /* @author Umar Ba <jUmarB@protonmail.com> | |
| * @Description : | |
| * This code summarizes the essential use of the posix thread: | |
| * -> Race Condition | |
| * -> Data hosted by the thread itself | |
| * -> Cleanup handler | |
| * -> Thread attribute | |
| * | |
| * Happy Hacking /Reading ... | |
| * please let me know if you want to see another concept. |
/** By Umar <Jukoo> */
#include <node_api.h>
/**
* NOTE: GNU/Linux Compatible only
*/
#ifndef __linux__
#error "Reserved Only for GNU/Linux OS x86 (glibc)"
Summarized from https://stgraber.org/2016/03/19/lxd-2-0-your-first-lxd-container-312/.
Interestingly, the LXD command line client is named.... lxc!
lxc image list ubuntu: # ubuntu: is officially supported image source
lxc image list images: # images: is an unsupported source
lxc image alias list images: # lists user-friendly names
| #include <stdio.h> | |
| #include <stdlib.h> | |
| #include <string.h> | |
| #include <dlfcn.h> | |
| int main(int argc, char** argv) | |
| { | |
| void *handle; | |
| void (*func_print_name)(const char*); |