Upstream openafs has released 1.8.10 http://openafs.org/dl/openafs/1.8.10/RELNOTES-1.8.10 Most important change: > Support mainline kernels up to 6.4 and distribution kernels It would be nice if Gentoo could add this new version to the tree.
Ping, just checking if there's any chance of this happening soon - it's a bit annoying to have to stick with a pretty old kernel on systems that use AFS ;x
(In reply to Adrian from comment #1) > Ping, just checking if there's any chance of this happening soon - it's a > bit annoying to have to stick with a pretty old kernel on systems that use > AFS ;x I may have some slot in August to update this package, but I can't guarantee this since updates take considerable ammount of effort. However, you don't have to stick with old kernels: you can use fuse client (USE=fuse), though it will need some more love with init scripts, it is always possible to run it manually.
Hey, just wanting to check if you have any idea when you'll be able to update the module
Ping :)
FUSE works fine! Would be nice if the init scripts were automatically adapted in case of `USE=-modules fuse`. In any case, this drop-in worked for me: ``` $ cat /etc/systemd/system/openafs-client.service.d/override.conf [Service] ExecStart= ExecStart=/usr/sbin/afsd.fuse $AFSD_ARGS $AFSD_CACHE_ARGS ExecStartPre= ExecStartPre=/bin/sh -c "/bin/mkdir -p $(cut -d : -f 2 /etc/openafs/cacheinfo)" ExecStopPost= ExecStopPost=/usr/sbin/afsd.fuse -shutdown ```
FUSE doesn't seem to support aklog which makes it far inferior to the native in-kernel version :/
Anyway, before going off-topic here: Maybe this bug should be closed (or updated) in favor of bumping to 1.8.11 which is currently in beta: https://lists.openafs.org/pipermail/openafs-info/2024-February/043447.html After all, 1.8.10 is already outdated in terms of kernel support so spending time on that probably does not make much sense right now.
Created attachment 888866 [details] Patch file needed by openafs-1.8.11.ebuild
Created attachment 888867 [details] Ebuild file
Attachment 888866 [details] and 888867 contains ebuild what I have used. These are derived from some older openafs-1.8.8. Patch file is also derived from older patch file but all patched that didn't apply cleanly are dropped. Dropped patch: 0003-fbsd.patch 0007-afsauthent-symbols.patch 0014-kernel-cc-ld.patch Maybe this should be synced with latest openafs-1.8.8.1-r1.ebuild but at least I can compile this (only tested using x86_64 platform) and it seems to work.
Created attachment 888942 [details] openafs-1.8.11.ebuild
Created attachment 888943 [details] Manifest
Ebuild synced with openafs-1.8.8.1-r1.ebuild masu@z600 openafs % diff openafs-1.8.8.1-r1.ebuild openafs-1.8.11.ebuild 11,12c11,12 < PVER=20211212 < KERNEL_LIMIT=5.17 --- > PVER=20240424 > KERNEL_LIMIT=6.7 Also Manifest file updated to include openafs-1.8.11
Just a quick comment from upstream openafs... 1.8.12 is just around the corner (Linux kernel up to 6.9) -- a 1.8.12pre1 has been tagged. And the patches to support linux 6.10 have been merged into the openafs master branch. BTW -- I use gentoo as my primary system and I use a local "vanilla-openafs" ebuild (no gentoo patches and allows me to grab from a specified git repo/branch) for my local system.
Now that the 1.8.12 version is out, could you please share your "vanilla-openafs" ebuild. I think, ebuild that "(no gentoo patches and allows me to grab from a specified git repo/branch)" is very valuable for gentoo users.
Created attachment 904618 [details] vanilla-openafs ebuild This is an ebuild that I use for building/testing openafs on gentoo. It was derived from the net-fs/openafs ebuild package, but I stripped out all the gentoo related patches. It may not (probably doesn't) meet all of the "gentoo" ebuild standards. I am willing to assist on updating.
Created attachment 904619 [details] server init.d script
Created attachment 904620 [details] server config
Created attachment 904621 [details] client init.d
Created attachment 904622 [details] client config
I've attached the ebuild and the init.d related files that I use. They were originally based on the "official" gentoo ebuilds. They may not be up to full gentoo standards, but I will be willing to assist in getting them updated.
