cp bug?

[Joakim Tjernlund]

On Fri, 2008-03-28 at 09:44 -0500, Kevin Holland wrote:
> You have to use something like 
> cat myfile > /dev/mtdblock/1
> because you don't have a filesystem mounted to that mtdblock I'm
> assuming.  If there is a filesystem you would mount it then copy the
> file to the mountpoint.
> Kevin

Yeah, I know the cat trick works but so should cp too, I think. Earlier
I used GNU cp and that worked like that. Compare with symlinks, cp
copies the contents, not the symlink itself(unless -d or -P is given)

   Jocke
> On Fri, 2008-03-28 at 15:36 +0100, Joakim Tjernlund wrote:
> > I just tried to "cp /dev/mtdblock1 myfile" and I got
> > a copy of the mtdblock1 file, not the contents:
> > > ls -l myfile 
> > brw-r-----    1 root     root      31,   1 Mar 28 15:33 myfile
> > 
> > Someone also mentioned problems copy files from /proc that has a zero
> > file size, i.e, it seemed like bb cp stats the file to get the size and
> > the copies that many bytes. Files in /proc don't always report correct
> > file size.
> > 
> > bb v1.7.3
> > 
> >  Jocke
> > _______________________________________________
> > busybox mailing list
> > busybox at busybox.net
> > http://busybox.net/cgi-bin/mailman/listinfo/busybox
>