Wir haben Grund zum saufen!

OpenWRT does not use liblzma or systemd so i think that one is pretty safe. I would also be surprised if Android included OpenSSH server binaries in that way.

https://theculturetrip.com/europe/germany/articles/11-german-places-with-incredible-and-hilarious-names

Not as long as OPs but has some real goodies.

downvote for lack of feathers. smh.

this is extra tricky because they did not specify the exact kernel. mainline could be any of the kernels tagged as stable that you can build from linus’ git tree. i know that in the past you could run a mainline linux on intel 368 chips but today you probably can not because official support was dropped a while ago.

datasheet for one of the drive models apparently these have a dual SAS interface, so what you are seing could be completely normal. i dont have any experience with this type of setup though.

btw you can uniquely identify partitions by using something like lsblk -o+PARTUUID,FSTYPE the partuuid should never repeat in the output even if the partition table was somehow used as a template (though "dd"ing from disk to disk will duplicate those of course)

also check out the “SERIAL” column for lsblk to uniquely identify the drives themselves.

most dishwasher detergent formulations contain corrosion inhibitors for steel, some even contain corrosion inhibitors for aluminium though those are usually in the upper price segment.

could you run something like sudo lsblk -o+MODEL and note down the model for the drives? i kind of suspect that the HBA you are using is still doing some abstraction and is not in IT mode. the duplication could come from connecting two SAS cables to the same backplane, thus creating a sort of double image of the enclosure. this is usually handled and hidden by the HBA though if it is configured correctly.

pls also check that you are in fact using the correct ports on the enclosure. if you are not building a SAN only the “A” ports are supposed to be used and the “B” ports should be unused/free.

just a bunch of individuals drives

that is literally what JBOD means so congratulations you already have one. a classical RAID would show up as a single drive.

Initiator-target (IT) mode enables creating a JBOD with zfs vdevs on it. You can have the zfs vdevs in raidz configuration (which would give you the same drive redundancy as a hardware raid, with raidz1 performing similar to RAID5)

zfs is commonly used with a JBOD configuration on a raid controller but you can also use any other kind of controller as long as the individual drives can be written to. examples for this would be NVMe drives directly attached to the PCIe bus or normal SATA controllers. This is more a performance optimization than an issue with compatibility.

In the Netherlands you can legally buy grow kits for magic mushrooms. They are fairly easy to use, mostly just weekly/daily checks to keep moisture at the right level and making sure to harvest at the right times (you usually get multiple harvests from just one kit).

Personally i think doing a shroom trip alone is too dangerous … so maybe find a group first?

Will it also allow the placement of entities to be parametrically changed? like the changing the position or enabling/disabling the placement of specific entities?