From: Matthias Schniedermeyer <ms@citd.de>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Cryptsetup FAQ montly pointer 8/13
Date: Sun, 4 Aug 2013 00:51:20 +0200 [thread overview]
Message-ID: <20130803225120.GA26923@citd.de> (raw)
In-Reply-To: <20130803214715.GB9684@tansi.org>
On 03.08.2013 23:47, Arno Wagner wrote:
> On Sat, Aug 03, 2013 at 10:47:25PM +0200, Milan Broz wrote:
> > On 3.8.2013 19:57, Arno Wagner wrote:
> > >>For plain crypt (or Truecrypt) you have no UUID, so you cannot use it.
> > >>(You can use uuid/wwid of underlying device as mentioned above
> > >>but this is not be present always.)
> > >
> > >Indeed. I tried both when I wrote the entry, only to find that
> > >neither worked on my system (Debain with custom kernel).
> > >
> > >As this is not a distrioution specific FAQ (there are those)
> > >distribution specific stuff shopuld not go into it. Of course
> > >documentation for a specific distribution can contain specific
> > >advice that is not general, and some people have already asked
> > >me about such things, also with regard to encrypted swap.
> >
> > Device UUID/model etc should not be distribution specific,
> > udev /dev/disk/by-id* is quite standard among distibutions here.
>
> I thought so too, but the only thing I have in my /dev/disk/by-id
> are my raid devices, nothing else, and I do have normal partitions.
There must be something wrong(tm).
E.g. just looking for the SSD my operating system is placed on i get 3
different entries:
(Ignoring the partitions)
lrwxrwxrwx 1 root root 9 Jul 28 03:17 ata-Samsung_SSD_840_PRO_Series_S12RNEACC37670P -> ../../sda
lrwxrwxrwx 1 root root 9 Jul 28 03:17 scsi-SATA_Samsung_SSD_840S12RNEACC37670P -> ../../sda
lrwxrwxrwx 1 root root 9 Jul 28 03:17 wwn-0x5002538550114fa0 -> ../../sda
Counting all symlinks i have 31 in by-id!
This is also a Debian System with a custom kernel (3.10.3).
udev itself has a README somewhere describing what CONFIG parameters
have to be set for udev to fully work. I look through that some ages ago
and i had a few missing back then.
Also "compatiblity with old userspace"-options
like: CONFIG_SYSFS_DEPRECATED should be disabled.
--
Matthias
next prev parent reply other threads:[~2013-08-03 23:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-03 14:10 [dm-crypt] Cryptsetup FAQ montly pointer 8/13 Dragan Milivojević
2013-08-03 14:47 ` Milan Broz
2013-08-03 17:57 ` Arno Wagner
2013-08-03 20:47 ` Milan Broz
2013-08-03 21:47 ` Arno Wagner
2013-08-03 22:51 ` Matthias Schniedermeyer [this message]
2013-08-03 17:47 ` Arno Wagner
2013-08-03 12:49 ` Alex Elsayed
-- strict thread matches above, loose matches on Subject: below --
2013-08-02 21:54 Arno Wagner
2013-08-03 13:51 ` Robert Nichols
2013-08-03 17:46 ` Arno Wagner
2013-08-04 15:02 ` Sven Eschenberg
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=20130803225120.GA26923@citd.de \
--to=ms@citd.de \
--cc=dm-crypt@saout.de \
/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