Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)T
Posts
10
Comments
255
Joined
2 yr. ago

  • I've been super happy with my 8th gen Intel NUC i5. I put it in an Akasa Turing fanless case, installed an NVMe for host OS, and an 8TB SSD for data. It's low power and so quiet that I couldn't imagine ever using fans again.I also have a USB 3.2 drive dock for external backup HDDs, but I only turn it on when actively doing a monthly backup.

    8TB holds more media than I'll ever need, but I do trim movies and shows regularly. For some, 8TB won't be anywhere near enough, and SSDs exceeding this are ridiculously expensive.

  • We swapped our 2080s for 6800 XTs last year and couldn't be happier...a 7900 GRE should be great for gaming, but I can't speak to LLM performance.

  • I was able to extract the img from the ISO using geteltorito as described in section 5 of this ArchWiki article. Once you mount the resulting img file, you'll end up with the same file contents achieved by running their Windows BIOS Utility through wine.

    The relevant binaries appear to be under the folders, N24ET76P and N24ET76W. Both scan clean for me, for whatever that's worth:

     
        
    curl -X POST -F'file=@N24ET76P/$0AN2400.FL1' https://pk.fail
    {"details":{"analysis-time":"1.395106993s","hashes":{"md5":"ba73792a5fc831ca84b4cd3a21c03247","sha1":"24a5bb42d670c7705aed06588f0092ec11a32564","sha256":"b9510c73657460ae24c550b71d217a543b0fc3c30a3e081eff31d9d8f1a2bdda","sha512":"8ef6f0dcffbca05b79710b8599b1b1c926ee59185a675bc7eeede6da040c751097303ada523611271de6aaf190a597cdd6e9d5cf564d06987abcf712f61227c6"}},"status":"not-vulnerable"}
    
    curl -X POST -F'file=@N24ET76W/$0AN2400.FL1' https://pk.fail
    {"details":{"analysis-time":"1.438471526s","hashes":{"md5":"de1551b0bcc73e19375f7111def72278","sha1":"cd41f36d018f940c308a7be25a20e81bdb7e4cf2","sha256":"b3f646095e47bb94f04390c756cb4133201b1231a8b224174f10bb06bd3835f2","sha512":"55143f4903f92d88057bc9d4232b0d328e9ace36330f35fafdf0485d8bebb3f79b9fedc88ab1dec7fc04a8a3e0890887c1dd7632a2ffa397fb0917be90e3f93f"}},"status":"not-vulnerable"}
    
    
      

    The linux command mentioned in the Ars Technica article elsewhere here is efi-readvar -v PK. For Fedora and Arch users, efi-readvar is available in the efitools package.

    Edit: Clarity

  • I can't say for certain, but I think you just have to grab the last firmware binary released for your T480 from the Lenovo website and run it through the online validator: https://pk.fail/

  • If ambient noise is a concern, I'd go with an SSD. If money is tight, an HDD will give you the best value.

    My server is in an otherwise quiet home office/sitting room, so I went with an 8TB SSD (870 QVO). Spinning disks make a fair bit of noise just waking up, let alone the actual file operations.

  • You should be able to layer the xdg-desktop-portal-gnome package, which will also pull any dependencies.

    To answer your general question though, yes I believe you can easily install at least minimal versions of each DE with little impact to rpm-ostree performance. They don't need to be separate images, though that's possible too by rebasing and pinning. I would just layer the necessary packages to load a GNOME environment (start with rpm-ostree install gnome-shell). This way everything stays up to date with the active image. For example, I'm running GDM under Kinoite simply because I was having unresolvable issues with SDDM and LightDM.

    Pinning separate images would require you to rebase with each image update and then unpin/pin the old/new images...too much work.

  • NUC 8i5, 32GB, 500GB NVMe (host), 8TB SSD (data), Akasa Turing fanless case, running Proxmox:

    • samba
    • syncthing
    • pihole
    • radicale
    • jellyfin
    • minidnla

    I also have a Pi 4 running LibreElec for Kodi on the home theater. Nothing fancy yet and it more than meets our current needs. Most maintenance done over SSH.

    Would like to eventually get a proper web and email server going (yes, I know).

  • Haha, oh I know and I'm all for trying things for the fun of it! Just wondered if there was a practical benefit of such a setup.

  • Interesting endeavor...any practical benefits? I would think that even a slow USB 2.0 drive would provide better performance than a cloud-based file system.

  • Craigslist is still superior in the PNW, at least in my experience.

  • I've enjoyed seeing some of these blasts from the past, but I admit it's not as nice when the VM host window is captured as well. Just something to consider... I appreciate it all the same.

  • A gecko is a lizard, so it's in keeping with SUSE's chameleon theme. Maybe a little too similar for corporate.

    I think Komodo Linux, or KomodOS are good options too, but I can't recall if they were already used for a distro.

  • Off the top of my head...

    • Gecko or GeckOS
    • LizOS
    • ReptilOS
    • ChamelOS
    • KomodOS
  • Me too! I can't recall now why I parted with it, but I wish I hadn't. Would love to see what it could do today.

  • If that's one of those old 10" netbooks, I had good experiences running dwm and xmonad on mine back in the day (had an Acer and later an MSI Wind U120(?)). Typically ran all my apps maximized, one per desktop. Firefox did okay, but this was around 2010-2012. Mostly stuck with terminal apps and it was more than snappy enough.

    Some screenshots from days past...

  • See my follow-up post elsewhere here. Sounds like you might not have an always-online device to keep others always synced, and/or the devices you're using to add entries aren't online when you do. Might consider using a designated device for database modifications.

  • That used to happen to us before we started using SyncThing (and before we had data plans on our phones).

    By the time we migrated to it, we had a home server running 24/7 and this ensured that at least one device in the chain was always online, had the latest version of the database, and pushed it to other devices as they came online. Our phones also have data plans now, so things generally sync in realtime which helps avoid issues.

    If you don't have at least one always-online device, I think the next easiest way to avoid sync conflicts is to modify the database from one designated device. That way even if a conflict does arise, you'll know which device is always correct.

    For resolving the conflicts, I would open both databases, sort by modified, and review the latest changes in each.