Re: IPFire 2.27 - Core Update 179 is available for testing

Re: IPFire 2.27 - Core Update 179 is available for testing

[Adolf Belka]

[-- Attachment #1: Type: text/plain, Size: 1298 bytes --]

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 state 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 Testing.
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*
> 
>     Just after releasing Core Update 178 which was added into our release cycle to address Intel's and AMD's latest CPU vulnerabilities, we are back on track with our regular schedule. This release features Indirect 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 <https://blog.ipfire.org/post/ipfire-2-27-core-update-179-is-available-for-testing>
> 
> The IPFire Project
> Don't like these emails? Unsubscribe <https://people.ipfire.org/unsubscribe>.
> 

Re: IPFire 2.27 - Core Update 179 is available for testing

[Michael Tremer]

[-- Attachment #1: Type: text/plain, Size: 1463 bytes --]

Oh, sorry. I just merged this into core 180.

I will fix this...

> On 21 Aug 2023, at 10:46, Adolf Belka <adolf.belka(a)ipfire.org> 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 state 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 Testing.
> 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*
>>    Just after releasing Core Update 178 which was added into our release cycle to address Intel's and AMD's latest CPU vulnerabilities, we are back on track with our regular schedule. This release features Indirect 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 <https://blog.ipfire.org/post/ipfire-2-27-core-update-179-is-available-for-testing>
>> The IPFire Project
>> Don't like these emails? Unsubscribe <https://people.ipfire.org/unsubscribe>.

Re: IPFire 2.27 - Core Update 179 is available for testing

[Adolf Belka]

[-- Attachment #1: Type: text/plain, Size: 2526 bytes --]

Feedback on the Extra HD update.

It seems to not be working with LVM based systems on my vm testbed.

I had two LVM volumes defined in CU178 (Started in CU177 after the problems with LVM a short while back)

In CU178 rebooting the system auto mounts the LVM volumes and they show up as mounted on the Extra HD page.

I then upgraded to CU 179 and after the update the dm-0 and dm-1 volumes show up on the Extra HD page but without any mount point defined and no icons to allow to mount them. The raw partitions from the volumes (sda1 and sdb1) show up on the page with an edit pencil icon.

The LVM volumes are also no longer mounted and rebooting does not auto mount them as previously. I can manually mount them to the mount point but rebooting then removes them from the mount point and does not attach them back.

I will add this into the Extra HD bug#12863 report together with the screenshot of the page as it was with CU178 and now with CU179.

Regards,

Adolf.


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 <adolf.belka(a)ipfire.org> 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 state 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 Testing.
>> 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*
>>>     Just after releasing Core Update 178 which was added into our release cycle to address Intel's and AMD's latest CPU vulnerabilities, we are back on track with our regular schedule. This release features Indirect 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 <https://blog.ipfire.org/post/ipfire-2-27-core-update-179-is-available-for-testing>
>>> The IPFire Project
>>> Don't like these emails? Unsubscribe <https://people.ipfire.org/unsubscribe>.
> 

Re: IPFire 2.27 - Core Update 179 is available for testing

[Peter Müller]

[-- Attachment #1: Type: text/plain, Size: 3053 bytes --]

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 either.

Should we be concerned about it?

Thanks, and best regards,
Peter Müller


> Feedback on the Extra HD update.
> 
> It seems to not be working with LVM based systems on my vm testbed.
> 
> I had two LVM volumes defined in CU178 (Started in CU177 after the problems with LVM a short while back)
> 
> In CU178 rebooting the system auto mounts the LVM volumes and they show up as mounted on the Extra HD page.
> 
> I then upgraded to CU 179 and after the update the dm-0 and dm-1 volumes show up on the Extra HD page but without any mount point defined and no icons to allow to mount them. The raw partitions from the volumes (sda1 and sdb1) show up on the page with an edit pencil icon.
> 
> The LVM volumes are also no longer mounted and rebooting does not auto mount them as previously. I can manually mount them to the mount point but rebooting then removes them from the mount point and does not attach them back.
> 
> I will add this into the Extra HD bug#12863 report together with the screenshot of the page as it was with CU178 and now with CU179.
> 
> Regards,
> 
> Adolf.
> 
> 
> 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 <adolf.belka(a)ipfire.org> 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 state 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 Testing.
>>> 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*
>>>>     Just after releasing Core Update 178 which was added into our release cycle to address Intel's and AMD's latest CPU vulnerabilities, we are back on track with our regular schedule. This release features Indirect 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 <https://blog.ipfire.org/post/ipfire-2-27-core-update-179-is-available-for-testing>
>>>> The IPFire Project
>>>> Don't like these emails? Unsubscribe <https://people.ipfire.org/unsubscribe>.
>>

Re: IPFire 2.27 - Core Update 179 is available for testing

[Adolf Belka]

[-- Attachment #1: Type: text/plain, Size: 3465 bytes --]

Hi Peter,

On 23/08/2023 16:45, Peter Müller wrote:
> 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 either.
>
> Should we be concerned about it?
I don't know but it was raised as an issue in the ppp github after 
version 2.5.0 was issued.

I will apply the fix with a patch that they merged into a new update 
submission. When the next version is released then this patch can be 
removed.

Regards,
Adolf.

> Thanks, and best regards,
> Peter Müller
>
>
>> Feedback on the Extra HD update.
>>
>> It seems to not be working with LVM based systems on my vm testbed.
>>
>> I had two LVM volumes defined in CU178 (Started in CU177 after the problems with LVM a short while back)
>>
>> In CU178 rebooting the system auto mounts the LVM volumes and they show up as mounted on the Extra HD page.
>>
>> I then upgraded to CU 179 and after the update the dm-0 and dm-1 volumes show up on the Extra HD page but without any mount point defined and no icons to allow to mount them. The raw partitions from the volumes (sda1 and sdb1) show up on the page with an edit pencil icon.
>>
>> The LVM volumes are also no longer mounted and rebooting does not auto mount them as previously. I can manually mount them to the mount point but rebooting then removes them from the mount point and does not attach them back.
>>
>> I will add this into the Extra HD bug#12863 report together with the screenshot of the page as it was with CU178 and now with CU179.
>>
>> Regards,
>>
>> Adolf.
>>
>>
>> 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 <adolf.belka(a)ipfire.org> 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 state 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 Testing.
>>>> 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*
>>>>>      Just after releasing Core Update 178 which was added into our release cycle to address Intel's and AMD's latest CPU vulnerabilities, we are back on track with our regular schedule. This release features Indirect 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 <https://blog.ipfire.org/post/ipfire-2-27-core-update-179-is-available-for-testing>
>>>>> The IPFire Project
>>>>> Don't like these emails? Unsubscribe <https://people.ipfire.org/unsubscribe>.

-- 
Sent from my laptop