Watching @JurassicWorld I witnessed "dmidecode --isolate" and throughout the remainder of the film I could not stop thinking about this. movies.stackexchange.com/questions/9006… I am positive I saw "dmidecode --isolate" and now I'm thinking how I could make that a real thing
There's something called the DPDK for Linux. dpdk.org Stands for Data Plane Development Kit. It has an option for isolating CPUs. If you're going to add an option to dmidecode to "isolate" something/everything -- and in the premise of the @JurassicWorld movie -- 1/
if "dmidecode --isolate" is to "save the day" in a failing ventilation system, it would have to (no doubt) isolate a failing component. In #FreeBSD quite often we see cards that violate our standard understanding and ultimately evoke warnings about interrupt storms and thus 2/
I would imagine "dmidecode --isolate" to function similarly. Though, what interaction it would use to communicate back to a BIOS to quell errant hardware is beyond me. Engaging to say the least. Would certainly rate the movie a great experience. Cheers @JurassicWorld
• • •
Missing some Tweet in this thread? You can try to
force a refresh
I wonder how many of my followers know about ssh's builtin session management prompts? To explore this, I first need to explain why initial tilde(s) (~) seem to be "eaten" by your shell. Strap in for a fun one, you either already knew about this or this might just shock you 1/?
2/? While ssh'd to another host, after you press ENTER (this only works after pressing ENTER) press tilde (~). It won't appear on screen. Press tilde again. If you are ssh'd more than once (e.g., ssh -> ssh -> shell), it still won't appear. For each ssh, +1 tilde is eaten
3/? If you are 4 ssh's deep (e.g., from laptop: ssh A -> ssh B -> ssh C -> ssh D -> login shell on server D) you have to press tilde (~) 5 times after ENTER to get it to appear on the shell prompt of your login shell on server D. There is hidden magic in those missing tildes ...