[exploderate]

The one line "article" on lwn.net has a link to this email:

  From: Kent Overstreet @ 2025-09-11 23:19 UTC
 
  As many of you are no doubt aware, bcachefs is switching to shipping as
  a DKMS module. Once the DKMS packages are in place very little should
  change for end users, but we've got some work to do on the distribution
  side of things to make sure things go smoothly.

  Good news: ...

https://lore.kernel.org/linux-bcachefs/yokpt2d2g2lluyomtqrdv...

[doublerabbit]

> Once the DKMS packages are in place very little should change for end users

Doesn't that mean I now have to enroll the MOK key on all my work workstations that use secure boot? If so that's a huge PITA on over 200 machines. As like with the NVIDIA driver you can't automate the facility.

[yomismoaqui]

Not to troll, I'm asking in good faith

Is this filesystem stable enough for deploying on 200 production machines?

From a cursory look I get things like this:

https://hackaday.com/2025/06/10/the-ongoing-bcachefs-filesys...

[jandrese]

Don't you only have to do that once per machine? After that the kernel should use the key you installed for every module that needs it. It is a pain in the ass for sure, but if you make it part of the deployment process it's manageable.

For sure it's a headache when you install some module on a whole bunch of headless boxes at once and then discover you need to roll a crash cart over to each and every one to get them booting again, but the secure boot guys would have it no other way.