Points 0 and 1: None of this is new. This goes back to 2011 or 2012.
Point 2: If someone gets hold of your phone and unlocks it (meaning, they can interact with it), they have access to your Signal messages on-board. This is why additional security measures (not using biometrics, encrypting your phone natively) are recommended. If your phone is off and someone dumps the data from it, they get encrypted data.
If you're going self-hosted with your stuff, have you consider a bookmarking webapp like Shaarli? You can even export your bookmarks from your browser and import them.
In a journalistic context, a ZKP can't prove veracity of the information.
Let's say you have a hoax that you want to pull on a journo. You cook up something that looks legit, like the blueprints for a super secret stealth fighter or something. You find a way to apply a ZKP to that file (let's say an elaborate cryptographic hash). You leak the file to the journo. They ask for you to iterate on the ZKP a few hundred thousand times (which is on the low side for a ZKP) - easy to do, because you came up with it.
But that doesn't mean the file's legit. That's a separate problem, and not one that is technological in nature.
You might want to start by rebalancing by percentages and not all at once. If nothing else it'll tell you much sooner if you're on the right track or not. Something like sudo btrfs balance start -dusage=20 -musage=20 /mnt/disk3 to work on only blocks that are 20% full or less. That should coaleace them into single data blocks and free up some others.
There has to be a way of getting FreeDOS onto the SD card. Way back when, there used to be ways of getting a floppy disk (and hard drive, I did it a few times) bootable with the SYS command to write the boot files to the right places. That was MS-DOS, though.
Please note that I haven't actually tried any of this. I'm at work and trying to pull together what scraps of knowledge I still have from my DOS days into something that seems coherent. This might not work, so please treat it as kicking some ideas around over coffee right now!
ms-sys basically does the same thing that format /s and sys a: used to do back in the days of DOS. That makes a drive bootable. So, you'd partition and format your SD card as VFAT or FAT32 from your box (I don't know if you have a Linux box or a Windows machine, or what). I'm guessing it'd be something like this:
sudo fdisk /dev/mmcblk0
# New DOS disk label
o
# New partition.
n
p
1
t
c
a
1
w
Format the partition on the SD card:
sudo mkfs.vfat -c -v -F32 /dev/mmcblk0p1
Then use ms-sys to write the MBR to the SD card.
sudo ms-sys --mbrdos /dev/mmcblk0p1
Mount the SD card. Download FreeDOS and uncompress it. I think that would be FD13-FullUSB.zip. There doesn't seem to be a downloadable archive of "Here's all the stuff that's in the disk image," just the disk image. Some gymnastics do seem to be required to mount it:
sudo losetup /dev/loop0 FD13FULL.img
sudo fdisk -l /dev/loop0
Disk /dev/loop0: 512 MiB, 536870912 bytes, 1048576 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000
Device Boot Start End Sectors Size Id Type
/dev/loop0p1 * 63 1048319 1048257 511.8M e W95 FAT16 (LBA)
The gymnastics in question have to do with mounting a partition of the disk image, because you can't just set up the disk image and manipulate it like a disk device. In this case, it's calculating where to mount the FreeDOS partition: sector size * first sector == 512 * 63 == 32256
From there, it looks like you'll have to look at /mnt/setup.bat to figure out how to do a manual setup of FreeDOS on the SD card. There is also a /mnt/FDOS-x86/SETUP.BAT file that I think will have to be read through to get the process figured out.
Again, this is all theoretical. I've no idea if it'll work without tinkering with it on real hardware. It's as close to figuring out how to do a manual installation as I have time for right now.
Have you tried a smaller card? 32GB was pretty well unheard of, even in the DOS 6.22 days.
It's been a very long time since I've thought about stuff like this. It reminds me of when I was trying to get a 1GB drive working on a 486 when I was in college. The drive wasn't seen (just like you're seeing). What I had to do was install the manufacturer's backwards compatibility software (it was for systems that were too old to have BIOSes that recognized drives that big) so that the BIOS, when it probed the hard drive would somehow load a TSR that added support for large hard drives.
Looking up the card in question, it loads the XTIDE BIOS, and the card has "Select XT-CF(PIO) Mode/Base IO 300h" silkscreened on the back. Zooming in on the front of the card, it doesn't look like you can set that on the DIP switch block for some reason. I don't see any documentation for download from the site. Did any docs come with the card?
The Doctor @ drwho @beehaw.org Posts 0Comments 944Joined 2 yr. ago
They start with Mac clients because those devs use Macs.