XOSVIEW(1)

📦
version 1.25 · 4 versions
, in fedora 43, fedora 44, nixpkgs unstable, ubuntu resolute, ubuntu stonking

🌸 XOSVIEW(1) — General Commands Manual 🌸

okay bestie, welcome to xosview, the system monitor that literally watches your machine breathe. this is the manual page, Gen Z edition, and yes — every single detail is still here, i promise on my life 💖

✨ NAME ✨

xosview — an X based system monitor 👑

✨ SYNOPSIS ✨

xosview [options]

✨ DESCRIPTION ✨

so xosview is a monitor that shows you the status of a bunch of system parameters. we're talking CPU usage, load average, memory, swap space, network usage, and honestly more than that. every resource gets its own horizontal bar, and that bar is split into color coded regions so you can see exactly how much of the resource is being used for which particular thing. it's giving data visualization but make it cute 📊

xosview runs on several platforms: Linux, NetBSD, FreeBSD, OpenBSD, DragonflyBSD, some Solaris systems, IRIX 6.5, HPUX and GNU. but listen — not all of the meters described below are supported on all platforms 😭. some meters may even look different depending on which platform xosview is running on. also, heads up: *BSD is used as an abbreviation for all the supported BSD operating systems (NetBSD, FreeBSD, OpenBSD, DragonflyBSD). iykyk.

🌈 Load: Kernel reported load average

  • all platforms — load
  • Linux — load | CPU frequency
  • *BSD — load | CPU frequency
  • SunOS5 — load | CPU frequency

🔥 CPU Usage

  • Linux — user | nice | system | soft-interrupt | interrupt | io-wait | guest | niced guest | stolen | idle
  • *BSD — user | nice | system | interrupt | idle
  • SunOS5 — user | system | wait | idle
  • IRIX — user | system | interrupt | wait | idle
  • HPUX — user | nice | system | interrupt | idle

🧠 Memory Usage

  • Linux — used | buffers | slab | map | cache | free
  • FreeBSD — active | inactive | wired | cache | free
  • DFBSD — active | inactive | wired | cache | free
  • OpenBSD — active | inactive | wired | free
  • NetBSD — active | inactive | wired | free
  • SunOS5 — kernel | zfs | other | free
  • IRIX — kernel | fs | user | free
  • HPUX — text | used | other | free
  • GNU — active | inactive | wired | free

💾 Swap Usage

  • Linux — used | free
  • *BSD — used | free
  • SunOS5 — used | free
  • HPUX — used | free
  • GNU — used | free

💿 Disk Usage: Throughput to/from local disk, per second

  • Linux — in | out | idle
  • *BSD — in | out | idle
  • SunOS5 — in | out | idle

🦋 Page Swapping: Pages to/from swap, per second

  • Linux — in | out | idle
  • *BSD — in | out | idle
  • SunOS5 — in | out | idle
  • HPUX — in | out | idle
  • GNU — in | out | idle

🌐 Network Usage

  • Linux — in | out | idle
  • *BSD — in | out | idle
  • SunOS5 — in | out | idle

🎀 GFX Usage: Framebuffer exchanges, per second

  • IRIX — swapbuffers
  • Linux — IRQs
  • *BSD — IRQs

💥 Interrupt Rate: Per second

  • Linux — interrupts | free
  • *BSD — interrupts | free
  • SunOS5 — interrupts | free

🔌 Serial Port Status: "leds" which show the serial port parameters

  • Linux — LSR and MSR

🔋 Battery Level: charge and status of batteries

  • Linux — available | used
  • *BSD — available | used

🗄️ RAID: State of disks in a software RAID array

  • Linux — disk0 disk1 disk2 ... diskN | rebuild
  • Linux — quality

🌡️ Sensors: Readings from sensors

  • Linux — I2C/hwmon sensors (lmstemp)
    • Intel Core/AMD K8+/VIA C7 temperature (coretemp)
    • ACPI thermal zones (acpitemp)
  • *BSD — I2C sensors (bsdsensor)
    • Intel Core/AMD K8+ temperature (coretemp)
💅 pro tip bestie: typing a q in the window will terminate xosview. periodt.

✨ more parts incoming, don't go anywhere ✨

✨ OPTIONS ✨

okay bestie so most of these command line options are literally just a ✨convenient✨ way to set one or more of xosview's resources. wanna know what a resource even does? scroll down to the RESOURCES section, it's all there 💖

  • -v — shows u the version number, that's it, that's the whole vibe 💅
  • -name name — sets the Resource name xosview is gonna use (same energy as the -name option on ur typical X apps like xterm). when it does resource lookups, xosview looks under name first, then under xosview. example time, straight from README.netbsd:
xrdb -merge Xdefaults.stipple
xosview -name xosvstipple &
xosview -name xosvstipplebw &
  • -display display — sets the X display to display. this one overrides the xosview*display resource, no cap.
  • -font font — picks the font xosview uses for labels. overrides the xosview*font resource 🎀
  • -title title — tells the window manager what name to use for the X window AND the icon. overrides the xosview*title resource.
  • -geometry geometry_string — sets the X geometry to geometry_string. overrides the xosview*geometry resource ✨
  • -captions — overrides the xosview*captions resource. literally equivalent to setting xosview*captions to "False".
  • +captions — overrides the xosview*captions resource. literally equivalent to setting xosview*captions to "True".
  • -labels — overrides the xosview*labels resource. equivalent to setting xosview*labels to "False".
  • +labels — overrides the xosview*labels resource. equivalent to setting xosview*labels to "True".
  • -usedlabels — overrides the xosview*usedlabels resource. equivalent to setting xosview*usedlabels to "False".
  • +usedlabels — overrides the xosview*usedlabels resource. equivalent to setting xosview*usedlabels to "True".
  • -cpu — overrides the xosview*cpu resource. equivalent to setting xosview*cpu to "False".
  • +cpu — overrides the xosview*cpu resource. equivalent to setting xosview*cpu to "True".
  • -cpus — forces the display of a single meter for ALL the CPUs in the system. equivalent to setting xosview*cpuFormat to "single". one meter, all the cores, minimalism slay 🦋
  • +cpus — forces the display of all CPUs in the system. equivalent to setting xosview*cpuFormat to "all". every core gets its moment 👑
  • -load — overrides the xosview*load resource. equivalent to setting xosview*load to "False".
  • +load — overrides the xosview*load resource. equivalent to setting xosview*load to "True".
  • -mem — overrides the xosview*mem resource. equivalent to setting xosview*mem to "False".
  • +mem — overrides the xosview*mem resource. equivalent to setting xosview*mem to "True".
  • -swap — overrides the xosview*swap resource. equivalent to setting xosview*swap to "False".
  • +swap — overrides the xosview*swap resource. equivalent to setting xosview*swap to "True".
  • -battery — overrides the xosview*battery resource. equivalent to setting xosview*battery to "False".
  • +battery — overrides the xosview*battery resource. equivalent to setting xosview*battery to "True".
  • -gfx — overrides the xosview*gfx resource. equivalent to setting xosview*gfx to "False".
  • +gfx — overrides the xosview*gfx resource. equivalent to setting xosview*gfx to "True".
  • -wireless — overrides the xosview*wireless resource. equivalent to setting xosview*wireless to "False".
  • +wireless — overrides the xosview*wireless resource. equivalent to setting xosview*wireless to "True".
  • -net — overrides the xosview*net resource. equivalent to setting xosview*net to "False".
  • +net — overrides the xosview*net resource. equivalent to setting xosview*net to "True".
  • -network maxbandwidth, -networkBW maxbandwidth, -networkBandwidth maxbandwidth — these override the xosview*netBandwidth resource. they make xosview display a meter that shows network usage with a max bandwidth of maxbandwidth. ⚠️ heads up bestie: setting the bandwidth to 0 does NOT disable the meter anymore — use the -net option for that instead, fr fr.
  • -page — overrides the xosview*page resource. equivalent to setting xosview*page to "False".
  • +page — overrides the xosview*page resource. equivalent to setting xosview*page to "True".
  • -pagespeed val — overrides the xosview*pageBandWidth resource. the resource xosview*pageBandWidth gets set to val. simple as 🍓
  • -disk — overrides the xosview*disk resource. equivalent to setting xosview*disk to "False".
  • +disk — overrides the xosview*disk resource. equivalent to setting xosview*disk to "True".
  • -int — overrides the xosview*int resource. equivalent to setting xosview*int to "False".
  • +int — overrides the xosview*int resource. equivalent to setting xosview*int to "True".
  • -ints, +ints, -interrupts, +interrupts — equivalent to -int and +int. same thing, different name, iykyk 💅
  • -irqrate — overrides the xosview*irqrate resource. equivalent to setting xosview*irqrate to "False".
  • +irqrate — overrides the xosview*irqrate resource. equivalent to setting xosview*irqrate to "True".
  • -intrate, +intrate — equivalent to -irqrate and +irqrate.
  • -lmstemp — overrides the xosview*lmstemp resource. equivalent to setting xosview*lmstemp to "False".
  • +lmstemp — overrides the xosview*lmstemp resource. equivalent to setting xosview*lmstemp to "True".
  • -coretemp — overrides the xosview*coretemp resource. equivalent to setting xosview*coretemp to "False".
  • +coretemp — overrides the xosview*coretemp resource. equivalent to setting xosview*coretemp to "True".
  • -acpitemp — overrides the xosview*acpitemp resource. equivalent to setting xosview*acpitemp to "False".
  • +acpitemp — overrides the xosview*acpitemp resource. equivalent to setting xosview*acpitemp to "True".
  • -bsdsensor — overrides the xosview*bsdsensor resource. equivalent to setting xosview*bsdsensor to "False".
  • +bsdsensor — overrides the xosview*bsdsensor resource. equivalent to setting xosview*bsdsensor to "True".
  • -xrm resource_string — this one is iconic: it lets u set ANY of xosview's resources right on the command line. here's how u'd set xosview*memFreeColor with it. notice the quoting — it stops the shell from expanding * or from splitting this into two separate arguments, xosview*memfreeColor: and purple:
-xrm "xosview*memFreeColor: purple"

🌈 X RESOURCES 🌈

here's the full list of X resources xosview supports 🫶 each one has a default value already assigned to it. u can find those defaults in the file Xdefaults, which u can get from the source distribution of xosview. wanna override them? do it in all the usual places (/usr/lib/X11/app-defaults/XOsview, $HOME/.Xdefaults, etc.) ✨

also quick PSA: it's totally OK to have a resource defined for a port of xosview that doesn't even support the feature that resource configures. xosview just ignores resources that are set for it but not supported on a given platform. no drama 💅

💖 General Resources 💖

  • xosview*title: name — the string xosview uses for the X window title. normally it uses 'xosview@machine_name' as the title, and this resource overrides that default behavior.
  • xosview*geometry: geometry_string — a standard X geometry string that defines the size and location of the X window xosview uses.
  • xosview*display: name — the name of the display where xosview contacts the X server to draw its window.
  • xosview*pixmapName: name — the filename of an X pixmap (xpm) file to use as a background image 🎀
  • xosview*captions: (True or False) — if True, xosview displays meter captions.
  • xosview*labels: (True or False) — if True, xosview displays meter labels.
  • xosview*meterLabelColor: color — the color used for the meter labels.
  • xosview*usedlabels: (True or False) — if True, xosview displays labels showing the percentage of the resource being used (or the absolute amount, depending on the meter). ⚠️ this one needs the labels option to ALSO be set to True, they're a package deal.
  • xosview*usedLabelColor: color — the color used for "used" labels.
  • xosview*borderwidth: width — the width of the border for the xosview window.
  • xosview*font: font — the font xosview uses. it's a bitmap font rendered at the X server. wanna see what's available? use xlsfonts(1) to list the fonts, and rehash the list with xset(1).
  • xosview*background: color — the color used for the background.
  • xosview*foreground: color — the color used for the foreground.
  • xosview*enableStipple: (True or False) — set it to true to try stipple support. this is mainly for the girlies stuck on 1-bit monitors/display cards 😭 try setting enableStipple true. and pls give us feedback on this if u use it — it needs some more work, but literally no one has given us any feedback so far 🙈
  • xosview*graphNumCols: number — defines the number of sample bars drawn when a meter is in scrolling graph mode. side effect alert: it also defines the width of the graph columns. this is only used by meters that have graph mode enabled.

💾 Load Meter Resources 💾

Bestie, this is the load average meter and it is so important for vibe checks on your system. 🫶

  • xosview*load — (True or False) Set this to True and xosview will show you a load meter, periodt.
  • xosview*loadProcColor — color — the color the load meter paints the load average with while it's still chillin' below the warning threshold. 🟢
  • xosview*loadWarnColor — color — the color it switches to once the load average has climbed above the warning threshold but is still below the critical load threshold. Yellow-flag energy. 🟡
  • xosview*loadCritColor — color — the color it rocks once the load average is above the critical load threshold. It's giving "girl, something is on fire". 🔥
  • xosview*loadIdleColor — color — the load meter uses this one to paint the idle field. 😴
  • xosview*loadPriority — priority — this number (and it must be an integer >= 1) sets how many tenths of a second the load meter waits between updates. A value of 1 has xosview update the meter 10 times per second (the fastest). A value of 600 would cause xosview to update the meter once a minute.
  • xosview*loadWarnThreshold — int — this number (again, must be an integer >= 1) sets the value at which the loadmeter flips its status and color from "normal" to "warning". The default value is the number of processors.
  • xosview*loadCritThreshold — int — this number (must be an integer >= 1) sets the value at which the loadmeter flips its status and color from "warning" to "critical". The default value is four times the warning threshold.
  • xosview*loadDecay — (True or False) honestly? You should probably leave this at the default value (False). The load is already a time-averaged value! No notes. 🙈
  • xosview*loadGraph — (True or False) Set it to True and the load meter gets drawn as a horizontally scrolling bargraph, showing the state value verses time. 📈
  • xosview*loadUsedFormat — (float, percent or autoscale) This resource tells xosview how to display "used" labels. The formats work as follows:
    • float: Display the value as a floating point number.
    • percent: Display the value as a percentage of the total.
    • autoscale: Display the absolute value and automatically print the units (K, M, or G) as appropriate.
  • xosview*loadCpuSpeed — (True or False) Display the current CPU speed in the load meter. ✨

🧠 CPU Meter Resources 🧠

  • xosview*cpu — (True or False) If True then xosview will display a cpu meter. On Linux, *BSD, Solaris and IRIX SMP machines, the resource cpuFormat defines how meters are created for multiple CPUs. (iykyk 👑)
  • xosview*cpuUserColor — color — the cpu meter uses this color to display the cpu user time field.
  • xosview*cpuNiceColor — color — the cpu meter uses this color to display the cpu nice time field.
  • xosview*cpuSystemColor — color — the cpu meter uses this color to display the cpu system time field.
  • xosview*cpuInterruptColor — color — the cpu meter uses this color to display the cpu hard interrupt time field.
  • xosview*cpuSInterruptColor — color — the cpu meter uses this color to display the cpu soft interrupt time field.
  • xosview*cpuWaitColor — color — the cpu meter uses this color to display the cpu IO waiting time field.
  • xosview*cpuGuestColor — color — the cpu meter uses this color to display the cpu virtualization guest time field.
  • xosview*cpuNiceGuestColor — color — the cpu meter uses this color to display the cpu niced virtualization guest time field.
  • xosview*cpuStolenColor — color — the cpu meter uses this color to display the cpu involuntary wait time field.
  • xosview*cpuFreeColor — color — the cpu meter uses this color to display the cpu idle time field.
  • xosview*cpuPriority — priority — this number (must be an integer >= 1) sets the number of tenths of a second the cpu meter waits between updates. A value of 1 has xosview update the meter 10 times per second (the fastest). A value of 600 would cause xosview to update the meter once a minute.
  • xosview*cpuDecay — (True or False) If True then the cpu meter gets split vertically in two. The top half shows the instantaneous state, while the bottom half displays a decaying average of the state. two moods fr. 🦋
  • xosview*cpuGraph — (True or False) Set it to True and the cpu meter gets drawn as a horizontally scrolling bargraph showing the state value verses time.
  • xosview*cpuUsedFormat — (float, percent or autoscale) This resource tells xosview how to display "used" labels. The formats work as follows:
    • float: Display the value as a floating point number.
    • percent: Display the value as a percentage of the total.
    • autoscale: Display the absolute value and automatically print the units (K, M, or G) as appropriate.
  • xosview*cpuFormat — (single, all, both or auto) If single, only a cumulative meter for all CPU usage is created. all creates a meter for each CPU, but no cumulative meter. both creates one cumulative meter and one for each CPU. auto makes a choice based on the number of CPUs found. slay, options. 💅
  • xosview*cpuFields — USED/USR/NIC/SYS/INT/SI/HI/WIO/GST/NGS/STL/IDLE — The set of fields to show in Linux CPU meter instead of the default. Possible fields are:
    • USED: Combine all used CPU time into one field. This is the sum of user, nice, system, soft and hard interrupts, guest, niced guest and stolen times. None of these, except stolen, may be defined together with USED.
    • IDLE: Time spent doing nothing. Includes I/O wait if it is not defined separately.
    • USR: Time spent in user mode processes. Includes nice, guest and niced guest if those are not defined separately.
    • NIC: Time spent in niced user mode processes. Includes niced guest if neither it nor guest is not defined separately.
    • SYS: Time spent in kernel code. Includes soft and hard interrupt as well as stolen time if those are not defined separately.
    • INT: Combines soft and hard interrupt handling times into one field.
    • SI: Time the kernel used to handle soft interrupts. Available on Linux kernel 2.6.0 and higher.
    • HI: Time the kernel used to handle hard interrupts. Available on Linux kernel 2.6.0 and higher.
    • WIO: Time spent waiting for I/O to complete. Available on Linux kernel 2.6.0 and higher.
    • GST: Time spent running guest OS in virtual machine. Includes niced guest if it is not defined separately. Available on Linux kernel 2.6.24 and higher.
    • NGS: Time spent running niced guest OS in virtual machine. Available on Linux kernel 2.6.32 and higher.
    • STL: Involuntary wait time when running as guest in virtual machine. Available on Linux kernel 2.6.11 and higher.

Most combinations are possible (see above for restrictions), but at least USED or USR and SYS need to be defined. IDLE field is added automatically.

🍓 Memory Meter Resources 🍓

  • xosview*mem — (True or False) If True then xosview will display a mem meter.
  • xosview*memUsedColor — color — the mem meter uses this color to display the used memory field.
  • xosview*memSharedColor — color — the mem meter uses this color to display the shared memory field.
  • xosview*memBufferColor — color — the mem meter uses this color to display the buffer memory field.
  • xosview*memCacheColor — color — the mem meter uses this color to display the cache memory field.
  • xosview*memFreeColor — color — the mem meter uses this color to display the free memory field.
  • xosview*memKernelColor — color — the mem meter uses this color to display the kernel memory field.
  • xosview*memSharedColor — color — the mem meter uses this color to display the shared memory field. (yes bestie, it's listed again, and yes it's the exact same thing — we keep it real 🫶)
  • xosview*memTextColor — color — the mem meter uses this color to display the HP text memory field.
  • xosview*memOtherColor — color — the mem meter uses this color to display the HP ``other'' memory field.
  • xosview*memActiveColor — color — the mem meter uses this color to display the *BSD active memory field.
  • xosview*memInactiveColor — color — the mem meter uses this color to display the *BSD inactive memory field.
  • xosview*memWiredColor — color — the mem meter uses this color to display the *BSD wired memory field.
  • xosview*memSlabColor — color — the mem meter uses this color to display the Linux in-kernel data structures field.
  • xosview*memMapColor — color — the mem meter uses this color to display the Linux memory mapped files field.
  • xosview*memPriority — priority — this number (must be an integer >= 1) sets the number of tenths of a second the mem meter waits between updates. A value of 1 has xosview update the meter 10 times per second (the fastest). A value of 600 would cause xosview to update the meter once a minute.
  • xosview*memDecay — (True or False) If True then the mem meter gets split vertically in two. The top half shows the instantaneous state, while the bottom half displays a decaying average of the state.
  • xosview*memGraph — (True or False) Set it to True and the mem meter gets drawn as a horizontally scrolling bargraph showing the state value verses time.
  • xosview*memUsedFormat — (float, percent or autoscale) This resource tells xosview how to display "used" labels. The formats work as follows:
  • float — shows the value as a floating point number, plain and simple 💁
  • percent — shows it as a percentage of the total, so you get the vibe in context 📊
  • autoscale — shows the absolute value and auto-prints the units (K, M, or G) as appropriate, bestie it literally picks the unit for you ✨

💾 Swap Meter Resources 💾

  • xosview*swap — (True or False) set it True and xosview will display a swap meter. periodt 💅
  • xosview*swapUsedColor — color. the swap meter uses this one for the used swap field.
  • xosview*swapFreeColor — color. and this one for the free swap field. balance 🫶
  • xosview*swapPriority — priority. this number (must be an integer >= 1, no negotiating) sets how many tenths of a second the swap meter waits between updates. a value of 1 has xosview update the meter 10 times per second (the fastest, she's zoomin 🔥). a value of 600 would cause xosview to update the meter once a minute. choose your own adventure.
  • xosview*swapDecay — (True or False) if True the swap meter gets split vertically in two. top half shows the instantaneous state, bottom half shows a decaying average of the state. it's giving duality 🌗
  • xosview*swapGraph — (True or False) set it True and the swap meter is drawn as a horizontally scrolling bargraph showing the state value verses time. so cinematic 📈
  • xosview*swapUsedFormat — (float, percent or autoscale). this resource tells xosview how to display the "used" labels. the formats work like this:
    • float — display the value as a floating point number.
    • percent — display the value as a percentage of the total.
    • autoscale — display the absolute value and automatically print the units (K, M, or G) as appropriate.

📄 Page Swapping Meter Resources 📄

  • xosview*page — (True or False) if True then xosview will display a page meter. let her cook 🍳
  • xosview*pageBandWidth — maxEvents. this number specifies the expected maximum bandwidth (in events / sec) for the page meter. when the expected maximum bandwidth (maxEvents) is exceeded, the page meter will display the relative percentage of page swapping (25% in, 75% out). lowkey informative.
  • xosview*pageInColor — color. the page meter uses this for the page-in field.
  • xosview*pageOutColor — color. and this for the page-out field.
  • xosview*pageIdleColor — color. and this for the idle field. the chill one 😴
  • xosview*pagePriority — priority. this number (must be an integer >= 1) sets the number of tenths of a second the page meter waits between updates. a value of 1 has xosview update the meter 10 times per second (the fastest). a value of 600 would cause xosview to update the meter once a minute.
  • xosview*pageDecay — (True or False) if True the page meter will be split vertically in two. the top half shows the instantaneous state, the bottom half displays a decaying average of the state. same energy as the swap one 💫
  • xosview*pageGraph — (True or False) set this True and the page meter is drawn as a horizontally scrolling bargraph showing the state value verses time.
  • xosview*pageUsedFormat — (float, percent or autoscale). this resource tells xosview how to display "used" labels. the formats work as follows:
    • float — display the value as a floating point number.
    • percent — display the value as a percentage of the total.
    • autoscale — display the absolute value and automatically print the units (K, M, or G) as appropriate.

🎮 Gfx Meter Resources 🎮

  • xosview*gfx — (True or False) if True xosview will display the GfxMeter. the value is sampled once per second, due to the usage of sadc to sample data. yes, only once a second, that's the deal bestie 🐢
  • xosview*gfxWarnColor — color. this is the color the gfx meter uses once the warn state is reached. ⚠️ vibes
  • xosview*gfxAlarmColor — color. this is the color it uses once the alarm state is reached. 🚨
  • xosview*gfxSwapColor — color. this is the color the gfx meter uses in normal state. (yes, it's spelled SwapColor, no I did not make that up, keep it exactly like that 💀)
  • xosview*gfxIdleColor — color. the gfx meter uses this to display the idle field.
  • xosview*gfxPriority — priority. this number (must be an integer >= 1) sets the number of tenths of a second the gfx meter waits between updates. a value of 1 has xosview update the meter 10 times per second (the fastest). a value of 600 would cause xosview to update the meter once a minute.
  • xosview*gfxWarnThreshold — int. this number (must be an integer >= 1) of swapbuffers per second and pipe at which the gfxmeter changes its status and color from "normal" to "warn". the default value is 60.
  • xosview*gfxAlarmThreshold — int. this number (must be an integer >= gfxWarnThreshold) of swapbuffers per second and pipe at which the gfxmeter changes its status and color from "warn" to "alarm". the default value is 120.
  • xosview*gfxDecay — (True or False) you should probably leave this at the default value (False). the gfx does not work in decay mode. so like. don't. 🙈
  • xosview*gfxGraph — (True or False) set this True and the gfx meter is drawn as a horizontally scrolling bargraph showing the state value verses time.
  • xosview*gfxUsedFormat — (float, percent or autoscale). this resource tells xosview how to display "used" labels. the formats work as follows:
    • float — display the value as a floating point number.
    • percent — display the value as a percentage of the total.
    • autoscale — display the absolute value and automatically print the units (K, M, or G) as appropriate.

🌐 Network Meter Resources 🌐

  • xosview*net — (True or False) if True xosview will display the NetMeter. Linux users will have to configure their kernels and setup some ip accounting rules to make this work. see the file README.linux which comes with the xosview distribution for details. yeah it's a whole side quest 😭
  • xosview*netBandwidth — maxBytes. this number specifies the expected maximum bandwidth (in bytes / sec) for the meter. when the expected maximum bandwidth (maxBytes) is exceeded, the network meter will display the relative percentage of network usage (25% incoming, 75% outgoing).
  • xosview*netIface — interface. if False, xosview will display the data received/transmitted by any of the network interfaces. otherwise, xosview will only display the data received/transmitted by the specified network interface. if the name is prepended with a - sign, the data in that interface is ignored. pick your faves, exclude your opps 💅
  • xosview*netInColor — color. the net meter uses this for the incoming field.
  • xosview*netOutColor — color. and this for the outgoing field.
  • xosview*netBackground — color. this is the color the network meter uses for the "idle" field.
  • xosview*netPriority — priority. this number (must be an integer >= 1) sets the number of tenths of a second the net meter waits between updates. a value of 1 has xosview update the meter 10 times per second (the fastest). a value of 600 would cause xosview to update the meter once a minute.
  • xosview*netDecay — (True or False) if True the net meter will be split vertically in two. top half = instantaneous state, bottom half = decaying average of the state. the classic combo 🦋
  • xosview*netGraph — (True or False) set this True and the net meter is drawn as a horizontally scrolling bargraph showing the state value verses time.
  • xosview*netUsedFormat — (float, percent or autoscale). this resource tells xosview how to display "used" labels. the formats work as follows:
    • float — display the value as a floating point number.
    • percent — display the value as a percentage of the total.
    • autoscale — display the absolute value and automatically print the units (K, M, or G) as appropriate.

🗂️ NFSStats (Client) Resources 🗂️

  • xosview*NFSStats — (True or False) if True xosview will display a meter to monitor NFS client stats.
  • xosview*NFSStatReTransColor — color. the color to be used for retransmit stats.
  • xosview*NFSStatAuthRefrshColor — color. the color to be used for auth refresh stats. (yep, that spelling — Refrsh — is exactly what it says, do not "fix" it, she's iconic as-is 👑)
  • xosview*NFSStatCallsColor — color. the color to be used for call stats.
  • xosview*NFSStatIdleColor — color. the color to be used for idle stats.

🖥️ NFSDStats (Server) Resources 🖥️

  • xosview*NFSDStats — (True or False) if True xosview will display a meter for NFS server/daemon stats.
  • xosview*NFSDStatCallsColor — color. the color to be used for call stats.
  • xosview*NFSDStatBadCallsColor — color. the color to be used for bad stats.
  • xosview*NFSDStatUDPColor — color. the color to be used for UDP stats.
  • xosview*NFSDStatTCPColor — color. the color to be used for TCP stats.
  • xosview*NFSDStatIdleColor — color. the color to be used for idle stats.

🔌 Serial Meter Resources 🔌

  • xosview*serial(0-9) — (True, False, or portBase). if True then xosview will display a serial meter for ttySx. the portbase will be autodetected. because autodetection can fail (if the port is locked by ppp/slip for example) you can specify the portbase instead of "True". if a portBase is used then xosview will use it instead of trying to autodetect. lowkey autodetect is just guessing with confidence 🙈

for this to work on Linux xosview needs to be suid root in order to have access to the ports. see the file README.linux which comes with the xosview distribution for more details.

okay bestie real talk: that's suid root. it's the price of admission for touching the ports. don't skip the README. 🫶
  • xosview*serialOnColor — color. this is the color the serial meter uses for bits that are set.
  • xosview*serialOffColor — color. and this is the color the serial meter uses for bits that are not set.
  • xosview*serialPriority: priority — bestie this number (and it has to be an integer >= 1, no decimals, no zero, no negativity) sets how many tenths of a second the serial meter sits around between updates. So 1 = the meter refreshes 10 times a second (that's the fastest it goes 🏃‍♀️💨). And 600 = it refreshes literally once a minute. Chill meter energy. 🧘

💥 Interrupt Meter Resources 💥

  • xosview*interrupts: (True or False) — set it True and boom, xosview shows you an interrupt meter. ✨
  • xosview*intSeparate: (True of False) — True means you get one interrupt meter per CPU on SMP machines (so many meters, so much drama 👑). False means just one single meter, no crowd. Default: True.
  • xosview*intOnColor: color — the color used to show interrupts that are active. 🔥
  • xosview*intOffColor: color — the color used to show interrupts that are inactive. 💤
  • xosview*intPriority: priority — same deal as always, and yes it must be an integer >= 1: this is how many tenths of a second the int meter waits between updates. 1 = 10 updates per second (fastest). 600 = one update per minute. Pick your vibe. 🎀

📊 Interrupt Rate Meter Resources 📊

  • xosview*irqrate: (True or False) — True and xosview will show an interrupt rate meter. Slay. 💅
  • xosview*irqrateUsedColor: color — the color used to show the interrupt rate itself.
  • xosview*irqrateIdleColor: color — the irqrate meter uses this color to display the idle field. 😴
  • xosview*irqratePriority: priority — you already know the drill: integer >= 1, number of tenths of a second the irqrate meter waits between updates. 1 = 10 times a second (the fastest). 600 = once a minute. ⏱️
  • xosview*irqrateDecay: (True or False) — True means the irqrate meter gets split vertically in two, like a lil sandwich 🥪. The top half shows the instantaneous state, and the bottom half shows a decaying average of the state. Iconic.
  • xosview*irqrateGraph: (True or False) — True here and the irqrate meter gets drawn as a horizontally scrolling bargraph, showing the state value vs. time. It's giving history lesson 📈.
  • xosview*irqrateUsedFormat: (float, percent or autoscale) — this one tells xosview how to display those "used" labels. The formats go like this:
    • float: display the value as a floating point number.
    • percent: display the value as a percentage of the total.
    • autoscale: display the absolute value and automatically print the units (K, M, or G) as appropriate. ✨

🌡️ Lm Sensors Resources 🌡️

  • xosview*lmstemp: (True or False) — True = xosview shows an lmstemp meter. Temperature check, but make it a graph 🫶.
  • xosview*lmstempHighest: number — the highest value displayed. If you don't give it, or the number you give is too small, the meter will adjust itself to fit the actual and alarm values (it's flexible like that 💁‍♀️). You can also override it for any single meter with lmstempHighestN.
  • xosview*lmstempActColor: color — color of the actual value.
  • xosview*lmstempHighColor: color — color above the high alarm value, and it's also used to indicate the alarm. 🚨
  • xosview*lmstempLowColor: color — color of the actual value when it's below the low alarm value.
  • xosview*lmstempIdleColor: color — color of the zone between the actual and high alarm values.
  • xosview*lmstempN: filename — the name of the input file from /proc/sys/dev/sensors/*/* or /sys/class/hwmon/*/{,device}/, where N=1,2,3,.... It can also be an absolute path. For example:
xosview*lmstemp1: temp1
xosview*lmstemp2: temp2_input
Note: lots of sensors keep the value and the alarm threshold in files named *_input and *_max/*_min respectively. In that case, just specifying the base name like "temp1" right here is enough — xosview will use both files for you. 💖
Note: if the same file name as lmstempN, lmshighN or lmslowN exists in other sensor directories, then lmsnameN needs to be specified, or an absolute path used, so xosview finds the correct one. No mixing up sensors, okay? 🙈
  • xosview*lmshighN: filename or number — an optional high alarm value, or the name of a file from /sys/class/hwmon/*/{,device}/, with N=1,2,3,.... Can also be an absolute path. If you don't give it, lmstempHighest is used as both the maximum and the high alarm. For example:
xosview*lmshigh1: 70
xosview*lmshigh2: temp1_crit_hyst
  • xosview*lmslowN: filename or number — an optional low alarm value, or the name of a file from /sys/class/hwmon/*/{,device}/, with N=1,2,3,.... Can also be an absolute path. Default is 0. For example:
xosview*lmslow1: 1.5
xosview*lmslow2: fan1_min
  • xosview*lmsnameN: name — optional name of the sensor device to use when xosview is hunting down the filename(s) you gave in lmstempN, lmshighN and lmslowN. Peep /sys/class/hwmon/*/{,device}/name for the names of your sensors. Heads up: this has no effect on files given as absolute paths. For example:
xosview*lmsname1: nct6779
xosview*lmsname2: radeon
  • xosview*lmstempLabelN: string — the N-th label for the values above. Default is TMP.
  • xosview*lmstempHighestN: number — overrides the default lmstempHighest for meter N. 🎯
  • xosview*lmstempUsedFormatN: (float, percent or autoscale) — overrides the default lmstempUsedFormat for meter N.
  • xosview*lmstempPriority: priority — okay so it's the same rule every time: integer >= 1, the number of tenths of a second the lmstemp meter waits between updates. 1 = 10 updates per second (fastest). 600 = once a minute. ⏰
  • xosview*lmstempUsedFormat: (float, percent or autoscale) — how xosview displays the "used" labels. The formats, once again:
    • float: display the value as a floating point number.
    • percent: display the value as a percentage of the total.
    • autoscale: display the absolute value and automatically print the units (K, M, or G) as appropriate. 🌈

🔥 ACPI Temperature Resources 🔥

  • xosview*acpitemp: (True or False) — True and xosview displays an acpitemp meter. 🌡️
  • xosview*acpitempHighest: 100 — highest temp value displayed, default 100. But if acpihighN is given, the value gets read from there instead. Sneaky swap 👀.
  • xosview*acpitempActColor: color — color of the actual temperature.
  • xosview*acpitempHighColor: color — color above the alarm temperature, also used to indicate the alarm. 🚨
  • xosview*acpitempIdleColor: color — color of the space between actual and alarm temperatures.
  • xosview*acpitempN: filename — name of the temperature file from /proc/acpi/thermal_zone or /sys/devices/virtual/thermal. Careful bestie: the last directory part must be given, like TZ0/temperature. An absolute path can also be used. 💅
  • xosview*acpihighN: filename — name of the high value / trip point file from /proc/acpi/thermal_zone or /sys/devices/virtual/thermal, or an absolute path to one.
  • xosview*acpitempLabelN: Labelstring — the N-th label for the temperatures above. Default is TMP.
  • xosview*acpitempPriority: priority — you know it, you love it: an integer >= 1 setting how many tenths of a second the acpitemp meter waits between updates. 1 = 10 per second (the fastest). 600 = once a minute. 🕐
  • xosview*acpitempUsedFormat: (float, percent or autoscale) — how to display the "used" labels. Here's the rundown:
    • float: display the value as a floating point number.
    • percent: display the value as a percentage of the total.
    • autoscale: display the absolute value and automatically print the units (K, M, or G) as appropriate. ✨

🧊 Intel Core / AMD K8+ / VIA C7 Temperature Sensor Resources 🧊

  • xosview*coretemp: (True or False) — True = xosview shows a coretemp meter. 🌡️💖
  • xosview*coretempHighest: 100 — highest temp value displayed, default 100. But if the CPU throttling temperature (tjMax) is supplied by the operating system, that gets used instead. The OS said what it said 👑.
  • xosview*coretempHigh: number — the value to use as the alarm temperature, default is coretempHighest. If a usable value is supplied by the operating system — like the temperature for which maximum cooling is required — then that's used instead. ❄️
  • xosview*coretempActColor: color — color of the actual temperature.
  • xosview*coretempHighColor: color — color above the alarm temperature, also used to indicate the alarm.
  • xosview*coretempIdleColor: color — color of the zone between actual and alarm temperatures.
  • xosview*coretempDisplayType: (separate, average or maximum) — tells xosview how to display the CPU temperature. The formats work like this:
    • separate: display one meter for each CPU core of a multi-core CPU. This is the default.
    • average: display the average of core temperatures of a multi-core CPU. On multi-socket machines, one meter per physical CPU is displayed.
    • maximum: display the highest core temperature of a multi-core CPU. On multi-socket machines, one meter per physical CPU is displayed. 🏆
  • xosview*coretempPriority: priority — yes, again, integer >= 1: how many tenths of a second the coretemp meter waits between updates. 1 = 10 updates per second (the fastest). 600 = once a minute. ⏳
  • xosview*coretempUsedFormat: (float, percent or autoscale) — how to display the "used" labels. As follows:
    • float: display the value as a floating point number.
    • percent: display the value as a percentage of the total.
    • autoscale: display the absolute value and automatically print the units (K, M, or G) as appropriate. 🌸

🐡 *BSD Sensor Resources 🐡

  • xosview*bsdsensor: (True or False) — True and xosview will display a bsdsensor meter. 🦋
  • xosview*bsdsensorHighest: number — the biggest value the meter is ever gonna show. If you don't give it, or you give it something too smol, the meter just adjusts itself to fit the actual and alarm values. And yes bestie, you can override it per-meter with bsdsensorHighestN. 💅
  • xosview*bsdsensorActColor: color — the color of the actual value. The real one. The moment. ✨
  • xosview*bsdsensorHighColor: color — color for anything above the high alarm value, and it's also what flags the alarm. She's serving double duty. 🚨
  • xosview*bsdsensorLowColor: color — the color of the actual value when it dips below the low alarm value. 🥶
  • xosview*bsdsensorIdleColor: color — the color for the zone between the actual and high alarm values. Chill zone energy. 😌
  • xosview*bsdsensorN: name.type
  • xosview*bsdsensorHighN: name.type
  • xosview*bsdsensorLowN: name.type

okay so THESE three are the plug — they define where the actual value, the high alarm value and the low alarm value for meter N=1,2,3,... get read from. The name is the sensor driver, and type is the value you want. Both alarm values are optional, and they can also just be handed to you as static numerical values. no cap.

On OpenBSD and DragonFly BSD you can find the correct pair with the systat command, like:

xosview*bsdsensor1:     it0.temp1
xosview*bsdsensorHigh1: 100

On NetBSD, you find the driver name with the envstat command. The value name for the actual reading is typically 'cur-value', for the high alarm it's 'critical-max' and for the low alarm it's 'critical-min', like:

xosview*bsdsensor2:     coretemp0.cur-value
xosview*bsdsensorHigh2: coretemp0.critical-max

For literally all possible NetBSD value names, go read the envstat source code. iykyk. 📖

FreeBSD has no usable sensor drivers as of version 9.0. 🙈 However, ACPI thermal zones can be used by defining the sysctl node below hw.acpi.thermal, like:

xosview*bsdsensor1:     tz0.temperature
xosview*bsdsensorHigh1: tz0._CRT

ACPI thermal zones can be used like this on DragonFly BSD as well. 🐉

  • xosview*bsdsensorLabelN: string — the N-th label for the meters above, and the default is SENN. 🏷️
  • xosview*bsdsensorHighestN: number — overrides the default bsdsensorHighest for meter N. 💅
  • xosview*bsdsensorUsedFormatN: (float, percent or autoscale) — overrides the default bsdsensorUsedFormat for meter N.
  • xosview*bsdsensorPriority: priority — this number (and it must be an integer >= 1, don't try it) sets how many tenths of a second the bsdsensor meter waits between updates. A value of 1 has xosview updating the meter 10 times per second (that's the fastest). A value of 600 would make xosview update the meter once a minute. 🐢
  • xosview*bsdsensorUsedFormat: (float, percent or autoscale) — this resource tells xosview how to display "used" labels. The formats work like this:
    • float: Display the value as a floating point number.
    • percent: Display the value as a percentage of the total.
    • autoscale: Display the absolute value and automatically print the units (K, M, or G) as appropriate.

🔋 Battery Meter Resources 🔋

  • xosview*battery: (True or False) — if True then xosview will display a battery meter. Linux girlies will need APM or ACPI support in their kernels for this to work, periodt. For both APM and ACPI, xosview shows the status/sum of all the batteries. Plus — the legend text gets changed/adjusted to reflect the current state (charging/low/critical/etc.) of the battery/batteries. 💖
  • xosview*batteryLeftColor: color — the color used to show how much battery power is left. 🔋
  • xosview*batteryUsedColor: color — the color used to show how much battery power got used.
  • xosview*batteryChargeColor: color — used as 'left' when the batteries are getting charged. ⚡
  • xosview*batteryFullColor: color — used as 'left' when the batteries are fully charged. APM and ACPI do provide this info, but not all machines actually do. 😭
  • xosview*batteryLowColor: color — APM only — the 'left' color that indicates a low battery. Depends on the machine — e.g. below 25% remaining capacity.
  • xosview*batteryCritColor: color — APM case: the 'left' color if APM indicates a 'critical' state (less than 5%). ACPI case: the 'left' color if the remaining capacity is below the alarm value (which you can set yourself in /proc/acpi/battery/BAT[01]/alarm). 🚨
  • xosview*batteryNoneColor: color — for when no battery is present, or all the batteries get removed (while on AC). 💀
  • xosview*batteryPriority: priority — this number (which must be an integer >= 1) sets how many tenths of a second the battery meter waits between updates. A value of 1 has xosview update the meter 10 times per second (the fastest). A value of 600 would cause xosview to update the meter once a minute.
  • xosview*batteryUsedFormat: (float, percent or autoscale) — this resource tells xosview how to display "used" labels. The formats work like this:
    • float: Display the value as a floating point number.
    • percent: Display the value as a percentage of the total.
    • autoscale: Display the absolute value and automatically print the units (K, M, or G) as appropriate.

📶 Wireless Meter Resources 📶

  • xosview*wireless: (True or False) — if True then xosview will display the link quality of each wireless connection. Note that the graph will *never* show up if you don't have any wireless devices, or no wireless extensions in the kernel (/proc/net/wireless). Default is true. 🌈
  • xosview*PoorQualityColor: color — the color for the quality field when it's between 0 and 6. 😬
  • xosview*FairQualityColor: color — the color for the quality field when it's between 7 and 14.
  • xosview*GoodQualityColor: color — the color for the quality field when it's higher than 14. slay. ✨
  • xosview*wirelessUsedColor: color — this one's the background color.
  • xosview*wirelessPriority: priority — this number (which must be an integer >= 1) sets how many tenths of a second the wireless meter waits between updates. A value of 1 has xosview update the meter 10 times per second (the fastest). A value of 600 would cause xosview to update the meter once a minute.
  • xosview*wirelessDecay: (True or False) — if True then the wireless meter gets split vertically in two. The top half shows the instantaneous state, while the bottom half displays a decaying average of the state. she's giving duality. 🦋
  • xosview*wirelessUsedFormat: (float, percent or autoscale) — this resource tells xosview how to display "used" labels. The formats work like this:
    • float: Display the value as a floating point number.
    • percent: Display the value as a percentage of the total.
    • autoscale: Display the absolute value and automatically print the units (K, M, or G) as appropriate.

💾 Disk Meter Resources 💾

  • xosview*disk: (True or False) — if True then xosview will display a disk meter.
  • xosview*diskInColor: color — the disk meter uses this color to display the reads field.
  • xosview*diskOutColor: color — the disk meter uses this color to display the writes field.
  • xosview*diskIdleColor: color — the disk meter uses this color to display the idle field.
  • xosview*diskBandwidth: bandwidth — this number specifies the expected maximum bandwidth in bytes per second for the disk meter.
  • xosview*diskWriteColor: color — this color gets used for the linux meter to show writes.
  • xosview*diskReadColor: color — this color gets used for the linux meter to show reads.
  • xosview*diskPriority: priority — this number (which must be an integer >= 1) sets how many tenths of a second the disk meter waits between updates. A value of 1 has xosview update the meter 10 times per second (the fastest). A value of 600 would cause xosview to update the meter once a minute.
  • xosview*diskDecay: (True or False) — if True then the disk meter gets split vertically in two. The top half shows the instantaneous state, while the bottom half displays a decaying average of the state.
  • xosview*diskGraph: (True or False) — if this is set to True then the disk meter gets drawn as a horizontally scrolling bargraph showing the state value verses time. 📈
  • xosview*diskUsedFormat: (float, percent or autoscale) — this resource tells xosview how to display "used" labels. The formats work like this:
    • float: Display the value as a floating point number.
    • percent: Display the value as a percentage of the total.
    • autoscale: Display the absolute value and automatically print the units (K, M, or G) as appropriate.

👑 RAID Meter Resources 👑

  • xosview*RAID: (True or False) — if True then xosview will display a RAID meter.
  • xosview*RAIDdevicecount: int — please drop your RAID device count (n) here, or 0 if you don't have any supported RAID devices. xosview will then display n RAID state displays. 🫶
  • xosview*RAIDdiskOnlineColor: color
  • xosview*RAIDdiskFailureColor: color

These colors get used for indicating working/online or failed/offline disks. The order (from left to right) is the same as in /proc/mdstat. 💅

  • xosview*RAIDresyncdoneColor: color
  • xosview*RAIDresynctodoColor: color
  • xosview*RAIDresynccompleteColor: color

If a resync/rebuild of the RAID array is in progress, the "done" and "todo" colors get used. If no rebuild/resync is running, then the "complete" color will be shown. ✨

  • xosview*RAIDPriority: priority — this number (which must be an integer >= 1) sets how many tenths of a second the RAID meter waits between updates. A value of 1 has xosview update the meter 10 times per second (the fastest). A value of 600 would cause xosview to update the meter once a minute.
  • xosview*RAIDUsedFormat: (float, percent or autoscale) — this resource tells xosview how to display "used" labels. The formats work like this:
  • float — shows the value as a floating point number. decimals, bestie, live a little 💅
  • percent — shows the value as a percentage of the total. very "what portion of the whole is this" of it ✨
  • autoscale — shows the absolute value and auto-prints the units (K, M, or G) as appropriate. it just knows. iconic behavior honestly 🎀

🔍 OBTAINING 🔍

so if you're like "okay bestie where do I even get this" — this version of xosview is distributed from the following site:

http://www.pogo.org.uk/~mark/xosview/

go get it, she's waiting 💖

👑 AUTHORS 👑

okay this is the part where we give everybody their flowers because this is a group project and it ate 🌸 every single one of these people put in work, no cap:

  • Mike Romberg <mike.romberg@noaa.gov> — original author, plus the Linux and HPUX ports. the founding mother of the group chat 👑
  • Brian Grayson <bgrayson@netbsd.org> — NetBSD port and most of the nice enhancements for version 1.4, plus initial work on the FreeBSD port. carrying the 1.4 era fr fr
  • Scott McNab <jedi@tartarus.uwa.edu.au> — added the scrolling graph mode. the scrolling graph?? obsessed 🔥
  • Tom Pavel <pavel@slac.stanford.edu> — most of the FreeBSD support, and more resource-handling improvements
  • Greg Onufer <exodus@cheers.bungi.com> — SunOS port
  • Stefan Eilemann <eilemann@gmail.com> — IRIX 6.5 port
  • Sheldon Hearn <axl@iafrica.com> — FreeBSD libdevstat-based diskmeter support
  • David W. Talmage <talmage@jefferson.cmf.nrl.navy.mil> — added battery-meter support to NetBSD 🔋
  • Oleg Safiullin <form@openbsd.org> — OpenBSD interrupt-meter support
  • Werner Fink <werner@suse.de> — originator of the loadmeter
  • Massimiliano Ghilardi <ghilardi@cibs.sns.it> — Linux pagemeter
  • Carsten Schabacker <cschaba@spock.central.de> — made extensions to the serial-meter
  • Paal Beyer <pbeyer@online.no> — ported the linux memstat kernel module to linux-2.1
  • Jerome Forissier <forissier@isia.cma.fr> — author of the Linux SMP kernel patch which xosview uses to display meters for each CPU. one meter per CPU? main character energy 🫶
  • Tomer Klainer <mandor@cs.huji.ac.il> — initial port to BSDI
  • Arno Augustin <Arno.Augustin@3SOFT.de> — Solaris disk and network meters
  • Alberto BARSELLA <ishark@lsh01.univ-lille1.fr> — fixes for linux diskmeter + ip_chains support
  • Thomas Waldmann <ThomasWaldmann@gmx.de> — Linux raid meter, bitfieldmeter. many cosmetic fixes ✨
  • Leopold Toetsch <lt@toetsch.at> — Linux lms temp meter 🌡️
  • David O'Brien <obrien@nuxi.com> — FreeBSD 4.* updates, and a few other suggestions
  • Christos Zoulas <christos@netbsd.org> — C++ standard compliance and other NetBSD fixes
  • Tim Ehlers <tehlers@gwdg.de> — wireless Link-Meter for Linux 📶
  • Mark Hills <mark@pogo.org.uk> — bug fixes and general caretaking. the caretaker!! 🧚
  • Tomi Tapper <tomi.o.tapper@student.jyu.fi> — temperature sensor, and FreeBSD updates
  • Raymond S Brand (rsbx@acm.org) — misc fixes
  • And many others who have sent in small fixes and improvements. — not me getting emotional over the unnamed contributors 😭 every single one of y'all matters, lowkey legends
and that's the whole page bestie!! you read it all, that's genuinely so slay of you 💜

so real talk — this one comes to you from the 3rd Berkeley Distribution, it's XOSVIEW(1), and that's a wrap fr fr. go check your meters, hydrate, and remember: it's giving system monitor, it's giving iconic, periodt 🦋🌈⭐💖

📦 where this page comes from