| Summary: | sys-apps/systemd-200-r1 announces to remove /bin/systemd - why not /sbin/systemd ? | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Ulenrich <ulenrich> |
| Component: | [OLD] Core system | Assignee: | Gentoo systemd Team <systemd> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | 10.0 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| See Also: | https://bugs.gentoo.org/show_bug.cgi?id=465236 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
It's a very bad one since it's inventing something completely opposite to the direction upstream goes. While at it, I was thinking of making /sbin/init a symlink with eselect module to switch it. That would involve renaming sysvinit binary, though. |
> You are using a compatibility symlink to run systemd. The symlink > will be removed in near future. Please update your bootloader > to use: > init=/usr/lib/systemd/systemd There is an almost canonical /sbin/init for years. The /bin/systemd symlink was somehow weird in the first place therefore, because systemd is not supposed to be called directly. I will create myself a symlink ln -s /usr/lib/systemd/systemd /sbin/systemd Is this a bad habit? Or would this be convenient for all users? Because I don't expect all users to get it right using this long path init=/usr/lib/systemd/systemd at CMDLINE especially if they edit the grub at boot time. :( Reproducible: Always