Building firefox on aarch64 usually takes 3-4 hours depending on the device, so I hope they got a beefy aarch64 server to pull off the builds. Quickest I was able to get was about 90 minutes on a 24 core system.
Strit
joined 2 years ago
How would they determine what is AI generated and what is not?
It has been default in Arch for a long time.
What is the output of your df -h | grep tmpfs command?
It should list a couple of devices using tmpfs, where /tmp is one of them.
2 good reasons to have your /tmp on tmpfs filesystems.
- It's faster. RAM speeds are faster than your drive speeds, even SSDs.
- You are certain that all the files are removed on reboot, because RAM always gets cleared when it looses power.
1 bad reason for having your /tmp be tmpfs.
- It can quickly fill out your RAM if your application (or you manually) drop huge files in /tmp and don't move them out afterwards.
In my mind, the Pros outweigh the Cons.
Does the same happen if the panel is at the bottom of the screen?
The main issue is that they are based, and likely re-use most of the packages, on Arch Linux ARM, which has been going down hill for a while when it comes to maintenance of their repositories.
I think Manjaro ARM suffers from the same thing, as they haven't had a new release since I left over a year ago.
Some of it already works through WSL.
Not sure what you mean. The protocol supports the bridge, not the client.
SOme OS's put it in the Grub/boot menu, but otherwise you can run it from a memtest live ISO like https://www.memtest.org/.
https://tiddlywiki.com/ could also be an option. Although it's mostly for notes and such I think.