Slashdot Mirror


The Strange Birth and Long Life of Unix

riverat1 writes "After AT&T dropped the Multics project in March of 1969, Ken Thompson and Dennis Ritchie of Bell Labs continued to work on the project, through a combination of discarded equipment and subterfuge, eventually writing the first programming manual for System I in November 1971. A paper published in 1974 in the Communications of the ACM on Unix brought a flurry of requests for copies. Since AT&T was restricted from selling products not directly related to telephones or telecommunications, they released it to anyone who asked for a nominal license fee. At conferences they displayed the policy on a slide saying, 'No advertising, no support, no bug fixes, payment in advance.' From that grew an ecosystem of users supporting users much like the Linux community. The rest is history."

293 comments

  1. Future by masternerdguy · · Score: 5, Insightful

    I can see some form of UNIX making it to the 22nd century and beyond.

    --
    To offset political mods, replace Flamebait with Insightful.
    1. Re:Future by swanzilla · · Score: 5, Funny

      I can see some form of UNIX making it to the 22nd century and beyond.

      +1 Forth-sightful

    2. Re:Future by jellomizer · · Score: 5, Funny

      Not the 32bit versions though. They wont make it past 2038.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    3. Re:Future by NoNonAlphaCharsHere · · Score: 1, Informative

      Fail. That's:

      1 + Forth-sightful.

    4. Re:Future by CmdrPony · · Score: 1, Insightful

      That's easy to fix, just reset the timer. We should change 0 to 2000 anyway, it's much better place for it than 1970.

    5. Re:Future by PolygamousRanchKid+ · · Score: 4, Insightful

      Just before 2038, there will be tons of hype about "The End of the Epoch!", just like "Happy New Year 2000! Nothing works anymore!" Plenty of work for onery, old C programmers like me, with lawns to get off of.

      After 2038, when everything is still working despite dire predictions, we will have to wait a bit for the next opportunity, when the 64 bit epoch runs out . . .

      --
      Schroedinger's Brexit: The UK is both in and out of the EU at the same time!
    6. Re:Future by gman003 · · Score: 5, Informative

      After 2038, when everything is still working despite dire predictions, we will have to wait a bit for the next opportunity, when the 64 bit epoch runs out . . .

      64-bit Unix time will run out on December 4, precisely at 3:30:08 PM, 292,277,026,596 AD. It will be a Sunday.

      By then I fully expect computers will already have migrated well into the gigabytes-per-machine-word range, or will no longer be using bits as we know them. Either that, or we'll have encountered the heat death of the universe, so it will be irrelevant.

    7. Re:Future by tangent · · Score: 1

      Are you sure? I would have thought it would be

      1 Forth-sightful +

    8. Re:Future by Lithdren · · Score: 1

      Lets hope not, the heat death of the universe isn't supposed to be for another 99,999,999,999,999,999,999,999,999,999,999,999,999,999,999,999,999,999,999,999,999,999,999,999,999,999,999,999,999,986,250,000,000 years or so, give or take a few ...hundred billion or so.

    9. Re:Future by wavedeform · · Score: 2

      Fail. That's: 1 + Forth-sightful.

      Actually, wouldn't it be: 1 Forth-sightful +

    10. Re:Future by Anonymous Coward · · Score: 5, Funny

      Is that a Sunday?

    11. Re:Future by crutchy · · Score: 1

      Re: "we will have to wait a bit for the next opportunity, when the 64 bit epoch runs out . . ."

      Machines will be programming us by then (well, whatever is left of us). The Matrix said so it must be true.

      Hopefully I can catch a transport to the other galaxy far far away by then and hook up with Princess Leia. I'll have to kill of Han Solo and his pet Chewbacca, but I'll have a death ray gun by then.

    12. Re:Future by Anonymous Coward · · Score: 0

      AC will fix the heat death problem. After all, it is "The Last Question".

    13. Re:Future by r0b!n · · Score: 1

      Hey that is my birthday. Shit will I feel old.

    14. Re:Future by Anonymous Coward · · Score: 0

      If a universe experiences heat death, can anyone be there to see it?

    15. Re:Future by Anonymous Coward · · Score: 0

      But we'll still be waiting for ZFS to fill up.

    16. Re:Future by froggymana · · Score: 1

      And then it wouldn't make it past 2068....

      --
      "To prevent this day from getting any worse, I'll just read ERROR as GOOD THING" 1GJU8xLuDKDxEs4KLf8fAGyptoDsqvEsBT
    17. Re:Future by Anonymous Coward · · Score: 0

      64-bit Unix time will run out on December 4, precisely at 3:30:08 PM, 292,277,026,596 AD. It will be a Sunday.

      Did you account for leap seconds?

    18. Re:Future by ardeez · · Score: 1

      Ha! We developers will never learn.

      Come Sunday Dec 4th 292,277,026,596AD I bet you there'll still be some poor saps running around doing last minute testing whilst the managers on multi universe conference calls will all be saying :
      'but we never thought the cobol code would be going for soo long! We just kept putting off the upgrades, and before you know it 2,922,770,245 centuries had passed and here we are!'

      --
      don't be a spelling loser
    19. Re:Future by Darinbob · · Score: 1

      Just switch to unsigned longs and gain some more decades.

    20. Re:Future by dbc · · Score: 1

      Continuing in the tradition of Forth programmers everywhere to define new words and compress the code until the entire application fits on one line, and is indistinguishable from modem noise:

      Forth-sightful 1+

      the word '1+' (or a variant) is often defined because incrementing the top of stack is so useful.
      And if you want to see the result:

      Forth-sightful 1+ .

      Forth has its place, but I'd hate to implement anything big using it.

    21. Re:Future by dbc · · Score: 1

      Actually.... Forth-sightful is just the address. So:

      Forth-sightful @ 1 + !

      is more correct. Or:

      Forth-sightful @1+

      which might not be quite right either.... this is why Forth has a blessedly small cult following.

    22. Re:Future by philfr · · Score: 4, Funny

      Not sure, but the restaurant out there is open 24/7.

    23. Re:Future by operagost · · Score: 1

      Thanks, you just blew up my email archives going back to 1996!

      --

      Gamingmuseum.com: Give your 3D accelerator a rest.
    24. Re:Future by Anonymous Coward · · Score: 0

      Of course not. It's going to be on a Friday at 5:00 PM.

    25. Re:Future by TreyGeek · · Score: 1

      Or is that 1 +1 +Forth-sighful +1?

    26. Re:Future by darenw · · Score: 1

      By then, enough leap seconds will have accumulated that maybe it won't be a Sunday.

    27. Re:Future by arkane1234 · · Score: 1

      Most 32-bit processors will be dead before that time, thankfully :)

      --
      -- This space for lease, low setup fee, inquire within!
    28. Re:Future by jellomizer · · Score: 2

      You say this after I had debug some code programmed to run in a tape stack.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    29. Re:Future by Anonymous Coward · · Score: 0

      depends on your time zone

    30. Re:Future by Anonymous Coward · · Score: 0

      friendliest steaks in town

    31. Re:Future by Anonymous Coward · · Score: 0

      hmmm ....2038........2 years until I finish paying up my mortgage :D

    32. Re:Future by neonKow · · Score: 1

      Are you accounting for leap seconds and the like? After all, there will be quite a few of them.

    33. Re:Future by DrProton · · Score: 1

      64-bit Unix time will run out on December 4, precisely at 3:30:08 PM, 292,277,026,596 AD. It will be a Sunday.

      Hmm. With tongue planted in cheek, what did you use for the length of a day, which is slowly increasing, due to tidal acceleration? If I make the simplistic assumption of a linear increase of +1.70 ± 0.05 ms/cy over a time span of 2^64 seconds, the total increase in the length of a day is given by 0.0017*2^64/(100*365.2425*24*3600) 9937419 years (100*365.2425*24*3600 is the number of seconds in a century with accounting for leap years). This obviously cannot be the case. We have no idea what the date will be 2^64 seconds from now, never mind that no humans will be around to record it.

      --
      "Mit der Dummheit kaempfen Goetter selbst vergebens." - Schiller
    34. Re:Future by CSMoran · · Score: 2

      If a universe experiences heat death, can anyone be there to see it?

      INSUFFICIENT DATA FOR MEANINGFUL ANSWER

      --
      Every end has half a stick.
    35. Re:Future by Thing+1 · · Score: 1

      ~292 billion years from now will be ~288 billion years after the sun expands to Earth's radius. So, we will need to have migrated away from where we are now if those computers are to continue computing.

      --
      I feel fantastic, and I'm still alive.
    36. Re:Future by Anonymous Coward · · Score: 0

      Nice Asimov reference!

    37. Re:Future by t_ban · · Score: 1

      64-bit Unix time will run out on December 4, precisely at 3:30:08 PM, 292,277,026,596 AD. It will be a Sunday.

      What a coincidence -- that is also the year of Linux on the Desktop!

      --
      First they ignore you. Then they laugh at you. Then they fight you. Then you win. -Gandhi
  2. Version 1, shirley? by Nimey · · Score: 1

    since the old versions were known as Version 5, Version 7, and so on.

    --
    Hail Eris, full of mischief...

    E pluribus sanguinem
    1. Re:Version 1, shirley? by Coeurderoy · · Score: 1

      System I, I think System II got the "versions", then they "jumped" to System III, although many people allready had sidejumped to Berkeley.
      But indeed it started with System, not versions, (but the "versions" made it popular :-))
      I found particularly interesting the "programmers work bench" http://en.wikipedia.org/wiki/PWB/UNIX wich had all kinds of cool programming and text processing tools :-)

    2. Re:Version 1, shirley? by antdude · · Score: 1

      ... and don't call me Shirley. ... and stop calling me Shirley! :)

      --
      Ant(Dude) @ Quality Foraged Links (AQFL.net) & The Ant Farm (antfarm.ma.cx / antfarm.home.dhs.org).
    3. Re:Version 1, shirley? by Guy+Harris · · Score: 1

      System I, I think System II got the "versions", then they "jumped" to System III, although many people allready had sidejumped to Berkeley. But indeed it started with System, not versions, (but the "versions" made it popular :-))

      Well, yeah, it started with "System", as in "The UNIX Time-sharing System". The document cited there is "Unix Programmer's Manual, First Edition", at least according to Dennis Ritchie's home page. I'm not sure Research UNIX had anything as formalized as "releases", as opposed to "what we have right now when we're making a UNIX tape", and I'm not sure that the "version numbers" applied to the operating system rather than to the manual.

      There was no "System I" or "System II"; "System III" came from a line of UNIXes that combined Research stuff with the (based on something that looked like V6 with the "Phototypesetter, Version 6" enhancements and some other post-V6 stuff) first edition of PWB/UNIX and a bunch of other UNIXes inside AT&T.

  3. So THEY invented "RTFM!" by tomhudson · · Score: 0

    eventually writing the first programming manual for System I in November 1971
    From that grew an ecosystem of users supporting users much like the Linux community.

    For those few who are new here and don't know what RTFM means, read the RTFM!

    1. Re:So THEY invented "RTFM!" by maxwell+demon · · Score: 2

      For those few who are new here and don't know what RTFM means,

      which obviously includes you because otherwise you would not have written:

      read the RTFM!

      --
      The Tao of math: The numbers you can count are not the real numbers.
    2. Re:So THEY invented "RTFM!" by Anonymous Coward · · Score: 3, Funny

      You should be aware that RTFM hasa different meaning in the Windows world: Reboot The Fucking Machine

    3. Re:So THEY invented "RTFM!" by V!NCENT · · Score: 2

      Parent is correct:
      $man rtfm

      It's a manual on reading the fscking manual.

      --
      Here be signatures
    4. Re:So THEY invented "RTFM!" by asheller · · Score: 1

      Waite! Let me do a man on that!

    5. Re:So THEY invented "RTFM!" by rasherbuyer · · Score: 1

      $ man rtfm
      No manual entry for rtfm

    6. Re:So THEY invented "RTFM!" by V!NCENT · · Score: 1

      Download The Fscking Manual!

      --
      Here be signatures
    7. Re:So THEY invented "RTFM!" by Wandering+Voice · · Score: 1

      Not only that, but as long as I ignore/don't think of how I had done things in WinXP, I find that Linux (OpenSUSE 11.4 here) is very straightforward and simple.

      It may help that before migrating from XP, I made effort to use open-source and cross-platform tools whenever possible. And it really paid off this year when I switched. (Yay! Year of the Linux desktop, for me at least.)

    8. Re:So THEY invented "RTFM!" by Anonymous Coward · · Score: 0

      Wouldn't that be:
      man fscking

    9. Re:So THEY invented "RTFM!" by V!NCENT · · Score: 1

      In order to be fscking, you must first understand fscking by typing "man fsck", or in your case; "info fsck".

      --
      Here be signatures
    10. Re:So THEY invented "RTFM!" by Hognoxious · · Score: 1

      For those few who are new here and don't know what RTFM means, read the RTFM!

      Yo dawg, I heard you like to RTFM, so I put an FM in the FM so you can RTFM while you RTFM.

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
  4. UNIX family tree by HockeyPuck · · Score: 5, Informative

    Image from wikimedia of the UNIX Family Tree

    1. Re:UNIX family tree by HiroProX · · Score: 1

      They missed IRIX.

    2. Re:UNIX family tree by the+linux+geek · · Score: 5, Informative

      And DG/UX, Reliant UNIX, Risc/os, SINIX, Unicos, Dynix, and about twenty other moderately successful moderate 90's UNIX systems. If you look closely, it's only showing systems that are either still alive or ancestors of systems that are still alive.

    3. Re:UNIX family tree by HockeyPuck · · Score: 4, Informative

      This is a much better tree, has atleast a hundred different versions on it...

      http://www.levenez.com/unix/

    4. Re:UNIX family tree by 0100010001010011 · · Score: 5, Informative

      That's just the "Light" version.

      A more complete version is here:
      http://www.levenez.com/unix/

      Includes IRIX, Reliant, SINIX, Risc, Unicos, Dynix.

      And more fun stuff like iOS.

    5. Re:UNIX family tree by Jeremiah+Cornelius · · Score: 1

      I miss Irix. :-( And Indigo Magic.

      --
      "Flyin' in just a sweet place,
      Never been known to fail..."
    6. Re:UNIX family tree by NoNonAlphaCharsHere · · Score: 2

      You forgot ULTRIX, although why anyone would want a computer in their home is beyond me.

    7. Re:UNIX family tree by Anonymous Coward · · Score: 1

      I guess GNU has nothing to do with UNIX, eh?

      'Linux' should be 'GNU/Linux', on that diagram if nowhere else.

    8. Re:UNIX family tree by Anonymous Coward · · Score: 1

      IRIX is still alive, looking grave but still kicking. The last release is from 2006, and I guess support is supposed to continue till December 2013 at least.

    9. Re:UNIX family tree by Maximum+Prophet · · Score: 2

      I have several unopened sets of Irix 6.x buried somewhere in a box in my basement. Alas, I've nothing to run them on. As I recall, Irix came complete with lots of utilities, but the C complier was crippled, unless you paid extra, PPP was crippled unless you paid extra, etc. etc.

      --
      All ideas^H^H^H^H^Hprocesses in this post are Patent Pending. (as well as the process of patenting all postings)
    10. Re:UNIX family tree by Jeremiah+Cornelius · · Score: 1

      True about the Irix libs for the C compiler.

      I have an Indigo R4400 Elan and an Indigo2 R4400 MaxImpact. They are elegant space-heaters, that also run antique FIrefox versions.

      --
      "Flyin' in just a sweet place,
      Never been known to fail..."
    11. Re:UNIX family tree by sunderland56 · · Score: 1

      Wouldn't it be awesome to port Irix to the Chinese MIPS laptop?

    12. Re:UNIX family tree by DrSkwid · · Score: 1

      GNU is Not Unix

      the clue is in the title

      --
      There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
    13. Re:UNIX family tree by Anonymous Coward · · Score: 0

      What about those of us running BSD/Linux?

    14. Re:UNIX family tree by Guy+Harris · · Score: 1

      And they also missed a line from SunOS 4 to SVR4; they showed it as a line from 4.3BSD instead. The SVR4 VM system and VFS layer came from SunOS 4.x, and the dynamic-linking mechanism, although changed a bit with the switch from a.out to ELF, also came from SunOS 4.x. Most of the BSDisms added to SVR4 also came from SunOS 4.x rather than directly from 4.3BSD.

    15. Re:UNIX family tree by jedidiah · · Score: 1

      Never trust a recursive acronym.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    16. Re:UNIX family tree by Jeremiah+Cornelius · · Score: 1

      It'd be fun.

      I wish xorg had framebuffer support for these old Indigos.

      Then? You could get a Linux or BSD going.

      --
      "Flyin' in just a sweet place,
      Never been known to fail..."
    17. Re:UNIX family tree by Anonymous Coward · · Score: 0

      Well the acronym GNU pretty much says it, eh?

    18. Re:UNIX family tree by CronoCloud · · Score: 1

      or a Fat PS2, you'd still need the Linux kit to boot it though.

    19. Re:UNIX family tree by bobstreo · · Score: 1

      I didn't see AUX on either of them either.

      I think I may still have the floppies for AUX (Unix for Macintosh around I wanna say Finder v6)

      Startup message: "When in danger, when in doubt, run in circles, scream and shout"

    20. Re:UNIX family tree by Anonymous Coward · · Score: 0

      FAIL acronym isn't looppy.

    21. Re:UNIX family tree by lowen · · Score: 1

      If you have IRIX sets, go to Nekochan.net

    22. Re:UNIX family tree by Bert64 · · Score: 1

      Funny thing about the IRIX C compiler (on 6.5), if you tried to use it you got a big warning about it not being licensed, but then it worked anyway... You also had a second compiler tucked away in a subdir somewhere which was for rebuilding the kernel modules.

      I think the compiler on 5.3 just worked normally and shipped with the OS, but that was quite some time ago.

      Would you part with a copy of IRIX? i have a bunch of old SGI boxes, and no original media for them...
      Also if you want a box to run your IRIX on, i have a spare octane and a spare onyx.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    23. Re:UNIX family tree by Bert64 · · Score: 1

      Linux supports X on the Octane series, might as well get one of those since they're pretty cheap these days...

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    24. Re:UNIX family tree by Bert64 · · Score: 1

      The IRIX source code is available if you know where to look...

      Speaking of chinese MIPS cpus, the only machines i've seen available are using the Loongson 2f chips which are pretty mediocre, whereas the Loongson 3 chips look really interesting (quad core, low power)... I've been trying for a while to get one of the dual cpu loongson 3 motherboards they talked about a while ago but they're impossible to get hold of... Contacting loongson direct they told us to go to their "oem partners" but wouldnt tell me who they were, and i couldnt locate any of them myself.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    25. Re:UNIX family tree by Anonymous Coward · · Score: 0

      It appears from the tree that the only versions which were not derived from original Unix are Minix and Linux.

    26. Re:UNIX family tree by Anne+Thwacks · · Score: 1
      That is pretty much correct.

      Now get off my lawn

      --
      Sent from my ASR33 using ASCII
    27. Re:UNIX family tree by unixisc · · Score: 1

      Lemote? RMS uses GNewSense Linux on one of those, calling it as completely free hardware. As for Indigos and Indy workstations, both Debian & FreeBSD have ports that support it.

    28. Re:UNIX family tree by Jeremiah+Cornelius · · Score: 1

      Debian and FreeBSD don't support the IP20 and similar series framebuffers, or the digital audio. :-(

      These MAY become my home heating system/servers, tho. :-)

      --
      "Flyin' in just a sweet place,
      Never been known to fail..."
    29. Re:UNIX family tree by cthulhu11 · · Score: 1

      Looks like ConvexOS didn't rate.

    30. Re:UNIX family tree by zandeez · · Score: 1

      I find it somewhat amusing that "OpenServer" is marked as Closed Source.

  5. The heydays ended ten years ago by G3ckoG33k · · Score: 1
    1. Re:The heydays ended ten years ago by the+linux+geek · · Score: 4, Insightful

      Top500 is basically irrelevant as a model of the server industry as a whole. UNIX is still kickin' on scale-up commercial servers and doing pretty well at it.

    2. Re:The heydays ended ten years ago by sunderland56 · · Score: 3

      Do you really consider Unix and Linux to be two separate things?

      If lawyers didn't exist, Linux would not have been needed.

    3. Re:The heydays ended ten years ago by JWSmythe · · Score: 3, Insightful

      [smacks G3ckoG33k with a wrench, and drags him into another room]

      Look here, we have something to explain to you.. Unix spawned many variations.

      http://upload.wikimedia.org/wikipedia/commons/7/77/Unix_history-simple.svg

      All were similar in concept, but had their own ways of doing things. As this branched away from a common path, most groups agreed on a common set of rules, known as POSIX.

      Once you've learned how one Unix-like environment works, you can use them all. You will find that a Linux server, an Android phone, a TiVo DVR, and even an Apple desktop, all operate in very similar ways, although each has its quirks.

      The outstanding rogue operating system now is Windows. They too have recognized that they are missing out by remaining completely non-compliant, and have begun incorporating various aspects of POSIX as add-on (SFU or SUA) and 3rd party (Cygwin) packages.

      The chart you displayed should have had the "Unix" name divided between major and minor groups. Major being operating systems such as Linux. Minor elements combined in as "Other Unix" and "Other OS". In that, "Windows" having such a minor share, should have only been labeled "Other OS".

      In November 1993, Cray, Inc accounted for 40% all systems in the graph, and the largest share of the "Unix" segment. It would have been a mixture of UNICOS, COS, and Solaris. "Unix" as a specific OS only accounted for 15%. Even those were simply the OS name provided for the list, as an indication of a Unix-like operating system, not that it was actually "Unix".

      Now get back out there, and don't make me hit you with a wrench again.

      --
      Serious? Seriousness is well above my pay grade.
    4. Re:The heydays ended ten years ago by BitZtream · · Score: 3, Informative

      Yes, they are different things.

      UNIX implies a specific API and several other things. Several OSes are UNIX, including Mac OS and Solaris.

      Linux is an OS that is not UNIX as it intentionally does not implement the requirements for being called UNIX and as such has never and will unlikely ever be certified as a UNIX.

      Just because you don't know what the words you use MEAN doesn't mean no one else does.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    5. Re:The heydays ended ten years ago by jedidiah · · Score: 1

      No. Linux was needed because the FSF takes too long to finish anything. Even without the lawsuits, GNU would have had broader mass market appeal than the BSD.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    6. Re:The heydays ended ten years ago by Guy+Harris · · Score: 1

      The heydays ended ten years ago:

      http://en.wikipedia.org/wiki/File:Operating_systems_used_on_top_500_supercomputers.svg

      The culprit? Linux.

      ...which is a UNIX-compatible OS.

      I'm curious how much recognizably-AT&T-derived code is in the current commercial UNIXes; probably more than in Linux distributions, but it might not be as much more than people think. UNIX's legacy is more the APIs and command-line interface than the actual code, and Linux has that stuff.

    7. Re:The heydays ended ten years ago by DesScorp · · Score: 4, Insightful

      The heydays ended ten years ago:

      http://en.wikipedia.org/wiki/File:Operating_systems_used_on_top_500_supercomputers.svg

      The culprit? Linux.

      Linux is Unix. Even if it's not certified as such. If it walks like a duck, quacks like a duck, etc. People started using Linux in the first place because they wanted "a Unix" for personal use. Linux is just a clone of Unix. In the end, it's not really all that different from "Unix proper" than the various flavors of licensed Unix are from each other. I'd argue that most Linux systems are a good deal closer to, say, Solaris, than OS X is... an officially certified Unix.

      --
      Life is hard, and the world is cruel
    8. Re:The heydays ended ten years ago by Anonymous Coward · · Score: 0

      Do you really consider Unix and Linux to be two separate things?

      Ayup. I use both every day. Linux is better, because it has capabilities. It still has the horribly limited and antique unix-style file/folder structures, though - three octal modes, single group per file, no fs-level versioning, etc.

      I used to write systems and apps code on 64-bit computers with graphical UIs, language and context-sensitive IDEs, no root superuser, and automatic versioning filesystems. But that was back in the 1980s, before the black ships came and the secret of hose gartering that never ravels was forgotten.

      I miss VMS vaxen sometimes.

    9. Re:The heydays ended ten years ago by sunderland56 · · Score: 3, Funny

      Several OSes are UNIX, including Mac OS and Solaris.

      Right, of course, I had *totally* forgotten that MacOS and Solaris were binary compatible. My bad.

      Good thing I didn't confuse the terms "Unix" and "POSIX compliant". That would have been embarrasing.

    10. Re:The heydays ended ten years ago by Guy+Harris · · Score: 1

      Do you really consider Unix and Linux to be two separate things?

      "Unix", as in "the registered trademark "Unix"", is separate from "Linux", meaning either the Linux kernel or the set (equivalence class?) of Linux distributions. To be legally eligible to be called a "Unix", an OS has to pass the Single UNIX Specification test suite; as far as I know, nobody's run any Linux distributions through that test suite.

      However, Linux is most definitely a "Un*x", in that its API is a UNIX-derived API, even if it might not be able to check every single checkbox for the Single UNIX Specification.

    11. Re:The heydays ended ten years ago by UnknowingFool · · Score: 1

      The top500 is only an indicator of a specific use. And I suspect that Linux is used because of specific advantages like cost and flexibility. The ability to run Intel/AMD in combination with GPUs is a lot cheaper than hardware from a single maker. Also the Linux kernel can be tweaked for HPC. It is harder with commercial Unix. For the most part Unix is still being used for things like big iron.

      --
      Well, there's spam egg sausage and spam, that's not got much spam in it.
    12. Re:The heydays ended ten years ago by jedidiah · · Score: 1, Insightful

      You sound like a Mac user that's content to use a very limited definition of what constitutes Unix in order to brag and create misleading ads.

      Those of us that actually use multiple Unixen on a daily basis and have done so for decades have a more complete picture of what a Unix is.

      The "several other things" are kind of important on a day to day basis.

      Linux is much more compliant as a Unix than MacOS is in this regard.

      Go play with your pretty pictures and stop trying to lecture real Unix users.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    13. Re:The heydays ended ten years ago by Guy+Harris · · Score: 3, Insightful

      Those of us that actually use multiple Unixen on a daily basis and have done so for decades have a more complete picture of what a Unix is.

      And those of us who actually develop for multiple Unixes have to deal with all their quirks, and don't always find Mac OS X the quirkiest.

    14. Re:The heydays ended ten years ago by MightyMartian · · Score: 3, Informative

      No kidding. The whole "*nix" descriptor came about because there were operating systems that were actually licensed variants of Unix, and other systems that were Unix-like, but legally could not call themselves Unix. Unix vs. Unix-like was not a technical description, but rather a legal one. Since Linux supports pretty much all the major features found in actual Unix-based systems, for all intents and purposes it is a Unix variant, even if it is a rewrite.

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
    15. Re:The heydays ended ten years ago by Guy+Harris · · Score: 3, Informative

      I use both every day.

      I don't think there's an OS sold today whose name is just "Unix", so "[using] Unix" presumably means "using an operating system that has been certified as following the Single UNIX Specification"; which particular such OSes do you use every day?

      Linux is better, because it has capabilities.

      If by "capabilities" you mean stuff such as "POSIX capabilities" that means you don't just have "normal privilege" and "root privilege", Solaris (which is an operating system that has been certified as following the Single UNIX Specification) has them as well.

      It still has the horribly limited and antique unix-style file/folder structures, though - three octal modes

      As opposed to four hexadecimal modes?

      Linux, and several other UN*Xes, also support access control lists, at least on some file systems, if that's what you're contrasting with "three octal modes". (Adding a "delete" privilege and a set of permission bits for what amounts to root, to get the four hexadecimal modes, isn't a huge change.)

      I used to write systems and apps code on 64-bit computers with graphical UIs, language and context-sensitive IDEs, no root superuser, and automatic versioning filesystems. But that was back in the 1980s, before the black ships came and the secret of hose gartering that never ravels was forgotten.

      So what 64-bit computers were those? (Presumably that means "64-bit address space"; "does 64-bit arithmetic in one instruction" is a lot less interesting.) System/38 and AS/400 had larger address spaces, but I think they had 48-bit address spaces until the PowerPC update. (I'm not talking about the 128-bit pointers, I'm talking about the address space available to the instructions that are executed by the machine rather than to the instructions translated into machine instructions.)

      I miss VMS vaxen sometimes.

      (Those, of course, weren't the 64-bit computers to which you were referring. OpenVMS Alphas were, but those didn't come out until the 1990's, and OpenVMS Itaniums are, but they didn't come out until even later. In any case, you've been talking about OS features, so VAX is irrelevant.)

    16. Re:The heydays ended ten years ago by Anonymous Coward · · Score: 0

      Congratulations, you are the blind man holding the trunk of the elephant. Those other blind men you are responding to are holding a leg or a tail or an ear.

    17. Re:The heydays ended ten years ago by Jonner · · Score: 1

      There's so much code in common between Unix and Unix-like operating systems today that the distinction really only matters to lawyers and marketdroids.

    18. Re:The heydays ended ten years ago by Dadoo · · Score: 1

      But what Unixes are still around? Tru64 is effectively dead, since HP bought Compaq; Solaris' future is questionable, since Oracle bought Sun; I've only even seen one HP/UX machine in the last decade, and we're only keeping that around for legal reasons. I'd like to say AIX is still going strong, but we just decommissioned our last AIX server a month ago, and we probably won't be going back to IBM.

      Pretty much all of our Unix servers have been replaced with Linux, and the main reason is that it runs on commodity hardware. All the other Unixes, pretty much require vendor lock-in - one of the best ways to increase the cost of running your data center.

      --
      Sit, Ubuntu, sit. Good dog.
    19. Re:The heydays ended ten years ago by Guy+Harris · · Score: 3, Informative

      Congratulations, you are the blind man holding the trunk of the elephant. Those other blind men you are responding to are holding a leg or a tail or an ear.

      Actually, my eyes work quite well, and can see that there are a pile of different UN*X systems out there, which are similar in a lot of ways (a lot of core APIs, for example) and different in a lot of ways (system administration quirks, for example). If you focus on the parts that are most different, they're all weird in their own ways, with Mac OS X not necessarily being any worse than others (hey, at least ifconfig works the way it's supposed to); if you focus on the parts that are most similar, they're all close enough to call them UN*X.

    20. Re:The heydays ended ten years ago by Guy+Harris · · Score: 1

      There's so much code in common between Unix and Unix-like operating systems today

      "Unix" can either refer to "the trademark and systems that have it" or to "the software released by AT&T". If you're referring to the latter, I'm not sure how much code is in common between, for example, AT&T Unix and a typical Linux distribution. Even if you're referring to the former, I'm not sure how much code is in common between, say, Solaris or AIX or HP-UX and a typical Linux distribution.

    21. Re:The heydays ended ten years ago by ChrisMaple · · Score: 1

      Multics also had hexadecimal access control: read, execute, write, append.

      --
      Contribute to civilization: ari.aynrand.org/donate
    22. Re:The heydays ended ten years ago by Guy+Harris · · Score: 1

      Multics also had hexadecimal access control: read, execute, write, append.

      But it didn't have "4 hexadecimal modes", it had ACLs - and, at least according to the 1975 Multics Programmer's Manual Reference Guide, they're read/execute/write/deny-everything for segments and status/modify/append/deny-everything for directories.

    23. Re:The heydays ended ten years ago by Anonymous Coward · · Score: 0

      I, sir, have a problem with your last line - it's incorrect.

      It should read, "Here's a nickel, go buy yourself a computer, kid."
      Please don't let that happen again...

    24. Re:The heydays ended ten years ago by Anonymous Coward · · Score: 0

      The outstanding rogue operating system now is Windows. They too have recognized that they are missing out by remaining completely non-compliant, and have begun incorporating various aspects of POSIX as add-on (SFU or SUA) and 3rd party (Cygwin) packages.

      No they haven't..

      For further evidence that SFU is also being removed, see Wikipedia and read it all -- don't skim, read it.

      Windows is not UNIX, Windows is not *IX, Windows is Windows. You either accept that or you don't, and there are many choices available to you in the case of the latter -- and none of those are Windows. And do not bring WINE into the discussion either. Thank you drive through.

      Footnote: captcha phrase was "reject". Indeed.

    25. Re:The heydays ended ten years ago by Anonymous Coward · · Score: 0

      >> Several OSes are UNIX, including Mac OS and Solaris.

      > Right, of course, I had *totally* forgotten that MacOS and Solaris were binary compatible. My bad.

      Neither is my PDP-11 (yes, I really have one)

    26. Re:The heydays ended ten years ago by Anonymous Coward · · Score: 0

      > Do you really consider Unix and Linux to be two separate things?

      Not sure if you mean "the same kind of thing" or "variants of the same thing"?

      Anyway, GNU is a Unix clone, a work-alike. It is a deliberately separate thing. RMS started it because he couldn't accept the terms of Unix licensing, and Linus started his project because he couldn't get real Unix for PC hardware. Minix didn't support the 386.

      So yes, "separate but equal" !

    27. Re:The heydays ended ten years ago by JWSmythe · · Score: 1

      I never said Windows is Unix. I said that they are trying to add parts. It's more of a token towards their ongoing extend, embrace, and extinguish methodology.

      Windows 8 hasn't been finalized. Heck, it's still pre-beta. You can't say that it *won't* have some sort of Unix-like compatibility. Even if it isn't available on day 1, it could be released later. Or as they say, it's a forward looking statement, and should not be used to predict future performance of the product.

      Cygwin has done a better job, but even that isn't perfect. And it never will be. As you said, Windows is not Unix.

      Windows is, and will remain, being the rogue OS, stubbornly remaining different, while everyone else cooperates towards a common future.

      We're now to the point where most people, like it or not, have more Unix devices than Windows devices.

      Scanning across my living room...

      2 Windows computers (for gaming)
      1 Dual boot laptop (Windows/Linux)
      1 Mac (Unix)
      3 Android tablets (Unix)
      2 Android phones (Unix)

      So the score just in this room is... 2.5 Windows, 6.5 Linux.

      We won't talk about my 4 old TiVo DVR's in the other room, or the stack of old Linux servers waiting to find a new home.

      --
      Serious? Seriousness is well above my pay grade.
    28. Re:The heydays ended ten years ago by dbIII · · Score: 1

      Once you've learned how one Unix-like environment works, you can use them all.

      http://www.youtube.com/watch?v=dFUlAQZB9Ng

    29. Re:The heydays ended ten years ago by Carewolf · · Score: 1

      Windows has had a POSIX layer since the earliest NT versions, and still do. It is not used much, and is a separate system API from win32 and all the other Windows APIs they seem to pump out and dump every few years..

    30. Re:The heydays ended ten years ago by JWSmythe · · Score: 1

          It would have been more impressive if it didn't look like a C64 generated the ubercool graphic on the screen, and she had at least said something more tech than "Unix" and "find the file".. If she was actually using find and file, I would have been at least a little impressed. find and grep would have probably at least helped. :) At very least "oh look, the password is taped to the monitor" would be more believable than in the middle of a dinosaur attack the console was still logged in and unlocked.

      --
      Serious? Seriousness is well above my pay grade.
    31. Re:The heydays ended ten years ago by unixisc · · Score: 1

      It ain't just those 2 things, but also the Posix compliance as well as the API's. While the differences are there, the fact remains that Linux, BSD & Minix all follow OS principles that were there in Unix, but not in DOS or Windows NT - be it the various shell commands, the shells themselves and API's. So while Linux, BSD & Minix may not have gone through the certification process that an OS goes through before it is certified as Unix, fact remains that anyone familiar with any one could probably work w/ or use the other, in a way they couldn't w/ things like VMS, DOS, OS/2, et al.

    32. Re:The heydays ended ten years ago by Guy+Harris · · Score: 1

      It ain't just those 2 things, but also the Posix compliance as well as the API's.

      Yes, as I've noted several times when pointing out that, whilst Linux etc. might not be "Unixes" in the trademark sense, they're most definitely Un*xes in the "how you deal with them in real life" sense.

      However, the point remains that, unless the "code in common" refers to software running *atop* those OSes rather than code *in* those OSes, there's not a huge amount of code in common between an AT&T-derived Unix and Linux, so it's not the "code in common" that makes Linux a Un*x.

    33. Re:The heydays ended ten years ago by cthulhu11 · · Score: 1
      I too roll my eyes and sigh when I see "Unix" and "Linux" portrayed as two wholly different things. Trademarks aside, any real-world rational use includes the latter as an instance of the former, much more so than the madness that was Apollo's Aegis/DomainOS, but I digress ...

      Linux is better, because it has capabilities.

      Eg. a single, integrated utility for listing and managing disks, including their models, serial numbers, controller/target numbers, partition tables, defect lists, etc? Oh, wait, that's Solaris. Linux has a handful of lame fdisk utilities, some of which work within their limited scope, and some of which don't (yes, cfdisk, I'm talking to YOU). If you have an LSI HBA you can do some things with lsiutil or megacli, if you can manage to find them and not go insane trying to figure out their syntax -- it's a sad day when the most useful document for something is written by DELL. Oh, you have an HP HBA? Use hpacucli. Oh, you have an Adaptec HBA? 1) My sympathies 2) Good luck finding arcconf or whatever. Have some other HBA? Sucks to be you, all you get to know is that the kernel calls disks sda, sdb, sdc, etc. and you have no way of knowing which is on what controller at what target, which is SERIOUS fun when you have to locate a specific disk to repair or upgrade. Oh, you're talking about mii-tool and ethtool, two utilities for the same thing, except that one of them doesn't understand GigE interfaces and erroneously reports them as 100Mbit, causing you to burn a day trying to figure out what's going on? And as someone else alluded to, WTF is up with the goofy-ass ifconfig? Oh, I just realized that you're talking about the badass modern filesystem used by Linux systems, which maxes out at 16TB and is a separate layer on top of the lame-ass volume manager, which is in turn a separate layer on top of the lame MD system for RAID. It's sooooo nice to have three layers of stuff to build and destroy rather than the annoying integration, flexibility and downright awesome-on-a-stick that is ZFS.

      I miss VMS vaxen sometimes.

      "Vaxen"? Seriously? Are you Nomad?

    34. Re:The heydays ended ten years ago by lars_stefan_axelsson · · Score: 1

      Linux is Unix

      Indeed. No less than Doug McIlroy thinks so. (Google his name + Linux). He should know. And even if he didn't, he has the credentials to proclaim it so. :-)

      --
      Stefan Axelsson
  6. The most intelligent OS I've ever seen by ackthpt · · Score: 0

    Sure wish Microsoft, who with the hindsight of Xenix, had adopted more *ix practices in Windows. I know some are there, but buried. Windows is such a pile of muck in a darkened room and when I first had my hands on an *ix system I fell in love with the simplicity and flexibility of it. Then there was Linux - build according to your needs, which utterly blew my mind. How long until we finally say Good-bye to non-*ix system architecture?

    --

    A feeling of having made the same mistake before: Deja Foobar
    1. Re:The most intelligent OS I've ever seen by jeremiahstanley · · Score: 4, Insightful

      Yes, the camel surely looks elegant in the desert. But then again, fish don't climb trees.

      Just because something works well in one area doesn't mean that it will function well outside of that area. This is why there will always be "other methods" for operating systems.

    2. Re:The most intelligent OS I've ever seen by ackthpt · · Score: 4, Informative

      Yes, the camel surely looks elegant in the desert. But then again, fish don't climb trees.

      Just because something works well in one area doesn't mean that it will function well outside of that area. This is why there will always be "other methods" for operating systems.

      Windows is such an incredibly fragile system - all eggs in one basket. While it made sense for mass sall of PCs with a single disk, by feat it left the programs, work, operating system, registry, swap space, all on one disk. You can choose to save your work done in various suites on other drives, but they are still fooling around with Drive C:, D:, E: etc. If I need to reinstall the OS I end up with such a massive corruption of drivers I'm almost better off starting from scratch, but I'd lose all my installed programs, because Microsoft likes to keep them all in Program Files on the C: drive, where the OS resides. I can move my memory swap to another physical drive, to relieve some I/O burden, but it's not well known how to do this. Having application, operating system files, swap file and work files all on one disk is such a horrible idea, particularly without even the benefit of partitions (to protect some files or installed applications during a re-install)

      I configured my first Linux box to have a tidy spot for the OS and its sources, not too much bigger than necessary (safety factor of 2). Put swap file on its own partition and installed all applications on a separate physical drive, with workspace for each on separate partitions. Flexible. I can change my harddisk configuration with a minimum of fuss. Try that with Windows.

      --

      A feeling of having made the same mistake before: Deja Foobar
    3. Re:The most intelligent OS I've ever seen by jedidiah · · Score: 1

      Your comment would be more convincing if Unix weren't infact running everywhere and doing a better job at it.

      Microsoft sandbagged for a long time. The users suffered for it and a lot of needless extra costs were incurred because of it.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    4. Re:The most intelligent OS I've ever seen by Anonymous Coward · · Score: 1

      Don't worry, Ploettering and his merry band of audio-saboteurs are about to fuck that up too.

      Last thing I heard from them wrt their latest concoction - "systemd" - was that configurations with more than one partition, specifically a separate /usr was "unsupported" and "not something that had a place in a modern computer."

      Why do what these deluded jackasses have to say carry so much weight?

    5. Re:The most intelligent OS I've ever seen by BitZtream · · Score: 0

      Your whole first paragraph can be summed up with 'I don't know how to use windows, won't bother to google for solutions I'm looking for, and don't even understand why I want to do this things, but I'm going to bitch about it like its Microsoft's fault I'm ignorant of how Windows works'

      I configured my first Linux box to have a tidy spot for the OS and its sources, not too much bigger than necessary (safety factor of 2). Put swap file on its own partition and installed all applications on a separate physical drive, with workspace for each on separate partitions. Flexible. I can change my harddisk configuration with a minimum of fuss.

      Bullshit.

      I have no doubt you can change your configuration, but you clearly spent too much time deciding how to layout your first Linux box. Typical of someone doesn't something because they saw someone else do it, not because they understand why to do it.

      You're bragging about how bad ass you are, yet you're too stupid to realize that you put a metric fuckton of silly effort into a problem thats unlikely to effect most people as they'll probably replace the machine before a hard drive issue or need to reinstall occurs. See most people aren't like you and don't fuck their OS up so often that they plan on how easy its going to be to reinstall.

      MOST people have better things to do then dick around with a PC all day long to make it uber perfect when all they are going to do is spend 15 minutes using it to browse facebook and check email. You're the kind of guy who brings a 55 ton bull dozer to your friends house to help him dig a hole for his new mailbox.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    6. Re:The most intelligent OS I've ever seen by jedidiah · · Score: 2

      > I have no doubt you can change your configuration, but you clearly spent too much time deciding how to layout your first Linux box.

      Actually, that's the beauty of Unix. I don't have to be married to that initial layout. It is trivial for me to split and merge things pretty much anywhere and at will.

      So, I can take the Windows-esque Ubuntu default and tweak it to my hearts content later.

      Now I think that being able to blow away my boot partition and not touch "my data" is a really cool and useful thing. I can also preserve "apps" in much the same way in a manner that's similar to MacOS. If people with no taste don't see this, then that's their loss.

      Even "Grannies" have personal data they are interested in protecting these days.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    7. Re:The most intelligent OS I've ever seen by Anonymous Coward · · Score: 0

      Windows allows you to mount a filesystem pretty much just as the unixoid systems do (maybe slightly more confusing due to the fs root usually being associated with a certain physical drive/partition but that's just naming conventions...).

      http://support.microsoft.com/ph/14019

      However, even tech-literate people seem to be largely unaware of this feature.

    8. Re:The most intelligent OS I've ever seen by MrLizardo · · Score: 1

      Ah, so what you're getting at, is that while Unix-like OSes are well suited for multi-user text processing, workstations, desktops, servers, super computers, cell phones, and embedded industrial computers with realtime processing requirements they might not necessarily work everywhere?

      --
      ^I'm with stupid.^
    9. Re:The most intelligent OS I've ever seen by jedidiah · · Score: 1

      The interfaces in Windows generally expose you to the old way of doing things.

      Legacy issues are always a tough problem. That's why it's best to avoid them, or at least fix them sooner rather than later.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    10. Re:The most intelligent OS I've ever seen by JWSmythe · · Score: 1

      Being that virtually everyone has dropped the idea of building their own OS, I expect we'll see that Unix-like operating systems will be the only choice in a few years, and most likely Linux will remain on top of that. Despite it not hitting the desktop like everyone had hoped, it's found it's niche in everything that needs processing power. Since people have become comfortable with Linux (Android) on their phones and tablets, I would see real expansion of that to desktops sometime in the next few years.

      --
      Serious? Seriousness is well above my pay grade.
    11. Re:The most intelligent OS I've ever seen by Anonymous Coward · · Score: 0

      Actually, it's not systemd's fault: http://www.freedesktop.org/wiki/Software/systemd/separate-usr-is-broken

    12. Re:The most intelligent OS I've ever seen by SnarfQuest · · Score: 1

      The problem with MicroSoft being more *nix like, is that leaves a migration path away from MicroSoft.

      --
      Who would win this election: Andrew Weiner vs Andrew Weiner's weiner.
    13. Re:The most intelligent OS I've ever seen by ackthpt · · Score: 2

      I have no doubt you can change your configuration, but you clearly spent too much time deciding how to layout your first Linux box.

      I was sys admin on a few mainframes before Linux even existed. Picked up the wisdom of how those systems were configured and why. When I got my distro disks I spent about 30 minutes working out how I wanted it configured. Really wasn't something most newbs would understand, even with *ix builds/installs. Certainly not in any way close to the default, out of the box set up for Windows on any retailed or business configured PC I've ever seen - I'd wager 99.9% of all Windows PCs, to the present have massive I/O bottlenecks (not to overlook the pagefile is usually highly fragmented as process calls the filesystem to allocate and free up sectors rather than being created once of contiguous sectors, geez) and recovery issues, which happen more often than you are acknowledging, because many worms/viruses/trojans can only be fully recovered from with a fresh install. To read your words is to believe nobody has had much of a problem with malware and it shouldn't be an issue, so don't bother with firewalls or antivirus software.

      --

      A feeling of having made the same mistake before: Deja Foobar
    14. Re:The most intelligent OS I've ever seen by ackthpt · · Score: 1

      Your comment would be more convincing if Unix weren't infact running everywhere and doing a better job at it.

      Microsoft sandbagged for a long time. The users suffered for it and a lot of needless extra costs were incurred because of it.

      Microsoft catered to cookie-cutter installs. Most are express installs, no thought to performance, just a quick stall by whatever tech team is doing it and get it out the door. Good practices require thought, thoughtful configurations require training on the hows and whys, whereas drones are cheap to employ. Microsoft's approach was along the line of - "Just do it this way, nobody really cares or is likely to be impacted by our one-size-fits-all design". *ix, particularly Linux brought the ability to configure your desktop like a mainframe and take advantage of multiple drives for performance reasons.

      --

      A feeling of having made the same mistake before: Deja Foobar
    15. Re:The most intelligent OS I've ever seen by Locutus · · Score: 1

      Microsoft executives learned long ago that once they had the monopoly on desktop OS's and therefore the developers, if they made their system "unique" enough it would be very difficult and expensive to make Windows programs run on other operating systems. You don't get an elegant design from that business model and you never will.

      Remember, the threat of cross platform development was the reason Microsoft went against OOP and build a layered interface based system. Abstraction was a threat to keeping developers tied to their APIs. They were quite aggressive at putting the cross platform C++ frameworks vendors out of business.

      Just about the time Smalltalk was finally picking up steam along came Java and it's piggy back on the Internet( ie buzz ). But it was not long before that cross platform system was declared a threat to Windows and Microsoft went and did their own version even though they signed documents and licenses saying they would not. It took years for Sun to settle that and by then Microsoft had gutted Borland of it's top language engineers and directed them to come up with a competitor to Java and patented the stuff developers would find useful. They paid a "standards" org to declare part of their system an industry standard but you couldn't do much of any thing cross platform on what was even hinted as being open.

      We'll never see Microsoft act anything like what it would have taken for them to adopt *ix practices because they exist only because they have a monopoly and they build everything to tightly tie developers to their platform. So if the current trend toward handhelds and portable devices continues it'll still be a very long time before Microsoft becomes a footnote and therefore it'll still be a very long time before those non-*ix systems such as theirs goes away. And remember, they have lots of cash to buy their way into lots of places. Over a billion for Nokia and for what? Windows Phone 7 is still with low single digit market share and then they'll be talking about Windows 8 and that'll be quite bloated compared to the Windows CE based WP7. But they've got like $50 billion in cash so they have enough for a very long time.

      LoB

      --
      "Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
    16. Re:The most intelligent OS I've ever seen by sjames · · Score: 1

      But then, a creature composed of poodle legs on the left, horse legs on the right, a ducks bill, a camel hump, giraffe's neck, and a peacock tail with gills (and so aquatic) will never be an elegant creature in any environment.

  7. Re:No support, no bug fixes by Anonymous Coward · · Score: 4, Insightful

    "in 2008 Microsoft confirmed a vulnerability in Internet Explorer, which affected some versions that were released in 2001"
    i rest my case

  8. I remember ... by versimilidude · · Score: 5, Interesting

    I remember the first time I saw Unix, in 1976. The first step in installing it was to compile the C compiler (supplied IIRC in PDP-11 assembler) and then compile the kernal, and then the shell and all the utilities. You had an option as to whether you wanted to put the man pages online since they took up a significant (in those days) amount of disk space. Make was not yet released by AT&T so this was all done either by typing at the command line or (once the shell was running) from shell scripts.

    1. Re:I remember ... by Guy+Harris · · Score: 4, Interesting

      I remember the first time I saw Unix, in 1976. The first step in installing it was to compile the C compiler (supplied IIRC in PDP-11 assembler)

      As I remember, and as the "SETTING UP UNIX - Sixth Edition" document says (see the start *roff document in this V6 documentation tarball - yes, I know, tarballs are an anachronism here :-)), V6 came in a binary distribution that you read from a 9-track tape onto a disk:

      If you are set up to do it, it might be a good idea immediately to make a copy of the disk or tape to guard against disaster. The tape contains 12100 512-byte records followed by a single file mark; only the first 4000 512-byte blocks on the disk are significant.

      The system as distributed corresponds to three fairly full RK packs. The first contains the binary version of all programs, and the source for the operating system itself; the second contains all remaining source programs; the third contains manuals intended to be printed using the formatting programs roff or nroff. The `binary' disk is enough to run the system, but you will almost certainly want to modify some source programs.

      You didn't have to recompile anything (at least not if you had more than 64KB; I had to do some hackery with the assembler to get it to run on a 64KB machine, as there wasn't enough memory to run the C compiler - I had to stub out the pipe code with an assembler-language replacement for pipe.c, and then recompile the kernel with a smaller buffer cache and the regular pipe code). Most users probably either had to or had good reasons to recompile the kernel (different peripherals, more memory for the buffer cache - or less memory in my case, so I had to shrink it from 8 whole disk blocks to 6 - etc.), and if you weren't in the US eastern time zone or didn't have daylight savings time you had to change ctime.c, or whatever it was called, in the C library for your time zone, recompile the C library, and then rebuild all utilities with the new C library (no Olson code and database, no shared libraries, no environment variables so no TZ environment variable).

    2. Re:I remember ... by Thud457 · · Score: 1

      do I smell a whiff of Gentoo in here?

      --

      the preceding comment is my own and in no way reflects the opinion of the Joint Chiefs of Staff

    3. Re:I remember ... by c0d3g33k · · Score: 1

      Gentoo sounds much less painful, since it's nicely automated. But probably less fun since you don't generally need to modify sources to get things working the way they need to.

    4. Re:I remember ... by Anonymous Coward · · Score: 0

      you got it backwards dude

    5. Re:I remember ... by dargaud · · Score: 1

      The first step in installing it was to compile the C compiler (supplied IIRC in PDP-11 assembler) and then compile the kernal, and then the shell and all the utilities.

      I program embedded systems, and to get Linux on them we still proceed the exact same way... OK, there are powerful scripts such as BuildRoot that can do everything in 2 commands, but still...

      --
      Non-Linux Penguins ?
  9. going around patents and copyrights by roman_mir · · Score: 0

    note that the entire history of Unix is permeated with history of lawyer intervention and lawsuits, all thanks to the copyright and patent laws that exist because of government and that are enforced by government agencies and courts. This is just one more reason to abolish all patents and copyrights.

    1. Re:going around patents and copyrights by Anonymous Coward · · Score: 0

      permeate me roman baby!

    2. Re:going around patents and copyrights by sjames · · Score: 1

      It figures. A few engineers tricked the suits into letting them create something great and then a community around it, so the suits then spent the next 30 years trying to get their claws on it and trying to squash the community.

  10. Re:No support, no bug fixes by CmdrPony · · Score: 1

    Are you saying all gamers are idiots?

  11. Not directly related to telephones? by cashman73 · · Score: 5, Insightful
    Since AT&T was restricted from selling products not directly related to telephones or telecommunications, they released it to anyone who asked for a nominal license fee.

    It's interesting how AT&T couldn't support it for this reason, because today, UNIX is at the heart of both iOS and Android, which run some of today's most popular telephones.

    1. Re:Not directly related to telephones? by ackthpt · · Score: 5, Insightful

      Since AT&T was restricted from selling products not directly related to telephones or telecommunications, they released it to anyone who asked for a nominal license fee.

      It's interesting how AT&T couldn't support it for this reason, because today, UNIX is at the heart of both iOS and Android, which run some of today's most popular telephones.

      Also at the heart of OS X. One of the smartest moves by Apple and Jobs, replacing the hideous old Mac OS with something built on Mach and borrowing heavily from BSD. Apple made the painful leap and it paid off handsomely.

      --

      A feeling of having made the same mistake before: Deja Foobar
    2. Re:Not directly related to telephones? by Desler · · Score: 1

      Except that's not all that interesting. This just in: technology used in different areas than originally designed for. zOMG!!!

    3. Re:Not directly related to telephones? by jonnythan · · Score: 1

      I think he's commenting on the fact that AT&T wasn't allowed to sell it because it wasn't related to telephones, and now it's at the core of today's most popular telephones.

    4. Re:Not directly related to telephones? by AB3A · · Score: 3, Insightful

      Yes, but imagine trying to argue this to Judge Greene during the breakup of AT&T in the early 1980s.

      AT&T stayed out of that fray because there was no way in hell that they could have argued that this was a possible outcome based upon what was going on with the state of the art at the time.

      --
      Nearly fifty percent of all graduates come from the bottom half of the class!
    5. Re:Not directly related to telephones? by MightyMartian · · Score: 2

      I thought it was a Mach kernel and a BSD userland. How exactly that's quintessentially different from me installed Cygwin on my Windows machine and calling it a Unix machine is beyond me.

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
    6. Re:Not directly related to telephones? by Anonymous Coward · · Score: 0

      Well, OSX (at least 10.5 and 10.6) is certified Unix 03. It's unclear about Lion and whether Apple intends to have it certified or not.

    7. Re:Not directly related to telephones? by Anonymous Coward · · Score: 0

      You're a fucking ignorant idiot. The tie-in between BSD and Mach for Darwin is far more coupled then cygwin on Windows. You are completely out of your expertise if you believe there is any reasonable comparison that can be drawn. Mac OS X is not simply taking Mach as some huge mess as a given (like Windows) and layering BSD on top of it. The Mach/BSD kernel of Mac OSX as a hybrid is specifically built for the purpose. fork doesn't take an eternity on Mac OSX, for instance.

      Even if cygwin somehow managed to meet SUSv3, the appalling performance of some of the most important syscalls mean it will never be even close to a true UNIX. (Contrast this to Linux which "isn't UNIX" either, but makes a pretty damn good attempt at fooling most reasonable hackers).

      Mac OSX is Unix and Unix-like, end of story. Windows is not, and cygwin doesn't change that.

    8. Re:Not directly related to telephones? by Darinbob · · Score: 1

      Actually later on AT&T used computers in their telecommunications routers at which point they were directly related and integral to the phone system.

    9. Re:Not directly related to telephones? by Darinbob · · Score: 1

      Windows had to do this leap from dumb micro computer OS to a real OS also but it was a longer period of pain because they were too hesitant to break compatibility so the conversion happened piecemeal over time.

    10. Re:Not directly related to telephones? by Anonymous Coward · · Score: 1

      Since AT&T was restricted from selling products not directly related to telephones or telecommunications, they released it to anyone who asked for a nominal license fee.

      It's interesting how AT&T couldn't support it for this reason, because today, UNIX is at the heart of both iOS and Android, which run some of today's most popular telephones.

      This all took place before the break-up of Ma Bell into the baby Bells. At the time, AT&T was a regulated monopoly. The transistor was basically given away to the public for the same reason. I've forgotten the details, but their arrangement with the federal government was structured in such a way that it was in AT&T's own best interest to have large investments in research and R-D.

      Dividends were linked to gross income, while profits were limited by gross income minus capital investment? It was something like that anyway.

      While this sort of thing drives neo-cons nuts, it was a very good arrangement all-around. AT&T had lots of money for infrastructure upgrades and research (leading to product development for themselves) while at the same time the research spending also benefited the rest of the country with things like patent-free transistors. They also had a large, stable, dividend which kept the investors happy.

    11. Re:Not directly related to telephones? by cduffy · · Score: 1

      I thought it was a Mach kernel and a BSD userland. How exactly that's quintessentially different from me installed Cygwin on my Windows machine and calling it a Unix machine is beyond me.

      Mach is a microkernel, not a kernel -- that is, it's a lightweight component you build your actual kernel on top of. And that actual kernel provides POSIX interfaces.

      Any clearer?

    12. Re:Not directly related to telephones? by Guy+Harris · · Score: 2

      I thought it was a Mach kernel and a BSD userland.

      It's a kernel that consists of Mach plus BSD code plus IOKit, with the BSD code modified to let Mach handle platform-specific stuff, the lower levels of process/thread management, and paging and let IOKit handle talking to hardware. Except when doing stuff such as sending Mach messages, userland talks to the BSD code for system calls - process management, address-space management, file system operations, and network operations all involve system calls to the BSD layer even if the system call in question makes a lot of calls to the Mach layer (I'm not sure to what extent pthread operations go to Mach system calls arther than BSD system calls).

      How exactly that's quintessentially different from me installed Cygwin on my Windows machine and calling it a Unix machine is beyond me.

      It's because Cygwin sits atop the OS's main native API, Win32, and emulates UN*X as best it can, while libc, err, umm, libSystem on Mac OS X implements the lowest userland layer of the UN*X API and, when it needs to talk to the kernel, mostly does it with UN*X system calls (some places end up doing Mach messaging to processes such as DirectoryService/opendirectoryd or mDNSResponder), but there's no "native" API (either in the sense of Win32 on NT or the native NT API on NT) atop which the UN*X APIs are implemented. The only Mach APIs implemented for applications are things such as mach_msg() and stuff atop it such as MIG, but that's not really any "non-UNIXy" than, say, doors in Solaris.

    13. Re:Not directly related to telephones? by Guy+Harris · · Score: 1

      Well, OSX (at least 10.5 and 10.6) is certified Unix 03.

      And z/OS is certified Unix 95 but it's a layer atop an OS whose native API isn't UN*X, so "it's certifioed Unix 03" isn't a sufficient refutation. ("There is no "native API" atop which Mac OS X's UNIX API is implemented" is a sufficient refutation.)

    14. Re:Not directly related to telephones? by Guy+Harris · · Score: 1

      (Contrast this to Linux which "isn't UNIX" either, but makes a pretty damn good attempt at fooling most reasonable hackers).

      And, as is the case on Mac OS X, but as isn't the case with Cygwin, the UN*X API is the native API for Linux; it's not an attempt at implementing a UN*X API atop an OS whose "native" API isn't UN*X.

    15. Re:Not directly related to telephones? by Guy+Harris · · Score: 1

      Windows had to do this leap from dumb micro computer OS to a real OS also but it was a longer period of pain because they were too hesitant to break compatibility so the conversion happened piecemeal over time.

      Presumably you mean "piecemeal" in the sense that it took Windows XP to kick the old "Windows OT" code base to the curb for mainstream users; it's not as if they replaced bits and pieces of "Windows OT" piecemeal from release to release - Windows NT 3.1 wasn't a "dumb micro computer OS", but it also wasn't the OS that shipped on most Windows PC that shipped at the time.

    16. Re:Not directly related to telephones? by Darinbob · · Score: 1

      Ya, I'm talking home computers. For a long time people just didn't put on good OS because first the CPUs were very limited and second they assumed people didn't need anything better just to run one app at a time. Corporate users did need more and did tend to have beefier machines so NT was oriented to them.

    17. Re:Not directly related to telephones? by Anonymous Coward · · Score: 0

      Unix is just a certification. Any OS that can pay to write the test and pass it is Unix. OS X has.

    18. Re:Not directly related to telephones? by Anonymous Coward · · Score: 0

      Are you kidding me? Installing Cygwin on an NT Kernel (NOT Win32) would be a Unix too. In fact, NT4 has a crippled subsystem in it.

  12. Read some of the original Bell System docs, too by Myself · · Score: 5, Informative

    Several issues of the Bell System Technical Journal tell the story of UNIX, in their own words. This one in particular is interesting.

    1. Re:Read some of the original Bell System docs, too by Myself · · Score: 5, Informative

      Here's the index of the July-August 1978 issue where the whole series of articles appears. Better format than the search above.

    2. Re:Read some of the original Bell System docs, too by kiwimate · · Score: 1

      Thanks! Fascinating reading. Like this snippet:

      UNIX systems generally have a good, though not impeccable, record for software reliability. The typical period between software crashes (depending somewhat on how much tinkering with the system has been going on recently) is well over a fortnight of continuous operation.

      (The term "fortnight" is not widely used in the U.S., so I'll clarify that a fortnight is two weeks.)

    3. Re:Read some of the original Bell System docs, too by kiwimate · · Score: 1

      Cardinal sin of replying to myself, but this one is too good not to post (in the spirit of the apochryphal "640K should be enough for anyone"). From page 1962:

      ...most installations do not use groups at all (all users are in the same group), and even those that do would be happy to have more possible user IDs and fewer group-IDs. (Older versions of the system had only 256 of each; the current system has 65536, however, which should be enough.)

    4. Re:Read some of the original Bell System docs, too by Myself · · Score: 1

      You already replied to Myself two posts up...

    5. Re:Read some of the original Bell System docs, too by tbuskey · · Score: 1

      I have that issue. Also the 1984 issue that focused on Unix. I got them around 1990.

  13. Re:No support, no bug fixes by icebraining · · Score: 1, Insightful

    No, some gamers don't prefer Windows, they just boot it as a second OS to play.

  14. Re:No support, no bug fixes by darkonc · · Score: 5, Insightful

    Well, if you read the Microsoft EULA, you'll notice that they don't promise bug fixes either. It just isn't advertised that way (although they definitely do supply advertising)... and sometimes the support just consists of "yes, I think that's unfortunate, too".

    --
    Sometimes boldness is in fashion. Sometimes only the brave will be bold.
  15. Re:No support, no bug fixes by CmdrPony · · Score: 1

    I also prefer it as desktop OS, and not just for games. I use Linux on servers because that's where it shines best, but Linux in general either doesn't have the desktop programs I want or they're poor options. Like for example I love PHPEdit for editing php files, like I do with Visual Studio for .NET programs. Linux lacks compared to those, especially if you want to develop with C# or any other sane higher level language or for Windows. Another case is photo editing. There's both Photoshop and Paint Shop Pro along with several video editing programs and website designing programs like Artisteer. Those don't support Linux and there just isn't anything equivalent. Linux totally lacks on software catalog side of things. There just isn't any programs available.

  16. So Windows got ahead because of regulations? by mc6809e · · Score: 1

    Makes me wonder whether or not we'd be using as many Windows machines had the government allowed AT&T to sell and market Unix.

    1. Re:So Windows got ahead because of regulations? by BitterOak · · Score: 2

      Makes me wonder whether or not we'd be using as many Windows machines had the government allowed AT&T to sell and market Unix.

      No. Windows got ahead because it was designed primarily as a platform for running high level applications, such as word processors and spreadsheets, by single users on microcomputers rather than being designed as a multi-user, general purpose platform for programmers and other users who could invest a little more time in learning their way around the operating system. Also, Windows was backwards compatible with an operating system (DOS) which ran on older computers that did not have the hardware resources to support a full, multi-user operating system (x86 processors before the 80386 did not have the memory protection features necessary for a multi-user operating system). Microsoft got in early with DOS on the PCs, and kept their lead going forward through backward compatibility and name recognition.

      --
      If I can be modded down for being a troll, can I be modded up for being an orc, or a balrog?
    2. Re:So Windows got ahead because of regulations? by TheRaven64 · · Score: 1

      Windows? Windows didn't even exist back then. The competitor on the low end was CP/M. A few years later MS introduced their CP/M clone, DOS. Windows came about a decade later. No one used UNIX on personal computers because it was only lightweight by mainframe / minicomputer standards. Most personal computer didn't have protected memory and multitasking was a completely pointless operating system feature on a system that barely had enough RAM for one program.

      Window got ahead because DOS was already entrenched and it provided backwards compatibility. Early versions of Windows ran on DOS, so in the worst case you could always quit Windows and run the DOS program outside, but most business apps ran happily inside the Windows DOS box. Most people installed Windows 3.0 and earlier as a way to run multiple DOS programs at once.

      --
      I am TheRaven on Soylent News
    3. Re:So Windows got ahead because of regulations? by jedidiah · · Score: 1

      Windows was born ahead.

      It was born ahead, because it was the successor to DOS.

      DOS was successful because of it's association with the previous computing monopoly, namely IBM.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    4. Re:So Windows got ahead because of regulations? by swb · · Score: 1

      Most personal computer didn't have protected memory and multitasking was a completely pointless operating system feature on a system that barely had enough RAM for one program. .

      To read the descriptions of the early systems UNIX ran on, 640k sounds like a lot of memory, especially when combined with one of those beefy 10 mb early hard disks.

      Or was the 8086 really that crippled? I seem to remember some kind of UNIX-alike OS running on it, but maybe it was on better 80286 CPUs or even 386s.

    5. Re:So Windows got ahead because of regulations? by 0123456 · · Score: 1

      Windows got ahead because it was designed primarily as a platform for running high level applications, such as word processors and spreadsheets, by single users on microcomputers rather than being designed as a multi-user, general purpose platform for programmers and other users who could invest a little more time in learning their way around the operating system.

      Windows got ahead because a Sun Workstation cost 10x as much. Windows 3.x was a joke compared to what people were doing on Unix workstations at the time, but few people could afford to buy a Sun for their home.

      Windows 95 was the first version that was better than SunOS from a user perspective (obviously it was a pile of crap internally).

    6. Re:So Windows got ahead because of regulations? by jgrahn · · Score: 1

      Windows got ahead because a Sun Workstation cost 10x as much.

      No, it got ahead because a mass psychosis told people there was nothing else. In the early 1990s, nothing but the PC and the Mac existed in the public mind. The C64, Atari ST and Commodore-Amiga didn't exist (although every other kid had one). The Sun machines didn't exist if you weren't into some very specific niches -- not because they weren't suited there, but because of the PC psychosis.

      At that time I was an embittered Amiga user. We never got mentioned in the press or on TV, even though the Amiga at the time was both cheaper and more powerful that the PC+Windows 3.x combo.

      There seemed to have been an narrow opening in the mid-1980s where people experimented with proprietary Unix on PC hardware. Even Commodore made one for the Amiga. As far as I can tell that window closed quickly -- most of those systems sucked, and I suppose they also suffered from the then-rampant Unix fragmentation. SCO Unix was the only one people are likely to remember.

    7. Re:So Windows got ahead because of regulations? by riverat1 · · Score: 1

      From TFA (emphasis added):

      The first edition of Unix let programmers call 34 different low-level routines built into the operating system. It's a testament to the system's enduring nature that nearly all of these system calls are still available—and still heavily used—on modern Unix and Linux systems four decades on. For its time, first-edition Unix provided a remarkably powerful environment for software development. Yet it contained just 4200 lines of code at its heart and occupied a measly 16 KB of main memory when it ran.

    8. Re:So Windows got ahead because of regulations? by tbuskey · · Score: 1

      Minix ran on an 8086/8088 with 512k ram. It used the same 64k I&D model as PDP-11s

    9. Re:So Windows got ahead because of regulations? by TheRaven64 · · Score: 1
      640KB was a lot of memory. The first IBM PCs had 16-256KB of RAM and were competing against 8-bit computers with 1-64KB. These were the machines that CP/M ran on. UNIX, needing 16KB for just the kernel, was massive in comparison - it was only small in comparison to minicomputer / mainframe operating systems. CP/M ran on machines with 16KB of RAM, with most of that available to the program. The operating system itself could run from ROM. DOS 1.0 was a cheap CP/M clone, running on IBM PCs with 16KB of RAM. It was easy to port CP/M programs to DOS, so it started with a lot of applications (including VisiCalc, the first killer app).

      The later PCs, with 640KB of RAM were able to run MINIX or Xenix, but they were also able to run Windows 3.0, so there was a choice between Windows 3.0 on top of DOS, which let you run GUI applications and all of your legacy DOS applications, or UNIX without any legacy compatibility and without most of the advantages of a real operating system since the hardware didn't support protected memory.

      The 286 had protected memory, but via a segmentation system. The 386 was the first x86 chip to be powerful enough for a real operating system with protected memory and preemptive multitasking, but by the time it was introduced there was so much legacy DOS code floating around that any operating system that couldn't run DOS applications was dead in the water.

      By this time, UNIX was mired down in the AT&T vs UCB lawsuit and also competing with OS/2 and Windows NT, both of which had protected memory, preemptive multitasking, and the ability to run both DOS and Windows 3.0 programs.

      --
      I am TheRaven on Soylent News
  17. Re:No support, no bug fixes by Anonymous Coward · · Score: 0

    No, just the ones who don't know how to install and use wine.

  18. user experience by Anonymous Coward · · Score: 0

    I've worked with Unix twice. The first time in 1996 and the second time from November 2011 to June of this year. It is as user unfriendly now as it was in 1996.

    1. Re:user experience by MechanicJay · · Score: 1

      I've worked with windows -- first in 1996 and most recently December 2011. It is as user unfriendly now as it was in 1996.

    2. Re:user experience by tgeek · · Score: 1

      Yeah, but what other OS would allow you to time travel backwards? From November 2011 to June 2011 . . .

    3. Re:user experience by DrSkwid · · Score: 5, Funny

      Unix is perfectly user friendly, it's just careful who it is friends with.

      --
      There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
    4. Re:user experience by Anonymous Coward · · Score: 0

      I've worked with Unix twice. The first time in 1996 and the second time from November 2011 to June of this year. It is as user unfriendly now as it was in 1996.

      Define UNIX.

      Mac OS X is UNIX, it is known to be very user friendly.

      Ubuntu is Unix:y and some flavours of Ubuntu are pretty user friendly (but the latest main flavour isn't, like MS Windows, its UI is designed by people that haven't designed a system for their own use, but for what they think would be good for other people, people they know nothing about). There are many other distributions of Linux that are very user friendly, for different kinds of users.

      iOS and Android are UNIX:y on a low level, although not with a traditional set of UNIX user tools.

      My moms TV run on Linux, her cable TV box is BSD. My camera run on BSD. My brother have a stereo player that run on Linux (but I've never told him that, because he is working for companies with MS based products and is very anti-Linux). All the people I know with internet access use home network boxes that run on either Linux or BSD. All pretty user friendly. Almost half of all the electrical appliances today run some kind of unix-like OS (the other "almost half" run that Japanese OS that nobody ever heard of and I keep forgetting the name of). Compare that to using a Windows mobile phone or some other applience that run on Windows (shudder). MS Windows is installed on only a fraction of the "computers" that UNIX:y OSes are, but you always know when you use Windows, because it is a pain in the ass, while you don't even know when you use Unix:y OSes, because they are so user friendly and runs so smooth.

    5. Re:user experience by Anonymous Coward · · Score: 0

      Mac OS X is UNIX, it is known to be very user friendly.

      I like that fact, and I use a Mac every day. However, the "Unixy" parts of Mac OS X are no easier to use than any older Unix - actually, they are harder to use because the OS supports multiple standards and has a lot of newer features.

      For the most part, Mac OS X is user-friendly because it hides the functionality that lies underneath. I really was hoping that Apple would fashion it into a polished GUI-driven interface that exposes ALL of the functionality but makes it easier to manage.

  19. Not really by Anonymous Coward · · Score: 1

    Makes me wonder whether or not we'd be using as many Windows machines had the government allowed AT&T to sell and market Unix.

    We probably would. If ATT had been allowed to sell Unix, it almost certainly would have priced it way too high for IBM's taste.

    Indeed, ATT tried selling a Unix-based personal computer (which, with typical former-Bell-System flair, they termed the "AT&T Unix PC") in the mid-80s, after they'd divested the local phone companies and could legally do whatever they wanted. It flopped, since it was obscenely priced at $5000, which was about twice the price of a fully-loaded DOS PC.

  20. Re:No support, no bug fixes by DarwinSurvivor · · Score: 3, Informative

    Unless you buy windows on a disk in a cardboard box, the only support you will get is some minimum wage tech in india employed by dell/hp/etc.

  21. They actually got sued over the support. by darkonc · · Score: 5, Informative
    According to a friend of mine (who had a single-digit Unix license #), AT&T originally refused to release UNIX on the advice of their lawyers because the anti-trust agreement prevented them from getting into non-phone markets. The universities who wanted access to the, then fledgling, OS then sued them over a clause that prevented AT&T from suppressing technology. The universities won that battle.

    So (after probably sticking their tongue out at the lawyers who originally nixed the release) they released UNIX ... and were then sued by other computer companies for violating the "phones only" clause of the anti-trust agreement. AT&T also lost that battle.

    So now it was law. They couldn't suppress the technology, but they couldn't market or support it because it wasn't directly phone- related. That's where they came up with the rather convoluted system where, for a nominal price ($1 for universities, and more ($20K, I think for companies), and signing a non-disclosure agreement, anybody could get a mag tape with a working system, and source code, a pat on the back and a 'good luck'.

    ALL support was done by users (who, pretty early on got better at it than any company would have been) -- but the non-disclosure agreement meant that you couldn't just post a file with the fixed code in it... so that's where diff(1) patches came into play -- they exposed the fix without exposing too much of the source code. In some cases where patches were extensive, the originator of the patch would simply announce it and require people to fax a copy of the first page of their license before being emailed the fix.

    AT&T was also rather pedantic about protecting their trademark, which resulted in people often using the UN*X moniker rather than include the trademark footnote at the end of their postings.

    --
    Sometimes boldness is in fashion. Sometimes only the brave will be bold.
    1. Re:They actually got sued over the support. by Anonymous Coward · · Score: 0

      I still have my NDA and hard copy of the Version 7 Kernel source code sitting on my bookshelf at home. One of my senior year CSCI classes was simply going through the kernel line-by-line figuring out what it did & how it did it. I was hooked on Unix from that point on.

  22. Re:http://www.canadianfreestuff.com by jedidiah · · Score: 1

    I am even more lazy.

    I just realize that a little bit of work upfront can save me more work later or even allow me to achieve something new with minimal effort.

    Unix users are no less lazy. They're just a little smarter about it.

    --
    A Pirate and a Puritan look the same on a balance sheet.
  23. AT&T Needs *De*regulation??? by Anonymous Coward · · Score: 0

    And the recent attempts to merge with T-Mobile aren't enough to tell you why your statement is beyond reckless?

    Makes me wonder whether or not we could even afford to pay for cellular service had the government allowed AT&T to circumvent government; regulation in the interest of the "user".

  24. Re:No support, no bug fixes by stanlyb · · Score: 3, Informative

    Actually, KDevelop, Anjuita, SourceNavigator, Kylix are pretty good IDE for linux. And MSVS compared to Borland IDE (CodeGear now) sucks, to say it plainly.

  25. Re:No support, no bug fixes by Dr_Barnowl · · Score: 3, Interesting

    any other sane higher level language

    Is Java an insane higher level language? What about Eclipse, which works well with a whole range of high AND low level languages?

    There just isn't any programs available.

    I find that most of my needs are met. In fact, a lot of the programs I use on Windows were ported from Linux. The only piece of software I pay for (a developers merge tool) had it's origins on Windows, but they sell a Linux port - presumably in recognition of the fact that so many professionals find Linux machines productive.

    If you want to do C#, Monodevelop is available, although was distinctly inferior to it's Windows progenitor, SharpDevelop, the last I looked. But that's also true of Mono itself, IMHO. Aristeer is written in C#, so in principle there's no reason it couldn't be run on Mono / Linux, unless it uses some of the features that Mono hasn't caught up with yet.

    For PHP (and a host of other things too) there's Komodo IDE (with it's free / Open counterpart Komodo Edit).

    You probably have a point on the media side of things. But I think a media person could justifiably prefer OS X to Windows.

  26. Smaller /. numbers here, please by Cragen · · Score: 1

    Seems like this sort of story always brings out the low number /.'ers. I remember one post in the last few years where each reply was by a lower post until someone showed up with a number under 1000. (If I remember right, lol. Memory is not my strong suit now. And the older I get, the less I can about that. lol) While this was all happening, I was changing vacuum tubes in military crypto boxes. lol Hell, I remember my dad testing our TV's vacuum tubes at the A&P grocery store.

    1. Re:Smaller /. numbers here, please by c0d3g33k · · Score: 1

      Hell, I've tested vacuum tubes down at the drug store too. Son, is that you? :-)

      Very likely many people of your generation and younger have done the same thing if they own a tube guitar amplifier (or audiophile stereo equipment). After the tube testers disappeared from drugstores, you could still test them at Radio Shack (and buy replacements too). No more - now you just order a replacement set on the internet.

    2. Re:Smaller /. numbers here, please by SteveFoerster · · Score: 1

      I remember using NCR SVR4 MP-RAS, which was NCR's flavor of UNIX after they were split off from AT&T in the late '80s.

      Okay, now it's someone's turn from the upper five digit cadre. ;-)

      --
      Space game using normal deck of cards: http://BattleCards.org
    3. Re:Smaller /. numbers here, please by Myself · · Score: 1

      Okay, I've got a five-digit...

    4. Re:Smaller /. numbers here, please by Anonymous Coward · · Score: 0

      We loaded a tape we "borrowed" from Pitt in '73 to a PDP-8. Now get off my lawn!

    5. Re:Smaller /. numbers here, please by Guy+Harris · · Score: 2

      We loaded a tape we "borrowed" from Pitt in '73 to a PDP-8. Now get off my lawn!

      Not onto your PDP-8, you didn't. PDP-11, maybe.

      Now get off my lawn. :-)

    6. Re:Smaller /. numbers here, please by Anonymous Coward · · Score: 0

      I use a tube tester for my guitar amps. Thanks for the shout out, buddy.

    7. Re:Smaller /. numbers here, please by KlomDark · · Score: 1

      Kids these days... ;)

    8. Re:Smaller /. numbers here, please by Doug+Merritt · · Score: 1

      Indeed. I'm with you, brother.

      --
      Professional Wild-Eyed Visionary
    9. Re:Smaller /. numbers here, please by Doug+Merritt · · Score: 1
      I must have joined /. at least an hour before you did, so get off *my*...ah hell, you can use my lawn. :-)

      (and: PDP-11 FTW -- I was part of one of the efforts mentioned in this Strange Birth article)

      --
      Professional Wild-Eyed Visionary
  27. Re:No support, no bug fixes by Anonymous Coward · · Score: 0

    Didn't your beloved Apache web server have a major security vulnerability for just as many years? Despite it being open source...

  28. Re:No support, no bug fixes by abigor · · Score: 1

    The good old ad hominem attack. I guess the truth hurts.

  29. Re:No support, no bug fixes by Anonymous Coward · · Score: 0

    So you prefer the programs that run on Windows, but I still don't hear an argument for Windows itself.

  30. The History of a Rolling Trainwreck by oakwine · · Score: 1

    My first encounter with UNIX was learning it on a dialup system back in the days when CP/M was still the user operating system. It looked to me like a vast rolling trrainwreck that was continually evolved to keep it more or less functional. Teams of wizards surrounded it and made lots of money from its care and feeding. I became one of the wizards. But I still hated it. And do.

    1. Re:The History of a Rolling Trainwreck by Anonymous Coward · · Score: 0

      Rolling train wreck as compared with.....?

  31. Servers by Anonymous Coward · · Score: 0

    Come on dude, we're talking about server systems here, not desktop unix which isn't exactly a "consumer" product. FYI, only a handful of linux people actually want linux to "take over the desktop". The rest of us have already preferred it for 15 years.

    1. Re:Servers by Guy+Harris · · Score: 4, Informative

      Come on dude, we're talking about server systems here, not desktop unix which isn't exactly a "consumer" product.

      Not even if somewhere around 10% of desktops and laptops are running Un*x? Heck, some of them are even running trademarked UNIX.

  32. So basically what AT&T still does with Android by Kamiza+Ikioi · · Score: 3, Funny

    'No advertising, no support, no bug fixes, payment in advance.'

    --
    I8-D
  33. Re:No support, no bug fixes by toadlife · · Score: 1, Interesting

    Also, try to find a Linux equivalent to WinMerge. There is none. KDiff is the closest you can get, but not close enough. I've been using Linux to compile Android kernels and WinMerge is perfect for getting a high level view what the various kernel devs (who don't use git properly) have done to the stock Samsung kernel source.

    I resorted to Running WinMerge under Wine. It crashes whenever I do certain functions, but the native linux alternatives are so bad that I put up with it.

    And don't get me started on gnome. Holy crap what an abomination. I used to enjoy the KDE 3.x series on my FreeBSD desktops. It was functional and relatively customizable, but this transition of the linux community to gnome boggles my mind, even with the clusterfuck that Kde 4.x series was/is. KDE 3.x is still better than the current Gnome IMO.

    And before anyone replys, yes, I know I can choose a distro that uses KDE or install it myself. I've been around that block, and will be doing it again soon.

    -1 Flamebait

    --
    I don't always use unix-like operating systems; but when I do, I prefer FreeBSD.
  34. Re:No support, no bug fixes by Anonymous Coward · · Score: 0

    And what's the problem with Windows 7? It boots fast, doesn't crash, the file system is reliable, and its memory footprint is smaller than OS X or Ubuntu. My only real complaint is that the included commandline tools are weak.

  35. Re:No support, no bug fixes by blackest_k · · Score: 1

    photoshop can run in wine , there is a paintshop portable app which works perfectly in wine or on windows. It's not legal of course. Although there is no reason you couldn't buy a legal version with a licence. ...
       

  36. Re:No support, no bug fixes by toadlife · · Score: 1

    No other argument is needed.

    --
    I don't always use unix-like operating systems; but when I do, I prefer FreeBSD.
  37. What support and bug fixes by microphage · · Score: 1

    Unless you are a major corporation and have a contract with Microsoft the only support you get is reinstall-reinstall-reinstall, with Open Source you get to contact the developers directly ...

    1. Re:What support and bug fixes by shark72 · · Score: 1

      "Unless you are a major corporation and have a contract with Microsoft the only support you get is reinstall-reinstall-reinstall, with Open Source you get to contact the developers directly ..."

      And like that poor woman who wrote to Squirrelmail developer Steve Brown found out, it's liable to get your email published along with open calls for your harrassment.

      By the developer.

      Because you were a novice user who had the audacity to contact a developer, because that was the only email address you could find.

      Other FOSS developers supported his behavior because "the act of contacting the developer is a pretty big no-no."

      --
      Sitting in my day care, the art is decopainted.
    2. Re:What support and bug fixes by microphage · · Score: 1

      Could you find anything newer than January 2007 to generalize that the entire Open Source universe is populated by rude people. ref and it's considered rude not to provide links to what-so-ever you are refering to.

  38. The conditions that led to UNIX... by freality · · Score: 4, Interesting

    There's a talk from 1986 by Richard Hamming at Bellcore, about how to do great research, but it also ends up in a short discussion about the conditions there that led to UNIX:

    http://www.paulgraham.com/hamming.html

    The whole talk is really excellent, and there's this theme in it that the really great things come from some unexpected places, by the compounding of seemingly unrelated character traits, work habits and organization dynamics.

    At the end in the Q&A, Hamming gets into a short discussion with the host Alan Chynoweth about the origins of UNIX, evincing from Alan a favorite quote:

    "UNIX was never a deliverable!"

    expanded:

    "Hamming: First let me respond to Alan Chynoweth about computing. I [was in charge of] computing in research and for 10 years I kept telling my management, ``Get that !&@#% machine out of research. We are being forced to run problems all the time. We can't do research because we're too busy operating and running the computing machines.'' Finally the message got through. They were going to move computing out of research to someplace else. I was persona non grata to say the least and I was surprised that people didn't kick my shins because everybody was having their toy taken away from them. I went in to Ed David's office and said, ``Look Ed, you've got to give your researchers a machine. If you give them a great big machine, we'll be back in the same trouble we were before, so busy keeping it going we can't think. Give them the smallest machine you can because they are very able people. They will learn how to do things on a small machine instead of mass computing.'' As far as I'm concerned, that's how UNIX arose. We gave them a moderately small machine and they decided to make it do great things. They had to come up with a system to do it on. It is called UNIX!

    A. G. Chynoweth: I just have to pick up on that one. In our present environment, Dick, while we wrestle with some of the red tape attributed to, or required by, the regulators, there is one quote that one exasperated AVP came up with and I've used it over and over again. He growled that, ``UNIX was never a deliverable!''"

    1. Re:The conditions that led to UNIX... by bill_mcgonigle · · Score: 1

      They had to come up with a system to do it on. It is called UNIX!

      You can pick up the rest of that story with a video I made of Doug McIlroy giving a history-of-Unix talk to my LUG. (Doug managed the lab, kept the managers away from Thompson and Ritchie, and came up with pipes).

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
  39. Some misleading info on this article from the IEEE by akuma624 · · Score: 2

    The article is well written but I am not sure they have checked their facts ... here is a direct quote from the article .... "It even runs some supercomputers." Now ... just head over to the TOP500 page (http://i.top500.org/stats) and sort by OS ..... I wouldn't call > 80 % just 'some supercomputers' ???

    --
    ... if music be fruit of love, play on ....
  40. Re:No support, no bug fixes by jedidiah · · Score: 2

    Just wait for the next version...

    " WinMerge 3 will be modern compare/synchronization tool. It will be based on Qt library and cross-platform. You can use the same tool in Windows and in Linux. "

    --
    A Pirate and a Puritan look the same on a balance sheet.
  41. Re:No support, no bug fixes by Drencrom · · Score: 1

    ... and its memory footprint is smaller than OS X or Ubuntu ...

    [citation needed]

    Really interested not trolling.

  42. Re:No support, no bug fixes by CmdrPony · · Score: 1

    If you are droning on about Photoshop then you are a poser that has no clue what Photoshop is used for. It's a canned Lemming Troll for idiots with no real clue.

    I do my professional work with Photoshop. I wouldn't say I'm an artist (artists don't paint with computers), but I have very professional use for it. Yet you say I have no clue what it is used for. Care to tell me what it's good for, then?

  43. Re:No support, no bug fixes by toadlife · · Score: 1

    Awesome!

    --
    I don't always use unix-like operating systems; but when I do, I prefer FreeBSD.
  44. Re:No support, no bug fixes by MightyMartian · · Score: 3, Insightful

    The reason Windows, Mac OS and pretty much all consumer and small business OSs became successes is because they were cheap. DOS and Windows, in particular, became dominant because of the OEM ecosystem. Support and bugfixes? Microsoft support has always been expensive, and bugfixes for the operating system didn't even become widely distributed until Windows vulnerabilities reached a level where Microsoft was essentially forced to come up with Windows Updates to dole out its bugfixes in a much easier way. When I first started out administering Windows NT based systems, bugfixes only came regularly with service packs, or if you installed them based on advice from Microsoft directly or via KB articles, or because some guy on randomtechforum.com told you "yeah, KB28342818122 will fix your problem." And earlier versions of Windows sure the hell didn't even have that level of support. Windows 95 or Windows 3.1 were what they were and about the only way you would get updates is if it was shipped with some piece of software that needed to update a DLL or other support file.

    It little or nothing to do with support. Until Linux came along and basic took the expensive licensing and support costs associated with most *nix operating systems, *nix vendors didn't even give a shit about the PC market, and regarded PCs as glorified terminals when and where they had to connect to *nix-based systems. Still, even on the old Xenix system I administered, there were updates available, the last one I remember installing around 1992 or 1993 was a patch to fix hard-coded originator host names in UUCP bangpaths (and if that doesn't date me, nothing does).

    --
    The world's burning. Moped Jesus spotted on I50. Details at 11.
  45. Re:No support, no bug fixes by tempest69 · · Score: 1

    have you installed powershell yet? It helps a fair bit.

  46. Re:No support, no bug fixes by jedidiah · · Score: 0

    Judging by your original post which mentions both Photoshop and Paint Shop Pro in the same breath, probably not much.

    If someone else paid for it, or if you never paid for it at all you can certainly find trivial uses for it.

    --
    A Pirate and a Puritan look the same on a balance sheet.
  47. UNIX required a more powerful CPU by peter303 · · Score: 1

    Ironically MicroSoft's first saleable OS was a flavor of UNIX called Xenix. But Xenix on 80286's was really lame compared to UNIX on a PDP-11 or VAX. UNIX wasnt really that efficient on a PC until the 80486s in the mid-1990s. That was fortunately the same time Linus started his version. MicroSoft sold Xenix to SCO after it developed MS-DOS. SCO patent-trolled it unsuccessfully for many years.

  48. It's a Unix system! by Anonymous Coward · · Score: 0

    Rubbish. Everyone knows the birthplace of Unix was in Jurassic Park.

    1. Re:It's a Unix system! by Anonymous Coward · · Score: 0

      Only those born in the 1990s.

  49. Re:No support, no bug fixes by jedidiah · · Score: 1

    > , and its memory footprint is smaller than OS X or Ubuntu

    No it isn't. Not by a long stretch.

    Set your sights a little lower. This is a monopoly product you are talking about. If you try to talk nonsense, all of use that are forced to use it by corporate overlords or have to fix computers for relatives are going to know that you're full of it.

    --
    A Pirate and a Puritan look the same on a balance sheet.
  50. will UNIX last a century? by peter303 · · Score: 1

    The "first brood" of high level languages- COBOL, LISP and FORTRAN- are well into their 2nd half century. I would not be surprised if they last a century along with UNIX and C.

  51. Is that you by drainbramage · · Score: 1

    Sandusky?

    --
    No brain, no pain.
  52. A nice story but. by Anonymous Coward · · Score: 1

    Nice piece. A bit incorrect about multiplexing as Burroughs had released the B-5500/5700 in 1966 that allowed multiple terminals and running the CANDE ( Command And Edit interface) allowed batch jobs and terminals to run simulatinously, unlike IBM computers of the day which were batch orietented for almost 10 years later.

    1. Re: A nice story but. by Guy+Harris · · Score: 1

      Nice piece. A bit incorrect about multiplexing as Burroughs had released the B-5500/5700 in 1966 that allowed multiple terminals and running the CANDE ( Command And Edit interface) allowed batch jobs and terminals to run simulatinously, unlike IBM computers of the day which were batch orietented for almost 10 years later.

      ...if you don't count the IBM System/360 Model 67 running either TSS or, more likely, CP/CMS (or third-party OSes such as the Michigan Terminal System, but you're presumably talking about OSes from the hardware vendor). (And it's more like "for almost 5 years later", given TSO, which showed up in 1971.)

      But, yeah, it's not as if Multics invented time-sharing (that dates back to CTSS back in the early '60's) or even was the first commercially-sold time-sharing OS (the original PDP-6/PDP-10 time-sharing monitor came out in the mid '60's).

  53. Re:No support, no bug fixes by CmdrPony · · Score: 1

    I paid for it myself. Like I said, I use it for work, so can pay too.

  54. Re:No support, no bug fixes by next_ghost · · Score: 1

    Valgrind and Git. I rest my case on software development tools.

  55. repeated again and again by Anonymous Coward · · Score: 0

    the worth thing of this history is that it repeated again and again: some one in financial or marketing team cut founds for an intesting and inovating project, and some stupid technical guys works in their free time with discarted equipment, and ...
    I work in the old Lucent and see this history may times in the last 10 years.
         

  56. Re:No support, no bug fixes by next_ghost · · Score: 1

    its memory footprint is smaller than OS X or Ubuntu.

    Get real man, I have a working desktop Linux on a machine from 1998 which has only 96 megs of RAM and 266MHz CPU. Even XP wouldn't run on something that old. And with the right choice of desktop environment, the machine can still run a lot of modern desktop software.

  57. Re:No support, no bug fixes by 19thNervousBreakdown · · Score: 0

    *Googles for literally 3 seconds*:

    Gnome
    KDE

    --
    <xml><I><am><so><damn>Web 2.0</damn></so></am></I></xml>
  58. Re:No support, no bug fixes by crutchy · · Score: 2

    Re: "major security vulnerability"

    Yeah and cos Apache has hosted more than half the web for years that would make it a big fish for hackers to exploit... and the number of web hosts adversely affected by this bug are?

    Whatever the number (small no doubt), has it crippled Apache's share of the web hosting pie?

    I'm sure you get my point.

  59. Re:No support, no bug fixes by Anonymous Coward · · Score: 0

    No, but you are an idiot for coming to that conclusion (and also for the OP).

  60. Re:No support, no bug fixes by toadlife · · Score: 0

    Are you that fucking stupid to think that I could compile my own working Android kernel, yet not find Kdiff and Meld?

    Those are the first two things I tried and neither compare to WinMerge.

    Someone else bothered to go into detail if you care:
    http://petermoulding.com/what_is_the_equivalent_to_winmerge_in_linux

    --
    I don't always use unix-like operating systems; but when I do, I prefer FreeBSD.
  61. Re:No support, no bug fixes by DarKnyht · · Score: 2

    I dual boot Ubuntu and Windows 7. Ubuntu boots so fast that if I am not paying attention it is up before I realize it and log in is just as responsive. Windows 7 on the hand takes about double the time to the log in screen, and then there is a wait at least as long for the machine to become responsive enough to use.

    Granted, this on a machine with only 2 GB of RAM. But running the same applications on each OS presents a world of difference (Remote Support Client [supports both OSes], Lotus Notes 8.5 full feature, Chrome Browser, Skype, plus a RDC client). Linux responses and functions, while I generally have to wait and be patient for Windows. Needless to say, I find myself only using Windows when I must (Microsoft Access mainly, but occasionally the RDC client since it supports Windows 7 and Server 2008).

    But then to be fair, I am forced to run the bloated piece of crap called Symantec Endpoint Protection on the Windows 7 side of life. However, it doesn't excuse the poor performance prior to it starting.

    --
    Voting them all out of office, now that's change I can believe in.
  62. Re:No support, no bug fixes by kiwimate · · Score: 1, Interesting

    So you prefer the programs that run on Windows, but I still don't hear an argument for Windows itself.

    Well, gosh, that sounds like a fairly decent argument for Windows right there.

    "Hi, I run Linux."

    "And I run Windows."

    "(Sneer) I'm super reliable. And free! And Open Source!!! (Angelic music cue.)"

    "Oh, nice. What programs do you run?"

    "Ummm, none. But I'm very, very stable while I'm sitting at rest, doing nothing!"

    "Err, well, golly, isn't that nice..."

    "You poor sucker. You're Windows. You BSOD all the time while you're running Photoshop."

    "Well, actually, I haven't seen a blue screen of death in ages. Windows is pretty stable now. How about you? Stable, huh? No problems running Photoshop, I bet..."

    "Umm, well, actually I can't run Photoshop. But anyone who wanted to get a team of coders and expert graphics editors together to dedicate a few years of their life could write an open source and free equivalent and it'd be lightning fast."

    "But, look, I hate to press the matter, but what do you run now, not in the theoretical future?"

    "Well, nothing. But I do it really, really well."

    (Pats Linux on the head...)

  63. Re:No support, no bug fixes by AF_Cheddar_Head · · Score: 1

    Actually it might if you use the full disk encryption part of the endpoint. I do and it absolutely sucks, including the fact that if I boot my laptop on the docking station I have to open the laptop to do the initial login as my external keyboard does not work before the encryption is unlocked. Symantec Endpoint just plain sucks.

  64. Re:No support, no bug fixes by rbeef · · Score: 2

    "in 2008 Microsoft confirmed a vulnerability in Internet Explorer, which affected some versions that were released in 2001" i rest my case

    It's not the bugfixes people want. It's the perception of bugfixes. Remember, perception is reality.

  65. Re:No support, no bug fixes by KingMotley · · Score: 1

    Then stop using cmd and switch to powershell -- which also comes with windows 7.

  66. Eunuchs Have Descendants!??!?! by Jeremiah+Cornelius · · Score: 1, Offtopic

    Heck, how'd that happen, after they lost their dangling participles?

    --
    "Flyin' in just a sweet place,
    Never been known to fail..."
  67. XNU by Udo+Schmitz · · Score: 2

    I thought it was a Mach kernel and a BSD userland. How exactly that's quintessentially different from me installed Cygwin on my Windows machine and calling it a Unix machine is beyond me.

    http://en.wikipedia.org/wiki/XNU

    http://osxbook.com/book/bonus/ancient/whatismacosx//arch.html

  68. Re:No support, no bug fixes by scottbomb · · Score: 1

    This is comical indeed, but not exactly accurate. I started dual-booting a couple of months ago, just to try it out. Frankly, there isn't much I can do on Windows 7 that I can't do on Xubuntu. There may be no Visual Studio but there is Netbeans. Everyone knows about the lack of gaming support. Even if I quit playing games, I'll probably never be able to replace Windows for one reason: Windows Media Center. I've tried MythTV and sadly, it doesn't come close. In fact, it downright blows in a lot of ways. Maybe someday I'll write a new UI for it but my skillz aren't quite there yet.

  69. Re:No support, no bug fixes by grub · · Score: 4, Interesting

    Apple is the largest UNIX vendor in the world right now...

    --
    Trolling is a art,
  70. Re:No support, no bug fixes by Aighearach · · Score: 1

    True enough, eventually one comes to try emacs and then they realize that platform lock is silly and needless.

  71. Re:No support, no bug fixes by Anonymous Coward · · Score: 1

    What version of Symantec Endpoint Protection are you running? I work for the company, and we spent a lot of time focused on performance in the latest release.

  72. Re:So basically what AT&T still does with Andr by Guy+Harris · · Score: 1

    'No advertising, no support, no bug fixes, payment in advance.'

    No advertising?

    And they're not really selling "Android" the operating system - Google does that; they sell/offer it to their customers, who are, in this case, phone (and tablet) manufacturers. AT&T are selling phones that run Android (just as they sell phones that run iOS and Windows Phone).

    I don't know whether AT&T or the phone manufacturer would be the ones responsible for providing support and/or bug fixes in this case.

  73. Re:No support, no bug fixes by arkane1234 · · Score: 1

    Your new I can tell.

    --
    -- This space for lease, low setup fee, inquire within!
  74. Re:No support, no bug fixes by kiwimate · · Score: 1

    Nah, I've been reading /. since it started. If I'd registered when I started reading I'd have a four digit UID. (Smugness.) I'm just contrary...they keep me around for comic effect and to be provocative.

  75. Best Unix yet... by ritzer · · Score: 2

    I have played with many flavours of Unix, Linux since '92 -- but the GUI is conflicted and never amounted to anything I will likely program. OS X is the best Unix that this old timer has used in my 23 years with the OS.

    1. Re:Best Unix yet... by unixisc · · Score: 1

      Actually, the best Unix I ever worked w/ was NeXTstep, in my college Computer Center lab. Painful part was that they were NeXT's diskless workstations, but other than that, the entire file system was visible from Workspace Manager. Never had any problems using it, even though @ the time, I was pretty new to Unix. Many of the other users I saw would work some things in consoles, but otherwise, much of the stuff was just there. That platform might have been more successful had it accompanied some of the more powerful workstations of the time, such as Suns, HP 9000s, RS/6000, DECstations and so on.

      Too bad GNUSTEP hasn't been a mainstream UI instead of GNOME. GNUSTEP is more of an Object Modelled Environment than GNOME is.

    2. Re:Best Unix yet... by Anonymous Coward · · Score: 0

      OS X is the current generation of supported NextStep. That's what Apple bought in '96 when stevie returned as iCEO. It was in 2001 when it was released under the Apple moniker -- at least that was the year I switched from a brief career with Windows.

      I always wondered why Linux developers seemed so keen on the re-creation of Windows -- when there are so many of us running from that. Perhaps someday someone will crave a GNUSTEP which is modern and complete.

  76. Re:No support, no bug fixes by gfody · · Score: 1

    You might be interested in this: http://www.gentoo.org/proj/en/gentoo-alt/prefix/
    I use git w/diff.external=winmerge and couldn't be happier

    --

    bite my glorious golden ass.
  77. Re:No support, no bug fixes by dave87656 · · Score: 1

    Is that why Windows has more bugs and is less reliable than Linux or Mac? MS has never placed a priority on bug fixes and usually uses bugs them as a selling point for users to upgrade to the next version (Windows ME to Windows 95 and Vista to Windows 7 for example.

    As far as support is concerned, get your credit card out, just like you would if you were using Red Hat or Open Suse.

  78. Re:No support, no bug fixes by dave87656 · · Score: 1

    especially if you want to develop with C# or any other sane higher level language or for Windows

    Of course Windows is a better environment if you are developing for Windows.

  79. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  80. UNIX stagnated with the rise and dominance of x86 by g2racer · · Score: 1

    When companies stopped buying big iron proprietary RISC servers to put in their datacenters and started putting commodity x86 servers instead, UNIX stagnated. Linux which was seen as a toy prior took advantage of this.

  81. Systems & Versions by Anonymous Coward · · Score: 0

    I've never understood the difference b/w System# and Version# in Unix. What does SVR4 mean? What would trigger a change from System III to System V, and what happened to System IV in b/w? If you have releases, why have decimal releases, like SVR3.2, SVR4.2? SCO's Unixware 7.x was supposed to be SVR5. (Oh, and why are System# Roman numerals and Version# Hindu numerals? (I'm not going to call it Arabic, since the Arabs had nothing to do w/ their invention)) How come nobody else, e.g. Sun, thought of coming out w/ an SVR5 Unix?

    On a different note, since Open Group owns the trademark and the certification of what's Unix, is there still anything (other than SCO's moribund appeals) preventing SVR4.x and BSD to merge back into a single Unix? Also, aside from DEC, did Open Group retire OSF/1 after the merger of OSF and SVID? Also, if Unixware is a trademark of the Open Group, what exactly is its definition - Unix plus some sort of Netware?

    For the current market, is it valid to think of BSD as the only active Unix out there? Yeah, I know Solaris, HP/UX & AIX are still around, but they are all largely platform specific (and if Itanium dies, I think so will HP/UX). Incidentally, anyone know whether if BSD & Linux were subjected to the Open Group's certification tests, they'd both be certified as Unix, just like OS-X is?

  82. Re:No support, no bug fixes by unixisc · · Score: 1

    You mean that Oracle, IBM, or HP don't offer bug fixes or support? We're talking about Unix now, not some Linux or BSD distro you might download from distrowatch. I find it pretty hard to believe that Oracle, IBM or HP won't support a corporation that buys $$$ worth of hardware & software from them.

  83. Re:So basically what AT&T still does with Andr by Hognoxious · · Score: 1

    But does two hours of pushing broom get an 8 x12 4 bit room?

    --
    Confucius say, "Find worm in apple - bad. Find half a worm - worse."
  84. Re:No support, no bug fixes by Anonymous Coward · · Score: 0

    Unless you buy windows on a disk in a cardboard box, the only support you will get is some minimum wage tech in india employed by dell/hp/etc.

    In most countries (USA is not most countries, it is only ONE country), if you buy windows on a disk in a cardboard box, you will get no support from Microsoft at all (other then their web page) and no support from anybody else. Support from minimum wage tech employed by dell/hp/etc. is an improvement to that. Only English speaking countries get support from India, although Indian tech-support-companies are starting to support other languages, e.g. Swedish speakers still get most support from low(er) wage countries like Netherlands (it is reasonably easy to learn Swedish if you know Dutch), South Africa, and Ireland and Scotland (I have no idea as to why someone thought learning Irishmen and Scots Swedish was a good idea, except for the lower wages); Norwegian speakers get their tech support from Sweden (much lower wages, very similar languages); Spanish speakers from the Philippines and South American countries, or Portugal (lower wages, similar languages), French speakers from prior French colonies in Africa and Asia et c.

  85. Re:No support, no bug fixes by DarwinSurvivor · · Score: 1

    Interesting, I did not know that. Just out of curiosity, does Canada get similar support to Windows, or are they also "other countries"?