devil-linux-develop — developer discussions

Re: [Devil-linux-develop] Build error

[<hzu...@ra...>]

On 02/11/2004 11:34:56 AM Arnaud Gomes-do-Vale wrote:
>Hi,
>
>Building current CVS blows on configure for libgcrypt.
>
>executing libgcrypt with option build (in
>/data/build/tmp/libgcrypt-1.1.91)
>.../...
>checking for gpg-error-config... no
>checking for GPG Error - version >= 0.5... no
>configure: error: libgpg-error is needed.
>See ftp://ftp.gnupg.org/gcrypt/libgpg-error/ .
>ERROR
>/data/build/scripts/libgcrypt build failed
>check log file for details
>make: *** [build] Error 1
>root:/data/build#
>
>Config file is attached.


You need to update from CVS and from the FTP Server, the changes are in
there.
(Don't select DDT, it won't compile with the new libgcrypt.)

Heiko

Re: [Devil-linux-develop] Method to send package ?

[Friedrich L. <fl...@fl...>]

Christophe Crier wrote on 11.02.2004 19:43 MET:
> Hello,
> 
> I have terminated my squidguard package but before send you i have one 
> question.
> 
> My mail size is 5.5Mo.
> content:
> 	squidguard 1.2.0 with blacklists
> 	BerkleyDB 3.2.9 and patch

For sources in tar.gz/bz2 and new files packaged as tar.gz/bz2 please send 
a link from where we can download those files.

> 
> Can i follow the 'patch' procedure found in documentation with this mail ?

Patches only for real changes. New files as said before please package into 
an tar.gz/bz2 archive and make it available for download.

For every software you want to add to DL please provide a patch to the file 
LINKS contained in the build directory so we know where we can download 
newer versions if the need arises.

PS: Heiko you might want to add my last remark to the documentation.

-- 
MfG / Regards
Friedrich Lobenstock
____________________________________________________________________
Friedrich Lobenstock                       Linux Services Lobenstock
URL: http://www.lsl.at/                         Email: fl...@fl...
____________________________________________________________________

[Devil-linux-develop] Method to send package ?

[Christophe C. <chr...@he...>]

Hello,

I have terminated my squidguard package but before send you i have one=20
question.

My mail size is 5.5Mo.
content:
	squidguard 1.2.0 with blacklists
	BerkleyDB 3.2.9 and patch

Can i follow the 'patch' procedure found in documentation with this mail ?

Regards

=2D-=20
Christophe Crier
Responsable technique
T=E9l : (+33) 04 42 97 25 71
=46ax : (+33) 04 42 97 25 74
Courriel : chr...@he...
Web : www.heolys.com

Re: [Devil-linux-develop] [Patch] network script

[Friedrich L. <fl...@fl...>]

Ok I've checked-in the following changes to the network script (both for 
1.0.x and 1.1.x).

--- network	31 Dec 2003 21:26:53 -0000	1.27
+++ network	11 Feb 2004 16:57:08 -0000	1.28
@@ -41,3 +41,3 @@

-VLAN=vconfig
+VLAN=/bin/vconfig


-- 
MfG / Regards
Friedrich Lobenstock
____________________________________________________________________
Friedrich Lobenstock                       Linux Services Lobenstock
URL: http://www.lsl.at/                         Email: fl...@fl...
____________________________________________________________________

Re: [Devil-linux-develop] possible change in IPv4 routing configuration syntax

[Friedrich L. <fl...@fl...>]

Arnaud Gomes-do-Vale wrote on 11.02.2004 17:50 MET:
> Friedrich Lobenstock <fl...@fl...> writes:
> 
> 
>>If I change the syntax of ROUTE to match one of IPV6ROUTE (= using '|'
>>instead of ':') then we need to take care of updating configurations
>>from before the change (eg. 1.0.x and 1.1.y y<=2) to the new syntax.
> 
> 
> I know. However, only the ROUTE variable needs be modified, so the
> presence of : in IPv6 routes won't affect the sed lines.

Excatelly (please see subject) that's what I am talking about. Your IPv6 
stuff is in NO way affected - but it creates an urge for a change in the 
IPv4 routing stuff. That change is what I am currently preparing for.

> 
> This begins to sound quite confusing, we should stop arguing when we
> in fact agree. :-)
> 

We totally agree :-)

-- 
MfG / Regards
Friedrich Lobenstock
____________________________________________________________________
Friedrich Lobenstock                       Linux Services Lobenstock
URL: http://www.lsl.at/                         Email: fl...@fl...
____________________________________________________________________

Re: [Devil-linux-develop] possible change in IPv4 routing configuration syntax

[Arnaud Gomes-do-V. <Arn...@ir...>]

Friedrich Lobenstock <fl...@fl...> writes:

> If I change the syntax of ROUTE to match one of IPV6ROUTE (= using '|'
> instead of ':') then we need to take care of updating configurations
> from before the change (eg. 1.0.x and 1.1.y y<=2) to the new syntax.

I know. However, only the ROUTE variable needs be modified, so the
presence of : in IPv6 routes won't affect the sed lines.

This begins to sound quite confusing, we should stop arguing when we
in fact agree. :-)

-- 
Arnaud

Re: [Devil-linux-develop] possible change in IPv4 routing configuration syntax

[Friedrich L. <fl...@fl...>]

Arnaud Gomes-do-Vale wrote on 11.02.2004 17:22 MET:
> Friedrich Lobenstock <fl...@fl...> writes:
> 
> 
>>I know but to keep the confusion down we should have the same syntax
>>for both ROUTE and IPV6ROUTE. That's what I want to do.
> 
> 
> Yes, but upgrades should not be a problem as IPV6ROUTE does not
> currently exist.
> 

If I change the syntax of ROUTE to match one of IPV6ROUTE (= using '|' 
instead of ':') then we need to take care of updating configurations from 
before the change (eg. 1.0.x and 1.1.y y<=2) to the new syntax.

-- 
MfG / Regards
Friedrich Lobenstock
____________________________________________________________________
Friedrich Lobenstock                       Linux Services Lobenstock
URL: http://www.lsl.at/                         Email: fl...@fl...
____________________________________________________________________

Re: [Devil-linux-develop] possible change in IPv4 routing configuration syntax

[Arnaud Gomes-do-V. <Arn...@ir...>]

Friedrich Lobenstock <fl...@fl...> writes:

> I know but to keep the confusion down we should have the same syntax
> for both ROUTE and IPV6ROUTE. That's what I want to do.

Yes, but upgrades should not be a problem as IPV6ROUTE does not
currently exist.

-- 
Arnaud

Re: [Devil-linux-develop] possible change in IPv4 routing configuration syntax

[Friedrich L. <fl...@fl...>]

Bruce Smith wrote on 11.02.2004 16:51 MET:
>>>>From my head I the following could be a possible solution (though not 
>>>>tested yet):
>>>>  sed -e "s/^\(ROUTE.*\):/\0|/"
>>>
>>>Wouldn't that only change the first : to |  ?
>>
>>I will go over it and come back to you when I have a final sed expression.
> 
> My main problem is I know nothing about IPv6, so I don't know what to
> look for.  i.e.  Will a normal IPv6 ROUTE contain legal colons? (:)
> Can you show me a couple example ifcfg files?  For v4 & v6 both?

I will give you the relevant sed expression so don't worry.

-- 
MfG / Regards
Friedrich Lobenstock
____________________________________________________________________
Friedrich Lobenstock                       Linux Services Lobenstock
URL: http://www.lsl.at/                         Email: fl...@fl...
____________________________________________________________________

Re: [Devil-linux-develop] possible change in IPv4 routing configuration syntax

[Friedrich L. <fl...@fl...>]

Arnaud Gomes-do-Vale wrote on 11.02.2004 16:58 MET:
> ....However, in its current state, my patch
> separates ROUTE and IPV6ROUTE so this should be no problem.

I know but to keep the confusion down we should have the same syntax for 
both ROUTE and IPV6ROUTE. That's what I want to do.

-- 
MfG / Regards
Friedrich Lobenstock
____________________________________________________________________
Friedrich Lobenstock                       Linux Services Lobenstock
URL: http://www.lsl.at/                         Email: fl...@fl...
____________________________________________________________________

Re: [Devil-linux-develop] possible change in IPv4 routing configuration syntax

[Arnaud Gomes-do-V. <Arn...@ir...>]

Bruce Smith <bw...@ar...> writes:

> My main problem is I know nothing about IPv6, so I don't know what to
> look for.  i.e.  Will a normal IPv6 ROUTE contain legal colons? (:)

Yes it will. The usual form for an IPv6 address is something like
aaaa:bbbb::cccc:dddd:eeee/XX where "::" means "enough :0000: blocks"
and /XX is the netmask. However, in its current state, my patch
separates ROUTE and IPV6ROUTE so this should be no problem.

-- 
Arnaud

Re: [Devil-linux-develop] possible change in IPv4 routing configuration syntax

[Bruce S. <bw...@ar...>]

> >>>Although I'm not sure how to handle that.  If I simply "s/:/|/g", 
> >>>won't it will break the valid IPv6 routes?  (and IP aliases?)
> >>
> >>Ok, then I will need to give you the right sed rules.
> >>
> >> From my head I the following could be a possible solution (though not 
> >>tested yet):
> >>   sed -e "s/^\(ROUTE.*\):/\0|/"
> > 
> > Wouldn't that only change the first : to |  ?
> 
> I will go over it and come back to you when I have a final sed expression.

My main problem is I know nothing about IPv6, so I don't know what to
look for.  i.e.  Will a normal IPv6 ROUTE contain legal colons? (:)
Can you show me a couple example ifcfg files?  For v4 & v6 both?

> In the meantime you can think about how this could possibly integrated into 
> the update utility as generic as possible - eg. by defining in a filter 
> config file which filters to apply to a specific set of files. Filter might 
> not be the right expression, transformation program might be more to the point.

OK, I'll take a look.

 - BS

Re: [Devil-linux-develop] possible change in IPv4 routing configuration syntax

[Friedrich L. <fl...@fl...>]

Bruce Smith wrote on 11.02.2004 16:28 MET:
>>>Although I'm not sure how to handle that.  If I simply "s/:/|/g", 
>>>won't it will break the valid IPv6 routes?  (and IP aliases?)
>>
>>Ok, then I will need to give you the right sed rules.
>>
>> From my head I the following could be a possible solution (though not 
>>tested yet):
>>   sed -e "s/^\(ROUTE.*\):/\0|/"
> 
> 
> Wouldn't that only change the first : to |  ?

I will go over it and come back to you when I have a final sed expression.

In the meantime you can think about how this could possibly integrated into 
the update utility as generic as possible - eg. by defining in a filter 
config file which filters to apply to a specific set of files. Filter might 
not be the right expression, transformation program might be more to the point.

-- 
MfG / Regards
Friedrich Lobenstock
____________________________________________________________________
Friedrich Lobenstock                       Linux Services Lobenstock
URL: http://www.lsl.at/                         Email: fl...@fl...
____________________________________________________________________

Re: [Devil-linux-develop] possible change in IPv4 routing configuration syntax

[Bruce S. <bw...@ar...>]

> > Although I'm not sure how to handle that.  If I simply "s/:/|/g", 
> > won't it will break the valid IPv6 routes?  (and IP aliases?)
> 
> Ok, then I will need to give you the right sed rules.
> 
>  From my head I the following could be a possible solution (though not 
> tested yet):
>    sed -e "s/^\(ROUTE.*\):/\0|/"

Wouldn't that only change the first : to |  ?

 - BS

Re: [Devil-linux-develop] possible change in IPv4 routing configuration syntax

[Friedrich L. <fl...@fl...>]

Bruce Smith wrote on 11.02.2004 15:15 MET:
>>>>Now to have consistent syntax in the routing syntax - it makes the 
>>>>documentation much less confusing to the users and saves us a lot of 
>>>>possible troubles - I want to change the syntax for IPv4 too when 
>>>>integrating Arnauds changes for IPv6.
>>>>
>>>>Not much fuzz about that _but_ the crux is that it would introduce troubles 
>>>>during upgrading. So could you possible prepare the update script to take 
>>>>this into account, but not checking in those changes till I've got the 
>>>>contributions of Arnaud applied?
>>>
>>>The upgrade script doesn't look inside those files, it only compares
>>>them to see if they are different.  Your changes shouldn't cause any
>>>problems with the current upgrade script.
>>
>>I meant, could you please add the transformation from old to new format to 
>>the update script, as just copying the ifcfg-XXXX files will break the 
>>system when I change the syntax for adding routes.
> 
> 
> OK, I'm with you now.  (it's early here :)
> 
> Although I'm not sure how to handle that.  If I simply "s/:/|/g", 
> won't it will break the valid IPv6 routes?  (and IP aliases?)

Ok, then I will need to give you the right sed rules.

 From my head I the following could be a possible solution (though not 
tested yet):
   sed -e "s/^\(ROUTE.*\):/\0|/"

-- 
MfG / Regards
Friedrich Lobenstock
____________________________________________________________________
Friedrich Lobenstock                       Linux Services Lobenstock
URL: http://www.lsl.at/                         Email: fl...@fl...
____________________________________________________________________

Re: [Devil-linux-develop] possible change in IPv4 routing configuration syntax

[Bruce S. <bw...@ar...>]

> >>You might have read that Arnaud Gomes-do-Vale is working on IPv6 support 
> >>for DL. But this implies that he has to modify the syntax for the routing 
> >>entries in /etc/sysconfig/nic/ifcfg-ethX and replace the : with a | as the 
> >>: is used in IPv6 addresses.
> >>
> >>Now to have consistent syntax in the routing syntax - it makes the 
> >>documentation much less confusing to the users and saves us a lot of 
> >>possible troubles - I want to change the syntax for IPv4 too when 
> >>integrating Arnauds changes for IPv6.
> >>
> >>Not much fuzz about that _but_ the crux is that it would introduce troubles 
> >>during upgrading. So could you possible prepare the update script to take 
> >>this into account, but not checking in those changes till I've got the 
> >>contributions of Arnaud applied?
> > 
> > The upgrade script doesn't look inside those files, it only compares
> > them to see if they are different.  Your changes shouldn't cause any
> > problems with the current upgrade script.
> 
> I meant, could you please add the transformation from old to new format to 
> the update script, as just copying the ifcfg-XXXX files will break the 
> system when I change the syntax for adding routes.

OK, I'm with you now.  (it's early here :)

Although I'm not sure how to handle that.  If I simply "s/:/|/g", 
won't it will break the valid IPv6 routes?  (and IP aliases?)

 - BS

Re: [Devil-linux-develop] possible change in IPv4 routing configuration syntax

[Friedrich L. <fl...@fl...>]

Bruce Smith wrote on 11.02.2004 14:32 MET:
> 
>>You might have read that Arnaud Gomes-do-Vale is working on IPv6 support 
>>for DL. But this implies that he has to modify the syntax for the routing 
>>entries in /etc/sysconfig/nic/ifcfg-ethX and replace the : with a | as the 
>>: is used in IPv6 addresses.
>>
>>Now to have consistent syntax in the routing syntax - it makes the 
>>documentation much less confusing to the users and saves us a lot of 
>>possible troubles - I want to change the syntax for IPv4 too when 
>>integrating Arnauds changes for IPv6.
>>
>>Not much fuzz about that _but_ the crux is that it would introduce troubles 
>>during upgrading. So could you possible prepare the update script to take 
>>this into account, but not checking in those changes till I've got the 
>>contributions of Arnaud applied?
> 
> 
> The upgrade script doesn't look inside those files, it only compares
> them to see if they are different.  Your changes shouldn't cause any
> problems with the current upgrade script.

I meant, could you please add the transformation from old to new format to 
the update script, as just copying the ifcfg-XXXX files will break the 
system when I change the syntax for adding routes.

-- 
MfG / Regards
Friedrich Lobenstock
____________________________________________________________________
Friedrich Lobenstock                       Linux Services Lobenstock
URL: http://www.lsl.at/                         Email: fl...@fl...
____________________________________________________________________

Re: [Devil-linux-develop] possible change in IPv4 routing configuration syntax

[Bruce S. <bw...@ar...>]

> Hi Bruce!

Hi!  :-)

> You might have read that Arnaud Gomes-do-Vale is working on IPv6 support 
> for DL. But this implies that he has to modify the syntax for the routing 
> entries in /etc/sysconfig/nic/ifcfg-ethX and replace the : with a | as the 
> : is used in IPv6 addresses.
> 
> Now to have consistent syntax in the routing syntax - it makes the 
> documentation much less confusing to the users and saves us a lot of 
> possible troubles - I want to change the syntax for IPv4 too when 
> integrating Arnauds changes for IPv6.
> 
> Not much fuzz about that _but_ the crux is that it would introduce troubles 
> during upgrading. So could you possible prepare the update script to take 
> this into account, but not checking in those changes till I've got the 
> contributions of Arnaud applied?

The upgrade script doesn't look inside those files, it only compares
them to see if they are different.  Your changes shouldn't cause any
problems with the current upgrade script.

 - BS

[Devil-linux-develop] [fmII] Clam AntiVirus 0.66 released (Default branch)

[<no...@fr...>]

This email is to inform you about the release of version '0.66' of 'Clam
AntiVirus' through freshmeat.net. All URLs and other useful information
can be found at

    http://freshmeat.net/projects/clamav/

The changes in this release are as follows:
This release contain a fix for the latest libclamav vulnerability
published on security lists. It has better support for detection of
non-standard virus bounces and contains many small bugfixes and code
cleanups. 

Project description:
Clam AntiVirus is an anti-virus toolkit for Unix. The main purpose of
this software is the integration with mail servers (attachment
scanning). The package provides a flexible and scalable
multi-threaded daemon, a commandline scanner, and a tool for
automatic updating via Internet. The programs are based on a shared
library distributed with the Clam AntiVirus package, which you can
use in your own software.  

Trove categories:
[License             ] OSI Approved :: GNU General Public License (GPL)
[Topic               ] Utilities 

If you would like to cancel subscription to releases of this project,
login to freshmeat.net and choose 'home' from the personal menubar at the
top of the page. You'll be presented with a list of projects and
categories you're subscribed to in the right column, which you may cancel
by highlighting the project or category in question and clicking the
'delete' button.

Sincerely,
freshmeat.net 
 
____________________________| Advertising |____________________________
ETNUS TOTALVIEW NOW HAS BUILT-IN MEMORY DEBUGGING 

Etnus TotalView, the world's most advanced debugger on Linux and UNIX, has
advanced features absent in other debuggers. Example:
TotalView tracks heap activity and stops execution when allocation errors
occur. Get insight into memory usage without leaving your debug session.
Try it free today.   

www.etnus.com 
____________________________| Advertising |____________________________

Re: [Devil-linux-develop] [Patch] network script

[Thomas E. <tho...@bu...>]

Friedrich Lobenstock wrote:
> Thomas Eder wrote on 11.02.2004 00:49 MET:
> 
>> Friedrich Lobenstock wrote:
>>
>>> Thomas Eder wrote on 11.02.2004 00:30 MET:
>>>
>>>> the /etc/sysconfig/nic/ifcfg-vlanXXX doesn't work without this patch:
>>>>
>>>> --- config/etc/init.d/network.old       2004-02-11 
>>>> 00:09:57.000000000 +0100
>>>> +++ config/etc/init.d/network   2004-02-11 00:10:25.000000000 +0100
>>>> @@ -275,9 +275,9 @@
>>>>         start)
>>>>
>>>>                 #
>>>> -               # if vlan tools are installed set vlan naming shema
>>>> +               # set vlan naming shema
>>>>                 #
>>>> -               test -x $VLAN && $VLAN set_name_type 
>>>> VLAN_PLUS_VID_NO_PAD &> /dev/null
>>>> +               $VLAN set_name_type VLAN_PLUS_VID_NO_PAD &> /dev/null
>>>
>>>
>>>
>>>
>>>
>>> OK, I think after taking a closer look at the network script I know 
>>> what the real problem is.
>>>
>>> Please change the VLAN varibale (around line 42) to reflect the full 
>>> patch of the vconfig utility. Run "which vconfig" to find out.
>>
>>
>>  
>> -VLAN=vconfig
>> +VLAN=/bin/vconfig
>>   ..[..cut..]..
>> -        # if vlan tools are installed set vlan naming shema
>> +        # set vlan naming shema
>>          #
>> -        test -x $VLAN && $VLAN set_name_type VLAN_PLUS_VID_NO_PAD &> 
>> /dev/null
>> +        $VLAN set_name_type VLAN_PLUS_VID_NO_PAD &> /dev/null
> 
> 
> If you change the above then the "test -x" should successfully run the 
> vlan utility. Please test with only changing the VLAN variable. THX.
> 

Klaer mich bitte auf, aber:

ich glaube /bin /usr/bin /sbin /usr/sbin sind bei den meisten linux/unix in $PATH enthalten, daraus 
folgt fuer mich, dass VLAN=vconfig "fast immer" stimmt. Wenn /bin/vconfig auf zb. /sbin/vconfig 
geaendert wird, hast du mit unserem script ein _Problem_.
Das "test -x $VLAN" ist, seit DL auf _CD_ ist eigentlich absurd, oder kennst du einen Weg um Dateien 
von der RO CD zu "deaktivieren".
Wenn du sagen wuerdest wir testen ob es vlan ueberhaupt verwendet wird, ok aber so tauschen wir 
einen "Fehler" durch einen anderen :-(

-- 
thomas

[Devil-linux-develop] [ devil-linux-Bugs-894573 ] IPv6 as module

[SourceForge.net <no...@so...>]

Bugs item #894573, was opened at 2004-02-10 13:51
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410643&aid=894573&group_id=34096

Category: Base System
Group: all
Status: Open
Resolution: None
Priority: 5
Submitted By: Heiko Zuerker (smiley73)
Assigned to: Nobody/Anonymous (nobody)
Summary: IPv6 as module

Initial Comment:
change kernel config so ipv6 is a module
only a few people need this at the moment

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410643&aid=894573&group_id=34096

Re: [Devil-linux-develop] [Patch] network script

[Friedrich L. <fl...@fl...>]

Thomas Eder wrote on 11.02.2004 00:49 MET:
> Friedrich Lobenstock wrote:
> 
>> Thomas Eder wrote on 11.02.2004 00:30 MET:
>>
>>> the /etc/sysconfig/nic/ifcfg-vlanXXX doesn't work without this patch:
>>>
>>> --- config/etc/init.d/network.old       2004-02-11 00:09:57.000000000 
>>> +0100
>>> +++ config/etc/init.d/network   2004-02-11 00:10:25.000000000 +0100
>>> @@ -275,9 +275,9 @@
>>>         start)
>>>
>>>                 #
>>> -               # if vlan tools are installed set vlan naming shema
>>> +               # set vlan naming shema
>>>                 #
>>> -               test -x $VLAN && $VLAN set_name_type 
>>> VLAN_PLUS_VID_NO_PAD &> /dev/null
>>> +               $VLAN set_name_type VLAN_PLUS_VID_NO_PAD &> /dev/null
>>
>>
>>
>>
>> OK, I think after taking a closer look at the network script I know 
>> what the real problem is.
>>
>> Please change the VLAN varibale (around line 42) to reflect the full 
>> patch of the vconfig utility. Run "which vconfig" to find out.
> 
>  
> -VLAN=vconfig
> +VLAN=/bin/vconfig
>   
> ..[..cut..]..
> -		# if vlan tools are installed set vlan naming shema
> +		# set vlan naming shema
>  		#
> -		test -x $VLAN && $VLAN set_name_type VLAN_PLUS_VID_NO_PAD &> /dev/null
> +		$VLAN set_name_type VLAN_PLUS_VID_NO_PAD &> /dev/null

If you change the above then the "test -x" should successfully run the vlan 
utility. Please test with only changing the VLAN variable. THX.

-- 
MfG / Regards
Friedrich Lobenstock
____________________________________________________________________
Friedrich Lobenstock                       Linux Services Lobenstock
URL: http://www.lsl.at/                         Email: fl...@fl...
____________________________________________________________________

Re: [Devil-linux-develop] [Patch] network script

[Thomas E. <tho...@bu...>]

Friedrich Lobenstock wrote:
> Thomas Eder wrote on 11.02.2004 00:30 MET:
> 
>> the /etc/sysconfig/nic/ifcfg-vlanXXX doesn't work without this patch:
>>
>> --- config/etc/init.d/network.old       2004-02-11 00:09:57.000000000 
>> +0100
>> +++ config/etc/init.d/network   2004-02-11 00:10:25.000000000 +0100
>> @@ -275,9 +275,9 @@
>>         start)
>>
>>                 #
>> -               # if vlan tools are installed set vlan naming shema
>> +               # set vlan naming shema
>>                 #
>> -               test -x $VLAN && $VLAN set_name_type 
>> VLAN_PLUS_VID_NO_PAD &> /dev/null
>> +               $VLAN set_name_type VLAN_PLUS_VID_NO_PAD &> /dev/null
> 
> 
> 
> OK, I think after taking a closer look at the network script I know what 
> the real problem is.
> 
> Please change the VLAN varibale (around line 42) to reflect the full 
> patch of the vconfig utility. Run "which vconfig" to find out.
> 
> 

--- config/etc/init.d/network.old       2004-02-11 00:09:57.000000000 +0100
+++ config/etc/init.d/network   2004-02-11 00:44:19.000000000 +0100
@@ -39,7 +39,7 @@
  [ -s /etc/sysconfig/network/config ] && . /etc/sysconfig/network/config
  [ -s /etc/sysconfig/network/dhcp ] && . /etc/sysconfig/network/dhcp

-VLAN=vconfig
+VLAN=/bin/vconfig

  CONFIG_DIR=/etc/sysconfig/nic
  CONFIG_FILE=ifcfg-
@@ -275,9 +275,9 @@
         start)

                 #
-               # if vlan tools are installed set vlan naming shema
+               # set vlan naming shema
                 #
-               test -x $VLAN && $VLAN set_name_type VLAN_PLUS_VID_NO_PAD &> /dev/null
+               $VLAN set_name_type VLAN_PLUS_VID_NO_PAD &> /dev/null

                 #
                 # physical interfaces are brought up first


-- 
thomas

Re: [Devil-linux-develop] [Patch] network script

[Friedrich L. <fl...@fl...>]

Friedrich Lobenstock wrote on 11.02.2004 00:37 MET:
> 
> OK, I think after taking a closer look at the network script I know what 
> the real problem is.
> 
> Please change the VLAN varibale (around line 42) to reflect the full 
> patch of the vconfig utility. Run "which vconfig" to find out.

It's too late in the night - or early in the morning.

Of course I meant "path" _not_ "patch".


-- 
MfG / Regards
Friedrich Lobenstock
____________________________________________________________________
Friedrich Lobenstock                       Linux Services Lobenstock
URL: http://www.lsl.at/                         Email: fl...@fl...
____________________________________________________________________

Re: [Devil-linux-develop] [Patch] network script

[Friedrich L. <fl...@fl...>]

Thomas Eder wrote on 11.02.2004 00:30 MET:
> the /etc/sysconfig/nic/ifcfg-vlanXXX doesn't work without this patch:
> 
> --- config/etc/init.d/network.old       2004-02-11 00:09:57.000000000 +0100
> +++ config/etc/init.d/network   2004-02-11 00:10:25.000000000 +0100
> @@ -275,9 +275,9 @@
>         start)
> 
>                 #
> -               # if vlan tools are installed set vlan naming shema
> +               # set vlan naming shema
>                 #
> -               test -x $VLAN && $VLAN set_name_type 
> VLAN_PLUS_VID_NO_PAD &> /dev/null
> +               $VLAN set_name_type VLAN_PLUS_VID_NO_PAD &> /dev/null


OK, I think after taking a closer look at the network script I know what 
the real problem is.

Please change the VLAN varibale (around line 42) to reflect the full patch 
of the vconfig utility. Run "which vconfig" to find out.


-- 
MfG / Regards
Friedrich Lobenstock
____________________________________________________________________
Friedrich Lobenstock                       Linux Services Lobenstock
URL: http://www.lsl.at/                         Email: fl...@fl...
____________________________________________________________________