• 0 Posts
  • 22 Comments
Joined 2 years ago
cake
Cake day: August 2nd, 2023

help-circle



  • A decade and change ago, in a past life, I was tasked with switching SELinux to permissive mode on the majority of systems on our network (multiple hundreds, or we might have gotten above one thousand at that point, I don’t recall exactly). This was to be done using Puppet. A large number of the systems, including most of our servers, had already been manually switched to permissive but it wasn’t being enforced globally.

    Unfortunately, at that point I was pretty familiar with Puppet but had only worked with SELinux a very few times. I did not correctly understand the syntax of the config file or setenforce and set the mode to … Something incorrect. SELinux interpreted whatever that was as enforcing mode. I didn’t realize what I had done wrong until we started getting alerts from throughout the network. Then I just about had a panic attack when I couldn’t login to the systems and suddenly understood the problem.

    Fortunately, it’s necessary to reboot a system to switch SELinux from disabled to any other mode, so most customer facing systems were not impacted. Even more fortunately, this was done on a holiday, so very few customers were there to be inconvenienced by the servers becoming inaccessible. Even more fortunately, while I was unable to access the systems that were now in enforcing mode, the Puppet agent was apparently still running … So I reversed my change in the manifest and, within half an hour, things were back to normal (after some service restarts and such).

    When I finally did correctly make the change, I made sure to quintuple check the syntax and not rush through the testing process.

    edit: While I could have done without the assault on my blood pressure at the time, it was an effective demonstration of our lack of readiness for enforcing mode.



  • A while ago, I made a post saying things very similar to your first two sentences.

    I definitely am far more active here than I was on Reddit. It’s less intimidating here because of a smaller audience. Also, on Reddit, I’d often get negative responses if any at all. The crowd here is much friendlier; once or twice people have lashed out in response to something I said, but mostly people have been kind even if they apparently disagreed with my message.





  • I think I’m a cloud engineer, so I can’t use the same reasoning as you; but when I started at my company, I was given the option of either a Linux laptop with root or a Mac laptop. Obviously I selected Linux, but about a year later they started retiring all Linux laptops. The reason for this, I was told, is because the IT department didn’t know how to manage Linux laptops but they were familiar with Jamf. They did let us keep root on them, though.

    I still miss using that laptop for work. The good news is, since they never implemented mandatory RTO policies, the company moved to a much smaller office. In doing so, they needed to reduce inventory, so they gave away the old laptops (sans drives) to their employees. I now own the same laptop (or a very similar one)!








  • I bought one based on this thread, but only set it up a few days ago.

    Two days ago, my five-year-old requested that I print them a cat. I downloaded two cat models, one that was print-in-place bendy and one that was meant to test your calibration. I tried to print both, but both of them caused the printer to hang after displaying "stop processing, please wait … "

    I spent several hours testing and troubleshooting this, only to find an old thread saying that the printer firmware can’t handle filenames between 6-9 characters (not including the extension), meaning the filenames could be 5 characters or fewer; or 10 or more. I had named my files calicat.gcode and flexicat.gcode. After adjusting them to be longer filenames, everything started working beautifully.

    I’m very happy with the printer now that I know that, but it seems such a random error that it was very frustrating to try to fix. I thought my printer arrived broken. Hopefully if someone else encounters the same problem, they find this post and it fixes their problems!