All the virus-bounces I'm receiving are from brain-dead ISP's trying to filter and send out "helpful" messages to people who, because of forgery, didn't send the offending email in the first place.
You'd think an ISP could do better, but since the worst of them begins with an "A" and ends with an "L", I'm not surprised...
SCO makes no guarantees or commitments that any SOURCE CODE PRODUCT is available from SCO. If available, SCO will, within a reasonable time after SCO receives the fee specified in this
Agreement for a SOURCE CODE PRODUCT, furnish to LICENSEE one (1) copy of such SOURCE CODE PRODUCT."
So it seems like they're saying, "Yeah, we'll take a hundred buck from ya, but we're not guaranteeing that you'll get anything in return. Maybe we'll send you something, if it's available..."
"...You can pay by VISA, MasterCard, or American Express credit card if you choose. Quote your credit card details in the cover note, if you are paying by this method, and authorize SCO to withdraw US$100 from your card..."
"... Wait for a response. SCO will try to respond within 3 weeks. If you have any questions about the license or its status, contact..."
...the first substantive instance of the thought I've had all along, here..
"...Linus Torvalds found a Linux-kernel mailing list (lkml) posting from Christoph Hellwig, a former employee at SCO, then called Caldera. Hellwig pointed out the impracticality of actually getting copied code from UnixWare accepted by the tough critics on the mailing list. "The kernel internals are so different that you'd need a big glue layer to actually make it work and you can guess how that would be ripped apart in a usual lkml review," Hellwig wrote..."
"...what they did is lift 5 to 10 to 15 lines of code from multiple parts of linux and place it into SCO owned code and then simply claim that it was stolen from them..."
I just created this theory, (see down below a ways..) and you haven't gotten in touch with my attorney, Bernie, for rights to reproduction.
...about what SCO is saying the more I think that they need some time to fabricate similarites between their source code and Linux, not demonstrate that it's the other way around.
Or am I missing something:
"...We will actually be showing the code, and the basis for why we have made the allegations that we have. We are very confident about our case. Because we are dealing with confidential source code that we have never released without confidentiality agreements, we will have to put in place nondisclosures [agreements] simply to protect the source..."
That's the SCO source code he's talking about.
And they need the time to re-write *it* to contain fragments of Linux.
That's why they can't release any "proof" just yet.
And of course, no one will generally know what they've done, because SCO's source hasn't been released before their big date..
So they release their source, say "Hey! look! Linux is just like ours code! See! Here and here and here..."
Slashdot Mirror
Windows is not.
Window$ doesn't have a kernel; a rat's nest, maybe, but certainly not a kernel...
t_t_b
t_t_b
Read More... | 268 of 686 comments
Looks like it worked...
t_t_b
All the virus-bounces I'm receiving are from brain-dead ISP's trying to filter and send out "helpful" messages to people who, because of forgery, didn't send the offending email in the first place.
You'd think an ISP could do better, but since the worst of them begins with an "A" and ends with an "L", I'm not surprised...
t_t_b
"...so that one can run Windows 9x (95/98/Me) inside GNU/Linux..."
Why in god's name would you ever want to?
t_t_b
"4. DELIVERY
SCO makes no guarantees or commitments that any SOURCE CODE PRODUCT is available from SCO. If available, SCO will, within a reasonable time after SCO receives the fee specified in this Agreement for a SOURCE CODE PRODUCT, furnish to LICENSEE one (1) copy of such SOURCE CODE PRODUCT."
So it seems like they're saying, "Yeah, we'll take a hundred buck from ya, but we're not guaranteeing that you'll get anything in return. Maybe we'll send you something, if it's available..."
They were a bunch of pricks back then, too..
t_t_b
"...You can pay by VISA, MasterCard, or American Express credit card if you choose. Quote your credit card details in the cover note, if you are paying by this method, and authorize SCO to withdraw US$100 from your card..."
"... Wait for a response. SCO will try to respond within 3 weeks. If you have any questions about the license or its status, contact..."
Pay one hundred bucks and wait three weeks...
t_t_b
Down towards the bottom.
t_t_b
Stop right there.
t_t_b
My last exposure to QBasic was in about 1996 or 1997, teaching a programming class to fourth graders.
Is today April 1?
Is this guy serious?
t_t_b
You *still* need to get a life.
t_t_b
*You* have solved *your* spam problem.
*You* are not the center of the universe.
Your attitude is: "Problem? What problem? I don't see no stinkin' problem."
Your self-centered approach is tantamount to those who say "There's no traffic congestion on our freeways! I ride my bike to work!"
Open your eyes and try to look beyond your little world.
t_t_b
That's it?
Give me a break.
*Which* 80 lines?
I continue to refuse to buy into a bit of this.
SCO is dead meat, and good ridance..
t_t_b
Funny you mention this!
I actually sysadmin'ed a POS system at an auto parts store for about a year, around 1987..
The OS?
SCO Xenix, running on an NEC 80386..
A-Plus was the software, if memory serves, but that was a *long* time ago...
The cash drawer was kinda funky on that system, too...
t_t_b
"...Linus Torvalds found a Linux-kernel mailing list (lkml) posting from Christoph Hellwig, a former employee at SCO, then called Caldera. Hellwig pointed out the impracticality of actually getting copied code from UnixWare accepted by the tough critics on the mailing list. "The kernel internals are so different that you'd need a big glue layer to actually make it work and you can guess how that would be ripped apart in a usual lkml review," Hellwig wrote..."
t_t_b
Not issuing a recall just means they're still in denial.
t_t_b
I've a suggestion for you.
It's called reading.
It's a great prevention for foot-in-mouth disease...
t_t_b
t_t_b
Just one minute!
"...what they did is lift 5 to 10 to 15 lines of code from multiple parts of linux and place it into SCO owned code and then simply claim that it was stolen from them..."
I just created this theory, (see down below a ways..) and you haven't gotten in touch with my attorney, Bernie, for rights to reproduction.
Expect a call from him, right quick!
t_t_b
t_t_b
Or am I missing something:
"...We will actually be showing the code, and the basis for why we have made the allegations that we have. We are very confident about our case. Because we are dealing with confidential source code that we have never released without confidentiality agreements, we will have to put in place nondisclosures [agreements] simply to protect the source..."
That's the SCO source code he's talking about.
And they need the time to re-write *it* to contain fragments of Linux.
That's why they can't release any "proof" just yet.
And of course, no one will generally know what they've done, because SCO's source hasn't been released before their big date..
So they release their source, say "Hey! look! Linux is just like ours code! See! Here and here and here..."
Anyway: + 5 points: cool conspiracy theory
t_t_b
You're full of shit.
And you don't even have the balls to post as anything but an AC
feh..
t_t_b
t_t_b
$SEX!=$LOVE
(and thank god, I sez...)
t_t_b
t_t_b