On Wed, Sep 10, 2025 at 11:59:18PM +0200, Mark Wielaard wrote: > Christopher, > > On Mon, Sep 08, 2025 at 06:11:51PM +0000, Christopher Klooz wrote: > > The below change proposal was accidentally sent to the mailing list under a wrong name. > > And the new name is so long I originally missed this. Sorry. > > The long name also suggests (at least to me) that this is really > multiple proposals. It seems to suggest three different policy > changes. One for logging and processing kernel addresses, impacting > programs needing to inspect e.g. /proc/kallsyms. One for BPF using > packages, impacting performance and power consumption. And one for > tracing/profiling/debugging user space programs, impacting whether > installing such a package works out of the box or not. > > It would be good to turn this into three separate proposals with input > from some of the affected package maintainers to come up with a good > way to set these values to make sure when you install a package it > works out of the box. I don't think just asking FESCO to pick a > default value, force the systemd package maintainers to set that > and then hope users will read some documentation to enable their > installed packages to work again is a great policy. It is really hard to tell from the proposal name, and the huge wall of text in the proposal, exactly what it is doing at a conceptual level. I wouldn't have realized it was proposing to break use of gdb & strace out of the box if someone had not mentioned in here. I agree it would be preferrable to split this into three proposals that can be evaluated & approved/denied independantly, and while doing this, make the proposal text more concise in describing their impact/goals. With regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :| -- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx 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/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue