• 10 Posts
  • 86 Comments
Joined 3 年前
cake
Cake day: 2023年2月1日

help-circle



  • So, first of all, there is no gui for this, that I’m aware of, so you will have to do it from terminal. Second, on f2fs, compression works that you don’t enable compression for a folder, instead you mount the drive with compression enabled, and new files will be compressed automatically.

    So what you need is to set up your disk to be mounted with compression. There are many paths you can follow here. If you want your drive to be (almost) permanently connected, the easiest way is to use “/etc/fstab”. If you want to use it as a regular SD card, mounting and ejecting it from your file explorer etcetera, then you should go here and learn how to have udisks2 mount your device with compression, which should be what your desktop environment uses to mount drives. I suggest you set that up for your specific device, and not for all f2fs devices. Good luck.

    You can look up other useful f2fs options on the arch wiki. I suggest you add all those options that reduces writes to your disk and improve durability (like lazytime).

    You should use zstd as compression algorithm, and because this is a slow and small drive, you can crank up the level of compression.

    If you manage to pull this off, the next time you install a (bigger and faster) drive on your pc, you can try to look into zfs.







  • You can buy an usb-powered one for a couple euros from AliExpress, or you can hook 5V to an original bar. But the bar itself is just two Infrared lights, there’s plenty of substitutes (i.e. literally two candles 20cm apart).

    P.s. do not leave the bar permanently on, you will burn out the LEDs. The Wii turns it off with the console

    P.p.s. you can configure esperto-wiimote to run a command when you connect the First wiimote, and disconnect the last. It’s meant for turning on and off the bar, if you can do it programmatically




  • Fedora desktop (any DE, and most desktop distros, for that matter) uses networkmanager to configure networks, because it is powerful and offers an API for DEs to configure networks, so as long as you have the drivers, networking will work the same. However, If I recall correctly, Gnome and KDE use the same frontend library for networkmanager, just with different GUIs, so they really are going to be the same, and they have for many years. Cosmic being new and rust based might have rolled its own frontend or used a different library, and it might not be as mature as what the other DEs use.

    Try configuring your WiFi manually, editing networkmanager’s config files directly, instead of the gui. And see if that work. I would even suggest straight up copying the config files produced by gnome or KDE.




  • Mainly two reasons, one about architecture, and one about vendors

    In the PC world, the entire ecosystem is designed to be modular, and people expect to be able to put windows/Linux on any pc and have it work despite the manufacturer. The kernel just wakes up on one of the cores, figures out the CPU, wakes the rest of the cores, and from there it figures out the rest of the computer. By contrast arm systems are tightly integrated, each SoC is unique and there’s no way to figure out the rest of the system, the kernel wakes up on one of the cores, reads out what SoC this is, and mostly has to already know the chip and any additional hardware connected to it.

    But, sure, there are only so many SoCs (kinda), and displays, cameras, and touchscreens are mostly similar, you are bound to find a way to tell the kernel what hardware is running on and have it work, right? Except a lot of phone hardware is proprietary (duh) and requires bespoke proprietary drivers, google pretends to encourage vendors to submit their drivers upstream, but this doesn’t really happen. Now, if you are familiar with running external drivers on Linux, you probably know how picky the kernel is in what to load, but android’s kernel is specifically modified to be less picky, to allow vendors more slack. Mind you, the API is not more stable, the kernel is just less picky.

    Bonus: running Linux on arm laptops is indeed proving kind of a challenge (nothing impossible, but resources are limited), that’s because they are built like a mobile phone.