nostr:npub1jlvvus75texf4xaamyndnzgxnhxtack2sreyjmsmrz5ywk2w87yq4vctnj this vmem bit didn't sit right with me given that the importance of swap is greatly diminished on modern systems
Fun fact: file modification times on FAT filesystems cannot represent odd-numbered seconds
I will never forgive the french for "UTC"
Hyprland: the only Wayland compositor developed entirely in the high school boy's locker room
VFS plus ext4 plus FAT32
The FAT32 filesystem is on an MBR partition and ext4 on GPT
nostr:npub1ku30mphs68tg30c4jj0d80g698resvue70hhrvnawxvdfaq4p0usadqwn9 free software must be usable by the military but that doesn't mean we have to overtly associate with them and run marketing for them.
nostr:npub1m6ngtnj7f967ul5nttsn8gu3zmdr7rm4pcktnrujqj75kazdmtsslg5slc works on KWinFT
And so this blog post should have been written about Gnome or KDE not supporting screensavers.
nostr:npub1m6ngtnj7f967ul5nttsn8gu3zmdr7rm4pcktnrujqj75kazdmtsslg5slc it's nonsense to talk about "wayland" in a vacuum for the same reasons its nonsense to talk about, for instance, X11 less Xrandr
nostr:npub1m6ngtnj7f967ul5nttsn8gu3zmdr7rm4pcktnrujqj75kazdmtsslg5slc at the very least it's a major oversight not to mention the wlroots approach which (1) has existed for years (2) is Wayland and (3) solves this exact problem
nostr:npub1m6ngtnj7f967ul5nttsn8gu3zmdr7rm4pcktnrujqj75kazdmtsslg5slc it's nonsense to talk about "wayland" in a vacuum for the same reasons its nonsense to talk about, for instance, X11 less Xrandr
Re: screensavers on Wayland: there have been sufficient protocols to write screensavers for Wayland on wlroots-based compositors for five years. No one has bothered because screensavers are no longer in fashion. But to say it is not possible is incorrect
tfw implementing a FAT32 driver
I don't like systemd, so I don't use it. I can articulate my reasons why I don't like systemd when it comes up, but I don't go out of my way to go on any anti-systemd crusades and I don't think anyone else should, either.
Instead I just use something else and I /put the work in/ to maintaining my setup so that it works without systemd. I maintain OpenRC scripts and I patch software that is too systemd-aware to work without it.
Been porting the upstream Hare standard library to Ares, my favorite Hare example program now runs on Ares unmodified
nostr:npub1u4r67ddtcp7z06k45uywdafftmdmr40pd3uvlqduq57986gug7ns282ft7 those are the registers of the faulting process at the time of the fault
(needed to define ZYAN_NO_LIBC in cmake)
nostr:npub1zxqn376lced9ygcfccerhy0ecml0eady5e0rw5z9fv3yxyc40yfquhdw3k yeah I use this most of the time and it works fine but it can only debug the whole system at once and when you have several processes switching contexts and such it's much harder to use
Or at least dumping core on faults so you can pull it out and examine with gdb