From: Mistave <mistave@countermail.com>
To: cryptsetup@lists.linux.dev
Subject: Re: Partition table instead of LVM inside a LUKS container
Date: Sun, 25 Feb 2024 18:04:58 +0100 [thread overview]
Message-ID: <fd408ce3-bf49-4dd3-841e-e9fa631de574@countermail.com> (raw)
In-Reply-To: <d9045882cb08f2cf0b09f959f0dca6cee5a26e03.camel@interlinx.bc.ca>
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.
next prev parent reply other threads:[~2024-02-25 17:05 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 [this message]
2024-02-26 1:11 ` 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=fd408ce3-bf49-4dd3-841e-e9fa631de574@countermail.com \
--to=mistave@countermail.com \
--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