Login or Register to Ask a Question and Join Our Community


UNIX and Linux RSS News

Novell Responds to SCO's Objections to its Bill of Costs

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News Novell Responds to SCO's Objections to its Bill of Costs
# 1  
Old 09-08-2010
Novell Responds to SCO's Objections to its Bill of Costs
Novell has responded to SCO's Objections to Novell's Bill of Costs for the two trials. Novell did not fail to notice and point out to the court SCO's cheeky move, asking that the court deny the entire bill, when some of it was costs from the first Utah trial that had already been authorized by the court:
SCO objects to $2,914.74 in costs for folders and binders, which were part of the copy costs. Rather than further dispute entitlement to such costs, Novell withdraws its request for them. However, SCO's assertion that because Novell failed to disaggregate these costs, the Court should "deny Novell's Bill of Costs in its entirety," is absurd. (Objections to Bill of Costs at 7.) Novell's Bill of Costs contains several entries that are not even addressed in SCO's Objections, not the least of which is $99,639.09 in costs that were previously awarded by the Court following the initial bench trial and simply have never been paid by SCO.
After the first trial, SCO objected to Novell's Bill of Costs, got it reduced, and then, despite the court ordering SCO to pay it, never did so. Now they ask that the court toss the bill overboard. Like I say, cheeky. I'm a little shocked that SCO's Chapter 11 Trustee Edward Cahn would allow such a request. SCO seems to show no sense of honor at all about its debts.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question

LEARN ABOUT NETBSD

ubt

UBT(4)							   BSD Kernel Interfaces Manual 						    UBT(4)

NAME

     ubt -- USB Bluetooth driver

SYNOPSIS

     ubt* at uhub? port ? configuration ? interface ?

DESCRIPTION

     The ubt driver provides support for USB Bluetooth dongles to the Bluetooth protocol stack.

     USB Bluetooth dongles provide two interfaces, both of which the ubt driver claims.  The second interface is used for Isochronous data and
     will have several alternate configurations regarding bandwidth consumption, which can be set using the hw.ubtN.config sysctl(8) variable.
     The number of alternate configurations is indicated by the value in the hw.ubtN.alt_config variable, and the isoc frame size for the current
     configuration is shown in the hw.ubtN.sco_rxsize and hw.ubtN.sco_txsize variables.

     By default, configuration 0 is selected, which means that no bandwidth is used on the Isochronous interface and no SCO data can be sent.
     Consult the Bluetooth USB specification at https://www.bluetooth.org/ for complete instructions on setting bandwidth consumption.	The fol-
     lowing extract may be useful as a general guidance though details may differ between manufacturers.

     0	  No active voice channels
     1	  One voice channel with 8-bit encoding
     2	  Two voice channels with 8-bit encoding, or one voice channel with 16-bit encoding.
     3	  Three voice channels with 8-bit encoding
     4	  Two voice channels with 16-bit encoding
     5	  Three voice channels with 16-bit encoding

SEE ALSO

     bluetooth(4), uhub(4), sysctl(8)

HISTORY

     This ubt device driver was originally a character device written by David Sainty and Lennart Augustsson.  It was rewritten to support socket
     based Bluetooth access for NetBSD 4.0 by Iain Hibbert.

CAVEATS

     Isochronous data is seemingly not well supported over USB in the current system and to get SCO working, you may have to calculate the SCO
     packet size that the stack will use.  This is the sco_mtu value reported by the btconfig(8) command, and when combined with the SCO header (3
     bytes) should fit exactly into an integer number of Isochronous data frames where the frame size is indicated by the 'hw.ubtN.sco_txsize'
     sysctl variable.

     For example: I want one voice channel (which is all that is supported, for now) so am using configuration #2, with a frame length of 17
     bytes.  This gives possible values of:

	   (17 * 1) - 3 = 14
	   (17 * 2) - 3 = 31
	   (17 * 3) - 3 = 48
	   (17 * 4) - 3 = 65
	   (17 * 5) - 3 = 82
	   etc.

     btconfig(8) shows the maximum SCO payload as 64 bytes, so I am using the next smaller size of 48, to minimize the overhead of the 3 header
     bytes.

     The SCO packet size can be changed using the 'scomtu' option to btconfig(8).

     The failure mode is that the USB Bluetooth dongle locks up though generally removal/reinsertion will clear the problem.

BUGS

     The Isochronous configuration can only be changed when the device is not marked up.

BSD
								  August 27, 2006							       BSD