From: Eyal Lebedinsky <eyal@eyal.emu.id.au>
To: Jari Ruusu <jari.ruusu@pp.inet.fi>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Announce loop-AES-v1.4d file/swap crypto package
Date: Tue, 04 Sep 2001 22:27:21 +1000 [thread overview]
Message-ID: <3B94C8A9.EA7D4E72@eyal.emu.id.au> (raw)
In-Reply-To: <3B93B32A.69D25916@pp.inet.fi> <3B93EE69.5674035F@eyal.emu.id.au> <3B940291.C752F45B@pp.inet.fi>
Jari Ruusu wrote:
>
> Eyal Lebedinsky wrote:
> > Jari Ruusu wrote:
> > > In short: If file and swap crypto is all you need, this package is a hassle
> > > free replacement for international crypto patch and HVR's crypto-api.
> >
> > 1) It claims to allow you to specify the kernel sources dir, but it then
> > runs 'depmod' without a nominated version which is only valid if you
> > are building for the running kernel. I now have it doing
> > depmod -ae $(KERNELRELEASE)
>
> I will fix that in next release. However, most systems (if not all) run
> depmod from bootup initialization scripts. Depmod from the Makefile is only
> needed when you intend to use the driver immediately without rebooting.
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
> 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.
--
Eyal Lebedinsky (eyal@eyal.emu.id.au) <http://samba.anu.edu.au/eyal/>
next prev parent reply other threads:[~2001-09-04 12:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-03 16:43 Jari Ruusu
2001-09-03 20:56 ` Eyal Lebedinsky
2001-09-03 22:22 ` Jari Ruusu
2001-09-04 12:27 ` Eyal Lebedinsky [this message]
2001-09-04 17:56 ` Jari Ruusu
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=3B94C8A9.EA7D4E72@eyal.emu.id.au \
--to=eyal@eyal.emu.id.au \
--cc=jari.ruusu@pp.inet.fi \
--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®