Like seriously and I’m not even intending to be racist
(Though some smarmy asshole will for sure post this unironically thinking that they’re not being racist.)
Like seriously and I’m not even intending to be racist
(Though some smarmy asshole will for sure post this unironically thinking that they’re not being racist.)
Google the concept of an escrow service.
Your edit is a bad take. It doesn’t matter if he’s also selling shirts with MLK and Ghandi quotes. Nazi shit is Nazi shit. Doing Nazi shit, no matter what his own stupid rationalization, makes literally everything else he does irrelevant.
deleted by creator
deleted by creator
deleted by creator
Man, I use my switch all the time. But I love little metroidvania and smaller indie and single player games. Any time I see something interesting on steam, I’ll buy it on the switch if available.
I’ve also been using it to replay older stuff. The first red dead, the Arkham trilogy, currently going through Nier: Automata again.
deleted by creator
Or how about, rather than your narrow, specific 3 definitions, a fourth thing, such as how it’s phrased in the wiki:
Misogyny is hatred of, contempt for, or prejudice against women or girls. It is a form of sexism that can keep women at a lower social status than men.
The emphasis there is why you’re being called names on the internet. If you’re advocating systems or societal norms of gender oppression, you’re being misogynist. This remains true even if you’re not doing it intentionally.
The world we live in is deeply patriarchal, so it can be hard to see these problems, because the views and opinions you’ve got are just “normal”. Something being the norm doesn’t mean it isn’t oppressive, and having an opinion doesn’t mean you shouldn’t consider the impacts of that opinion.
Generally, if someone calls you a misogynist, and you go “bUt I rEsPeCt wOmEn”, you might want to take a little time to figure out where it’s coming from. It can certainly be real without fitting in your 3 tidy little self-serving definitions.
I’ll also point out that you can replace nearly every instance of misogyny in this thread with racism, and replace women with black, and it would be the same discussion. Or you could swap misogyny/women with misandry/men. Oppression is oppression, no matter who holds the power.
Yup. Treating VMs similar to containers. The alternative, older-school method is cold snapshots of the VM, apply patches/updates (after pre-prod testing & validation), usually in an A/B or red/green phased rollout, and roll back snaps when things go tits up.
deleted by creator
If you are in a position to ask this question, it means you have no actual uptime requirements, and the question is largely irrelevant. However, in the “real” world where seconds of downtime matter:
Things not changing means less maintenance, and nothing will break compatibility all of the sudden.
This is a bit of a misconception. You have just as many maintenance cycles (e.g. “Patch Tuesdays”) because packages constantly need security updates. What it actually means is fewer, better documented changes with maintenance cycles. This makes it easier and faster to determine what’s likely to break before you even enter your testing cycle.
Less chance to break.*
Sort of. Security changes frequently break running software, especially 3rd party software that just happened to need a certain security flaw or out-of-date library to function. The world has got much better about this, but it’s still a huge headache.
Services are up to date anyway, since they are usually containerized (e.g. Docker).
Assuming that the containerized software doesn’t need maintenance is a great way to run broken, insecure containers. Containerization helps to limit attack surfaces and outage impacts, but it isn’t inherently more secure. The biggest benefit of containerization is the abstraction of software maintenance from OS maintenance. It’s a lot of what makes Dev(Sec)Ops really valuable.
Edit since it’s on my mind: Containers are great, but amateurs always seem to forget they’re all sharing the host kernel. One container causing a kernel panic, or hosing misconfigured SHM settings can take down the entire host. Virtual machines are much, much safer in this regard, but have their own downsides.
And, for Debian especially, there’s one of the biggest availability of services and documentation, since it’s THE server OS.
No it isn’t. THE server OS is the one that fits your specific use-case best. For us self-hosted types, sure, we use Debian a lot. Maybe. For critical software applications, organizations want a vendor so support them, if for no other reason than to offload liability when something goes wrong.
It is running only rarely. Most of the time, the device is powered off. I only power it on a few times per month when I want to print something.
This isn’t a server. It’s a printing appliance. You’re going to have a similar experience of needing updates with every power-on, but with CoreOS, you’re going to have many more updates. When something breaks, you’re going to have a much longer list of things to track down as the culprit.
And, last but not least, I’ve lost my password.
JFC uptime and stability isn’t your problem. You also very probably don’t need to wipe the OS to recover a password.
My Raspberry Pi on the other hand is only used as print server, running Octoprint for my 3D-printer. I have installed Octoprint there in the form of Octopi, which is a Raspian fork distro where Octoprint is pre-installed, which is the recommended way.
That is the answer to your question. You’re running this RPi as a “server” for your 3d printing. If you want your printing to work reliably, then do what Octoprint recommends.
What it sounds like is you’re curious about CoreOS and how to run other distributions. Since breakage is basically a minor inconvenience for you, have at it. Unstable distros are great learning experiences and will keep you up to date on modern software better than “safer” things like Debian Stable. Once you get it doing what you want, it’ll usually keep doing that. Until it doesn’t, and then learning how to fix it is another great way to get smarter about running computers.
E: Reformatting
The actual answer to OP’s question is to look up cognitive biases, and to eventually realize that “black” isn’t the relevant descriptor here.