mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: jmerkey@wolfmountaingroup.com
To: linux-kernel@vger.kernel.org
Subject: Forensic File System Patches Posted 11-20-08
Date: Sat, 22 Nov 2008 11:05:56 -0700 (MST)	[thread overview]
Message-ID: <51963.166.70.238.45.1227377156.squirrel@webmail.wolfmountaingroup.com> (raw)


Pursuant to the GPL, the following patches are posted or the Forensic File
System appliance on Linux.  We will be shipping and are now shipping
support for Linux with the Forensic File System after reviewing customer
requirements and looking at GPL issues wit commercial software deployment.

ftp://ftp.wolfmountaingroup.org/pub/forenfs/ffs-2.6.26.4-el5-11-20-08.patch

The File System is not distributed with Linux or built on it or any other
GPL code and is not linked against Linux until installed by the customer
and is provided in a non-GNU object format for linking against Linux,
similar to how ndiswrapper works.  I do not believe there are any GPL
restrictions on customers downloading or purchasing Linux add ons provided
they are not distributing them with Linux.  I have observed that a large
number of companies, including the providers of VMWare and Novell
distribute Linux and GPL code with their proprietary software bundled with
it.

This appears to violate the GPL, but I am not certain of this.  So given
this, I am offering for sale Linux add ons not distributed with Linux and
providing the patches and kernel changes back as required by the GPL.

Jeffrey Vernon Merkey


I am working on MDB updates for 2.6.28 and will post mdb with major kernel
releases from now on in order to better measure kernel breakage between
releases.  The rc level debugger releases seem to be redundant since the
areas debuggers touch rarely changes.







                 reply	other threads:[~2008-11-22 19:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=51963.166.70.238.45.1227377156.squirrel@webmail.wolfmountaingroup.com \
    --to=jmerkey@wolfmountaingroup.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®