From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: Feedback on Core Update 155 Testing Date: Wed, 17 Mar 2021 15:54:07 +0000 Message-ID: <530A2D41-7586-45D5-BF48-B89861082F48@ipfire.org> In-Reply-To: <1d2ca961-efce-70c0-cd94-e45c5ee38210@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1871261718197298789==" List-Id: --===============1871261718197298789== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello, > On 17 Mar 2021, at 12:40, Adolf Belka wrote: >=20 > Hi All, >=20 > On 17/03/2021 11:51, Adolf Belka wrote: >> Hi Everyone, >>=20 >> On 17/03/2021 10:35, Adolf Belka wrote: >>> Dear all, >>>=20 >>> There is feedback on the forum about IPFire not rebooting after update an= d needing a soft reset. After that it boots again. I also found the same effe= ct on my VM testbed system for testing. >>>=20 >>> https://community.ipfire.org/t/feedback-core-update-155-testing/4896 >>>=20 >>> That symptom triggered my memory (a bit late) and I found the discussion = about my sysvinit patch. >>>=20 >>> https://lists.ipfire.org/pipermail/development/2021-February/009403.html >>>=20 >>> So the fix never got created and it did not revert from the update. >>>=20 >>> Sorry for this mess. I will do a new patch to hopefully solve that proble= m for adding to Core Update 155, or you can revert sysvinit and I will make t= he update for the following Core Update. >>>=20 >> Thinking about this while out walking the dog, I realised if the decision = is to leave the updated package in Core Update 155 then I need to just create= a patch for whatever fix is required to make it work properly on first boot.= If the decision is to revert then I will need to create a patch for the full= update again. I will work on creating a patch to just fix what is now in CU1= 55 unless I hear differently from anyone. >>=20 >> Regards, >>=20 >> Adolf. >>=20 > Back in early 2018 the sysvinit team decided to move the initctl pipe from = /dev to /run. >=20 > The commit message for this was "FreeBSD apparently does not like named pip= es in /dev, so we move it to /run for better cross-platform compatibility." >=20 >=20 > I installed CU155 from scratch and I had no problem at all. The pipe was in= /run and nothing in /dev. >=20 > It is when an upgrade is carried out and the system starts with the pipe in= /dev, then the upgrade is not changing this. It is only changed after a forc= ed reboot by doing a soft reset. >=20 > It seems that we need some lines to remove the pipe from /dev and create it= in /run at an appropriate stage of the upgrade. Is the lfs file the correct = place to have these commands after the install commands or should they be in = the file used to carry out the Core Update. The lfs file doesn't seem the cor= rect place for this as it is only needed once for the upgrade from CU154 to C= U155. After that the pipe will always stay in /run. >=20 >=20 > I would appreciate advice on the best approach. If it should be in the upgr= ade script, where is that located? If it should be in the lfs do I just put t= he mknod command after the install command. Arne applied this which should be good enough until the system reboots and cr= eates the new pipe in the right place: https://git.ipfire.org/?p=3Dipfire-2.x.git;a=3Dcommitdiff;h=3D5d747ddb70e74c9= f5503618cc8aaa79b8f728cb3 -Michael >=20 > Regards, >=20 > Adolf. >=20 >>>=20 >>> I also found the same problem with ssh not working after the update as me= ntioned in the forum post. >>>=20 >>> Rebooting gave the following error message in the log. >>>=20 >>> /usr/sbin/sshd: /lib/libcrypt.so.1: version `XCRYPT_2.0' not found (requi= red by /usr/sbin/sshd) [FAIL] >>>=20 >>>=20 >>> People on the forum had deleted the /lib/libcrypt.so.1 link, which was ma= de to /lib/libcrypt-2.32.so and remade it to /usr/lib/libcrypt.so.1 and they = have reported that ssh then works. I have not tried that fix yet. >>>=20 >>> I checked the OpenSSH update patch I created and I didn't find anything r= elated to libcrypt or a change of libcrypt location from /lib to /usr/lib >>>=20 >>>=20 >>> Regards, >>>=20 >>> Adolf --===============1871261718197298789==--