Who says NAS to mean anything other than Network-Attached Storage?!?
“When I say left, I kinda mean right half the time almost.”
Who says NAS to mean anything other than Network-Attached Storage?!?
“When I say left, I kinda mean right half the time almost.”
The wd60efrx is a 5400 with 0.00% failure. I think all the WD reds were 5400.
Yes. He is not a an-i-mal.
search for a keyword or URL on all instances.
Iso27002 fail.
npm
can’t be run in prod due to inconsistency of upstream, and dev tools which are verboten in stage/prod.an open-source social media scheduling tool.
Pshaw! Didn’t you read the tin? It’s the ultimate open source social media scheduling tool.
Are you really saying “we the developers are going to build this however we see fit, and you the user can go fuck yourself, or else learn how to code and build it yourself”? Is that really the dynamic you’re trying to cultivate here? Seems very welcoming and productive.
Nope.
People will volunteer their time how they want, and you don’t get to tell them how to, unless you pay and also say please.
Your choice, when faced with devs spending their free time not helping your particular goals, is between
None of this should be surprising, given the fediverse is very largely supported by great people donating a lot of time. And remember, they’re not doing it for you specifically, and they’re usually doing it for their own interest or goals.
You’re going to have to spend some time or money making your particular goals happen; or else suffer someone else’s goals, or be the product they sell, or both.
I hope you realize it’s not someone denying you stuff; that it’s someone doing what they want with their free time, and it’s only accidental that it impacts you badly.
Make it better.
As an end-user (that is, the IT staff that will be deploying/managing things), I prefer less-frequent releases. I’d love to see 1 or 2 releases a year for all software
The hard floor for release frequency must always be “as security issues are fixed”, and those will rarely be infrequent in our current environment of ever-shifting dependencies.
If your environment is struggling to keep up with patching, you need to analyze that process and find out why it’s so arduous.
As an example, I took a shop from a completely manual patch slog 10 years ago to a 97% never-touch automated process. It was hard with approvals and routines, but the numbers backed me up. When I left 2 years ago, the humans had little to do beyond validation.
The sad news is, the great loss of mentors after Y2K will be seen again after RTO, and we’re not going to fix the fundamental problems that enable longer release cycles in a safe way; and so shorter update cadence will be our reality if we want to stay safe …
… and stay bleeding-edge. Shifting from feature-driven releases to only bugfix-driven releases means no churn for features, but that’s a different kind of rebasing. It’s the third leg of the shine-safe-slack pyramid; choose 2.
Compared to web-forum sites?
Half-dozen of one, 6 of the other, I’d say. It’s like they both don’t want to BE UseNET, but want the same federation and reach.
At least a few webfora tools work as mere WebUIs backing onto UseNET NNTP backbone, and that’s got the potential to use, preserve and extend the life of that protocol and interchange. But a federation that’s older than a few years may not get the love for shine that the neu protocols get.
Don’t forget, disaster recovery with a 7010 is a bobble, as you pull the disks out of one and pop them into the next and you’re likely back up and running.
Or, hell, run two with gluster. ;-)
Pros:
Cons: (vs docker-on-vm)
Refactoring is good work. Rewriting is shallow fun.
Do the math.
Exception: perl is write-only code. Always rewrite.
support us at https://buy.immich.app/
Blank page. JavaScript crutches?
Zero.
I run VMs and LDoms at work and VMs at home, a dwindling number of VMware VMs and a growing number of qemus to replace them.
I don’t need the hassle.
resort to static linking. As you always should, actually. :-)
Tell us you have no concept of enterprise OSes without using those words. Wow, is this particular statement near-sighted and provincial.
Oh god; it gets worse. This-week’s everything, like support and consistency are thrown out the window because supply chain exploits and random new bugs are just the best things ever.
This guy needs to talk to an OS security guy. I used to be one, and I could be one in a pinch, but he really needs to find an adult with a clue about the three goals of build and maybe spend a bit of time on an OS support line to learn why his process is the best way to fuck and or breach your system.
Sorry to rant, but my entire career has been either learning again in/yum-cron why what this guy says is super irresponsible and/or preventing or then fixing the fallout from following this guy’s criminally-bad advice.
A easy to use DIY grow controller firmware (for cannabis).
It would be “an [easy-to-use D.I.Y. growth] controller firmware”, but ‘firmware’ isn’t a countable so doesn’t need that article.
It’s neat how that’s two mistakes in one letter.
deleted by creator
Well, st Luigi doesn’t have a million dollar legal team to stall the proceedings until he can become president and just quash the whole thing by extending the polite convention.
How do I “care for my attention”?
If all the things in the work queue, you’re balking on a COLOUR SCHEME?
That’s like stopping the construction crew for using the wrong colour work boots, man!