busybox 1.19.3 cp bug w.r.t device files?

[Baruch Siach]

Hi Joakim,

On Wed, Dec 21, 2011 at 12:31:23PM +0100, Joakim Tjernlund wrote:
> Recently installed bb 1.19.3 (gentoo) on our ppc target. Today I discovered
> that cp vmlinux /dev/mtdblock5 dosn't work. The device file is removed and
> a new plain file is created instead.
> Feels like a bb bug, comments?

This is normal behaviour of cp as far as I know. You can do 'cat vmlinux > 
/dev/mtdblock5' instead.

Note two other things however:

1. Unless your bootloader can parse ELF, having vmlinux on /dev/mtdblock5 
   won't do what you expect

2. If /dev/mtdblock5 is on a NAND device, you should use nandwrite for writing 
   into your raw MTD device (/dev/mtd5), because nandwrite is bad block aware, 
   while 'cat' is not

baruch

-- 
                                                     ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -