From: walt <w41ter@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Kernel upgrade and now LUKS failure.
Date: Tue, 04 May 2010 16:51:08 -0700 [thread overview]
Message-ID: <hrqbt8$b1b$1@dough.gmane.org> (raw)
In-Reply-To: <4BE05BA3.1000509@xunil.at>
On 05/04/2010 10:38 AM, Stefan G. Weichinger wrote:
> Am 04.05.2010 18:54, schrieb walt:
>
>>> pam_mount(mount.c): crypt_activate_by_passphrase: Operation not
>>> permitted
>>
>> I don't have a pam_mount, where does it come from? Perhaps it needs
>> a reference to pam_ssh.so?
>
> What do you mean with "where does it come from?" ?
>
> It's in portage ...
Okay, I'm assuming pam_mount.so and mount.crypt come from the sys-auth/
pam_mount package but I can't check because all of those packages are
masked by the ~x86 keyword at the moment.
> Could it be the case that my current setup somehow uses "the new API"
> which isn't available yet in some package?
>
> I don't yet have the whole picture ...
Daniel knows more than I do about this subject, so I recommend that you
follow his advice. However, all of the pam_mount packages being masked
at the same time makes me suspect that not everything is working exactly
as it should. I'll follow this thread, hoping to learn more.
next prev parent reply other threads:[~2010-05-04 23:52 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-03 16:56 [gentoo-user] Kernel upgrade and now LUKS failure Jason Dusek
2010-05-03 17:31 ` Florian Philipp
2010-05-04 10:06 ` Stefan G. Weichinger
2010-05-04 16:54 ` [gentoo-user] " walt
2010-05-04 17:38 ` Stefan G. Weichinger
2010-05-04 19:28 ` Stefan G. Weichinger
2010-05-04 21:24 ` Daniel Troeder
2010-05-05 4:42 ` Stefan G. Weichinger
2010-05-05 8:00 ` Daniel Troeder
2010-05-05 8:42 ` Stefan G. Weichinger
2010-05-05 19:39 ` Daniel Troeder
2010-05-05 20:17 ` Stefan G. Weichinger
2010-05-05 20:23 ` Stefan G. Weichinger
2010-05-06 16:24 ` Daniel Troeder
2010-05-06 18:38 ` Stefan G. Weichinger
2010-05-07 8:53 ` Stefan G. Weichinger
2010-05-07 14:24 ` Stefan G. Weichinger
2010-05-07 21:14 ` Stefan G. Weichinger
2010-05-10 16:48 ` Daniel Troeder
2010-05-04 23:51 ` walt [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-05-16 12:36 Jan Engelhardt
2010-05-17 9:14 ` Stefan G. Weichinger
2010-05-17 21:01 ` Daniel Troeder
2010-05-18 13:05 ` Jan Engelhardt
2010-05-18 13:44 ` Stefan G. Weichinger
2010-05-18 16:04 ` Jan Engelhardt
2010-05-18 16:56 ` Stefan G. Weichinger
2010-05-18 17:57 ` Jan Engelhardt
2010-05-18 18:57 ` Stefan G. Weichinger
2010-05-18 19:33 ` Stefan G. Weichinger
2010-05-18 20:06 ` Jan Engelhardt
2010-05-18 20:17 ` Stefan G. Weichinger
2010-05-18 21:16 ` Jan Engelhardt
2010-05-18 21:49 ` Stefan G. Weichinger
2010-05-18 22:23 ` Jan Engelhardt
2010-05-20 10:25 ` Stefan G. Weichinger
2010-05-20 13:40 ` Stefan G. Weichinger
2010-05-18 19:38 ` Eray Aslan
2010-05-21 20:24 ` Daniel Troeder
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='hrqbt8$b1b$1@dough.gmane.org' \
--to=w41ter@gmail.com \
--cc=gentoo-user@lists.gentoo.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