The headline seems to mean 81% of generation and storage capacity. When the article talks about battery storage, it only says storage, not generation.
The headline seems to mean 81% of generation and storage capacity. When the article talks about battery storage, it only says storage, not generation.
Yes. A perpetual license just means no fixed end date, not that it’s irrevocable or interminable.
You can probably get away with continuing to use ESXi free licenses even commercially, you just won’t have support. And at home, nothing is going to stop existing versions from working.
Incidentally, assuming I found the right license agreement: https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/downloads/eula/universal_eula.pdf
It doesn’t actually say it’s perpetual. It only says “The term of this EULA begins on Delivery of the Software and continues until this EULA is terminated in accordance with this Section 9”, but that section only covers termination for cause or insolvency, there is no provision for termination at VMware’s discretion. So, while I’m not a lawyer, it definitely sounds like you can continue using ESXi free.
Actually, reading further, I think the applicable license is this one: https://www.vmware.com/vmware-general-terms.html
But that one has even less language about license term and termination. Although it does define “perpetual license” as “a license to the Software with a perpetual term”, again not irrevocable or interminable.
That one was posted by a spambot, which a lot of people have blocked.
I missed the word “server” every time and thought it was a client, and spent far too long trying to figure out how you’d play Minecraft in Bash. Text based? ASCII graphics?
Increase account creation restrictions (you are here)
I’ve been using Alma for a while and been happy with it. Like RHEL types, it’s slightly behind on versioning, but that’s by design.
No, but it’s a hell of a lot easier to put huge language datasets into the machine learning blender and get a model out, instead of manually programming every conceivable linguistic construction.
Yes, and that’s a good thing if you don’t want it to start killing processes. You have that extra time/space to deal with the out-of-memory condition yourself.
Or you can ignore that condition and continue using the system in a degraded state, with swap as “disk RAM”.
No, but Windows is so entrenched that they don’t need to actually be competitive in order to keep making profit. Instead, the Windows team has to invent things nobody ever wanted or needed that they can advertise to make it look like they’re still useful. Software UX polish-passes don’t make good marketing. You can’t seriously put “you know that one weird thing that only happened to a fraction of users sporadically? we fixed it” on a marketing campaign.
Nobody. And it’s not like Red Hat runs the X.Org Foundation, either, at most they have one seat on the board. Development will continue.
it’d be real cool if the mods of the biggest community on lemmy.world would actually do some moderating
ISP shittiness aside, ISPs do actually pay for Internet backbone access by the byte. Usually there are peering agreements saying “you take 1tb of traffic from us, and we’ll take 1tb of traffic from you”, whether that traffic is destined for one of their customers (someone on Comcast scrolling Instagram), or they’re just providing the link to the next major node (Comcast being the link between AT&T’s segment of the US backbone and Big Mike’s Internet out in podunk Nebraska).
And normally that works pretty well, until power users start moving huge amounts of data and unbalancing the traffic.
I’m not sure what that post is meant to show, if swap isn’t “disk RAM”. That post even concludes:
Swap […] provides another, slower source of memory […]
PSoD is already used by VMware ESXi. And Windows Insider builds, I think.
Maybe green?
If it’s only on the ESP, it won’t persist across reinstalls, and definitely not drive swaps.
But I do see mentions of attacking via firmware capsule. If that works, then yes, that will persist.
A singularity is the single point mass at the center of an ideal (Schwarzschild) black hole. But mathematically, that can only happen if the mass that forms the black hole isn’t rotating. In reality, all the mass in the universe is moving around, because mass is not distributed uniformly, so gravity is pulling stuff around in a big mess. So when a black hole forms, it’s definitely a rotating (Kerr) black hole.
A rotating mass has different gravity than a non-rotating mass. Not by much, but when you’ve got the enormous mass of a black hole, it becomes significant. This causes objects “falling into” a black hole to “miss” the point at the center, and form more of a cloud during spaghettification.
The article is fairly accessible if you sit down and read it.
Honestly, inside the event horizon, everything stops making sense compared to our day-to-day experiences. The immense gravitational forces distort space and time. It doesn’t really make sense to think about objects remaining intact as recognizable objects once they cross the event horizon.
How? You could certainly temporarily break the boot process, but I can’t see how you’d completely brick it.
My favorite is when the sssd package maintainers don’t properly update their dependencies, so when some of the packages get updated, they don’t pull in others, and then I’m not able to log in with my external account.
It depends. I’ve used a chargeback where I sent a product back for a warranty repair, and the seller stopped responding. The bank just wanted documentation, and they put it through. I imagine you could argue for a chargeback in this case, if you used a credit card.
Are current laws against harassment insufficient?