Marc Haber <mh+debian-b...@zugschlus.de> writes: > On Mon, Feb 28, 2011 at 06:39:48AM +0100, Christian PERRIER wrote: > >> Quoting Thomas Mieslinger (thomas.mieslin...@1und1.de): >> >>> To get my job done all those 5000 Machines must comply to some very >>> very basic guidelines. After the installation, the inner interface >>> is always eth0 if there is a public interface, it is eth1. If there >>> are crosslinks they are eth1 and onward. >>> >>> I need a simple and powerful mechanism to enforce this against the >>> quirks of udev and bioses. >> >> You may want to develop the needed support for such things in >> netcfg. > > Are there any docs for netcfg? After a cursory glance at the source > package, it looks like the docs are contained in those nice .c and .h > files with a little too little documentation about the interfaces.
There's no docs for netcfg, AFAIK, but it isn't that complicated. However, Matt Palmer is currently reorganizing the code, so you'd better synchronize with him before you start fiddling with it. On the other hand, the issue at hand probably doesn't belong into netcfg. Naming network interfaces is a job for udev, and netcfg can simply use eth0 after that, if I read Thomas correctly. I routinely do this by putting /etc/udev/rules.d/60-manual-net.rules into the installer initramfs AND copying it into /target at the end of the installation. One could make this fully dynamic if needed, even without remastering the initramfs, by elaborate preseed/early_command specifications. -- Regards, Feri. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
