this post was submitted on 23 Sep 2024
556 points (96.8% liked)

linuxmemes

20703 readers
1266 users here now

I use Arch btw

Sister communities:

Community rules

  1. Follow the site-wide rules and code of conduct
  2. Be civil
  3. Post Linux-related content
  4. No recent reposts

Please report posts and comments that break these rules!

founded 1 year ago
MODERATORS
[email protected]
[email protected]
556
Average systemd debate (lemmy.world)
submitted 12 hours ago* (last edited 12 hours ago) by [email protected] to c/[email protected]
86 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 23 points 3 hours ago* (last edited 2 hours ago) (1 children)

systemd gets stuck because it's trying to mount two separate partitions to the same mount point

Uh... Sounds like it's not really systemd's fault, your setup is just terrible.

I've tried fixing it, but all I did was break it more.

If you're unable to fix it, maybe get somebody else? Like, this doesn't sound like it's an unfixable issue...

[–] [email protected] 11 points 3 hours ago

Uh… Sounds like it’s not really system’s fault, your setup is just terrible.

I don't know his specific issue, but the general behavior of systemd going completely nuts when something is a bit 'off' in some fashion that is supremely confusing. Sure, there's a 'mistake', but good luck figuring out what that mistake is. It's just systemd code tends to be awfully picky in obscure ways.

Then when someone comes along with a change to tolerate or at least provide a more informative error when some "mistake" has been made is frequently met with "no, there's no sane world where a user should be in that position, so we aren't going to help them out of that" or "that application does not comply with standard X", where X is some standard the application developer would have no reason to know exists, and is just something the systemd guys latched onto.

See the magical privilege escalation where a user beginning with a number got auto-privileges, and Pottering fought fixing it because "usernames should never begin with a number anyway".