Why Folks Didn't Want a SCOsource License: Let Us Count the Reasons

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News Why Folks Didn't Want a SCOsource License: Let Us Count the Reasons
# 1  
Old 02-21-2010
Why Folks Didn't Want a SCOsource License: Let Us Count the Reasons

I thought it'd be fun to answer SCO's expert report from Dr. Gary Pisano, some more, on one point in particular, namely his inability to find any other reason SCOsource wasn't popular other than Novell's counterclaims to ownership of the code. Here's a list of media reactions, community and mainstream, that may illuminate him. Please note that not a single one even mentions Novell, and every single one would provide a sensible man with a reason, I think, to avoid SCOsource.
I focused on 2003, for now, both before and after Novell's public statement. You can do the same for any year. Just go to Google News, choose your year and follow the trail, as I just did, and you'll be amazed how hard it is to find anyone even mentioning Novell as a reason not to buy a license.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

6 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Updating the license tag in XML file with new license

Hi All, I have a XML file : System.xml in which I want to update the license tag with the new data from file licence.xml. The content of files is in following format: System.xml: <?xml version="1.0"?> <!DOCTYPE Configuration SYSTEM "SystemVariables.dtd"> <usageConfiguration... (2 Replies)
Discussion started by: Pramod_T
2 Replies

2. Programming

Determining C/C++ License count

Can someone give me some guidance on what command to run to list how many compiler seats/licenses I am licensed for? This is an AIX system. Thanks, Justin ---------- Post updated 04-30-10 at 10:03 AM ---------- Previous update was 04-29-10 at 02:42 PM ---------- I can't believe nobody... (3 Replies)
Discussion started by: juredd1
3 Replies

3. Programming

Hi Folks please see the code and respond the questions!

Hi All. I have a package discreibed down. CREATE OR REPLACE PACKAGE BODY IRISCOS_REFRESH_pkg AS PROCEDURE IRISCOS IS CURSOR cur_pci(c_myear number) IS Select cstc.cid, cstc.elid, p.first_name,p.last_name,p.email_id ,pl.plan_name, ptc.chair_id from person p, person_to_chair ptc,... (7 Replies)
Discussion started by: Haque123
7 Replies

4. Programming

Hi Folks UTL_FILE Issue.

Hi Folks UTL_FILE Issue. I want to do detail study about the UTL FILE package could any one please provide me some of the best detail utl package links to go through and implement in my project will be very help full thanks a ton!!! Rgds Ann. (1 Reply)
Discussion started by: Haque123
1 Replies

5. IP Networking

netstat - possible reasons for high IP count ???

One of my servers started getting heavily loaded a few weeks ago for a few hours, so I did some studying and wrote a script to use netstat to get the IP addresses connected and the count. I put a new chain in iptables and if an IP is using more than 40 connections, it gets added to that chain which... (3 Replies)
Discussion started by: PWSwebmaster
3 Replies

6. UNIX for Dummies Questions & Answers

What do you Folks think??

Hi, I am currently in college and thought that I would go for an OCP ceritification....I know Windows fairly well, so I thought that I would learn it (oracle) Linux while I'm at it... My suSe 7.3 Pro came in the mail yesterday.... so I was curious if you folks could recommend a book that... (1 Reply)
Discussion started by: F4i_Rider
1 Replies
Login or Register to Ask a Question
funparamput(3)							SAORD Documentation						    funparamput(3)

NAME
FunParamPut - put a Funtools param value SYNOPSIS
#include <funtools.h> int FunParamPutb(Fun fun, char *name, int n, int value, char *comm, int append) int FunParamPuti(Fun fun, char *name, int n, int value, char *comm, int append) int FunParamPutd(Fun fun, char *name, int n, double value, int prec, char *comm, int append) int FunParamPuts(Fun fun, char *name, int n, char *value, char *comm, int append) DESCRIPTION
The four routines FunParamPutb(), FunParamPuti(), FunParamPutd(), and FunParamPuts(), will set the value of a FITS header parameter as a boolean, int, double, and string, respectively. The first argument is the Fun handle associated with the FITS header being accessed. Normally, the header is associated with the FITS extension that you opened with FunOpen(). However, you can use FunInfoPut() to specify that use of the primary header. In particular, if you set the FUN_PRIMARYHEADER parameter to 1, then the primary header is used for all parameter access until the value is reset to 0. For example: int val; FunParamPuti(fun, "NAXIS1", 0, 10, NULL, 1); # current header val=1; FunInfoPut(fun, FUN_PRIMARYHEADER, &val, 0); # switch to ... FunParamPuti(fun, "NAXIS1", 0, 10, NULL, 1); # primary header (You also can use the deprecated FUN_PRIMARY macro, to access parameters from the primary header.) The second argument is the name of the parameter. ( In accordance with FITS standards, the special names COMMENT and HISTORY, as well as blank names, are output without the "= " value indicator in columns 9 and 10. The third n argument, if non-zero, is an integer that will be added as a suffix to the parameter name. This makes it easy to use a simple loop to process parameters having the same root name. For example, to set the values of TLMIN and TLMAX for each column in a binary table, you can use: for(i=0; i<got; i++){ FunParamPutd(fun, "TLMIN", i+1, tlmin[i], 7, "min column val", 1); FunParamPutd(fun, "TLMAX", i+1, tlmax[i], 7, "max column val", 1); } The fourth defval argument is the value to set. Note that the data type of this argument is different for each specific FunParamPut() call. The comm argument is the comment string to add to this header parameter. Its value can be NULL. The final append argument determines whether the parameter is added to the header if it does not exist. If set to a non-zero value, the header parameter will be appended to the header if it does not exist. If set to 0, the value will only be used to change an existing parameter. Note that the double precision routine FunParamPutd() supports an extra prec argument after the value argument, in order to specify the precision when converting the double value to ASCII. In general a 20.[prec] format is used (since 20 characters are alloted to a floating point number in FITS) as follows: if the double value being put to the header is less than 0.1 or greater than or equal to 10**(20-2-[prec]), then %20.[prec]e format is used (i.e., scientific notation); otherwise %20.[prec]f format is used (i.e., numeric nota- tion). As a rule, parameters should be set before writing the table or image. It is, however, possible to update the value of an existing parame- ter after writing an image or table (but not to add a new one). Such updating only works if the parameter already exists and if the output file is seekable, i.e. if it is a disk file or is stdout being redirected to a disk file. It is possible to add a new parameter to a header after the data has been written, but only if space has previously been reserved. To reserve space, add a blank parameter whose value is the name of the parameter you eventually will update. Then, when writing the new param- eter, specify a value of 2 for the append flag. The parameter writing routine will first look to update an existing parameter, as usual. If an existing parameter is not found, an appropriately-valued blank parameter will be searched for and replaced. For example: /* add blank card to be used as a place holder for IPAR1 update */ FunParamPuts(fun, NULL, 0, "IPAR1", "INTEGER Param", 0); ... /* write header and data */ FunTableRowPut(fun, events, got, 0, NULL); ... /* update param in file after writing data -- note append = 2 here */ FunParamPuti(fun, "IPAR", 1, 400, "INTEGER Param", 2); The parameter routines return a 1 if the routine was successful and a 0 on failure. In general, the major reason for failure is that you did not set the append argument to a non-zero value and the parameter did not already exist in the file. SEE ALSO
See funtools(7) for a list of Funtools help pages version 1.4.2 January 2, 2008 funparamput(3)