You can still create kernel extensions, there's just a process to get them approved. The requirements are a little more stringent than getting a signed driver, which makes sense as the permissions are higher.
And it's not as if older versions of the kernel cease to exist when a new one lands, too. Worst case, it'll always be there in source control, just a checkout and a build away.
Old kernel perhaps, but that's still what's being shipped with the latest CentOS6 (and by extension, RHEL 6 as well). Old as it might be, it's in very wide use.
This would be a tremendous boon for those environments!
Their kernel at least is and it’s Unix. From a user standpoint I don’t have any issues with it, it’s like if Linux could run photoshop natively and had good paid software and you can’t change the UI. It’s not ideal but it works for me.
I'm just surprised they would impose that restriction in the kernel considering they have very little problem with closed-source binary blobs for drivers and whatnot.
reply