Ви не можете вибрати більше 25 тем Теми мають розпочинатися з літери або цифри, можуть містити дефіси (-) і не повинні перевищувати 35 символів.
lub fc0002114c remove smartmontools
nvme-cli also can display S.M.A.R.T. values

lol
1 місяць тому
authorized_keys update keys 2 роки тому
config/etc add sysctl for inotify 1 місяць тому
hardware fixup of last commit 1 місяць тому
README.md streamline readme example 1 місяць тому
post-debootstrap-installer.sh remove smartmontools 1 місяць тому
reset.sh make reset multithreaded and shorter 2 роки тому
setup.sh use longform arguemtsn for mkdir 1 місяць тому

README.md

These scripts setup a blank hardware server according to our requirements including partitions, raids, debootstrap, package installation and various other configuration. The goal is to create a server ready to join into the swarm.

Usage (from a live system):

# (!) wipes the start sectors of all disks (!)
# (!) review before executing (!)
./reset.sh
reboot

./setup.sh <template> <fqdn>

# example:
apt-get update && apt-get -y dist-upgrade && git clone https://gitea.lubiland.de/lubiland/hardware-setup.git && cd hardware-setup
./setup.sh hetzner_ax51-nvme asef.lubi.link


# Unlock the disk after booting the server from disk:
# Dropbear is configured on 222 and only allows the user root
ssh -p 222 root@<fqdn>
cryptroot-unlock

setup.sh executes the hardware specific template files, debootstraps and invokes the actual installer inside the fresh environment.
As much as possible should be done in the chroot, as only there we have control over the software (the live system is normally provided by the hardware provider).

Templates (hardware/*) consist of three files:

  • esp - a symlink to the desired ESP partition
  • parted.sh - script to prepare the partitions. Should create ESP (/boot/efi), md0 (/) and md1 (/boot)
  • network.sh - creates the neccessary configs in /etc/systemd/network

config/* gets copied to the chroot and contains static config files

authorized_keys/* is used to create the users and populate their respective ~/.ssh/authorized_keys