systemd(ont) (www.arscyni.cc)
submitted 6 months ago by to c/linux@lemmy.ml
⚜️ 1 🚀 1
 

Because of the ubiquity, nay, monopoly of systemd I always assumed it was miles ahead of other init systems. Nope. I've been using a non-systemd environment for a while and must say I'm surprised by how little breaks, i.e., next to nothing. Moreover, boot and shutdown times are faster, and more of that good stuff. I suggest trying it out.

https://nosystemd.org/.

A photoshop of a group of sprinters where all the runner-ups have their starting block stuck to their feet, referring to systemd. The winner is free of starting block, representing the other init systems, OpenRC, runit, dinit, s6, et cetera.
you are viewing a single comment's thread
view the rest of the comments
[–] 1 point 6 months ago (1 child)

It is exactly configured as default.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 5 points 6 months ago

    Strange I guess I am not aware of any distros that come with network drives pre-configured. But either way that would be a configuration error on the distro's side then. Waiting for a network share to be available is actually a feature to many.

    Say for instance you had critical data on the network share then you might not want to boot if that is not available. And if you don't then you might mark the share as nobootwait.

    Without knowing what the configuration on this specific drive you are having trouble with I really could not say what is wrong.

  • source
  • parent