Package Details: linux-pf 6.8.6-1

Git Clone URL: https://aur.archlinux.org/linux-pf.git (read-only, click to copy)
Package Base: linux-pf
Description: The pf-kernel and modules
Upstream URL: https://pfkernel.natalenko.name
Keywords: bbr bbr3 kernel ksm linux linux-pf pf-kernel uksm uksmd v4l2loopback zstd
Licenses: GPL-2.0-only
Provides: KSMBD-MODULE, linux-pf, NTFS3-MODULE, UKSMD-BUILTIN, V4L2LOOPBACK-MODULE, VIRTUALBOX-GUEST-MODULES, WIREGUARD-MODULE
Replaces: virtualbox-guest-modules-arch, wireguard-arch
Submitter: nous
Maintainer: post-factum
Last Packager: post-factum
Votes: 210
Popularity: 0.41
First Submitted: 2011-07-24 12:01 (UTC)
Last Updated: 2024-04-20 09:52 (UTC)

Dependencies (17)

Required by (13)

Sources (2)

Pinned Comments

post-factum commented on 2023-09-25 20:30 (UTC)

Official binary builds for various x86_64 μ-arches are available here.

post-factum commented on 2023-09-25 20:20 (UTC)

pf-kernel follows its own versioning scheme that doesn't depend on stable kernel releases versioning. X.Y.Z package version here corresponds to vX.Y-pfZ release in the source code repo.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 .. 106 Next › Last »

post-factum commented on 2023-09-27 11:23 (UTC)

Yes, that sounds like a good idea. Thanks, I'll consider that for the next update.

ZhangHua commented on 2023-09-27 10:22 (UTC)

@post-factum Following linux package should be a good idea. However, setting -dkms packages to conflicts is not good as we may install other kernels that need those -dkms packages to work. I think we may simply remove them from replaces? If you installed a -dkms package which has kernel module that is provided by linux-pf kernel, the kernel module shipped by kernel will be disabled by dkms, so I think we can simply remove this limit, people who want to use those -dkms modules can also install related packages directly.

post-factum commented on 2023-09-27 08:35 (UTC)

I think I should keep replaces for at least virtualbox-guest-modules-arch wireguard-arch as the linux package do, right? Should I move -dkms packages only to conflicts then?

ZhangHua commented on 2023-09-27 08:22 (UTC)

@post-factum OK, I know that, thanks for your explanation. I know that you want to keep the build script simple. However, I think you may also need to adjust your replaces in PKGBUILD. According to ArchWiki, I think you may use replace with wrong. You may need to move them to conflicts and provides to let pacman do not replace those packages with linux-pf automatically.

post-factum commented on 2023-09-27 07:41 (UTC)

Hello. Regarding linux-pf-docs package, I do not provide it intentionally as I think that should the need to read such a documentation arise, the user of a custom kernel is perfectly able to open the Documentation/ folder within the source code tree.

As for customisation for μ-arches, a config file can be edited before building the package, and any decent AUR helper should allow that. I'm not going to bake this into PKGBUILD to not overcomplicate it.

ZhangHua commented on 2023-09-27 06:33 (UTC)

Hello, is there any linux-pf-docs package just like those official kernels? What's more, I think we may need to add some environment variables to let user do more customization like using x86_64-v3 micro architecture?

post-factum commented on 2023-09-25 20:30 (UTC)

Official binary builds for various x86_64 μ-arches are available here.

post-factum commented on 2023-09-25 20:20 (UTC)

pf-kernel follows its own versioning scheme that doesn't depend on stable kernel releases versioning. X.Y.Z package version here corresponds to vX.Y-pfZ release in the source code repo.

post-factum commented on 2023-09-25 18:29 (UTC)

Pushed an update. Further suggestions are welcome.

post-factum commented on 2023-09-25 15:05 (UTC)

I've adopted the package. Please expect some churn with it in upcoming days and please allow me some time to work things out. Thanks.