You are not logged in.
Pages: 1
Just noticed the symlink /bin/systemd which is owned by the systemd package got removed at systemd-204-1. My boot command-line used 'init=/bin/systemd' which is broken by this. My solution is to use init=/usr/lib/systemd/systemd' instead.
Wasn't using '/bin/systemd' the correct way since the removal of /sbin/init ?
Last edited by starfry (2013-05-13 12:36:53)
Offline
No, the correct way is to install systemd-sysvcompat
Online
I thought that was just for people who wanted to hang onto old ways. It is an optional dependency of systemd....
Offline
No, that's the recommended way and is the default on all new installations.
Offline
Offline
So the correct practice is to use
init=/usr/lib/systemd/systemd
Marking solved.
Offline
As arojas said, the correct practice is to install systemd-sysvcompat. It may be an optional dependency, but it is in `base` group, so it should be installed on all systems (unless someone wants to do something unusual, or just doesn't check if all of the base group is installed).
Offline
So the correct practice is to use
init=/usr/lib/systemd/systemd
Marking solved.
see part 6. you don't need to do anything if you have systemd-sysvcompat installed systemd-sysvcompat https://wiki.archlinux.org/index.php/Sy … stallation
Last edited by mamamia88 (2013-05-13 13:31:22)
Offline
If using systemd-sysvcompat then you get back the /sbin/init symlink which means you don't need to mess around with kernel parameters at boot, whicn is nice.
Offline
Not sure of the best place to post my question, but as far as having "systemd --user &" in my .xinitrc file, what would be the better option; to create a symlink, or just call /usr/lib/systemd/systemd?
Offline
Not sure of the best place to post my question, but as far as having "systemd --user &" in my .xinitrc file, what would be the better option; to create a symlink, or just call /usr/lib/systemd/systemd?
Welcome to Arch Linux
Please open a new thread. Be advised, I have no clue what you are asking there, so when you do open that thread, please be sure to include your question, what you have read, and what you are trying to do.
Thanks.
Leaving the thread open the event the original topic needs any additional discussion.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
He he, thanks for that post.
I got quite surprised that solution is so easy -> to remove init=/bin/systemd from the boot loader configs (since I have the systemd-sysvcompat installed). It got there in the early days of systemd adoption [1] and I may have missed the info that such a significant thing has changed :-/
[1] https://wiki.archlinux.org/index.php?ti … did=193253
Just a pitty that even the fallback ended up with a console, where typing on my usb wireless keyboard did not do anything and even the old PS/2 keyboard burried deep in boxes in garage was of no help (ctrl + alt + del worked, but only this) and I eventually had to create a live usb on another computer at work.
--
Milan Knizek
http://knizek.net
Offline
This happened to me as well, I guess it was the first time I rebooted since the systemd update to 204 and I got the warning that /bin/systemd was not found. I had it loading as a kernel parameter probably because of the wiki page that MilanKnizek pointed to. I was only able to get back in to my system by pointing init at /usr/lib/systemd/systemd (I don't have a live USB or CD available.
Thanks for the updated info that all I have to do is remove the "init=*" parameter
Offline
Welcome to Arch Linux
Please open a new thread. Be advised, I have no clue what you are asking there, so when you do open that thread, please be sure to include your question, what you have read, and what you are trying to do.
Thanks.
Leaving the thread open the event the original topic needs any additional discussion.
Was just a general question, I didn't realize I wasn't all too specific. My apologies!
(I have figured my issues out on my own, so I don't need to open a new thread.)
Partially on topic: From the update that deleted the sym link originally, I was having issue getting mpd to start, since I had it set up to run with systemd --user within my .xinitrc file. All I did was to recreate the sym link, and all was good after that. So a question that pertains to this - Is this a proper or improper way in resolving any issues regarding the original problem?
Offline
I would guess the proper way is a new thread?
Offline
Pages: 1