![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/8f2046ae-5d2e-495f-b467-f7b14ccb4152.png)
looks like the house of saud has placed its bet.
…just this guy, you know.
looks like the house of saud has placed its bet.
indeed, but your SSH ports should not be hanging out in the wind for any old IP to hit.
from the same comedy troupe that brought you last seasons blockbuster hit, “the sanctity of marraige” comes the sequel, “for everyone but you!”.
tl;dw - individual containers isolated in HVMs with traditional container tooling.
I have been living under a rock and had not heard of this project before. it does seem to give a reasonable alternative to the manual VM[container] two-step for some workloads.
an older, but more complete intro lives at Kata Containers An introduction and overview [you tube]
understood. tinycore is a live installable distro, so you can still test it on bare metal.
pick the GUI flavor and kick the tires for a while.
the repos are browsable inside the package manager - I would imagine they are browsable outside as well, but I have never had cause to do so.
honestly, give tinycore a shot. fire it up in a VM and take a look around - it really is an amazingly useful distro.
- Lazy
the only honest answer.
creative is great, but sometimes you really just want your fleet of servers to do their fleet of servers thing. no fuss, no hassle. 100% solid and stable. learn the “debian way” and life is grand.
debian saved my marraige and raised my kids - ok, not really, but almost.
lots of debian. its debian all the way down.
“oh hell. someone is trying to be more evil than us! gotta fix that.” - google, definately.
if the install had finished and the installer was simply reading the flash drive to clean itself up, unmount filesystems and reboot, then chances are you are fine. However, as a personal rule I never allow an installation to go into production if there were any unexpected anomalies during installation. its just not worth the risk.
agreed on the batterygate thing. ars did a pretty decent writeup on the reasons behind the CPU throttling.
my issue with Apple has always been their… “its magic!” bullshit. that marketing leads to more and more e-waste as other manufacturers follow the sucessful Apple marketing trend, because, you know… its NOT actually magic and batteries are consumable items.
“Ford, how am I supposed to operate my [insanely expensive] digital watch now [that the battery is broken]?” guess i’ll just get another one!
The only way to circumvent this problem is to invent a battery that doesn’t age. The person who does that is going to be a _very _ rich dude.
or how about easily replacable batteries. yes, they can be designed in a sleek, apple-y ergonomic way. but its much easier and more profitable to make battery replacements a phone killing endeavour. this applies to other manufacturers as well.
“have you tried swtching it off and on again” solves 90% of support requests - at least for a little while ;-)
its presidential pokemon and, now that they have trump, they plan on breeding him hard.