Comment by Muromec

2 days ago

The hard part is finding enough people working for the public sector salary who know those two extra lines and where to put them, and then making sure they are not getting bored or disillusioned enough.

7 comments

Muromec

Reply
ndriscoll  2 days ago

You don't need someone who knows those two lines anymore. You can just ask codex to make it so that users can't do whatever. It's highly competent at just reading the nixpkgs source, or it knows how Linux works and can write its own modules.

Nix happens to also set you up with a working build environment so if a program doesn't expose the necessary options to manage it the way you want, I bet Codex would have no trouble patching it as part of your nix config.

  • Muromec  2 days ago

    You still need to have somebody half competent to ask the electric shaitan to the thing and validate the result and also demonstrate this ability during the hiring process. I'm not sure it's easier than actually finding a person who can do those two lines.

    • ndriscoll  2 days ago

      If you trust someone to manage IT policy in the first place I'd think they'd be smart enough to be able to learn the basics of Nix? Like 95%+ of it is just declaring obvious settings that are already in nixpkgs. In practice it's mostly an ini file, but with the power to do more if you need it.