All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] help mounting partitions in an encrypted disk after first reboot
Date: Sun, 18 Jun 2017 21:03:55 +0200	[thread overview]
Message-ID: <20170618190355.GA13250@tansi.org> (raw)
In-Reply-To: <20170618184517.GC20747@yeono.kjorling.se>

On Sun, Jun 18, 2017 at 20:45:17 CEST, Michael Kjörling wrote:
> On 18 Jun 2017 17:40 +0200, from arno@wagner.name (Arno Wagner):
> > A fix might be to just call "partprobe" after opening the
> > LUKS container.
> 
> That is indeed a _far_ better solution than what I had in mind.
> 
> As for LVM vs non-LVM, while I don't use LVM myself except for one
> system which I could wipe and reinstall right now if needed and not
> lose much more than some web browser settings; LVM _does_ offer a few
> niceties that are hard to get with plain partitions, and it is in
> widespread use. But I absolutely agree that it is an additional
> complex layer of things that can go wrong.

I agree to that. For a "throw-away" installtion that you just
wipe if things break, automated use of LVM is perfectly fine. 
For a complex installation that is carefully crafted due to 
special needs and with real understanding of the LVM details, 
it is perfectly fine too. 

Just in the middle, I do not think it has a place and I do think 
it is used far too often without a real need and increasing 
complexity without any real benefit. It is like it is used 
to get a longer "feature list" to sell.
 
> As a famous scientist once allegedly said: always make things as
> simple as possible, but never simpler.

And that is the trick. It is not easy, becuse making things simpler
as possible is about as bad as making them too complex and it
is pretty easy to mess up in that direction as well (and later
find out that you did shoot yourself in the foot...). 

As some other smart guy wrote: "There is no silver bullet". 
Every situation is difficult and there is no replacement for
understanding what is going on. One reason I like the discussions
here: People comming at it from different directions and backgrounds
and you get to compare different approaches.

Regards,
Arno
-- 
Arno Wagner,     Dr. sc. techn., Dipl. Inform.,    Email: arno@wagner.name
GnuPG: ID: CB5D9718  FP: 12D6 C03B 1B30 33BB 13CF  B774 E35C 5FA1 CB5D 9718
----
A good decision is based on knowledge and not on numbers. -- Plato

If it's in the news, don't worry about it.  The very definition of 
"news" is "something that hardly ever happens." -- Bruce Schneier

  reply	other threads:[~2017-06-18 19:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-18  6:49 [dm-crypt] help mounting partitions in an encrypted disk after first reboot Julio Gago
2017-06-18  7:25 ` Michael Kjörling
2017-06-18  8:30   ` Julio Gago
2017-06-18 15:25   ` Carl-Daniel Hailfinger
2017-06-18 15:51     ` Arno Wagner
2017-06-18 22:26       ` Carl-Daniel Hailfinger
2017-06-18 23:01         ` Arno Wagner
2017-06-19 19:02           ` Carl-Daniel Hailfinger
2017-06-19 21:34             ` Arno Wagner
2017-06-18 15:40 ` Arno Wagner
2017-06-18 17:21   ` Julio Gago
2017-06-18 18:03     ` Arno Wagner
2017-06-18 19:13       ` Julio Gago
2017-06-18 20:07         ` Arno Wagner
2017-06-18 18:45   ` Michael Kjörling
2017-06-18 19:03     ` Arno Wagner [this message]
2017-06-19 22:04   ` Sven Eschenberg
2017-06-19 22:48     ` Arno Wagner

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=20170618190355.GA13250@tansi.org \
    --to=arno@wagner.name \
    --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 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.