zarenki
@zarenki@lemmy.ml
- Comment on Chinese startup launching RISC-V laptop for devs and engineers priced at around $300 1 month ago:
It is a Linux machine. Runs a Debian derivative, and it’s not like Windows or anything else that isn’t Linux/BSD can run on a RISC-V laptop.
This isn’t the first RISC-V laptop, but the significance of a RISC-V laptop existing is primarily for developers who work on software targeting RISC-V systems. The ability to run RV64 programs without emulation and to natively compile RV64 software without cross-compilers is valuable to some people. Also, China in particular sees value in having computing products that aren’t affected by sanctions; the processor in this is designed and manufactured by a Chinese company without licensing any intellectual property from US or UK.
Explaining what RISC-V is
RISC-V is a relatively newer CPU instruction set architecture that competes with x86 (Intel, AMD) and ARM (Qualcomm, Ampere, MediaTek, etc.). Its current designs don’t really match those two in general-purpose performance yet but has the distinction of being a free, open, and extendable standard. Whereas x86 has only two CPU vendors and ARM has many vendors who all need to pay per-core license fees to ARM Holdings and have limits imposed on what they can do to it, RISC-V processors can be made by any hardware vendor with the means to make a processor and can be custom-designed to better fit specialized use-cases. Its use in general-purpose CPUs is catching on fastest in China but it sees use across the world in academia and in special-purpose processors by companies like Western Digital.
- Comment on Do you encrypt your data drives? 2 months ago:
Yes.
My home server has dropbear-initramfs installed so that after reboot I can access the LUKS decryption prompt over SSH. The one LUKS partition contains a btrfs filesystem with both rootfs and home as subvolumes. For all the other drives attached to that system, I use ZFS native encryption with a dataset that decrypts with a keyfile from that rootfs and I have backups of an encrypted copy of that keyfile.
I don’t think there’s a substantial performance impact but I’ve never bothered benchmarking.
- Comment on Roku has patented a way to show ads over anything you plug into your TV 2 months ago:
The problem with those TV apps is DRM. All the major streaming services require that you either use a locked down platform (probably checking SafetyNet and more on Android TV) or settle for their browser UI which lacks dpad support and gets quality throttled to 1080p or lower.
Circumventing that DRM is possible, but doing no project at the scale of a platform like those would dare the both legal risk and support headache of making those circumventions (which are very liable to break) a core part of the OS.
- Comment on My Overconfidence Killed Me and My Immich Installation 2 months ago:
Something I’ve noticed that is somewhat related but tangential to your problem: The result I’ve always gotten from using compose files is that container names and volume names get assigned names that contain a shared prefix by default. I don’t use docker and instead prefer podman but I would expect both to behave the same on this front. For example, when I have a file at
nextcloud/compose.yml
that looks like this:volumes: nextcloud: db: services: db: image: docker.io/mariadb:10.6 ... app: image: docker.io/nextcloud ...
I end up with volumes named
nextcloud_nextcloud
andnextcloud_db
, with containers namednextcloud_db
andnextcloud_app
, as long as neither of those services overrides this behavior by specifying acontainer_name
. I believe this prefix probably comes from the file-levelname:
if there is one and the parent directory’s name otherwise.The reasons I adjust my own compose files to be different from the image maintainer’s recommendation include: to accommodate the differences between podman and docker, avoiding conflicts between the exported listen ports, any host filesystem paths I want to mount in the container, and my own preferences. The only conflict I’ve had with other containers there is the exported port. zigbee2mqtt, nextcloud, and freshrss all suggest using port 8080 so I had to change at least two of them in order to run all three.
- Comment on Linux distro for selfhosting server 3 months ago:
That’s actually a choice you’re offered during Debian’s interactive install. When you’re offered the option to set a root password, if you leave it empty the system will disable direct root login and instead give your first normal user
sudo
access. - Comment on Linux distro for selfhosting server 3 months ago:
Debian. I was in a similar boat to OP and just a couple weeks ago migrated my almost 8-year-old home server setup from Ubuntu LTS to Debian Stable. Decided to finally move away from Ubuntu because I never cared for snap (had to keep removing it with every upgrade) and gradually gained a few smaller issues with Ubuntu. Seems good to me so far.
I considered RHEL/Rocky but decided against them largely because I wanted btrfs for my rootfs, which their stock kernel doesn’t have, though I use a few Red Hat developed tools like podman and cockpit. Fedora Server and the like have too fast a release lifecycle for my liking, though I use Fedora for my desktop. That left Debian as the one remaining obvious choice.
I also briefly considered throwing a Debian VM into TrueNAS Scale, since I also use this system as a ZFS NAS, but setting that up felt like I was fighting against the “appliance” nature of what TrueNAS tries to be.
- Comment on Announcing Ibis, the federated Wikipedia Alternative 3 months ago:
The main reason people use Fandom in the first place is the free hosting. Whether you use MediaWiki or any other wiki software, paying for the server resources to host your own instance and taking the time to manage it is still a tall hurdle for many communities. There already are plenty of MediaWiki instances for specific interests that aren’t affected by Fandom’s problems.
Even so, federation tends to foster a culture of more self-hosting and less centralization, encouraging more people who have the means to host to do so, though I’m not sure how applicable that effect would be to wikis.
- Comment on Sustaining Proton’s mission over time | Proton 4 months ago:
If you’re planning to subscribe to Proton Unlimited or Proton Family regardless, you might as well try Proton Drive. They try to be fairly privacy focused similar to Proton’s other products.
Mega has a similar privacy-oriented design. Such that the server side shouldn’t have direct access to your unencrypted file data or its decryption keys.
Still, any web-based service necessitates trusting the JavaScript you receive not to leak out your password or keys. Both Proton and Mega have a good track record so far in that regard, but the best practice for privacy with raw data storage is to encrypt your own data with local tools and treat any remote server as untrusted.
- Comment on Windows 11 24H2 goes from “unsupported” to “unbootable” on some older PCs 4 months ago:
I would not count on all major distros maintaining support for processors as old as Core 2 forever.
RHEL 9 in particular (and by extension CentOS Steam, Alma, Rocky) already dropped support for all of the processors affected by this breakage since 2022.
Linux systems often group these CPU feature set generations into levels, where “x86-64-v2” requires SSE4 and POPCNT (Nehalem/2008 and newer) and “x86-64-v3” requires AVX2 (Haswell/2013 and newer).
Ubuntu and Fedora are already evaluating optimized package builds for both v2 and v3 but haven’t announced any plans to drop baseline x86-64 yet; I wouldn’t be surprised to see it happen within the next two years. Debian is a relatively safer bet for old hardware.