cp foo{,.bak} not always supported

Dan Nicholson dbn.lists at gmail.com
Tue Jun 3 11:06:53 MDT 2008


On Mon, Jun 2, 2008 at 12:29 AM, Alexander E. Patrakov
<patrakov at gmail.com> wrote:
> 2008/6/1, Gilles Espinasse <g.esp at free.fr>:
>> cp configure{,.bak}
>> cp: missing destination file operand after `configure{,.bak}'
>> Try `cp --help' for more information.
>
> This simply can't happen if the user follows the book to the letter.
> Look at http://www.linuxfromscratch.org/lfs/view/development/chapter04/addinguser.html:
>
> useradd -s /bin/bash -g lfs -m -k /dev/null lfs
>
> See "bash" here? On the next page, /bin/bash is also explicitly called
> in ~/.bash_profile.
>
> So: the bug report is invalid.

+1

Guys, please remember the difference between running commands
interactively (using the _login_ shell, which we, and Ubuntu, set to
/bin/bash) and executing a shell script with the /bin/sh interpreter.

--
Dan


More information about the lfs-dev mailing list