If you run your services off of a homelab rack that dims the lights whenever you power it on
If you are in this situation, then you definetly should get some more power, or at least a UPS to make sure you don’t trip a breaker.
If you run your services off of a homelab rack that dims the lights whenever you power it on
If you are in this situation, then you definetly should get some more power, or at least a UPS to make sure you don’t trip a breaker.


Ooh, very cool!
Are the two different pictures different wavelengths, or do you just have two seperate sensors? (I have no idea how this works, just a highschool level understanding of x-rays.)
That sounds pretty plausible, but I’m not sure.
The windows are only very slightly off center, inconsistent, and even the ones above the clock are as well (although the clock mechanism could extend both up and down).
But I also don’t have any better explanation.
I have a number of things running in the background after booting, so here’s some numbers for you:
In addition to that, there’s always a number of systems services, most of which use a negligible amount of memory, but here’s some I’m just picking out because I recognize what they do:
Of course, these are just a snapshot of the systems state, and can only really give you a very rough idea of how much memory something might use at one point in time.
If you want to make your board game more complicated (probably not, but I like the idea, so I’m just throwing it in here), you could use it as an opportunity to teach virtual memory, segmentation, paging and internal vs external fragmentation. Maybe players get certain processes with memory requirements and have to fit them into their own main memory, and whoever can fit the most processes wins, or whoever cannot allocate memory for a new process looses. (I’m just writing down what’s coming out of my head, I don’t want to hijack your game idea, sorry.)