(old)Puppy Linux Discussion Forum

@Keef
I did try just using "dd" but it did not work. I put dd both in /bin and /usr/ bin. I tried a couple of ways of running it in a terminal in the directory in which I placed dd. One was, I think, right click>window>open terminal here then running dd. Another was using cd /bin or cd /usr/bin then running dd. The last was to use the the full path i.e. /bin/dd or /usr/bin/dd. None of these worked and gave no terminal output and I was not sure why. I tried the first method with Barry's ./dd --help and this did work as it gave a help like output.
However, I'm happier with the gui version I now have working.

Regards,
I
Ken.

I used EasyDD_v.3-amd64.pet
Also used EasyDD-v.4_static-noarch.pet

I installed a Slacko64-6.3.2-uefi.iso

Had to change .iso to .img on the end of the file name.

EasyDD did a good install to a USB flash drive.

Booting and using it to post this.

So, seems you can use EasyDD to install a Puppy version iso.

However, this turns the USB flash drive into a read only device (like a live CD), formatted with an iso9660 filesystem.
You cannot add or write anything new to the flash drive.
Cannot put the puppysave on the USB flash drive.

Afternoon, boys & girls.

New, v5 portable packages of BK's EasyDD (with statically-compiled 'dd' - noarch) have been attached to post #1 of the thread. There's an AppImage; a 'self-extracting script' (these two courtesy of Fred's 'portable-creation' scripts); and a more traditional RoxApp.

Help yourselves to whichever takes your fancy. All will run from literally anywhere.

Enjoy.


Mike.

Is there any documentation of how easydd works?
Too hard for me to read the code and the sed-command is not my problem.

I've bought some "intenso" SD-Cards who like to loose data,
Updating a backup with rsync to an SD-card ends up with errors like: I am sure the easydd could elliminate the trouble

@ mann:-

Best thing would be to drop BarryK a PM, and ask him.

I don't believe any documentation was ever provided, TBH. I've simply packaged the easydd script and statically-compiled binary as provided by Barry; AFAIK, these are used by him with his new EasyOS. I just thought it was a useful utility for the community, that's all, so I packaged them and hosted them. The GUI is pretty straight-forward, and easy to follow.

I don't understand the coding involved at all, I afraid. Coding is not my "strong point"..!!

If any documentation should ever come to light for it, I will of course be happy to add it in to an updated package.....


Mike.

mann wrote:Is there any documentation of how easydd works?
Too hard for me to read the code and the sed-command is not my problem.

I wrote this recently:

https://bkhome.org/linux/easydd-write-i ... drive.html

There is also my own take on a self-extracting portable easydd. It uses the chroot method, and needs testing:

https://bkhome.org/news/202005/easydd-p ... linux.html

If you have a recent pup or pup-derivative, you don't need any of the portable creations, just the bare script.
Reason is, all pups have 'gtkdialog', and if no more than a couple of years old will have a suitable 'dd' utility.

mann wrote:Is there any documentation of how easydd works?
Too hard for me to read the code and the sed-command is not my problem.

I've bought some "intenso" SD-Cards who like to loose data,
Updating a backup with rsync to an SD-card ends up with errors like:

Code: Select all

rsync: readlink_stat("/mnt/sdd1/backup/stein.jpg") failed: Input/output error (5)
...
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]

I am sure the easydd could elliminate the trouble

Oh, and easydd is only for writing an OS image file to a drive. It is not for anything else such as file backup with rsync.

[Deleted]