public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dirk Heinrichs <dirk.heinrichs@online.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] lvm problem -- is timing?
Date: Sat, 20 Jun 2009 22:48:49 +0200	[thread overview]
Message-ID: <200906202248.49451.dirk.heinrichs@online.de> (raw)
In-Reply-To: <200906202224.03186.dirk.heinrichs@online.de>

[-- Attachment #1: Type: text/plain, Size: 735 bytes --]

Am Samstag 20 Juni 2009 22:23:58 schrieb Dirk Heinrichs:
> > No good. rc-update shows udev, devfs, dmesg, device-mapper in sysinit
> > runlevel.
>
> device-mapper is wrong, there.

After reading your initial post in this thread again, that explains the 
problem. You have dm-crypt and dm-mod compiled as modules. Module loading is 
the first thing to happen in the boot runlevel. But the sysinit runlevel is 
executed before the boot runlevel. That means, when your device-mapper init 
script runs, it doesn't even have its module loaded.

So you should really put device-mapper into the boot runlevel. And btw, why do 
compile things as modules which you need in any case? Doesn't make sense to 
me.

Bye...

	Dirk

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 190 bytes --]

  reply	other threads:[~2009-06-20 20:48 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-20  4:15 [gentoo-user] lvm problem -- is timing? Maxim Wexler
2009-06-20  5:33 ` Mike Kazantsev
2009-06-20  7:08   ` Dirk Heinrichs
2009-06-20  7:37     ` Mike Kazantsev
2009-06-20  9:01       ` Dirk Heinrichs
2009-06-20 11:56         ` Mike Kazantsev
2009-06-20 12:46           ` Dirk Heinrichs
2009-06-20 19:23     ` Maxim Wexler
2009-06-20 20:26       ` Dirk Heinrichs
2009-06-20 20:34         ` Dirk Heinrichs
2009-06-20 19:14   ` Maxim Wexler
2009-06-20 20:23     ` Dirk Heinrichs
2009-06-20 20:48       ` Dirk Heinrichs [this message]
2009-06-20 23:51         ` Maxim Wexler
2009-06-21  7:57           ` Dirk Heinrichs
2009-06-21 21:16             ` Maxim Wexler
2009-06-21 21:32               ` Maxim Wexler
2009-06-21 21:49               ` Neil Bothwick
2009-06-21 22:17                 ` Ian Lee
2009-06-22  1:20                   ` Maxim Wexler
2009-06-22 16:43                     ` Dirk Heinrichs
2009-06-22 17:23                       ` Maxim Wexler
2009-06-22  1:13                 ` Maxim Wexler
2009-06-22  7:12                   ` Neil Bothwick
2009-06-22 17:42                     ` Maxim Wexler
2009-06-22 22:20                       ` Neil Bothwick
2009-06-22 18:09                     ` Maxim Wexler
2009-06-22 22:25                       ` Neil Bothwick
2009-06-23  2:12                         ` Maxim Wexler
2009-06-23  7:32                           ` Neil Bothwick
2009-06-23 19:15                             ` Maxim Wexler
2009-06-23 21:09                               ` Alan McKinnon
2009-06-23 21:36                               ` Neil Bothwick
2009-06-23 21:59                                 ` Maxim Wexler
2009-06-23 22:03                                   ` Neil Bothwick
2009-06-24 20:10                                     ` Maxim Wexler
2009-06-22 16:49               ` Dirk Heinrichs
2009-06-22 17:33                 ` Maxim Wexler
2009-06-22 22:21                   ` Neil Bothwick

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=200906202248.49451.dirk.heinrichs@online.de \
    --to=dirk.heinrichs@online.de \
    --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