SCO Files July MORs

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News SCO Files July MORs
# 1  
Old 09-25-2010
SCO Files July MORs

Finally, SCO filed its MORs for July. Is anybody noticing they don't seem to be reorganizing?
I need to lighten up, yo. This is *bankruptcy* court, and your checkbook isn't supposed to balance out. Just spend, spend, spend, and who's to check your hand? You want 4 hotels on Park Place and 6 houses on Baltic Avenue? Why not? No one will ever hold you accountable. It's not like us little people, who have to, you know, pay our debts and all.
Page 16 says that professional fees for July were $340,960. For one month. That is more than SCO paid its employees and more than it made in net profit from the business that month, but who's counting? Obviously not the US Bankruptcy Court in Delaware.
Guess how much the professional fees total since bankruptcy began? $5,738,877. It means, as I read it, that instead of paying Novell what SCO owes in damages, it paid professionals to help them try to avoid it.
Then there's the millions for the IBM and Novell litigation, if I've read these MORs right.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
BTSCO(4)						   BSD Kernel Interfaces Manual 						  BTSCO(4)

NAME
btsco -- Bluetooth SCO Audio SYNOPSIS
btsco* at bthub? audio* at audiobus? DESCRIPTION
The btsco driver provides support for Bluetooth SCO Audio devices through the audio(4) driver. The btsco driver must be configured at run time with the btdevctl(8) program. The following properties are used by the btsco driver during autoconfiguration: local-bdaddr Local device address. remote-bdaddr Remote device address. service-name The btsco driver matches the 'HF' and 'HSET' services. For the 'HF' service, the btsco device will, on open(2), listen for incom- ing connections from the remote device. Otherwise, btsco will attempt to initiate a connection to the remote device. rfcomm-channel This integer value is not used directly, but will be stored and passed via the BTSCO_INFO ioctl as below: SCO connections require a baseband connection between the two devices before they can be created. The btsco driver does not create this, but can provide information to facilitate an application setting up a control channel prior to use, via the BTSCO_INFO ioctl(2) call on the mixer device, which returns a btsco_info structure as follows: #include <dev/bluetooth/btsco.h> struct btsco_info { bdaddr_t laddr; /* controller bdaddr */ bdaddr_t raddr; /* headset bdaddr */ uint8_t channel; /* RFCOMM channel */ int vgs; /* mixer index speaker */ int vgm; /* mixer index mic */ }; #define BTSCO_INFO _IOR('b', 16, struct btsco_info) The btsco driver can be configured to act in Connect or Listen mode. In Connect mode, the btsco driver will initiate a connection to the remote device on an open(2) call, whereas in Listen mode, open(2) will block until the remote device initiates the connection. SEE ALSO
bthset(1), ioctl(2), audio(4), bluetooth(4), bthub(4), btdevctl(8) HISTORY
The btsco driver was written for NetBSD 4.0 by Iain Hibbert under the sponsorship of Itronix, Inc. BUGS
btsco takes no notice of the HCI Voice Setting in the Bluetooth controller, and this must be 0x0060 (the default) as alternate values are currently unsupported. BSD
October 4, 2006 BSD