From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter =?utf-8?q?M=C3=BCller?= To: development@lists.ipfire.org Subject: Re: IPFire 2.27 - Core Update 179 is available for testing Date: Wed, 23 Aug 2023 14:45:00 +0000 Message-ID: <017f8cd9-e512-44f3-b80c-e2c4422a0ee3@ipfire.org> In-Reply-To: <09305758-fae5-402c-824a-57a9f3b6845d@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1909126865047263531==" List-Id: --===============1909126865047263531== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello *, aside from the patch I just submitted for the update.sh script of Core Update= 179, one minor difference struck me after the upgrade: While starting pppd again, = the following message is logged: > Aug 23 16:12:24 maverick kernel: pppd uses obsolete (PF_INET,SOCK_PACKET) This did not occur with ppp 2.4.9, but does not seem any noticeable impact ei= ther. Should we be concerned about it? Thanks, and best regards, Peter M=C3=BCller > Feedback on the Extra HD update. >=20 > It seems to not be working with LVM based systems on my vm testbed. >=20 > I had two LVM volumes defined in CU178 (Started in CU177 after the problems= with LVM a short while back) >=20 > In CU178 rebooting the system auto mounts the LVM volumes and they show up = as mounted on the Extra HD page. >=20 > I then upgraded to CU 179 and after the update the dm-0 and dm-1 volumes sh= ow up on the Extra HD page but without any mount point defined and no icons t= o allow to mount them. The raw partitions from the volumes (sda1 and sdb1) sh= ow up on the page with an edit pencil icon. >=20 > The LVM volumes are also no longer mounted and rebooting does not auto moun= t them as previously. I can manually mount them to the mount point but reboot= ing then removes them from the mount point and does not attach them back. >=20 > I will add this into the Extra HD bug#12863 report together with the screen= shot of the page as it was with CU178 and now with CU179. >=20 > Regards, >=20 > Adolf. >=20 >=20 > On 21/08/2023 12:00, Michael Tremer wrote: >> Oh, sorry. I just merged this into core 180. >> >> I will fix this... >> >>> On 21 Aug 2023, at 10:46, Adolf Belka wrote: >>> >>> Hi Michael, >>> >>> Three days ago the OP from the request to update ppp to 2.5.0 had already= tried it out from CU179 Testing. >>> >>> He identified that there was a problem with the location for the run stat= e directory for the pid files. >>> >>> /usr/var/run/ was being used rather than /var/run so the directories did = not exist when trying to run ppp. >>> >>> I submitted a patch to correct this which needs to be merged into CU179 T= esting. >>> https://lists.ipfire.org/pipermail/development/2023-August/016337.html >>> >>> Regards, >>> Adolf. >>> >>> >>> On 21/08/2023 10:00, IPFire Project wrote: >>>> IPFire Logo >>>> there is a new post from Michael Tremer on the IPFire Blog: >>>> *IPFire 2.27 - Core Update 179 is available for testing* >>>> =C2=A0=C2=A0=C2=A0 Just after releasing Core Update 178 which was added = into our release cycle to address Intel's and AMD's latest CPU vulnerabilitie= s, we are back on track with our regular schedule. This release features Indi= rect Branch Tracking for user space, a completely rewritten ExtraHD amongst a= large number of package updates and the usual bunch of bug fixes. >>>> Click Here To Read More >>>> The IPFire Project >>>> Don't like these emails? Unsubscribe . >> --===============1909126865047263531==--