Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Duplicator mode #182

Open
cassidyjames opened this issue Jun 16, 2022 · 4 comments
Open

Duplicator mode #182

cassidyjames opened this issue Jun 16, 2022 · 4 comments

Comments

@cassidyjames
Copy link
Contributor

We're using Popsicle at the Endless OS Foundation to make copies of drives used to install Flatpak'd learning apps in offline or limited connectivity deployments. Currently, our process looks like:

  1. Use flatpak create-usb to prepare one USB drive, which takes a lot of time due to downloading all the apps and dependencies, compressing them, and writing them to the drive.
  2. Create an .img of that drive
  3. Use Popsicle to copy that .img to several additional drives

It could be handy to use Popsicle more like a disk duplicator, where it could read the contents of one drive and copy them bit-for-bit to additional drives, cutting out that middle step.

@ids1024
Copy link
Member

ids1024 commented Jun 16, 2022

This could be useful. Though in this particular case it sounds like it would be better if flatpak create-usb had support for outputting an image file?

@cassidyjames
Copy link
Contributor Author

cassidyjames commented Jun 16, 2022

Ooh, that's not a bad idea as well. Though I could see the duplicator mode being useful in other contexts, like when we copy drives that are used in the laptop provisioning process or with other, not-only-Flatpak content.

Actually, in this case another example is that we're including a document on the root of the drive (I guess that would be step 1a) as well. :)

@ids1024
Copy link
Member

ids1024 commented Jun 16, 2022

Yep, there are other uses for a duplicator mode.

@ids1024
Copy link
Member

ids1024 commented Jun 16, 2022

I guess this would require that the USB drive being cloned is no larger than the ones it is cloned onto, and the full size will be copied even if the used portion is smaller?

It could perhaps detect a partition table smaller than the drive, but that would probably only happen when it was flashed from an image.

Other than that, reading from a drive instead of an image should be straightforward, so I think other than a few smaller details, this would mostly be a matter of designing and implementing a good UI for the feature.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants