great feedback; i shall check out Beej and see what's up. it was many years ago that i learned my basic UNIX work.
networking algorithmics is a classic, and there's nothing else quite like it. i stand by that one for sure. he also has a lot of the great networking algorithms in there that you can't get collected anywhere else.
haven't looked at strang, either--axler did well by me!
appreciate the informed and quality comments. --nick
also dan kaminsky's and to a lesser degree dan knapp's. i was put on the spot as a sixteen year old Georgia Tech freshman acquiring his college of computing account, and between a love of good weed and childish stupidity, i chose "dank@". twenty-five years later, i'm not about to change it. no insults are meant to any of the aforementioned hax0rs.
you might want to use different algorithms for automatic control than those exposed through the motherboard firmware, which are pretty much limited to either constant, manual setpoints (usually with extrapolation), and a linear temp-to-rpm curve (ideally with different possible sources).
if you look at my linked Counterforce project, i believe there to be value beyond these simplest management schemes. we'll see.
huh, i didn't know they could be connected like that! i only knew of the -12V as a source for RS-232. thank you for the tip; i'll investigate this (i assume you're correct, just want to understand it for myself) and update the page. thank you very much!
yeah, if you look at the equations at the bottom, power goes up with the third power in relation to rpm. whippin' and drivin' that much air takes some oomph. connect that fan to any normal motherboard, and you're going to burn out your fan header pretty much immediately (especially since inrush current is probably even higher than the steady state).
that makes me so happy to hear. you have no idea how much of a pain in the ass that video was to make, lol--i'm really glad to hear it's been effective in carrying forth The Message.
i'm working on a new one now which is going to be some absolute Wizard of Oz shit; stay tuned. =] hack on!
WITH THAT SAID, Notcurses can now acquire the default background from the terminal (this was not true when I wrote the book, sigh), and I fully support @akkartik's approach given this fact. Using NCALPHA_HIGHCONTRAST together with explicit reproduction of the user's chosen background is a complete and general solution to this problem, and I really ought update the book. Thanks, @akkartik!
i am indeed a yellow jacket several times over. pa dank did not attend the university of alabama at tuscaloosa, nor any other institute of higher learning, but as anyone who knows SEC fans can tell you, attendance is not required for fandom. his roll tides were valid.
alas, it's pretty hard to get it up for GT when you just got waxed by a directional middle school from illinois.
The key is ending the device query string with DA1 aka "Primary Device Attributes", which literally every terminal i've managed to test with responds to. Guaranteed that one answer, you completely avoid nasty timeouts. This is required for even VT100 conformance, so it can be expected on even hardware terminals (though not necessarily those outside the DEC family).
I tested over 24 terminals personally, and the only one I found which didn't respond to DA1 was Terminology from EFL, which crashed forty ways to a friday anyway so who really cares?
i'm glad you asked, as i'm hella proud of this entire system. you can check the code at:
1) you can run from a regular console. if it's a linux framebuffer console and you're local, it'll even use the framebuffer to draw graphics. if you're on a pure VGA console, or ssh'd from the framebuffer console, that obviously won't work, alas.
2) there is an up-to-date port in the Ports Collection (i maintain it), and DragonFly imports things from time to time (they're running a pretty old 2.2.2 iirc). nothing on NetBSD or OpenBSD but i'd love to be there, and would be happy to take PRs!
i TA'd the intro to computer science class at Georgia Tech, taught using Java 1.1.7, back in 1999, and have used very little java since. at the time, it was not a particularly pleasant environment, though i suppose few things were.
more concretely, Autumn Lamonte's Jexer (https://jexer.sourceforge.io/) is a far better solution for Java, better than any wrapper of Notcurses could ever be due to its rich integration with the language and its expansive APIs.
beyond that, i authentically don't ever want to have to deal with bugs about a java port.