Received: from poseidon.malbolge.net (hera.malbolge.net [185.232.68.32]) by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id 62A2D782D03 for <~alpine/users@lists.alpinelinux.org>; Tue, 20 Jul 2021 12:36:45 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; s=_domainkey; bh=9mZTyQRFr eCnV655vSyJEL9kP1Ms+EzwX5bBRj67/yY=; h=references:in-reply-to:subject: cc:to:from:date; d=mail.malbolge.net; b=H65k876mYtntaAZ3BCyyDUhzsNvSJ/ PInx8XSy8BfyJPUJfqi3nCPLsO/j1gSMkRvpXAWxFik0/3/dD38w/AhEay4US6INxzWZ21 cBkDujSkpgK7ukUlNXTQVU8Th9e2rorV2eJVHoTqT3IrlTFWZ2lH8NICvB29432tivmffK w= Received: from hermes.malbolge.net (hermes.malbolge.net [192.168.123.201]) by poseidon.malbolge.net (OpenSMTPD) with ESMTP id 62cb0777; Tue, 20 Jul 2021 14:36:43 +0200 (CEST) Received: from moon (hera.malbolge.net [10.0.11.1]) by hermes.malbolge.net (Postfix) with ESMTPSA id 7A4C81C096F; Tue, 20 Jul 2021 14:36:43 +0200 (CEST) Date: Tue, 20 Jul 2021 14:35:10 +0200 From: Michael Siegel To: caskd Cc: ~alpine/users@lists.alpinelinux.org Subject: Re: "LVM on LUKS" wiki page: Questions and suggestions Message-ID: <20210720143510.12c89045@moon> In-Reply-To: <20210719210325.5jno55lrja76vrdu@navi> References: <20210719215114.531515a2@moon> <20210719210325.5jno55lrja76vrdu@navi> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am Mon, 19 Jul 2021 21:03:25 +0000 schrieb caskd : > >Then, when using dd(1), going with the default block size will take > >ages to complete. Adding `bs=3D1M` is generally much faster, in my > >experience. =20 > This is entirely dependent on the device you have and a few other > factors, so it makes more sense to keep the default. I see. I still think it should be mentioned that choosing a more adequate block size might speed things up considerably. =20 > >So, I suggest the following: > > > > * Remove section "Optional: Overwrite LUKS Partition with Random > > Data" entirely. =20 > It should be replaced with "Overwrite disk with Random Data" before > creating the partition table instead. Okay, but this is already covered in "Preparing the Temporary Installation Environment". And that is where these instructions belong, I'd say. > >This section is obviously specific to the case of using GRUB with > >UEFI. > > > >The version for Syslinux with BIOS would have to look like this, if > >I'm not mistaken: > > > > # cd > > # umount /mnt/boot > > # swapoff /dev/vg0/swap > > # umount /mnt > > # vgchange -a n > > # cryptsetup luksClose lvmcrypt > > # reboot > > > >So, there should be two sub-sections here: > > > > * "Syslinux with BIOS", containing the above command block. > > * "Grub with UEFI", containing what's already there. =20 > This has nothing to do with the bootloader. If syslinux supported > UEFI, it would be similar if not the same. It should instead keep the > `umount /mnt/boot/efi` with a comment or a note that says it is UEFI > specific. The problem is that the whole tutorial is based on going about things one of two ways: either BIOS/MBR/Syslinux or UEFI/GPT/GRUB. And lines 2=E2=80=935 in the code block as it is on the page are specific to what the tutorial describes for going with UEFI/GPT/GRUB. So, for consistency, there should be two sub-sections, just like in some of the previous sections. -- Michael