376 karma · joined April 3, 2024
I know, it's bogus, but this is their explanation.
also: source?
Hygiene, folks.
Also could be the fact that the entire reason OpenBSD exists is that De Raadt got cancelled out of NetBSD: http://mail-index.netbsd.org/netbsd-users/1994/12/23/0000.ht...
That's a bug not a feature.
Every language these days is trying to force you to use its own badly-implemented imitation of Nix. Just look at what cargo does with the target/ directory and wonky "build fingerprints".
It's madness.
The fundamental difference with Guix is that evaluation (what they call "host code" -- everything that happens BEFORE the .drv is written) is wildly impure.
Guile code can access the network, write to the filesystem, heck it can even pull bytes from /dev/random. It can delete your home directory or email your ssh private keys to Zimbabwe.
The Nix language, by contrast, is incredibly restricted in order to make evaluation a deterministic function of the .nix source code you give it, things whose cryptographic hash is in the .nix source code, and nothing else. There is an --impure flag which lets it read from (but not write to) the filesystem but nixpkgs does not use that.
That is a pretty big rift that I find myself unable to cross. I can eval Nix code from any random bozo on the interwebs without having to trust them. If I trust the nix sandbox (which I mostly do) I can even build the resulting drv. I can be sure that evaluating that Nix code will produce exactly the same drv two years from now that it did today. Guix doesn't offer those things. Because scheme. I'm sorry but scheme just isn't the right language for this, it's too powerful.
When the atom ejects an electron, the hole left behind gets filled by an electron from a neighboring atom. Then the same thing happens to the neighbor -- and so on. This is electrical current flowing. Eventually the loop closes and some hole somewhere in the universe gets filled by the original ejected electron.
The hole in one atom can get filled by an electron from a higher orbital in a neighboring atom. In that case the energy gained will be greater than the energy lost by the original electron ejection. This is the situation where you get a photon (x-ray) with a higher energy (= shorter wavelength) than the original incident photon (ultraviolet).
Of course there's no free lunch. The way this happens is that N thorium atoms eject electrons from some orbital with energy X, the electrons shuffle around, and those N holes get filled by donors from orbitals whose total energy is N*X even though some of the donors are at higher levels and some are at lower levels.
If one could make the UV source highly efficient perhaps it could be used as a battery with extremely good energy density.
Yeah I've been thinking that if we had really tiny VLSI-integrated UV lasers (which we absolutely don't, not even close) that a bunch of these 229Th atoms embedded in a silicon chip would be a device with totally fascinating properties.
We can build waveguides in silicon wafer processes pretty easily but I'm not sure we can do that at UV wavelengths. You could imagine a single, big, off-chip laser whose beam can be steered by waveguides to illuminate any of a few billion 229Th deposits. These could act like the configuration memory bits of an FPGA. They would be "almost nonvolatile" -- you'd have to refresh them every hour or so, instead of several thousand times per second (dram) or never (sram). At such a low refresh rate the steering doesn't need to be particularly fast, and having to share one laser across all the deposits would not be a problem.
Unfortunately 229Th is mildly radioactive, but so are household smoke detectors so hopefully people wouldn't freak out about this.
What you can't do is deny others the same freedoms the license grants to you.
It's almost like this page is part of the web from some parallel universe, which has been disenshittified to the same extent that our own web has been... well, you know.
Apparently it is neither:
Decay of the 229Th isomeric state of the neutral thorium atom occurs predominantly by internal conversion (IC) with emission of an electron
https://www.nature.com/articles/nature17669
https://en.wikipedia.org/wiki/Internal_conversion
This is pretty weird. You shine UV light (with exactly the right wavelength) on 229Th, and it spits out electrons. But not like the photoelectric effect, where the electrons stop as soon as you turn off the light. No no. The Thorium keeps spitting out an exponentially-decaying stream of electrons for hours after you stop illuminating it.
Almost like an exponentially-discharging solar-powered current source (for a very specific wavelength of "solar").
The development of dedicated VUV lasers with narrow linewidth will make it possible to access a new regime of resolution and accuracy in laser M¨ossbauer spectroscopy and to perform coherent control of a nuclear excitation"
Previously, if you wanted to manipulate nuclear states, you needed a synchrotron. Now, you need an infinitely less expensive instrument. I suppose the idea is that that will generate a lot of interest in improving the less-expensive instrument.
https://bertoldi.seas.harvard.edu/publications/shell-bucklin...
Note that this is not "gripper" like "five-fingered robot hand". A better description might be "vise" (like the kind in a woodworking shop). The egg gets pressed between two linear actuators each with one degree of freedom.
For 1gbit: Ubiquiti Edgerouter ER-4 and ER-6; both have SFP cages for fiber optic transcievers https://github.com/NixOS/nixpkgs/pull/194153 https://store.ui.com/us/en/products/er-4
revs chainsaw
Single-mode fiber is future-proof. Utilities bury that stuff and depreciate it over a 30-year lifetime. There has been like one spec change since the 1970s.
Single-mode fiber. Always single-mode fiber. Nothing else, ever.
https://ipng.ch/s/articles/2023/11/11/mellanox-sn2700.html
The cable has a SAS (SFF-8087) connector on each end. I bet you can replace it with an SFF-8087-to-Oculink cable:
https://www.amazon.com/chenyang-SFF-8611-SFF-8087-PCI-Expres...
and a PCIe-to-oculink card like one of these:
https://www.amazon.com/Ableconn-PEX-OL153-OCuLink-SFF-8612-A...
(none of the links are affiliate links)
If you really want software switching you have to use the management port (there's only one or two of these) whose name is "eth0" or "eth1" or something like that. So avoiding "accidental software switching" is really easy -- if you're typing "eth" you're doing it wrong. You can even explicitly delete this interface if you don't need the CPU to be able to snoop/inject traffic to/from the switch ports.
The answer is "switchdev":
https://www.kernel.org/doc/html/latest/networking/switchdev....
The Linux switchdev driver is the awesome magic that says "make hardware-offloaded switching ASICs look just like software switching". It's beautiful and amazing, as you'd expect from Mellanox.
https://www.kernel.org/doc/html/latest/networking/switchdev....
https://github.com/dentproject/dentOS
Switchdev support means you don't need hardware-specific userspace tools (with their own bizarre syntax to learn) in order to configure the switch.
DentOS support means the device uses a sane bootloader (uboot or grub) and the only binary blobs on the device will be the ones built into the bootloader (IntelME, Arm Trusted Firmware) and the switch firmware which will be part of linux-firmware (and therefore very easy to manage/update).
In particular, looking for these two keywords is how you make sure that the hardware vendor is staying on "their side of the line" between hardware and software. Violations of this line are endemic to 10G+ switching.
Powered by what?
Solar panels in a place where the sun doesn't even rise for months at a time? That big beefy transmission grid that the Antarctic continent is so famous for? The jillions of oil wells already drilled into the Antarctic?
Oh wait, I know: penguin guano.
Pass the crack pipe, you've had enough my friend.
_ _ __ _ _ _
(_)_ _ ___| |_ _ _ ___ ___ / _(_) __ _| | ___| |_
| | | | / __| __| | | | / __|/ _ \ | |_| |/ _` | |/ _ \ __|
| | |_| \__ \ |_ | |_| \__ \ __/ | _| | (_| | | __/ |_
_/ |\__,_|___/\__| \__,_|___/\___| |_| |_|\__, |_|\___|\__|
|__/ |___/
https://repology.org/project/figlet/versionsUnderstatement of the year.
Ever heard of SSL MITM Proxy? Required by law (and corporate compliance departments) in many industries.
Also, cloudflare. They are the MITM for what, like 80% of the internet now?