Monday, March 18, 2024

[fedora-arm] [Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting

Dear all,

You are kindly invited to the meeting:
Fedora ARM & AArch64 status meeting on 2024-03-19 from 16:00:00 to 17:00:00 UTC

The meeting will be about:
Fedora ARM & AArch64 weekly status meeting.

Join us on Matrix at [https://matrix.to/#/#meeting-2:fedoraproject.org](https://matrix.to/#/#meeting-2:fedoraproject.org) through [chat.fedoraproject.org](through chat.fedoraproject.org).

More information available at:
[https://fedoraproject.org/wiki/Architectures/ARM](https://fedoraproject.org/wiki/Architectures/ARM)


Source: https://calendar.fedoraproject.org//meeting/10455/

--
_______________________________________________
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[389-users] Re: Directory Administrators vs. Password Administrators

Hi,

I assume your question is about privileges 'Directory manager' vs
'Password Administrators'.

They are both allowed to bypass the password policy (global or local)
and set any value they want. While 'Directory manager' does not need
specific ACI, Administrators belonging to 'passwordAdminDN' group do
need ACIs granting read/write on password attributes [1]

[1] https://www.port389.org/docs/389ds/design/password-administrator.html

best regards
thierry

On 3/16/24 00:04, tdarby@arizona.edu wrote:
> I see tn the docs that you can make a Password Administrators group, like so:
>
> dn: cn=config
> changetype: modify
> replace: passwordAdminDN
> passwordAdminDN: cn=Passwd Admins,ou=groups,dc=example,dc=com
>
> I'm curious though, what privileges does a Directory Administrator have over and above one of these Password Administrators.
> --
> _______________________________________________
> 389-users mailing list -- 389-users@lists.fedoraproject.org
> To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
--
_______________________________________________
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[fedora-arm] Re: Details on Raspberry Pi 5 support timelines



On 17 Mar 2024, at 18:23, Peter Robinson <pbrobinson@gmail.com> wrote:

The TL;DR is that there won't be any way of even basic support
officially for F-40 GA.

There are people asking for status on https://discuss.python.org/ and I have replied pointing to this thread. I will continue to help with the conversation on discuss.

Barry


Sunday, March 17, 2024

[fedora-arm] Re: Details on Raspberry Pi 5 support timelines

If your local to Northern Virginia
I'd love to see a kernel presentation
at NoVALUG
I'm not a kernel hacker
But would like seeing some issues involved
as a long time Linux LUG guy


On Sun, Mar 17, 2024, 17:51 Peter Robinson <pbrobinson@gmail.com> wrote:
On Sun, 17 Mar 2024 at 21:38, Sally A.haj <sallyahaj@yahoo.com> wrote:
>
> Hi Peter,
> Thank you for all your efforts.
>
> I just thought about rpmfusion's images for RPix, while they are using
> the downstream kernel, they might consider adding the support for RPi5,
> this one instead of make a new remix, if that make sense.

I have no idea what RPix is. My intention is to ultimately get
everything into Fedora, the remix is intended to be short lived and
assist in moving forward the upstreaming.

> Sally
>
> On Sun, 2024-03-17 at 18:21 +0000, Peter Robinson wrote:
> > Hi Folks,
> >
> > I finally got some time over the weekend to dig into Fedora on the
> > RPi5.
> >
> > The TL;DR is that there won't be any way of even basic support
> > officially for F-40 GA.
> >
> > For those interested in more details.....
> >
> > The main pieces missing from the upstream kernel to boot to a login
> > prompt over serial is appear to be the following:
> > * The SoC pinctrl driver
> > * Support in the mmc storage driver for the SoC variant
> > * Minor bits for the gpio driver
> >
> > I'm not aware of any efforts to get anything upstream, I've not seen
> > patches on lists etc.
> >
> > We have the firmware (bcm/u-boot) pieces in place in Fedora 40 and
> > the
> > kernel will start to boot and you get serial console output except
> > you
> > end up at a dracut prompt due to lack of storage.
> >
> > I am considering doing a Fedora kernel with patches in copr, and
> > probably a F-40 remix minimal image, to enable minimal boot so other
> > low level developers can use it as a basis for further investigation
> > for things like upstream development. I don't have a timeline for
> > this
> > yet but I suspect late April. At the moment this looks like it'll be
> > mSD, WiFi, serial console support and not much else. I've not looked
> > at PCIe, the RP1 chip, or any other peripherals at all.
> >
> > I'll reply to this thread if/when I have any further updates, feel
> > free to reference it elsewhere.
> >
> > Until there's either a kernel or kernel+image unless you can
> > contribute to upstream kernel pieces there's probably nothing that
> > can
> > be done like "testing". If you can do kernel and would like to assist
> > me feel free to reachout outside of this thread.
> >
> > Peter
> > --
> > _______________________________________________
> > arm mailing list -- arm@lists.fedoraproject.org
> > To unsubscribe send an email to arm-leave@lists.fedoraproject.org
> > Fedora Code of Conduct:
> > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > List Guidelines:
> > https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives:
> > https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org
> > Do not reply to spam, report it:
> > https://pagure.io/fedora-infrastructure/new_issue
>
--
_______________________________________________
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[fedora-arm] Re: Details on Raspberry Pi 5 support timelines

On Sun, 2024-03-17 at 21:51 +0000, Peter Robinson wrote:
> On Sun, 17 Mar 2024 at 21:38, Sally A.haj <sallyahaj@yahoo.com>
> wrote:
> >
> > Hi Peter,
> > Thank you for all your efforts.
> >
> > I just thought about rpmfusion's images for RPix, while they are
> > using
> > the downstream kernel, they might consider adding the support for
> > RPi5,
> > this one instead of make a new remix, if that make sense.
>
> I have no idea what RPix is. My intention is to ultimately get
> everything into Fedora, the remix is intended to be short lived and
> assist in moving forward the upstreaming.
I got your point.
The project of rpmfusion seems in a different direction:
https://rpmfusion.org/Howto/RaspberryPi
Their images are for RPi 3 B/B+ & 4 B/400

>
> > Sally
> >
> > On Sun, 2024-03-17 at 18:21 +0000, Peter Robinson wrote:
> > > Hi Folks,
> > >
> > > I finally got some time over the weekend to dig into Fedora on
> > > the
> > > RPi5.
> > >
> > > The TL;DR is that there won't be any way of even basic support
> > > officially for F-40 GA.
> > >
> > > For those interested in more details.....
> > >
> > > The main pieces missing from the upstream kernel to boot to a
> > > login
> > > prompt over serial is appear to be the following:
> > > * The SoC pinctrl driver
> > > * Support in the mmc storage driver for the SoC variant
> > > * Minor bits for the gpio driver
> > >
> > > I'm not aware of any efforts to get anything upstream, I've not
> > > seen
> > > patches on lists etc.
> > >
> > > We have the firmware (bcm/u-boot) pieces in place in Fedora 40
> > > and
> > > the
> > > kernel will start to boot and you get serial console output
> > > except
> > > you
> > > end up at a dracut prompt due to lack of storage.
> > >
> > > I am considering doing a Fedora kernel with patches in copr, and
> > > probably a F-40 remix minimal image, to enable minimal boot so
> > > other
> > > low level developers can use it as a basis for further
> > > investigation
> > > for things like upstream development. I don't have a timeline for
> > > this
> > > yet but I suspect late April. At the moment this looks like it'll
> > > be
> > > mSD, WiFi, serial console support and not much else. I've not
> > > looked
> > > at PCIe, the RP1 chip, or any other peripherals at all.
> > >
> > > I'll reply to this thread if/when I have any further updates,
> > > feel
> > > free to reference it elsewhere.
> > >
> > > Until there's either a kernel or kernel+image unless you can
> > > contribute to upstream kernel pieces there's probably nothing
> > > that
> > > can
> > > be done like "testing". If you can do kernel and would like to
> > > assist
> > > me feel free to reachout outside of this thread.
> > >
> > > Peter
> > > --
> > > _______________________________________________
> > > arm mailing list -- arm@lists.fedoraproject.org
> > > To unsubscribe send an email to arm-leave@lists.fedoraproject.org
> > > Fedora Code of Conduct:
> > > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > > List Guidelines:
> > > https://fedoraproject.org/wiki/Mailing_list_guidelines
> > > List Archives:
> > > https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org
> > > Do not reply to spam, report it:
> > > https://pagure.io/fedora-infrastructure/new_issue
> >
> --
> _______________________________________________
> arm mailing list -- arm@lists.fedoraproject.org
> To unsubscribe send an email to arm-leave@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines:
> https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
--
_______________________________________________
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Test-Announce] [Test Week] Help Test Fedora 40 IoT!

Calling all testers!

This week (2024-03-18 to 2024-03-22) is the Fedora 40 IoT test week! Help us by testing Fedora 40 IoT version on x86_64 or aarch64 hardware. You can find more information as well as links to the F40 IoT images here[0]. The wiki page will have instructions for downloading and installing Fedora IoT, as well as a link to the results page[1] where you can store your results after testing.

If you have any questions, please reach out on the Fedora IoT Matrix room[3].

Thank you for your help and happy testing!

[fedora-arm] Re: Details on Raspberry Pi 5 support timelines

On Sun, 17 Mar 2024 at 21:38, Sally A.haj <sallyahaj@yahoo.com> wrote:
>
> Hi Peter,
> Thank you for all your efforts.
>
> I just thought about rpmfusion's images for RPix, while they are using
> the downstream kernel, they might consider adding the support for RPi5,
> this one instead of make a new remix, if that make sense.

I have no idea what RPix is. My intention is to ultimately get
everything into Fedora, the remix is intended to be short lived and
assist in moving forward the upstreaming.

> Sally
>
> On Sun, 2024-03-17 at 18:21 +0000, Peter Robinson wrote:
> > Hi Folks,
> >
> > I finally got some time over the weekend to dig into Fedora on the
> > RPi5.
> >
> > The TL;DR is that there won't be any way of even basic support
> > officially for F-40 GA.
> >
> > For those interested in more details.....
> >
> > The main pieces missing from the upstream kernel to boot to a login
> > prompt over serial is appear to be the following:
> > * The SoC pinctrl driver
> > * Support in the mmc storage driver for the SoC variant
> > * Minor bits for the gpio driver
> >
> > I'm not aware of any efforts to get anything upstream, I've not seen
> > patches on lists etc.
> >
> > We have the firmware (bcm/u-boot) pieces in place in Fedora 40 and
> > the
> > kernel will start to boot and you get serial console output except
> > you
> > end up at a dracut prompt due to lack of storage.
> >
> > I am considering doing a Fedora kernel with patches in copr, and
> > probably a F-40 remix minimal image, to enable minimal boot so other
> > low level developers can use it as a basis for further investigation
> > for things like upstream development. I don't have a timeline for
> > this
> > yet but I suspect late April. At the moment this looks like it'll be
> > mSD, WiFi, serial console support and not much else. I've not looked
> > at PCIe, the RP1 chip, or any other peripherals at all.
> >
> > I'll reply to this thread if/when I have any further updates, feel
> > free to reference it elsewhere.
> >
> > Until there's either a kernel or kernel+image unless you can
> > contribute to upstream kernel pieces there's probably nothing that
> > can
> > be done like "testing". If you can do kernel and would like to assist
> > me feel free to reachout outside of this thread.
> >
> > Peter
> > --
> > _______________________________________________
> > arm mailing list -- arm@lists.fedoraproject.org
> > To unsubscribe send an email to arm-leave@lists.fedoraproject.org
> > Fedora Code of Conduct:
> > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > List Guidelines:
> > https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives:
> > https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org
> > Do not reply to spam, report it:
> > https://pagure.io/fedora-infrastructure/new_issue
>
--
_______________________________________________
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue