From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
Cc: "Theodore Y. Ts'o" <tytso@MIT.EDU>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
pavel@suse.cz, kernel@blackhole.compendium-tech.com,
hps@tanstaafl.de, linux-kernel@vger.kernel.org,
jmerkey@timpanogas.org
Subject: Re: Fasttrak100 questions...
Date: Tue, 5 Dec 2000 01:07:30 -0600 [thread overview]
Message-ID: <20001205010730.A5760@openss7.org> (raw)
In-Reply-To: <20001202182126.A20944@vger.timpanogas.org> <200012030342.WAA17517@tsx-prime.MIT.EDU> <20001202221146.A21761@vger.timpanogas.org>
In-Reply-To: <20001202221146.A21761@vger.timpanogas.org>; from jmerkey@vger.timpanogas.org on Sat, Dec 02, 2000 at 10:11:46PM -0700
Jeff,
Have you also seen this applied where it is to the employer's
disadvantage? For example, given that I looked at and worked
with GPL code (say Linux kernel) in University before taking
employment as a programmer that the employer's product is
inevitably contaiminated and no longer a trade secret? Can
a previous employee get an injunction against their former
employer to cease and desist from using this negative knowledge?
If so, I might have a solution: make the Linux kernel required
reading in University programming classes!
On Sat, 02 Dec 2000, Jeff V. Merkey wrote:
> On Sat, Dec 02, 2000 at 10:42:29PM -0500, Theodore Y. Ts'o wrote:
> > Date: Sat, 2 Dec 2000 18:21:26 -0700
> > From: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
> >
> > Under this argument, it is argued that the engineer who had source
> > code access "inevitably used" negative knowledge he gained from
> > his study of the Linux sources. Absent the vague descriptions of
> > what a "derivative work" is in the GPL, it could be argued that
> > conversion of any knowledge contained in GPL code is a "derivative
> > work".
> >
--
Brian F. G. Bidulock ¦ The reasonable man adapts himself to the ¦
bidulock@openss7.org ¦ world; the unreasonable one persists in ¦
http://www.openss7.org/ ¦ trying to adapt the world to himself. ¦
¦ Therefore all progress depends on the ¦
¦ unreasonable man. -- George Bernard Shaw ¦
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-05 7:40 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-24 22:46 Fasttrak100 questions James Lamanna
2000-11-25 1:35 ` Andre Hedrick
2000-11-25 12:10 ` Henning P. Schmiedehausen
2000-11-25 17:20 ` Andre Hedrick
2000-11-25 17:22 ` Andre Hedrick
2000-11-29 19:53 ` Dr. Kelsey Hudson
2000-11-29 20:08 ` Henning P . Schmiedehausen
2000-11-29 21:11 ` Andre Hedrick
2000-11-29 22:12 ` Stop your abusive language! (Re: Fasttrak100 questions...) Dominik Kubla
2000-11-29 23:52 ` Fasttrak100 questions Jeff V. Merkey
2000-11-30 15:14 ` Christopher Friesen
2000-11-30 18:43 ` Jeff V. Merkey
2000-11-30 18:09 ` Christopher Friesen
2000-11-30 20:10 ` Jeff V. Merkey
2000-12-02 3:44 ` Peter Samuelson
2000-12-03 22:54 ` Pavel Machek
2000-12-05 4:10 ` Peter Samuelson
2000-11-29 20:42 ` Alan Cox
2000-11-29 21:05 ` Andre Hedrick
2000-11-29 21:10 ` James A Sutherland
2000-11-29 21:18 ` Alan Cox
2000-11-29 21:30 ` Andre Hedrick
2000-12-02 16:50 ` Pavel Machek
2000-12-02 17:18 ` Alan Cox
2000-12-02 23:46 ` Theodore Y. Ts'o
2000-12-03 1:21 ` Jeff V. Merkey
2000-12-03 1:31 ` Jeff V. Merkey
2000-12-03 3:42 ` Theodore Y. Ts'o
2000-12-03 5:11 ` Jeff V. Merkey
2000-12-05 7:07 ` Brian F. G. Bidulock [this message]
2000-12-05 8:25 ` Jeff V. Merkey
-- strict thread matches above, loose matches on Subject: below --
2000-12-03 16:41 Wayne.Brown
2000-12-03 17:49 ` Pavel Machek
2000-12-03 18:45 ` Alan Cox
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=20001205010730.A5760@openss7.org \
--to=bidulock@openss7.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hps@tanstaafl.de \
--cc=jmerkey@timpanogas.org \
--cc=jmerkey@vger.timpanogas.org \
--cc=kernel@blackhole.compendium-tech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--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