On Thu, Jun 9, 2011 at 11:03 PM, Tom Gundersen wrote:

On Thu, Jun 9, 2011 at 11:01 PM, Heiko Baums wrote:

...

Am Wed, 08 Jun 2011 16:01:15 -0000 schrieb "Arch Linux: Recent news updates: Tom Gundersen" :

...

Tom Gundersen wrote:

This April marked the ten year anniversary of the last net-tools release. We decided to look at this as an opportunity to deprecate net-tools and provide alternative, and better maintained, solutions for net-tools functionality. ... We want to encourage the use of more advanced network solutions, such as `networkmanager` or our own `netcfg`.

Well, I don't want to say anything, but netcfg still depends on net-tools. ;-)

One battle at a time ;-)

Patches welcome! -t

That is correct. net-utils could be made an optdepend, or the support could just be removed entirely. IIRC the iproute/netutils code was separate and equivalent. It's been a while since I've looked though. On Thu, 09 Jun 2011 15:11 -0600, "Thomas S Hatch" wrote:

Does netcfg still need net-tools? or can it be an opt depends? It was my understanding that it only used ip unless specified otherwise.

On Fri, 10 Jun 2011 08:19 +0200, "Rémy Oudompheng" wrote:

On 2011/6/9 Thomas S Hatch wrote:

...

Does netcfg still need net-tools? or can it be an opt depends? It was my understanding that it only used ip unless specified otherwise.

Actually, I think it only depends on net-tools because there is some obscure option that allows users to make it run ifconfig with certain options. Of course, it could be replaced by an option that runs ip with custom options... All the remaining things are indeed done with iproute2

Rémy.

netcfg has an option that runs ip/iproute with any custom option (routes, IPs anything), the option is "IPCFG". It may be seen in the example ethernet-iproute[1]. IFCFG is the obscure command you mention, unfortunately it's not too obscure, as this was how static IPs were set before iproute configuration was added. It was retained for backwards compatibility. The only reason net-tools was still a requirement was setting hostname. A change similar to initscripts [2] at line 121 of src/connections/ethernet [3] would suffice. After that it ought to be safe to make net-tools an optional dependency. Systems already using net-tools will keep functioning, and a notice could be placed in code that handles IFCFG to advise those users to migrate to the iproute configuration. [1] http://projects.archlinux.org/initscripts.git/commit/?id=f262299928f1aca454a... [2] http://projects.archlinux.org/netcfg.git/tree/src/connections/ethernet#n121 [3] http://projects.archlinux.org/netcfg.git/tree/examples/ethernet-iproute

On Fri, 10 Jun 2011 15:05 +0200, "Tom Gundersen" wrote:

On Fri, Jun 10, 2011 at 2:51 PM, James Rayner wrote:

...

The only reason net-tools was still a requirement was setting hostname. A change similar to initscripts [2] at line 121 of src/connections/ethernet [3] would suffice.

What is the reason the hostname is set in netcfg? Do we ever want it to change from what was set on boot?

-t

Hostname is only set if someone specifies one in the configuration, otherwise it is left as is. I've never heard of anyone using this option. Judd's original netcfg script from 2005 included this option so I retained it when I wrote netcfg. James

Hi Rémy, On Sat, Jun 11, 2011 at 4:56 PM, Rémy Oudompheng wrote:

I will need testers for the various patches I merged from the bug tracker, notably IPv6. Any comments on the suggested implementation are welcome.

Great to hear that you are working on this! My two cents: I noticed you made a change to the state dir. Maybe worth also moving it from /var/run to /run? To avoid hassle with changing network backend in the future, it might be worth trying to avoid config variables that are passed to the backend without parsing (don't know if this has been, or will be added, just something that caused trouble in initscripts). -t

On Fri, Jun 10, 2011 at 16:27, Ignacio Galmarino wrote:

On Thu, Jun 9, 2011 at 3:01 PM, Heiko Baums wrote:

...

Am Wed, 08 Jun 2011 16:01:15 -0000 schrieb "Arch Linux: Recent news updates: Tom Gundersen" :

...

Tom Gundersen wrote:

This April marked the ten year anniversary of the last net-tools release. We decided to look at this as an opportunity to deprecate net-tools and provide alternative, and better maintained, solutions for net-tools functionality. ... We want to encourage the use of more advanced network solutions, such as `networkmanager` or our own `netcfg`.

wicd stop working if you uninstall net-tools. Just a warning to wicd users :)

Ignacio

same for rp-pppoe users.

On Fri, Jun 10, 2011 at 17:58, Tom Gundersen wrote:

On Fri, Jun 10, 2011 at 3:31 PM, Bogdan Ionuț wrote:

...

same for rp-pppoe users.

Please file a bug about the missing dependency.

-t

https://bugs.archlinux.org/task/24639

On Fri, Jun 10, 2011 at 3:27 PM, Ignacio Galmarino wrote:

wicd stop working if you uninstall net-tools. Just a warning to wicd users :)

Please file a bug about the missing dependency. -t