[pve-devel] [RFC PATCH installer 2/5] fix #5579: first-boot: add initial service packaging
Thomas Lamprecht
t.lamprecht at proxmox.com
Fri Nov 15 14:39:16 CET 2024
Am 15.11.24 um 14:34 schrieb Christoph Heiss:
> On Thu, Nov 14, 2024 at 09:23:48PM +0100, Thomas Lamprecht wrote:
>> [..]
>> 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.
>
> Thinking about this again, while implementing - if we need to customize
> the unit file, do we want to:
>
> - create an `override.conf` file in
> `/etc/systemd/system/proxmox-first-boot.service.d/`, like systemd
> would do it when using `systemctl edit <service>`?
> Disadvantage is, that that file isn't removed when removing the
> `proxmox-first-boot` package from the system (although we could do it
> via postrm maybe?)
I'd either use above or as an additional alternative: ship the different
variants as separate complete unit files with a common Alias (to convey
that they're the "same" thing) and enable only the one (manually) that is
configured. That would keep every file fully covered by the package
system.
>
> - edit the unit file directly? That would mean that e.g. `debsums -c`
> would complain.
>
> - even bother with a separate package and instead just write the unit
> file directly to /etc/systemd/system?
> Disadvantage here is that it would be a "lost" file, not managed by
> dpkg, and administrators would have to remove the file directly, if
> they want/need to.
>
> I have implemented the first variant for now, for testing. But not sure
> if it's the best way to go.
>
Fine by me, but maybe you find some benefits on the separate unit file
one, not to hard feelings here.
More information about the pve-devel
mailing list