Are you happy with the Kiyo X?

I don’t really want to give some of your hyperbolic statements credibility by replying, but - I’ve been loving Mudeer for tiling. I’m not sure if it qualifies as a true tiling window manager and my setup does straddle the line between tiling and floating, but it works great for me.

f2fs doesn’t track file creation times. I thought I was ok with this, but, the longer I used it the more places it started to become an issue. Now I have all these notes that were created in 1970 and it just really takes away a powerful way of searching and organizing my notes.

Really? There are some pretty serious trade-offs that Qubes requires if you’re going to use it as your daily driver. I’m far more security-conscious than anyone I know, but I couldn’t bring myself to make those trade-offs.

I really enjoyed reading this, thank you.

I’d be interested in reading more about the benefits of using an atomic distro, if you were looking for ideas on things to write about. I imagine it must make system upgrades easier but what about replicating your setup elsewhere? Like if I was doing some development and now I need to throw some serious hardware at the problem, could I just backup all my Flatpaks some configs, and spin up my desktop on a cloud VM?

I’m pretty sure that’s what Nix is all about, but the learning curve seems steep.

I really appreciate this, thank you. I think I had confused myself by playing with ‘u16’ and ‘u8’ and somehow coming to the conclusion that they were matching the right side of a 32-bit string. (Which may still be true, but, I’m just masking u32s now).

This is what I ended up with, which is working the way I’d expect:

tc filter add dev wlan0 protocol ip parent 1: prio 1 u32 \
	match u32 0x30d6 0x0000ffff at -16 \
	match u32 0xc92d1905 0xffffffff at -12 flowid 1:20

This sends Ethernet frames destined for 30:d6:c9:2d:19:05 to flow 1:20, and it doesn’t seem to match a second device I tested. So, all good! Thank you again.

Here’s a little script I’ve put in my $PATH, called memsum:

#!/usr/bin/bash
/usr/bin/ps -eo rss,command --sort -rss | egrep $1 | awk '{ hr=$1/1024 ; sum +=hr} END {print sum}'

Now you can go: memsum firefox or memsum whatever and see that, actually, apps use a ridiculous amount of memory these days.

I can get Firefox up to 8GB by using things like Office 365.