Hello,
Are there any software to do binary copy of the flash card to another
one ( master one and destination located in PCMCIA slot).
Thanks, Janusz.
Janusz wrote:
Hello,
Are there any software to do binary copy of the flash card to another
one ( master one and destination located in PCMCIA slot).Thanks, Janusz.
cp ?
What about not QNX file system flash cards?
“Rennie Allen” <rallen@csical.com> wrote in message
news:3C7D37F9.5070308@csical.com…
Janusz wrote:
Hello,
Are there any software to do binary copy of the flash card to another
one ( master one and destination located in PCMCIA slot).Thanks, Janusz.
cp ?
Janusz <ruszelj@baxter.com> wrote:
What about not QNX file system flash cards?
cp ?
cp will work on raw flash devices – you can back up (to a formatted
floppy) by doing:
cp /dev/fd0 /tmp/fd_data
(swap floppies)
cp /tmp/fd_data /dev/fd0
Similarly for flash –
cp /dev/raw_flash_mnt1 /dev/raw_flash_mnt2
-David
“Rennie Allen” <> rallen@csical.com> > wrote in message
news:> 3C7D37F9.5070308@csical.com> …
Janusz wrote:Hello,
Are there any software to do binary copy of the flash card to another
one ( master one and destination located in PCMCIA slot).Thanks, Janusz.
cp ?
–
QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.
In these situations I would say you should always use ‘dd’ - it has much
more robust error reporting than cp and handles timeouts in a nicer way.
cheers,
Kris
“David Gibbs” <dagibbs@qnx.com> wrote in message
news:a5jg6f$2jk$1@nntp.qnx.com…
Janusz <> ruszelj@baxter.com> > wrote:
What about not QNX file system flash cards?cp ?
cp will work on raw flash devices – you can back up (to a formatted
floppy) by doing:cp /dev/fd0 /tmp/fd_data
(swap floppies)
cp /tmp/fd_data /dev/fd0Similarly for flash –
cp /dev/raw_flash_mnt1 /dev/raw_flash_mnt2
-David
“Rennie Allen” <> rallen@csical.com> > wrote in message
news:> 3C7D37F9.5070308@csical.com> …
Janusz wrote:Hello,
Are there any software to do binary copy of the flash card to
another
one ( master one and destination located in PCMCIA slot).Thanks, Janusz.
cp ?
\QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.
Additionally I would like to add, that pccard-launch utility has a bug which
corrupts data
if you do not slay dev-eide driver before you remove card.
cp /dev/hd1 /dev/hd2 is very slow, faster solution is to:
cp /dev/hd1 /tmp/img.dat
cp /tmp/img.dat /dev/hd2
cheers,
Janusz.
ps. Thanks David.
“Kris Warkentin” <kewarken@qnx.com> wrote in message
news:a5jjrq$5si$1@nntp.qnx.com…
In these situations I would say you should always use ‘dd’ - it has much
more robust error reporting than cp and handles timeouts in a nicer way.
cheers,
Kris
“David Gibbs” <dagibbs@qnx.com> wrote in message
news:a5jg6f$2jk$1@nntp.qnx.com…
Janusz <> ruszelj@baxter.com> > wrote:
What about not QNX file system flash cards?cp ?
cp will work on raw flash devices – you can back up (to a formatted
floppy) by doing:cp /dev/fd0 /tmp/fd_data
(swap floppies)
cp /tmp/fd_data /dev/fd0Similarly for flash –
cp /dev/raw_flash_mnt1 /dev/raw_flash_mnt2
-David
“Rennie Allen” <> rallen@csical.com> > wrote in message
news:> 3C7D37F9.5070308@csical.com> …
Janusz wrote:Hello,
Are there any software to do binary copy of the flash card to
another
one ( master one and destination located in PCMCIA slot).Thanks, Janusz.
cp ?
\QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.
Janusz wrote:
cp /dev/hd1 /dev/hd2 is very slow, faster solution is to:
cp /dev/hd1 /tmp/img.dat
cp /tmp/img.dat /dev/hd2
dd would help with the speed also, as you can specify block size.
Janusz <ruszelj@baxter.com> wrote:
Additionally I would like to add, that pccard-launch utility has a bug which
corrupts data if you do not slay dev-eide driver before you remove card.
That’s not a bug, that’s a mis-use!? A similar “bug” would exist with
devb-fdc and you ejecting the floppy with the light still on! Slaying
the driver to force a cache cleanup is a little heavy-handed, you
could either (i) umount the block device prior to eject, (ii) wait a
couple of seconds (data is not as aggressively cached for removable
media as it is for hard disks), (iii) issue a few “sync” commands,
(iv) from code you’d use fsync() - “cp”/“dd” don’t do this. The
safest option is to mount/umount the filesystem around card insertion/
removal (although the filesystem will attempt to automatically do this
for you because most non-UNIX users would find it cumbersome otherwise).