Novell Files Its Appeal Brief in SCO v. Novell - Updated as text

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News Novell Files Its Appeal Brief in SCO v. Novell - Updated as text
# 1  
Old 10-30-2010
Novell Files Its Appeal Brief in SCO v. Novell - Updated as text

Here it is, Novell's appeal brief in SCO v. Novell. It's responsive to SCO's earlier filing, which you can find in our permanent Novell Appeals page.
Novell's fundamental argument is that SCO was given its jury trial, and now it wants to retry the case all over again to the appeals court. That is what it is not allowed to do:
SCO now seeks to undo the factual findings of the jury and judge. Throughout its brief, SCO makes arguments based on its version of events-a version that would require that factual findings below be ignored or reversed. But SCO is not entitled to re-try its case in this Court. Instead, SCO must demonstrate the jury's verdict and the district court's factual findings were unreasonable and unsupported by the evidence. That SCO utterly fails to do. To the contrary, the findings below were consistent with the evidence, and thus should not be disturbed on appeal.
We'll work on getting a text version for you soon, but this will get you started.

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)