Blank Rome Files Vague, Redacted Bills for March and April. Finally.

Special Forums News, Links, Events and Announcements UNIX and Linux RSS News Blank Rome Files Vague, Redacted Bills for March and April. Finally.

11-16-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

Blank Rome Files Vague, Redacted Bills for March and April. Finally.

Blank Rome has finally filed its bills for March and April. Yes. March. April. I'd suggest they'd rather we not watch them in real time. Or too closely period. The SCO bottom line does look better, one assumes, if bills for March through November are not yet included in the spreadsheet.
What stands out, though, is these are the first bills I recall in the bankruptcy that are redacted in places.

More...

Linux Bot

View Public Profile for Linux Bot

Find all posts by Linux Bot

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. Fedora

uname too vague?

Hi all, I am ssh'ed into a cluster and want to install a package. However, I don't know which type to chose (CentOS, Fedora, OpenSuSE are some of the options). I ran called uname with various arguments but none are specific... $ uname -n resolute.research... $ uname -i x86_64 $ uname...

LEARN ABOUT XFREE86

ucom

UCOM(4) 						   BSD Kernel Interfaces Manual 						   UCOM(4)

NAME

     ucom -- USB tty support

SYNOPSIS

     To compile this driver into the kernel, place the following line in your kernel configuration file:

	   device ucom

     Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):

	   ucom_load="YES"

DESCRIPTION

     The ucom driver attaches to USB modems, serial ports, and other devices that need to look like a tty.  The ucom driver shows a behavior like
     a tty(4).	This means that normal programs such as tip(1) or pppd(8) can be used to access the device.

     The portno locater can be used to decide which port to use for devices that have multiple external ports.

BUGS

     Prior to FreeBSD 6.0 ucom created /dev/ucom? rather than the uniform device names created today.  Old scripts must be adjusted accordingly.

FILES

     /dev/cuaU?

     /dev/ttyU?

SEE ALSO

     tty(4), uark(4), uchcom(4), uftdi(4), umct(4), umodem(4), uplcom(4), usb(4), uvisor(4), uvscom(4)

HISTORY

     The ucom driver was adopted from NetBSD in March of 2002.	This manual page was adopted from NetBSD by Tom Rhodes <trhodes@FreeBSD.org> in
     April 2002.

BSD
								   March 1, 2008							       BSD

UNIX and Linux RSS News