From: Nico Schottelius <nico-linux-admin-ml@schottelius.org>
To: linux-admin@vger.kernel.org, scholz@wdt.de
Subject: Re: Cryptoloop and kernel 2.6?
Date: Wed, 14 Jan 2004 13:51:49 +0100 [thread overview]
Message-ID: <20040114125149.GB15599@schottelius.org> (raw)
In-Reply-To: <20040114122749.GA1787@mainserver.organic.net>
[-- Attachment #1: Type: text/plain, Size: 888 bytes --]
markus reichelt [Wed, Jan 14, 2004 at 01:27:49PM +0100]:
> Nico Schottelius <nico-linux-admin-ml@schottelius.org> wrote:
> > what about crypto loops created within 2.4?
> > Is it possible something changed and 2.6 cannot read the old
> > ones?
>
> sigh, so much is possible these days...
that was true since we live, not just today.
Goethe's "Faust" shows you that very well.
> do you experience any problems with your crypto loops created with a
> 2.4 kernel under a brand new 2.6? do you use crypto loops in the
> first place? if so, why don't you just find out and tell us? :)
"tell"
no go on and fix it ;)
Nico
ps: does anyone know if there were changes in the cryptoloop, which
cause this problem?
--
Keep it simple & stupid, use what's available.
pgp: 8D0E E27A | Nico Schottelius
http://nerd-hosting.net | http://linux.schottelius.org
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-01-14 12:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-11 19:02 Cryptoloop and kernel 2.6? Benjamin Walkenhorst
2004-01-12 13:51 ` Nico Schottelius
2004-01-12 17:56 ` Milan P. Stanic
2004-01-12 21:02 ` Bradley Hook
2004-01-12 22:47 ` Nico Schottelius
2004-01-14 12:27 ` markus reichelt
2004-01-14 12:51 ` Nico Schottelius [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=20040114125149.GB15599@schottelius.org \
--to=nico-linux-admin-ml@schottelius.org \
--cc=linux-admin@vger.kernel.org \
--cc=scholz@wdt.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.