Changes and Additional Documents to the Yarro Deal Filed

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News Changes and Additional Documents to the Yarro Deal Filed
# 1  
Old 03-04-2010
Changes and Additional Documents to the Yarro Deal Filed

There are more filings in the bankruptcy, related to the proposed Yarro deal, and because that hearing is coming up soon, on Friday, I'm posting them quickly, before even reading them myself. Specifically, there are proposed changes to the deal, so take a look. Exhibit A is the redlined draft. Exhibit F is "proof" that Seung Ni Capital, LLC actually exists, or at least that it has written up Articles of Organization. It's a Utah LLC. Or at least the page we get to see has a stamp "Received - Mar 01 2010 - Utah Tax Commission [address]."
I'm starting to get the impression that they don't want us to have time to actually read and think about this super-fast proposed deal.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

5 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

2 (two) here documents in a row

Ok, it may sound a bit stupid but I can't find the answer.. How do one put 2 here documents in a row? for instance, i want to do something like: diff <<eof <<eof2 # doesn't work... > a > b > eof > a > c > eof2 its mostly to satisfy my curiosity!! thanks, Anthony (4 Replies)
Discussion started by: anthalamus
4 Replies

2. Linux

The LimitRequestBody filed in openSUSE 10.2

Because some program i have installed can not upload files bigger than some size as printing, the base got a packet bigger than 'max_allowed_packet' bytes what that i need to do as written in the documentation of the program increase the value of a fileld called LimitRequestBody told that is in... (5 Replies)
Discussion started by: tal
5 Replies

3. UNIX for Dummies Questions & Answers

The LimitRequestBody filed in openSUSE 10.2

Because some program i have installed can not upload files bigger than some size as printing, the base got a packet bigger than 'max_allowed_packet' bytes what that i need to do as written in the documentation of the program increase the value of a fileld called LimitRequestBody told that is in... (3 Replies)
Discussion started by: tal
3 Replies

4. Shell Programming and Scripting

deleting pipes in a particular filed

i have a file with some records seperated by pipe. I am getting unwanted "|" in the 7th field and i want to remove any pipes in the 7th field only. Can somebody help out? Here is the sample record. 460625192|432559595|MANU... (3 Replies)
Discussion started by: dsravan
3 Replies

5. Shell Programming and Scripting

Filed substitution with awk

guys, I'm trying to 9k lines of the following: aaa aaa 1 1 1 to aaa aaa 1 01 1 Im pretty ignorant when it comes to subtituting fields using awk any help ? Tony (1 Reply)
Discussion started by: tony3101
1 Replies
Login or Register to Ask a Question
Specific(3pm)						User Contributed Perl Documentation					     Specific(3pm)

NAME
Coro::Specific - manage coroutine-specific variables. SYNOPSIS
use Coro::Specific; my $ref = new Coro::Specific; $$ref = 5; print $$ref; DESCRIPTION
This module can be used to create variables (or better: references to them) that are specific to the currently executing coroutine. This module does not automatically load the Coro module (so the overhead will be small when no coroutines are used). A much faster method is to store extra keys into %$Coro::current - all you have to do is to make sure that the key is unique (e.g. by prefixing it with your module name). You can even store data there before loading the Coro module - when Coro is loaded, the keys stored in %$Coro::current are automatically attached to the coro thread executing the main program. You don't have to load "Coro::Specific" manually, it will be loaded automatically when you "use Coro" and call the "new" constructor. new Create a new coroutine-specific scalar and return a reference to it. The scalar is guarenteed to be "undef". Once such a scalar has been allocated you cannot deallocate it (yet), so allocate only when you must. BUGS
The actual coroutine specific values do not automatically get destroyed when the Coro::Specific object gets destroyed. AUTHOR
Marc Lehmann <schmorp@schmorp.de> http://home.schmorp.de/ perl v5.14.2 2012-04-13 Specific(3pm)