I also do that with my roommate, along with “you must want my undoing” and “you want me to fail at everything in life”
- 2 Posts
- 29 Comments
edinbruh@feddit.itto
Linux@lemmy.ml•Google's ANGLE has merged official Wayland support, finally unblocking proper native Wayland support for the Chromium Embedded Framework (CEF)English
6·3 days agoMainly for the overlay. Even if some games can already run on Wayland, the steam client runs in CEF, so the overlay won’t work, and with that, other features, like hosting and joining a game via steam won’t work.
Ideally, we wouldn’t build infinite compute, just as much as we are actually using, and using it efficiently allows you to build less. We would still need datacenters even without LLMs, but they wouldn’t need to be so gargantuan, because even the worst, inefficient, nodejs-based, intern-written server you could ever encounter, would be heaps more efficient (or at least less demanding) than any LLM. This is true even from an economical point of view, or any practical point of view, not just environmental.
To quote Tannenbaum: “You know you have the right computer when you are always using 99% of it. If you are using 100%, you are being limited by the machine. If you are using 98% you have bought more than you need”. If datacenters were always running at 40%, we would build bigger ones.
edinbruh@feddit.itto
Linux@lemmy.ml•Google's ANGLE has merged official Wayland support, finally unblocking proper native Wayland support for the Chromium Embedded Framework (CEF)English
17·3 days agoI love how no one really cares about angle and cef, they just want steam on Wayland
(Me included)
Rice grains is not the plural of rice grain.
Unless we are eating fish grains too.
Believe it or not… For me, it was an increase in productivity, this day at least
My favourite part is when the antagonist “not Solid” says: “haha Solid, you just activated my Metal Gear” and then proceeds to metal gear everyone… Or something, I didn’t play the game
What doesn’t kill you, will do it later
I have a similar setup and it works. So you are probably doing something wrong, I don’t know what. Maybe look at dmesg for a filesystem error.
That is not a good method for testing. Maybe the filesystem still requires new files to be smaller than free space. Or maybe the file could be not really compressible, for example, you won’t be able to compress random data. You also won’t compress already compressed data, like videos.
You could write a real text file of some kB and then check the compression ratio with something like “compsize”.
The mount command mounts the disk with the options you give to it but only once. Now, because you don’t want to manually run mount everytime you use your disk, you must set it up so it is always mounted with the options you want. Udisks2 is one of the tools for that.
edit: apparently compsize is btrfs only. You can use “du” with and without --apparent-size and check the differenze
It’s like the difference between “sex” and “orgy”
Charlie! You look quite down
With your big sad eyes and your big sad frown
Life doesn’t have to be so blueeeee!
Put a banana in your ear
A banana in my ear?
Put the right banana right into your favourite ear
It’s true!
Says who?
A banana in your eeeeeeeeeEEEEEEEEEeeeeeeeaaar
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.
If it’s a flash memory (sd card, usb stick, ssd, etc), you could try f2fs, it’s very light, and it supports compression and is meant specifically for that kind of devices (well, more for ssds).
But judging your experience from your comments, I suggest you don’t delve into niche filesystems until you have more experience with Linux, especially for something like 128MB. I especially suggest you avoid zfs for now.
Huh. My computer allows me to format a 128MB image file with brtfs. It won’t do it at 64MB though.
edinbruh@feddit.itOPto
Linux@lemmy.ml•We wrote "esperto-wiimote", a Wiimote remapper with good IR tracking and complex key combosEnglish
2·1 month agoFrom what I see, the dolphin bar requires walking up to it to change mode. We want to enable and disable the IR by holding a button, and other combos in general. Also, I don’t know if the dolphin bar still lacks pointer smoothing, but we have it, and it’s even configurable
edinbruh@feddit.itOPto
Linux@lemmy.ml•We wrote "esperto-wiimote", a Wiimote remapper with good IR tracking and complex key combosEnglish
2·1 month agoThanks!




Sounds like a bug, file an issue to gnome’s gitlab. They might help you, or tell you that it’s a bug elsewhere