Even if nothing got fried they were detected only at boot.
Auto-detecting and auto-mounting removable devices has gone through a lot of stages in Linux.
The systemd code was written primarily by Leonard Poettering.
Upstart has been the default in Ubuntu since 6.10 Edgy Eft and is available in most distros.
Then there are network services that could be on-demand like file shares, printers, VNC, SSH, and so on.
The bottom line is in these modern times way more stuff happens after startup, so instead of trying to anticipate everything you might need and start it all at boot, why not build a system that launches and stops processes on demand?
Remember the fun old days of manually mounting and unmounting CDs and USB sticks?
And making fun of Windows and Mac refugees who thought that was weird and dumb? But Linux was still a baby, so we had to deal with it.
I have no use for either, so I always disable them.
You can see these with $ netstat -a --protocol=unix Active UNIX domain sockets (only servers) Proto Ref Cnt Flags Type State I-Node Path unix 2 [ ACC ] STREAM LISTENING 4836 /var/run/dbus/system_bus_socket unix 9 [ ] DGRAM 4584 /dev/log unix 3 [ ] STREAM CONNECTED 489456 /tmp/orbit-carla/linc- aaa-0-476044c676da9 unix 3 [ ] STREAM CONNECTED 489455 unix 3 [ ] STREAM CONNECTED 489452 /tmp/orbit-carla/ linc-8ba-0-45fe9270a46b2 [...] As you can see the sockets have inodes, following the tradition of “everything in Unix is a file.” So you can perform various operations on them with standard Linux file utilities, which is a fun topic for another day.
So all sockets for all daemons can be created in one step, and then all daemons in a second step.
So what’s with this new systemd thingy, and what benefits does it bring to us mere Linux users? At boot the kernel launches PID 1, the very first process to run at startup.
(Run the command to see a nice artistic ASCII diagram of your process tree.) It used to be that the BIOS and sysvinit were equal offenders in dragging boot times out to a minute or more.