Am 13.11.24 um 14:59 schrieb Christoph Heiss: > diff --git a/proxmox-first-boot/etc/proxmox-first-boot.service > b/proxmox-first-boot/etc/proxmox-first-boot.service > new file mode 100644 > index 0000000..046bb24 > --- /dev/null > +++ b/proxmox-first-boot/etc/proxmox-first-boot.service > @@ -0,0 +1,16 @@ > +[Unit] > +Description=Proxmox First Boot Setup > +After=systemd-remount-fs.service > +Before=network-pre.target > +Wants=network-pre.target
I now I mentioned above ordering in our off-list chat, and it seems correct for the usecase where one needs to configure networking itself here. But, when summarizing our chat in the bug report, I re-read the use-cases and saw that there might be also some users that require the first-boot script to have the network available, e.g. to pull further automation stuff in. So it really would be great to allow overriding that ordering. Simplest way might be to leave it out here, or well go for the default we want (in doubt -> dice roll), and write out a systemd unit snippet during installation depending on a additional setting from the answer file. > +ConditionPathExists=/var/lib/proxmox-first-boot/pending-first-boot-setup > +ConditionPathIsReadWrite=/var/lib > + > +[Service] > +Type=oneshot > +RemainAfterExit=yes > +ExecStart=/var/lib/proxmox-first-boot/proxmox-first-boot > +ExecStartPost=/usr/bin/rm -v > /var/lib/proxmox-first-boot/pending-first-boot-setup > + > +[Install] > +WantedBy=network.target _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
