avidamoeba

BEIRUT, Lebanon — The Lebanese army says that a soldier was killed in an Israeli strike on a military post in southern Lebanon, adding that soldiers fired back at the source of the fire.

It is the first time the army has fired back at Israeli forces since the conflict began a year ago, a Lebanese security source tells Reuters.

Folks with vaginas, I'm conducting some family comparative analysis and I'd like to know how many standard pieces of toilet paper do you use when wiping after a pee. I posted some comments with options to upvote if you like.

cross-posted from: https://sh.itjust.works/post/25996640

https://www.visualcapitalist.com/charted-how-american-tech-workers-feel-about-joining-a-union/

Is that a thing at all? I doubt it but thought I'd check just in case.

Personal use numbers:

• Ubuntu: 27.7%
• Debian: 9.8%
• Other Linux: 8.4%
• Arch: 8%
• Red Hat: 2.3%
• Fedora: 4.8%

in 1986, mountain bikes were making their mark in Canada, as cyclists swapped out their 10-speeds for more rugged rides. This CBC news segment from The National explores the early days of the mountain biking craze, featuring enthusiasts like Ian K., who traded his Volkswagen-like commuter for an $800 mountain bike, likening it to driving a Porsche. While the trend was just beginning, the piece questions whether mountain biking would remain a luxury niche or become a mainstream activity as prices dropped and mass availability rose. Originally aired on May 26, 1986.

It's fairly obvious why stopping a service while backing it up makes sense. Imagine backing up Immich while it's running. You start the backup, db is backed up, now image assets are being copied. That could take an hour. While the assets are being backed up, a new image is uploaded. The live database knows about it but the one you've backed up doesn't. Then your backup process reaches the new image asset and it copies it. If you restore this backup, Immich will contain an asset that isn't known by the database. In order to avoid scenarios like this, you'd stop Immich while the backup is running.

Now consider a system that can do instant snapshots like ZFS or LVM. Immich is running, you stop it, take a snapshot, then restart it. Then you backup Immich from the snapshot while Immich is running. This should reduce the downtime needed to the time it takes to do the snapshot. The state of Immich data in the snapshot should be equivalent to backing up a stopped Immich instance.

Now consider a case like above without stopping Immich while taking the snapshot. In theory the data you're backing up should represent the complete state of Immich at a point in time eliminating the possibility of divergent data between databases and assets. It would however represent the state of a live Immich instance. E.g. lock files, etc. Wouldn't restoring from such a backup be equivalent to kill -9 or pulling the cable and restarting the service? If a service can recover from a cable pull, is it reasonable to consider it should recover from restoring from a snapshot taken while live? If so, is there much point to stopping services during snapshots?

China and Russia announced Friday that they are conducting joint naval exercises in the waters and airspace near Zhanjiang city in the south of China.

Have some new old stock SATA drives vomiting at you?

[  234.811385] ata1.00: status: { DRDY }
[  234.811392] ata1: hard resetting link
[  240.139340] ata1: link is slow to respond, please be patient (ready=0)
[  244.855349] ata1: COMRESET failed (errno=-16)
[  244.855375] ata1: hard resetting link
[  250.199443] ata1: link is slow to respond, please be patient (ready=0)
[  254.875508] ata1: COMRESET failed (errno=-16)
[  254.875533] ata1: hard resetting link
[  260.211562] ata1: link is slow to respond, please be patient (ready=0)
[  289.919779] ata1: COMRESET failed (errno=-16)
[  289.919810] ata1: limiting SATA link speed to 3.0 Gbps
[  289.919816] ata1: hard resetting link
[  294.963876] ata1: COMRESET failed (errno=-16)
[  294.963904] ata1: reset failed, giving up
[  294.963909] ata1.00: disable device

Grab your contact cleaner and clean their SATA connectors!

I just bought a new 1TB Crucial MX500 made in god knows what year and installed it in a virgin SATA port of a M710q made in 2016 and I got the vomit you see above every time I loaded the drive. Reseated all the connectors. More vomit. Scratched my head a couple of times reaching for the trash bin and I had a brainwave that there might be oxidation from sitting naked with the elements. Took out the DeoxIt Gold, dabbed all the connectors on the SATA path, cycled them a few times, powered on and loaded the drive. No more vomit.

Coffee Addicts have their DF64 Gen 2 for CAD $420 at the moment. Still in-stock at the time of writing. I was considering a DF54 but at this price I couldn't not jump on the 64.

E: Seems like many other distributors have the discount now.