Novell and SCO throw legal darts at each other's motions in limine

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News Novell and SCO throw legal darts at each other's motions in limine
# 1  
Old 02-20-2010
Novell and SCO throw legal darts at each other's motions in limine

It's a plot, I tell you! The parties in SCO v. Novell are trying to cause me to lose my beauty sleep. Before I can finish doing the text of one filing, they file 25 more. Literally. They have filed between them 25 memoranda in opposition to the others' motions in limine.
Say. They have finally hit on the way to shut Groklaw up. Just keep filing documents until I give up and go to sleep.
: D
I'm serious about the sleep part. What a week. So please help me out. Here are the 25 or so new memoranda in opposition to each others' motions in limine. Whatever you notice in your reading, tell the rest of us, as there is no way for me to read, transcribe, research, and then write about all of these. And if you can OCR or do HTML of any of them, please email your work to me or post it IF you carefully remove all addresses, phone numbers and email addressed first.

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)