devil-linux-develop Mailing List for Devil-Linux (Page 12)

http://developers.slashdot.org/story/11/01/27/2059200/SourceForge-Down-After-Attack-Updated

 - BS


On Thu, Jan 27, 2011 at 08:41, Heiko Zuerker <he...@zu...> wrote:
> Quoting Andrzej Odyniec <an...@ma...>:
>
>> Dears,
>>
>> Maybe someone knows what happened with CVS:
>>
>>> # cvs
>>> -d:pserver:ano...@de...:/cvsroot/devil-linux
>>> login
>>> Logging in to
>>> :pserver:ano...@de...:2401/cvsroot/devil-linux
>>> CVS password:
>>> cvs [login aborted]: connect to
>>> devil-linux.cvs.sourceforge.net(216.34.181.110):2401 failed:
>>> Connection refused
>>> #
>>
>> There is other server?
>
> No, that's the only server sourceforge is providing us for CVS.
>
> --
>
> Regards
>   Heiko Zuerker
>   http://www.devil-linux.org
>
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>
>
>
> ------------------------------------------------------------------------------
> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
> Finally, a world-class log management solution at an even better price-free!
> Download using promo code Free_Logger_4_Dev2Dev. Offer expires
> February 28th, so secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsight-sfd2d
> _______________________________________________
> Devil-linux-develop mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
>

Quoting Andrzej Odyniec <an...@ma...>:

> Dears,
>
> Maybe someone knows what happened with CVS:
>
>> # cvs  
>> -d:pserver:ano...@de...:/cvsroot/devil-linux  
>> login
>> Logging in to  
>> :pserver:ano...@de...:2401/cvsroot/devil-linux
>> CVS password:
>> cvs [login aborted]: connect to  
>> devil-linux.cvs.sourceforge.net(216.34.181.110):2401 failed:  
>> Connection refused
>> #
>
> There is other server?

No, that's the only server sourceforge is providing us for CVS.

-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Dears,

Maybe someone knows what happened with CVS:

> # cvs -d:pserver:ano...@de...:/cvsroot/devil-linux login
> Logging in to :pserver:ano...@de...:2401/cvsroot/devil-linux
> CVS password:
> cvs [login aborted]: connect to devil-linux.cvs.sourceforge.net(216.34.181.110):2401 failed: Connection refused
> #

There is other server?

Best Regards

-- 
Andrzej Odyniec

Quoting Andrzej Odyniec <an...@ma...>:

> Dears,
>
> It seems that the reason for pausing prepare a script with an error  
> in line 72
> prepare a script. Recently inserted line:
>
> 	set_kernel_option CONFIG_NR_CPUS $(CONFIG_LINUX_NR_CPUS)
>
> should be:
>
> 	set_kernel_option CONFIG_NR_CPUS $CONFIG_LINUX_NR_CPUS

My bad.
Fixed in CVS, thx.

-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Dears,

It seems that the reason for pausing prepare a script with an error in line 72 
prepare a script. Recently inserted line:

	set_kernel_option CONFIG_NR_CPUS $(CONFIG_LINUX_NR_CPUS)

should be:

	set_kernel_option CONFIG_NR_CPUS $CONFIG_LINUX_NR_CPUS

Best regards

-- 
Andrzej Odyniec

Heiko Zuerker wrote:
>>What do you think about this?
> Is there a newer version available which fixes the issue?
> I didn't see a fix in the bug report.

I searched but could not find any fix to alsa. I tried to compile the latest 
version of the project site: 1.0.23, but compilation reports the same error. I 
do not feel it so necessary to patch alsa-utils myself. Actually, I connected 
Alsa to the Asterisk for unusual applications. Virtually alsa can be useful 
only to the interception of telephone channels on a machine with Asterisk, but 
it probably does not apply, however, independent server-router but rather GUI 
installation. So I resigned for now of Alsa.

I think alsa must remain on DL in experimental state for some time.

Best Regards

-- 
Andrzej Odyniec

<an...@ma...>
Rada Nadzorcza Macrologic SA
ul. Kłopotowskiego 22, 03-717 Warszawa
tel. +48-222566332, kom. +48-601276572
Skype: andrzej.odyniec
Rejestr: Sąd Rejonowy dla m.st. Warszawy,
          XIII Wydział Gospodarczy Krajowego
          Rejestru Sądowego, numer 0000045462
Numer identyfikacji podatkowej: PL 5220002825
Kapitał zakładowy: 1888719 zł opłacony w całości

Quoting Andrzej Odyniec <an...@ma...>:
> Dears,
>
> Alsa is probably not too often compiled. But I sometimes use ALSA for
> Asterisk. Attempt to compile alsa-utils fails:
>
>> init_sysdeps.c:22: error: static declaration of 'strlcpy' follows  
>> non-static declaration
>
> The explanation for this situation I found here:
>
> http://bugs.gentoo.org/337937
>
> They wrote:
>> Currently, openrc strictly assumes that glibc won't export strlcpy(). This
>> means that if at some point glibc starts to supply this function, or an user
>> patches his glibc to do so (yes, I know nobody is going to support  
>> that), the
>> build is going to fail with 'static declaration of 'strlcpy'  
>> follows non-static
>> declaration' error.
>>
>> In my opinion, the correct programming practice here is to use real  
>> guessing to
>> determine whether a particular C library exports that function.
>
> Probably the last upgrade of glibc gave this effect.
>
> What do you think about this?

Is there a newer version available which fixes the issue?
I didn't see a fix in the bug report.

-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Dears,

Alsa is probably not too often compiled. But I sometimes use ALSA for 
Asterisk. Attempt to compile alsa-utils fails:

> init_sysdeps.c:22: error: static declaration of 'strlcpy' follows non-static declaration

The explanation for this situation I found here:

http://bugs.gentoo.org/337937

They wrote:
> Currently, openrc strictly assumes that glibc won't export strlcpy(). This
> means that if at some point glibc starts to supply this function, or an user
> patches his glibc to do so (yes, I know nobody is going to support that), the
> build is going to fail with 'static declaration of 'strlcpy' follows non-static
> declaration' error.
> 
> In my opinion, the correct programming practice here is to use real guessing to
> determine whether a particular C library exports that function.

Probably the last upgrade of glibc gave this effect.

What do you think about this?

Best regards

-- 
Andrzej Odyniec

<an...@ma...>
Rada Nadzorcza Macrologic SA
ul. Kłopotowskiego 22, 03-717 Warszawa
tel. +48-222566332, kom. +48-601276572
Skype: andrzej.odyniec
Rejestr: Sąd Rejonowy dla m.st. Warszawy,
          XIII Wydział Gospodarczy Krajowego
          Rejestru Sądowego, numer 0000045462
Numer identyfikacji podatkowej: PL 5220002825
Kapitał zakładowy: 1888719 zł opłacony w całości

Hi,

Thanks for Your attention.

Just as I suspected, after downloading all the sources from ftp, everything is 
built correctly. Of course I have no way to determine the specific cause. 
Perhaps something was damaged on the drive. Or seemed to lftp client that does 
not need to update something in my backup sources.

Heiko Zuerker wrote:
> This shouldn't have happened.
> I updated some code yesterday, hopefully I didn't screw anything up.

I work on computers for over 30 years, beginning from CDC CYBER, ICL, UNIVAC, 
DGC, PDP... Half my life I was a designer, programmer, tester. And I know that 
sometimes, things can happen. If from time to time I pay attention and thus to 
help out, all my pleasure. :)
I will try as soon as the next compilation.

Regards

-- 
Andrzej Odyniec

Quoting Andrzej Odyniec <an...@ma...>:

> Heiko Zuerker wrote:
>> I can't see anything wrong with what you're doing.
>> Let's try to force a re-compile of minicom:
>>
>> In the chroot:
>> rm tmp/FLAGS/build/minicom
>> make all
>
> Thanks for suggestion. I will try it next time if needed.
>
> As for now, this night I run build with all sources from ftp, but now I found
> build waiting in build/prepare for
>
> Maximum number of CPUs (NR_CPUS) [32] (NEW)
>
> I think, this is according to Serge changes because of Joachim note  
> on discuss.
>
> So I pushed this and I'm waiting

This shouldn't have happened.
I updated some code yesterday, hopefully I didn't screw anything up.

-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Heiko Zuerker wrote:
> I can't see anything wrong with what you're doing.
> Let's try to force a re-compile of minicom:
> 
> In the chroot:
> rm tmp/FLAGS/build/minicom
> make all

Thanks for suggestion. I will try it next time if needed.

As for now, this night I run build with all sources from ftp, but now I found 
build waiting in build/prepare for

Maximum number of CPUs (NR_CPUS) [32] (NEW)

I think, this is according to Serge changes because of Joachim note on discuss.

So I pushed this and I'm waiting

Regards

-- 
Andrzej Odyniec

Hey,

I can't see anything wrong with what you're doing.
Let's try to force a re-compile of minicom:

In the chroot:
rm tmp/FLAGS/build/minicom
make all

Heiko

Quoting Andrzej Odyniec <an...@ma...>:

> Heiko Zuerker wrote:
>> Are you using the default or a cusomized config?
>> I have a nightly compile running and it ran through fine last night.
>
> Interresting. I'm using default config from beginning to end.
> Always, when I'm not sure, before giving info to You, I repeat full build
> process from clean beginning without making my patches and customizations.
>
> Maybe host system is inadequate.
>
> Host system is DL built without grsecurity, but not last...  
> 1.4RC3-2010-03-30.
> I'm building on this system as Yoy see, from near year.
>
> But... maybe I need some changes in my default build process? Look into this,
> please:
>
> -----
> I'm building all as always. Always preparing environment from begin to empty
> lfssystem directory.
>
> Build environment is from:
>  > tar -xjf lfssystem-SVN-20070314-cleaned.tar.bz2
>
> And after this, build directory I get from CVS:
>
>> cd lfssystem
>> cvs  
>> -d:pserver:ano...@de...:/cvsroot/devil-linux  
>> login
>> cvs  
>> -d:pserver:ano...@de...:/cvsroot/devil-linux  
>> co build
>  > cd ..
>
> and after I'm copying sources from my pool for reduce internet transfer and
> doing update source:
>
>> cd lfssystem
>> cp -dpv /var/sources/devil/src/* build/src/
>> mkdir -p build/src/firmware/
>> cp -dpv /var/sources/devil/src/firmware/* build/src/firmware/
>> mkdir -p build/src/pecl/
>> cp -dpv /var/sources/devil/src/pecl/* build/src/pecl/
>> mkdir -p build/src/special/
>> cp  -dpv /var/sources/devil/src/special/* build/src/special/
>> mkdir -p build/src/perl-ext/
>> cp -dpv /var/sources/devil/src/perl-ext/* build/src/perl-ext/
>> mkdir -p build/src/webmin-modules/
>> cp -dpv /var/sources/devil/src/webmin-modules/* build/src/webmin-modules/
>> cd build
>> ./update_src
>
> I'm updating sources always from [1]. After each update_src I'm  
> always syncing
> build/src/ to my private pool /var/sources/devil/src/
>
> (Now I will run again getting all sources from ftp... maybe in sources I have
> errors? Maybe my sources are broken i.e. because of disk errors?)
>
> And after this as usally:
>
>> chroot /var/design/lfssystem /usr/bin/env -i HOME=/root TERM=$TERM  
>> /bin/bash -login
>
> and after:
>> cd build
>> make menuconfig
> here I choose default config and save them and:
>
>> make mrproper unpack prepare build install iso
>
> So I suppose, this is default config on clean build.
>
> Problems in minicom install log is strange... There is no references  
> to libiconv
>
> I have no idea as for now.
>
> Regards
>
> --
> Andrzej Odyniec
>
> <an...@ma...>
> Rada Nadzorcza Macrologic SA
> ul. Kłopotowskiego 22, 03-717 Warszawa
> tel. +48-222566332, kom. +48-601276572
> Skype: andrzej.odyniec
> Rejestr: Sąd Rejonowy dla m.st. Warszawy,
>           XIII Wydział Gospodarczy Krajowego
>           Rejestru Sądowego, numer 0000045462
> Numer identyfikacji podatkowej: PL 5220002825
> Kapitał zakładowy: 1888719 zł opłacony w całości
>
> ------------------------------------------------------------------------------
> Protect Your Site and Customers from Malware Attacks
> Learn about various malware tactics and how to avoid them. Understand
> malware threats, the impact they can have on your business, and how you
> can protect your company and customers by using code signing.
> http://p.sf.net/sfu/oracle-sfdevnl
> _______________________________________________
> Devil-linux-develop mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
>



-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Heiko Zuerker wrote:
> Are you using the default or a cusomized config?
> I have a nightly compile running and it ran through fine last night.

Interresting. I'm using default config from beginning to end.
Always, when I'm not sure, before giving info to You, I repeat full build 
process from clean beginning without making my patches and customizations.

Maybe host system is inadequate.

Host system is DL built without grsecurity, but not last... 1.4RC3-2010-03-30. 
I'm building on this system as Yoy see, from near year.

But... maybe I need some changes in my default build process? Look into this, 
please:

-----
I'm building all as always. Always preparing environment from begin to empty 
lfssystem directory.

Build environment is from:
 > tar -xjf lfssystem-SVN-20070314-cleaned.tar.bz2

And after this, build directory I get from CVS:

> cd lfssystem
> cvs -d:pserver:ano...@de...:/cvsroot/devil-linux login
> cvs -d:pserver:ano...@de...:/cvsroot/devil-linux co build
 > cd ..

and after I'm copying sources from my pool for reduce internet transfer and 
doing update source:

> cd lfssystem
> cp -dpv /var/sources/devil/src/* build/src/
> mkdir -p build/src/firmware/
> cp -dpv /var/sources/devil/src/firmware/* build/src/firmware/
> mkdir -p build/src/pecl/
> cp -dpv /var/sources/devil/src/pecl/* build/src/pecl/
> mkdir -p build/src/special/
> cp  -dpv /var/sources/devil/src/special/* build/src/special/
> mkdir -p build/src/perl-ext/
> cp -dpv /var/sources/devil/src/perl-ext/* build/src/perl-ext/
> mkdir -p build/src/webmin-modules/
> cp -dpv /var/sources/devil/src/webmin-modules/* build/src/webmin-modules/
> cd build
> ./update_src

I'm updating sources always from [1]. After each update_src I'm always syncing 
build/src/ to my private pool /var/sources/devil/src/

(Now I will run again getting all sources from ftp... maybe in sources I have 
errors? Maybe my sources are broken i.e. because of disk errors?)

And after this as usally:

> chroot /var/design/lfssystem /usr/bin/env -i HOME=/root TERM=$TERM /bin/bash -login

and after:
> cd build
> make menuconfig
here I choose default config and save them and:

> make mrproper unpack prepare build install iso

So I suppose, this is default config on clean build.

Problems in minicom install log is strange... There is no references to libiconv

I have no idea as for now.

Regards

-- 
Andrzej Odyniec

<an...@ma...>
Rada Nadzorcza Macrologic SA
ul. Kłopotowskiego 22, 03-717 Warszawa
tel. +48-222566332, kom. +48-601276572
Skype: andrzej.odyniec
Rejestr: Sąd Rejonowy dla m.st. Warszawy,
          XIII Wydział Gospodarczy Krajowego
          Rejestru Sądowego, numer 0000045462
Numer identyfikacji podatkowej: PL 5220002825
Kapitał zakładowy: 1888719 zł opłacony w całości

Quoting Andrzej Odyniec <an...@ma...>:

> Dears,
>
> Now build (from clean state) stops in install phase on minicom:
>> Making install in src
>> make[1]: Entering directory `/build/tmp/minicom-2.4/src'
>> gcc -DHAVE_CONFIG_H -I. -I..  -I../lib -DCONFDIR=\"/etc\"  
>> -DLOCALEDIR=\"/usr/share/locale\"  -mtune=i686 -march=i686 -Wall -W  
>> -mtune=i686 -march=i686 -MT minicom.o -MD -MP -MF .deps/minicom.Tpo  
>> -c -o minicom.o minicom.c
>> mv -f .deps/minicom.Tpo .deps/minicom.Po
>> gcc -mtune=i686 -march=i686 -Wall -W -mtune=i686 -march=i686   -o  
>> minicom minicom.o vt100.o config.o help.o updown.o util.o dial.o  
>> window.o wkeys.o ipc.o windiv.o sysdep1.o sysdep1_s.o sysdep2.o  
>> rwconf.o main.o file.o getsdir.o wildmat.o common.o  
>> ../lib/libport.a -lncurses
>> minicom.o: In function `do_iconv':
>> minicom.c:(.text+0x69f): undefined reference to `libiconv'
>> minicom.c:(.text+0x6fc): undefined reference to `libiconv'
>> minicom.o: In function `.L182':
>> minicom.c:(.text+0x1947): undefined reference to `libiconv_open'
>> minicom.o: In function `.L327':
>> minicom.c:(.text+0x3971): undefined reference to `libiconv_close'
>> collect2: ld returned 1 exit status
>> make[1]: *** [minicom] Error 1
>> make[1]: Leaving directory `/build/tmp/minicom-2.4/src'
>> make: *** [install-recursive] Error 1
>> (
>
> libiconv hasn't install phase -- was installed in build.
>
> Both packages: minicom and libiconv are old and not updated. I don't
> understand this. Maybe You?

Are you using the default or a cusomized config?

I have a nightly compile running and it ran through fine last night.

-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Dears,

Now build (from clean state) stops in install phase on minicom:
> Making install in src
> make[1]: Entering directory `/build/tmp/minicom-2.4/src'
> gcc -DHAVE_CONFIG_H -I. -I..  -I../lib -DCONFDIR=\"/etc\" -DLOCALEDIR=\"/usr/share/locale\"  -mtune=i686 -march=i686 -Wall -W -mtune=i686 -march=i686 -MT minicom.o -MD -MP -MF .deps/minicom.Tpo -c -o minicom.o minicom.c
> mv -f .deps/minicom.Tpo .deps/minicom.Po
> gcc -mtune=i686 -march=i686 -Wall -W -mtune=i686 -march=i686   -o minicom minicom.o vt100.o config.o help.o updown.o util.o dial.o window.o wkeys.o ipc.o windiv.o sysdep1.o sysdep1_s.o sysdep2.o rwconf.o main.o file.o getsdir.o wildmat.o common.o ../lib/libport.a -lncurses
> minicom.o: In function `do_iconv':
> minicom.c:(.text+0x69f): undefined reference to `libiconv'
> minicom.c:(.text+0x6fc): undefined reference to `libiconv'
> minicom.o: In function `.L182':
> minicom.c:(.text+0x1947): undefined reference to `libiconv_open'
> minicom.o: In function `.L327':
> minicom.c:(.text+0x3971): undefined reference to `libiconv_close'
> collect2: ld returned 1 exit status
> make[1]: *** [minicom] Error 1
> make[1]: Leaving directory `/build/tmp/minicom-2.4/src'
> make: *** [install-recursive] Error 1
> (

libiconv hasn't install phase -- was installed in build.

Both packages: minicom and libiconv are old and not updated. I don't 
understand this. Maybe You?

Regards

-- 
Andrzej Odyniec

Quoting Andrzej Odyniec <an...@ma...>:

> Andrzej Odyniec wrote:
>> FYI: Today build stops on sagator. Build log of sagator is:
> [...]
>> Maybe sagator is outdated for new python? I will try tomorow with other
>> versions of packages.
>
> Yes. Last stable sagator 1.2.2 builds without errors.

I accidentally checked in a broken version of the sagator script.
I fixed this earlier today and also updated sagator to the latest  
version. I should work after you update from CVS+FTP.

Sorry for that.

-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Andrzej Odyniec wrote:
> FYI: Today build stops on sagator. Build log of sagator is:
[...]
> Maybe sagator is outdated for new python? I will try tomorow with other 
> versions of packages.

Yes. Last stable sagator 1.2.2 builds without errors.

Regards

Andrzej Odyniec

Dears,

FYI: Today build stops on sagator. Build log of sagator is:
> checking for my version... 1.2.1-1 (stable)
> checking for your operating system... other
> checking for datadir... share (share)
> checking for python... python, version python2.6, in /usr
> checking for apache... /etc/httpd
> checking for logwatch... /etc/log.d/conf, /etc/log.d/scripts
> checking for webdir... /var/www/html/sagator
> configured prefix... /usr
> creating Makefile
> creating po/Makefile
> creating scripts/sagator.spec
> creating scripts/cron
> creating scripts/graphs/mrtg.cfg
> creating scripts/apache.conf
> creating debian/changelog
> python avir/libclamav/getconst.py avir/libclamav/const.py /usr/include/clamav.h
> make aspam/pydspam/const.py || true
> make[1]: Entering directory `/build/tmp/sagator-1.2.1'
> python aspam/pydspam/getconst.py aspam/pydspam/const.py \
>                 /usr/include/dspam/libdspam_objects.h
> make[1]: Leaving directory `/build/tmp/sagator-1.2.1'
> python doc/gendoc.py doc
> Traceback (most recent call last):
>   File "doc/gendoc.py", line 8, in <module>
>     import scanners,srv
>   File "./scanners.py", line 14, in <module>
>     from avir import *
>   File "./avir/__init__.py", line 5, in <module>
>     from clamav import *
>   File "./avir/clamav.py", line 174, in <module>
>     import libclamav
>   File "./avir/libclamav/__init__.py", line 15, in <module>
>     from const import *
>   File "./avir/libclamav/const.py", line 122
>     all failures are fatal */
>                ^
> SyntaxError: invalid syntax
> make: *** [doc] Error 1

Maybe sagator is outdated for new python? I will try tomorow with other 
versions of packages.

Happy New Year for All, wifes and families :)

Regards

-- 
Andrzej Odyniec

Hi,

Since it is quite time consuming and and I am very busy these days, I
give up my test for the moment.

I will maybe retry in a few weeks with a new hardware.

Thanks for your support.

Regards.

2010/12/10 mailing dl2 <mai...@gm...>:
> Ok,
>
> I will retry from the beginning one of these days.
>
> Thanks for your help.
>
> 2010/12/9 Heiko Zuerker <he...@zu...>:
>> Quoting mailing dl2 <mai...@gm...>:
>>
>>> Hello,
>>>
>>>> Which host OS are you using?
>>> Ubuntu 9.10 server
>>>
>>>> Could you look into this:
>>>> http://www.devil-linux.org/documentation/1.4.x/ch03s05.html
>>> I do not think I have PAX or Grsec installed
>>>
>>> And I do not have the file /proc/sys/kernel/exec-shield on my system.
>>>
>>>> It's not finding the iconv library, but that's a mandatory install as
>>>> part of the build.
>>> In the "cr" environement, I can find the library:
>>> root:/# find / | grep libiconv
>>> /usr/lib/libiconv.so
>>> /usr/lib/libiconv.so.2.5.0
>>> /usr/lib/preloadable_libiconv.so
>>> /usr/lib/libiconv.so.2
>>> /usr/lib/libiconv.la
>>> ...
>>>
>>> What more can I try?
>>
>> Honestly, in weird cases like this I usually nuke everything and start over.
>> This includes starting over with a fresh lfssystem.
>>
>> I just checked my logs on my compile server and last night's compile
>> with the standard settings went through without any problems.
>> Other than setting a CPU, these are the only settings I'm changing
>> before the compile (to save time):
>> CONFIG_PARALLEL_JOBS=3
>> CONFIG_PMAKE=2
>> This keeps my 3 CPU VM pretty busy....
>>
>> --
>>
>> Regards
>>   Heiko Zuerker
>>   http://www.devil-linux.org
>>
>>
>> ----------------------------------------------------------------
>> This message was sent using IMP, the Internet Messaging Program.
>>
>>
>>
>> ------------------------------------------------------------------------------
>> This SF Dev2Dev email is sponsored by:
>>
>> WikiLeaks The End of the Free Internet
>> http://p.sf.net/sfu/therealnews-com
>> _______________________________________________
>> Devil-linux-develop mailing list
>> Dev...@li...
>> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
>>
>

Hello DL Community!

Devil-Linux 1.4.1 is available for download from the usual places.

This release brings a lot of security fixes and glibc 2.10.1. See the  
changelog for details.

Upgrading is strongly recommended.

-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Ok,

I will retry from the beginning one of these days.

Thanks for your help.

2010/12/9 Heiko Zuerker <he...@zu...>:
> Quoting mailing dl2 <mai...@gm...>:
>
>> Hello,
>>
>>> Which host OS are you using?
>> Ubuntu 9.10 server
>>
>>> Could you look into this:
>>> http://www.devil-linux.org/documentation/1.4.x/ch03s05.html
>> I do not think I have PAX or Grsec installed
>>
>> And I do not have the file /proc/sys/kernel/exec-shield on my system.
>>
>>> It's not finding the iconv library, but that's a mandatory install as
>>> part of the build.
>> In the "cr" environement, I can find the library:
>> root:/# find / | grep libiconv
>> /usr/lib/libiconv.so
>> /usr/lib/libiconv.so.2.5.0
>> /usr/lib/preloadable_libiconv.so
>> /usr/lib/libiconv.so.2
>> /usr/lib/libiconv.la
>> ...
>>
>> What more can I try?
>
> Honestly, in weird cases like this I usually nuke everything and start over.
> This includes starting over with a fresh lfssystem.
>
> I just checked my logs on my compile server and last night's compile
> with the standard settings went through without any problems.
> Other than setting a CPU, these are the only settings I'm changing
> before the compile (to save time):
> CONFIG_PARALLEL_JOBS=3
> CONFIG_PMAKE=2
> This keeps my 3 CPU VM pretty busy....
>
> --
>
> Regards
>   Heiko Zuerker
>   http://www.devil-linux.org
>
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>
>
>
> ------------------------------------------------------------------------------
> This SF Dev2Dev email is sponsored by:
>
> WikiLeaks The End of the Free Internet
> http://p.sf.net/sfu/therealnews-com
> _______________________________________________
> Devil-linux-develop mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
>

Quoting mailing dl2 <mai...@gm...>:

> Hello,
>
>> Which host OS are you using?
> Ubuntu 9.10 server
>
>> Could you look into this:
>> http://www.devil-linux.org/documentation/1.4.x/ch03s05.html
> I do not think I have PAX or Grsec installed
>
> And I do not have the file /proc/sys/kernel/exec-shield on my system.
>
>> It's not finding the iconv library, but that's a mandatory install as
>> part of the build.
> In the "cr" environement, I can find the library:
> root:/# find / | grep libiconv
> /usr/lib/libiconv.so
> /usr/lib/libiconv.so.2.5.0
> /usr/lib/preloadable_libiconv.so
> /usr/lib/libiconv.so.2
> /usr/lib/libiconv.la
> ...
>
> What more can I try?

Honestly, in weird cases like this I usually nuke everything and start over.
This includes starting over with a fresh lfssystem.

I just checked my logs on my compile server and last night's compile  
with the standard settings went through without any problems.
Other than setting a CPU, these are the only settings I'm changing  
before the compile (to save time):
CONFIG_PARALLEL_JOBS=3
CONFIG_PMAKE=2
This keeps my 3 CPU VM pretty busy....

-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Hello,

> Which host OS are you using?
Ubuntu 9.10 server

> Could you look into this:
> http://www.devil-linux.org/documentation/1.4.x/ch03s05.html
I do not think I have PAX or Grsec installed

And I do not have the file /proc/sys/kernel/exec-shield on my system.

> It's not finding the iconv library, but that's a mandatory install as
> part of the build.
In the "cr" environement, I can find the library:
root:/# find / | grep libiconv
/usr/lib/libiconv.so
/usr/lib/libiconv.so.2.5.0
/usr/lib/preloadable_libiconv.so
/usr/lib/libiconv.so.2
/usr/lib/libiconv.la
...

What more can I try?

Regards.


2010/12/8 Heiko Zuerker <he...@zu...>:
> Hey,
>
> this is weird.
> It's not finding the iconv library, but that's a mandatory install as
> part of the build.
>
> Which host OS are you using?
> Could you look into this:
> http://www.devil-linux.org/documentation/1.4.x/ch03s05.html
>
> Heiko
>
> Quoting mailing dl2 <mai...@gm...>:
>
>> Hello,
>>
>> The install file is now attached.
>>
>> Regards.
>>
>> 2010/12/7 Heiko Zuerker <he...@zu...>:
>>> Quoting mailing dl2 <mai...@gm...>:
>>>
>>>> Hello,
>>>>
>>>> It was attached to my mail.
>>>
>>> Oops didn't see it.
>>> Anyway, you attached the wrong file (both times ;-) ), you sent the
>>> 'build' instead of the 'install' log.
>>>
>>> Please send /usr/src/lfssystem//build/tmp/LOGS/install/minicom
>>>
>>> --
>>>
>>> Regards
>>>   Heiko Zuerker
>>>   http://www.devil-linux.org
>>>
>>>
>>> ----------------------------------------------------------------
>>> This message was sent using IMP, the Internet Messaging Program.
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> What happens now with your Lotus Notes apps - do you make another costly
>>> upgrade, or settle for being marooned without product support? Time to move
>>> off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
>>> use, and manage than apps on traditional platforms. Sign up for the Lotus
>>> Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
>>> _______________________________________________
>>> Devil-linux-develop mailing list
>>> Dev...@li...
>>> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
>>>
>>
>
>
>
> --
>
> Regards
>   Heiko Zuerker
>   http://www.devil-linux.org
>
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>
>
>
> ------------------------------------------------------------------------------
> What happens now with your Lotus Notes apps - do you make another costly
> upgrade, or settle for being marooned without product support? Time to move
> off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
> use, and manage than apps on traditional platforms. Sign up for the Lotus
> Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
> _______________________________________________
> Devil-linux-develop mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
>

Hey,

this is weird.
It's not finding the iconv library, but that's a mandatory install as  
part of the build.

Which host OS are you using?
Could you look into this:  
http://www.devil-linux.org/documentation/1.4.x/ch03s05.html

Heiko

Quoting mailing dl2 <mai...@gm...>:

> Hello,
>
> The install file is now attached.
>
> Regards.
>
> 2010/12/7 Heiko Zuerker <he...@zu...>:
>> Quoting mailing dl2 <mai...@gm...>:
>>
>>> Hello,
>>>
>>> It was attached to my mail.
>>
>> Oops didn't see it.
>> Anyway, you attached the wrong file (both times ;-) ), you sent the
>> 'build' instead of the 'install' log.
>>
>> Please send /usr/src/lfssystem//build/tmp/LOGS/install/minicom
>>
>> --
>>
>> Regards
>>   Heiko Zuerker
>>   http://www.devil-linux.org
>>
>>
>> ----------------------------------------------------------------
>> This message was sent using IMP, the Internet Messaging Program.
>>
>>
>>
>> ------------------------------------------------------------------------------
>> What happens now with your Lotus Notes apps - do you make another costly
>> upgrade, or settle for being marooned without product support? Time to move
>> off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
>> use, and manage than apps on traditional platforms. Sign up for the Lotus
>> Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
>> _______________________________________________
>> Devil-linux-develop mailing list
>> Dev...@li...
>> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
>>
>



-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Hello,

The install file is now attached.

Regards.

2010/12/7 Heiko Zuerker <he...@zu...>:
> Quoting mailing dl2 <mai...@gm...>:
>
>> Hello,
>>
>> It was attached to my mail.
>
> Oops didn't see it.
> Anyway, you attached the wrong file (both times ;-) ), you sent the
> 'build' instead of the 'install' log.
>
> Please send /usr/src/lfssystem//build/tmp/LOGS/install/minicom
>
> --
>
> Regards
>   Heiko Zuerker
>   http://www.devil-linux.org
>
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>
>
>
> ------------------------------------------------------------------------------
> What happens now with your Lotus Notes apps - do you make another costly
> upgrade, or settle for being marooned without product support? Time to move
> off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
> use, and manage than apps on traditional platforms. Sign up for the Lotus
> Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
> _______________________________________________
> Devil-linux-develop mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
>