cp foo{,.bak} not always supported

[Bryan Kadzban]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

Bruce Dubbs wrote:
> Bryan Kadzban wrote:
> 
>> Just make sure the user that's running your scripts (...or at
>> least, I'm assuming that's how people do an "IPCop compile"?) is
>> running bash.  Then, if they already are running bash, also add a
>> "set -B".  The book instructions should work at that point.
> 
> Why should we recommend setting what is set by default?

That's why I said "if they already are running bash" -- because if
they're running bash, then the only way that it would avoid doing brace
expansion is if +B was set.  Which means -B needs to be set for brace
expansion to start working.

Of course, if they aren't running bash, then they need to do that first.

> Why would someone want to turn this off in an initialization script?

I strongly suspect the user was running either sh (which was not linked
to bash) or dash.  I left that in there just in case they were running
it, but someone decided to "set +B" in one of the startup files.  No, I
don't know why anyone would want to do this, but it is one possible
explanation for the failure.  :-)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIQy2mS5vET1Wea5wRA4I0AKCj/rrxr5PAD9aet6MDpKGS+IJ3sACfXmRG
Sw6CYxB0RK9xaZViGCavblY=
=zVra
-----END PGP SIGNATURE-----