You can accomplish that by using BTRFS or LVM. Years ago (on the Debian forum) I mentioned that I would use such an approach if I ever decided to run Debian Sid.

Are you using Daedalus or an earlier version of Devuan?

I did a search on DuckDuckGo for "icecat 102.11.0esr" (no quotes) and found this:

“Version 102.11.0, first offered to ESR channel users on May 9, 2023”

Firefox ESR Release Notes
https://www.firefox.com/en-US/firefox/102.11.0/releasenotes/

Which version of Icecat are you using?

I believe that the real reason is because VirtualBox is not compatible with the way that Debian prefers to do things. Oracle wants people to use the latest version of VirtualBox rather than the Debian way, which is to apply patches to an older version of VirtualBox.

Please reply with the output of this command:

$ whereis connman

That seems a bit odd. Try this and reply with the results:

$ nslookup sledjhamr.org

$ nslookup sledjhamr.org 1.1.1.1

A university instructor once told me (I'm paraphrasing here) that, although C is very powerful, it also gives you enough rope to hang yourself. He was teaching a course on programming for Apple Macintosh computers, and the language he recommended for that purpose was Pascal. Some students, though, insisted on using C, and that was permitted. However, the students using C tended to have a lot more problems debugging their programs than the ones using Pascal.

The poor performance of QEMU is why I switched to VirtualBox years ago, despite all the criticism of VirtualBox that I came across. Even though people were claiming that QEMU is faster than VirtualBox, in my experience it was the exact opposite.

I started using QEMU again about three years ago. Its performance still seems a bit slow, but it's acceptable for the Linux guest VMs that I've used it for. I wish I knew how to tweak it for better performance, though.

Thanks for all the suggestions. Since I was able to return the Lexar drives for a full refund, I decided to do that instead of spending any more time on them. Frankly, if filling the flash drive using f3write was enough to kill it (if that's what did it), then that drive isn't trustworthy enough to use for any important purpose. Based on my experience, and the fact that there are multiple reviews stating that the purchaser received a drive that was DOA, or died after a relatively short period of time, I no longer trust this brand. I will probably be replacing these with a pack of USB flash drives from Micro Center.

I did that last night. Fortunately, I didn't see anything suspicious. Mostly just lots of zeroes.

The slower Lexar JumpDrive definitely seems flaky. This morning I ran fdisk -l /dev/sdb to give it a quick look and got "Permission denied". So I tried again as root and it still didn't work. Then I tried sudo wipefs --all /dev/sdb, and that got things working again. Even so, this doesn't seem like a good sign. I have strong suspicion that this drive is going to be unreliable or end up dying early. I still have time (a few days) to return the drives for replacement or a refund, so maybe I should go ahead and do that.

Yes.

The 128 GB flash drive is a Silicon Power Blaze B02, and the 32 GB flash drive is a Lexar JumpDrive V100. By the way, the Lexar drive came in a pack of three, and one of the three is clearly defective (much slower than the other two).