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

Dr. Alberto Benati wrote:
> Very long time ....
> 
> I test DL 1.3.5 (8 May 2008) with all pack selected.
> I update with:

The list of packages I haven't updated yet:
> arpwatch-2.1a14PATCH.tar.bz2  
> p7zip_4.57-libun7zip.patch.bz2
> awstats-6.8.tar.gz            
> p7zip_4.57_src_all.tar.bz2
> e2fsprogs-1.40.3.tar.gz       
> php-5.2.6.tar.bz2
> ImageMagick-6.3.9-10.tar.bz2
> scponly-20080308.tgz
> iptstate-2.2.1.tar.bz2        
> shorewall-common-4.0.10.1.tar.bz2
> shorewall-perl-4.0.10.1.tar.bz2
> shorewall-shell-4.0.10.tar.bz2
> mysql-5.0.51b.tar.gz          
> nut-2.2.1.tar.gz              
Ok, I'll do it during the next round of updating.


> 
> Compile but not test if all pack works.
> 
> - Upgrade src: lm-sensors-3.0.1
>   Upgrade script: lm-sensors (attach)
>   Remove src/script: i2c and sysfsutils (www.lm-sensors.org/wiki/Download)
Hm... As far as I know lm-sensors-3 and i2c are different packages now. Have I
understood you correctly that you suggest to exclude i2c from DL? Not update and
keep it as a different package but exactly remove?


> - Error in compile libun7zip
>   Upgrade src: p7zip_4.57 and p7zip_4.57-libun7zip (attach)
>   Upgrade script: p7zip (attach)
OK. I'll try it.

> 
> - Error in pptp-patches for 2.6.24
>   Upgrade src (attach), soon for kernel 2.6.25
....
> - Error in rp-pppoe
Is it the consequence of pptp-patches for 2.6.24?

> 
> - Error in RPM. It makes sense to take this?
I think we may neglect that.

> 
> - Error in portslave. One radiusclient.h is in ppp but there are many many
> errors. Maybe install old radiusclient pack?
Portslave is a troglodytic package. I'm not sure we have to spent our time for
adapting it.

> 
> - Error in eagle-usb. It's based an old kernel (view configure). Try to
> substitute version.h with utsrelease.h but many many errors.
Hm... Probably we should check the project status and if it's a dead project -
disable/remove it.

> 
> - kid requirement for sagator (for webq service)
>   New src: kid-0.9.6.tar.gz
>   New script: kid (attach)
>   Upgrade script: sagator
>   New requirement: kid.requirement.tar.bz2 (attach)
>   + elementtree-1.2.6-20050316.tar.gz
>   + cElementTree-1.0.5-20051216.tar.gz
Will be tested soon.


> 
> 
> Attach (460 KB) in:
> http://econtools.economia.unife.it/devil-linux/devil-linux.1.3.5.tar.gz

I've got it. Thank you!

--
Serge

Hi Guys,

What do You use to collect Netflow on Devil-Linux, i.e. netflow from fprobe?

I'm looking for method to logging netflow in Devil-linux and can't find. I'm 
used sometime netacct but now netacct-mysql is not logging flows, but only 
RRD. It is not sufficient.

I found NNFC, but this package is not present on Devil-Linux. Maybe is need to 
append tool for collect netflow into log files to external analysis.

Any suggestions?

best Regards

Andrzej Odyniec

Hi Heiko,

the shorewall-stuff is working, I've made a new build of my config yesterday with updated shorewall and had no issues.

Kind regards,
Björn Rudner

-----Ursprüngliche Nachricht-----
Von: dev...@li... [mailto:dev...@li...] Im Auftrag von Heiko Zuerker
Gesendet: Mittwoch, 14. Mai 2008 16:05
An: dev...@li...
Betreff: Re: [Devil-linux-develop] software update in DL 1.3


Does anyone have time to look at what Alberto sent?
Seems like he got quite a few more updates.

--

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



Quoting "Dr. Alberto Benati" <be...@ec...>:

> Very long time ....
>
> I test DL 1.3.5 (8 May 2008) with all pack selected.
> I update with:
> arpwatch-2.1a14PATCH.tar.bz2  p7zip_4.57-libun7zip.patch.bz2
> awstats-6.8.tar.gz            p7zip_4.57_src_all.tar.bz2
> e2fsprogs-1.40.3.tar.gz       php-5.2.6.tar.bz2
> gnupg-1.4.9.tar.bz2           samba-3.0.28a.tar.gz
> ImageMagick-6.3.9-10.tar.bz2  scponly-20080308.tgz
> iptstate-2.2.1.tar.bz2        shorewall-common-4.0.10.1.tar.bz2
> libiconv-1.12.tar.gz          shorewall-perl-4.0.10.1.tar.bz2
> libpcap-0.9.8.tar.gz          shorewall-shell-4.0.10.tar.bz2
> libpng-1.2.28.tar.bz2         snort-2.8.1.tar.gz
> mysql-5.0.51b.tar.gz          syslog-ng-2.0.9.tar.gztcpdump-3.9.8.tar.gz
> nut-2.2.1.tar.gz
> openldap-2.4.9.tgz
>

____________________________________________________________________________

baulogis GmbH
Zamdorfer Str. 100
81677 München / Munich
Deutschland / Germany
www.baulogis.com

Geschäftsführer / Managing Director: Thomas Bachmaier
HRB 133832, Amtsgericht München
Ust-ID: DE 212 020 193


Der Inhalt dieser E-Mail ist vertraulich und ausschließlich für den bezeichneten Adressaten (dev...@li...) bestimmt.
Wenn Sie nicht der vorgesehene Adressat dieser E-Mail oder dessen Vertreter sein sollten,
so beachten Sie bitte, dass jede Form der Kenntnisnahme, Veröffentlichung, 
Vervielfältigung oder Wiedergabe des Inhalts dieser E-Mail unzulässig ist.
Bitte setzen Sie sich in diesem Fall mit dem Absender der E-Mail in Verbindung (br...@ba...).

Does anyone have time to look at what Alberto sent?
Seems like he got quite a few more updates.

-- 

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



Quoting "Dr. Alberto Benati" <be...@ec...>:

> Very long time ....
>
> I test DL 1.3.5 (8 May 2008) with all pack selected.
> I update with:
> arpwatch-2.1a14PATCH.tar.bz2  p7zip_4.57-libun7zip.patch.bz2
> awstats-6.8.tar.gz            p7zip_4.57_src_all.tar.bz2
> e2fsprogs-1.40.3.tar.gz       php-5.2.6.tar.bz2
> gnupg-1.4.9.tar.bz2           samba-3.0.28a.tar.gz
> ImageMagick-6.3.9-10.tar.bz2  scponly-20080308.tgz
> iptstate-2.2.1.tar.bz2        shorewall-common-4.0.10.1.tar.bz2
> libiconv-1.12.tar.gz          shorewall-perl-4.0.10.1.tar.bz2
> libpcap-0.9.8.tar.gz          shorewall-shell-4.0.10.tar.bz2
> libpng-1.2.28.tar.bz2         snort-2.8.1.tar.gz
> mysql-5.0.51b.tar.gz          syslog-ng-2.0.9.tar.gztcpdump-3.9.8.tar.gz
> nut-2.2.1.tar.gz
> openldap-2.4.9.tgz
>
> Compile but not test if all pack works.
>
> - Upgrade src: lm-sensors-3.0.1
>   Upgrade script: lm-sensors (attach)
>   Remove src/script: i2c and sysfsutils (www.lm-sensors.org/wiki/Download)
>
> - Error in compile libun7zip
>   Upgrade src: p7zip_4.57 and p7zip_4.57-libun7zip (attach)
>   Upgrade script: p7zip (attach)
>
> - Error in pptp-patches for 2.6.24
>   Upgrade src (attach), soon for kernel 2.6.25
>
> - Error in RPM. It makes sense to take this?
>
> - Error in portslave. One radiusclient.h is in ppp but there are many many
> errors. Maybe install old radiusclient pack?
>
> - Error in rp-pppoe
>
> - Error in eagle-usb. It's based an old kernel (view configure). Try to
> substitute version.h with utsrelease.h but many many errors.
>
> - kid requirement for sagator (for webq service)
>   New src: kid-0.9.6.tar.gz
>   New script: kid (attach)
>   Upgrade script: sagator
>   New requirement: kid.requirement.tar.bz2 (attach)
>   + elementtree-1.2.6-20050316.tar.gz
>   + cElementTree-1.0.5-20051216.tar.gz
>
>
> Attach (460 KB) in:
> http://econtools.economia.unife.it/devil-linux/devil-linux.1.3.5.tar.gz
>
>
> Best regards
> Alberto
>
> +--------------------------+
> |   Dott. Alberto Benati   |
> |   System Administrator   |
> |   Faculty of Economics   |
> |  University of  Ferrara  |
> | be...@ec... |
> |  Tel: +39 0532 45 5012   |
> +--------------------------+
>
> ---------- Original Message -----------
> From: Heiko Zuerker <he...@zu...>
> To: dev...@li...
> Sent: Tue, 13 May 2008 08:27:44 -0500
> Subject: Re: [Devil-linux-develop] software update in DL 1.3
>
>> Quoting Bruce Smith <br...@ar...>:
>>
>> >> > Does the compile complete for other arch, such as i586?
>> >> I didn't verify it. Well, I'll start the compilation tonight
>> >
>> > Don't bother.  I'm sure it'll fail too.
>> >
>> >> > Or do you have to disable netacct-mysql?
>> >> Yes. I checked the error and understood that it's autoconf error  
>> - so, the
>> >> easiest way was just disable it.
>> >
>> > I agree with Heiko that we should remove the package if it's no longer
>> > being maintained.
>> >
>> > I recommend checking in all of your updates, no matter if netacct-mysql
>> > builds or not.
>>
>> Agreed
>>
>> --
>>
>> Regards
>>    Heiko Zuerker
>>    http://www.devil-linux.org
>>
>> ----------------------------------------------------------------
>> This message was sent using IMP, the Internet Messaging Program.
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Microsoft
>> Defy all challenges. Microsoft(R) Visual Studio 2008.
>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>> _______________________________________________
>> Devil-linux-develop mailing list
>> Dev...@li...
>> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
> ------- End of Original Message -------
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Devil-linux-develop mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
>



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

> >> I recommend checking in all of your updates, no matter if netacct-mysql
> >> builds or not.
> > 
> > Agreed
> 
> Done.

Sweet!  I'll start a new compile tonight.  :-)

 - BS

Heiko Zuerker wrote:

>> I recommend checking in all of your updates, no matter if netacct-mysql
>> builds or not.
> 
> Agreed
> 

Done.

--
Serge

Serge Leschinsky wrote:
> Heiko Zuerker wrote:
>> I found a little bit newer version of netacct-mysql, not sure how good it is:
>> http://netacct-mysql.gabrovo.com/download/netacct-mysql-0.79rc2.tar.gz
> 
> Ok, I'll check it and send the result.
> 
The same result for the updated package. I'm disabling netacct-mysql in the
profiles...

--
Serge

Very long time ....

I test DL 1.3.5 (8 May 2008) with all pack selected.
I update with:
arpwatch-2.1a14PATCH.tar.bz2  p7zip_4.57-libun7zip.patch.bz2
awstats-6.8.tar.gz            p7zip_4.57_src_all.tar.bz2
e2fsprogs-1.40.3.tar.gz       php-5.2.6.tar.bz2
gnupg-1.4.9.tar.bz2           samba-3.0.28a.tar.gz
ImageMagick-6.3.9-10.tar.bz2  scponly-20080308.tgz
iptstate-2.2.1.tar.bz2        shorewall-common-4.0.10.1.tar.bz2
libiconv-1.12.tar.gz          shorewall-perl-4.0.10.1.tar.bz2
libpcap-0.9.8.tar.gz          shorewall-shell-4.0.10.tar.bz2
libpng-1.2.28.tar.bz2         snort-2.8.1.tar.gz
mysql-5.0.51b.tar.gz          syslog-ng-2.0.9.tar.gztcpdump-3.9.8.tar.gz
nut-2.2.1.tar.gz              
openldap-2.4.9.tgz

Compile but not test if all pack works.

- Upgrade src: lm-sensors-3.0.1
  Upgrade script: lm-sensors (attach)
  Remove src/script: i2c and sysfsutils (www.lm-sensors.org/wiki/Download)

- Error in compile libun7zip
  Upgrade src: p7zip_4.57 and p7zip_4.57-libun7zip (attach)
  Upgrade script: p7zip (attach)

- Error in pptp-patches for 2.6.24
  Upgrade src (attach), soon for kernel 2.6.25

- Error in RPM. It makes sense to take this?

- Error in portslave. One radiusclient.h is in ppp but there are many many
errors. Maybe install old radiusclient pack?

- Error in rp-pppoe

- Error in eagle-usb. It's based an old kernel (view configure). Try to
substitute version.h with utsrelease.h but many many errors.

- kid requirement for sagator (for webq service)
  New src: kid-0.9.6.tar.gz
  New script: kid (attach)
  Upgrade script: sagator
  New requirement: kid.requirement.tar.bz2 (attach)
  + elementtree-1.2.6-20050316.tar.gz
  + cElementTree-1.0.5-20051216.tar.gz


Attach (460 KB) in:
http://econtools.economia.unife.it/devil-linux/devil-linux.1.3.5.tar.gz


Best regards
Alberto

+--------------------------+
|   Dott. Alberto Benati   |
|   System Administrator   |
|   Faculty of Economics   |
|  University of  Ferrara  |
| be...@ec... |
|  Tel: +39 0532 45 5012   |
+--------------------------+

---------- Original Message -----------
From: Heiko Zuerker <he...@zu...>
To: dev...@li...
Sent: Tue, 13 May 2008 08:27:44 -0500
Subject: Re: [Devil-linux-develop] software update in DL 1.3

> Quoting Bruce Smith <br...@ar...>:
> 
> >> > Does the compile complete for other arch, such as i586?
> >> I didn't verify it. Well, I'll start the compilation tonight
> >
> > Don't bother.  I'm sure it'll fail too.
> >
> >> > Or do you have to disable netacct-mysql?
> >> Yes. I checked the error and understood that it's autoconf error - so, the
> >> easiest way was just disable it.
> >
> > I agree with Heiko that we should remove the package if it's no longer
> > being maintained.
> >
> > I recommend checking in all of your updates, no matter if netacct-mysql
> > builds or not.
> 
> Agreed
> 
> --
> 
> Regards
>    Heiko Zuerker
>    http://www.devil-linux.org
> 
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft 
> Defy all challenges. Microsoft(R) Visual Studio 2008. 
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Devil-linux-develop mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
------- End of Original Message -------

Quoting Bruce Smith <br...@ar...>:

>> > Does the compile complete for other arch, such as i586?
>> I didn't verify it. Well, I'll start the compilation tonight
>
> Don't bother.  I'm sure it'll fail too.
>
>> > Or do you have to disable netacct-mysql?
>> Yes. I checked the error and understood that it's autoconf error - so, the
>> easiest way was just disable it.
>
> I agree with Heiko that we should remove the package if it's no longer
> being maintained.
>
> I recommend checking in all of your updates, no matter if netacct-mysql
> builds or not.

Agreed

-- 

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



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

> > Does the compile complete for other arch, such as i586?  
> I didn't verify it. Well, I'll start the compilation tonight

Don't bother.  I'm sure it'll fail too.

> > Or do you have to disable netacct-mysql?
> Yes. I checked the error and understood that it's autoconf error - so, the
> easiest way was just disable it.

I agree with Heiko that we should remove the package if it's no longer
being maintained.  

I recommend checking in all of your updates, no matter if netacct-mysql
builds or not.

 - BS

Heiko Zuerker wrote:
> I found a little bit newer version of netacct-mysql, not sure how good it is:
> http://netacct-mysql.gabrovo.com/download/netacct-mysql-0.79rc2.tar.gz

Ok, I'll check it and send the result.

--
Serge

Bruce Smith wrote:
>> I updated several packages to fix some issues in DL and final list for update is
> ...
>> Fresh compilation fails in one place (default config, but arch = i686):
>>
>> netacct-mysql (checking "for mysql"... configure: error: "mysql headers"
>> ./configure: line 5663: exit: /usr/lib/include: numeric argument required
>>
>> Do you have any objections against update? If now, I'll do it within Wed-Thu.
> 
> Does the compile complete for other arch, such as i586?  
I didn't verify it. Well, I'll start the compilation tonight

> Or do you have to disable netacct-mysql?
Yes. I checked the error and understood that it's autoconf error - so, the
easiest way was just disable it.

--
Serge

I found a little bit newer version of netacct-mysql, not sure how good it is:
http://netacct-mysql.gabrovo.com/download/netacct-mysql-0.79rc2.tar.gz

This package doesn't seem to get maintained anymore.
Maybe debian is still creating patches for it, otherwise I leaning  
towards removing it.

-- 

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



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

> Hello,
>
> I updated several packages to fix some issues in DL and final list  
> for update is
> below:
>
> src/bridge-utils-1.4.tar.gz
> src/conntrack-tools-20080507.tar.bz2
> src/cryptsetup-1.0.6.tar.bz2
> src/cyrus-imapd-2.3.12p2.tar.gz
> src/device-mapper.1.02.25.tgz
> src/e1000-8.0.1.tar.gz
> src/e100-3.5.17.tar.gz
> src/freeradius-server-2.0.4.tar.bz2
> src/gnupg-1.4.9.tar.bz2
> src/hdparm-8.6.tar.gz
> src/krb5-1.6.3.tar.gz
> src/libevent-1.4.3-stable.tar.gz
> src/libgcrypt-1.4.1.tar.bz2
> src/libiconv-1.12.tar.gz
> src/libnetfilter_conntrack-20080508.tar.bz2
> src/libnfnetlink-20080508.tar.bz2
> src/libpcap-0.9.8.tar.gz
> src/libpng-1.2.29.tar.bz2
> src/loop-AES-v3.2c.tar.bz2
> src/LVM2.2.02.36.tgz
> src/lzo-2.03.tar.gz
> src/memtest86+-2.01.tar.gz
> src/nmap-4.62.tar.bz2
> src/openl2tp-1.3.tar.gz
> src/open-vm-tools-2008.04.14-87182.tar.gz
> src/patch-2.6.24.7.bz2
> src/patch-o-matic-ng-20080507.tar.bz2
> src/pcre-7.7.tar.bz2
> src/samba-3.0.28a.tar.gz
> src/snort-2.8.1.tar.gz
> src/strongswan-4.2.0.tar.bz2
> src/syslog-ng-2.0.9.tar.gz
> src/tcpdump-3.9.8.tar.gz
> src/util-linux-ng-2.13.1.tar.bz2
> src/vblade-16.tgz
> src/xfsprogs_2.9.8-1.tar.gz
>
> Fresh compilation fails in one place (default config, but arch = i686):
>
> netacct-mysql (checking "for mysql"... configure: error: "mysql headers"
> ./configure: line 5663: exit: /usr/lib/include: numeric argument required
> )
>
>
> Do you have any objections against update? If now, I'll do it within Wed-Thu.
>
> --
> Serge
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Devil-linux-develop mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
>



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

> I updated several packages to fix some issues in DL and final list for update is
...
> Fresh compilation fails in one place (default config, but arch = i686):
>
> netacct-mysql (checking "for mysql"... configure: error: "mysql headers"
> ./configure: line 5663: exit: /usr/lib/include: numeric argument required
> 
> Do you have any objections against update? If now, I'll do it within Wed-Thu.

Does the compile complete for other arch, such as i586?  
Or do you have to disable netacct-mysql?

 - BS

Hello,

I updated several packages to fix some issues in DL and final list for update is
below:

src/bridge-utils-1.4.tar.gz
src/conntrack-tools-20080507.tar.bz2
src/cryptsetup-1.0.6.tar.bz2
src/cyrus-imapd-2.3.12p2.tar.gz
src/device-mapper.1.02.25.tgz
src/e1000-8.0.1.tar.gz
src/e100-3.5.17.tar.gz
src/freeradius-server-2.0.4.tar.bz2
src/gnupg-1.4.9.tar.bz2
src/hdparm-8.6.tar.gz
src/krb5-1.6.3.tar.gz
src/libevent-1.4.3-stable.tar.gz
src/libgcrypt-1.4.1.tar.bz2
src/libiconv-1.12.tar.gz
src/libnetfilter_conntrack-20080508.tar.bz2
src/libnfnetlink-20080508.tar.bz2
src/libpcap-0.9.8.tar.gz
src/libpng-1.2.29.tar.bz2
src/loop-AES-v3.2c.tar.bz2
src/LVM2.2.02.36.tgz
src/lzo-2.03.tar.gz
src/memtest86+-2.01.tar.gz
src/nmap-4.62.tar.bz2
src/openl2tp-1.3.tar.gz
src/open-vm-tools-2008.04.14-87182.tar.gz
src/patch-2.6.24.7.bz2
src/patch-o-matic-ng-20080507.tar.bz2
src/pcre-7.7.tar.bz2
src/samba-3.0.28a.tar.gz
src/snort-2.8.1.tar.gz
src/strongswan-4.2.0.tar.bz2
src/syslog-ng-2.0.9.tar.gz
src/tcpdump-3.9.8.tar.gz
src/util-linux-ng-2.13.1.tar.bz2
src/vblade-16.tgz
src/xfsprogs_2.9.8-1.tar.gz

Fresh compilation fails in one place (default config, but arch = i686):

netacct-mysql (checking "for mysql"... configure: error: "mysql headers"
./configure: line 5663: exit: /usr/lib/include: numeric argument required
)


Do you have any objections against update? If now, I'll do it within Wed-Thu.

--
Serge

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

> Bruce Smith wrote:
>>> IMQ keeps being a pain when we want to upgrade to a newer kernel.
>>> Did anybody play with IFB yet? It's part of the vanilla kernel.
>>>
>>> http://www.linux-foundation.org/en/Net:IFB
>>
>> Do they both do the same thing?  (I haven't used either)
> approximately yes. I'd say what imq is designed for usage together with
> iptables, but ifb - with tc.

I heavily doubt that you're too stupid (looking at the work you did for DL).

>> Is IFB available in the latest DL 1.3 now, in case I want to try it?
> Yes, you can. I tried to create a shaper with IFB some time ago. Probably I'm
> too stupid but after a day of attempts to do it I gave it up and  I  
> made it with
> imq within couples of hours.

I was afraid of something like that.

-- 

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



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

Bruce Smith wrote:
>> IMQ keeps being a pain when we want to upgrade to a newer kernel.
>> Did anybody play with IFB yet? It's part of the vanilla kernel.
>>
>> http://www.linux-foundation.org/en/Net:IFB
> 
> Do they both do the same thing?  (I haven't used either)
approximately yes. I'd say what imq is designed for usage together with
iptables, but ifb - with tc.

> 
> Is IFB available in the latest DL 1.3 now, in case I want to try it?
Yes, you can. I tried to create a shaper with IFB some time ago. Probably I'm
too stupid but after a day of attempts to do it I gave it up and  I made it with
imq within couples of hours.

--
Serge

> IMQ keeps being a pain when we want to upgrade to a newer kernel.
> Did anybody play with IFB yet? It's part of the vanilla kernel.
>
> http://www.linux-foundation.org/en/Net:IFB

Do they both do the same thing?  (I haven't used either)

Is IFB available in the latest DL 1.3 now, in case I want to try it?

 - BS

Hey guys,

IMQ keeps being a pain when we want to upgrade to a newer kernel.
Did anybody play with IFB yet? It's part of the vanilla kernel.

http://www.linux-foundation.org/en/Net:IFB

-- 

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





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

Duh, I could have thought of that too...
Let me ask the question.

-- 

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



Quoting Bruce Smith <bw...@re...>:

> Is it worth asking the question on the list (about what it means for grsec)?
>
> Or shall we just dump grsec now?  :-)
>
>  - BS
>
>
>>  not sure if you guys are following the grsecurity mailing list, but it
>> seems PAX may soon not be adapted for new kernels anymore.
>>  I'm not sure what the game plan is going to be from our side if this really
>> happens. Brad did not mention what this would mean for grsecurity.
>>
>>  --
>>
>>  Regards
>>   Heiko Zuerker
>>   http://www.devil-linux.org
>>
>>
>>  ----------------------------------------------------------------
>>  This message was sent using IMP, the Internet Messaging Program.
>>
>>
>>
>> ---------- Forwarded message ----------
>> From: pag...@fr...
>> To: grs...@gr...
>> Date: Wed, 07 May 2008 03:27:43 +0200
>> Subject: Re: [grsec] grsecurity 2.1.11 released for Linux 2.4.36.2/2.6.24.4
>> On 14 Apr 2008 at 21:07, Brad Spengler wrote:
>>
>>  > It is not clear if the PaX Team will be able to continue supporting
>>  > future versions of the 2.6 kernels, given their rapid rate of release
>>  > and the incredible amount of work that goes into porting such a
>>  > low-level enhancement to the kernel (especially now in view of the
>>  > reworking of the i386/x86-64 trees). It may be necessary that grsecurity
>>  > instead track the Ubuntu LTS kernel so that users can have a stable
>>  > kernel with up-to-date security fixes. I will update this page when a
>>  > final decision has been reached.
>>  >
>>  > In the meantime, please email pag...@fr... and let him know how
>>  > much you appreciate the hard work he has put in for the past 8 years.
>>  > The accomplishments of the PaX Team have extended far beyond just Linux,
>>  > and have today found their way into all mainstream operating systems.
>>
>>  now that i released a new test patch for 2.6.25.1, i'd like to address
>>  the above.
>>
>>  first of all, thank you all who emailed me during this time, i hope
>>  you'll forgive me for not responding to everyone individually, it'd
>>  take too much time and repetition, so i'd rather answer here. if
>>  there're questions left unanswered, just ask again (preferably in
>>  public).
>>
>>  as spender said, there're several factors that make the continued
>>  maintenance of PaX harder than necessary or maybe even unfeasible
>>  given the circumstances.
>>
>>  for me the most important one is my free time i can spend on this
>>  project, which has always been a delicate balance between family
>>  and friends and other things that needed my attention. as long as
>>  this time was enough to cover the necessary work needed for a forward
>>  port, i did the work.
>>
>>  things have changed on both fronts though in that both my time i
>>  can spend on this will soon decrease and the effort needed has
>>  increased quite a lot as well with the inevitable consequence that
>>  the development (or let's just stick to maintenance) of PaX have
>>  slowed to a crawl. so lest things change for the better, future
>>  releases may not happen at all or rather irregularly.
>>
>>  many of you asked how things can change for the better. given the
>>  above, there're a few ways but frankly, i don't think any of it is
>>  realistic.
>>
>>  one way is to increase the time spent on PaX. this can come from
>>  either me or someone else. for me it's pretty much not possible
>>  because if there's anything i want to spend less and less my time
>>  on then it's everything computer security related. it was fun and
>>  interesting at the turn of the millennium, but not anymore. so no
>>  amount of funding or moral support will help here i'm afraid. on
>>  the other hand the door is open for other adventurous souls to take
>>  over, although i doubt anyone will show up. note that helping with
>>  a few chunks or trivial rejects is of little help to me since, well,
>>  i can do that easily too. the really big work is always related to
>>  core changes done in PaX and porting those requires very deep
>>  understanding of both the kernel and PaX (and a lot of time to debug
>>  the inevitable bugs).
>>
>>  the other way is to decrease the effort needed for a forward port.
>>  this in turn would require a change in the current linux development
>>  model which is not going to happen anytime soon. one could also track
>>  the vanilla tree more often/closely, but then we're back at the free
>>  time problem (most of which would be a complete waste since as end
>>  users you're really interested in the patch that works with a release,
>>  not arbitrary git snapshots).
>>
>>  so there you have it, i know it looks rather bleak, but c'est la vie.
>>
>>  cheers,
>>   PaX Team
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
> Don't miss this year's exciting event. There's still time to save $100.
> Use priority code J8TL2D2.
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> Devil-linux-develop mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
>



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

Is it worth asking the question on the list (about what it means for grsec)?

Or shall we just dump grsec now?  :-)

 - BS


>  not sure if you guys are following the grsecurity mailing list, but it
> seems PAX may soon not be adapted for new kernels anymore.
>  I'm not sure what the game plan is going to be from our side if this really
> happens. Brad did not mention what this would mean for grsecurity.
>
>  --
>
>  Regards
>   Heiko Zuerker
>   http://www.devil-linux.org
>
>
>  ----------------------------------------------------------------
>  This message was sent using IMP, the Internet Messaging Program.
>
>
>
> ---------- Forwarded message ----------
> From: pag...@fr...
> To: grs...@gr...
> Date: Wed, 07 May 2008 03:27:43 +0200
> Subject: Re: [grsec] grsecurity 2.1.11 released for Linux 2.4.36.2/2.6.24.4
> On 14 Apr 2008 at 21:07, Brad Spengler wrote:
>
>  > It is not clear if the PaX Team will be able to continue supporting
>  > future versions of the 2.6 kernels, given their rapid rate of release
>  > and the incredible amount of work that goes into porting such a
>  > low-level enhancement to the kernel (especially now in view of the
>  > reworking of the i386/x86-64 trees). It may be necessary that grsecurity
>  > instead track the Ubuntu LTS kernel so that users can have a stable
>  > kernel with up-to-date security fixes. I will update this page when a
>  > final decision has been reached.
>  >
>  > In the meantime, please email pag...@fr... and let him know how
>  > much you appreciate the hard work he has put in for the past 8 years.
>  > The accomplishments of the PaX Team have extended far beyond just Linux,
>  > and have today found their way into all mainstream operating systems.
>
>  now that i released a new test patch for 2.6.25.1, i'd like to address
>  the above.
>
>  first of all, thank you all who emailed me during this time, i hope
>  you'll forgive me for not responding to everyone individually, it'd
>  take too much time and repetition, so i'd rather answer here. if
>  there're questions left unanswered, just ask again (preferably in
>  public).
>
>  as spender said, there're several factors that make the continued
>  maintenance of PaX harder than necessary or maybe even unfeasible
>  given the circumstances.
>
>  for me the most important one is my free time i can spend on this
>  project, which has always been a delicate balance between family
>  and friends and other things that needed my attention. as long as
>  this time was enough to cover the necessary work needed for a forward
>  port, i did the work.
>
>  things have changed on both fronts though in that both my time i
>  can spend on this will soon decrease and the effort needed has
>  increased quite a lot as well with the inevitable consequence that
>  the development (or let's just stick to maintenance) of PaX have
>  slowed to a crawl. so lest things change for the better, future
>  releases may not happen at all or rather irregularly.
>
>  many of you asked how things can change for the better. given the
>  above, there're a few ways but frankly, i don't think any of it is
>  realistic.
>
>  one way is to increase the time spent on PaX. this can come from
>  either me or someone else. for me it's pretty much not possible
>  because if there's anything i want to spend less and less my time
>  on then it's everything computer security related. it was fun and
>  interesting at the turn of the millennium, but not anymore. so no
>  amount of funding or moral support will help here i'm afraid. on
>  the other hand the door is open for other adventurous souls to take
>  over, although i doubt anyone will show up. note that helping with
>  a few chunks or trivial rejects is of little help to me since, well,
>  i can do that easily too. the really big work is always related to
>  core changes done in PaX and porting those requires very deep
>  understanding of both the kernel and PaX (and a lot of time to debug
>  the inevitable bugs).
>
>  the other way is to decrease the effort needed for a forward port.
>  this in turn would require a change in the current linux development
>  model which is not going to happen anytime soon. one could also track
>  the vanilla tree more often/closely, but then we're back at the free
>  time problem (most of which would be a complete waste since as end
>  users you're really interested in the patch that works with a release,
>  not arbitrary git snapshots).
>
>  so there you have it, i know it looks rather bleak, but c'est la vie.
>
>  cheers,
>   PaX Team

Hey,

not sure if you guys are following the grsecurity mailing list, but it  
seems PAX may soon not be adapted for new kernels anymore.
I'm not sure what the game plan is going to be from our side if this  
really happens. Brad did not mention what this would mean for  
grsecurity.

-- 

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


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

> >>> I ran a fresh compile after the latest updates, and nagios-plugins
> >>> aborted.  Compatibility problem with the new kernel?  Anyone else have
> >>> this problem?
> > Not, it isn't a kernel. It's postgres update. I'll try to fix it.
> 
> Fixed.

Yes it is.  Thanks!!!  :-)

 - BS

Serge Leschinsky wrote:

>>> I ran a fresh compile after the latest updates, and nagios-plugins
>>> aborted.  Compatibility problem with the new kernel?  Anyone else have
>>> this problem?
> Not, it isn't a kernel. It's postgres update. I'll try to fix it.

Fixed.

--
Serge

Serge Leschinsky wrote:
> Bruce Smith wrote:
>> I ran a fresh compile after the latest updates, and nagios-plugins
>> aborted.  Compatibility problem with the new kernel?  Anyone else have
>> this problem?
Not, it isn't a kernel. It's postgres update. I'll try to fix it.

> check_pgsql.c:71: error: 'NAMEDATALEN' undeclared here (not in a function)

--
Serge