rtxn

But did we really have to take such a long break on the way to the mortuary?

Having a consistent definition of "woke" is too woke for some fossils.

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.

It's the other way around. Parallel capacitors boost capacitance to the sum of the individuals. It's like increasing the plates' area. Serial connected capacitors do the reverse: decreased capacitance with greater breakdown voltage, like the dielectric's thickness is increased.

Cool Retro Term has finally added hardware support. They even included the vertical wrap-around when a capacitor is about to pop!

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.

kill automatically sends SIGTERM (15) if no other signal is specified. It's the gentle way to terminate a process.