Slashdot Mirror
Ransom Love on United Linux, SCO Unix
tit4tat writes: "Caldera chief executive Ransom Love confessed to ZDNet UK that "[Caldera is] not moving Open Unix [i.e., the former SCO Unix] onto Intel's 64-bit platform...." I suspected that Caldera bought SCO just to kill SCO Unix, even though they denied it at the time. Now, the first Unix I ever knew is about to be no more. "
Well considering that SCO sucked why would they ever want to port it to IA-64. No they didn't by SCO to kill it. It was going to die anyway. They bought it for the Intellectual Property and some of the application software that SCO had developed. Also I understand they were interested in SCO's support division.
*sigh*
(from the article)
So OpenUnix will continue in parallel to OpenLinux?
Yes. Open Unix could well keep going in parallel to OpenLinux. We are not moving Open Unix onto Intel's 64-bit platform, but IA32 will be around for a long time yet.
Please read the articles before you post them....
-BlueLines
--BlueLines "The cost of living hasn't affected it's popularity." -anonymous
... SCO sucked? It was late to market with every major improvement of BSD, had obnoxious licensing restrictions enforced by code (which was easily overridable -- just drop in a Linux-derived /bin/login with some obvious patches), and did its best to be absolutely unusable as hell at all times. The only way to fix it without Linux was to install the unsupported Skunkware CD, which made life tolerable, but never fun. SCO's dead? Well, good riddance, say I. (Oh, and did I mention it derived from Microsoft's Xenix? All the more reason to stake the bugger.)
Dog is my co-pilot.
The wholesale company I work for used SCO Unix for 12 years. Our customers would dial into it with our windows software to order product. The last few years was a real pain in the butt. SCO Unix didn't have many device drivers, was hard to install even with the recommended hardware, and crashed too often.
Four years ago when I started working for the company, I recommended Linux. My boss didn't want to use it because at the time there were no companies that had decent support. Last year we finally switched to Red Hat. They have decent support. The only big problem with RH is being able to install from a backup tape. SCO unix had utilities for this that worked well. With Linux this is much more difficult.
We have been more than satisfied since the switch to Red hat.
Good Riddance to SCO. It was good at one point, but they let it fall to peices.
So does Ransoms. The standard desktop client at Caldera is Windows. Pretty pathetic really.
Uh, this is pretty common practice. For example, you can compile all the source that makes up Red Hat and distribute binaries of it, you just can't call it "Red Hat".
I assume that they made this decision to try and increase their sales of official boxed products, versus having everyone download a free ISO. There's nothing to stop you from compiling the whole system, building an ISO, and distributing it under the name "Divided Linux".
You aren't using a 'fucking' winmodem, are you? It takes no time at all to get it working if you are using the correct hardware. Just a thought.
*desperately desires karma*
SCO UNIX did not suck and was an extremely stable UNIX(tm) for the Intel platform. It was an AT&T variant and was aien to a lot of folks who were BSDers. Suck it did not as long as a competent person admin'd it. It once had a emulation layer that allowed Win 3.x to run with all the apps. And STABLE. Xenix which was an M$ bastardized offshoot was a bit unstable, but worked just fine. I coded a lot of apps and admin'd on both SCO products. I saw my first Xenix running on an i286 with 3 meg of RAM and 10 meg of disk. It will be missed.
Of course you can do this. This is just a question of configuring your system properly. You need to edit your /etc/inittab and add apropriate -I parameters for your getty processes:
1:2345:respawn:/sbin/getty 38400 tty1 -I 'ESCcESC[?17;55;248cESC]RESC]P0681800'
2:23:respawn:/sbin/getty 38400 tty2 -I 'ESCcESC[?17;55;248cESC]RESC]P0686800'
3:23:respawn:/sbin/getty 38400 tty3 -I 'ESCcESC[?17;55;248cESC]RESC]P0005078'
4:23:respawn:/sbin/getty 38400 tty4 -I 'ESCcESC[?17;55;248cESC]RESC]P0681868'
5:23:respawn:/sbin/getty 38400 tty5 -I 'ESCcESC[?17;55;248cESC]RESC]P0006818'
6:23:respawn:/sbin/getty 38400 tty6 -I 'ESCcESC[?17;55;248cESC]RESC]P0006878'
Make sure that you enter a literal escape character for ESC (in vi you do this by preceding it with a CTRL-V, in emacs you must press CTRL-Q first).
After you have made these changes restart all your getty processes:
telinit q
killall -HUP getty
If you want to know what the escape sequences do, then here you go:
It's not well known, because it isn't true.
Sun's OS derived directly from BSD. One of Sun's founders, Bill Joy (now their Chief Scientist), was one of the primary developers of BSD and one of the people responsible for getting BSD to run on the 68000 (which was the processor used in the first Suns).
At the time, Apollo didn't even run Unix, but rather their own OS named "Domain." To compete, Apollo modified Domain to support a Unix emulation (including a switching mechanism based on conditional symlinks). Domain didn't die until HP bought Apollo, though I believe they did ultimately port native Unix to Apollos just before then.