

The reasoning behind this move is said to be X/Twitter not being in line with Debian’s shared values
The reasoning behind this move is said to be X/Twitter not being in line with Debian’s shared values
But did you read the last line? This isn’t classic control panel, this is the new control panel.
0 hours.
It is currently off because I don’t leave it running overnight when I am not using it.
Having some blackberry flashbacks with that keyboard.
Beat me to it mate.
Here is the link. https://vscodium.com/
I thought one of them did comment about it and it was something like the uefi drivers taken from Fedora or something.
Humans order by strings, computers order by characters.
Imagine how fast problems would be identified with that many rubber ducks for an engineer to talk to.
And each in their own way. Like leftpad or openssl
Wouldn’t be the first time.
Does the job get suspended if tasks are being done on the drive or will the task stall with the command being fired then the drive wakes up again defeating the purpose of the job?
Much like school essays
Draft.
Final.
ActualFinal.
ActualFinalFixed.
ActualFinalFixed2.
Oh so ublock origin lite. A manifest V3 compatible adblocker for chromium browsers.
The original ublock origin is unaffected
Looks normal for testing stuff. I have 5ish in my desktop hypervisor.
Honestly, ewaste center.
Not much an atom with a gig of ram can do.
It’s asking me for a password. OMG why doesn’t it know it’s me and do what I tell it.
I have been burnt too many times by vendor incompatibility at work to not read the manuals before deploying something.
Windows can’t even get their own UI right.
Look at the win10 control panel. Nearly a decade later and we still have to use the classic control panel to change settings.
Had a Centos VM that kept slipping time. Every week it would loose about 30min. No amount of NTP syncing got the time correct until manual intervention.
Msp couldn’t work it out, couldn’t rebuild the server for infrastructure reasons, and only that server had the issue. The other 3 VMs on that host were fine.
Cron job on one server took it current time, sshed to the dodgy server and configured the correct time.
Why does that sound familiar.
Did they load an OS into ram to run ssh then rebuild the machine, also some VPS that the provider was dragging their feet on remote hands.