Read the Jesus parts again. Would Jesus like that?

  • 16 Posts
  • 855 Comments
Joined 3 years ago
cake
Cake day: August 12th, 2023

help-circle

  • Clearly you know of lot about this. Here are some comments for the next human.

    Deny all modules seems more possible than a whitelist approach. To deny all, the command is likely “sysctl kernel.modules_disabled=1”.

    Whitelisting is harder. One could store a list of all loaded modules on a working system. Store a list of all kernel modules currently installed on the system. Compare the lists and remove from the “all” list the “running” list (grep will do this) and write it to the blacklist file.

    The problem with the Whitelisting approach is that it needs to run after every kernel module install (which is doable).

    If the above is the case, then someone must have automated this already, but I cannot find it quickly. (I checked Debian’s package repository.)








  • exact same thing every time

    I imaging it is this, combined with memory saving. So each scoop of ice cream is the same scoop (3 scoops in that bowl are the same three scoops.) Maybe even more extreme with the “scoop” being a “replicate this 1 mL of ice cream and apply a scoop shape, where that shape is ‘round’”.

    My evidence is that some recipes are simply not in the replicators storage of galaxy class ships. This indicates that it takes both storage and effort to get a recipe into the machine.






  • There are more options than the two you mentioned. Listing a few as more people should remember them. I did get a bit off topic…

    1. Use huge company to provide service.
    2. Provide service oneself (, likely with Open Source. )
    3. Use small or medium company to provide service (, likely with Open Source. )
    4. Use huge company for things huge company is great with, but keep “crown jewels” of company on internal self provided systems.
    5. Use a small or medium company to provide a service, and another series of small or medium companies to check on the first company.
    6. Use a huge company based in a country that is very serious about laws and putting CEOs in prison for wrongful acts.
    7. Do not do the thing. (Included for completeness.)
    8. Do the thing not on a computer. (Violation of privacy could result in violation of more serious laws.)
    9. Use an older technology on a computer.
    10. Use the huge company to provide service, but ensure the data includes insane things.

  • business with a contract

    I always wonder at this and have cautioned my managers repeatedly. Yes, we have a contract, but they have a literal army of lawyers and we have less (one lawyer one retainer for hourly work or a small grouping focused on taxes and employment law). As if our ownership won’t bend over backwards to avoid suing a large company like Google, AWS, Microsoft, or Oracle. (Maybe OpenAI and Anthropic are sue-able by a $100 million corp?)

    As proof I offer the lawsuits between businesses that have proceeded far enough the general public has heard about them. Not a specific one, just all of them.






  • Edit: I should explain first that I do not think you can change your employees or manager. A technical solution will never fix a management problem. Perhaps your manager is getting enough heat to be open to better management controls. You should be in “sanity protecting” mode.

    Original: While the posts include a lot of fiction, but “overemployed” crowd have some good advice. Start applying elsewhere, downshift your effort at $job_one, and move to collecting a check.

    Or ramp up and take your manager’s job or get fired trying. Gather data and allies in the C-suit, and stage a coup. Or unionize (or post pro-union flies in the bathroom).