EMC Objects to SCO's Cure Amount and a Tiny Bill from Tanner Arrives

10-22-2010

Registered User

26,240, 27

Join Date: Sep 2000

Last Activity: 1 August 2008, 3:09 PM EDT

Posts: 26,240

Thanks Given: 0

Thanked 27 Times in 26 Posts

EMC Objects to SCO's Cure Amount and a Tiny Bill from Tanner Arrives

All the intricacies of SCO never alter the big picture, do they? The first objection has arrived to SCO's recently-filed cure amounts. And shades of DaimlerChrysler, check out the reason:

As agent for the creditor, EMC Corporation ("EMC") who acquired Data General Corporation ("DGC"), we object to the Debtors' proposed assignment and cure amount for a "Source License Agreement" with DGC. EMC is not aware of an ongoing contractual arrangement with the Debtors. In fact, service and maintenance support between the parties stopped almost two (2) years ago.

In order to properly evaluate the assumption and cure, EMC will need the Source License Agreement, together with a list of all equipment related to the Agreement. Without this information, EMC cannot agree to anything.

Funny, no? What license agreement? Nothing ever really changes in the SCOniverse. And the cherry on top is that the letter comes from Receivables Management Services, and so their letterhead shows a big RMS. If you put that in a movie, unless you were Groucho, people would say you were over the top silly.

More...

Linux Bot

View Public Profile for Linux Bot

Find all posts by Linux Bot

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

UNIX and Linux RSS News

EMC Objects to SCO's Cure Amount and a Tiny Bill from Tanner Arrives

LEARN ABOUT NETBSD

btsco