On Wed, Feb 19, 2025 at 10:30:56AM -0800, Darrick J. Wong wrote: > If instead it turns out that 2037-era userspace (coughsystemdcough) > doesn't work on an old 2030 kernel, then they'll have to go install a > 2030-era userspace, boot the 2030 kernel, and migrate the data. Now > they have a V5 filesystem with 2030 era features. If they want 2037 era > features, they have to move the device to the new system and migrate a > second time. You probably wouldn't boot the old kernel on hardware but in a VM. Or have and old user mode Linux build around :)
