|
|
Sponsored Content
Special Forums
News, Links, Events and Announcements
SCO sues IBM
Post 34732 by LivinFree on Saturday 8th of March 2003 11:35:51 PM
03-09-2003
Well, I don't think anybody really understands whats going on with this - it seems to be some sort of poli-techinal "fireman's contest", to put it politely.
There's a short article on it here:
http://seattletimes.nwsource.com/htm...nixsuit08.html
I don't think they've hit it quite on the head, though. Just as a further evidence on the misunderstandings of this issue, below is a link to a comment posted on Slashdot by Bruce Perens ( for those who have not heard the name before, Bruce Perens is an adamant Open Source advocate, and I believe he still works for HP):
http://slashdot.org/comments.pl?cid=...=56225&tid=123
As for the trademark name, X/Open {(r)(t) and so on} does acknoledge the use of the Unix name to companies who have "bought" the name before they had it - one of them being SCO (the current owner of the direct descendent sysVr4 code). Heck, you can browse true Unix code online now: http://minnie.tuhs.org/UnixTree/ . I've even gotten SystemV and older versions running on a linux box using PDP-11 emulators...
And then again, maybe Bruce (and the rest of the world) is way off... Hey, being that I'm up here in Cupertino for a while for training at HP (Their campus is across the street right now - in fact I can see it out the window), maybe I could track down Mr. Perens and ask him whats going on
There's a short article on it here:
http://seattletimes.nwsource.com/htm...nixsuit08.html
I don't think they've hit it quite on the head, though. Just as a further evidence on the misunderstandings of this issue, below is a link to a comment posted on Slashdot by Bruce Perens ( for those who have not heard the name before, Bruce Perens is an adamant Open Source advocate, and I believe he still works for HP):
http://slashdot.org/comments.pl?cid=...=56225&tid=123
As for the trademark name, X/Open {(r)(t) and so on} does acknoledge the use of the Unix name to companies who have "bought" the name before they had it - one of them being SCO (the current owner of the direct descendent sysVr4 code). Heck, you can browse true Unix code online now: http://minnie.tuhs.org/UnixTree/ . I've even gotten SystemV and older versions running on a linux box using PDP-11 emulators...
And then again, maybe Bruce (and the rest of the world) is way off... Hey, being that I'm up here in Cupertino for a while for training at HP (Their campus is across the street right now - in fact I can see it out the window), maybe I could track down Mr. Perens and ask him whats going on
|
|
2 More Discussions You Might Find Interesting
1. SCO
Even though IBM states that the x3500 server is Openserver 6.x compatible, it is still a bit of a trick to install SCO Openserver 6 to the machine because the standard method of installing the BTLD required to install the OS requires that the driver be written to a floppy which doesn't exist on... (3 Replies)
Discussion started by: qkrenge
3 Replies
2. SCO
I cannot install sco on this particular ibm server because sco cannot find the raid controller and thefore the logical drive.
I have a floppy disk that I use in other machines when boot: shows on the screen. I usually type restart link=ad320 and it works but this time i have no floppy drive.
... (1 Reply)
Discussion started by: iNetForce
1 Replies
LEARN ABOUT NETBSD
urlphy
URL(4) BSD Kernel Interfaces Manual URL(4) NAME
url -- Realtek RTL8150L USB Ethernet driver SYNOPSIS
url* at uhub? urlphy* at mii? DESCRIPTION
The url driver provides support for USB Ethernet adapters based on the Realtek RTL8150L USB-ether bridge chip. The url driver supports the following adapters: CompUSA USBKR100 GreenHouse GH-USB100B Melco Inc. LUA-KTX Sitecom LN013 For more information on configuring this device, see ifconfig(8). DIAGNOSTICS
url%d: watchdog timeout A packet was queued for transmission and a transmit command was issued, however the device failed to acknowledge the transmission before a timeout expired. url%d: no memory for rx list The driver failed to allocate an mbuf for the receiver ring. SEE ALSO
arp(4), mii(4), netintro(4), usb(4), ifconfig(8) HISTORY
The url device driver first appeared in NetBSD 1.6. AUTHORS
The url driver was written by Shingo WATANABE <nabe@nabechan.org>. BSD
September 18, 2006 BSD