lfs fail during 6.26

[Michael Havens]

if so That begs the question as to why everything is good now.

:-)~MIKE~(-:


On Mon, Aug 18, 2014 at 9:53 PM, Michael Havens <bmike1 at gmail.com> wrote:

> okay, I modified my script a little (see below) and it seemed to run but
> the red fail didn't seem to come up in the grep command. So everything is
> good now?
>
> FORCE_UNSAFE_CONFIGURE=1 ./configure \
>             --prefix=/usr            \
>             --enable-no-install-program=\
> kill,uptime>>config.fail
> make >>make.fail
> make NON_ROOT_USERNAME=nobody check-root>>check.fail
> echo "dummy:x:1000:nobody" >> /etc/group
> chown -Rv nobody .
> su nobody -s /bin/bash \
>           -c "PATH=$PATH make RUN_EXPENSIVE_TESTS=yes /
>           check">>test.fail
> sed -i '/dummy/d' /etc/group
> make install>>install.fail
> mv -v /usr/bin/{cat,chgrp,chmod,chown,cp,date,dd,df,echo} /bin
> mv -v /usr/bin/{false,ln,ls,mkdir,mknod,mv,pwd,rm} /bin
> mv -v /usr/bin/{rmdir,stty,sync,true,uname,test,[} /bin
> mv -v /usr/bin/chroot /usr/sbin
> mv -v /usr/share/man/man1/chroot.1 /usr/share/man/man8/chroot.8
> sed -i s/\"1\"/\"8\"/1 /usr/share/man/man8/chroot.8
> mv -v /usr/bin/{head,sleep,nice} /bin
> cat {config,make,test,install}.fail|grep fail
>
> :-)~MIKE~(-:
>
>
> On Mon, Aug 18, 2014 at 9:52 PM, Michael Havens <bmike1 at gmail.com> wrote:
>
>> okay, I modified my script a little (see below) and it seemed to run but
>> the red fail didn't seem to come up in the grep command. So everything is
>> good now?
>>
>> FORCE_UNSAFE_CONFIGURE=1 ./configure \
>>             --prefix=/usr            \
>>             --enable-no-install-program=\
>> kill,uptime>>config.fail
>>
>> make >>make.fail
>> make NON_ROOT_USERNAME=nobody check-root>>check.fail
>> echo "dummy:x:1000:nobody" >> /etc/group
>> chown -Rv nobody .
>> su nobody -s /bin/bash \
>>           -c "PATH=$PATH make RUN_EXPENSIVE_TESTS=yes /
>>
>>           check">>test.fail
>> sed -i '/dummy/d' /etc/group
>> make install>>install.fail
>> mv -v /usr/bin/{cat,chgrp,chmod,chown,cp,date,dd,df,echo} /bin
>> mv -v /usr/bin/{false,ln,ls,mkdir,mknod,mv,pwd,rm} /bin
>> mv -v /usr/bin/{rmdir,stty,sync,true,uname,test,[} /bin
>> mv -v /usr/bin/chroot /usr/sbin
>> mv -v /usr/share/man/man1/chroot.1 /usr/share/man/man8/chroot.8
>> sed -i s/\"1\"/\"8\"/1 /usr/share/man/man8/chroot.8
>> mv -v /usr/bin/{head,sleep,nice} /bin
>> cat {config,make,test,install}.fail|grep fail
>>
>> :-)~MIKE~(-:
>>
>>
>> On Sat, Aug 16, 2014 at 2:32 PM, Michael Havens <bmike1 at gmail.com> wrote:
>>
>>> cool! I was watching the text scroll by and noticed a red 'fail'. I
>>> tried to go up to the 'fail' but the terminal wouldn't let me and by the
>>> time it had finished the 'fail' was way past the buffer. I need to know if
>>> the following (the commands you are supposed to enter with the package)
>>> plus my modifications ('>>' and 'cat {*.fail}|grep fail') will reveal what
>>> failed so I can google it.
>>>
>>> {FORCE_UNSAFE_CONFIGURE=1 ./configure \
>>>             --prefix=/usr            \
>>>             --enable-no-install-program=kill,uptime}>>config.fail
>>> make >>make.fail
>>> make NON_ROOT_USERNAME=nobody check-root>>check.fail
>>> echo "dummy:x:1000:nobody" >> /etc/group
>>> chown -Rv nobody .
>>> {su nobody -s /bin/bash \
>>>           -c "PATH=$PATH make RUN_EXPENSIVE_TESTS=yes check"}>>test.fail
>>> sed -i '/dummy/d' /etc/group
>>> make install>>install.fail
>>> mv -v /usr/bin/{cat,chgrp,chmod,chown,cp,date,dd,df,echo} /bin
>>> mv -v /usr/bin/{false,ln,ls,mkdir,mknod,mv,pwd,rm} /bin
>>> mv -v /usr/bin/{rmdir,stty,sync,true,uname,test,[} /bin
>>> mv -v /usr/bin/chroot /usr/sbin
>>> mv -v /usr/share/man/man1/chroot.1 /usr/share/man/man8/chroot.8
>>> sed -i s/\"1\"/\"8\"/1 /usr/share/man/man8/chroot.8
>>> mv -v /usr/bin/{head,sleep,nice} /bin
>>> cat *.fail|grep fail
>>>
>>> :-)~MIKE~(-:
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.phxlinux.org/pipermail/plug-discuss/attachments/20140819/92ca1ba2/attachment.html>