All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jeff V. Merkey" <jmerkey@drdos.com>
To: jonathan@jonmasters.org
Cc: brian wheeler <bdwheele@indiana.edu>, linux-kernel@vger.kernel.org
Subject: Re: Linux v2.6.9 and GPL Buyout
Date: Fri, 22 Oct 2004 18:02:48 -0600	[thread overview]
Message-ID: <41799FA8.3010803@drdos.com> (raw)
In-Reply-To: <35fb2e59041022173042f92fa@mail.gmail.com>

Jon Masters wrote:

>On Fri, 22 Oct 2004 16:58:54 -0600, Jeff V. Merkey <jmerkey@drdos.com> wrote:
>  
>
>>Jon Masters wrote:
>>
>>    
>>
>>>Jeff,
>>>
>>>Could you please digitally sign this mail that you are planning to
>>>send or otherwise provide notorisation that confirms you definately
>>>mean this?
>>>
>>>I'd love for you to accept liability for this so we can pass all SCO
>>>enquiries on to you.
>>>
>>>Jon.
>>>      
>>>
>
>  
>
>>Yes. I can do even better.
>>    
>>
>
>Ok. But I need you to sign this using some recognised signature -
>other folks can suggest mechanisms we can use that are legally valid.
>I'm happy to act as a gobetween if we could get you to undertake to
>accept liability for any infringing code left in the kernel after any
>proven SCO demands were to be met (I'm sure other folks can see where
>I'm going with this discussion - let's see what the response is).
>  
>

I would agree to this. I will meet with SCO Monday and see if they will 
accept this as a proposal. I think
they probably will.

>  
>
>>I met with Darl McBride this afternoon
>>    
>>
>
>Did you have tea and crumpets? Jam?
>
>  
>
They gave me raw carrots (in a plastic bag on Blake's desk) and Baby 
Ruth candy bars. We met in
Blake's office (The PR Guy). They had their corporate counsel sitting in 
another room and I guess he was
listenting in or something, but he never entered the room. We talked 
about the Novell/Bill Mason/Pamela Jones/Groklaw
connections (all of these people are ex Novell employees). I was met at 
the front door door by Joan (Darl's
admin) and Blake, then Darl came into the Blakes office. They typed a 
letter first roasting GrokLaw then the
SCO general counsel said not to sign it even though Darl wanted him to, 
and they said to have Blake put out
some sort of release instead. Then Darl and I talked about all the Linux 
code for about an hour or so.


>>He gave me the first list, and I am waiting on the second
>>    
>>
>
>Like I said, if you could provide this to me with legally valid,
>documented proof that you'll accept liability for further infringement
>then that would help greatly with this thread.
>
>  
>

Yes. I am waiting for them to send it. I called Joan and Darl after I 
sent this and Darl had left for the day
and Joan called him on his cell phone and I am supposed to talk to Blake 
on Monday.

>>I don't think he likes Linux much
>>    
>>
>
>That surprises me. I thought Darl loved Linux more than life itself -
>thanks for the correction.
>
>  
>
>>I will have it probably Monday. I'll post it then.
>>    
>>
>
>If you mail it to me at: jcm@jonmasters.org along with some contact
>details then I can arrange to have you mail me a signed declaration
>accepting liability.
>
>  
>

Agreed. I will do so. I think SCO just wants their stuff our of Linux. 
We should accomodate them.
Who wants to use this stuff besides IBM anyway.

>>Darl seemed like a nice enough sort
>>    
>>
>
>I'd love to interview the guy, if he were interested.
>
>  
>

I could ask him...

>>We argued for 30 minutes about SMP support in Linux and I think
>>he will just let this one go since I pointed out that Novell had
>>disclosed the Unixware SMP stuff at Brainshare and he
>>cannot claim it as trade secrete any longer.
>>    
>>
>
>That's interesting. Can you commit to that too in your declaration please?
>  
>
Yes.

>>and he would claim any contribution from any IBM employee in Linux.
>>    
>>
>
>Were there any restrictions upon when that person was an employee?
>  
>

Yes. He said any employee who had access to their source code and who 
fell under the license agreements. It was
somewhat nebulous, and form the way he explained it, the agreements with 
IBM pretty much covered all employees
everywhere. There was some sort of non-compete clause so I think this 
affects everyone.

>  
>
>>I will post to kernel.org the complete listing.
>>    
>>
>
>Thanks. I look forward to reading that.
>  
>

You got it.

Jeff


  reply	other threads:[~2004-10-23  0:45 UTC|newest]

Thread overview: 116+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-22 21:31 Linux v2.6.9 and GPL Buyout brian wheeler
2004-10-22 21:27 ` Jeff V. Merkey
2004-10-22 23:03   ` Jon Masters
2004-10-22 22:58     ` Jeff V. Merkey
2004-10-22 23:27       ` Jeff V. Merkey
2004-10-23 13:30         ` Denis Vlasenko
2004-10-24 11:10         ` Matthias Andree
2004-10-23  0:24       ` David Schwartz
2004-10-23  0:48         ` Jon Masters
2004-10-23  0:30       ` Jon Masters
2004-10-23  0:02         ` Jeff V. Merkey [this message]
2004-10-23  1:18           ` Diego Calleja
2004-10-23  8:43       ` Thomas Gleixner
2004-10-23 16:13         ` Giuseppe Bilotta
2004-10-23 12:59   ` Bernd Petrovitsch
2004-10-24 11:04   ` Matthias Andree
  -- strict thread matches above, loose matches on Subject: below --
2004-10-24 19:38 Xose Vazquez Perez
2004-10-24  8:45 Shawn Starr
2004-10-22 19:38 Jeff V. Merkey
2004-10-18 22:45 Linux v2.6.9 Linus Torvalds
2004-10-19 17:38 ` Linux v2.6.9 and GPL Buyout Jeff V. Merkey
2004-10-19 19:13   ` Russell King
2004-10-19 19:04     ` Jeff V. Merkey
2004-10-19 19:24   ` Kurt Wall
2004-10-19 19:12     ` Jeff V. Merkey
2004-10-19 20:01     ` Richard B. Johnson
2004-10-19 20:39       ` Matt Mackall
2004-10-20  0:06         ` Richard B. Johnson
2004-10-20  5:21           ` Matt Mackall
2004-10-19 19:28   ` Andre Hedrick
2004-10-19 19:10     ` Jeff V. Merkey
2004-10-19 19:30   ` Rik van Riel
2004-10-19 19:05     ` Jeff V. Merkey
2004-10-19 20:14       ` Diego Calleja
2004-10-19 19:41         ` Jeff V. Merkey
2004-10-20  8:27           ` Bernd Petrovitsch
2004-10-20  8:45             ` Jens Axboe
2004-10-19 19:47         ` Jeff V. Merkey
2004-10-19 20:05     ` Richard B. Johnson
2004-10-19 19:38       ` Jeff V. Merkey
2004-10-19 20:30         ` Thomas Gleixner
2004-10-19 20:15           ` Jeff V. Merkey
2004-10-22 23:22           ` Tonnerre
2004-10-19 19:45   ` Ross Biro
2004-10-19 19:36     ` Jeff V. Merkey
2004-10-19 19:54   ` David Johnson
2004-10-19 19:55   ` viro
2004-10-19 19:25     ` Jeff V. Merkey
2004-10-19 20:38   ` Dax Kelson
2004-10-19 20:09     ` Jeff V. Merkey
2004-10-19 22:16       ` Jim Nelson
2004-10-19 22:57         ` Bernd Petrovitsch
2004-10-19 22:27       ` Scott Robert Ladd
2004-10-20 19:41         ` Bill Davidsen
2004-10-20  1:15       ` Horst von Brand
2004-10-20  1:16       ` Bastiaan Spandaw
2004-10-20 19:35         ` Bill Davidsen
2004-10-20  3:45       ` Ryan Anderson
2004-10-20  4:18         ` Lee Revell
2004-10-20  4:41           ` Lee Revell
2004-10-20 11:49             ` Richard B. Johnson
2004-10-20  5:58           ` John Alvord
2004-10-20 14:42           ` Martin Waitz
2004-10-21 23:59       ` Kelledin
2004-10-22  8:46       ` Bernd Petrovitsch
2004-10-22  9:07       ` David Weinehall
2004-10-22 16:15         ` Jeff V. Merkey
2004-10-22 17:52           ` Al Viro
2004-10-22 17:22             ` Jeff V. Merkey
2004-10-22 19:37               ` Jeff V. Merkey
2004-10-22 20:46                 ` Grahame White
2004-10-22 20:58                 ` Buddy Lucas
2004-10-22 21:00                 ` Richard B. Johnson
2004-10-22 21:03                 ` Thomas Gleixner
2004-10-23 12:33                 ` Bernd Petrovitsch
2004-10-24 14:15                 ` Kai Henningsen
2004-10-27  1:45                 ` Horst von Brand
2004-10-24 11:00           ` Matthias Andree
2004-10-24 14:13           ` Kai Henningsen
2004-10-25 18:44             ` Bill Davidsen
2004-10-20 19:46     ` Bill Davidsen
2004-10-19 21:02   ` Pekka Pietikainen
2004-10-19 20:27     ` Jeff V. Merkey
2004-10-22  6:54       ` Erik Andersen
2004-10-22 16:12         ` Jeff V. Merkey
2004-10-19 21:17     ` Paul Fulghum
2004-10-20 20:41     ` Geert Uytterhoeven
2004-10-23 13:43       ` James Bruce
2004-10-19 21:26   ` Ramón Rey Vicente
2004-10-19 22:52   ` Buddy Lucas
2004-10-20 23:43   ` Eric Bambach
2004-10-20 23:48     ` Eric Bambach
2004-10-20 23:59     ` Hua Zhong
2004-10-21  0:13     ` Russell Miller
2004-10-21  0:18       ` Adam Heath
2004-10-21 10:16       ` Horst von Brand
2004-10-22  8:48   ` Ingo Molnar
2004-10-22 16:15     ` Jeff V. Merkey
2004-10-23  0:14   ` Jon Masters
2004-10-22 23:46     ` Jeff V. Merkey
2004-10-23  0:57       ` Jon Masters
2004-10-23  4:42         ` Jeff V. Merkey
2004-10-23  6:32           ` Nick Piggin
     [not found]             ` <20041023064538.GA7866@galt.devicelogics.com>
2004-10-23  7:20               ` Jeff V. Merkey
2004-10-23 10:11           ` Gene Heskett
2004-10-23 16:28           ` Linus Torvalds
2004-10-24  2:48             ` Jesper Juhl
2004-10-24  5:11             ` Jeff V. Merkey
2004-10-24 11:14               ` Jon Masters
2004-10-24 11:50               ` Jim Nelson
2004-10-24 15:35               ` Ingo Molnar
2004-10-24 15:53               ` Bernd Petrovitsch
2004-10-31 23:14               ` Jan 'JaSan' Sarenik
2004-10-24  2:11           ` Buddy Lucas
2004-10-23  0:38     ` Lee Revell
2004-10-23  0:07       ` Jeff V. Merkey
2004-10-23  1:06         ` Lee Revell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=41799FA8.3010803@drdos.com \
    --to=jmerkey@drdos.com \
    --cc=bdwheele@indiana.edu \
    --cc=jonathan@jonmasters.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.