- Original Message -
From: Gilles Espinasse [EMAIL PROTECTED]
To: LFS Developers Mailinglist lfs-dev@linuxfromscratch.org
Sent: Monday, June 02, 2008 11:15 PM
Subject: Re: cp foo{,.bak} not always supported
...
I check in make-3.81 sources and /bin/sh is the default shell.
NEWS file
On Mon, Jun 2, 2008 at 12:29 AM, Alexander E. Patrakov
[EMAIL PROTECTED] wrote:
2008/6/1, Gilles Espinasse [EMAIL PROTECTED]:
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
2008/6/1, Gilles Espinasse [EMAIL PROTECTED]:
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
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Bruce Dubbs wrote:
My point is that this is an unusual user problem and it is not
appropriate for the book to address it.
Ah. Yes, I'd completely agree with that. :-)
(I was trying to suggest that the set -B be added to the IPCop scripts
- Original Message -
From: Bruce Dubbs [EMAIL PROTECTED]
To: LFS Developers Mailinglist lfs-dev@linuxfromscratch.org
Sent: Monday, June 02, 2008 3:39 AM
Subject: Re: cp foo{,.bak} not always supported
Bryan Kadzban wrote:
I strongly suspect the user was running either sh (which
It has been reported on ipcop-devel list that cp foo{,.bak} contruction is
broken on Ubuntu-8.04
This was on expect instructions
cp configure{,.bak}
cp: missing destination file operand after `configure{,.bak}'
Try `cp --help' for more information.
Could it not be prefered to build sed at the
On Sun, Jun 01, 2008 at 02:52:30PM +0200, Gilles Espinasse wrote:
It has been reported on ipcop-devel list that cp foo{,.bak} contruction is
broken on Ubuntu-8.04
This was on expect instructions
cp configure{,.bak}
cp: missing destination file operand after `configure{,.bak}'
Try `cp
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Gilles Espinasse wrote:
It has been reported on ipcop-devel list that cp foo{,.bak} contruction is
broken on Ubuntu-8.04
This was on expect instructions
cp configure{,.bak}
cp: missing destination file operand after `configure{,.bak}'
Gilles Espinasse wrote:
It has been reported on ipcop-devel list that cp foo{,.bak} contruction is
broken on Ubuntu-8.04
This was on expect instructions
cp configure{,.bak}
cp: missing destination file operand after `configure{,.bak}'
Try `cp --help' for more information.
Could it
- Original Message -
From: Ken Moffat [EMAIL PROTECTED]
To: LFS Developers Mailinglist lfs-dev@linuxfromscratch.org
Sent: Sunday, June 01, 2008 5:06 PM
Subject: Re: cp foo{,.bak} not always supported
On Sun, Jun 01, 2008 at 02:52:30PM +0200, Gilles Espinasse wrote:
It has been
On Sun, Jun 01, 2008 at 04:06:47PM +0100, Ken Moffat wrote:
On Sun, Jun 01, 2008 at 02:52:30PM +0200, Gilles Espinasse wrote:
It has been reported on ipcop-devel list that cp foo{,.bak} contruction is
broken on Ubuntu-8.04
This was on expect instructions
cp configure{,.bak}
cp:
Ken Moffat wrote:
On Sun, Jun 01, 2008 at 02:52:30PM +0200, Gilles Espinasse wrote:
It has been reported on ipcop-devel list that cp foo{,.bak} contruction is
broken on Ubuntu-8.04
This was on expect instructions
cp configure{,.bak}
cp: missing destination file operand after
On Sun, Jun 01, 2008 at 06:19:03PM +0200, Gilles Espinasse wrote:
This was just to inform.
You could require what you desire.
For me, less requirement is better so we will adapt our scripts.
I do not imagine I could make Ubuntu change something just to let IPCop
compile ;-)
Gilles
Hi
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Gilles Espinasse wrote:
This was just to inform.
You could require what you desire.
For me, less requirement is better so we will adapt our scripts. I do
not imagine I could make Ubuntu change something just to let IPCop
compile ;-)
You
Ken Moffat wrote:
On Sun, Jun 01, 2008 at 06:19:03PM +0200, Gilles Espinasse wrote:
This was just to inform.
You could require what you desire.
For me, less requirement is better so we will adapt our scripts.
I do not imagine I could make Ubuntu change something just to let IPCop
Bryan Kadzban wrote:
You don't have to make Ubuntu change anything. 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
-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.
Bryan Kadzban wrote:
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
18 matches
Mail list logo
