The base system packages are exempt from the stipulation I posted above.
65 karma · joined May 11, 2023
The base system packages are exempt from the stipulation I posted above.
What the author wrote objectively demonstrates a lack of essential skills and also a lack of temperament for what could be called a sys-admin, and therefore they are ultimately disqualified.
Whether this is "harsh" or not doesn't change that it is true.
Being an amateur who landed a job and being someone who is qualified for the title are not the same.
>> No serious systems administrator is going full Gentoo on their entire setup. It's a waste of time and effort to do so.
This is a total strawman argument, but I'll knock it down anyway. There are professionals who actually do use Gentoo on their local machine. The local machine (a laptop) doesn't do any compiling, there is a server that builds the packages.
I was actually using Gentoo myself for a couple years and all my packages were automatically built by a cluster of servers using distcc, so any build job was done with something like "make -j128"
Because I knew how to use Unix-like systems properly and having a dedicated build server, Gentoo didn't cost me any time, quite the opposite actually, because Gentoo is flexible with package versions and everything tends to just werk.
>> That's not how sysadmins people get their software, though.
For those of us contending with PowerPC and ARM, it is half of how we get our software, the other half is we have already automated the process and a cicd pipeline has built the software often before we as humans notice a new version is out.
Mostly it deploys Podman configs to run proxies that do "nat traversal" and provide various things on our machine most using Git as a backend.
Our internal docs are mostly a variant of Markdown or Scientific Markdown.
We use a private Jitsi server for meetings and our company policy is to never impose influence (no matter how light) on any employee to inadvertantly leak their likeness/biometrics to a third party org.
Our CIO is pretty legit I must say.
Yeah the correct spelling of the word is good to have there ya go.
About to roll a J and kick back probably gonna browse the web and some of my favorite subreddits.
I have work on Monday.
Beyond seeing this post on HN, I'd have no idea this "protest" is happening, and to be fair I'll have forgotten about it by Sunday.
lol
The crowd in Washington DC isn't like it was in the 80s and 90s. The notion that they've actually got a grip on things and Ukraine is going to go the way they want.. yeah..
Yet it did exist on computers used by senators, lawyers, executives, everyone I mentioned. Consumers are not the high value targets.
>> This vulnerability was responsibly disclosed to Intel
The vulnerability was uncovered and well known of by very many private espionage teams for a very long time. If this wasn't already obvious to you then your view of the world is too sheepish and naive to meaningfully participate in discussion about this kind of topic.
>> I am not seeing all of these fatal 0 days that you are talking about.
Those of us in the offensive security space see vulnerabilities that could be exploited "locally", anywhere where bad code could get running on the ME as critical too. Getting SYSTEM or root (the former being easier because of that OS' particular culture) is generally easier than it should be. Intel ME makes it a much bigger problem than it otherwise would have to be.
While you most likely are not, you come across as a shill.
I have been responsible for keeping small fleets of laptops patched and I actually read the relevant CVEs Intel puts out, which if you bothered to do you would find that yes over the years there has been an endless stream of fatal 0days