You are not logged in.
Pages: 1
Topic closed
Hi,
in the last years arch linux became my favourite Linux Distribution because it was current and simple. Especially the startup with the old init scripts was easy to understood and easy to configure. It was perfect for my need, becaus I did not have any complicated network configuration or other special things. It was just a plain and simple desktop computer in my LAN at home and work.
Now you switched to systemd and the pain started. Systemd is just too complex to understand easily, and I do not see the advantage of a quicker boot. I Boot my system just once a day. I can wait 30 seconds more.
At the beginning my computer only booted up sucessfully every 10th time because it only could mount my windows partition sometimes. It seems that there was a race condition between my dmraid and mounting local file systems. Systemd could have ignored that mount failure...but no, I had to boot from the live arch CD and get rid of the auto mount...
Now I cannot power off correctly, because systemd just stops trying to unmount my local filesystems (in the pre step) nothing happens it is unclear on what event systemd waits. Having activated a permanent shell on a different terminal I could not see what systemd was doing or why it is waiting.
Are there others that feel the same way? Is there a documentation how to debug those systemd errors?
Regards,
Kretikus
Offline
Systemd is easy to use once you read the docs. I am guessing that this is a case of PEBKAC.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
Try reading the Wiki entry for systemd and keep your rant to yourself
Offline
systemd,
systemctl [enable/disable/start/stop/restart] whatever.service
journalctl
this was very simple for me to migrate too.
good luck
Offline
Kretikus, if you really do not like Arch anymore, change to a distro that you do like, and stop wasting everyone's time.
If, however, you want help with your issues, leave out the whiny rants, describe your issues in detail, do everything you can to fix them yourself, and ask nicely for help if you can't.
Offline
I agree. Arch sucks.
Offline
I agree. Arch sucks.
Time to close the thread.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
Try reading the Wiki entry for systemd and keep your rant to yourself
I did not want to rant, it' just frustating. Even after reading any documentation I found I still cannot make heads or tails out of debug logs that won't help:
[ 191.773244] systemd[1]: Stopping Local File Systems (Pre).
[ 191.773249] systemd[1]: local-fs-pre.target changed active -> dead
[ 191.773253] systemd[1]: Job local-fs-pre.target/stop finished, result=done
[ 191.773796] systemd[1]: Stopped target Local File Systems (Pre).
[ 191.773850] systemd[1]: Accepted connection on private bus.
[ 191.774066] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
[ 191.774162] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
After that the shutdown stalls ... so what happend there please?
Systemd is complex, I'am purely begging for more simplicity.
Offline
Allan wrote:I agree. Arch sucks.
Time to close the thread.
Good advice. Done!
@Kretikus: Try to understand what has been documented and discussed at length in the forums. If you want to stay with Arch and cannot really solve some problem you are free to start a new thread and ask to the point.
And, yes, please read the forum etiquette before posting another rant.
To know or not to know ...
... the questions remain forever.
Offline
Pages: 1
Topic closed