Scholars_Mate

I've been using FolderSync. It let's you sync to/from a remote server through a bunch of different protocols like SMB, SFTP, and WebDAV. You can schedule it to run automatically.

I haven't tried it myself, but I think there is a way you can get Tasker to run scripts in Termux. You could set up your own rsync scripts that way.

If you’re worried enough to encrypt the drive, you shouldn’t be auto mounting it.

This really depends on your threat model. If you are only concerned about the drive getting stolen, or wanting to keep the data on it private if you need to RMA the drive, mounting it automatically on boot with a key stored on the rootfs can be perfectly fine. If you are a journalist in a hostile country and protecting your sources from state level actors is a matter of life and death, then yeah, this would be woefully insufficient.

You can leave it.

As long as you ran systemctl daemon-reload, you should be able to try sleeping without needing to reboot.

It might be due to https://github.com/systemd/systemd/issues/33083.

Try disabling user session freezing when sleeping:

sudo systemctl edit systemd-suspend.service

Add the following to the file:

[Service]
Environment="SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=false"

Reload systemd:

sudo systemctl daemon-reload

After that, try sleeping and waking again.

Looking forward to this. I have a pair of XREAL Air 2 Pros that I mainly use to watch movies when I'm traveling. With those and a bluetooth keyboard, desktop mode on my Pixel 8 would be pretty neat.

It can be. Some of those keys might just taking advantage of regional pricing to buy keys in cheaper markets and resell them elsewhere, but some of them are purchased using stolen credit cards. Those actually cost the devs money from chargeback fees once the actually owner of the credit cards finds the fraudulent transactions. It's hard to say how many of them are from stolen credit cards, and key-resellers try to stop it, but it still happens. This was back in 2019, but the Factorio devs had a couple blog posts talking about G2A:

Blog post saying G2A is worse than piracy

Follow up blog post where G2A reimburses them (at very bottom)

• What steps did you take to rollback your root subvolume?
• Can you log into the emergency shell and share any logs?
• Is your root partition mounted in the emergency shell, or is the initramfs still mounted in the emergency shell?

I pre-ordered the 128GB SKU in the second wave. Soldered RAM doesn't matter to me if I am already maxing out what the platform is capable of. If I can dynamically configure the memory allocation between the CPU and GPU, this will be an extremely potent little AI workstation. I'll be able to cancel the pre-order of things aren't what I expect, and it isn't much of a loss for me ($100 refundable deposit).

I do agree that this branching away from Framework's roots, but I am still very happy that they are doing interesting things. I've always thought that what Minisforum has been doing with their SFF workstations has awesome, so I'm glad to see other companies wading into the same space.

Apparently Framework did try to get AMD to use LPCAMM, but it just didn't work from a signal integrity standpoint at the kind of speeds they need to run the memory at.

What filesystem are you using on the external drive? If it is NTFS or FAT, they won't store permissions on the filesystem, which would explain why the owner/group changes are not persistent. To fix that, you can set the uid/gid on mount in your fstab.

/dev/mapper/YOUR_DRIVE /path/to/mnt <fstype> rw,uid=<jellyfin_uid>,gid=<jellyfin_gid>,dmask=0002,fmask=0113

Are you using the default bridge? I have a similar setup (with Traefik instead of NPM), and for each compose file am using separate networks for the internet, proxy, and backend services.

services:
  some_service:
    ...
    networks:
      - frontend_network
      - proxy_network
      - backend_network
  backend_service:
    ...
    networks:
      - backend_network
networks:
  frontend_network:
    driver: "bridge"
  proxy_network:
    driver: "bridge"
    internal: true
  backend_network:
    driver: "bridge"
    internal: true