#introductions It's been a long time since I used anything like twitter but I like the idea of a decentralized social network, so here I am! Toot, toot!
@smxi Yeah we need to write down some technical details for new members of the team or just to understand more of the code after few months from commits. Too big and too complex system to not write any documentation, even simple one.
Mainly because they slightly changed their syntax internally, but then once I had looked at it, I decided to add a top/bottom x count of distros with a new -r option.
Everything seems to work, last 6 months, top 6:
dws -t 6 -r 6
Distrowatch.com 6 month rankings:
Manjaro: 1 (3981+)
Mint: 2 (2279-)
elementary: 3 (1804+)
MX Linux: 4 (1647+)
Ubuntu: 5 (1426-)
Debian: 6 (1080-)
Must be something about a minimal installer iso that is 12MiB in size, heh. And a 'full' iso that is 150MiB or so.
#windhand at the intimate Starline Social Club... amazing.
Just released #Inxi 3.0.27 which contains #OpenBSD memory and disk size fixes, Android ARM phone fixes, #TinyCore #tce fixes, better debuggers for complicated debugging situations, and some #osx bug fixes. Note that normally I don't do anything more than remove real errors for osx, but because one issue raised also was an existing old issue, I fixed that as well (space in remote file system name for partitions).
Also uploaded my first #tcz package for tce, will see if it is accepted.
#OpenBSD changed column order and syntax for fre and avm in vmstat, thus breaking the expected syntax. This is fixed in #pinxi, and will be out in #inxi 3.0.27. One could ask about the wisdom of changing things like this, but there are better ways to spend ones time so all I can do is create work arounds for this type of randomness and flux. But I think I will use this to create a FAQ about why inxi is so long, with vmstat output from OpenBSD 6.1 and 6.3, along with how many lines of code the fix required
With yet another last minute fix, #inxi 3.0.26 goes live, that took way too long, and I think I'll step away from active dev for a while now barring new bugs or issues.
Found a case where #TimeShift system restore tool mounts its backup partition in hidden mode, which I've never seen before, that's a udiskd mount, not sure why it's hidden, but it is is.
Rather than mess with the complex cross architecture code for df processing in #inxi, I am just reusing some lsblk data to detect these partitions, then using the new raw size output option from --admin to show the raw size, along with <root required> message for size and used items, which are not available to non root.
I just learned that #inxi 3.0.24 made it into Ubuntu main 18-10 release, though 3.0.25, just released now, didn't, but that's fine.
3.0.25 ended up having a silly amount of new features, --admin -p/-P/-d, --partition-sort [sort type], totally refactored Device/USB data generators, #ARM / #MIPS support extended, #OpenWRT basic support working, the list is way too long for my taste.
Sometimes I worry that too many features are added that are really just for a few users, but I can't know who uses what.
New #pinxi dev output option for --admin -P, show swap swappiness and vfs cache pressure.
Useful in fringe admin type cases, for example, #liquorix tells me that if users or distros have altered these two default values, that can trigger hard to figure out bugs in the kernel. At least kernels with some configuration focuses like #liquorix.
Turns out the method I was going to use for #inxi --admin -p to determine block size was wrong, but found a standard linux tool that will give the partition logical and physical block sizes, so this feature is now working.
Added the /sys based block size report for -d disks as well, since I already had the logic, figured might as well.
This makes the upcoming inxi, as seems to the norm, filled with features and new tricks and gadgets.
--admin now actually does more than just -C cpu data, which is nice.
Free software developer.
This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!
Hosting costs are largely covered by our generous supporters on Patreon – thanks for all the help!