Open source oftware (OSS) is computer software with source code available with a license. The OSS copyright holder provides anyone the rights to read, modify, and distribute the software for any purpose.
Does anyone know the differences in commands when it come to Linux and Mac OS X? I'm wanting to know if I use "this" command in Linux and It doesn't work in Mac then what command is equivalent to the one in Linux. Example Ctrl+Alt+f2 switches to (tty2) so what equivalent switches to ttys2 on Mac?
I think you will not find a translator like what you're looking for.
This might help you understand why (expounding on wisecracker's post above): what's the difference between linux and unix commands? - Stack Overflow
Some judicious use of "man -k" or "apropos" can help you locate the functionality in commands you might want to utilize, should a command found in Linux not be available in another Unix OS.
Of course, if you have the time, you could create the translator you are looking for.
The Following User Says Thank You to [MA]Flying_Meat For This Useful Post:
I need some Help with this, I'm trying to install Recordmydesktop via tar. Im not sure whats going on but I'm having trouble executing the command make and make install. This is what i have gotten
ONEs-MacBook-Air:recordmydesktop-0.3.8.1 1negroup$ sudo make
make: *** No targets specified and no makefile found. Stop.
ONEs-MacBook-Air:recordmydesktop-0.3.8.1 1negroup$ sudo make install
make: Nothing to be done for `install'.
ONEs-MacBook-Air:recordmydesktop-0.3.8.1 1negroup$ sudo makefile
sudo: makefile: command not found
Here is everything else. Just to let you know I executed ./configure first
ONEs-MacBook-Air:recordmydesktop-0.3.8.1 1negroup$ sudo ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... ./install-sh -c -d
checking for gawk... no
checking for mawk... no
checking for nawk... no
checking for awk... awk
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking whether gcc and cc understand -c and -o together... yes
checking build system type... i386-apple-darwin13.3.0
checking host system type... i386-apple-darwin13.3.0
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking whether byte ordering is bigendian... no
checking for dirent.h that defines DIR... yes
checking for library containing opendir... none required
checking for ANSI C header files... (cached) yes
checking for X... no
checking alsa/asoundlib.h usability... no
checking alsa/asoundlib.h presence... no
checking for alsa/asoundlib.h... no
checking endian.h usability... no
checking endian.h presence... no
checking for endian.h... no
checking machine/endian.h usability... yes
checking machine/endian.h presence... yes
checking for machine/endian.h... yes
checking sys/soundcard.h usability... no
checking sys/soundcard.h presence... no
checking for sys/soundcard.h... no
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking for unistd.h... (cached) yes
checking vorbis/vorbisfile.h usability... no
checking vorbis/vorbisfile.h presence... no
checking for vorbis/vorbisfile.h... no
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking for u_int16_t... yes
checking for u_int32_t... yes
checking for u_int64_t... yes
checking for isnan in -lm... yes
checking for deflate in -lz... yes
checking for IceOpenConnection in -lICE... no
configure: error: Can't find libICE
Uh.. yes and no. The programs and utilities are BSD-ish...so somebody comfortable with a BSD variant will have no problem. However it is *not* BSD... if for no other reason than it uses a Mach based kernel.
So...is it BSD +... no. It's close to that though.
It feels like BSD mostly, but with some differences and has some GNU-isms here and there. And of course a lot of very unique Apple-only things (some of which do *not* work that well).