0x4E4F

Ah, a man of culture I see 😌.

Actually, I kinda am. Can't really afford to spend a month or two without pay, so if I do find anything better (which I seriously doubt, every company here is more or less the same regarding IT practices), it would have to be a drop in replacement, which is also hard to do here (they're gonna try and squeeze as much free labour as possible from you, so you'll probably be stuck with a 200, 250 euro freelance salary for the next month or two, and as I said, I just can't afford to do that right now, money is tight, got a family now).

It's basically like a tool for controlling what X does or doesn't... at least that's how I see it (have never read a manual of what ot actually is).

BSD users are even worse than Linux users if you ask me... back in the day I mean, have no idea if things have changed the past 10 years or so.

They have far less failure points. Also, the AUR. None of them have anything remotely like that, which is also a big stability issue, but hey, it's bleeding edge, so you should be prepared for that.

Debian is more or less like RHEL/Rocky... with RHEL being even more stable and taking even less risks. They update only if they have to and only security related issues. Otherwise, RHEL is feature fixed. You have to upgrade to a new version to get a new set of libraries and applications. Debian... yeah, they're also feature fixed, but they sometimes update certain things that are required by most users, since Debian is also considered a desktop distro, not just a server distro.

If you actually measure voltages (I have), you'll find out that that is not always true... in some cases, yes, in most cases, no. Depends from MB manufacturer and model. AMD chipsets usually allow this and the declared settings are what you can actually measure on the board. Intel though... nah, way too many failsafes in place to let you do whatever you want, even though the firmware will report that you've set it a certain way (Vcore = 2V, as in your case).

7. Compile shit yourslef with custom made templates while crying and praying this n-th time make will NOT throw a dependency error.

Patching servers and fixing infrastructure issues gets rewarded with getting blamed for any server or app issue going forward and then fixing said issues on top of your current workload.

Exactly! Couldn't have said it better myself.

Unfortunately, every IT job where I live is more or less like this. Sure, there are some that are not, but are not a whole lot better paid than what I currently make... and because of certain life decusions I've made, I currently can't move or work abroad. In 10+ years from now... maybe... we'll see... I hope so. So, basically, I'm more or less stuck here with this job. I could quit and find something else, but my current budget doesn't allow to go even for a month with no pay... so if I do, it'll have to be a quit today - hire tomorrow kind of a thing, which most companies around here don't do (they wanna squeeze as much free labour out of you as possible, so even if they don't go full pay for a month or two, that's a win in their book), so... again, not really an option currently.

Told ya 🤷... you and others just have no idea how desparate things are around here, that's why most people blame me for not updating... I believe 90% of people around here that said that, if they were in my shoes, they'd do the same 🤷.

The important part that @ramble81@lemm.ee is focusing on is that your mindset on how you approach these challenges is incredibly unprofessional.

I know it is.

Now, ask me why that is.

The professional thing to do is to decouple your feelings of how you're being paid from individual tasks or duties that are expected of you. "I'm not paid enough to deal with this" should be limited to tasks outside of your scope of work.

Lol 😂, no one has actually told me to keep the servers up to date, the only thing I was ever told was "keep shit running". I've done updates on my own incentive, since I'm the senior IT engineer in the company. When things turn to shit after an update, hey, I'm rolling back a snapshot, I did not sign up for this 🙌.

And that is basically it 🤷... I get the same salary regardless if I do them or not. After a few failed ones, I just gave up. F it, not worth the time or the effort.

If you're ultimately not paid enough to do your job, complaining about individual tasks that are part of your job being bnove your paygrade is just saying you aren't willing to do your job.

Nope, I'm saying "Fuck you, pay me!".

You think they care about updates and security? I've mentioned it a few times at meetings... "yeah, we'll talk about that later". OK 🤷. They obviously have no idea how fucked up things can get if you're not up to date regarding security... but hey, they have been warned more than a few times 🤷.

What you need to do regarding your workload is have a conversation with your manager/superior about prioritization. You say "hey, I have this this this and this that need to get done right now and I can't realistically do them all, what do you want me to prioritize and deprioritize" and if something important hasn't been given priority in a long time (such as patches) you need to then push back and say "we haven't been able to apply security patches in quite a while, I think we should reprioritize this so we can put some time into patching this week" this is how you manage a gigantic workload is by shifting priorities. The longer important maintenance tasks are ignored, the larger the impact and the harder it will be to complete the tasks

🤦... dude, you really have no idea where I live 😂🤣😂... otherwise you wouldn't be saying this.

Things have been said more than once... I have asked, have pleeded for more personel... deaf ears. I have put it in writing, no use. Fine, then I just keep things running and that's basically it 🤷.

Oh, and regarding workload, I already prioritize. The priority is to keep shit running, not to be up to date (obviously)... so, I just keep things running.

They have and that is why I don't do them any more. Happened a few months ago in fact. Updated one of the Debian servers for one of webapps we have running (a black box piece of shit VM that's stuck in 2010 I think)... suddenly, the app in the VM doesn't work. The VM does start, but the app doesn't work, just throws a 404. Why? Beats me, don't have time to troubleshoot. Roll back a snapshot, everything works again. Conclusion, don't update that.

See, around here, you don't keep your job by messing around with things that already work. They work, period, why did even feel the need to mess with that 🤨. If that's management's view on security, fine, so be it 🤷.

I still file reports on things not being up to date, just so that if shit hits the fan, I'm not the one taking the fall for it.