Using kAFS on Linux for Network Home Directories
summary
Mainline Linux now includes an in-kernel kAFS client that uses the kernel crypto API, FS-cache, keyrings, request_key and dynamic automounts; each AFS volume appears as its own mount with visible quotas. Kerberos tickets + aklog store AFS tokens in the session keyring, and systemd --user token isolation prevents services from seeing those tokens (workarounds: a system /etc systemd-user service to import creds, or disable systemd‑user). Early testing shows 80% latency vs OpenAFS; missing pieces include inotify, xattrs, user-keyring option and admin tools.
AI-written summary · about
chapters (31)
- 0:00Introduction
- 0:25Agenda
- 1:58AFS
- 3:17AFS File System
- 4:41Local File Systems
- 5:50Host Name
- 6:23Why Use kAFS
- 7:34Limitations of kAFS
- 8:40Linux Client
- 9:49Kernel Features
- 10:41System D Unit
- 12:12User Volumes
- 13:17User ReadWrite
- 13:28User ReadOnly
- 13:57Kerberos Tickets
- 14:18kFS Cache
- 15:23SystemD User
- 16:18SMB
- 16:53Kerberos Cache
- 17:15Run
- 17:50X crashes
- 19:15Gnome Terminal
- 19:37Credential Crash
- 20:19Multiple Logins
- 22:03Session Keyring
- 23:40Kerberos keyring
- 24:13gnome tracker
- 26:26more tools
- 26:59more distros
- 27:10thank you
- 27:24kAFS on a home network
related talks
56mReinventing Home Directories
11mImmutable Linux systems and how they work
29mFilesystem mounts in user namespaces
30mTo the Cloud and Beyond, Accessing Files Remotely from Linux via SMB3.1.1
17mCoFS: A Filesystem for Fast Container Startup
33mEncryption for filesystems with advanced features new fscrypt functionality
41mWhat Is Linux Kernel Keystore and Why You Should Use It in Your Next...
30mOpenZFS and Linux