unperson [he/him]

Huh, when I set it up zsmalloc wasn’t finished and never deallocated. But it seems that today it’s the right choice! Thanks.

am i right that you can create zswap block devices and mount them like with zram? (eg. mounting /var/tmp)

zswap is a “front swap”, it needs a backing swap to function that’s crucial to the design. It automtically goes in front of all the swaps you have enabled.

You could probably put the backing swap on a loop device on a tmpfs, but I don’t know how it will handle the loopback. It’s a better idea to put it on disk. It can be a slow or write-limited disk, it will not get used much. You definitely should not use zram and zswap at the same time.

excuse me the embargo has an exception for food and medicine

It’s really easy you see, you just need to pass an inspection and get a written permission from the President of the US, the payment must be made in cash in US dollars before shipment and through some non-American bank, and the shipping company must go straight from a US port to a Cuban port and back with no layovers.

This is not a joke, it’s what is actually written in the law.

Yes, more or less, they are closely related:

In regular swap, when you’re low on memory the kernel chooses some memory pages (low priority processes and least recently used) and writes them on disk on a file or partition. When the process that owns those pages need them back, the kernel goes fetch them one at a time. Since memory pages are 4KiB the speed on this depends on the 4k random access speed of your disk.

You can have more than one swap, and the order they are used depends on their priority, or on the order they were enabled in if you didn’t specify any priority.

zram is a kind of swap space that, instead of writing to disk, compresses the pages and writes them back in RAM. You set an uncompressed size for it and if the pages don’t compress well (usually encrypted on already-compressed data) then it will occupy the same amount of RAM. Since you can’t tell in advance what the compressed size will be and there’s no mechanism to stop it from filling up, you must be conservative on the size of zram. When the zram gets full all new pages will go to the next swap in priority order. This causes a problem where there’s old data you don’t care about taking RAM space in zram that cannot be reclaimed, and then your workload is going to regular swap which is slow.

zswap is a layer on top of swap, the technical name is “frontswap”. For it to work you need to already have a swap configured. Before memory pages are written down on the swap file, they are compressed, and if the compression ratio is good enough the pages go to RAM instead of to the swap file. You set a compressed size for the zswap (by default, 20% of your total RAM) and when this limit gets full the least recently used pages are written to disk. The compression is so fast that you barely notice a hiccup while it’s happening, it feels like you magically have 50% more RAM than before.

Answering your question, zswap is configured by kernel parameters, and now that you mention it it might work to put the parameters on the kernel cmdline instead of editing sysfs, this means configuring the boot loader and adding zswap.enabled=1 zswap.compressor=lz4 zswap.zpool=z3fold to the kernel cmdline.

zswap has the same purpose than zram but a better design: it sends to disk the pages that cannot be compressed, and when it gets full it writes them back least recently used first. zram on the other hand keeps uncompressible pages around, and when it gets full all new pages go to disk and it makes the situation worse when you’re low on RAM.

The size is allright, but the zswap config is crucial.

I can’t figure out how to do it in guix with any certainty, perhaps you can enable it manually once to test and then research it better if you feel that it’s worth it. Like this, as root:

modprobe zswap
echo z3fold > /sys/module/zswap/parameters/zpool
echo lz4 > /sys/module/zswap/parameters/compressor
echo 1 > /sys/module/zswap/parameters/enabled
sysctl vm.swappiness=100

The 1 > enabled must be written after the other two. If you don’t have sysfs mounted at /sys, check with the mount command where it is.

A couple of mailing list threads that may help you do it “properly” in guix:

https://lists.gnu.org/archive/html/guix-devel/2023-02/msg00077.html https://lists.gnu.org/archive/html/guix-devel/2018-03/msg00332.html

Try this if you have low RAM, I lived with it for months when I had a broken DIMM and had to make do with 4 GB. The difference is incredible.

/etc/tmpfiles.d/zswap.conf

#Type Path                              Mode UID GID Age Argument
w /sys/module/zswap/parameters/zpool	- - - -	z3fold
w /sys/module/zswap/parameters/compressor	- - - - lz4
w /sys/module/zswap/parameters/enabled	- - - - 1

/etc/sysctl.d/00-swappiness.conf

vm.swappiness = 100

Depending on your workload you may increase swappiness to 200 with good results.

You need to set up some 8 GB of swap, it’s mostly for accounting purposes and will barely get used so it can be anywhere. If you already have zram, disable zram, it’s counter productive. Use the swapon command with no arguments to check if you have zram.

I like it because it’s designed. It think it’s the only DE with actual designers continuously working on it. It has few options and doesn’t feel hacked together.

> por ahí somos un poco pícaros, pecadores, pero el corazón es bueno

< YES, THERE ARE SOME ROGUES AND SINNERS, BUT THE HEART ITSELF IS GOOD

How are you decoding the H.264 MVC video?

I’ve got a hang-over pet policy from when I was a baby leftist to abolish rents on land, but with a twist: Any exchange of money for the use of a property is a sale. It’s absolutely financial neo bullshit but I can’t take it off my mind.

The idea being that if, over time, you pay the landlord for maintenance + the value of the house, you get the title for the house, and this is the law and you can go to court, prove that you’ve paid for rent over however many years, and get the title of the house.

If you leave before that there’d be some system where the “rent” payments are split equally and you get the value back from whoever is currently living there, because you’re selling your share to them. Since the payments are split equally minority “shareholders” leave first. If nobody lives there but you’re paying taxes and maintenance, you still paying for the house so you accrue shares of the house.

I think it might be palatable for neolibs, destroy the value of homes for rent-seeking, but preserve it for construction, which is what libs always complain about when you talk about abolishing rent.

It sounds exactly like that. Perhaps you ran firefox as root at some point?

I’d say:

• delete the cache:

rm -rf .cache/mozilla

• set yourself as the owner of everything under ~/.mozilla:

chown -Rc $(id -u):$(id -g) ~/.mozilla

• make sure you can write to everything under /.mozilla:

chmod -Rc u+w ~/.mozilla

If you get permissions errors, run them with sudo.

Another idea is to press F12 to open the dev tools, go to the network tab, and refresh the page. If something is not loading it will be highlighted in red and it will tell you the reason.

It might be some addon messing things up, you can launch firefox with no addons with firefox --safe-mode.

Does it happen in a “private” window?

Click the 🔒 icon in the address bar in front of the URL, clear cookies and site data.

Be the change you wish to see in the world.

https://library.bz/main/upload/ anonymous username genesis password upload

Last time I checked, you could only unlock Huawei phones through exploits. And while you can re-lock Xiaomi phones, they will always show the screen telling you the system is corrupted on boot. They were having supply chain problems with resellers flashing malware to their phones.

I’m more partial to Xiaomi.

Sure it’s commendable that Huawei is a sanctioned Chinese cooperative with custom made CPUs pushing the boundary on 5G, but Xiaomi phones have very good specs for the price, big batteries, they are well constructed, easy to repair, the bootloader is unlockable, and they usually have snapdragon CPUs that work great with custom roms.

https://www.gettyimages.com/detail/1230454879

Without watermark https://s.hdnux.com/photos/01/16/10/34/20481839/5/rawImage.jpg

Since the federation update, when I pick an emoji with the picker I get markdown to a URL that doesn’t contain the shortcode.

For example inserts:

![dean-neutral](https://www.hexbear.net/pictrs/image/48c31f9a-8487-48f0-afce-9db1db5fb5d6.png "emoji dean-neutral") 

Notice that the url to the png: https://www.hexbear.net/pictrs/image/48c31f9a-8487-48f0-afce-9db1db5fb5d6.png doesn’t contain the shortcode.

So right now the database has posts mixed between what I’ll call the “old format” :shortcode: and the “new format” with the URL. The new format shows up in other instances and the old format doesn’t.

Shouldn’t it be possible to run a migration in the database, and switch the old format with the new for all posts? Then disable this on-the-fly shortcode substitution that the frontend is doing.

From then on we will have to use the picker, but the emoji can change name without braking old posts. And eventually the frontend conversion can be added to the backend to restore the old behaviour.

This would simultaneously solve the issue where emojis don’t show up in other instances some times.

deleted by creator