[arch-general] [arch-dev-public] [signoff] coreutils-8.12-2, initscripts-2011.06.3-1, net-tools-1.60-16, udev-171-2, yp-tools-2.12-2, ypbind-mt-1.33-2, iproute2-2.6.38-3
Javier Vasquez
j.e.vasquez.v at gmail.com
Tue Jun 7 19:33:50 EDT 2011
- Previous message: [arch-general] [arch-dev-public] [signoff] coreutils-8.12-2, initscripts-2011.06.3-1, net-tools-1.60-16, udev-171-2, yp-tools-2.12-2, ypbind-mt-1.33-2, iproute2-2.6.38-3
- Next message: [arch-general] [arch-dev-public] [signoff] coreutils-8.12-2, initscripts-2011.06.3-1, net-tools-1.60-16, udev-171-2, yp-tools-2.12-2, ypbind-mt-1.33-2, iproute2-2.6.38-3
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
...
>>
>> The new syntax is very simplistic and only supports one wired network
>> device (configured statically or by dhcp) and we do not expect to add
>> more features in the future. We want to encourage the use of more
>> advanced network solutions, such as `networkmanager` or our own
>> `netcfg`.
Just one officially supported? How about boxes with 2 nics acting as
routers or gateways? It sounds to me a bit limited... netcfg is
there but it's not the default, and most arch wiki documentation show
a way without netcfg, :-) Perhaps time to change the arch wikies when
the change take place, :-)
Did I misunderstand the statement?
Thanks,
--
Javier.
- Previous message: [arch-general] [arch-dev-public] [signoff] coreutils-8.12-2, initscripts-2011.06.3-1, net-tools-1.60-16, udev-171-2, yp-tools-2.12-2, ypbind-mt-1.33-2, iproute2-2.6.38-3
- Next message: [arch-general] [arch-dev-public] [signoff] coreutils-8.12-2, initscripts-2011.06.3-1, net-tools-1.60-16, udev-171-2, yp-tools-2.12-2, ypbind-mt-1.33-2, iproute2-2.6.38-3
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
More information about the arch-general
mailing list