Almrond

The problem with this is primarily that windows uses NTFS as it's filesystem. Being proprietary, NTFS has never played well with Linux and installing it to an NTFS partition is regarded as a genuinely terrible idea. Converting partitions safely is nearly impossible to do in place.

Oooo, this one actually happened to me. Head on collision with a barrier at 80mph, fell asleep at the wheel after getting out of a 27 day stint in the ICU. Dare To Be Stupid by Weird Al was playing when i collided.

Incognito mode and reopening closed tabs.

I have no issue with LTT as a whole, I just really don't like Linus. He portrays an almost weaponized incompetence in a lot of computing topics and doesn't accurately represent his own lack of understanding to the audience that couldn't tell on their own. By all accounts there is one hell of a team working there, they just chose a really bad face to represent the actual content.

Just my personal take for what it's worth.

Yeah, and the consequence of them using the dataset is massive amounts of people contribute useful data to the project. It is a fair exchange in my opinion. There are lots of reasons to hate Pokemon Go, but this isn't one of them. You can use the maps too, and they are far better as a result of PGO using them.

Maltesers

Haha, unfortunately no. None of the blades used a windowing system, so we technically wouldn't have been able to as there is no graphical output (well, the IPMI controllers could have, but that's kind of cheating). Although, as I'm thinking about it... We probably could have run it over ASCII graphics in a terminal... Man, that was a bit of a wasted opportunity, weather modelling is boring as hell.

We were running meteorological models mostly, but I did have a colleague that was trying to use it to predict wildlife migratory patterns using topographical mapping. It was batched out on a few projects at any given time while I was there, it was essentially timeshares between a few different research departments.

It's more of an operating cost issue. It's almost decade-old hardware. It was efficient in its day, but compared to new hardware it just costs so much to run you would be better served investing in something with modern efficiency. It won't be junked, it will be parted out. If you are someone that wants a cheap homelab with infiniband and shitloads of memory you could pick up a blade for a fraction of what it would otherwise cost. I fully expect it to turn into thousands of reasonably powerful servers for the prosumer and nerd markets instead of running as a monolithic cluster.

Hey, I have worked on this exact machine before, neat to see they are finally decommissioning it. It would be a terrible purchase to actually use these days though, for the cost of moving and deploying it you could rock a few Hopper or Grace clusters that would outperform the cluster for less than half of the operating overhead.

I fully expect it to get parted out, the actual components would be far more useful on their own as cheap homelab systems, and would be a much better ROI versus using it as is. This thing is water cooled, just the plumbing would be a nightmare to deal with if you aren't set up for it, and if you are you would be better off going with a modern architecture anyway.

Kind of, you would use a deployment node to manage the individual blades, they are running really specialized software that is basically useless without the management nodes. It wouldn't be difficult to spin it up (Terascale would have it ready to batch out jobs within a few hours) but you are going to need to engineer your building around it to even get that far. Your foundation needs to support multiple tons of weight, be perfectly level, be able to deliver megawatts of power, remove megawatts of heat (it is water cooled, so you need to have infrastructure and cooling towers to handle that), and you need to be able to get it into the building to begin with. I have worked on this system a few times, just moving it would literally cost upwards of 7 figures. The computer is pretty easy to use, it's all of the supporting infrastructure that will need a literal team of engineers. I could (and have, kind of) spin the machine up to start crunching data within a day on my own. Fuck moving it, and double fuck re-cabling it. Literal miles of fiber in those racks.

You do literally pop in an image that is pre-configured in and it deploys to everything at once. That's probably the easiest part of the whole setup.

But in order to get that ROM you need an unlocked bootloader, breaking integrity (best case scenario is device level integrity, you can't get strong anymore). Google RCS will sort of work if you can pass Device, but in my experience things break silently if you don't pass Strong (massively delayed messages, messages not sending, and RCS randomly disabling for no reason at all in the middle of a conversation).