Operating Systems > Linux and UNIX

Linux muscles into MS space?

<< < (3/3)

toadlife:
No problem.

I guess I should have pointed out the relevant stuff from that flaming linux rant page instead of just linking to it...


--- Quote ---# /bin/sh != sh; /bin/sh == bash. Lame. Nonstandard. Result: broken shell scripts and nonportable code.

# /usr/bin/make != make; /usr/bin/make == gmake. Lame. Nonstandard. Same result as above: nonportable code.

/usr/include/linux (come on. honestly.) Lame. Nonstandard. (for the clue-deprived, this means that any code written for linux using the linux/ headers will be incompatible with all other Unix flavors.) Guess what: string.h, types.h, malloc.h, signal.h, and so-on don't belong in a platform-specific include directory. Hope you didn't want to port your code...

--- End quote ---


There are also a few commands in linux that don't exist or are named differently in traditional UNIX, and vice versa. SOme commands, like the tar utility have different switches and/or different levels of functionality. If you get set in your ways, moving from one to the other could probably get annoying, but I really don't think it would be too big a deal. I doubt if you will notice much difference at all unless you get into very advance system administration or programming.

Navigation

[0] Message Index

[*] Previous page