When plain '--rbind' is used, the 'umount' process executed later in the
setup process completely unmounts the bound filesystem, resulting in various
forms of breakage on the host used to do the setup. When a Live CD is used
and the system will be immediately shutdown/rebooted, this isn't an issue,
but in other scenarios it can be problematic.
Making the bind mounts 'private' avoids this problem. This patch changes
the setup guides for 'modern' distribution versions but does not touch
the older ones where this functionality may not be available.
Signed-off-by: Kevin P. Fleming <kevin@km6g.us>
Signed-off-by: Richard Laager <rlaager@wiktel.com>
I think there might be a mixup in the errata between paths suggested
in 2020-05-30 fix and those in original/2020-12-15 fix.
Closes#244
Signed-off-by: Richard Laager <rlaager@wiktel.com>
This ensures that the Live hostname does not leak into e.g. OpenSSH
server keys. It's not a huge deal either way, but this is nicer.
Closes#158
Thanks: anarcat
Signed-off-by: Richard Laager <rlaager@wiktel.com>
It is not necessary to install zfs-initramfs in the Live environment.
I am changing this to reduce delta with the upcoming Debian Bullseye
instructions.
Signed-off-by: Richard Laager <rlaager@wiktel.com>
This enables 3D acceleration, which is desirable for desktop
installations.
Reported-by: Scott G. Ainsworth <scott@ainsworth.us>
Signed-off-by: Richard Laager <rlaager@wiktel.com>
Closes#224
"It turns out that stopping the service is only effective done shortly
after reboot (< 1 minute?). After that a kernel upgrade might be in
progress and the service stops only after the kernel upgrade is
complete. After the upgrade finishes, installation can continue.
However, stopping the unattended kernel upgrade can render the media
unbootable (because /etc/kernetl/postinit.d/zz-deccompress-kernel might
not have run)."
I guess we'll go back to telling people to wait (a possibly long time)
for unattended-upgrades to finish.
This reverts commit d9f50ffa89.
Signed-off-by: Richard Laager <rlaager@wiktel.com>
Closes#225
I don't know what I was thinking last night... this was _adding_
nosplash, not removing it.
This reverts commit c5e77db483.
Signed-off-by: Richard Laager <rlaager@wiktel.com>
The partition script for sfdisk does not need another layer of
indirection. Instead of being a shell script that writes an sfdisk
script, it is now just an sfdisk script directly. The shell variables
are interpolated by the heredoc anyway.
Signed-off-by: Richard Laager <rlaager@wiktel.com>
Just like the other instructions, add some groups that do not exist by
default but which are listed in the usermod command.
Signed-off-by: Richard Laager <rlaager@wiktel.com>
In this version, the swapoff is being run on the non-Pi system. I did
not mean for people to disable their swap (even temporarily).
Signed-off-by: Richard Laager <rlaager@wiktel.com>
This reduces the number of steps in the "First Boot" section that are
not related to the first boot.
Reported-by: Jonathan Dumont <JOduMonT>
Signed-off-by: Richard Laager <rlaager@wiktel.com>
Use swapoff to ensure swap partitions are not mounted prior to
'sgdisk --zap-all'
Signed-off-by: Scott G. Ainsworth <scott@ainsworth.us>
Signed-off-by: Richard Laager <rlaager@wiktel.com>
[Applied the change to Debian Buster; removed Ubuntu 16.04 and 18.04.]
Signed-off-by: Scott G. Ainsworth <scott@ainsworth.us>
Signed-off-by: Richard Laager <rlaager@wiktel.com>
[Applied to Ubuntu 20.04 Raspberry Pi & Debian Buster.]
Update the getting started instructions for Ubuntu on a Raspberry Pi to
use the 20.04.3 LTS release.
Signed-off-by: Fernando Carolo <fcarolo@google.com>
Update the getting started instructions for Ubuntu on a Raspberry Pi to
use the 20.04.2 LTS release. Add `-a` flag to the `wipefs` command to
make sure it will erase any filesystem header from previous use of the
SD card.
Signed-off-by: Fernando Carolo <fcarolo@google.com>
There was already a note about ignoring a cryptsetup WARNING, but:
A) cryptsetup also prints an ERROR message, and
B) this also occurs at an earlier step.
Fixes#134
Signed-off-by: Richard Laager <rlaager@wiktel.com>
This was mentioned in #99 and I added it as an alternative option.
However, it seems to break GRUB; see #107. GRUB tries to parse
/proc/mounts and see a line like this:
systemd-1 /boot/efi autofs ...
From there, it gets "systemd-1" as the device name, and breaks.
Closes#107
Signed-off-by: Richard Laager <rlaager@wiktel.com>
We need the bpool to end up in zpool.cache. For some reason, this is
not happening normally on Ubuntu 20.04. I added the same steps to
Debian too, for good measure.
This was discussed in #120.
Signed-off-by: Richard Laager <rlaager@wiktel.com>
If the disk has been used before (with partitions at the same offsets),
previous filesystems (e.g. the ESP) will automount if not disabled.
Co-authored-by: attero <service-github@attero.me>
Signed-off-by: Richard Laager <rlaager@wiktel.com>
Closes#119
"The /root dataset is created with default world-readable permissions
(755). debootstrap would create /root with 700 permissions, but it
does not change the permissions if it already exists."
Reported-by: zxyrepf
Closes#115
I made Debian follow the Ubuntu approach, which comes from the Ubuntu
installer. There was a report (#99) of a problem with the old approach
used on Debian. In that issue, user foo-git linked to a Fedora feature
request which discusses automounting /boot/efi instead. I've offered
that as an alternative.
I am not switching to that outright, as following the Ubuntu installer
(where possible) is a goal of mine.
Suggested-by: foo-git
Closes#99
The fix for #97, 66233a1138, seems to
have created yet another issue (beyond #100):
"the link /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf
is dangling (since /run has just been clobbered by an empty tmpfs).
debootstrap seems to populate all manner of stuff in /run."
f1721edda7 (commitcomment-45770519)
I considered just reverting all of this, since the original issue only
occurred when copying in an existing system. Ignoring it was my
decision the first time this came up. But it's come up twice now.
Also, this mode is mentioned in the guide. Most importantly, if we are
not mounting a /tmpfs at /run in the normal case, then we could end up
with cruft in /run in the root filesystem which could potentially break
something or be confusing later if the /run tmpfs ever failed to mount.
So in the interest of correctness, I'd like to try to handle this.
I am now mounting a tmpfs at /mnt/run before the debootstrap step.
Signed-off-by: Richard Laager <rlaager@wiktel.com>
It was reported, in #97, that this is required when copying an existing
system installation into the root filesystem. It is probably a good
idea to do this all the time, to avoid the risk of stray junk ending up
in /run during the install process.
Suggested-by: Hevisko <hvjunk@gmail.com>
Signed-off-by: Richard Laager <rlaager@wiktel.com>
The convention here is to add a blank line between commands that
cannot be copied-and-pasted together. apt is such a command, as it
will eat the input from the paste.
It is not necessary to enable universe in the Live CD. zfs-initramfs is
in main these days.
I left universe (and multiverse) enabled in the installed system.
People who care can customize.
