4 ms·

". it is not a Linux, it is a Unix system;" I've (often) wondered - what does this mean for practical purposes?

by ghshephard 13y ago

alcari 13y ago
It means you get a POSIX interface without GNU- and Linux-specific extensions or the GPL.
- ghshephard 13y ago
  I understand the theoretical implications - but, reading from, http://en.wikipedia.org/wiki/POSIX http://en.wikipedia.org/wiki/POSIX, Windows 2000 was Posix-1 compliant, so Posix doesn't really have much in the may of practical implications. What are the practical implications of being "Unix" - i'm of the belief there really are none.
UNIXgod 13y ago
It's a tool which is used by engineers, computer scientists and researchers. Focusing on your question for the /practical/ meaning of 'it's not linux...' outside what I explained in a previous comment that it's Berkeley UNIX unencumbered, though we do have the "one true awk"; Another diff would be that it's not a pure clean room implementation like the GNU operating system. BSD is over 35 years old and served us all well. If you haven't had an opportunity to explore FreeBSD it's worthy to explore your options and toolsets if for any reason to be a well rounded hacker and also to understand the freedom and choices you have to make your own educated decision on the tools which you find practical for your own purposes.
- ghshephard 13y ago
  I'm very familiar with OpenBSD, the BSDs in general, and Linux. I'm really interested in the statement, "It's not a linux, it's Unix" - and I'm wondering if that statement really has any meaning. I completely agree with you that understanding the licensing, the freedoms you chose, the wonderful documentation and great integration you get from the BSDs are all important - but that's really a question of "What is the practical difference between choosing an OpenBSD versus a Linux System" - which is somewhat different than making the blanket statement, "It's not a Linux, it's Unix."
sarnowski 13y ago
For the end user this means: different command line parameters for commands; more consistent userland; consistent documentation; less drivers; slightly less applications

". it is not a Linux, it is a Unix system;" I've (often) wondered - what does this mean for practical purposes?

alcari 13y ago

It means you get a POSIX interface without GNU- and Linux-specific extensions or the GPL.

ghshephard 13y ago
I understand the theoretical implications - but, reading from, http://en.wikipedia.org/wiki/POSIX http://en.wikipedia.org/wiki/POSIX, Windows 2000 was Posix-1 compliant, so Posix doesn't really have much in the may of practical implications. What are the practical implications of being "Unix" - i'm of the belief there really are none.

UNIXgod 13y ago

It's a tool which is used by engineers, computer scientists and researchers. Focusing on your question for the /practical/ meaning of 'it's not linux...' outside what I explained in a previous comment that it's Berkeley UNIX unencumbered, though we do have the "one true awk"; Another diff would be that it's not a pure clean room implementation like the GNU operating system. BSD is over 35 years old and served us all well. If you haven't had an opportunity to explore FreeBSD it's worthy to explore your options and toolsets if for any reason to be a well rounded hacker and also to understand the freedom and choices you have to make your own educated decision on the tools which you find practical for your own purposes.

ghshephard 13y ago
I'm very familiar with OpenBSD, the BSDs in general, and Linux. I'm really interested in the statement, "It's not a linux, it's Unix" - and I'm wondering if that statement really has any meaning. I completely agree with you that understanding the licensing, the freedoms you chose, the wonderful documentation and great integration you get from the BSDs are all important - but that's really a question of "What is the practical difference between choosing an OpenBSD versus a Linux System" - which is somewhat different than making the blanket statement, "It's not a Linux, it's Unix."

sarnowski 13y ago

For the end user this means: different command line parameters for commands; more consistent userland; consistent documentation; less drivers; slightly less applications