3 ms·

I think this is the most likely explanation for why systemd includes everything but the kitchen sink. For consistency, and ease of maintenance, having it all

I think this is the most likely explanation for why systemd includes everything but the kitchen sink. For consistency, and ease of maintenance, having it all under one umbrella is certainly a benefit (for the developers of systemd.) Also, NIH is a hell of a drug.

deleted 3y ago
[deleted]
yencabulator 3y ago
Systemd's catalogue of kitchen sinks is getting to be truly impressive. Here's an NVMe-over-TCP server, for some reason: https://github.com/systemd/systemd/blob/main/src/storagetm/storagetm.c https://github.com/systemd/systemd/blob/main/src/storagetm/s...
- znpy 3y ago
  Have you ever setup an iscsi shared device in linux? It’s quite complex and a bit messy. If systemd can make something similar (i still get a block device from another host in the network) in a simpler manner that would be just awesome, truly a huge win for everybody.
- acdha 3y ago
  This is a great example of an edge case which many people might never need but is really useful in a pinch: that’s what provides the equivalent of the Mac target disk mode, which is really handy if you need to repair a no longer-bootable system. https://github.com/systemd/systemd/commit/1761066b135f1a322c446f102343ea4aa61fe3ee https://github.com/systemd/systemd/commit/1761066b135f1a322c...
  - yencabulator 3y ago
    That's really not a great argument for why it belongs in systemd. Kitchen sinks are generally useful, but 17 kitchen sinks in a helicopter is not a good idea.
    - acdha 3y ago
      Where would you put it instead of something started by pid 1? It needs to boot the kernel and unlike macOS they have to run on a ton of different architectures so they can’t count on the firmware.
      - yencabulator 3y ago
        Huh? It's just another userspace program serving TCP.