public inbox for linux-newbie@vger.kernel.org
 help / color / mirror / Atom feed
From: Kristof Provost <Kristof@provost-engineering.be>
To: Dave Haywood <tla@oak.selfip.net>
Cc: linux-newbie@vger.kernel.org
Subject: Re: TruCrypt
Date: Wed, 21 Nov 2007 19:11:29 +0100	[thread overview]
Message-ID: <20071121181124.GH5255@berith> (raw)
In-Reply-To: <47446164.2040205@oak.selfip.net>

[-- Attachment #1: Type: text/plain, Size: 578 bytes --]

On 2007-11-21 16:48:36 (+0000), Dave Haywood <tla@oak.selfip.net> wrote:
> Hi,
> 
>   I see that the TruCrypt build borks under the latest -rc kernels.
> See https://bugs.gentoo.org/show_bug.cgi?id=198394 for an example.
 
>   Has anyone considered incorporating the non-userland parts of tc
> into the kernel to avoid this borkage in the future?  tc is under some
> non-GPL license so this may not be possible?
It's been discussed on the lkml. The author never submitted it for
inclusion in the kernel.
Take a look at http://lkml.org/lkml/2007/11/5/369 

Kristof

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2007-11-21 18:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-21 16:48 TruCrypt Dave Haywood
2007-11-21 18:11 ` Kristof Provost [this message]

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=20071121181124.GH5255@berith \
    --to=kristof@provost-engineering.be \
    --cc=linux-newbie@vger.kernel.org \
    --cc=tla@oak.selfip.net \
    /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