Making DO_POSIX_CP configurable

Denys Vlasenko vda.linux at googlemail.com
Tue Sep 11 10:37:19 UTC 2007


On Tuesday 11 September 2007 00:19, Alexander Kriegisch wrote:
> In SVN rev. #18119 [1] the default behaviour of 'cp' was changed by
> Denis in order to improve security and also to save a few bytes. This
> leads to problems in our application scenario here: We work on a
> mipsel-based router platform equipped with a TFFS (tiny flash
> filesystem) showing several "files" as character devices. Copying new
> contents over existing files results in the character devices being
> unlinked and regular files being created instead, which is a problem
> because they are not saved back into the flash memory, thus the changes
> are not persistent. We have to use 'cat' in order to fix this.
> 
> Denis, would you please consider making the hard-coded value of
> DO_POSIX_CP configurable? I could provide a patch, if needed, but it
> should be pretty straightforward and will probably be cleaner if you do
> it yourself. This way the default would still be the one you prefer and
> our firmware mod using a newer BB version than the original one would
> still work if we just changed this config option.

Try this, is it good enough?
--
vda
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 9.patch
Type: text/x-diff
Size: 1758 bytes
Desc: not available
Url : http://lists.busybox.net/pipermail/busybox/attachments/20070911/d7999a53/attachment-0002.bin 


More information about the busybox mailing list