From: ebiederm@xmission.com (Eric W. Biederman)
To: jmerkey@wolfmountaingroup.com
Cc: "Theodore Tso" <tytso@mit.edu>, "Rik van Riel" <riel@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [REQUEST] Clarification from Copyright Holders on FUSE/NDISWRAPPER
Date: Mon, 29 Sep 2008 21:06:11 -0700 [thread overview]
Message-ID: <m1bpy68eh8.fsf@frodo.ebiederm.org> (raw)
In-Reply-To: <49203.166.70.238.43.1222658858.squirrel@webmail.wolfmountaingroup.com> (jmerkey@wolfmountaingroup.com's message of "Sun, 28 Sep 2008 21:27:38 -0600 (MDT)")
jmerkey@wolfmountaingroup.com writes:
> Don't get me wrong, I love working on Linux and the debugger, but I think
> its ill advised to use it in any commercial venture where proprietary
> technology is being developed -- it's risky these days.
Yep. Business is risky and hard.
Eric
next prev parent reply other threads:[~2008-09-30 4:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-28 17:15 [REQUEST] Clarification from Copyright Holders on FUSE/NDISWRAPPER jmerkey
2008-09-28 19:45 ` Theodore Tso
2008-09-28 19:24 ` jmerkey
2008-09-28 23:46 ` Rik van Riel
2008-09-28 23:34 ` jmerkey
2008-09-29 1:57 ` Theodore Tso
2008-09-29 3:27 ` jmerkey
2008-09-30 4:06 ` Eric W. Biederman [this message]
2008-09-30 4:18 ` jmerkey
2008-10-05 10:12 ` Pavel Machek
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=m1bpy68eh8.fsf@frodo.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=jmerkey@wolfmountaingroup.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.com \
--cc=tytso@mit.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox