| View previous topic :: View next topic |
| Author |
Message |
equaeghe
l33t
Joined: 22 Feb 2005
Posts: 637
|
 Posted: Sat Jan 20, 2018 9:15 pm Post subject: systemd rootprefix migration: no systemd-234 in portage |
 |
|
There was a news item about “systemd rootprefix migration”:
| Code: | 2017-07-16-systemd-rootprefix
Title systemd rootprefix migration
Author Mike Gilbert <floppym@gentoo.org>
Posted 2017-07-16
Revision 3
Starting with the 234 release, Gentoo's sys-apps/systemd package will
be built with rootprefix=/. This means most of the included programs
and system units will be installed under /lib/systemd instead of
/usr/lib/systemd.
This change brings Gentoo into alignment with most other distros which
still maintain a distinction between boot-critical programs in /, and
less critical programs in /usr. This also means that users with a
separate /usr filesystem will have an easier time booting if their
initramfs should become corrupt or fail.
Symlinks are provided for /usr/lib/systemd/systemd and
/usr/lib/systemd/systemd-shutdown to avoid breaking bootloader configs
and to allow the system to be shutdown/rebooted without issue. These
symlinks will likely be removed in the 235 release, so please update
your boot configuration to reference init=/lib/systemd/systemd.
This change will be mostly transparent to typical users. You may notice
that system units move from /usr/lib/systemd/system to
/lib/systemd/system as you upgrade/re-install packages; this is normal.
Units will function properly from both locations.
After upgrading, please run systemctl daemon-reexec ensure that the new
version is executed. Also make sure to regenerate your initramfs if it
includes a copy of systemd (dracut).
If you encounter a problem, please report a bug. |
However, there is no systemd-234 in portage, 233 is current stable and it seems 236 is going to be the next stable. I suppose this means I should immediately change the init in the boot config once 236 is installed, as it seems there will not be a grace period with /lib/systemd/systemd. being symlinked to /usr/lib/systemd/systemd. Is this correct?
Furthermore, what am I missing here, or did the developers make some mistake? |
|
| Back to top |
|
 |
Naib
Watchman
Joined: 21 May 2004
Posts: 6051
Location: Removed by Neddy
|
| Posted: Sat Jan 20, 2018 10:24 pm Post subject: |
|
|
It was pulled, a number of bugs. One of which is this: https://forums.gentoo.org/viewtopic-p-8098458.html
ALso
| Code: | Author: Mike Gilbert <floppym@gentoo.org> 2017-10-28 19:58:21
Committer: Mike Gilbert <floppym@gentoo.org> 2017-10-28 19:58:29
Parent: 2e698f887553690f3172ab1c1cabf36296dd901e (sys-apps/systemd: backport fix for CVE-2017-9217)
Child: 30dafbf628705e2907443d7e440b66d5fccd8b16 (app-editors/atom: remove unused patch.)
Branches: remotes/origin/stable, stable
Follows:
Precedes:
sys-apps/systemd: remove old
Package-Manager: Portage-2.3.12_p5, Repoman-2.3.3_p75
ndex 0bfb021bca2..800a79b82c3 100644
@@ -1,4 +1,3 @@
DIST systemd-233-man.tar.gz 31386 SHA256 825e62eb82c4e23997061fc8f56f7ec9bb1e6ac1111d279c76c926cc2bfbf1dc SHA512 cc5215d3590ffc3c9203a64c14d6adeb0148c421c1396b8c1e43dcb58763b687ce99bdee327dd8a00abab7198171e73b22109a3f2032e4cec6adf2dcc85acf40 WHIRLPOOL ff1f36beff377f675047271df38503e8b71d615ea73c5fdfebf465edaf1fe29b4f89e3194d65cdf84eec9b7c3156de597627fdaffa4b86018520aaa127a7a159
DIST systemd-233.tar.gz 4660737 SHA256 8b3e99da3d4164b66581830a7f2436c0c8fe697b5fbdc3927bdb960646be0083 SHA512 5ad5329ea116d973cf67096f7e7ad28e9ea0905696e9451291f1d25e5064f4a9bfcfae87e912996c6a38397e9f4a148d4ccecfa9b70f7ecdf04deadb61784c8e WHIRLPOOL ce19f6a546b8f899cfa952e49d47f063fd29186be4a53391bc30ea2c487eb2c140a74ad843a1dc499bb61bba3e9ca055613852291e38b85af5d79c59409dc176
-DIST systemd-234.tar.gz 4800186 SHA256 da3e69d10aa1c983d33833372ad4929037b411ac421fb085c8cee79ae1d80b6a SHA512 762336a7d96c6583cf71cad62efce95a0ed93cd0a0d7251f128d10dba8200c0c8df0e5a7d168179ababa5b221295a231e73b7e7ea2697cb3fb5c1b33538efa68 WHIRLPOOL 9ff9f25ce82514db969a427eee51c0483b2bcaaa611f93c1fc17c356ea25eee712217708c54101ecaafd835cd8ac988b16e8ad411b48541a32442b9a0d148f07
DIST systemd-235.tar.gz 6586406 SHA256 25811f96f5a027bf2a4c9383495cf5b623e385d84da31e473cf375932b3e9c52 SHA512 243f2eb5340fa37dd1286eaa63e83387bda9e03953af266cd6196a37535a13491482caf14c6ab10608bba4ed23b6c41923608e52017e0c26988ed72ddd2b9993 WHIRLPOOL 05e50b31f7b3b1cd756abd1580dddae0e114953857564133784fc43b9ecd0e203ee534aaf76531ca7af5c43b03b9b73c6cbbbb1caf5afb17502555cc52fe06cd |
_________________
| Quote: | | Removed by Chiitoo |
|
|
| Back to top |
|
|
Anon-E-moose
Watchman
Joined: 23 May 2008
Posts: 6098
Location: Dallas area
|
| Posted: Sun Jan 21, 2018 10:50 am Post subject: |
|
|
Ah yes, nothing like following RH into the depths of the abyss 
_________________
PRIME x570-pro, 3700x, 6.1 zen kernel
gcc 13, profile 17.0 (custom bare multilib), openrc, wayland |
|
| Back to top |
|
|
mv
Watchman
Joined: 20 Apr 2005
Posts: 6747
|
| Posted: Sun Jan 21, 2018 6:39 pm Post subject: Re: systemd rootprefix migration: no systemd-234 in portage |
|
|
| equaeghe wrote: | | as it seems there will not be a grace period with /lib/systemd/systemd. being symlinked to /usr/lib/systemd/systemd. Is this correct? |
With sys-apps/systemd-236-r5 the symlink still seems to be installed. In any case, I would currently check after every sytemd emerge where the binary actually becomes installed and modify the boot-loader configuration correspondingly so that it is not necessary to rely on any symlinks for booting. |
|
| Back to top |
|
|
PeeJay
n00b
Joined: 15 Aug 2004
Posts: 46
Location: Sydney, Australia
|
| Posted: Tue Jan 23, 2018 10:43 pm Post subject: Re: systemd rootprefix migration: no systemd-234 in portage |
|
|
| equaeghe wrote: | | I suppose this means I should immediately change the init in the boot config once 236 is installed, as it seems there will not be a grace period with /lib/systemd/systemd. being symlinked to /usr/lib/systemd/systemd. Is this correct? |
That would seem to be the case. I was trying to install a new system which came with 233 on the stage3, I followed the instructions on the wiki, and then ended up in this thread when it wouldn't boot because /lib/systemd/systemd didn't exist  |
|
| Back to top |
|
|
mv
Watchman
Joined: 20 Apr 2005
Posts: 6747
|
| Posted: Wed Jan 24, 2018 6:03 am Post subject: Re: systemd rootprefix migration: no systemd-234 in portage |
|
|
| PeeJay wrote: | | and then ended up in this thread when it wouldn't boot because /lib/systemd/systemd didn't exist |
As mentioned, sys-apps/systemd-236-r5 still installed the symlink /usr/lib/systemd/systemd -> /lib/systemd/systemd here.
If your mail wasn't a typo and you don't have the latter file, something else is broken. |
|
| Back to top |
|
|
PeeJay
n00b
Joined: 15 Aug 2004
Posts: 46
Location: Sydney, Australia
|
| Posted: Wed Jan 24, 2018 6:27 am Post subject: Re: systemd rootprefix migration: no systemd-234 in portage |
|
|
| mv wrote: | | If your mail wasn't a typo and you don't have the latter file, something else is broken. |
I was following the Gentoo Systemd wiki which said add "GRUB_CMDLINE_LINUX="init=/lib/systemd/systemd", but that file didn't exist on the stage3 filesystem I installed which had systemd-233 (a week old I think). Upgraded systemd and all is well. |
|
| Back to top |
|
|
mv
Watchman
Joined: 20 Apr 2005
Posts: 6747
|
| Posted: Wed Jan 24, 2018 8:15 am Post subject: Re: systemd rootprefix migration: no systemd-234 in portage |
|
|
| PeeJay wrote: | | I was following the Gentoo Systemd wiki which said add "GRUB_CMDLINE_LINUX="init=/lib/systemd/systemd", but that file didn't exist on the stage3 filesystem I installed which had systemd-233 |
That's a different thing: This stage3 (and the systemd-233 on it) simply pre-dates the change which was announced in the NEWS item.
It is understandable that the Wiki already refers to the current version and not to the "outdated" one.
It is unfortunate (and bad luck for you) that this means that currently that information and the distributed stage3 do not match, but the problem will probably resolve itself when the next stage3 is distributed... |
|
| Back to top |
|
|
piotr5
Tux's lil' helper
Joined: 14 Dec 2012
Posts: 117
|
| Posted: Mon Feb 05, 2018 11:21 am Post subject: |
|
|
just installed sys-apps/systemd-236-r5 and it seems the ebuild has deleted /usr/lib/systemd/systemd by writing a symlink there, unless I give the option USE=usrmerge for that installation. funnily this results in a symlink from /lib/systemd to /usr/lib/systemd which actually boots! this raises the question: did I just remove some important files under /lib/systemd installed by other packages? funnily | Code: | | qfile /lib/systemd |wc |
tells me there are exactly 40 packages installing that directory and the command
| Code: | | emerge -1O /usr/lib/systemd/system |
installs exactly those 40 programs except that sys-apps/systemd gets installed instead of sys-apps/gentoo-systemd-integration. so to be sure, I reinstalled all 41 packages. but did I miss something? |
|
| Back to top |
|
|
|
Portage & Programming
