From: jmerkey <jmerkey@utah-nac.org>
To: Diego Calleja <diegocg@gmail.com>
Cc: "Jeff V. Merkey" <jmerkey@soleranetworks.com>,
Valdis.Kletnieks@vt.edu, arjan@infradead.org, riel@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] DSFS Network Forensic File System for Linux Patches
Date: Wed, 31 Aug 2005 16:50:24 -0600 [thread overview]
Message-ID: <43163430.7010107@utah-nac.org> (raw)
In-Reply-To: <20050901012218.02c79560.diegocg@gmail.com>
Diego Calleja wrote:
>El Wed, 31 Aug 2005 14:27:47 -0600,
>"Jeff V. Merkey" <jmerkey@soleranetworks.com> escribió:
>
>
>
>>
>>NOTE! This copyright does *not* cover user programs that use kernel
>> services by normal system calls - this is merely considered normal use
>> of the kernel, and does *not* fall under the heading of "derived work".
>> Also note that the GPL below is copyrighted by the Free Software
>> Foundation, but the instance of code that it refers to (the linux
>> kernel) is copyrighted by me and others who actually wrote it.
>>
>>
>
>So, that means that DSFS runs on userspace? (We can't see the source
>so it'd be nice to know how DSFS works)
>
>Also, I'm curious about this piece of code on your patch:
>ftp://ftp.soleranetworks.com/pub/dsfs/datascout-only-2.6.9-06-28-05.patch
>
>- printk(KERN_WARNING "%s: module license '%s' taints kernel.\n",
>- mod->name, license);
>+// printk(KERN_WARNING "%s: module license '%s' taints kernel.\n",
>+// mod->name, license);
>
>I mean, nvidia people also use propietary code in the kernel (probably
>violating the GPL anyway) and don't do such things.
>
>
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
>
>
>
I disagree with the language and the characterization that our
proprietary user application code is "tainted."
Jeff
next prev parent reply other threads:[~2005-09-01 0:05 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-31 16:33 [ANNOUNCE] DSFS Network Forensic File System for Linux Patches Jeff V. Merkey
2005-08-31 18:32 ` Rik van Riel
2005-08-31 17:27 ` Jeff V. Merkey
2005-08-31 18:58 ` Arjan van de Ven
2005-08-31 18:00 ` Jeff V. Merkey
2005-08-31 21:28 ` Valdis.Kletnieks
2005-08-31 20:23 ` Jeff V. Merkey
2005-08-31 20:27 ` Jeff V. Merkey
2005-08-31 23:22 ` Diego Calleja
2005-08-31 22:50 ` jmerkey [this message]
2005-09-01 0:36 ` Bernd Eckenfels
2005-09-01 0:33 ` Bernd Eckenfels
2005-09-01 0:56 ` jmerkey
2005-09-01 1:44 ` jmerkey
[not found] ` <67029b1705083120142c0c1dea@mail.gmail.com>
2005-09-01 3:19 ` Zhou Yingchao
2005-09-01 7:12 ` Lincoln Dale
2005-09-01 7:45 ` Vojtech Pavlik
2005-09-01 10:23 ` Alan Cox
2005-09-01 8:28 ` Bernd Petrovitsch
2005-09-01 10:15 ` Alan Cox
2005-09-03 21:26 ` Bernd Eckenfels
2005-09-04 8:45 ` Alan Cox
2005-09-05 20:19 ` Bernd Eckenfels
2005-08-31 21:49 ` Jose Luis Domingo Lopez
2005-09-01 21:11 ` Alistair John Strachan
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=43163430.7010107@utah-nac.org \
--to=jmerkey@utah-nac.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=arjan@infradead.org \
--cc=diegocg@gmail.com \
--cc=jmerkey@soleranetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.com \
/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