Besides the obvious s/buster/bullseye/ sort of changes, this:
- Removes the use of backports. At this time, the difference is
minimal (2.0.6 vs 2.0.3) and I do not see a need to force backports
on users. They are free to add it later if they wish.
- Updates the sources.list for bullseye-security also being at
deb.debian.org.
- Updates the bpool features:
- device_rebuild has an explanation of why it is not used.
- livelist is now used.
- log_spacemap has been tested, but shares the same explanation as
spacemap_v2 for why it is not used.
Fixes#204Closes#126Closes#205
Thanks: Juri Grabowski <git-commit@jugra.de>
Thanks: Freezed <freezed@users.noreply.github.com>
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 reverts commit b81a471939.
We clashed while working on this. The Bullseye HOWTO in the above
commit was not rebased on the current Buster HOWTO, so a lot of its
delta between Buster and Bullseye is improper.
Signed-off-by: Richard Laager <rlaager@wiktel.com>
When trying to execute this script, it fails because it doesn't move to the home directory. I think there's meant to be a `cd` after setting the `HOME` variable.
When doing `apt upgrade` on my Debian machine, I saw that two packages was being held back. The reason cited was that the names had somewhat changed I think. It is worth noting that I'm running bullseye, so this might not be applicable to buster, which is the version documented here.
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.]
We waited for changes to make 404s work properly
(absolute links with prefix).
It's in master now, use it.
Signed-off-by: George Melikov <mail@gmelikov.ru>
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>
A couple people have come by IRC having issues where the root cause was that they were stuck on the CDDL/GPL prompt from apt never rendering because their container runtime console wasn't being detected as dumb/noninteractive by apt, but wasn't capable of displaying the prompt.
So let's add a warning about that, shall we?
