Yes, the decryption happens in hardware. For your OS (and potential capturing software running on it) the place where you see the video is just an empty canvas on which the hardware renders the decrypted image.
I think the noise emissions of a successful launch already make it an unattractive and potentially hazardous (for your hearing) place to live, especially considering SpaceX' launch frequency.
Unfortunately not. I can't say for current gen, but the 5000 series APUs like the 5600G do not support ECC. I know, I tried...
But yes, most Ryzen CPUs do have ECC functionality, and have had it since the 1000 series, even if not officially supported. Official support for ECC is only on Ryzen PRO parts.
They have a video where they have an eInk display show video at 60 Hz. In contrast to a previous video, where the display was running at 2.4 Hz and the video then sped up by 10x, this is not sped up. What kind of black magic is this?
> As you'd expect, the embryo was only tiny and measured just 27cm long.
27cm is not exactly what I would call tiny. For comparison, this is what Wikipedia has to say on the topic of ostrich eggs:
> on average they are 15 cm (5.9 in) long, 13 cm (5.1 in) wide, and weigh 1.4 kilograms (3.1 lb)
It's almost twice as long. Talk about megafauna.
Looking for alternative sources, I found this:
> The unhatched dinosaur’s 24-centimetre-long skeleton is curled inside the egg, with its head tucked tightly into its body. The egg is 17 centimetres long and 8 centimetres wide.
Okay, so they were talking about the size of the dinosaur if it stretched out of its curled position inside the egg. The egg meanwhile is a little larger than an ostrich's egg. Still not tiny by any means, but slightly less mindblowing.
The BSDs have diverged significantly since then and not just in userland. Unlike Linux distros they do not all have the same kernel. There are of course common parts in their kernels, many of which date back to Unix, but there are also big differences between all of them.
I was also surprised to see Sailfish OS, Meego and Maemo listed separate from Linux, but my guess would be that the list comes from the build system of curl. Everything that is its own build target is listed there.
I recently used this (via https://depenguin.me/) to install FreeBSD from a Linux Rescue Image on a Hetzner root server. Hetzner sadly discontinued the FreeBSD Rescue Image.
This installation method uses KVM to boot the mfsBSD image, giving the VM the actual hard drives to install on. The one thing that tripped me up was that the network interface presented to the VM did not use the same driver as the physical network interface. So the FreeBSD installation configured (in my case) `em0`, but once I rebooted into FreeBSD, the network interface was `igb0`.
> Surely they can transfer data through water efficiently enough?
Actually, no. Water absorbs most of the electromagnetic spectrum pretty well, severely limiting the communication range. So you're limited to low frequencies or acoustic communication. Both have a low bandwidth, so forget live video footage.
No, there is no defragmentation for ZFS, unfortunately. A way to get around that is to send the pool's content to another (fresh) ZFS pool, where it would be written sequentially. But for that you would need a set of drives of same (or larger) capacity.
There are ideas on how one would do an actual defrag. They are generally based on a concept called block pointer rewrite, which Matt Ahrens once said could be the 'last feature ever implemented in ZFS', as it would make everything so much more complicated, that it would be hard to add new features afterwards [1].
When pointing out that HDDs can outperform these SSDs, 'sequential' is the key word. I regularly pull remote backups with syncoid (i.e. `zfs send | zfs receive`) and over time that fragmented the receiving side considerably. In the end `zpool list` showed over 80% capacity and 40% fragmentation. The hard drives were seeking constantly and the syncoid task would take over eight hours to complete. I replaced the disks with SSDs and now the task completes within 20 minutes.
- a FreeNAS with a bunch of Samba file shares and a Plex. I tried Jellyfin, because I got annoyed with Plex trying to force me to create an account on their cloud stuff, when I just want to use it locally. But the Playstation wouldn't play videos from Jellyfin, so I stuck with Plex.
On a dedicated server with public IP addresses:
- mail (opensmtpd + rspamd + dovecot)
- blog (made with Hugo, a static site generator)
- git (gogs)
- Nextcloud
- XMPP (ejabberd)
- VPN (tinc)
Each of those services is in a separate jail and the jail with the blog has an nginx that serves as a reverse proxy for all http-speaking services.
I'm considering replacing XMPP with Matrix (looking at conduit) and tinc with Wireguard. With the latter I might wait until FreeBSD 14 with in-kernel Wireguard is out.
Not sure what the confidence intervals of these numbers are. For example, the BH14NS40 drive is listed with an accuracy of 99.4937, whereas the WH14NS40 is listed with 98.0869. These are the same model of drive with the black and the white front respectively.
> Getting newer versions of software. Often the version available in pkg is several major versions out of date.
The default settings for pkg use the quarterly branch. Remove the comment from the line for using the latest branch in /usr/local/etc/pkg/repos/FreeBSD.conf.
Adding to the banking data points: I have an Xperia 10 II running Sailfish. MobileBankID and Swish (Sweden) as well as the ING Banking app (Germany) work on it.
I was pleasantly surprised by that. I upgraded from an Xperia X, where Sailfish had the old Android 4.4-compatible runtime and nothing worked. I kept an Android phone around, just for these three apps. As that one was also getting old in terms of OS (Android 7) and security updates, I'm very happy to no longer need it.
I have however come across Android Apps that don't work:
- Betala P (Parking app for Stockholm, no clue why this doesn't work)
- OI.Share (for remote-controlling OM-D cameras. I assume it has to do with it trying to control the WiFi on the phone)
It's what you get support for. At my job we run several third party applications that are targeted at RHEL/RHEL-clones. Sure, they might run on other distros, but if you need the vendors support, you better be running RHEL/CentOS/Alma/Rocky.
I guess it's always a question of perspective. Coming from Germany, there definitely is _more_ of a cycling culture in Sweden than in Germany. The cycling infrastructure is better and better maintained (snow plowing, etc.). Of course that is also a generalization, as the differences can be big within a country as well. (My frame of reference for Sweden is mostly Uppsala)
But the noticeable presence of SUV and even Pickup models I usually associate with the US in Sweden also surprised me. Those are rare in Germany.
Similarly I discovered yesterday that the systemd service definition for auditd includes the `RefuseManualStop` option for this exact reason. When stopping (and thus also when restarting) the service via systemd, auditd is unable to log who shut it down, so it just disallows being stopped. (https://linux-audit.redhat.narkive.com/3weoVaZE/rational-beh...)
The workaround is to use the service command instead. Manually I usually do that anyway, muscle memory etc. But Ansible's service module will default to systemctl if it finds systemd. So there I had to add a "use: service".
Yeah, but DACs are pretty short and tend to have much thicker cables than regular copper Ethernet.