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

Hey,

I never used another LiveCD as build environment. 

You do not need to turn on the compiler in DL in order to use it as a build
system. Keep in mind that DL uses a precompiled lfssystem (the tarball on
the ftp server), in order to have a controlled build environment. Everything
you need is in there.

Heiko

-----Original Message-----
From: Andrzej Odyniec [mailto:an...@ma...] 
Sent: Friday, February 20, 2009 9:51 AM
To: dev...@li...
Subject: Re: [Devil-linux-develop] DL as build enviroment

Heiko Zuerker wrote:
> You cannot use the standard DL version for building DL, since some of the
> security features (especially grsecurity) will not allow some compiles to
> finish.
> 
> But:
> You could compile a new DL version without grsecurity and use that. Of
> course I wouldn't hook that box up to the internet.... ;-)

Thanks, Heiko.

This means, that I need two versions of Devil: one for normal work on my 
routers and another for base system to build process.

I understand, switching off grsecurity and switching on development tools 
(e.g. compiler) is sufficient to run succesfully build process?

And maybe You has suggestions for choose other, ready to use, LiveCD Linux 
distribution working as base system? Any experiences?

Regards

-- 
Andrzej Odyniec

<an...@ma...>
Rada Nadzorcza Macrologic SA
ul. Chroscickiego 49, 02-414 Warszawa
tel. +48(22)8637681x132, fax: +48(22)8639861
ul. Jagiellonska 36, 03-719 Warszawa
tel. +48(22)5118115, fax: +48(22)5118117

----------------------------------------------------------------------------
--
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Devil-linux-develop mailing list
Dev...@li...
https://lists.sourceforge.net/lists/listinfo/devil-linux-develop

Heiko Zuerker wrote:
> You cannot use the standard DL version for building DL, since some of the
> security features (especially grsecurity) will not allow some compiles to
> finish.
> 
> But:
> You could compile a new DL version without grsecurity and use that. Of
> course I wouldn't hook that box up to the internet.... ;-)

Thanks, Heiko.

This means, that I need two versions of Devil: one for normal work on my 
routers and another for base system to build process.

I understand, switching off grsecurity and switching on development tools 
(e.g. compiler) is sufficient to run succesfully build process?

And maybe You has suggestions for choose other, ready to use, LiveCD Linux 
distribution working as base system? Any experiences?

Regards

-- 
Andrzej Odyniec

<an...@ma...>
Rada Nadzorcza Macrologic SA
ul. Chroscickiego 49, 02-414 Warszawa
tel. +48(22)8637681x132, fax: +48(22)8639861
ul. Jagiellonska 36, 03-719 Warszawa
tel. +48(22)5118115, fax: +48(22)5118117

You cannot use the standard DL version for building DL, since some of the
security features (especially grsecurity) will not allow some compiles to
finish.

But:
You could compile a new DL version without grsecurity and use that. Of
course I wouldn't hook that box up to the internet.... ;-)

Heiko

-----Original Message-----
From: Andrzej Odyniec [mailto:an...@ma...] 
Sent: Friday, February 20, 2009 6:43 AM
To: Devil-Linux Developer Mailinglist
Subject: [Devil-linux-develop] DL as build enviroment

Hi,

I think, Devil Linux is used (can be used?) as build environment for 
Devil-Linux itself. How You are configuring, compiling and build Devil-Linux

for using it as build environment in the next build?

Regards

-- 
Andrzej Odyniec

<an...@ma...>
Rada Nadzorcza Macrologic SA
ul. Chroscickiego 49, 02-414 Warszawa
tel. +48(22)8637681x132, fax: +48(22)8639861
ul. Jagiellonska 36, 03-719 Warszawa
tel. +48(22)5118115, fax: +48(22)5118117


----------------------------------------------------------------------------
--
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Devil-linux-develop mailing list
Dev...@li...
https://lists.sourceforge.net/lists/listinfo/devil-linux-develop

Hi,

I think, Devil Linux is used (can be used?) as build environment for 
Devil-Linux itself. How You are configuring, compiling and build Devil-Linux 
for using it as build environment in the next build?

Regards

-- 
Andrzej Odyniec

<an...@ma...>
Rada Nadzorcza Macrologic SA
ul. Chroscickiego 49, 02-414 Warszawa
tel. +48(22)8637681x132, fax: +48(22)8639861
ul. Jagiellonska 36, 03-719 Warszawa
tel. +48(22)5118115, fax: +48(22)5118117

Heiko Zuerker wrote:
> Quoting Serge Leschinsky <fi...@in...>:
> 
>> Heiko Zuerker wrote:
>>
>>> Yes I tried the bootcd.iso.new.
>>> It seemed to have replaced all files correctly, but had trouble
>>> finding the iso image later. As far as I remember it actually said it
>>> found it and then failed. Not sure when I can test it again.
>> OK. Let's wait another case.
I think I've found the reason of the failure (at least one :-) )
It's migration from initrd to initramfs - as we didn't update boot loader config
file, parameters "root=xxx", "init=xxx" became invalid.... It causes boot
failure.  Will we fix it?

>>> You can remount the partition in rw mode:
>>> mount -o remount, rw /var/adm/boot    (Or whatever the path was).
>>> That's how I upload the new iso image. 
>>>
>> Yes, I missed that. This code is in pre_init file. I tried several  
>> times, but it
>> seems not working with INITRAMFS (after switch_root). Would you mind  
>> if I move
>> this feature to linuxrc?
> 
> As always, do whatever you deem necessary. As long as it works  
> afterwards.... ;-)

 :-)
Done. Verified on initramfs and initrd. Seems to be working.

--
Sincerely,
Serge

Quoting Serge Leschinsky <fi...@in...>:

> Heiko Zuerker wrote:
>
>> Yes I tried the bootcd.iso.new.
>> It seemed to have replaced all files correctly, but had trouble
>> finding the iso image later. As far as I remember it actually said it
>> found it and then failed. Not sure when I can test it again.
> OK. Let's wait another case.
>
>
>> You can remount the partition in rw mode:
>> mount -o remount, rw /var/adm/boot    (Or whatever the path was).
>> That's how I upload the new iso image.
>>
> Yes, I missed that. This code is in pre_init file. I tried several  
> times, but it
> seems not working with INITRAMFS (after switch_root). Would you mind  
> if I move
> this feature to linuxrc?

As always, do whatever you deem necessary. As long as it works  
afterwards.... ;-)


-- 

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


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

Heiko Zuerker wrote:

> Yes I tried the bootcd.iso.new.
> It seemed to have replaced all files correctly, but had trouble  
> finding the iso image later. As far as I remember it actually said it  
> found it and then failed. Not sure when I can test it again.
OK. Let's wait another case.


> You can remount the partition in rw mode:
> mount -o remount, rw /var/adm/boot    (Or whatever the path was).
> That's how I upload the new iso image.
> 
Yes, I missed that. This code is in pre_init file. I tried several times, but it
seems not working with INITRAMFS (after switch_root). Would you mind if I move
this feature to linuxrc?

--
Serge

Quoting Serge Leschinsky <fi...@in...>:

> Heiko Zuerker wrote:
>
>> There seems to another problem with the booting from flash (in my case
>> a IDE DIM). I tried to upgrade my firewall last weekend and it wasn't
>> able to boot after it replaced the bootcd.iso. I didn't have time to
>> debug why it failed.
>>
> Oops.... Really bad news. Did you update DL by initrd updater, i.e. uploaded
> bootcd.iso.new ? It may happen if the kernel/initrd/image are not  
> coherent, from
> different builds for example. I tested update process with IDE-CF  
> adapter, so in
> general it works. However, hardware differences or other reasons may  
> cause the
> boot failure. The error messages are not suppressed and I hope they will help
> during investigations. It will be great if the testing will be  
> produced thoroughly.
>
> There is still a big (?) problem with accessing to the partition  
> where DL image
> is. I don't know how to get access from a working system to the  
> partition if DL
> was started not from RAM. Any ideas?
>
> Another problem is upgrade from previous versions. Due to a lot of  
> changes most
> probably it will not work automatically, so manual update is highly  
> recommended.

Yes I tried the bootcd.iso.new.
It seemed to have replaced all files correctly, but had trouble  
finding the iso image later. As far as I remember it actually said it  
found it and then failed. Not sure when I can test it again.

You can remount the partition in rw mode:
mount -o remount, rw /var/adm/boot    (Or whatever the path was).
That's how I upload the new iso image.

-- 

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


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

Heiko Zuerker wrote:

> There seems to another problem with the booting from flash (in my case  
> a IDE DIM). I tried to upgrade my firewall last weekend and it wasn't  
> able to boot after it replaced the bootcd.iso. I didn't have time to  
> debug why it failed.
> 
Oops.... Really bad news. Did you update DL by initrd updater, i.e. uploaded
bootcd.iso.new ? It may happen if the kernel/initrd/image are not coherent, from
different builds for example. I tested update process with IDE-CF adapter, so in
general it works. However, hardware differences or other reasons may cause the
boot failure. The error messages are not suppressed and I hope they will help
during investigations. It will be great if the testing will be produced thoroughly.

There is still a big (?) problem with accessing to the partition where DL image
is. I don't know how to get access from a working system to the partition if DL
was started not from RAM. Any ideas?

Another problem is upgrade from previous versions. Due to a lot of changes most
probably it will not work automatically, so manual update is highly recommended.

Thanks,
Serge

Quoting Serge Leschinsky <fi...@in...>:

> Hi Heiko,
>
> I know about two problems:
> the first is patch-o-matic (it has been changed considerably)
> the second is init script for ntop. I was able to start it manually - very
> roughly, without configs etc but it doesn't work out-of-the-box.
>
> I've already made some tests to adjust p-o-m, so hopefully it will be fixed
> shortly. Not sure about ntop, because I don't use it...

Yeah I'm not using ntop either.

There seems to another problem with the booting from flash (in my case  
a IDE DIM). I tried to upgrade my firewall last weekend and it wasn't  
able to boot after it replaced the bootcd.iso. I didn't have time to  
debug why it failed.

-- 

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


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

Hi Heiko,

I know about two problems:
the first is patch-o-matic (it has been changed considerably)
the second is init script for ntop. I was able to start it manually - very
roughly, without configs etc but it doesn't work out-of-the-box.

I've already made some tests to adjust p-o-m, so hopefully it will be fixed
shortly. Not sure about ntop, because I don't use it...

--
Sincerely,
Serge

Heiko Zuerker wrote:
> Hey guys,
> 
> do you think we're getting close enough to rename 1.3 to 1.4rc1 ?
> The one thing  I was hoping for was adding a newer gcc, but I don't  
> think I'll have time for that anytime soon. Implementing it takes a  
> lot of time because of all the patches and security features.
> Are you guys aware of anything still missing or broken?
> Do you have something in the queue which you would really like to add?
> 

Here is the net-tools patch. It is trivial, and it gives you
IPv6-enabled ifconfig and route for free (I was afraid there was a
dependency issue but there is none as far as I can tell).

-- 
Arnaud

Heiko Zuerker <he...@zu...> writes:

> Yes I do remember you, but I have to admit I forgot about the patch.
> Seems like I really need to go through my DL ToDo folder. ;-)
>
> Sorry about forgetting your patch!

You didn't forget about anything, I guess everything interesting I
sent you is in the init scripts now. :-) The last remaining bit is the
net-tools config, I have not had time to check it actually works yet.

-- 
Arnaud

Hey,

Quoting Arnaud Gomes-do-Vale <Arn...@ir...>:

> Hi,
>
> Don't know if you remember me, I sent you a few IPv6-related patches a
> few years ago.

Yes I do remember you, but I have to admit I forgot about the patch.
Seems like I really need to go through my DL ToDo folder. ;-)

Sorry about forgetting your patch!

-- 

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


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

Hi,

Don't know if you remember me, I sent you a few IPv6-related patches a
few years ago.

Heiko Zuerker <he...@zu...> writes:

> Do you have something in the queue which you would really like to add?

I have a two-line patch for enabling IPv6 in net-tools (basically just
setting the INET6 options to 1 in its config files). I am building the
latest CVS with this tiny patch right now.

-- 
Arnaud

Hey guys,

do you think we're getting close enough to rename 1.3 to 1.4rc1 ?
The one thing  I was hoping for was adding a newer gcc, but I don't  
think I'll have time for that anytime soon. Implementing it takes a  
lot of time because of all the patches and security features.
Are you guys aware of anything still missing or broken?
Do you have something in the queue which you would really like to add?

-- 

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


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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi, all!

I had the need for Wlan support for zydas based usb-adapters,
the driver is already included, but the firmware files are missing.

Here is the custom script (zd1211) to include it in DL.
Firmware for zydas can be found here.

> > http://sourceforge.net/project/showfiles.php?group_id=129083

The next i was looking for, was a tool to connect to
a WPA2 device.
Unfortunately there is no tool included right now.
I grabbed wpa_supplicant and compiled it for my custom-DL.
A default wpa_supplicant configuration file goes to /etc
After setting the right network etc. it works fine for me.

I think there are (maybe) a few more people who want to use wlan
with DL, so i attached my scripts - feel free to add them in the
next release, if you find them useful.

I don't know, if it is a good idea to implement wlan support for
a firewall distro - especially when you know about the last findings
about WPA (TKIP) protection, but as always in DL - you have the choice
to use it or not  :-)
Any opinions?

Oliver Niesner


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFJfkNz724ZL5LNhNcRAj7lAJ9xoMPhk+2VD2ad9EJNFvrYOtx3hQCfdoFp
OQ/roC+hdEqHD07TFhLKKiE=
=Nro8
-----END PGP SIGNATURE-----

Heiko Zuerker wrote:
> Quoting Serge Leschinsky <fi...@in...>:
>> Looks like /etc/ntp/step-tickers is not from the original ntp package and is
>> used in several distributions as an additional file/setting. Is it  
>> necessary to
>> hold that in DL if we can make preliminary synchronization just from  
>> /etc/ntp.conf ?
> 
> No clue. As always: do whatever you deem necessary. :)
> 
OK. Thanks! :-)

--
Serge

Oliver Niesner:
> I had the same problems when i tried to compile the development release.
> 
> It is very useful to set the following option in your .config file:
> 
> CONFIG_DISABLELOGGING=y		(yes, the naming of this option is extremly weird!)
> 
> It is confusing, but this ENABLES logging during compile.

Enables to console... but disables logging to files in directory 
/build/tmp/LOGS/... I think, cause of this is named DISABLELOGGING

> This is important when you have to answer some questions about new Kernel features,
> which causes the buildprocess seem to "hang" because you don't answer the question(s).

I solve this looking on compilation process on one PuTTY screen and when 
"hangs", then on second screen I display according log file, i.e.

tail -f /usr/src/lfssystem/build/tmp/LOGS/build/grsecurity

and answer on the first screen to the questions on second :)

Additionally I have logs in files and I can reference to this files, when some 
phase fails.

> After a complete remove of my lfssystem and enabling the above option, my setup build
> nicly and i have now a fresh DL-1.3.7 ;-)
> 
> Hope that helps,

Thanks, Oliver.

This time problem was solved by the hint from Heiko.

This new Heiko option "CONFIG_GCC_CPU=" was by default set empty in .config

Setting it to the CONFIG_GCC_CPU=i586 solved this problem and full build 
process ended some minutes ago. Now I run make install.

Regards

-- 
Andrzej Odyniec

<an...@ma...>
Rada Nadzorcza Macrologic SA
ul. Chroscickiego 49, 02-414 Warszawa
tel. +48(22)8637681x132, fax: +48(22)8639861
ul. Jagiellonska 36, 03-719 Warszawa
tel. +48(22)5118115, fax: +48(22)5118117

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Andrzej Odyniec schrieb:
> Hi,
> 
> Maybe it is temporary, but some days ago build stopped on ntop and after 
> updates on Jan 12 build stops on new binutils? How do You think? maybe my 
> compiler is to old?

I had the same problems when i tried to compile the development release.

It is very useful to set the following option in your .config file:

CONFIG_DISABLELOGGING=y		(yes, the naming of this option is extremly weird!)

It is confusing, but this ENABLES logging during compile.

This is important when you have to answer some questions about new Kernel features,
which causes the buildprocess seem to "hang" because you don't answer the question(s).

After a complete remove of my lfssystem and enabling the above option, my setup build
nicly and i have now a fresh DL-1.3.7 ;-)

Hope that helps,

Oliver




-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with CentOS - http://enigmail.mozdev.org

iD8DBQFJbKbF724ZL5LNhNcRAg1sAJ0aThP46AV8NX7+wfUD+gJnpzwNHwCfRQ3S
R93W8QUqdUq0GtgPnC+p4uM=
=uOT2
-----END PGP SIGNATURE-----

Quoting Serge Leschinsky <fi...@in...>:
> Looks like /etc/ntp/step-tickers is not from the original ntp package and is
> used in several distributions as an additional file/setting. Is it  
> necessary to
> hold that in DL if we can make preliminary synchronization just from  
> /etc/ntp.conf ?

No clue. As always: do whatever you deem necessary. :)

-- 

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


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

Hello,

Looks like /etc/ntp/step-tickers is not from the original ntp package and is
used in several distributions as an additional file/setting. Is it necessary to
hold that in DL if we can make preliminary synchronization just from /etc/ntp.conf ?

Please advice,

--
Serge

--- xntpd       25 Jul 2005 17:16:58 -0000      1.6
+++ xntpd       13 Jan 2009 01:06:41 -0000
@@ -50,7 +50,7 @@
    echo -n "Synchronizing with time server: "
    loadproc /usr/bin/ntpdate -s -b -p 8 -u \
-   `sed -e 's/#.*//' /etc/ntp/step-tickers`
+   $(grep server /etc/ntp.conf | grep -v "^#\|^$\|127\." | awk '{ print $2 }')
  fi
  if [ -f /etc/sysconfig/jail/$PACKAGE_NAME ] && [ "$JAIL_ENABLE" == yes ]; then
    /etc/init.d/jail start $PACKAGE_NAME

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

> Hi,
>
> Maybe it is temporary, but some days ago build stopped on ntop and after
> updates on Jan 12 build stops on new binutils? How do You think? maybe my
> compiler is to old?
>
> I obtain:
>
>> configure:3129: checking for C compiler default output file name
>> configure:3132: gcc -D_FORTIFY_SOURCE=0 -mtune= -march=   conftest.c  >&5
>> cc1: error: missing argument to "-mtune="
>> cc1: error: missing argument to "-march="

I added some additional config to "make menuconfig", you can now  
choose optimizations for specific CPUs under the build configuration.  
Keep in mind that DL doesn't support cross-compiling, you actually  
have to have a compatible CPU in your build machine!

Add this line to your .config:
CONFIG_GCC_CPU=i586

Or change it to whatever you want via make menuconfig. Other then  
i486-i686 is not very well tested, so please provide feedback if you  
run into problems. I finished a full compile with 'k8' and it seems to  
work.

-- 

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


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

Hi,

Maybe it is temporary, but some days ago build stopped on ntop and after 
updates on Jan 12 build stops on new binutils? How do You think? maybe my 
compiler is to old?

I obtain:

> + /build/tmp/binutils-2.18/configure --prefix=/usr --localstatedir=/var --enable-shared --disable-werror
> checking build system type... i586-pc-linux-gnu
> checking host system type... i586-pc-linux-gnu
> checking target system type... i586-pc-linux-gnu
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether ln works... yes
> checking whether ln -s works... yes
> checking for gcc... gcc -D_FORTIFY_SOURCE=0
> checking for C compiler default output file name... configure: error: C compiler cannot create executables
> See `config.log' for more details.

and in /build/tmp/binutils-build/config.log

> configure:3090: checking for C compiler version
> configure:3093: gcc -D_FORTIFY_SOURCE=0 --version </dev/null >&5
> gcc (GCC) 4.1.2
> Copyright (C) 2006 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> 
> configure:3096: $? = 0
> configure:3098: gcc -D_FORTIFY_SOURCE=0 -v </dev/null >&5
> Using built-in specs.
> Target: i686-pc-linux-gnu
> Configured with: ../gcc-4.1.2/configure --prefix=/usr --libexecdir=/usr/lib --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu --enable-languages=c,c++
> Thread model: posix
> gcc version 4.1.2
> configure:3101: $? = 0
> configure:3103: gcc -D_FORTIFY_SOURCE=0 -V </dev/null >&5
> gcc: '-V' must come at the start of the command line
> configure:3106: $? = 1
> configure:3129: checking for C compiler default output file name
> configure:3132: gcc -D_FORTIFY_SOURCE=0 -mtune= -march=   conftest.c  >&5
> cc1: error: missing argument to "-mtune="
> cc1: error: missing argument to "-march="
> configure:3135: $? = 1
> configure: failed program was:
> | /* confdefs.h.  */
> |
> | #define PACKAGE_NAME ""
> | #define PACKAGE_TARNAME ""
> | #define PACKAGE_VERSION ""
> | #define PACKAGE_STRING ""
> | #define PACKAGE_BUGREPORT ""
> | /* end confdefs.h.  */
> |
> | int
> | main ()
> | {
> |
> |   ;
> |   return 0;
> | }
> configure:3174: error: C compiler cannot create executables

Best regards

-- 
Andrzej Odyniec

<an...@ma...>
Rada Nadzorcza Macrologic SA
ul. Chroscickiego 49, 02-414 Warszawa
tel. +48(22)8637681x132, fax: +48(22)8639861
ul. Jagiellonska 36, 03-719 Warszawa
tel. +48(22)5118115, fax: +48(22)5118117

The main FTP Server is available again, I fixed the DNS entry (thanks  
Frank for the IP!).

Sorry for the inconvenience!

-- 

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


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