[BusyBox] PATCH: cp /dev/null some_file
tom at ceisystems.com
tom at ceisystems.com
Sun May 30 13:08:35 UTC 2004
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Anthony,
> Below is a bug fix for the common idiom
> cp /dev/null some_file
> to create an empty file.
I know this is getting a little off subject here, but what is the
_correct_ thing to do when cp gets a device file for its source? Should
it copy the dev file? I would think this would be the proper thing to
do. What I'm getting at here is this- should we taint busybox with fixes
for broken thinking? Isn't this what makes glibc and all of the standard
tools so big?
Thomas Cameron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (MingW32)
Comment: For info see http://www.gnupg.org
iEYEARECAAYFAkC53GYACgkQCnk9/RTg1dBFBwCggO0eOxRT1K8/JFHjoei8c5hv
OVYAn0uXtW9xiNxIrk8nxnUdoBjDBhOy
=746G
-----END PGP SIGNATURE-----
More information about the busybox
mailing list