On Wed, Jun 3, 2009 at 8:13 AM, Rob Landley <[email protected]> wrote:
> Remove FEATURE_VERBOSE_CP_MESSAGE, which is kind of useless. The help entry
> about it is wrong (it doesn't change "cannot create" to "cannot remove", it's
> create in both cases),
cp was fixed to not emit "cannot remove". Sometime ago, it did say
"cannot remove", because that's what actually happens: it fails
to unlink the file:
open("/does_not_exist/file", O_WRONLY|O_CREAT|O_EXCL|O_LARGEFILE,
0100755) = -1 ENOENT (No such file or directory)
unlink("/does_not_exist/file") = -1 ENOENT (No such file or directory)
write(2, "cp: cannot create '/does_not_exist...
So, "cannot remove" message was factually correct on micro-level,
but was utterly confusing.
> the option costs 60 bytes (which even if it was
> a space _savings_ would barely be worth the complexity of a config option).
>
> And worst of all, the system messages aren't actually that bad. Neither
> "Cannot stat /dir/file: not a directory" nor "cannot create /dir/file: no
> such file or directory" are especially confusing.
$ cp file /vmlinuz/file
cannot stat /vmlinuz/file: not a directory
User: "WTF?! I know it's not a directory, it's a file. Why is that a problem?"
It's impossible for me to make both camps happy, one which wants more options
("why do we have blanket CONFIG_DESKTOP?" people), and one which wants less.
It's an option. When you disable it, why do you still feel unhappy?
--
vda
_______________________________________________
busybox mailing list
[email protected]
http://lists.busybox.net/mailman/listinfo/busybox
