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>
Depends on the install env. having a cd-info file to parse the
product from, which we have since PVE 6.1 ISO release 2.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
proxmox-boot-tool now supports configuring grub to boot from the ESPs
the installer creates on all (bootable) disks - use this approach
for zfs installs.
Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
the argument "but if someting in raid0 fails all is dead" is true but
misses the point completely, namely:
* firmware is weird and sometimes allows booting only from certain
devices, which we cannot know here
* potentially only the boot partition could be corrupted/broken/...
in which case another dev in the raid 0 could allow successful
booting
In short, we can only win if we use all devices as boot devices, the
512 MiB lost in some devices are negligible, and they resulted in an
uneven storage space distribution.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
We had reports about problems stemming from skewed clocks during
installation, especially if their time was in the future during
installation and on first real boot got synced up, certs may not be
valid yet, RRD may has written data before that correcting time-sync
went through and errors afterwards, once time jumped back, and lots
of other issues.
So, depend on the modern and nifty, but still small, NTP
implementation `chrony`. Start its daemon just after we asked for a
DHCP lease, as then it can directly try to sync with one of the
(Debian namespaced) NTP pools time server.
In the worst case (no network, no server available) we are as good as
now, but if chrony can sync the time we avoid lots of issues and
breakages
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
just some nitpicky changes.
v2:
- remove tag files
@Thomas: Like you thought, they are autogenerated by some vim plugin.
They usually sit quitely in the untracked files, but this time, I guess
I somehow I managed to add them in without noticing.. Apologies!
Signed-off-by: Dylan Whyte <d.whyte@proxmox.com>
this patch partially reverts 8bc528041b
by writing /etc/default/keyboard and running `setupcon` in the background
the delay should not harm the UX in the installer
Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
certain tasks done during the installer need not block the GUI (e.g. setting
the keymap of the console, to have the correct one set in the shell on vt3)
and take a longer time.
This patch adds a simple run_in_background method, which forks and runs the
provided code in the child. Before exiting the children get reaped.
Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
currently when using the previous/next buttons the keyboard layout gets
defined based on the detected/selected country, even if it was set to a
different value explicitly.
This patch changes the behaviour to only update the layout and set it in
the installer if it got actively changed, or if a different country was
selected
Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
add more inner margin for scroll bar and reduce outer margins to
avoid to much empty border space.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
in create_country_view() when setting the keyboard config
setupcon is too slow, causing installer to hang for some
seconds when switching to/from country view.
setxkbmap is enough during the installation (next step
password & email works fine with different keymaps), vt
is largely unused during it anyway.
Signed-off-by: Oguz Bektas <o.bektas@proxmox.com>
Only auto reboot if no error happened.
default to on, as this is normally wanted behavior - the success
screem does not allow to do anything else anyway, and the IP address
gets then also showed as issue banner after that reboot.
show some countdown (it's set to 5 seconds, but due some internal
delay it more like 3s)
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
Use two fields it a single row: [ <address> ] / [ <mask> ]
Make the others also a bit bigger for symmetry.
Adapt html templates respectively.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
