• 0 Posts
  • 42 Comments
Joined 1 year ago
cake
Cake day: June 8th, 2023

help-circle

  • It sounds like nobody actually understood what you want.

    You have a non-ZFS boot drive, and a big ZFS pool, and you want to save an image of the boot drive to the pool, as a backup for the boot drive.

    I guess you don’t want to image the drive while booted off it, because that could produce an image that isn’t fully self-consistent. So then the problem is getting at the pool from something other than the system you have.

    I think what you need to do is find something else you can boot that supports ZFS. I think the Ubuntu live images will do it. If not, you can try something like re-installing the setup you have, but onto a USB drive.

    Then you have to boot to that and zfs import your pool. ZFS is pretty smart so it should just auto-detect the pool structure and where it wants to be mounted, and you can mount it. Don’t do a ZFS feature upgrade on the pool though, or the other system might not understand it. It’s also possible your live kernel might not have a new enough ZFS to understand the features your pool uses, and you might need to find a newer one.

    Then once the pool is mounted you should be able to dd your boot drive block device to a file on the pool.

    If you can’t get this to work, you can try using a non-ZFS-speaking live Linux and dding your image to somewhere on the network big enough to hold it, which you may or may not have, and then booting the system and copying back from there to the pool.





  • Plastic at the microscopic level, if they aren’t doing anything chemically interesting, really ought to function about like “rock, but light”. Most organisms don’t run into trouble because there are tiny bits of rock in the world, so I would expect tiny bits of plastic not to be a huge problem. Which is sort of backed up by how we have noticed microplastics everywhere and we haven’t seen huge problems resulting from it (most people are still alive, most children still develop to adulthood, etc.).

    But it’s entirely possible that some of these plastics are not chemically inert, and that they emit chemicals that do exciting and unwanted things in people’s bodies. If we can’t keep our plastics from becoming microplastics, we probably need to discontinue the manufacture of non-implantable plastics, since all the plastics will end up in someone’s body at some point.

    And it’s also possible that the microplastics physically do do something interestingly bad. I think there was a recent study to this effect on heart disease. But at this point, that’s the question we need to be asking. How many or what kind of microplastics does it take to give a ferret epilepsy? Not “are there microplastics in my all brands of peanut butter?”







  • I think you can keep doing the SMB shares and use an overlay filesystem on top of those to basically stack them on top of each other, so that server1/dir1/file1.txt and server2/dir1/file2.txt and server3/dir1/file3.txt all show up in the same folder. I’m not sure how happy that is when one of the servers just isn’t there though.

    Other than that you probably need some kind of fancy FUSE application to fake a filesystem that works the way you want. Maybe some kind of FUES-over-Git-Annex system exists that could do it already?

    I wouldn’t really recommend IPFS for this. It’s tough to get it to actually fetch the blocks promptly for files unless you manually convince it to connect to the machine that has them. It doesn’t really solve the shared-drive problem as far as I know (you’d have like several IPNS paths to juggle for the different libraries, and you’d have to have a way to update them when new files were added). Also it won’t do any encryption or privacy: anyone who has seen the same file that you have, and has the IPFS hash of it, will be able to convince you to distribute the file to them (whether you have a license to do so or not).







  • It really does though. Someone controls the project and decides what’s in or out. Other people engineer around that project, and the current latest version of that project becomes a de facto standard.

    So you can either use that and let the people who control the project be in charge, or you can find enough developer time to maintain 99% compatibility as the de facto standard project changes stuff and the ecosystem you need to use follows.