On 05/12/2011 04:26 PM, Pol Vangheluwe wrote:
> Op 12-mei-2011, om 11:34 heeft Simon Geard het volgende geschreven:
>
>> On Wed, 2011-05-11 at 23:18 +0200, Pol Vangheluwe wrote:
>>
>>> The bash manual tells me that the structure "command1&& command2"
>>> executes command2
>>> if and only if comman
Op 12-mei-2011, om 11:34 heeft Simon Geard het volgende geschreven:
> On Wed, 2011-05-11 at 23:18 +0200, Pol Vangheluwe wrote:
>
>> The bash manual tells me that the structure "command1 && command2"
>> executes command2
>> if and only if command1 returns the exit status of zero.
>> But here, ther
On Wed, 2011-05-11 at 23:18 +0200, Pol Vangheluwe wrote:
> The bash manual tells me that the structure "command1 && command2"
> executes command2
> if and only if command1 returns the exit status of zero.
> But here, there is only one command (cat), so I really don't
> understand why "&&" is neede
On 05/11/2011 04:18 PM, Pol Vangheluwe wrote:
>
> The bash manual tells me that the structure "command1 && command2"
> executes command2
> if and only if command1 returns the exit status of zero.
> But here, there is only one command (cat), so I really don't understand
> why "&&" is needed.
>
Th
rmally copy/paste the instructions from BLFS when building something on
>> my target machine.
>> I had to remove this "&&" to create successfully the configuration file.
>>
>> Same problem with the scripts to create the configuration files for
>> xi
achine.
> I had to remove this "&&" to create successfully the configuration file.
>
> Same problem with the scripts to create the configuration files for
> xinetd-2.3.14.
>
> pvg
>
>
>
That is the correct syntax. I did a quick test and it works
successfully the configuration file.
Same problem with the scripts to create the configuration files for
xinetd-2.3.14.
pvg
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
