This reverts commit eae6e7ef19.
It can be quite subtle on network or HW change, so avoid that - we
plan to set the ifupdown2 option for a static MAC from a bridge port
instead.
matters now with unconfigured being the actual PID 1, earlier this
was handled by the initrd PID 1
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
and handle that one via a snippet instead of touching the main
'/etc/default/grub' config file.
distributor (and disabling os-prober for PVE) are already handled by the
product-specific meta packages via snippets - proxmox-ve was the last to
join this club in 7.0-2.
Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
back in 2018, commit 1accc6da659d8a02dcf1c2a636749e6f48fb9c2d
"Inotify : write network config : use modern syntax for options"
changed pve-common's /etc/network/interfaces writer to prefer options
with '-' over those with '_'.
having the installer write the old variant makes any modification of the
vmbr0 interface via the API also change these three lines to the new
variant - so let's do it right from the start.
Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
We may be using a more minimal debootstrap nowadays, but busybox is
still available, so compensate that by telling it to install
symlinks in /bin and /sbin for those applets it knows and are not
already existing.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
Use the biggest terminus font we can get our hands on, and use the
Uni2 variant, which seems like an OK trade-off (the installer is
rather ascii anyway).
The detection uses the console columns in such away that high-dpi
screen should be detected but just wide-formats (like 21:9) should
not. This is a bit brittle, but even miss-detecting it should still
allow using it (the installer is made for 1024x768, which when
doubled still fits on WQXGA (2560x1600) and mostly on 1440p too.
It could be more robust to depend on edid-decode, but as physical
dimensions are not required there, and even if specified often quite
off, it's not a sure thing either. So go for simple first.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
can for now only work if booted via debug mode as one needs to
manually call iwctl in the debugshell, so only call it in the debug
case. This is currently more of a rough experimental way for the
brave and knowing.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
Previously we used a ugly hack to extract the device from the whole
line returned by passing it to bash's `set`, which assigns remaining
arguments it does not know about (or after "--") to $1, $2, etc.
This is ugly due to:
* not using "--", so it could break easily
* being quite subtle in general, e.g., shellcheck does not likes
unquoted variable expansions, so one would add quotes around
breaking the actual use case
Just use awk to do both the grep and extraction, which is much
clearer to do
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
We used to ship our own grub in the installer, originally due to ZFS
support, but we also used it to setup a slightly modified
`/etc/default/grub`. We do not need a self-build grub for technical
reasons like ZFS support anymore, so avoid the need to ship it and
move over deploying the config changes to the installer.
Just write out the whole config, much easier to see what's going on
compared to some `sed` calls.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
placing the common stuff top-level and the per-product stuff one
directory-level down allows to access all used resources (css,
images) from a common base path without hacking to much around.
Per-product files are always preferred.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
