Binary files are compiled programs. Libraries are external resources that one or more programs can call upon to aid them in a task.
Generally speaking, you don't need to "port" software from one distro to another. If the necessary libraries are present, the binary should work without modification. If the libraries are different or unavailable, you recompile. If you don't have source code for the binary, you use a container.
This depends somewhat on the operating system and what conventions are used there. In Linux and most Unix systems, data files are usually placed in a separate location from the binary. In Windows, data files are often placed along with the binary. If the program includes shared libraries that may be used by other programs, though, those should be placed in a separate folder.
No. It could emit characters that corrupt your terminal.
The cp command does that.
No, Linux has .so (Shared object) and .ko (Driver) files. Shared objects work in much the same way as dynamically linked libraries, except in a much better way that doesn't screw things up. There is no real Linux "DLL hell" equivalent.
These are different file types used under Linux 1. .tar and archieve files and need to be untared before use 2. .bin could be binary files in(elf format) 3. source file could be normal ASCII files.
It would depend what the binary files are and what you wanted to do with them.
EXE files are intended for use with the Microsoft Windows Operating System. However Wine allows Linux users to utilize many such applications as well. Depending on your Linux environment, there may be a binary package available, or you may build from the source code provided at http://www.winehq.org
different files
Binary file that has malicious code in it can create viruses. It depends on the programming on how it will be executed. Security of Operating System is considered on how handling such files.
do your own research
linux files dont need extensions