All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bryan Kadzban <bryan.kadzban@gmail.com>
To: Selim Levy <sjtlevy@gmail.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] configuration files
Date: Sun, 21 Feb 2010 09:10:52 -0800	[thread overview]
Message-ID: <4B81691C.9020500@gmail.com> (raw)
In-Reply-To: <6294c32a1002202042i7640ebbrd9899c5bfb33b49c@mail.gmail.com>

Selim Levy wrote:
> The contents of the rescue's /etc/crypttab, for which I've tried various
> things is:
> # cat crypttab
> sdb3_crypt /dev/sdb3 none luks

So, from 1000 miles away...

Doesn't Debian's initramfs bring up udev and let you use the
/dev/disk/by-*/ symlinks in crypttab?  That's a *LOT* better way to find
this drive (in your case, by-id might work, and by-uuid will almost
definitely work, assuming a new-enough udev that can find the UUID of a
LUKS volume).  Maybe poke around in /dev/disk when you're at the busybox
prompt, and see what you can find.

(If it doesn't bring up udev and let you use those symlinks, then ...
why not?  :-P  Not a question for you obviously, but more for the Debian
maintainers.)

Anyway, then you don't care which sd* name is given to this device,
since you're using an explicitly-guaranteed-stable name for it.

  parent reply	other threads:[~2010-02-21 17:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-18  0:25 [dm-crypt] configuration files Selim Levy
2010-02-20  8:55 ` Jonas Meurer
2010-02-21  4:42   ` Selim Levy
2010-02-21 11:27     ` Jonas Meurer
2010-02-21 19:46       ` Selim Levy
2010-02-21 20:40         ` Selim Levy
2010-02-21 17:10     ` Bryan Kadzban [this message]
2010-02-21 20:18       ` Selim Levy
2010-02-21 20:53         ` Jonas Meurer
2010-02-22  6:59           ` Selim Levy
2010-02-22 11:13             ` Jonas Meurer
2010-02-22 21:40               ` Selim Levy
2010-02-22 23:12                 ` Jonas Meurer
2010-03-05 19:36                   ` Selim Levy
2010-03-08 11:52                     ` Jonas Meurer
2010-03-08 21:35                       ` Selim Levy
2010-03-08 22:27                         ` Selim Levy
2010-03-08 22:37                         ` Jonas Meurer

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=4B81691C.9020500@gmail.com \
    --to=bryan.kadzban@gmail.com \
    --cc=dm-crypt@saout.de \
    --cc=sjtlevy@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.