public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jari Ruusu <jari.ruusu@pp.inet.fi>
To: Eyal Lebedinsky <eyal@eyal.emu.id.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Announce loop-AES-v1.4d file/swap crypto package
Date: Tue, 04 Sep 2001 20:56:28 +0300	[thread overview]
Message-ID: <3B9515CC.820C1F20@pp.inet.fi> (raw)
In-Reply-To: <3B93B32A.69D25916@pp.inet.fi> <3B93EE69.5674035F@eyal.emu.id.au> <3B940291.C752F45B@pp.inet.fi> <3B94C8A9.EA7D4E72@eyal.emu.id.au>

Eyal Lebedinsky wrote:
> Problem is that one gets tons of errors due to the use of the wrong
> kernel.
> The exact way for doing it right is actually:
>         depmod -ae $(KERNELRELEASE) -F $(LS)/System.map

Yep, but one must define KERNELRELEASE for 2.0 kernels. As I said, I will
fix this for next release.

> > Loop-AES build instructions _require_ you to disable the loop driver in the
> > kernel. If you have two loop.o drivers, you skipped some build instructions.
> 
> It is not in the kernel, it is in my /lib/modules as it was built
> originally.
> I want to keep it there while I play with the new module, and not lose
> the
> original. Naturally, just my preference, not everybodies.

I meant that loop must be completely disabled, as it says in the README:

CONFIG_BLK_DEV_LOOP=n

Regards,
Jari Ruusu <jari.ruusu@pp.inet.fi>


      reply	other threads:[~2001-09-04 17:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-03 16:43 Announce loop-AES-v1.4d file/swap crypto package Jari Ruusu
2001-09-03 20:56 ` Eyal Lebedinsky
2001-09-03 22:22   ` Jari Ruusu
2001-09-04 12:27     ` Eyal Lebedinsky
2001-09-04 17:56       ` Jari Ruusu [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=3B9515CC.820C1F20@pp.inet.fi \
    --to=jari.ruusu@pp.inet.fi \
    --cc=eyal@eyal.emu.id.au \
    --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