<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<atom:link href="http://dev1galaxy.org/extern.php?action=feed&amp;tid=2098&amp;type=rss" rel="self" type="application/rss+xml" />
		<title><![CDATA[Dev1 Galaxy Forum / Using the installer to install to non-standard partition/disk layout.]]></title>
		<link>http://dev1galaxy.org/viewtopic.php?id=2098</link>
		<description><![CDATA[The most recent posts in Using the installer to install to non-standard partition/disk layout..]]></description>
		<lastBuildDate>Sat, 26 May 2018 10:21:51 +0000</lastBuildDate>
		<generator>FluxBB</generator>
		<item>
			<title><![CDATA[Using the installer to install to non-standard partition/disk layout.]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=9452#p9452</link>
			<description><![CDATA[<p>I just posted this as a bug against the debian installer, though who knows if it will have any effect.&#160; Others might be interested in how to do this.</p><p>----------</p><p>I am just switching from Ubuntu to Debian, and finding the installer creating serious obstacles that were not present in Ubuntu. I am doing an install using non-default settings for cryptsetup, though the issues are not specific to using cryptsetup. Typically, I would prepare my disks, do the install, and then pivot in, correcting fstab &amp; crypttab, and updating the initramfs. For Debian it&#039;s taken quite some struggle. My procedure is below, and the &quot;**&quot;s indicate where problems are that I believe are unnecessary. </p><p>Run the installer. During &quot;Load Installer Components from CD&quot;, make sure to include crypto-dm-modules. **Note that there is no crypsetup.** Continue installation up to but not including &quot;Partition Disks&quot;. </p><p>Drop to a shell and: <br />anna-install cryptsetup-udeb <br />partition &amp; format disk(s), or **at least the ones the installer&#039;s partitioner is incapable of creating, eg. luks containers on a whole device or non-default cryptsetup options.** <br />make filesystems in the devices in /dev/mapper (eg. encrypted containers), otherwise **the installer&#039;s partitioner always demands to make partitions in these devices.** <br />exit </p><p>Run &quot;Detect Disks&quot; again. Then continue with the paritioner, which will now recognize the /dev/mapper devices. Associate the appropriate devices with /boot, /, etc. and &quot;write changes to disk&quot;. Then continue the installer through and including &quot;Select &amp; Install Software&quot;. </p><p>Drop to a shell and: <br />apt-install cryptsetup <br />edit /target/etc/{fs,crypt}tab <br />I need cryptsetup, and I find I have to **edit /target/etc/cryptsetup-initramfs/conf-hook setting &quot;CRYPTSETUP=y&quot;** <br />exit </p><p>Continue with installation, running through the end of the install. </p><p>On reboot, re-edit /target/etc/cryptsetup-initramfs/conf-hook, as &quot;CRYPTSETUP=y&quot; is no longer needed. update-initramfs, if you want. </p><p>(1) Please allow us to select cryptsetup in &quot;Load Installer Modules&quot; <br />(2) Please allow us to use containers, eg /dev/mapper/*, or even whole disks, without demanding the creation of a partition. <br />(3) Why does the installer not include cryptsetup in the initramfs, and recognize crypttab, without my editing /target/etc/cryptsetup-initramfs/conf-hook?</p>]]></description>
			<author><![CDATA[dummy@example.com (Diagon)]]></author>
			<pubDate>Sat, 26 May 2018 10:21:51 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=9452#p9452</guid>
		</item>
	</channel>
</rss>
