On Wed, Sep 26, 2007 at 09:04:19PM -0400, Mike Frysinger wrote:
> is it even possible to utilize NUL in scripts ? or does bash just strip it
> out ? for example, trying to work with binary data:
> foo=$( echo "${foo}" > new-file
> the "new-file" will be exactly "binary-file" if all NUL bytes are
On Wednesday 26 September 2007, Mike Frysinger wrote:
> or perhaps i want to take an arg list, append a string, and run a command
> on it ... but i cant pass it straight as it may be too large, so i need to
> xargs it ... so i'd do something like:
> echo ${@/%.moo/.foo$'\000'} | xargs -0 rm -f
> bu
Mike Frysinger schrieb:
> is it even possible to utilize NUL in scripts ? or does bash just strip it
> out ? for example, trying to work with binary data:
> foo=$( echo "${foo}" > new-file
> the "new-file" will be exactly "binary-file" if all NUL bytes are stripped out
>
> or perhaps i want to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Mike Frysinger on 9/26/2007 7:04 PM:
> is it even possible to utilize NUL in scripts ? or does bash just strip it
> out ? for example, trying to work with binary data:
> foo=$( echo "${foo}" > new-file
> the "new-file" will be exactly "
is it even possible to utilize NUL in scripts ? or does bash just strip it
out ? for example, trying to work with binary data:
foo=$( new-file
the "new-file" will be exactly "binary-file" if all NUL bytes are stripped out
or perhaps i want to take an arg list, append a string, and run a command
