From: Arno Wagner <wagner@arnowagner.info>
To: cryptsetup@lists.linux.dev
Subject: Re: Partition table instead of LVM inside a LUKS container
Date: Mon, 26 Feb 2024 02:11:18 +0100 [thread overview]
Message-ID: <20240226011117.GA15410@tansi.org> (raw)
In-Reply-To: <fd408ce3-bf49-4dd3-841e-e9fa631de574@countermail.com>
On Sun, Feb 25, 2024 at 18:04:58 CET, Mistave wrote:
> On 2/25/24 16:36, Brian J. Murrell wrote:
> > So while I cannot comment on any experience with using partitions
> > inside of a LUKS container, I just couldn't imagine not using LVM.
> >
> > What is your hesitance to using LVM?
> >
>
> I'm only asking for opinions in my quest to learn new things about the
> secluded parts of Linux. My "hesitance" was initially that I wanted to
> remove another layer of complexity and use something simpler than LVM...
> that is assuming the partition layout is performed at system setup and will
> remain static for the lifetime of the device.
>
> Also, I'm not sure, if GPT partitions are as antiqued as you're making them
> sound like.
>
> Best regards.
Here is my take: I never use LVM, since I consider it
much more of a problem than a solution. Except for some
automation that tries to do everything the same way, I
do not see any use for LVM at all.
What I do is partition the basic devive (and no, GPT is
in no way outdated), and then put LUKS containers
into one or more partitions and filesystems directly
on top of that. Quite enought flexibility for a manual
set-up and if something goes wrong, you actually have a
resonable chance of fixing things.
Alsaus remember KISS is the very basis of all reliable,
secure and save design. Do not use a mechanism unless
you really need it. Avoid complexity at all cost.
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
prev parent reply other threads:[~2024-02-26 1:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-25 15:14 Partition table instead of LVM inside a LUKS container Mistave
2024-02-25 15:36 ` Brian J. Murrell
2024-02-25 17:04 ` Mistave
2024-02-26 1:11 ` Arno Wagner [this message]
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=20240226011117.GA15410@tansi.org \
--to=wagner@arnowagner.info \
--cc=arno@wagner.name \
--cc=cryptsetup@lists.linux.dev \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).