This incident will be reported.
linuxmemes
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudo
in Windows. - No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
5. π¬π§ Language/ΡΠ·ΡΠΊ/Sprache
- This is primarily an English-speaking community. π¬π§π¦πΊπΊπΈ
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed. Β
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
You are not in the doers file
fsck
The job of a old style Linux admin has been superseded by infrastructure engineering and GitOps. You write automation to deploy and maintain thousands of VMs.
Some of us were doing infrastructure as code back when they still called us "Linux admins" and we were doing "gitops" with Subversion and Puppet. My title has changed a lot since the old days but some of the "new hotness" was around in the old days with different names. Fuck, look at LPARs.
You'll be lucky if there are actual VMs.
Is that... Fun?
actually, yes. you test solutions βmanuallyβ on servers and then roll them out with ansible across the whole infrastructure, neatly kept and carefully maintained in your local git instance. like raking a zen garden sometimes
in today's world I think you have to get in as a Windows System admin and then change your role by demonstrating how the Linux solution would be better for whatever the priority task at hand is
Not even sure of my chances at that these days. There are very few opportunities where I live too.
Got a few Linux VMs running on my work laptop for testing stuff though and literally no one else in the support team knows how to test what I use them for. It's a fairly rare task that no proper process exists for. My thinking is to see if I can either roll out VMs to people or better but less likely get my own virtual server.
document a basic set by set how to use it
make it look really good and find your coworker friends who will test it and give you feedback
documentation writing and scary shit like linux to normies goes a long way
Guess I was lucky. I got an apprenticeship as a Sysadmin and was told I'd mostly be in the in-house/client IT (Windows) but since I had a lot of Linux experience already, on my first day they put me into the server/hosting department (Linux) where I spent most of my apprenticeship.
But yeah looking for a job now, most companies seem to look for "good experience with windows/Windows server required" and "experience with Linux a bonus".
And then you get blamed when it breaks, so they switch back to what they know and use a ready-made solution from Microsoft with full 24/7 support package.
Because it is more important for it to work reliably and be fixed quickly, than for it to not be proprietary or not made by some evil corporation.
Downtime costs money.
I know Linux can be extremely reliable, but they rarely have all the bells and whistles that Microsoft offers and are rarely compatible with all the other software they are already using.
Having multiple different systems overlapping also adds overhead.
So I doubt you will be able to convince many like that. It is easy looking at it from a tech perspective, but they don't make those decisions.
You know what's funny about that? I can think of at 4 times in just the last year where a Microsoft outage caused significant downtime (at least 1 hour) for the company I work at.
- Twice, Outlook/Teams was having major regional issues for hours, people at my company couldn't log into Teams and weren't getting emails.
- Microsoft's Dynamics platform, (which my company's ERP software is built on) had some infrastructure issue that made it unusably slow for several hours.
- Who can forget the lovely Crowd Strike kiss of death fiasco a few months ago?
Meanwhile, the 12 year old janky Debian servers I had were running Ansible, Docker, OpenProject, and several other services without a hitch, same with all the Linux endpoints I had deployed.
Centralization causes many of these problems and makes them more severe than they otherwise would be. When you are locked into a single vendor for everything you do, you're completely at their mercy if anything breaks.
The problem is that nobody, at least in the US, markets open source solutions. The big players corner the market, and IT just learn those big players. You should see the looks I've been given when I present IT directors with a quote from ix Systems for a TrueNAS solution to their storage needs. They have no idea who they are, even though they provide enterprise grade storage solutions at a fraction of the price of Dell or HP.
The US tech environment is a cyber dystopia controlled by the Tech corpos of silicon valley. It's so frustrating.
I'm just here for the En Vogue.
Here's your typical day: Log into PC, immediately pinged by 3 people, 1 changed permissions into something they can't access for a business necessary file, the other deleted an entire directory and needs it restored, the third is concerned a file is giving a permission error and an entire directory is missing. You lock your desktop and go get coffee/tea before facing this.
More like 15 messages come to you, 7 of them are asking a question that is documented somewhere they have access to or you already answered for them, 4 of them use the word βurgentβ for help with a tool that isnβt in prod, yet theyβve decided to rely on for work, 3 of them want to schedule a meeting to have you babysit them following a set of instructions, and the last 1 is a group chat that you never pay attention to.
Good case (for the users), unless you are known as BOFH.