For hardening a server I log in every time after reboot and manually do

systemctl stop systemd-udevd systemd-udevd-control.socket systemd-udevd-kernel.socket 

which works just fine. udevd is, after all, the daemon handling device change events, e.g. new USB devices and the like. Since the server is located in a datacentre several hundred miles away I am not planning on plugging in anything.

My question is:

Can I completely disable systemd-udevd (and the corresponding sockets) or will the system stop booting?

So, can I do

systemctl disable systemd-udevd systemd-udevd-control.socket systemd-udevd-kernel.socket 

?

I suppose the question is whether systemd-udevd is used during boot for finding disks, or for md software RAID, or other things.

(I am afraid I cannot try this out really as there is no remote console.)

For hardening a server I log in every time after reboot and manually do

systemctl stop systemd-udevd systemd-udevd-control.socket systemd-udevd-kernel.socket 

which works just fine. udevd is, after all, the daemon handling device change events, e.g. new USB devices and the like. Since the server is located in a datacentre several hundred miles away I am not likely to plug in any device.

My question is:

Can I completely disable systemd-udevd (and the corresponding sockets) or will the system stop booting?

So, can I do

systemctl disable systemd-udevd systemd-udevd-control.socket systemd-udevd-kernel.socket 

?

I suppose the question is whether systemd-udevd is used during booting for finding disks, or for md software RAID, or other things like network setup.

(I am afraid I cannot try this out by disabling it really as there is no remote console and the computer may just hang, requiring expensive remote hands.)