On 05/12/2011 03:53 PM, luxInteg wrote:
> I would be most grateful if someone could explain how lfs/blfs logs boot
> processes. I cant find a boot.log file in /var/log
>
> sincerely
> luxInteg
> -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ:
> http://www.linuxfromscratch.org/b
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
In case anyone has interest. I was able to use jhbuild to install xorg
7.6 on LFS 6.8 w/ package users fairly easily.
I installed jhbuild as pkguser jhbuild. copied modulesets to ~.
I had issues running it as intended for two reasons:
1. I did not want to use /opt as a prefix.
2. using /usr as
I would be most grateful if someone could explain how lfs/blfs logs boot
processes. I cant find a boot.log file in /var/log
sincerely
luxInteg
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information
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
