• 0 Posts
  • 96 Comments
Joined 1 year ago
cake
Cake day: June 23rd, 2023

help-circle



  • tvcvt@lemmy.mltoLinux@lemmy.mlLinux on iMac?
    link
    fedilink
    arrow-up
    1
    ·
    3 months ago

    Linux runs fine on Intel Macs. There are a couple peculiarities you’ll want to be aware of, though.

    • Ventoy doesn’t work as an installer. The boot menu will come up, but any ISO you choose will hang
    • Not all distros will recognize the wireless card and install the firmware (Be prepared to install it using a USB to Ethernet adapter)
    • Same goes for the iSight web cam

    Other than those initial hiccups, everything works pretty flawlessly.




  • I’m making some assumptions, namely that you’re using an unprivileged LXC container and the mount point is a bind mount.

    Unprivileged LXC shift user ID numbers so that an escape won’t result in root access to the host. The root user (uid 0) in the container is actually uid 100000 from the perspective of the Proxmox host.

    What I usually do is set ownership of my bind mounts to that high-numbered ID (so something like chown -R 100000:100000 /path/to/bind/mount) from Proxmox. Then the root user in the container will be able to set whatever permissions you need directly.


  • Since you’re interested in this kind of DIY, approach, I’d seriously consider thinking the whole process through and writing a simple script for this that runs from your desktop. That will make it trivial to do an automatic backup whenever you’re active on the network.

    Instead of cron, look into systemd timers and you can fire off your script after, say, one minute of being on your desktop, using a monotonic timer like OnUnitActiveSec=60.

    Thinking through the script in pseudo code, it could look something like:

    rsync -avzh $server_source $desktop_destination || curl -d "Backup failed" ntfy.sh/mytopic

    This would pull the back from your server to your desktop and, if the backup failed, use a service such as ntfy.sh to notify you of the problem.

    I think that would pretty much take care of all of your requirements and if you ever decided to switch systems (like using zfs send/recv instead of rsync), it would be a matter of just altering that one script.



  • tvcvt@lemmy.mltoSelfhosted@lemmy.worldHomelab Organization
    link
    fedilink
    English
    arrow-up
    3
    ·
    5 months ago

    Dokuwiki (dokuwiki.org) is my usual go-to. It’s really simple and stores entries in markdown files so you can get at them as plain text files in a pinch. Here’s a life lesson: don’t host your documentation in the machine you’re going to be breaking! Learned that the hard way once or twice.

    For reverse proxies, I’m a fan of HAProxy. It uses pretty straightforward config files and is incredibly robust.



  • If you want an image, it doesn’t matter what the underlying file system is. You should be able to use a tool like Clonezilla and get a 1:1 copy. Depending how you’ve set up partitioning, you could also use sgdisk to set up the proper partitions and zfs send/recv for the new data portion of the drive and install a boot loader. That’s probably the way I’d go in this instance.




  • To amplify RedWeasel’s very good answer, fstab runs as root and unless you specify otherwise, the share will mount with root as the owner on the local machine. From the perspective of the Samba server, it’s the Jellyfin user accessing the files, but on the local machine, but local permissions come into play as well. That’s why you can get at the files when you connect to the share from Dolphin in your KDE system—it’s your own user that’s mounting the share locally.




  • Not sure how your stack works together, but sudo will let you run particular commands as a different user and you can be pretty specific with the privileges. For example you can have a script that’s only allowed to run docker compose -f /path/to/compose.yml restart containername as a user in the docker group. Maybe there’s some docker-specific approach, but this should work with traditional Unix tools and a little scripting.