Slashdot Mirror


Can GNU Ever Be Unix?

An anonymous reader writes "The question isn't whether Linux can be certified as Unix. At least some distributions no doubt can. But who would pay for it? And is it worth the trouble? Jem Matzan asks these questions on NewsForge, and reminds us that the Open Group, not SCO, owns the Unix trademark,"

217 comments

  1. The *real* question is ... by ggvaidya · · Score: 5, Insightful

    can Unix ever be *nix?

    Seriously, for all practical purposes, GNU + Linux is setting the trend now. Ask IBM, Novell, SCO ...

    1. Re:The *real* question is ... by mirror_dude · · Score: 0, Redundant

      No , No , No
      The real question is; why?

      --
      Note to Mods: When I post mirrors, it's a best guess. I don't know for certain whether or not the site will go down!
    2. Re:The *real* question is ... by smartfart · · Score: 3, Insightful
      Right... IBM has seen the writing on the wall, putting Linux on every piece of hardware they produce. Sun also sells Linux boxen. While not traditionally a UNIX vendor, Novell has all but dumped their old operating system, switching to Linux instead.

      I don't think UNIX matters much anymore.

    3. Re:The *real* question is ... by mystran · · Score: 3, Insightful

      No, the real question is "SHOULD" GNU ever be a Unix. The whole POINT of GNU is that it's not Unix, it's (or aims to be) something better!

      --
      Software should be free as in speech, but if we also get some free beer, all the better.
    4. Re:The *real* question is ... by strictnein · · Score: 0, Flamebait

      sorry fool.

      you were the second post :P

      Have a nice day

    5. Re:The *real* question is ... by Jahf · · Score: 1

      Nitpick:

      Novell not traditionally a Unix vendor?

      They definitely were in the past ... and they definitely still have plenty of Unix expertise. So -traditionally- (ie, pre '95) they were a Unix vendor. Recently no, but traditions include the past.

      --
      It is more productive to voice thoughtful opinions (reply) than to judge (moderate) others.
    6. Re:The *real* question is ... by Nailer · · Score: 1

      Indeed.

      It'd be more necessary for a Unix company to try and get LSB certification than for a Linux company to get Unix certification.

      AIX, Solaris, Longhorn etc all claim the ability to run Linux binaries as a feature. The last time Linux did that, it was using IBCS - which nobody's cared about for a long time.

    7. Re:The *real* question is ... by Anonymous Coward · · Score: 0

      Regarding your sig*, which was at the time of this post:
      Note to Mods: When I post mirrors, it's a best guess. I don't know for certain whether or not the site will go down!

      If you don't want to get modded down all the time, then don't post mirrors to only the big sites and then say stupid shit like "in case it goes down" for a yahooo story.

      Also, you can admit that you only mirror the stuff from big sites because you are using akamai's bandwidth to do "your mirroring"

      So please STFU or come clean about the whole fucking thing. The whole truth, you know, the I use other people's bandwidth to mirror stuff that doesn't need mirroring (and have never mirrorred the little guys sites that do need help) to get mod points for modding up troll posts.

      * Some people don't realize that if you change your sig it changes it on all your posts, old and new.

    8. Re:The *real* question is ... by Tony-A · · Score: 2, Insightful

      The whole POINT of GNU is that it's not Unix

      Not exactly.
      I'd say the point is to be Unix without being called Unix. By being better it cuts the ground out from under the ownership of the name.

      Vastly oversimplifying, and a lot of this is by association with the hardware it run on.
      Unix 1. AT&T Unix. Very expensive and underpowered hardware by today's standards.
      Unix 2. Berkeley Unix. Amazing what you can do with cheap grad student labor.
      Unix 3. Linux. Triumph of anarchy. Product of the internet.

      The name Unix is applicable to Unix 1 and some variants of Unix 2. GNU utilities make Unix useable. GNU/Linux further undermines the name. Linux on IBM mainframes and supercomputers (and everything else) is a new (GNU if you like puns) generation. Even if it's mostly due to the hardware, you gotta stick a lablel on it.

    9. Re:The *real* question is ... by wizzardme2000 · · Score: 0

      I'm going to have to disagree. GNU stands for "GNUs Not Unix", so I'm pretty sure that being seperate from Unix is pretty important to these (gender non-specific) guys. Sure a Unix stamp could be beneficial in many ways, but it just doesn't make sense for Linux. Unix-like is about as close as it should be.

      --

      Toast lands jelly down. If you jelly both sides of a piece of toast, it will hover in a state of quantum indecision.
    10. Re:The *real* question is ... by mirror_dude · · Score: 0

      Your actually confusing me with another mirror provider asshole.

      --
      Note to Mods: When I post mirrors, it's a best guess. I don't know for certain whether or not the site will go down!
  2. Why? by lphuberdeau · · Score: 5, Insightful

    Is there really a good reason why would GNU be considered as UNIX officially? GNU has it's own credibility. What is UNIX anyway? Does anyone have a concrete definition of what UNIX is right now (no historical reasons, not the fact that the filesystem starts with /).

    --
    Qui ne va pas à la chasse n'a pas de gibier
    PHP Queb
    1. Re:Why? by Anonymous Coward · · Score: 5, Informative

      Is there really a good reason why would GNU be considered as UNIX officially? GNU has it's own credibility. What is UNIX anyway? Does anyone have a concrete definition of what UNIX is right now (no historical reasons, not the fact that the filesystem starts with /).

      The UNIX specifications (93, 95, 98 and 03) specifically define what can be called a UNIX. Before then (each number is a year btw), I believe all you can do is combine all the generally accepted unix based systems (UNIX, BSD, AmigaOS, Xenix, etc) and accept that there was a time when there was no really accepted 'standard' and everyone just did thngs a similar way

    2. Re:Why? by k4_pacific · · Score: 5, Insightful
      The Unix trademark is allowed on anything that confroms to several standards laid out by the Open Group who owns the Unix trademark. Linux on X86 won't comply becuase some of the errno codes are incorrect, being based on Minix, which also uses incorrect values. GNU/Linux for other platforms could qualify as they are, but again, GNU/Linux seems to be evolving as its own standard which seems to be more widely supported because of the freeness and wide availability of Linux.

      --
      Unknown host pong.
    3. Re:Why? by alangmead · · Score: 4, Informative

      Before the Open Group had the trademark and developed the certification process, AT&T held the trademark and might allow AT&T source licensees to use it. In the later years, they had a certification process that became the initial Open Group certification. When AT&T owned it, anything marked as Unix had some amount of AT&T code as its base. BSD hadn't still contained AT&T code, the Net2 release was in 1994, so all commercial BSD based systems (older SunOS, NeXT, older SGI, etc.) were derivatives of a common code base . Xenix was a based on an early Bell Labs release. (I don't know where the reference to AmigaOS came from.)

      The AT&T conformance was mostly to prove that when vendors made local modifications, they didn't mess anything up.

    4. Re:Why? by Anonymous Coward · · Score: 1, Informative

      (I don't know where the reference to AmigaOS came from.)

      Amigas were a mid 1980s UNIX based machine with dedicated coprocessors to do just about ANYTHING without the CPU needing to handle it all. They lasted about until 1995.

    5. Re:Why? by andreyw · · Score: 3, Informative

      AmigaOS was not UNIX. It wasn't even UNIX-based. It was however an innovative design nontheless, with a message-passing microkernel.

    6. Re:Why? by Anonymous Coward · · Score: 0

      errno codes wrong? And I thought part of the basis of the SCO case was that Linux had ripped off the errno headers (and presumably codes).

      Perhaps Linux should be put forward for certification as Unix. Failure would dent SCO's case. But then that may well implode very soon anyway.

    7. Re:Why? by andreyw · · Score: 1

      Although AmigaOS is not UNIX-based, Amiga did release UNIX (also called A/UX, not to be confused with Apple's) which ran on machines like A3000U (and I think the A4000U). It came on a tape catridge.

    8. Re:Why? by Anonymous Coward · · Score: 0

      GNU will not be UNIX because...

      GNU = "GNU's Not UNIX"
      Linux = "Linux Is Not UNIX"

      I don't think that either needs to be considered UNIX because UNIX/BSD is dead.

    9. Re:Why? by Anonymous Coward · · Score: 1, Interesting

      Unix based?

      This must be an Amiga from a parallel universe you're talking about.

      I still remember the joy of the developers when the GCC compiler was ported to it, but it was not until 1990 if I remember correctly.

      You were not talking about the 2500UX, were you? That's another thing completely.

    10. Re:Why? by Anonymous Coward · · Score: 0

      One reason the UNIX specification appeared was to prevent vendors like Commodore pretending their OS was "UNIX" when it wasn't.

    11. Re:Why? by The+FooMiester · · Score: 1

      Wouldn't linux then have to do things like have manpages that are accurate and up to date? Linux isn't about manpages and maturity, it's about running a webserver from the kernel and "cool things".

      --
      The previous has been a secret message to my comrades.
    12. Re:Why? by Brandybuck · · Score: 2, Interesting

      Best reason: The Unix monicker would stop all the GNU fanatics from frothing at the mouth every time they heard the word "Unix".

      Case in point. I'm at a conference. Someone asks me what I use. I reply "Unix". Suddenly their eyes bug out, their ears turn red, and they scream, "no you're not, GNU/Linux is not Unix!!!" Then I explain that I'm not running Linux and they're heads finally explode.

      Okay, that's a bit of hyperbole, but in my experience most GNU advocates (a distinct breed from Linux advocates) take great pains to enforce the Open Group's trademark.

      --
      Don't blame me, I didn't vote for either of them!
    13. Re:Why? by kristaps.kaupe · · Score: 1

      Linux on X86 won't comply becuase some of the errno codes are incorrect, being based on Minix, which also uses incorrect values.

      The Open Group Single UNIX Specification Version 3 only specifies names of errno codes in errno.h not the exact values.

    14. Re:Why? by alangmead · · Score: 1

      I'm sorry. I wasn't very clear. I know what Amigas and the AmigaOS were. It was the idea of calling it "Unix-like" that caused the confusion.

      Take a look at an API listing of things like dos.library and exec.library, and take a look at /usr/share/man/man2 and try to find something resembling a kernel level similarity. Take a look at AmigaDOS and compare it to the Bourne shell and /usr/share/man/man1. A fair amount of /usr/share/man/man3 got standardized as ANSI C, so it starts to get similar around there.

      The description of AmigaOS as "unix" or "unix-like" implies a lack of understanding of what the Amiga was, or what Unix is. For example, The Unix process model inherently revolves around a parent child relationship between processes and fork() to create new processes. Without a fork(), don't even begin to talk to me about something being "unix-like". The Amiga process creation is much more like pthread_create() of a routine retreived from a dynamically loaded library.

    15. Re:Why? by peawee03 · · Score: 1

      The only reason why I can see is for the corporate boardroom types... think a PHB elevated to the status of a God. They may understand the point that UNIX is what runs their mainframes, and it isn't just a sexless person, but some computer software. However, many people I talk to seem to not be able to grasp that the same OS I'm trying to hack onto my iPaq is the same one that runs on the shiny new IBM mainframes, and SGI supercomputers. In other words, they've wrapped "UNIX = big computer stuff, everything else = little computer stuff" around their minds finally, and being able to say "GNU/Linux = Unix" would prolly give it a boost.

      To run with the PHB-as-God view, lots of business that don't really "do" computers (like, say, a farming megacorp) would most likely have the upper execs as people who understand the companies focus and business in general first and formost, and would just love having certifications up the butt for everything else, just so that if something goes down the tubes, they can point to the certifications and say "you certified it to work as perscribed, so fix it." IT-related things like Yahoo prolly would never need the certifications because their entire corporate focus is essentially computing. However, some midwest dairy corporate types would prolly sleep easier knowing their big computer investment is "certified", whatever that entails.

      --
      I wish I could write clever and witty sigs.
  3. Re:It's GNU/Linux! by Anonymous Coward · · Score: 0, Offtopic

    Hey RMS, I thought you didn't read slashdot

  4. Would have to then be GIU/Linux by Anonymous Coward · · Score: 5, Funny

    GNU = GNU's Not UNIX...

    Have to change that to say GIU Is UNIX :p

    1. Re:Would have to then be GIU/Linux by Anonymous Coward · · Score: 1, Funny

      GNU = GNU is Now Unix

    2. Re:Would have to then be GIU/Linux by geggibus · · Score: 1

      GNU is Now Unix...

      -K

    3. Re:Would have to then be GIU/Linux by aled · · Score: 5, Funny

      No, no! RMS will tell you it is GNU/Unix.
      Wait... GNU/Unix=GNU is Not Unix/Unix=(GNU is not Unix) is not Unix/Unix... Stack Overflow/Divide Error... my... head... hurts...

      --

      "I think this line is mostly filler"
    4. Re:Would have to then be GIU/Linux by Anonymous Coward · · Score: 5, Funny

      It is very simple:
      GNU/Unix = Gnu is Now Unix / Unix (using the new expansion of GNU)
      Unix/Unix = 1
      => GNU/Unix -> Gnu is Now.
      Takeover of the world accomplished!

    5. Re:Would have to then be GIU/Linux by Anonymous Coward · · Score: 0

      That would mean that GUI is Unix, which means that:

      *drum roll*

      Unix is Unix!

      That should be enough fuel for the Microsoft camp wanting to prove the open source community is on crack.

    6. Re:Would have to then be GIU/Linux by xSquaredAdmin · · Score: 5, Funny

      Or...

      GNU/Unix
      = (GNU is not Unix)/Unix
      = GNU is not

      Thus, we can see that if GNU became Unix, GNU would not be. :p

      --
      Crushing dreams at the speed of sarcasm
    7. Re:Would have to then be GIU/Linux by Anonymous Coward · · Score: 0

      no no no. It's concatenation, commonly represented as the + operator.

      "GNU" = "GNU is not Unix" = "GNU " + "is " + "not " + "Unix"
      "GNU"/"Unix" = ("GNU " + "is " + "not " + "Unix") / "Unix"

      I take this a limit where "Unix" is approaching zero (how true), making the "GNU is not " part infinite.
      To make this an even worse, one could simply say, "GNU is not infinite." Then that whole recursive thing kicks in, you know how that goes.

    8. Re:Would have to then be GIU/Linux by Pharmboy · · Score: 1

      I guess as soon as the HURD is production ready, we can just call it GNUNIX. Then again, considering the pace of the HURD project, I don't think we will need to worry about this for a few decades.

      --
      Tequila: It's not just for breakfast anymore!
    9. Re:Would have to then be GIU/Linux by Froze · · Score: 1
      Your algebra is wrong
      GNU/Unix = (GNU is Not Unix)/Unix
      = (GNU is Not)/Unix 1
      = (GNU is Not Unix is Not)/Unix 1
      = (GNU 2(is Not))/Unix 2*(1)
      = (GNU Inf*(is Not))/Unix Inf*(1)
      but (is Not) = 0; boolean false
      = (GNU)/Unix Infinity
      Which diverges, thus GNU/Unix is not Real.
      --
      -- The morphemes of your disquisition are ascertainable, but they have eschewed an ambit of transpicuous exposition.
    10. Re:Would have to then be GIU/Linux by Anonymous Coward · · Score: 0

      I for one welcome our new Gnu is Now Unix overloard.

    11. Re:Would have to then be GIU/Linux by Anonymous Coward · · Score: 0

      are you sure it wouldn't be:

      GNU/Unix == Unix/Unix

      effectively changing the name of the system to "1?"

    12. Re:Would have to then be GIU/Linux by thelenm · · Score: 1

      And suddenly, RMS disappears in a puff of logic.

      --
      Use Ctrl-C instead of ESC in Vim!
  5. Can GNU ever be UNIX? by appler · · Score: 0, Redundant

    Correct me if I'm wrong, but I thought I read somewhere that GNU's Not Unix!

    1. Re:Can GNU ever be UNIX? by JeremyR · · Score: 5, Funny

      I suppose that if a certification were awarded, the acronym could be changed to "GNU's Now Unix." :-)

    2. Re:Can GNU ever be UNIX? by Anonymous Coward · · Score: 0

      No, no, gnus is a newsreader.....

    3. Re:Can GNU ever be UNIX? by Uncle+Jimmy · · Score: 1

      I'd prefer GNU Narf! Unix

      Sincerely,
      Pinky.

  6. Maybe we should just ask SCO by nicholaides · · Score: 4, Funny

    Can GNU ever be unix?

    I don't know. Maybe we should just ask SCO. They would probably have a reasonable opinion.

    --
    http://ablegray.com
    1. Re:Maybe we should just ask SCO by thephotoman · · Score: 1

      Provided you can find Earth Logic at SCO.

      But then, given GNU"GNU's Not Unix", it would take a break from Earth Logic to get too GNU=Unix.

      --
      Haec merda tauri est. Ceterum censeo Carthaginem esse delendam.
  7. Who cares? by Ianoo · · Score: 4, Insightful

    If it's "close enough", surely big business are going to do more research than just look at whether it's been certified by The Open Group just so the Linux community can use its trademark?

    The problem, as well, is what to certify. There are so many combinations of kernel, drivers, libc, userspace utilities and windowing systems that any certificate could well be rendered useless.

    For example, if IBM paid for SuSE to get certified, would that apply to RHEL or Debian, if they were using slightly different kernel versions or different kernel patches as is often the case?

    1. Re:Who cares? by Halfbaked+Plan · · Score: 1

      It would apply to a version-frozen release. Probably as long as rigorous version control was implemented on further evolution and development of the certified version, incremental certification, rather than a full re-cert, would be acceptable.

      No 'wander down the path' distros need apply.

      --
      resigned
    2. Re:Who cares? by Jonas+the+Bold · · Score: 1

      I'm more or less convinced that proprietary UNIX is dead as a major force in the market.

      You're forgetting Mac OS X.

      --
      Everything seemed to be going so nice
      'till the end of all beings punched right through the ice
    3. Re:Who cares? by archen · · Score: 2, Insightful

      I think it's less of an issue of who is more like who, as opposed to who makes the right decisions and moves forward. Unix is not the end all pinnacle of operating systems. Posix compliance is a good thing, but Linux needs to move where the community wants it to, not where the Unix standards neccesarily is.

    4. Re:Who cares? by MaoTse · · Score: 1

      PC-focused market does not care, that's sure.

      But it doesn't cover the ground completely. There's lot of stuff aimed specifically for systems Linux is currently not able to reach (and won't be for some time, IMHO). The main reasons are:

      • major differences in thread library implementation
      • incompatible VM system
      • some subtle differences in basic libraries - things like Solaris gethrtime for example
      Such things are commonly used by software on big-iron machines Sun and IBM sell and that's why Solaris and AIX are certified.

      The second major issue is the plethora of possible Linux configurations - distributions, versions, kernel, system security levels etc. It is usually seen as balkanization by big-iron folks.

      Ask Ulrich Drepper if Linux will get The Open Group certificate ;-)

    5. Re:Who cares? by Anonymous Coward · · Score: 3, Informative

      It applies when bidding for contracts, especially government. Government contracts usually require a checklist of features, and if one of them asks for UNIX-certified OS, then people can't make bids using Linux.

    6. Re:Who cares? by Anonymous Coward · · Score: 0

      Which like Linux isn't a UNIX. He was talking about certified proprietary UNIX.

    7. Re:Who cares? by Fished · · Score: 3, Informative
      You're forgetting Mac OS X.
      No I'm not. OS X is based on FreeBSD and is not Open Group certified last I heard. Moreover, one of the major features of OS X.2 IIRC was enhanced Linux compatibility.
      --
      "He who would learn astronomy, and other recondite arts, let him go elsewhere. " -- John Calvin, commenting on Genesis 1
    8. Re:Who cares? by latroM · · Score: 1

      We are rapidly approaching the point at which UNIX is a Linux-like operating system

      You mean GNU-like? Linux is only a kernel, you know.

    9. Re:Who cares? by Zeinfeld · · Score: 4, Interesting
      Who cares if Linux is Unix at this point? We are rapidly approaching the point at which UNIX is a Linux-like operating system rather than Linux being a UNIX-like operating system.

      I have been saying that for several years now. UNIX is all but dead. The only commercial UNIX likely to still be arround in ten years time as an ongoing product is OS/X. Solaris will have long since joined IRIX, Digital UNIX and VMS as O/S you can still buy and occasionaly see a minor upgrade for it.

      There is a basic set of core functions that O/S do and this has not changed in principle for over a decade. Log based file systems, threads that work etc are now standard, but none of this was new ten years ago.

      The interesting stuff all takes place either above or below the O/S layer. .NET, J2EE etc are where interesting stuff is happening.

      At the driver level I think that both Unix and Windows have the model hopelessly wrong. We have at last got past the point where we have to recompile the kernel for each new driver. But drivers are still mostly executable code while the differences between devices of the same genre are with very few exceptions the type of thing that can be described by code tables.

      I would like to see device manufaturers get out of the device driver writing business, have a genuinely generic driver in the O/S and discover the repetoire of a particular device by reading a configuration file - preferably one that can be read from the device. From a pragmatic point of view XML would probably be a good match for the task since you would inevitably need structured data and a way to extend the basic data structures.

      Unix once had this with the printcap and termcap files. Unfortunately people just seem to be unable to resist turing complete code.

      --
      Looking for an Information Security student project suggestion?
      Try http://dotcrimeManifesto.com/
    10. Re:Who cares? by Brandybuck · · Score: 1

      We are rapidly approaching the point at which UNIX is a Linux-like operating system rather than Linux being a UNIX-like operating system.

      Bullshit. Until those commercial UNIX systems abandon their kernel architectures for one modeled on Linux, it won't happen. There are no improvements in Solaris to make its kernel more closely match the architecture of Linux.

      --
      Don't blame me, I didn't vote for either of them!
    11. Re:Who cares? by erik_norgaard · · Score: 1

      The GPL effectively prevents inclusion of software in any product that is not distributed under the terms as stated in the GPL. While some ideas may be merged into other systems, code cannot.

      This is contrary to BSD code which can be adopted into any commercial product without suffering under
      the GPL terms.

      I believe it more likely that we will see a paralel development.

      Anyway, it is questionable if the term Linux-like makes any sense at all. While some has attempted to develop a reference there is yet no consensus (AFAIK) about such a standard to compare against.

      It's linux if it uses the linux kernel, or it's not. There is no in between.

      Well, anyway, who cares whatever Linux is, BSD rules! ;-)

    12. Re:Who cares? by Dwonis · · Score: 1

      I thought OS X was based on NeXT.

    13. Re:Who cares? by Anonymous Coward · · Score: 0

      I have been saying that for several years now. UNIX is all but dead.

      Netcraft confirms it...

    14. Re:Who cares? by Pharmboy · · Score: 0

      According to Apple, it is based on FreeBSD. I assume that NeXT borrowed code from the various BSD projects as well. NeXT was proof you could do a consumer OS from BSD, but not the original source of the kernel. The GUI, perhaps.

      Go do a google for "freebsd site:apple.com" and you will see 2690 hits. OS/X kernel is absolutely derived from FreeBSD, and benefits from improvements to FreeBSD. I think this is one reason the kernel (Darwin) is open source.

      --
      Tequila: It's not just for breakfast anymore!
    15. Re:Who cares? by alangmead · · Score: 1

      I did a bit of research on this a few weeks ago. Most of the BSD kernel in OS X is still predominantly based on the kernel they bought from NeXT. There is a similarity because of the common ancestry in BSD 4.3 and 4.4, but since then they have both diverged significantly. There are a few localized chunks of the kernel that have FreeBSD copyrights ( the crypto directory in particular)

      The system library and user commands portions of Unix (manual sections 1 and 3) contain a lot more similarity between Darwin (the OS X version of Unix) and FreeBSD.

    16. Re:Who cares? by wiredbuddy · · Score: 1
      I would like to see device manufaturers get out of the device driver writing business, have a genuinely generic driver in the O/S and discover the repetoire of a particular device by reading a configuration file - preferably one that can be read from the device. From a pragmatic point of view XML would probably be a good match for the task since you would inevitably need structured data and a way to extend the basic data structures."

      In the industrial controls market, Allen-Bradley/Rockwell Automation has been doing something similiar to define the characteristics of their hardware. Each device has an EDS file (electronic data sheet) that "describes a product's device type, product revision and configurable parameters".

      www.ab.com/networks/eds/

    17. Re:Who cares? by jbolden · · Score: 1

      I personally think a fair way to thi9nk of it is OSX is based on NextStep while Darwin is based on BSD.

      Historically it was:

      BSD -> NeXTStep -> Openstep -> Rhapsody -> OSX.

      However OSX has been pulling new stuff from the BSD tree lately (but exclusively at the Darwin level), and thus its reasonable to consider Darwin to be part of the BSD family; while OSX is in some sense to different than the others to really be a sibling more like a distant cousin.

    18. Re:Who cares? by pthisis · · Score: 1

      This is different from the GNU/Linux argument, which is about complete distributions.

      Saying the OS is Linux-like is completely reasonable given that most CS people consider OS to mean roughly "The minimal system that interfaces to the hardware". The only major OS component of a standard Linux distribution that isn't part of Linux is graphics drives provided by the X server; arguably, init and the shell could be included, but the amount of GNU code is certainly FAR smaller than the amount of Linux or X11 code in the OS itself, and certainly a lot of people use tcsh, zsh, or another shell.

      There's a case for calling the complete distribution GNU/Linux, but not much of one at the OS level.

      And there isn't much of a case for saying that UNIX is a Linux-like system as a whole (yet).

      See, e.g., the Free Online Dictionary of Computing:
      (OS) The low-level software which handles the interface to peripheral hardware, schedules tasks, allocates storage, and presents a default interface to the user when no application program is running.

      Or the Jargon File:
      operating system: n. [techspeak] (Often abbreviated 'OS') The foundation software of a machine; that which schedules tasks, allocates storage, and presents a default interface to the user between applications.

      --
      rage, rage against the dying of the light
    19. Re:Who cares? by a1englishman · · Score: 1
      If it's "close enough", surely big business are going to do more research than just look at whether it's been certified by The Open Group just so the Linux community can use its trademark?

      If company X has an application running on a certified Unix, and they want to replace it with cheaper hardware/software, they are going to want another certified Unix. Otherwise, they are going to waste a lot of time and money getting their application to run on the new platform. It is bennificial to them to get another certified Unix platform. If Linux and BSD could get Unix certification, it would help their adoption in these scenarios. However, as the article states, the Unix license agreement binds the signer to ensuring that all updates to the OS continue to remain compliant with the Unix certification.

      The author of the article seems to be of the opinion that the differences aren't very big; however, stated differences include threads and error codes. Thread APIs don't sound fun or easy, and while it may be easy to change error codes in the OS, this could screw lots of applications. Many would have to be recompiled, and a lot would have values hard coded, instead of #DEFINEd.

  8. GNU's Not Unix by FooBarWidget · · Score: 0, Redundant

    GNU's Not Unix. Do I need to say more?

    1. Re:GNU's Not Unix by Anonymous Coward · · Score: 0

      GNU's Not Unix?! Dang, Who knew!.. umm.. so what does the G stand for?
      </recursive sarcasm>

    2. Re:GNU's Not Unix by Anonymous Coward · · Score: 0

      Partially serving as an emphatic statement stating what it definately isn't to avoid potential "issues"?

  9. Who cares? by Fished · · Score: 5, Interesting
    Who cares if Linux is Unix at this point? We are rapidly approaching the point at which UNIX is a Linux-like operating system rather than Linux being a UNIX-like operating system. I'm more or less convinced that proprietary UNIX is dead as a major force in the market. Moving forward, Linux will be setting the agenda and proprietary UNIX will be playing catch up.

    This is particularly evident when you notice that the major improvements in some recent version of Solaris (8 & 9, but not 10 apparently) is to add more open source software and stability improvements.

    --
    "He who would learn astronomy, and other recondite arts, let him go elsewhere. " -- John Calvin, commenting on Genesis 1
  10. Re:It's GNU/Linux! by Jon+Proesel · · Score: 2, Funny

    No, no, no. It's only GNU/Linux when those thieving Linux bastards don't give credit to the GNU folks, by calling the OS just 'Linux'.

    RMS has no problem with you just calling it GNU.

    --

    --
    Using GNU/Linux - Windows-free zone!
  11. Boy -- talk about your pointless questions... by YankeeInExile · · Score: 5, Interesting

    I think it is almost certain that some distro of Linux could easily pass OG's test suite. It is also almost a certainty that FSF/GNU would never opt for it on religious grounds.

    The rest of the thread is now available for stupid /. jokes.

    In Soviet Russia, The Open Group petitions GNU for certification.

    --
    How does the Slashdot Effect happen given that no slashdotters ever RTFA?
    1. Re:Boy -- talk about your pointless questions... by ggvaidya · · Score: 0, Offtopic

      In Soviet Russia, the Open Group certifies YOU! =D

    2. Re:Boy -- talk about your pointless questions... by imkonen · · Score: 3, Interesting
      Is there are particular reason that FSF/GNU would object to certification? I haven't read the 55 pages of requirements, but I didn't get the impression that either "closed source", "not free to modify" or anything else incompatible with the GPL are part of the requirements. If you take a certified version and modify it, you undoubtedly can't call it certified anymore, but you're still free to redistribute your modified, "no-longer certified as Unix" version.

      But I think the more significant point is that it's not FSF/GNU who would have the most incentive to get a distro certified as Unix. As the article pointed out, it's probably the hardware companies like IBM and Sun who would find it worthwhile.

    3. Re:Boy -- talk about your pointless questions... by Halfbaked+Plan · · Score: 2, Interesting

      it's probably the hardware companies like IBM and Sun who would find it worthwhile.

      IBM have specifically taken a hands-off approach to Linux. They have team members contributing to the 'greater' Linux source trees, but there's no sanctioned 'IBM' brand of Linux. They don't want nor need an 'official' IBM version of Linux.

      The reasons for this are complex.

      --
      resigned
    4. Re:Boy -- talk about your pointless questions... by fpga_guy · · Score: 1
      I think it is almost certain that some distro of Linux could easily pass OG's test suite. It is also almost a certainty that FSF/GNU would never opt for it on religious grounds.

      One question I had after reading the article, say IBM pays for certification of some particular IBM-distro. Now, is it IBM who is certified, or is it the distro? If I simply redistribute the exact sources that IBM do (free to under the GPL), am I now a supplier of a certified Linux solution?

      When certification can cost up to half a mega-buck (see article), I think this is a question that a potential certificee (is there such a word?) might want answered.

  12. funny thing by latroM · · Score: 0, Redundant

    GNU's Not Unix Unix :)

    1. Re:funny thing by Anonymous Coward · · Score: 1, Funny

      Are you Unix? Are you not Unix? If you answered "yes" to both of these questions, then GNUU might be exactly what you're looking for!

  13. also... by fatgraham · · Score: 0, Offtopic

    Can my cat ever be a bicycle?

  14. No. And Yes. by T-Ranger · · Score: 4, Insightful
    "UNIX" means different things to different people. One definition would be something that contains ATT UNIX code. Another would be something that has a bunch of certifications. Linux has neither.

    But, the BSDs, and I believe even Solaris and AIX have a Linux compatability layer, or at the very least, "the GNU toolset", GCC, glibc, etc. Of course you wont beable to run IA32 binaries on a UltraSPARC, regardless of the compatability layer, but you could run IA32/Linux stuff on IA32/*BSD, or SparcLinux stuff on a Solaris box.

    I guess Im trying to say, given that lots of things can run Linux binaries, can cleanly compile Linux targeted sources, Linux + GCC + glibc may be a better standard to target then POSIX and whatnot. It is definitly more modern. Or to put things another way, UNIX is irrelevent, the question shoud be: can UNIXes ever be Linux?

    1. Re:No. And Yes. by Anonymous Coward · · Score: 0

      "UNIX" means different things to different people. One definition would be something that contains ATT UNIX code. Another would be something that has a bunch of certifications. Linux has neither.

      That's not quite right. As I learned from my local newspaper, Linux contains SCO code. And SCO owns all AT&T and IBM code ever written.

      Therefore, Linux does contain AT&T code, it's just that AT&T is owned by SCO.

      Isn't that right?

    2. Re:No. And Yes. by kscguru · · Score: 2, Insightful
      Better standard maybe... but Linux + GCC + glibc is an incredibly difficult thing to standardize upon! Standardization at the industry level takes months if not years ... have you seen any one of those three stay at the same version (exact same API and ABI, no patches, etc) for any fraction of that time? Linux (or GNU/Linux if you prefer) is too much of a moving target for anyone to hit.

      Go out and look at industry certifications - they certify against RHES version X, or whatever else the flavor of the month is. UNIX is a heavy-duty standard, and Linux is still evolving too fast to qualify.

      Actually, I have a more interesting thought: for Linux to qualify as a Unix, development would have to slow down - a lot. Arguably, it is doing so now ... Linus claims there are no really large projects on the horizon that require a 2.7 branch, there haven't been any huge changes to the kernel in quite a while (not since the new VM in late 2.4 / early 2.5, or the O(1) scheduler in 2.5). If Linux sits back at this level for a good long while, I suspect it really will become a UNIX within a year or so. Alas, such a slowdown will leave Linux a long ways behind modern Unices, which is a shame. So... should Linux slow down and become Unix-certified, or should it speed up and catch up to modern Unix?

      --

      A witty [sig] proves nothing. --Voltaire

    3. Re:No. And Yes. by alangmead · · Score: 1
      "UNIX" means different things to different people. One definition would be something that contains ATT UNIX code. Another would be something that has a bunch of certifications. Linux has neither.

      It didn't occur to me at the time that AT&T sold the Unix copyrights and the Unix Trademark, but that act was solidly admitting defeat to the Open Software Foundation (now the Open Group) in the Unix wars. The OSF created their OSF/1 operating system to try to promote Unix as an API standard and not the name of a family of systems derived from a single source. The fact that AT&T sold them the name can be viewed as an implicit admission that it was the API and not the source code that matters.

      The Unix trademark is now owned by an organization whose initial charter was to make the AT&T based SYSVr4 irrelevant. Many groups have surpassed them. (There are probably many more Linux systems around than Digital Unix, the most recent OS derived from OSF/1) but their goal was achieved.

    4. Re:No. And Yes. by djdavetrouble · · Score: 1

      and unix means one thing to the open group

      unix.org

      --
      music lover since 1969
    5. Re:No. And Yes. by Anonymous Coward · · Score: 0

      Exactly -- look at RHEL, which is 'frozen' for a 5 year support window. "Linux" may be evolving, but any given version of RHEL is stable and only getting bugfixes. There's more than enough time and opportunity to certify it.

    6. Re:No. And Yes. by Brandybuck · · Score: 1

      ...or at the very least, "the GNU toolset", GCC, glibc, etc.

      As far as I am aware, only Linux and Hurd distros use glibc. Certainly Solaris, AIX and *BSD do not. They have their own, and probably more standard ones at that.

      --
      Don't blame me, I didn't vote for either of them!
  15. No. Unless Linus or Posix makes a change. by Ungrounded+Lightning · · Score: 4, Informative

    Linux deviates from Posix in several ways, and at least one of them is deliberate - because Linus is convinced that his way is better. Posix can't change because that would break all the existing and past unixes. IMHO Linus is unlikely to change because he believes in the advantages of his way.

    (I don't recall what the particular difference was but as I recall Linus had a very good point. Security? Robustness? Anyhow it should be trivial to look it up - which I'd do if I had the time just now.)

    And I don't see that it really matters, since they can continue as two operating systems and virtually anything will operate well on both, and some things break even crossing between Posix-compatible systems. Linux is doing quite well as is and may end up dominating. The rumors of the demise of the BSDs seem overblown. And who knows what will come next.

    --
    Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
  16. Definition of UNIX: The Open Brand by tepples · · Score: 5, Informative

    UNIX® describes any operating system sold under a brand licensing agreement with the Open Group. This requires the product to pass a checklist that includes certification to the Single UNIX Specification (free reg. req.) on a given set of supported hardware, based in part on product testing, and payment of brand fees pursuant to the Trademark Licensing Agreement (PDF). Often these brand fees are high enough to shut out publishers of low-volume operating system products.

    1. Re:Definition of UNIX: The Open Brand by Lussarn · · Score: 0, Troll

      Often these brand fees [opengroup.org] are high enough to shut out publishers of low-volume operating system products.

      Yeah, like Apple who didn't bother to get OS X certified and just call it UNIX anyway... Smart move.

    2. Re:Definition of UNIX: The Open Brand by Halfbaked+Plan · · Score: 1

      He meant 'volume' as in quantity sold. Not 'low volume' as in 'pipsqueak loudness.'

      --
      resigned
  17. All your Linux Standard Base... by tepples · · Score: 5, Interesting

    GNU/Linux seems to be evolving as its own standard

    And this standard is called LSB.

    1. Re:All your Linux Standard Base... by Anonymous Coward · · Score: 0

      I though it was called United Linux.

    2. Re:All your Linux Standard Base... by Anonymous Coward · · Score: 0

      I have to disagree. The LSB is a make-believe standard that matters to almost no one. It's fundamentally wrong-headed on many issues, and despite the name it applies only on x86, which is just one of the many platforms GNU/Linux works well on. As the linked article points out, the LSB concerns itself with binary compatibility, which is where the fundamantal wrong-headedness begins, although it goes much deeper. The Unix specification is far superior in that regard, worrying only about source level compatibility, which is what is important anyway. Binary compatibility isn't just not important, it's actually quite harmful in some situations, and definately should not be encouraged.

  18. Re:SCO goes down the drain... by Lussarn · · Score: 1

    SCO doesn't own the UNIX name, the open group does.

  19. Linux doesnt need it. by nurb432 · · Score: 4, Insightful

    Its just for 'brand recognition' anyway, and Linux has that now.

    If you say 'Linux' to the general IT population, they already know what you are talking about. ( and they also realize the differences beteeen it and 'unix' ) so why muddy the waters?

    --
    ---- Booth was a patriot ----
  20. Re:SCO goes down the drain... by ggvaidya · · Score: 2, Informative
    ...the Open Group, not SCO, owns the Unix trademark,"

    Dude, read your f\w+ screen!

  21. When GNU = Unix? by .+visplek+. · · Score: 5, Funny

    When GNU is Unix, LAME must be an MP3 encoder and WINE must be an emulator.

    --
    - Save a tree, eat more woodpeckers
  22. Re:SCO goes down the drain... by crackshoe · · Score: 1

    not reading the full article is one thing, but only reading the headline? come on, man -- what do you think this is? slashdot?

    --
    Don't worry - its just stigmata. Pass me a napkin and don't you dare tell my mother.
  23. Why? by toupsie · · Score: 3, Interesting

    What's the point? To be facetious, Unix is old and busted, linux is the new hotness. Instead of being focused on the past, look to the future. Being stamped "Unix" doesn't have the same meaning today as it did ten years ago. Bean counters today aren't asking about a Unix solution but a Linux one. Its the tech buzz word of the last 5 years. To the general public Linux has better name recognition than Unix. In fact, I commonly hear non-tech people referring to real Unix systems as "Linux".

    --
    Strange women lying in ponds distributing swords is no basis for a system of government.
  24. Re:It's GNU/Linux! by ultranova · · Score: 3, Informative

    No, no, no. It's only GNU/Linux when those thieving Linux bastards don't give credit to the GNU folks, by calling the OS just 'Linux'.

    RMS has no problem with you just calling it GNU.

    No. GNU/Linux is not the same as GNU. The "official" kernel of the GNU system is Hurd. From the linked website:

    "The GNU Hurd is the GNU project's replacement for the Unix kernel. The Hurd is a collection of servers that run on the Mach microkernel to implement file systems, network protocols, file access control, and other features that are implemented by the Unix kernel or similar kernels (such as Linux)."

    This clearly indicates that Hurd is the kernel specifically designed to be the centerpiece of the GNU system. Linux is just an acceptable placeholder until the Hurd is ready for spotlight. Therefore GNU/Linux is just a precursor for the True GNU System.

    Seriously speaking, the Hurd does seem to have a number of very nice ideas - the translators (little programs that can be attached to directories and files, and which will then control all access to those files - so you can attach one to a directory and make the contents of an FTP site or whatever appear there - not unlike the proc filesystem on Linux), for example. I wonder if anything like them could be implemented in Linux ?

    It also has some very serious problems, such as a lack of device drivers and every existing filesystem server memorymapping the entire partition, which means that you can't use partitions larger than 2 GB on a 32-bit system...

    Oh well, it's good to know that the next generation free open source operating system is already being worked on - should keep Linux from getting fat and lazy ;).

    --

    Forget magic. Any technology distinguishable from divine power is insufficiently advanced.

  25. Nope. by Anonymous Coward · · Score: 3, Informative


    One of the reasons that GNU's Not Unix is because intentionally or not, a lot of the GNU tools differ from and are often outright incompatible with their counterparts from the original Unix and its descendents. There would be a lot rewriting and outright disposal of some of the primary features (or "incompatible extensions", as we would say if this were Microsoft) of the GNU utilities and libraries. These changes would also break compatibility in innumerable ways just among various pieces of GNU software. File formats would have to change. (gtar archives, Makefiles, etc)

    The GNU project was a good idea with a good mission, but specifically calling it "GNU's Not Unix" really backfired on them in this aspect because Unix as we know it today is now more popular than it's ever been among both geeks and the corporate world.

    1. Re:Nope. by rmdir+-r+* · · Score: 1
      Unix as we know it today is now more popular than it's ever been among both geeks and the corporate world.

      Really? It is? Last time I checked, the GNU toolset comes with (essentially) EVERY linux distro, not to mention the fact that the GNU tools are included with most proprietary UNIX's, to the detriment of the 'traditional' UNIX tools...
    2. Re:Nope. by latroM · · Score: 1

      And not just tools. The GNU part in GNU/Linux consists not only of tools but crucial system libraries such as the C library. GNU has its extensions also there. And of course the GCC has its own features. This is not much of a problem because GNU is Free and it runs under different platforms and kernels.

    3. Re:Nope. by Anonymous Coward · · Score: 0

      Becoming UNIX certfied does not mean you have to remove incompatible GNU tools. They only need to add optional versions that are compatible (the BSD tools probably would do)

    4. Re:Nope. by Shadowlore · · Score: 1

      The GNU project was a good idea with a good mission, but specifically calling it "GNU's Not Unix" really backfired on them in this aspect because Unix as we know it today is now more popular than it's ever been among both geeks and the corporate world.

      Which of course expains why LINUX is growing at the expense of UNIX. It also explains why UNIX companies are using LINUX in places they previously would have used their own proprietary version of UNIX in. It also explains why LINUX is in more homes than UNIX is (knowingly and unknowingly).

      --
      My Suburban burns less gasoline than your Prius.
  26. GNU Unix by Anonymous Coward · · Score: 0

    I have access to a Sun Box and several Linux boxes. I use the Linux box by default because the tools are better. I only use the Sun box sometimes because it has 12GB memrory and the Linux boxes have on 4GB. The GNU tools may at one time have been imitations of their Unix counterparts, but they are far superior these days. I frequently download the source to the GNU version and compile it so that I have it's functionality on Unix machines.

    It's not a question of Linux fusing with Unix. They are, for most purposes, the same thing.

  27. Open Group certified Linux by foobsr · · Score: 2, Interesting

    If you ask google , it does not seem a good idea. SCO comes up first.

    CC.

    --
    TaijiQuan (Huang, 5 loosenings)
  28. Re:It's GNU/Linux! by DAldredge · · Score: 1

    IOW, it's ok to ignore the BSD and other non GPL licensed code as long as you give GNU credit.

    That is just stupid.

  29. Re:SCO goes down the drain... by pjt33 · · Score: 1

    In addition to the point made by previous replies, the name UNIX is a trademark, not copyrighted. You can't copyright a name.

  30. Paying for unix? by Cow007 · · Score: 2, Interesting

    Free BSD as the name suggests IS free. Unix is not a valad trademark beacause beacause of its many forks and variations it has become a generic term. IMHO I think the people at SCO and Sony (with its joke of a digital music player) fell off the stupid tree and hit every branch on the way down. Protecting your copyrights has become difficult these days. In a world of convergance, reverse engineering and "hey that was my idea" tactics A review of copyright laws and procedures needs to take place. If we come together and decide on open and fair standards that make things work. Things are going to change, biusness models that were viable before will no longer work. But its time to evolve.

    --
    411 Y0UR 8453 4R3 8310NG 70 U5!! -NSA
  31. Please, god no by jb.hl.com · · Score: 1

    The GNU people would just have to think up a new name, and then we'd have to put THAT in front of Linux. Not to mention it would probably be another fucking self-referential acronym :)

    --
    By summer it was all gone...now shesmovedon. --
  32. Hrm by bkhl · · Score: 1

    I though the whole idea was that GNU doesn't try to be Un*x compatible, it's just heavily inspired by it.

    1. Re:Hrm by polyp2000 · · Score: 1

      An interesting point, it just so happens that the Un*x philosophy is such that compatibility happens as a matter of course; even if that wasnt the intention.

      --
      Electronic Music Made Using Linux http://soundcloud.com/polyp
  33. Re:Can Linux ever beat BSD? by colinrichardday · · Score: 0, Offtopic

    The woman in the dis.org jpegs isn't that cute.

  34. A better question by Crashmarik · · Score: 3, Insightful

    Is what should GNU be. Not to be pedantic but if you have done real work with more than one GNU/Linux distribution you have run into compatibility issues. Its a fact of life and an impediment to the progress of GNU's penetration.

    If standardization is a good thing (I think it is, but your opinion may vary) how should The GNU/Linux world go about it, and what parties should certify. Right now there are the DeFacto standards (Redhat/slackware/Suse/Mandrake) of the big distributions. The problem with these defacto standards is eventually the game collapses. There have been attempts to have multiparty standards (United linux comes to mind) but those for various reasons havent made a big push.

    You can allready see the problems in setting a GNU/linux standard when there are vicious arguments over naming it Linux or GNU/Linux. Just who is going to be able to make decisions on filepaths, naming conventions, and library depencies and then shove it down the throats of the contrarians.

    So before you ask can "GNU be Unix", you need to ask does GNU want to be standard, Who's standard, and does that standard want to be close enough to Unix to comply.

  35. It's not important. by IGnatius+T+Foobar · · Score: 4, Insightful
    No Linux distribution has bothered to achieve Unix branding because it's simply not important anymore. People who purchase Unix systems know what Linux is and they know it's the best and fastest growing Unix-like system out there. More importantly, they know that the applications they use have been tested on Linux, probably as a top-tier platform, often as the recommended platform (see Oracle). That being the case, why would a Unix certification from The Open Group make any difference?

    Meanwhile, commercial Unix vendors are going out of their way to achieve Linux compatibility, at either the source or binary level. Linux is quickly becoming the standard to which other Unices are compared. This means two things:
    • The Open Group and its branding are irrelevant
    • Richard Stallman is effectively wrong: GNU is Unix. Except in the real world we don't call it GNU, we call it Linux.
    --
    Tired of FB/Google censorship? Visit UNCENSORED!
    1. Re:It's not important. by cpghost · · Score: 1

      GNU: GNU (is) Now Unix

      --
      cpghost at Cordula's Web.
  36. What's the point? by billsf · · Score: 2, Insightful

    This is redundant, but not knowing what its going to cost beforehand is the downfall of Open Group. $45,000 is one thing, half a million is another matter.

    Linux has indeed been repackaged and registered. (To avoid flames from those that don't already know, I won't say which ones.) Linux as in say Gentoo and BSD in say FreeBSD are very successful now and it would be hard to justify the value in risking so much money for a seemingly worthless qualification.

    I'm sure Suse (Novel) and Redhat will actually seek registration as commercial products. If X/Open would agree to fixed priced terms, they would do far more business. (Are you seeing this Open Group?) All things considered, this is like the MSCE scam and might have a negative impact.

    The above mentioned BSD and Linux have treated me very well on a number of hardware platforms. Keep up the good work.

  37. what real world benefits are there.... by zogger · · Score: 1

    ... just to be called a "unix"? Is this necessary, or just for coolness factor, are businesses demanding it, what? I really don't know, it's a legit question.

    When I am running something,right now fedora core 2, I don't even think "fedora core 2 gnu/linux a unix type system" I just think and say "fedora". What do I again if I can say "I am running unix" instead of saying "fedora"?

    1. Re:what real world benefits are there.... by Brandybuck · · Score: 1

      That's "GNU/Fedora" to you...

      --
      Don't blame me, I didn't vote for either of them!
  38. Ohh cool! THIS is what we need! LSB-certification! by urbieta · · Score: 1

    Within the google search I fonud Developing LSB-certified applications http://www-106.ibm.com/developerworks/linux/librar y/l-lsb.html maybe this is the subject we should be discussing, how many applications ARE following LSB guidelines?

    Also, why is the Linux Standard base hosted by the open group? Isn't the Open Group doing it's part already? so the other way arround becomes less relevant. ;)

    http://www.opengroup.org/lsb/cert/cert_prodlist.tp l?CALLER=index.tpl

  39. I'd rather call mine Willy! by urbieta · · Score: 1

    I am running Willy!

    I payed nobody, and it's the same Linux Mandrake I downloaded fron da net ;)

    Check out my Willy girls!

  40. the real question by Anonymous Coward · · Score: 0

    The more relevant question is, Can GNU ever be linux? (GNU/Linux)

  41. GNU by tomthebomb · · Score: 0, Redundant

    Gnu's Not Unix.

    Your question has been answered, o Anonymous Reader.

  42. Unix source vs. Unix complience by alangmead · · Score: 1

    Re-reading the article, I noticed a small point I missed when I posted the previous message. AT&T didn't sell the trademark to the Open Group. They sold the whole thing, source, trademark, and compliance certification to Novell, who split up their purchase to SCO and the Open Group. It was Novell who as a corporation recognized the difference between Unix as a standard interface to Unix as a body of source code.

  43. BEST QUESTION:Can UNIX ever be certified as Linux? by Anonymous Coward · · Score: 0

    Linux will soon be the second most pervasive operating system after Windows. Whether Linux can be certified to be a variant of UNIX is a moot question. The better question is whether UNIX can be certified to be a variant of Linux.

    The top dogs set the standard, and the underdogs are all measured against the top dogs. In the days of mainframe glory, you had the IBM mainframe as the top dog. All the clones, made by Fujitsu and its ilk, were advertised as being CERTIFIED to be 100% compatible with the IBM mainframe.

    Long live, Linux! Sir Linus Torvalds shall slay the dragon in Redmond!

  44. Re:It's GNU/Linux! by kbahey · · Score: 4, Insightful

    Hurd is definitely a good idea, but so far it is only that: an idea.

    I have been hearing about Hurd at least since 1992 or so, ever since Linus started his project. This is 12 years now, and nothing concrete has come up yet, that can be adopted by the masses.

    Don't get me wrong, I like many of the ideas and design decisions they have. But my gripe is that their model does not allow hordes of programmers to join in and get things out faster, like the Linux model.

  45. Re:No. Unless Linus or Posix makes a change. by Anonymous Coward · · Score: 0

    "IMHO Linus is unlikely to change because he believes in the advantages of his way."

    Does Linus get to really call the shots these days?

  46. Re:It's GNU/Linux! by arose · · Score: 1
    Oh well, it's good to know that the next generation free open source operating system is already being worked on - should keep Linux from getting fat and lazy ;). -- ultranova
    (*) Not FAT, but you should be able to see that it's sitting down because it's really too stuffed to stand up. Think "bean bag" here. -- linus
    --
    Analogies don't equal equalities, they are merely somewhat analogous.
  47. Re:No. Unless Linus or Posix makes a change. by Anonymous Coward · · Score: 3, Interesting

    Sure he does. But he understands that he's working for the distro companies. If RedHat/Suse/IBM/etc thought it was a priority to get UNIX-Certified, Linus would merge their patches.

    Note that Linus did a 180 on "Linux Threads" versus "POSIX Threads" because Linux vendors wanted portability.

  48. What's in a name? by lyberth · · Score: 1

    What's in a Name? that which we call a Linux,
    By any other name would operate as sweet

    --

    There isn't much like the scent of a fresh harddisk
  49. UNIX 2003 by taj · · Score: 4, Insightful



    Is the branding alive or not?

    What Unix passes Unix 2003? OK. Who passed UNIX 98? Get the picture? Its going to cost ~$0.5M when all said and done. What advantage is there? Some of the 'UNIX' systems out there have not passed a checklist in over a decade.

    Linux does not need people who dont code deciding what is right and wrong in expensive ongoing beurocratic processes. Things are decided much faster in open forums which document the process in ample detail.

    Linux does deviate but given a coin toss, it goes with the previous 'standards.' If the legacy means does not make sense, its ignored and documented.

    The UNIX branding made sense with legacy closed source Unix systems. It provided a level of trust that customers could drop to without even (imagine!) seeing the underlying code.

    It was a bandaid on a broken model. The outdated Unix systems deviated but the customer could only read documentation, not code.

    So systems like Solaris, AIX, HP-UX ... have two options. Continue down the documentation/standards/branding route increasing customers costs $100's/install or just open up the developement process/source.

    If they decide to open up the process, they have to decide wether to join open source projects or try to replicate the efforts.

    'UNIX' is dead. Do we need a netcraft survey?

    I know people are going to say that wont work. "Look at all the forks in apache and perl and python. It will be anarchy."

    Thats proven to not be the case. The problem has always been closed source.

  50. Mod parent redundant! by Anonymous Coward · · Score: 0

    Do I need to say more?

  51. ...are belong to SCO. by tepples · · Score: 1

    I though it was called United Linux.

    I thought SCO was in on UnitedLinux.

  52. Re:Ohh cool! THIS is what we need! LSB-certificati by foobsr · · Score: 1

    You are right. This could make life easier for all and would be an improvement facilitating deployment of Linux on the desktop - but imagine the (micro.political) difficulties of LSB-certification along the spectrum of distributions </sarcasm /> .

    CC.

    --
    TaijiQuan (Huang, 5 loosenings)
  53. UNIX matters by mnmn · · Score: 4, Interesting

    well, it mattered to me.

    Back in the days, around 1995, my friends and I were looking for any UNIX to put on our machines to learn. We tried an old copy of SCO Unix which didnt work, and were busy snooping till we found Linux just as it was getting popular online. We got into Linux because we were out looking for UNIX.

    Nowadays I've got AIX and Solaris on ultrasparc to play with, so I can finally brag about knowing 'unix', but would be real nice if Linux is called UNIX. Even though SCO has spilled cold water on the brand name, it still carries enough weight, and maturity of two decades, to get attention. Linux is still new to the scene, and UNIX has carried the full weight of the Internet since its birth... that means something.

    Linux means alot more now, so can UNIX be Linux, or at least its former self? Thats possible, if Linux is branded UNIX, and UNIX can once again claim to be a popular flexible modern OS. Cant do that with SCO Unixware.

    --
    "Give orange me give eat orange me eat orange give me eat orange give me you." -Nim Chimpsky
    1. Re:UNIX matters by boaworm · · Score: 4, Interesting

      I know that this is not entirely correct, but this is the way it "feels" like for me, personally.

      UNIX is the actual operating system (which Linux has made a very powerful and capable clone of). It could be OS X, Solaris, AIX, *BSD or whatever. Fine, now I have my UNIX station, what am I going to do with it ?

      Of course, I'm going to run GNU software on it. That's the whole point of running UNIX, the GNU software. Killer apps like the X server(s), Emacs, ftp/web/dns servers and virtually any other software you could ever imagine. I'm running UNIX (or clones) to run the GNU software.

      I'm curious, does anyone else share this view ?

      --
      Probable impossibilities are to be preferred to improbable possibilities.
      Aristotele
    2. Re:UNIX matters by Nick_dm · · Score: 1

      There is plenty of stuff out there that is OSS (and found on many linux distributions but not part of the GNU project. For example x.org and xfree86 are not GNU, neither is KDE and all the programs written for it, the BSD userland is not GNU and Apache, Open Office, MySQL and Mozilla variants are not GNU.

      If I switched from GNU/Linux to *BSD I probably wouldn't bother to replace all the BSD userland stuff with GNU. And most of the stuff I run on top of that is not GNU either, tho stuff like gcc would still be in use and I'm sure there are other bits in a BSD system. The GNU project is fantastic, but it is possible to run a UNIX type OS (and an open source one at that) without having to depend on it at every point.

    3. Re:UNIX matters by AstroDrabb · · Score: 4, Interesting
      UNIX is the actual operating system (which Linux has made a very powerful and capable clone of). It could be OS X, Solaris, AIX, *BSD or whatever.
      The thing is, is that Max OS X and *BSD are not UNIX. If you look at that list, according to the Open Group, the only recent OSes that are _true_ Unix and allowed to be called UNIX are Sun Solaris, IBM AIX and Compaq Tru64. So if you need a true Unix, these are your only choices. However, for me and probably many others, if you need close-to-Unix, then Linux, *BSD and even Mac OS X are very, very close and will do the job very well if not better then the current _true_ UNIX system out there. I don't think that the Unix name will be that important in a few years. Linux, Mac OS X and *BSD have a name already in the IT market. What would getting Linux, Mac OS X or *BSD Unix certified do for them?

      I do agree with you though about the GNU software. That is what makes a good Linux/*BSD system.

      --
      If Tyranny and Oppression come to this land,
      it will be in the guise of fighting a foreign enemy. -James Madison
    4. Re:UNIX matters by Anonymous Coward · · Score: 0
      ". . . it still carries enough weight, and maturity of two decades, to get attention."

      Try three and a half decades.

    5. Re:UNIX matters by smartfart · · Score: 1
      The thing is, is that Max OS X and *BSD are not UNIX.

      I don't remember there I read this, but someone once explained that while *BSD isn't trademark UNIX, it definitely is genetic Unix. Linux, on the other hand, isn't Unix at all, but merely a workalike.

    6. Re:UNIX matters by dosius · · Score: 1

      I am quite sure that someone was Eric S. Raymond.

      Moll.

      --
      What you hear in the ear, preach from the rooftop Matthew 10.27b
    7. Re:UNIX matters by pthisis · · Score: 1

      I don't remember there I read this, but someone once explained that while *BSD isn't trademark UNIX, it definitely is genetic Unix. Linux, on the other hand, isn't Unix at all, but merely a workalike

      To my mind, Unix is 3 things; an OS implentation, a trademark, and an OS family. BSD is the third and first, Solaris is all 3. Linux is the latter. I can't see any good reason that Linux would want the 1st or 2nd. POSIX certification seems much more useful, since (at least historically) being trademark Unix doesn't make many strong guarantees about your behavior--Xenix still had major differences from "real Unix" even after SCO had it and was legally calling it Unix.

      --
      rage, rage against the dying of the light
    8. Re:UNIX matters by Phred+T.+Magnificent · · Score: 1

      I'll agree that the whole point is to run the software, but please remember that the software isn't necessarily GNU. From your list, for instance, the X servers aren't, and the FTP, Web and DNS servers aren't. Expanding from there, Mozilla isn't, KDE and all of the software for KDE aren't, cdrecord isn't, ...



      It is certainly true that some of the important software is GNU (see, for instance, gcc and wget), but it would be a mistake to assume that Unix is only about running GNU software.

      --
      Where is the wisdom we have lost in knowledge?
      Where is the knowledge we have lost in information?
    9. Re:UNIX matters by KermitJunior · · Score: 1

      "it would be real nice if Linux is called UNIX"

      How about LUnix?

      --
      There is a Universal Life Value Check it
  54. What's in a name? by cpghost · · Score: 4, Insightful

    My first reaction was: "Why the heck should Linux be Unix-certified? With increasing popularity, Unix will soon have to be Linux-certified if it wants to get any kind of market acceptance."

    Well, as amusing as it may be, this thought is flawed. First of all Linux is merely the kernel; it's not even glibc, nor any other GNU tools, or third party packages. BSDs are Unix-like OS, just like Linux(-distros) are Unix-like. Solaris is also _a_ Unix-like OS, just like HP-UX.

    Actually Unix has become a generic term which refers to all kind of kernels that expose a POSIX (don't remember the exact number) interface to userland applications. Any kernel (or microkernel + servers) that implements this interface, can be justly called Unix (or at least Unix-like; so as to not feed SCOundrel or Open Group lawyers).

    The really interesting thing about the hype around Linux, is when we will move on and replace the Linux kernel with something totally different (be it microkernelized, or whatever). Then, we won't have just a GNU/Linux system anymore, but, say, also a GNU/Hurd/L4, GNU/Hurd/Mach or GNU/BSD, BSD/Linux, BSD/Hurd/*, ... system (terminology being "OS personality"/"OS servers"/"microkernel" or "OS personality"/"monolithic kernel").

    It seems silly to use the kernel name only as a brand for all kind of Unix-oid systems, regardless of them using the Linux kernel or something else; but providing the POSIX Unix interface.

    To wrap it up: it's just a matter of names and brands. As other posters have commented before, Linux has gained enough popularity and visibility. It doesn't need to be certified to be successful!

    --
    cpghost at Cordula's Web.
  55. Close enough by Anonymous Coward · · Score: 3, Interesting

    For the amiga's design purposes, it was pretty close to unix. It was intended to be a single-user system, so obviously, it didn't have all of unix's multi-user/network stuff. But it had true multitasking including it's own form of task prioritisation, pipes, similar commands, dynamic libraries, a powerful scriptable shell, etc.

    Sure, it wasn't unix technically speaking. However, if you allow a certain 'artistic license' like we do for OS X, and add in a 'handicap' since this was a 16-bit 7Mhz machine usually with 1MB RAM or less, we can start to see just what AmigaOS was. IMHO, it was closer to a personal version of GUI-enabled Unix than OS X has managed yet. Technology has moved on, but I still miss the productivity I had on AmigaOS.

    1. Re:Close enough by T-Ranger · · Score: 2, Funny

      By that logic, would CP/M not be VMS?

    2. Re:Close enough by kristaps.kaupe · · Score: 1

      For the amiga's design purposes, it was pretty close to unix. It was intended to be a single-user system, so obviously, it didn't have all of unix's multi-user/network stuff. But it had true multitasking including it's own form of task prioritisation, pipes, similar commands, dynamic libraries, a powerful scriptable shell, etc.

      MS-DOS 2.0 and later versions too had inspired from UNIX in many ways: handle-based file i/o API, pipes (well, not a real pipes, but...), possibility to use '-' as switch character, possibility to prefix device "files" with "/dev/" prefix, etc... But I don't think MS-DOS could be called "UNIX system".
    3. Re:Close enough by Anonymous Coward · · Score: 0

      Well, that's a good reference, actually. Compare Unix, AmigaOS, and DOS, and you'll see that, on the range of operating systems, AmigaOS and Unix are really quite similar.

    4. Re:Close enough by Anonymous Coward · · Score: 0

      Only if a single user on CP/M could do equivalent things to each single user on VMS, but with a more integrated and modern GUI :)

    5. Re:Close enough by Dwonis · · Score: 1

      I thought the main thing that made Unix Unix was its API. The AmigaOS API was almost nothing like Unix's, IIRC.

    6. Re:Close enough by Anonymous Coward · · Score: 0

      Well, I've already mentioned that some things were redesigned for various reasons. But, as others have already stated, the Unix API didn't even stablise until around a decade after the Amiga was launched, so it's tough to blame them for redesigning some things.

      And, well... the basic kernel docs *did* share a lot of similarty, if you insist on it. The Amiga Rom Kernel Manual was essentially a dump of manpages, too :)

    7. Re:Close enough by alangmead · · Score: 1

      Just because dos.library was written in BCPL, and BCPL is an ancestor of C, that doesn't make AmigaOS an ancestor of Unix. If you wanted to call AmigaOS an ancestor of TripOS, you would have less of an argument from me.

    8. Re:Close enough by NotZed · · Score: 1

      No way was it even close to unix.

      The design is much smaller/simpler (and hence more limited too), and far more modern. Sure it has its shell, but the shell isn't really anything like bourne shell. More than dos batch files but much less than bourne shell.

      Filesystem and device model is completely different. e.g. volumes have their own namespace, devices aren't attached to filesystem nodes, etc.

      Apart from being a 're-entrant pre-emptive multitasking os with a shell', there's really nothing at all similar between unix and amigaos (and even those areas are a stretch in many cases). Mores the pity for GNU in that regard.

      --
      _ // `Thinking is an exercise to which all too few brains
      \\/ are accustomed' - First Lensman
    9. Re:Close enough by Anonymous Coward · · Score: 0

      Well, I would hardly look to BCPL as a common factor in Unix Operating Systems. dos.library, in fact, was the only part of the OS that *wasn't* C.

      Not that I think a discussion of low-level details is relevant to the overall style and feel of an OS.

    10. Re:Close enough by alangmead · · Score: 1

      No, dos.library wasn't the only part that wasn't in C. There was the huge amount of 68K code too.

      And I'm not sure if you noticed that the thread, or even this topic is about, but it isn't the "overall style and feel of an OS", but what actually defines Unix as an OS. The initial question is "Can GNU Ever Be Unix?" and the thread started with a discussion of the Open Group's certification. Yes, you mentioned an "artistic license", but then compared it to a system with a complete BSD 4.4 kernel. You have to get to an extremely abstracted view before you can equate AmigaOS and Unix, and by then you have can probably include 75% of the operating systems ever developed to be in the same category.

    11. Re:Close enough by Anonymous Coward · · Score: 0

      Well, yes, you're right to a large degree -- you have to include other operating systems too. But just because others fall into the same category, that doesn't invalidate my point.

      As for OS X being BSD, isn't most of their BSD compatibility is an optional component? Last I heard, they didn't even support the full range of operations on their Unix filesystem.

    12. Re:Close enough by alangmead · · Score: 1

      In a previous version of the message, I started going through a list of multitasking systems that worked in ways I find very different than either Unix or the Amiga. Things like DESQview (multitasking multi-threaded extensions to MS-DOS with interapplication communication.) VxWorks ( a RTOS for embedded devices) etc. I took out the list because I thought that it didn't add significantly to the point. I'm now a bit sorry that I didn't. Those feature don't define Unix. Instead of "multitasking" being a Unix-like behavior, I'd describe Unix as having a mode of multitasking where new processes are described in terms of the processes that spawn them and inherit their parents characteristics. Instead of saying that interapplication communication is a Unix-like behavior, I'd describe Unix has having a unified of files, devices, pipes, and network communication. Most of these behaviors the Amiga got from its history from Tripos, and none of these were created with an attempt to mimic, nor any knowledge of the existence of Unix.

      As another point of proof. Notice that Tim King's resume talks about his work on the Amiga OS, but doesn't describe it as Unix-like. His later work on Helios he describes as Unix-like. http://www.tim-king.com/cv.html If he doesn't describe the Amiga OS as being Unix-like, I see no reason why anyone else should

      The Mac OS X installer does allow you to decide whether or not to optionally install the "BSD Subsystem", but that is not talking about whether to install Unix or not. It is always a BSD kernel running on a Mach microkernel. Processes and files and other kernel resources, even when they are created by programs using the Carbon API, still correspond to Unix PIDs and file descriptors and whatever and behave in that fashion. Even if you don't install the BSD subsystem, you still have a BSD kernel, the init process is still is spawned first and brings up the rest of the system. There is still a /bin/sh for running scripts, etc. The "BSD Subsystem" the installers mentions refers to user-space Unix components that aren't required for booting. The choice to install (or not) the BSD subsystem only controls whether more esoteric unix programs like, python, indent, info, banner, etc. are installed.

      I don't know what you mean by "full range of operations" of the Unix file system, unless you are referring to the way that the HFS filesystem drivers handle filenames in a case insensitive manner. (with makefile and Makefile both matching the same file.) All the other behavior (open/read/write/stat/link/unlink/fcntl/etc) all follow Unix semantics.

    13. Re:Close enough by students · · Score: 1

      How did you get the Amiga Rom Kernel Manual? That's illegal!

  56. WTF by Geekboy(Wizard) · · Score: 1

    Does noone remember that GNU stands for "GNU is Not Unix"

  57. Re:It's GNU/Linux! by 0x0d0a · · Score: 1

    Seriously speaking, the Hurd does seem to have a number of very nice ideas - the translators (little programs that can be attached to directories and files, and which will then control all access to those files - so you can attach one to a directory and make the contents of an FTP site or whatever appear there - not unlike the proc filesystem on Linux), for example. I wonder if anything like them could be implemented in Linux ?

    VFS, and at a user level, LUFS and fuse.

    It's implemented by mounting a new filesystem at that point, not by attaching something to a directory.

  58. Is Linux... Unix? by demon_2k · · Score: 0

    If it isn't, it must be bloody close. How else could SCO launch lawsuits on linux?

  59. Re:It's GNU/Linux! by Brandybuck · · Score: 1

    If you pay him $50 he will grudgingly allow you to omit the "GNU" from the name of your linux/busybox/dietlibc system. But you can't tell anyone else! Otherwise people will find out how truly unessential GNU is to Linux.

    --
    Don't blame me, I didn't vote for either of them!
  60. Breaking News by mslinux · · Score: 2, Funny

    GNU (GNU's not Unix) has been certified Unix. In other news... Richard Stallman died today of a sudden heart attack.

  61. New Acronym by NitsujTPU · · Score: 2, Interesting

    I don't know if this is a new idea, but why not just use Linux as an acronym.

    LINUX:
    Linix Is Not UniX

    Similar to PINE:
    Pine Is Not Elm

  62. Why bother by DarkOx · · Score: 3, Insightful

    Linux and GNU has its on street cred now. I really don't think the people still need to be sold on Linux and GNU being up to the job anymore. Most people wether they will admit it or not *know* Linux and GNU are now as good as the admin or engineer that runs the system, its the support network behind GNU and Linux they still worry about.

    I think whats telling is how often and for how long we have seen Unices shipping with the GNU tools and compiler in the system. GNU is not Unix its something that in most or maybe all cases is inspired by Unix works like Unix but is better then Unix. Getting GNU certified as Unix would in that sense almost be a slap in the face to GNU, although it might still be an endorsement to the Linux kernel. Linux though as stated before does have enough of its own cred that Unix certification will have very little meaning.

    --
    Repeal the 17th Amendment TODAY! Also Please Read http://www.gnu.org/philosophy/right-to-read.html
  63. Source code interoperability by iamacat · · Score: 1

    If Linux fully follows the Open Group standards, a lot of source code would run without change across compatible systems. Say you wrote a specialized, expensive CAD application for AIX. Now you might ask customers to cough up the hardware, since it will be only 30% of the cost anyway. On the other hand, if you can release it for Linux without any further effort, why wouldn't you?

  64. Can UNIX ever be certified as Linux? by ext42fs · · Score: 1

    That is the real question. The answer of course it that given it time, Linux will define UNIX.

  65. From the article.. (ok, a link in the article). by Mr2cents · · Score: 1

    The simple fact is that throughout all of this both SCO Group and IBM do have certified products, are licensed to and do use the UNIX trademark in association with certified products with the correct attribution.

    You can help us to remind the industry of the ownership of the UNIX trademark and ensure that its proper use as a neutral indicator of certification for the benefit of customers of UNIX systems.

    To help, is very simple, all you have to do is to publish the following attribution.

    "UNIX is a registered trademark of The Open Group in the United States and other countries."


    Consider it done.

    --
    "It's too bad that stupidity isn't painful." - Anton LaVey
  66. Comment removed by account_deleted · · Score: 2, Informative

    Comment removed based on user account deletion

  67. Re:It's GNU/Linux! by ultranova · · Score: 2, Interesting

    Hurd is definitely a good idea, but so far it is only that: an idea.

    I have been hearing about Hurd at least since 1992 or so, ever since Linus started his project. This is 12 years now, and nothing concrete has come up yet, that can be adopted by the masses.

    Of course, this is propably caused at least partially by Linux's success - Linux is drawing all the the good OS programmers.

    The dev mailing list archives seemed depressingly empty when I checked :(.

    Don't get me wrong, I like many of the ideas and design decisions they have. But my gripe is that their model does not allow hordes of programmers to join in and get things out faster, like the Linux model.

    Ironically, the Hurd should (at least in theory) be a lot easier to modify and develop. I wonder if I should give it a go... Maybe someone could port the Mach microkernel so it would work under Linux (or put a "Mach emulation layer" into the kernel) ? This would allow the Hurd to use the Linux device drivers, and allow people to try it without needing to repartition (you could use files as block devices via the loopback device). It would be just the kind of kick this project needs...

    Of course, you could make an user-mode Mach emulator, but that would likely be pretty inefficient. Or would it ? Hmm...

    Great, I already have all kinds of projects underway, from a roguelike for Java to a Usenet picture grapper with a web interface, and now this tought just had to pop in ;).

    --

    Forget magic. Any technology distinguishable from divine power is insufficiently advanced.

  68. Mach, with an emphasis on Mac... by MsGeek · · Score: 2, Interesting
    Apple's second foray into xNIX-like operating systems after A/UX was MKLinux. Basically MKLinux was the bastard child of Linux and the Mach microkernel. It's no longer actively developed by Apple for obvious (MacOS X) reasons, but it's still got a bit of a community left at http://www.mklinux.org/.

    I think it only runs on Power Macintosh, and it's the only flavor of Linux that will work on NuBus (first generation) Power Macs.

    --
    Knowledge is power. Knowledge shared is power multiplied.
    1. Re:Mach, with an emphasis on Mac... by Luyseyal · · Score: 1
      I think it only runs on Power Macintosh, and it's the only flavor of Linux that will work on NuBus (first generation) Power Macs.

      FYI, you can run with nubus patches to the standard linux kernel, these days. Not as many devices are supported and you need an installation of MacOS to get it to work, but it does work.

      Cheers,
      -l

      --
      Help cure AIDS, cancer, and more. Donate your unused computer time to worldcommunitygrid.org. Join Team Slashdot!
  69. GNU is hurdly Unix by Pan+T.+Hose · · Score: 1

    "Can GNU ever be Unix?" Doubtful at best. Personally I think GNU is not Unix and never will be. Incidentally, that is the very reason I use GNU in the first place, for I think it is much better than Unix, probably the EMACS alone is better (or at the very least complexier and more feature rich) than Unix. So no, GNU will not be Unix, in my opinion.

    --
    Sincerely,
    Pan Tarhei Hosé, PhD.
    "Homo sum et cogito ergo odi profanum vulgus et libido."
  70. GNU's Now Unix? by Pan+T.+Hose · · Score: 2, Insightful

    Great, that's what we need! Now the Santa Caldera Operation Group with Darl McBribe and other greedy rednecks from Tarantella, Utah, will want our money! When GNU was NOT Unix the life was simple. Now, everything is going to change, in this up-side-down world when GNU's Now Unix... Frightening perspective

    --
    Sincerely,
    Pan Tarhei Hosé, PhD.
    "Homo sum et cogito ergo odi profanum vulgus et libido."
  71. How about it's own certification? by Anonymous Coward · · Score: 0

    Nobody cares about Unix or it's owner SCO anymore. What we need is a certified API for Linux (and possibly *BSD/OSX if they want to play along) with a freely available test suite to ensure that any distribution or update remains compliant without having to take someone else's word for it. This frozen API should include the device driver side too or everyone needs to stop making excuses about why hardware support for Linux sucks and switch to OSX.

  72. Huh? by ElVirolo · · Score: 1

    Can GNU Ever Be Unix?

    Of course not !

    GNU's Not Unix, you insensitive clod !

  73. What Happened to Apple's UNIX lawsuit? by HighOrbit · · Score: 3, Interesting

    Last year the Open Group sued Apple because Apple was advertising OSX as a "UNIX". This was reported on slashdot here. Apparently Apple had originally licenced the trademark, but had stopped paying fees and the licence lasped. Apple contended that "UNIX" is now a generic term and that they shouldn't have to pay to licence it. The Open Group, of course, felt compelled to defend their cash-cow trademark, so they lauched a lawsuit.

    So, where is this now? I did a search but even the mighty power of Google can't seem to find any reference to the outcome or status of the case. Does anybody know what the status of this case is? Was it settled, or just languishing on the court's docket?

    1. Re:What Happened to Apple's UNIX lawsuit? by Anonymous Coward · · Score: 0

      Don't know abouth the lawsuit turnout,
      but Apple changed te "board" to "UNIX based" instead of "UNIX"!

      I guess the Opengroup put enough pressure to comply and pay or change the advertisement...

    2. Re:What Happened to Apple's UNIX lawsuit? by Anonymous Coward · · Score: 0

      Actually, Apple's bit was always "UNIX based." I imagine the lawsuit is just in a temporary limbo, but I'd love to know for sure.

  74. DUH by salesgeek · · Score: 1

    GNU is NOT Unix. GNU is NOT Unix.

    It's all in a name. Why even write an article about when "GNU is NOT Unix" will become certified Unix. This is a lot like having, say anarchists revolt and form a tolitarian government. Next article please.

    --
    -- $G
  75. [OT] your sig by Anonymous Coward · · Score: 0

    Project for a Non-American Century - sounds like a good idea to me. Here's 5 points for the budding European superpower to keep in mind:

    1: Being a superpower is expensive. Your government must be willing to dedicate at least 5 euros per year to military spending.
    2: Nobody ever got an aircraft carrier by wishing for it really hard. Be willing to dedicate at least a dozen full-time workers (6 hrs/day, 4 days/week, unless they're striking for shorter shifts this month) to building one.
    3: A functioning military needs equipment. A national arsenal consisting of 4 rifles left over from WWI and a medieval broadsword is totally insufficient.
    4: Tell the Americans to take all their military spending home. It's hard claim you're a superpower when you've got someone else's military camped out all over your country.
    5: Next time some half-assed dictator invades a neighboring country, goes on a genocidal rampage, or imposes an unfair import duty on Italian cheeses, go whinge to someone other than the Americans about it.

  76. Can an Apple be an Orange? by Anonymous Coward · · Score: 0

    What idiot asked this stupid question?

  77. No by Anonymous Coward · · Score: 0

    The amiga was not a Unix machine.

    It wasn't even close to a Unix machine.
    Windows NT is closer to being Unix than the Amiga was (through the Posix subsystem)

    And OS X doesn't need a certain artistic license, it really is Unix (just not trademark Unix).

    1. Re:No by Anonymous Coward · · Score: 0

      Well, we'll have to agree to disagree, I guess. My personal experience tells me otherwise.

  78. Unix is God by HermanAB · · Score: 1
    Linux is the son of God.

    Therefore Linux is God and consequently Linux == Unix.

    That would make perfect sense to 60% of Americans...

    --
    Oh well, what the hell...
  79. Can Stallman ever bathe? by Anonymous Coward · · Score: 0

    What about this?

  80. OT: could you explain a bit in your bio? by eugene+ts+wong · · Score: 1
    categorical syllogisms with non-validating logical form
    What are those? I looked up syllogisms, & I understand it, but not the rest.
  81. Frightening by Pan+T.+Hose · · Score: 1

    I still can hardly calm down. Please tell me, when GNU's Now Unix, I should send my cheques directly to Darl, shouldn't I? Or to SCO? Maybe Caldera? Or was it Tarantella? I am confused... Is it in Santa Cruz or Utah? Redmont, you say? You mean, I should pay the pimp Bill directly instead of using Darl, his bitch? What was the brothel called again? Caldera? SCO? Canopy? Microsoft? "Open" Linux my bloody arse... This is outrageously frightening. Please, let GNU continue being Not Unix. Thank you.

    --
    Sincerely,
    Pan Tarhei Hosé, PhD.
    "Homo sum et cogito ergo odi profanum vulgus et libido."
  82. Re:It's GNU/Linux! by alangmead · · Score: 2, Interesting

    The difference between what the HURD has designed and the various efforts to implement them in Unix like operating systems is in user space. The HURD allows (or will allow, once its done) per-process overrides of any system call. LUFS simply allows a user space program to tell the kernel how to represent a device. With the HURD, there is no reason why another user will even see the results of your translators.

    What I don't understand, is how the HURD is so late when it has these features. Creating or modifying a new system call should just involve installing a translator, testing it, and at worst logging out. No rebooting to test a new kernel feature.

  83. Being "Unix" would be BAD, people! by mcrbids · · Score: 1

    Linux is making a case for itself as being "NOT Unix".

    I saw an ad a while back in Ccmputer Reseller News that went something like: "Do we HAVE to use UNIX for our database?"...

    The implication is that "everybody knows"... UNIX==EXPENSIVE. Linus is much, much cheaper, and you can save $X,000 using Linux.

    Given its history of high price, vendor lockin, and balkinization, why would anything Linux even care about "being Unix"? Linux has buzz, Unix has a buzz. Which would you prefer?

    Unix is a good ancestor to Linux. Remember, GNU is NOT UNIX!

    --
    I have no problem with your religion until you decide it's reason to deprive others of the truth.
  84. Linux is more than a kernel these days by Nailer · · Score: 1

    First of all Linux is merely the kernel; it's not even glibc, nor any other GNU tools, or third party packages.

    Once upon a time, that was true - when you said 'Linux' it meant a kernel. These days, not so much.

    Technically, the Linux Standards Base includes kernel, c libaries, and various GNU tools (and their versions and interfaces).

    These days, kernel developers call themselves kernel developers. When people talk about Linux, they mean an OS. When people talk about getting a new version of Linux, they mean a new OS. Compare kernel.org with Linux.org.

  85. Could Linux be an extension to UNIX? by sdcmk · · Score: 2, Interesting

    I think a good point to remember is that the UNIX standard only lists minimum requirements for a UNIX. Linux could merely implement these requirements and still be able to innovate.

    Not only would this increase the capabilities of Linux but it could also serve as a way to bring UNIX applications into the Linux world with little effort. Once this is done, Linux can then efficiently replace UNIX itself.

    What I believe the industry needs, is a "modern UNIX" that can compete with Windows from not only a user point of view but also a technical one. We are starting to come to the point where not only is UNIX but Linux is starting to become "left behind" by Windows through .NET and the upcoming Longhorn. If Linux is going to be relevant after Longhorn on a technical level, it needs to start to innovate. The UNIX standard is a good place to start.

  86. why would we want to? by CAIMLAS · · Score: 3, Insightful

    Why would we want to have Linux be a certified Unix?

    When Saturn came around, or Asian cars came to the US, did they try and advertise themselves as "Ford-compatible" or did they try and make a name for themselves?

    This might have been a good idea a good 3, 4 years ago, but not now. 3, 4 years ago, Linux didn't have a market to speak of, and was not much more than an industry-wide toy. Now, it has major backing from IBM and Novell, and even people like my mom (technophobe nurse) is beginning to hear about Linux as the next-best thing. Linux currently offers, for the most part, much more than the Unix offerings. That couldn't have be said 5 years ago.

    The last thing the Linux community needs now is to have Linux associated with an old, outdated 'standard' that is Unix.

    --
    ~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
    1. Re:why would we want to? by jlockard · · Score: 1

      Apples and Oranges...

      Saturn would never have to advertise themselves as "Ford-Compatible". All they would have to do is advertise themselves as being an "automobile". And, there's no agency which would tell Saturn "You can't call that thing an automobile/car, unless you get us to validate your thing as meeting our requirements for being called an automobile/car." Sure there are gov't agencies which can determine that a "thing" isn't allowed on the roads, but the manufacturer can still call it an automobile/car.

      Actually, advertising the Saturn as "Ford Compatible" would probably hurt their sales. ;)

      --
      --JLockard - "Some mornings, it's just not worth chewing through the leather straps." - Emo Phillips
  87. This always comes up, but Linux is just the latest by Anonymous Coward · · Score: 0

    Well, as has long been clear to us old timers(tm), Unix is not a code base, it is a way to approach problems. This has been pointed out many times before, but perhaps the best description around is an excerpt from the recent science fiction novella PDU-1:

    I nodded again, appreciating as always the genius of the original Unix design, how it was in actuality more of a philosophy and methodology, a way to approach problems, than a code base. Because of this, it had been able to evolve, and therefore survive, over the many years of its existence.

    Linux is just the latest stage in the evolution of Unix, only this time it has finally achieved the type of license (GPL) it needs to keep on evolving. And because it is not a code base, antics such as those by SCO or other corporations will never be able to kill it.

    --ern

  88. Ask IBM, Novell, SCO ... by Shadowlore · · Score: 1

    and get 53 different answers.

    1 from IBM and Novell and 52 from SCO.

    --
    My Suburban burns less gasoline than your Prius.
  89. No. by mrkslntbob · · Score: 1

    It Can't.
    Then it would be GIU, and that just looks like a typo of GUI.

  90. Good old LSB... by Trejkaz · · Score: 1

    LSB is kinda neat, but I think that ruling out revolutionary distributions like GoboLinux due to non-compliance with the LSB would be unfair to those distributions. Revolution always seems to work better than evolution anyway.

    --
    Karma: It's all a bunch of tree-huggin' hippy crap!
  91. Yes But.. by noldrin · · Score: 1

    Yes it GNU could be Unix. But by the time they finished certifying it, the version would be far too old for anyone to care. The opensource software cycle is quite a bit different than the traditional software cycle.

  92. OSX is not based on FreeBSD by ValourX · · Score: 1

    You are totally wrong. The OS X kernel has nothing to do with FreeBSD... OS X is based on Darwin. Darwin is based on Mach and NeXTstep, with many userland programs from FreeBSD. The heart of OS X has little/nothing to do with FreeBSD.

    -Jem

  93. Hello, G.N.U by acidrain69 · · Score: 1

    GNU's not Unix. It can NEVER be Unix. Duh!

    --
    -- Having a Creationist Museum is like having an Atheist place of worship
  94. Re:No. Unless Linus or Posix makes a change. by 10Ghz · · Score: 1
    Note that Linus did a 180 on "Linux Threads" versus "POSIX Threads" because Linux vendors wanted portability.


    of course, the fact that the New Posix Threading Library (AKA NPTL) is an order of magnitude faster than LinuxThreads were, had absolutely nothing to do with it...
    --
    Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
  95. Re:No. Unless Linus or Posix makes a change. by pthisis · · Score: 1

    Note that Linus did a 180 on "Linux Threads" versus "POSIX Threads" because Linux vendors wanted portability

    Actually, he quite rightly didn't want to implement POSIX threads in the kernel originally, but went for a much more flexible Plan-9 style clone() call originally.

    He never "did a 180" on this, either. He originally wanted a userspace implementation on top of Posix threads, which is what Xavier Leroy's LinuxThreads package was. Then Ingo cam along and made another implementation in userspace called NPTL. During the process of designing it he discovered that a few features at the kernel level (most notably futexes and the CLONE_DETACHED option) could help tremendously. futexes are useful for many things outside of Posix threads (Linus insisted on making a generic mutual exclusion mechanism rather than one that's pthread-specific), and CLONE_DETACHED is no different from similar flags that had been added before.

    In short, Linus merely switched his endorsement from one implementation of pthreads at the userspace level to another. Had Xavier Leroy come up with a fast kernel mutex implementation, Linus probably would have accepted that as well. The original idea, though--that of using a much more general (and flexible, and easier to maintain) clone() call rather than implementing Posix threads at the kernel level--has not changed at all. In fact, at least some Java implementations use the native Linux threads without the POSIX wrappers, as do certain web servers.

    --
    rage, rage against the dying of the light
  96. UNG by 4of12 · · Score: 1

    GNU compliant systems proliferating as they are, they're no longer the rebellious and oppressed minority.

    If anything, TOG should start advertising itself as

    UNG, "Unix's Not GNU"
    ..

    UNG - It's not just a noise you emit when slugged in the solar plexus!

    --
    "Provided by the management for your protection."
  97. Re:It's GNU/Linux! by ultranova · · Score: 1

    What I don't understand, is how the HURD is so late when it has these features. Creating or modifying a new system call should just involve installing a translator, testing it, and at worst logging out. No rebooting to test a new kernel feature.

    The Hurd lacks device drivers. Most of them are copied from Linux 2.0, and the penguin has gone on a long way since then. Also, there is no support for sound cards currently. Then there's the annoying problem that the current filesystem translators have been designed to memory map the whole partition at once, which means that on a 32-bit system you can only have 2GB partitions (which, according to the development mailing list posts, prevents XFree86 from being compiled on the Hurd, among other things - there's simply not enough disk space (even the Hurd comfirms it - XFree86 is dying ;))...

    And you can't make testing new device drivers something that can be done by any user. A device driver must run at a higher permission level of the processor in order to communicate with the rest of the machine; and, of course, a faulty or malicious hard drive device driver will end up wiping your data under any operating system. The device drivers are the bane of any new PC operating system.

    Add the fact that, as I said, the penguin has marched on. Linux is eating Window's market, slowly but surely, but it's also eating Hurd's market. People who want a stable, efficient, free operating system are migrating to Linux. As a result, Linux gets more users, leading to everyone putting their efforts into improving Linux (and consequently not putting them into improving Hurd), which attracts more users which attracts more developers and so on. The Hurd is not only trying to do (AFAIK) something completely new, but it's directly competing with a technically superior, entrenched and still rapidly growing competitor at the same time.

    As long as Linux keeps on improving at a steady pace, Hurd will stay marginal. If/when the day comes that the monolithic kernel architechture has been tuned to it's limit with nothing left to improve (because any change is likely to cause weird bugs), then the developers might turn to the Hurd for new growth. But not before.

    --

    Forget magic. Any technology distinguishable from divine power is insufficiently advanced.

  98. Re:No. Unless Linus or Posix makes a change. by alangmead · · Score: 1

    This topic is probably so old that no one is reading it any more, but I just came across an old note that I left to myself about this document summarizing the differences between POSIX and LSB