Lewis Donzis <firstname.lastname@example.org> wrote:
David Bacon wrote:
Use the “tar” command, including compression if you wish. If the result is
still likely to be bigger than 2GB, pipe tar’s output into “split”.
tar would be fine, but then how do you un-tar the file on to the new
disk in a production environment? It seems that we’d have to boot up
QNX, run fdisk/dinit, and then un-tar the file. The target system will
not have a CD or even a diskette to boot from.
We could use an external disk duplicator, but it would be nice if it
didn’t have to copy the entire 60GB in order to move about 15MB of
First, the disks had better actually be identical. (Exact same
h/t/s etc, otherwise a duplicated partition table could be bad
Do you need to have it all be one partition?
Create the “constant” part of your file system as one partition,
and mount it as /, maybe even mount it read-only on your target.
Create the “open” part of your file system as a filesystem on
a second partition, and don’t put anything on it.
Then, duplicate the entire constant partition and just the first
bit of the second. (I’m pretty sure that if you create a partition
then just do a “dinit” on it, its only going to write to a bunch
of blocks at the start of the partition, rather than modify blocks all
the way along. You could test it just to make sure.)
Or, you might create this 2nd partition dynamically, by creating a
boot script, that on first boot creates and dinits (and even copies
initial stuff over onto) the 2nd partition, then replaces this
“initializer” boot script with a “normal run” boot script.
QNX Training Services
Please followup in this newsgroup if you have further questions.