Hey Chas, Thanks much for your reply. I actually want to have some more control over this.
Thinking in way to initiate some in parallel also to get rid of ""OS"" specific things [if there] thought of minimizing effort to run something which you suggested below. But seems like, the only option in this galaxy :( Thanks Everyone Regards, a b On Mon, Mar 28, 2011 at 6:10 PM, Chas. Owens <chas.ow...@gmail.com> wrote: > On Mon, Mar 28, 2011 at 05:22, a b <testa...@gmail.com> wrote: > > Thanks Rob > > > > I too was thinking that way. Just in case if any one might have face this > > issue and hence this email > > > > Well if no module i will live with it for time being > snip > > The Unix dd command is a swiss army knife of copying data, could you > narrow it down to what you want to use dd for? A simple > implementation would be > > #!/usr/bin/perl > > use strict; > use warnings; > > die "usage: $0 infile outfile\n" unless @ARGV == 2; > > open my $in, "<:raw", $ARGV[0] > or die "could not open $ARGV[0]: $!\n"; > open my $out, ">:raw", $ARGV[1] > or die "could not open $ARGV[1]: $!\n"; > > local $/ = \4096; #read 4k at a time > > print $out $_ while <$in>; > > > > -- > Chas. Owens > wonkden.net > The most important skill a programmer can have is the ability to read. >
