philkrylov

With ZFS support in NetBSD, I would expect one would use ZFS for bigger storage situations, keeping RAIDframe for special cases (e.g. boot/root)

bash, zsh, and ksh93 support `exec -a` especially for this case.

Hi, thanks for your project! Do you accept pull requests? https://github.com/simonw/datasette/pull/2616 https://github.com/simonw/datasette/pull/2617

Hi, adding WS2812B LED strips of arbitrary length would be awesome! Scrolling the canvas is sometimes problematic. Otherwise very interesting.

Hi, I am still blocked with "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:109.0) Gecko/20100101 Firefox/115.0"

hrx looks much better, as txtar can't include, e.g., other txtar files

The main problem with them is they are not working yet and there are not enough people working on improving that.

The link shows a list of firmwares. The actual sources are at https://github.com/Freetz-NG/freetz-ng - but it's not the original FritzBox firmware sources:

> Freetz is a toolbox for developers and experienced users to build a modified firmware based on the original firmware for the DSL/LAN/WLAN/VoIP-Routers AVM Fritz!Box and T-Com Speedport (identical hardware) and to transfer this firmware to the device. There are many extension packages available, along with options to remove unwanted functionality from the original firmware.

> for (int i = 0; i < strlen (str); i++) {...}

> A modern compiler will optimize this redundancy away

No, it won't: https://godbolt.org/z/xbzz4cEq3

> yes, ZFS can be configured to use a WAL too for durability

ZFS always uses ZIL for sync writes. You can optionally set `sync=disabled` for a dataset to switch it off. I would not describe it as "can be configured to use WAL".

Only with GNU su. A portable though limited replacement would be something like

    alias sudo="su root -c"

The heredoc in the script is never terminated. Probably it's not the production version but one for publishing ;-)

Actually, using DEBUG for creating anything besides one or two simple DOS/BIOS calls was a PITA due to the lack of symbolic labels. After that, the MASM/TASM boilerplate started to feel bearable.

The article suggests using NFC normalization as a simple solution, but fails to mention that HFS+ always does NFD normalization to file names, and APFS kinda does not but some layer above it actually does (https://eclecticlight.co/2021/05/08/explainer-unicode-normal...), and ZFS has this behavior controlled by a dataset-level option. I don't see how applying its suggestion literally (just normalize to NFC before saving) can work.

Looking at your search results, there's just one recent ZFS corruption case with SEEK_DATA/SEEK_HOLE (in several HN reflections), a 2-year old Ubuntu-only buggy patch story, and some 2008 [Open]Solaris corruption.

PostgreSQL does not use SEEK_DATA/SEEK_HOLE so they're ok

Although being faster in some cases, ripgrep lacks archive search support (no, transparent decompression ignoring the archive structure is not enough) which works great in ugrep.

just 4 CGA colors, to be exact

Right. At least for some time...

> the cost, besides having to actually create the file systems, is that moving data between them isn't instant.

No more the case after block cloning support goes production: https://github.com/openzfs/zfs/pull/13392

Soltek SL-75KAV was the first motherboard I've bought on my first salary! Was working great for 5 years or so before getting heavily outdated.

It is not, at least on FreeBSD and NetBSD.

At least error reporting has been improved recently: https://nim-lang.org/blog/2023/03/31/version-20-rc2.html

Some typedefs were promoted to 64-bit but it's the same Win32 API, even the name has not changed

openzfsonosx is a ZoL/OpenZFS2 fork. NetBSD ZFS is a fork of FreeBSD 10 ZFS.

NetBSD has a root-on-ZFS recipe only for amd64.

Tow-Boot SPI installer reports something like this for me:

Expected board: 'pine64-pinebookPro'

Found board: ''

thanks!

Check (GNU Make) .RECIPEPREFIX, (GNU Make) .ONESHELL, (POSIX Make) SHELL=