I know, but it is not default behaviour, i.e. without manually changing the POSIX switch in the source code it will still unlink devices and recreate them as files. This affects all users negatively, independent of their wish to be POSIX-compliant. My tendency is to call this a bug, not some optional thing which somebody would want, somebody else not.
I do not mean to get annoying, just want to clarify a possible misconception or misunderstanding of what my point is on your side. Respectfully -- Alexander Kriegisch Denys Vlasenko: > On Tuesday 11 September 2007 23:13, Alexander Kriegisch wrote: >> Sorry, Denys, I was never talking about the scenario you are mentioning, >> really just about overwriting an existing character device by a regular >> file, so it gets its contents. No more, no less. And I still insist that >> it is fair to expect that this will work. I am not talking about copying >> a device onto something else and not about copying recursively either. >> Only this: >> >> cp /regular/file /character/device >> >> Without unlinking the device before copying the source file into it. It >> is so straightforward it almost hurts. ;-) Why on earth should this not >> work by default (without tweaking the source code)? > > It works now. I fixed it after your first complaint. _______________________________________________ busybox mailing list busybox@busybox.net http://busybox.net/cgi-bin/mailman/listinfo/busybox
