Sponsored Content
Full Discussion: SCO sues IBM
Special Forums News, Links, Events and Announcements SCO sues IBM Post 34732 by LivinFree on Saturday 8th of March 2003 11:35:51 PM
Old 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 Smilie
 

2 More Discussions You Might Find Interesting

1. SCO

Install SCO Openserver 6.0.0 on an IBM x3500 7977E6U

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

Sco 5.0.7 on ibm server, no floppy drive.

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
URI::URL(3)						User Contributed Perl Documentation					       URI::URL(3)

NAME
URI::URL - Uniform Resource Locators SYNOPSIS
$u1 = URI::URL->new($str, $base); $u2 = $u1->abs; DESCRIPTION
This module is provided for backwards compatibility with modules that depend on the interface provided by the "URI::URL" class that used to be distributed with the libwww-perl library. The following differences exist compared to the "URI" class interface: o The URI::URL module exports the url() function as an alternate constructor interface. o The constructor takes an optional $base argument. The "URI::URL" class is a subclass of "URI::WithBase". o The URI::URL->newlocal class method is the same as URI::file->new_abs. o URI::URL::strict(1) o $url->print_on method o $url->crack method o $url->full_path: same as ($uri->abs_path || "/") o $url->netloc: same as $uri->authority o $url->epath, $url->equery: same as $uri->path, $uri->query o $url->path and $url->query pass unescaped strings. o $url->path_components: same as $uri->path_segments (if you don't consider path segment parameters) o $url->params and $url->eparams methods o $url->base method. See URI::WithBase. o $url->abs and $url->rel have an optional $base argument. See URI::WithBase. o $url->frag: same as $uri->fragment o $url->keywords: same as $uri->query_keywords o $url->localpath and friends map to $uri->file. o $url->address and $url->encoded822addr: same as $uri->to for mailto URI o $url->groupart method for news URI o $url->article: same as $uri->message SEE ALSO
URI, URI::WithBase COPYRIGHT
Copyright 1998-2000 Gisle Aas. perl v5.12.5 2011-08-13 URI::URL(3)
All times are GMT -4. The time now is 02:19 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy