cp: odd behaviour; does not preserve symlink

[Ming-Ching Tiew]

--- On Wed, 6/10/09, Cristian Ionescu-Idbohrn 
> 
> > I am not entirely sure that I am right doing do,
> > but in this case it's ugly enough that I do disagree.
> >
> > What do you think? Is it causing compat problems in
> real life?
> 
> It might.  I suppose some people expect the same
> (sometimes broken)
> behaviour as gnu & posix, just because they're the
> authorities.  And
> that's ok, except in this case I do agree with you, but I
> wouldn't be too
> surprized to hear it's a too intrusive change.
> 

This subject matter was brought up by me ( think 
it was at least a year ago ). I am for one difficult
to accept the busybox behaviour, despite the technical 
merits of it. 

Since I was unable to convince code maintainer 
to use the gnu behaviour, I ended up putting in
gnu cp since then. 

In my case, the risk of unable to copy a file using 
the gnu behaviour is too high  ( ie if I use the 
busybox behaviour the users might ended up enable 
to 'cp' a file too important for the system to 
function correctly. I am lesser concern to security 
but bigger concern for system up time.

That's just my personal choice. 

Regards.