From: martin f krafft <madduck@madduck.net>
To: linux-kernel@vger.kernel.org
Subject: Re: modprobe failed: digest_null
Date: Thu, 15 Jan 2004 09:50:52 +0100 [thread overview]
Message-ID: <20040115085052.GA28057@piper.madduck.net> (raw)
In-Reply-To: <20040114154836.35614a92.rddunlap@osdl.org>
[-- Attachment #1: Type: text/plain, Size: 655 bytes --]
also sprach Randy.Dunlap <rddunlap@osdl.org> [2004.01.15.0048 +0100]:
> > kernel: request_module: failed /sbin/modprobe -- digest_null. error = 256
>
> Chris Wright tells me that this is a null digest crypto plugin
> for testing. It might show up in your /etc/modprobe.conf file
> (or it might not).
i don't see such a module in the kernel config. there is the null
encryption, but it's not a null digest.
--
martin; (greetings from the heart of the sun.)
\____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck
invalid/expired pgp subkeys? use subkeys.pgp.net as keyserver!
this space intentionally left blank.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-01-15 8:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-13 21:53 martin f krafft
2004-01-13 22:30 ` Randy.Dunlap
2004-01-13 22:37 ` martin f krafft
2004-01-13 22:41 ` Randy.Dunlap
2004-01-13 22:50 ` martin f krafft
2004-01-13 23:03 ` Randy.Dunlap
2004-01-13 23:38 ` David Rees
2004-01-14 0:01 ` Randy.Dunlap
2004-01-14 0:59 ` Randy.Dunlap
2004-01-14 0:08 ` martin f krafft
2004-01-14 1:05 ` David Rees
2004-01-14 23:48 ` Randy.Dunlap
2004-01-15 0:46 ` Stian Jordet
2004-01-15 8:50 ` martin f krafft [this message]
2004-01-14 1:26 ` Steve Youngs
2004-01-14 1:31 ` Randy.Dunlap
2004-01-14 8:45 ` martin f krafft
2004-01-16 15:55 ` Martin Schlemmer
2004-01-14 23:22 ` Rusty Russell
2004-01-15 8:08 ` martin f krafft
2004-01-15 16:30 ` Randy.Dunlap
2004-01-15 20:51 ` Andreas Schrell
2004-01-19 4:53 ` Rusty Russell
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=20040115085052.GA28057@piper.madduck.net \
--to=madduck@madduck.net \
--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
Powered by JetHome