Meanwhile Yoko Taro: “I like big butts and I cannot lie”

Linguists now agree that the word “copium” was coined in ancient Rome.

This artist just happens to use a distinctive watercolor style.

The artist is bbmasa on Pixiv: https://www.pixiv.net/en/users/27414306

Slightly NSFW, some cartoon nudity but nothing explicit.

America is a different universe, I swear.

I’m not questioning the findings. I’m questioning the article, and your interpretation to arrive at such a summary.

APL plans to continue to partner with organizations to refine the CHESS thermoelectric materials with a focus on boosting efficiency to approach that of conventional mechanical systems

energy-harvesting technologies for applications ranging from computers to spacecraft

70% improvement in efficiency in a fully integrated refrigeration system.

It’s all potential, and possibilities, and future projections. I’m sure someone will find real world applications for it, but a fridge tacked out with Peltier tiles that draws energy from its ambient environment (while actively ruining the thermal gradient by the way) is ludicrous.

I’m calling bullshit. There’s no way a Peltier element can exceed the coefficient of performance of the refrigeration cycle, at an affordable price, without turning the room into a hothouse.

No.

The local machine boots using PXE. Clonezilla itself is transferred from a TFTP server as a squashfs and loaded into memory. When that OS boots, it mounts a network share using CIFS that contains the image to be installed. All of the local SATA disks are named sda, sdb, etc. A script determines which SATA disk is the correct one (must be non-rotational, must be a specific size and type), deletes every SCSI device (which includes ATA devices too), then mounts only the chosen disk to make sure it’s named sda.

Clonezilla will not allow an image cloned from a device named sda to be written to a device with a different name – this is why I had to make sure that sda is always the correct SSD.

There was no need to physically disconnect anything. We didn’t actually use any SCSI devices, but Linux (and in turn, the Debian-based Clonezilla) uses the SCSI kernel driver for all ATA devices, so SATA SSDs also appeared as SCSI hosts and could be handled as such. If I had to manually unplug and reconnect hundreds of physical cables, I’d send my resignation directly to my boss’ printer.

I presume you have had to run on RAM, considering you removed all drives

Yes. Mass deployment using Clonezilla in an extremely heterogenous environment. I had to make sure the OS got installed on the correct SSD, and that it was always named sda, otherwise Clonezilla would shit itself. The solution is a hack held together by spit and my own stubbornness, but it works.

Only if you’re working with SCSI hardware. On Linux, SATA (and probably PATA) devices use the same kernel driver as SCSI, and appear on the system as SCSI hosts. You can find them in /sys/class/scsi_disk or by running lsblk -o NAME,HCTL.

Broke: /dev/sd*
Woke: /dev/disk/by-id/*
Bespoke: finding the correct device’s SCSI host, detaching everything, then reattaching only the one host to make sure it’s always /dev/sda. (edit) In software. SATA devices also show up as SCSI hosts because they use the same kernel driver.

I’ve had to use all three methods. Fucking around in /sys feels like I’m wielding a power stolen from the gods.

And who’s going to thank you for getting ground down to the bone doing a job you hate? Loyalty is a lie.

One of the less lunatic posts here. Beyond what’s required by law and by contract, neither party owes the other shit… which is to say, from the perspective of living in a place that has the luxury of real worker protection laws and rights, Americans are kinda boned.

“Fuck around and find out”?

Calm the fuck down. This wasn’t a “Russian lathe accident” situation. We were trained professionals, and never left the machines unattended in an unsafe state. There were no injuries and only that one close call (which IIRC was traced back to a faulty e-stop button).

We never fell victim to complacency and I am quite proud of that.

They can’t even give a satisfactory answer to whether lawyers would be able to uphold confidentiality while using their tools. The obvious answer is no, they just don’t want to say it. What a fucking clown car.

Sometimes for maintenance, sometimes because manual intervention was necessary. The machines where we did this were built in the 90s and have been in near constant operation. Moving parts are worn out and the tolerances are gone. Replacement parts are difficult to find and expensive to manufacture, so if something more complex than a ball bearing or axle got out of alignment, we had to pound it back into place (sometimes literally).

I personally never bypassed the interlock, I wasn’t paid enough to take on that responsibility. I would just file a downtime notice and call the on-site mechanic when needed. I didn’t give a shit about reduced output.

Tagging @[email protected]

We used to routinely disable safety interlocks on production machines. A guy almost got decapitated once while performing maintenance.

That’s wishful thinking. Users don’t give a shit as long as the problem goes away without having to lift a finger.