From: Dave Haywood <tla@oak.selfip.net>
To: linux-newbie@vger.kernel.org
Subject: TruCrypt
Date: Wed, 21 Nov 2007 16:48:36 +0000 [thread overview]
Message-ID: <47446164.2040205@oak.selfip.net> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
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.
I think this is because the kernel interfaces tc uses have changed.
Is anyone aware of any fixes to correct this problem?
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?
Thx,
Dave.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
iD8DBQFHRGFks7shH0x9UrgRAgmbAJ91AFFTN9RkoQlnIJYMmOPpgiS0eACfcpED
yReT7yk/1Pv3oGdmGNmrHU4=
=GICs
-----END PGP SIGNATURE-----
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" 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.linux-learn.org/faqs
next reply other threads:[~2007-11-21 16:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-21 16:48 Dave Haywood [this message]
2007-11-21 18:11 ` TruCrypt Kristof Provost
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=47446164.2040205@oak.selfip.net \
--to=tla@oak.selfip.net \
--cc=linux-newbie@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