SCO's Opposition to Novell's Motion in Limine No. 1: Hey! No Fair, You Guys!

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News SCO's Opposition to Novell's Motion in Limine No. 1: Hey! No Fair, You Guys!
# 1  
Old 02-13-2010
SCO's Opposition to Novell's Motion in Limine No. 1: Hey! No Fair, You Guys!

SCO has filed its response to Novell's Motion in Limine No. 1. And Novell has added another lawyer to the team, Daniel P. Muino.
SCO's opposition in essence says, "No fair, Novell! We appealed the copyright ownership issue, and the slander of title is sort of related, and so that should be enough."
Here's what I don't see SCO saying: "We *did* appeal the slander of title decision."
They can't say that, because it isn't listed. It would like us all to infer it. Maybe the judge will, but I find that argument a stretch, given that there are rules and all. Oh, that. Anyway, SCO argues, Novell used to say that slander of title was back on the table, so now it's changing. Like SCO never has done that. I recall it saying one thing in the AutoZone courtroom, another in the IBM courtroom and another in Red Hat, pretty much all at the same time. Isn't that your memory too? But in any case, Novell agrees that it has changed. It told Judge Ted Stewart that it thought a number of claims were back on the table, until it read Judge Ted Stewart's words in denying Novell's 60(b) motion, stating that the 10th Circuit Court of Appeals mandated what items could be considered and no others.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
IPX_CMD(8)						      System Manager's Manual							IPX_CMD(8)

NAME
ipx_cmd - bridge between Novell's SCMD driver and local IPX network SYNOPSIS
ipx_cmd -A server name [ -l local interface name ] DESCRIPTION
ipx_cmd moves packets from tapN to server and vice versa. It is something like IPX Tunnel, but it uses Novell Netware 5 server Compatibil- ity Mode Driver (AKA Migration Agent) on the other end of wire. You must first configure your kernel tapN device with IPX EthernetII frame and with network number set up on server (you can use kernel autodetection). OPTIONS
-A server name This is IP name of compatibility mode server. You can use DNS name or dotted quad to specify server address. -l local interface name This allows you to specify, which of your IP addresses should be used as IP address of client side of CMD driver. You must configure your tapN device with hardware address 7E:01:AA:BB:CC:DD, where AA:BB:CC:DD is your IP address in hexa. EXAMPLE
If you are on server platan.vc.cvut.cz (147.32.240.81) and your migration agent runs on server boris.vc.cvut.cz, you can configure your system with: insmod ethertap ifconfig tap0 hw ether 7E:01:93:20:F0:51 up ipx_interface add -p tap0 EtherII ipx_cmd -A boris.vc.cvut.cz -l 147.32.240.81 & BUGS
This program was written to satisfy my own needs and should be really improved. At least it should configure tap interface itself. AUTHOR
Petr Vandrovec <vandrove@vc.cvut.cz> ipx_cmd IPX Utilities IPX_CMD(8)