riobard

No no definitely not that… it's more like "my stuff is a bit weird"

I don't know if it's common but for me ":p" is basically the text version of this emoji

[edit]: oops HN does not allow emoji … go here https://emojipedia.org/winking-face-with-tongue

Yeah I have this setup too just in case :p

I didn't use the ATX aux board because my mini PC does not have such headers. I just use Wake-on-LAN from NanoKVM web UI to power up my PC :P

I'm playing with one now (the full kit) attached to my toy mini PC. It's a little RISC-V device consuming a couple watts. No WiFi yet, but it attaches to PC and emulates 4 things in addition to capturing HDMI output to a web UI:

1. A USB keyboard.

2. A USB mouse.

3. A USB flash drive (using a partition on its internal SD card) for storing bootable ISO to install/rescure systems.

4. A USB NIC which is very neat. I can use it on the PC to expose management SSH port just on that instead of the primary NIC, so that the PC has a sorta dedicated IPMI interface.

Newer versions of the device software come with WireGuard and Tailscale support, so I can just connect to it over VPN.

Still have some minor issues, but the developers are working fast to fix them.

There's one gotcha tho.

For Dynamic DNS you want minimal TTL, ideally less than 60 seconds, otherwise the DNS records will be cached and will not reflect the correct address during the short period of time window it changes.

Dedicated DDNS services usually have very short TTL (some offering as low as 5 seconds IIRC), but free Cloudflare accounts have a minimal TTL of 300 seconds (5 minutes), coupled with the crontab running every 5 minutes, your endpoint could be out of contact for 10 minutes if everything aligns right.

I never understand the reasoning behind the design decision that SRV cannot just return IP address and forcing clients to query again for A/AAAA again. That decision forces an extra RTT before connection can be established, which makes people want to avoid SRV records. Totally self-inflicted wounds.

Is it possible for SSD firmware to act “progressively” from SLC to MLC to TLC and to QLC (and maybe PLC in the future)? E.g. for a 1TB QLC SSD, it would act as SLC for usage under 256GB, then MLC under 512GB, then TLC under 768GB, and then QLC under 1TB (and PLC under 1280GB).

What about reducing interference? Optics would be better right?

SystemD has this nice feature called DynamicUser, making it much more pleasant to deal with unprivileged user and nasty ID.

Reputable SLC SSD is almost impossible to find nowadays, I’ve always wondered why we can’t turn a large capacity TLC/QLC SSD into 1/3 or 1/4 capacity SLC SSD for use cases like ZFS SLOG or other kind of cache devices. Turns out it’s possible after all!

Please SSD manufacturers: make it official!

Thanks but the STH video you linked is talking about new "ruler" form factors for SSDs and accelerator cards. I was wondering if anyone actually used the 3.5" HDD with U.2/NVMe connector.

Does anyone know what's going on with those U.2 NVMe hard disk drives? (see https://blog.seagate.com/enterprises/seagate-unveils-worlds-...)

I'm asking coz the OP mentioned the need for a PCIe-to-SATA bridge chip to have more than a couple of SATA ports. I'd assume that if HDD were also NVMe devices, it will be simpler to just wire each PCIe lane to a drive, without requiring any bridges. A PCIe 2.0 x1 lane is 500MB/s, on par with SATA III 6Gbps.

> eHDD standards (and devices) that allow you to plainly read the SATA data from the drive, merely acting as a transport for the SATA connector itself

I'm a bit confused, but isn't eSATA exactly what you are looking for?

It’s literally called eSATA.

Yes I did run `sensors-detect` previously and just to be sure ran it again. No voltage sensors on this box unfortunately :(

Ran `sensors` and it only shows CPU core temps. I guess my MB does not report RTC battery voltage?

Cannot do that if it acts as the always-on router…

Somehow I feel reliability might take a hit… :|

Yes, this is very annoying.

Speaking of RTC battery, I've recently come to the realization that I have to make sure that BIOS battery is not absolutely dead in always-on PC boxes.

Background: I use an x86 box as home router. I've changed the configuration in the BIOS that it should automatically boot up on power. However if the BIOS battery is dead, the config will be lost and it will revert to default settings, which is not to boot on power.

But there is no way to know how much juice is left in the BIOS battery, thus there is no way to issue warnings that the battery should be replaced soon. If there is power loss AND the battery is dead, when the power comes back up again, the router will just stay off indefinitely until it's manually turned on.

That's when I realized why most consumer routers do not feature RTC nor do they require batteries.

Nay I'm just refuting the idea that performance is the utmost, singular goal, as is pointed out by vlovich123 4-levels up in the thread https://news.ycombinator.com/item?id=39785690

Modern storage hierarchy has become so convoluted precisely because of many conflicting goals: performance, efficiency, durability, cost, etc.

Not doing anything saves power and NAND cycles.

Disk also might be in standby mode, which saves motor spin up and head load cycles too.

I wonder… wouldn't a physically disconnected ethernet cable work as well?

Fillipo said here (https://abyssdomain.expert/@filippo/111393097818470743)

> It is IMHO the strongest security guarantee you can offer without forcing each module author to manage keys.

Outsourcing the problem to DNS still forces module authors to manage keys. Not keys to sign code, but keys to sign TLS certs nonetheless. Granted, authors can further delegate managing TLS keys to other people, but you cannot escape the ultimate issue of managing control of the domain (passwords at registries at least).

If we cannot get rid of key management anyway, can we split the problem into 1) Code Signing and 2) Code Distribution? Once we get the Code Signing done right, Code Distribution will be much easier with robust solutions (e.g. content addressable storage and various kinds of proxies/caches for high availability).

Now code signing, lots of schools of thoughts… On the extreme end of decentralization, PGP/GPG people will say Web of Trust and Crypto/web3 people will say hardware wallets; while on the other end of centralization we seem to be getting by just fine with publishing public keys on GitHub and various social networks. Just pick a place where you Feel Good Enough™ :p

I was wondering if Amazon, instead of wasting money and time on Fire phones/tablets, had poured a portion of that resource into making native Kindle apps a thing, maybe it could have a more compelling ecosystem by now.

Nonce could be an implicit counter in which case it's not transmitted.

I think the puzzle essentially boils down to: what does it mean by "natively run application code"?

Mostly because geofencing is getting much more widespread for various legit reasons (security, anti spam, licensing restrictions, etc) and very annoying for end users.

A few days ago I accidentally put wife's beloved Bialetti Brikka pot in the dishwasher. The aluminium lost its anodized coating due to chemical reaction with the detergent (alkaline I think), and the pot turned dull/dark gray. Scrubbing the surface left some gray mark on fingers, which got me wonder if aluminium is actually safe for making coffee? Bialetti also sells stainless steel pots, and I wonder if they're safer to use.