Day 9 of the SCO v. Novell Trial, March 18, 2010, Part 2 - The Jury Gets to Learn About Earlier SCO

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News Day 9 of the SCO v. Novell Trial, March 18, 2010, Part 2 - The Jury Gets to Learn About Earlier SCO
# 1  
Old 10-12-2010
Day 9 of the SCO v. Novell Trial, March 18, 2010, Part 2 - The Jury Gets to Learn About Earlier SCO

Let's continue with the second part of the events of Day 9 at the second SCO v. Novell trial, before the Hon. Ted Stewart, a continuation of this article, part 1, where you'll find the complete transcript as text. We ran out of space, so you may want to open up the previous article alongside this one, so you can follow along with the transcript.
So we're still talking about the events on March 18, 2010. When we left off, Dr. Christine Botosan was on the stand, enduring cross examination by Novell's lawyer, Sterling Brennan. I do mean enduring, because she was very much on the defensive, and as you will see, it gets worse for her.
We'll pick up the narrative right after the court has taken a break. When the judge returns, but before the jury is brought back, he brings up again his decision to let Novell mention the previous Judge Dale Kimball rulings against SCO in this case. SCO in its appeal is claiming it was error to let the jury hear about all that, so let's focus on that part especially.

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