CouncilOfFriends

joined 1 year ago
[–] [email protected] -1 points 6 months ago (3 children)

I don't run gnome myself but I asked AI and there may be a setting:

  1. Open the GNOME Control Center (you can search for "Control Center" in the Activities overview).
  2. Navigate to the "Desktop" section.
  3. Click on the "Keyboard" settings.
  4. Scroll down to the "Visualization" section.
  5. Uncheck the option labeled "Control pointer with keyboard focus."
[–] [email protected] 23 points 6 months ago (3 children)

No. Do not bring snek

[–] [email protected] 21 points 8 months ago* (last edited 8 months ago) (6 children)

Anyone who has read a single NTSB accident report will understand what an insane idea this is.

[–] [email protected] 2 points 8 months ago

When I moved into my otherwise shitty apartment, having Google Fiber was the selling point. Paying Comcast a monthly fee for unlimited bandwidth is something I vow never again to do.

[–] [email protected] 7 points 8 months ago (3 children)

This is correct. As the article says employees are using their phones as hotspots so it's not as if it's a Faraday cage. Their IT guy should do a Wi-Fi site survey and install a few AC Pros.

[–] [email protected] 5 points 8 months ago

After using some grandfathered T-Mobile family plan for over a decade I moved us to Tello. Still the same towers, but with our usage it's half the price.

[–] [email protected] 9 points 9 months ago
  1. Don't make him angry
  2. If Hulk is already angry, light a lavender candle and play some calming music
[–] [email protected] 1 points 9 months ago* (last edited 9 months ago)

One note which may not apply to you, I installed my Proxmox to boot from 2 256G SSDs as a basic RAID 1 mirror and only have the bare minimum data in VM storage to reduce size of backups. Backup retention on the boot drives is limited because a cron job on the VM handles copying backups to the MergerFS pool for longer term storage.

Moving docker's data directory to the 'slow' drives was a helpful decision, this post covers the old/wrong ways to do that and the way which worked (data-root). Docker data doesn't take up a huge amount of space, but it saved me some work recently when I found my media server had been down for a while and couldn't remember when it worked last to identify a working backup. I spun up a fresh Debian image and ran through the steps to reinstall the stack, and point to the same Docker data path. Running the same Docker compose command got most services working with the old metadata, though others i renamed/removed the service's path and reconfigured.

My docker-compose and its revisions are the extent of a backup I need for a piracy box as my internet is quick enough to recreate my library within a couple days if needed.

view more: ‹ prev next ›