The integration part is because we would like for anyone to fit in, and not be confined to your ‘hood’
We don’t mind you not speaking the language, but English is usually not a first language, sometimes not even a second, and sometimes omitted. Especially in rural areas.
So yeah, it’s nice if we can actually have a conversation about the local soccer team, or town buffoon who thinks the government is conspiring about pricing covid shots too high…
So… Europe? 160 ish?
The problem with SELinux/nftables/cgroups is that they don’t come with a centralised log aggregator, and they don’t do much blocking beyond the defaults for 99% of deployments.
You must not have heard of ®syslog.
Also, SELinux is a massive pain to set up (even compared to AppArmor), and setting it up correctly is even worse.
I beg to differ, I find SELinux easy to setup. But your mileage may vary, depending on one’s experience.
CrowdStrike does a lot of what SELinux does but it’s easier to configure, works on every operating system, and comes with tools to roll out configuration across an organisation. There’s nothing close to that in the open source world. Even if you set up something yourself, you’ll need to continuously tweak your setup not to get in the way of employees and to prevent alert fatigue from all of the false positives. Apparently, recent events show it doesn’t work on every OS… 😜
When talking about ease of use… Configuration is configuration. If you do not take the time to learn how to use your product, the product you know will always be better than the one you don’t. I’ve used Crowdstrike. I’ve battled them to get their kernel modules signing certificate to be signed by RedHat. I’ve battled them to have the possibility to have the auto update disabled. So no, I am not impressed by the quality of their product. I’ll bet any day a vanilla RHEL with the correct security related software and the latest updates outperforms and outclasses Crowdstrike.
I think a preconfigured solution like Security Onion combined with tons of group policy and Ansible can form an open source alternative, but that only monitors, whereas CrowdStrike also blocks. To block behaviour, you’ll need to write code for most platforms, and that’s just as likely to take down your org as an auto update from CrowdStrike. I can’t speak of MS products, as I have not managed them for 20 years, but all of this is not needed on a decent Linux distro.
What CrowdStrike is actually selling, is someone who actually looks at the system logs and who pushes a button when something pops up. Roughly.
There are better solutions on the market. Unfortunately CrowdStrike has the more aggressive sales team.
For those wondering, I’m referring to *nix based solutions like SElinux, appArmor, iptables, nftables, cgroups, … But you need to monitor your logs if you want to take appropriate action.
Illy
I was kind of getting really desperate, as I usually, IMO, take good care of the machine. And usually I know hoe to solve issues. But in hindsight, and after checking timestamps, I do believe it is the slicer. When I updated it earlier this year I printed some figs, but couldn’t troubleshoot during to time constraints, and I parked it. So recently I picked up printing some more, but it didn’t connect immediately.
So yeah, I blame the slicer, and my lack of time.
Thanks for taking the time to reply.
I eventually ended up removing my slicer (Chitubox basic) and install the latest and greatest after cleaning up my profile. So literally starting anew.
Aside from changing te resin, I didn’t modify any other settings to begin with, so my config was rather vanilla.
After taking these steps (and cleaning the z-axis and replacing the nofep again) everything seems to be working fine now.
Cleaning the axis and a new nofep didn’t seem to do anything, so I think it was just a crappy version of the slicer.
Thanks for taking the time to reply.
I eventually ended up removing my slicer (Chitubox basic) and install the latest and greatest after cleaning up my profile. So literally starting anew.
Aside from changing te resin, I didn’t modify any other settings to begin with, so my config was rather vanilla.
After taking these steps (and cleaning the z-axis and replacing the nofep again) everything seems to be working fine now.
Cleaning the axis and a new nofep didn’t seem to do anything, so I think it was just a crappy version of the slicer.
Hey, I cleaned the z-axis: no change I replaced the nofep (again): no change I removed my old slicer (Chitubox Basic 1.9.5) and installed the latest (2.1). I cleaned up my profile, so it was vanilla config: what do you know: it seems to work now!
Still running some prints to monitor any changes, but it’s looking good!
Thank you for your time!
Thanks for taking the time to reply.
I eventually ended up removing my slicer (Chitubox basic) and install the latest and greatest after cleaning up my profile. So literally starting anew.
Aside from changing te resin, I didn’t modify any other settings to begin with, so my config was rather vanilla.
After taking these steps (and cleaning the z-axis and replacing the nofep again) everything seems to be working fine now.
Cleaning the axis and a new nofep didn’t seem to do anything, so I think it was just a crappy version of the slicer.
Thanks for taking the time to reply.
I eventually ended up removing my slicer (Chitubox basic) and install the latest and greatest after cleaning up my profile. So literally starting anew.
Aside from changing te resin, I didn’t modify any other settings to begin with, so my config was rather vanilla.
After taking these steps (and cleaning the z-axis and replacing the nofep again) everything seems to be working fine now.
Cleaning the axis and a new nofep didn’t seem to do anything, so I think it was just a crappy version of the slicer.
Thanks for taking the time to reply.
I eventually ended up removing my slicer (Chitubox basic) and install the latest and greatest after cleaning up my profile. So literally starting anew.
Aside from changing te resin, I didn’t modify any other settings to begin with, so my config was rather vanilla.
After taking these steps (and cleaning the z-axis and replacing the nofep again) everything seems to be working fine now.
Cleaning the axis and a new nofep didn’t seem to do anything, so I think it was just a crappy version of the slicer.
Well, it seems you might be right.
I installed the latest version of Chitubox Basic (2.1) and now it works just great.
Thank you very much, kind internet stranger!
The glass is half full, yeah? 😉
So you think is is maybe a software issue?
I’ll check if there are any known issues and possibly update my chitubox
I did select different settings for the other resin. I checked both in the app and on Epax’s website, and my settings are aligned
Thank you for your reply! I hadn’t thought of the mechanics!
I’ll check the screw and clean it.
As long as the OS was supported, updates were available.
But yes, I loaded a nice Fedora on it… 😉
Doesn’t “digital” imply “electricity”?