On 20150402_1142-0500, David Wright wrote:
Quoting Paul E Condon (pecon...@mesanetworks.net):
I read the prior discussion as taking for granted the idea that one
must have only one method of identifying individual partitions,
^^^ ^^
If you're referring to my post (which
On 04/01/2015 11:45 PM, David Wright wrote:
Quoting ~Stack~ (i.am.st...@gmail.com):
On 04/01/2015 03:27 PM, David Wright wrote:
I don't recall seeing you post what you actually put into
/etc/crypttab to test PARTUUID, only the erroneous earlier versions
where you were still using swap's UUID.
Quoting Paul E Condon (pecon...@mesanetworks.net):
I read the prior discussion as taking for granted the idea that one
must have only one method of identifying individual partitions,
If you're referring to my post (which you quoted), then the opposite
is true. The opening paragraphs argues
Quoting ~Stack~ (i.am.st...@gmail.com):
On 04/01/2015 03:27 PM, David Wright wrote:
I don't recall seeing you post what you actually put into
/etc/crypttab to test PARTUUID, only the erroneous earlier versions
where you were still using swap's UUID.
Fair enough. Completely plausible I
On 04/01/2015 03:27 PM, David Wright wrote:
I don't recall seeing you post what you actually put into
/etc/crypttab to test PARTUUID, only the erroneous earlier versions
where you were still using swap's UUID.
Fair enough. Completely plausible I did something wrong as I haven't
used PARTUUID's
I read the prior discussion as taking for granted the idea that one
must have only one method of identifying individual partitions, and
that that method must be the latest to have arrived on the scene. For
example, if everyone else in the world accepts your idea that
LABEL=sda1 on the partition
Quoting Paul E Condon (pecon...@mesanetworks.net):
You can also use disk LABEL=. As implemented, the LABEL is actually
applied to individual partition. As long as every partition has a
different LABEL values there is no ambiguity. You only need to have
unique values for partitions that you
Quoting ~Stack~ (i.am.st...@gmail.com):
On 03/29/2015 07:06 AM, Sven Hartge wrote:
~Stack~ i.am.st...@gmail.com wrote:
One more question if you don't mind: I understand why the encrypted
partition UUID is going to change every time, but the physical
partition UUID for my /dev/sda3
On 20150331_1923-0500, ~Stack~ wrote:
On 03/29/2015 07:06 AM, Sven Hartge wrote:
~Stack~ i.am.st...@gmail.com wrote:
One more question if you don't mind: I understand why the encrypted
partition UUID is going to change every time, but the physical
partition UUID for my /dev/sda3
On 03/29/2015 07:06 AM, Sven Hartge wrote:
~Stack~ i.am.st...@gmail.com wrote:
One more question if you don't mind: I understand why the encrypted
partition UUID is going to change every time, but the physical
partition UUID for my /dev/sda3 shouldn't change though. If they are
the same
~Stack~ i.am.st...@gmail.com wrote:
One more question if you don't mind: I understand why the encrypted
partition UUID is going to change every time, but the physical
partition UUID for my /dev/sda3 shouldn't change though. If they are
the same systemd.fsck shouldn't have a problem with the
On 03/28/2015 02:15 PM, David Wright wrote:
Quoting ~Stack~ (i.am.st...@gmail.com):
[snip]
$ grep swap /etc/crypttab
# causes systemd to fsck swap
#sda3_crypt UUID=ef2496cd-ca4d-43aa-8c90-dba084029f6e /dev/urandom
cipher=aes-xts-plain64,size=256,swap
# systemd doesn't fsck swap
sda3_crypt
~Stack~ i.am.st...@gmail.com wrote:
On 03/28/2015 02:15 PM, David Wright wrote: Quoting ~Stack~
(i.am.st...@gmail.com):
$ grep swap /etc/crypttab
# causes systemd to fsck swap
#sda3_crypt UUID=ef2496cd-ca4d-43aa-8c90-dba084029f6e /dev/urandom
cipher=aes-xts-plain64,size=256,swap
# systemd
On 03/28/2015 03:37 PM, Sven Hartge wrote:
~Stack~ i.am.st...@gmail.com wrote:
[snip]
In my /dev/disk/by-id/ directory I have both dm-name-sda3_crypt and
dm-uuid-CRYPT-PLAIN-sda3_crypt which point to ../../dm-1. I can
not use either of those in my /etc/crypttab because then I get the
~Stack~ i.am.st...@gmail.com wrote:
In another post on this thread you asked where I got that UUID from.
That question fits in well here so I am just going to dump it all
here. :-)
I just checked a number of my systems with blkid and the UUID's I am
using are indeed the physical /dev/sdx#
On 03/28/2015 06:45 PM, Sven Hartge wrote:
~Stack~ i.am.st...@gmail.com wrote:
In another post on this thread you asked where I got that UUID from.
That question fits in well here so I am just going to dump it all
here. :-)
I just checked a number of my systems with blkid and the UUID's I
16 matches
Mail list logo
