Im glad to see you explanation, now is solved... a doubt is left: How could the Sys Builder make image that boot always in eth0? might they use eth0 or wifi... IMHO
Il giorno venerdì 4 ottobre 2013 20:23:31 UTC+2, garyamort ha scritto: > > > > On Friday, October 4, 2013 1:11:48 PM UTC-4, [email protected] wrote: >> >> >> so from what i see is impossible to scale an image flashing to multiple >> BBB without setting the eth interface... is it correct? >> >> > > When Linux boots up, it assigns loads the various network drivers for each > network device and assigns names "randomly" > > IE eth0 is the FIRST ethernet device to initialize. eth1 is the SECOND > ethernet device to initialize. Etc. > > Because some people depend on eth0 always being assigned to the SAME > network card, there are a number of different "systems" in place for linux > to force this to occur. Most of them revolve around using a program called > udev can detect very specific information about the card[mac address, > hardware id, etc] and then force the name to be assigned that you want. > See > http://www.linuxfromscratch.org/blfs/view/development/chapter07/network.html > for > details. > > This means if you take a "working" image of linux from one machine and > copy it to another machine, eth0 can ONLY be assigned to the network > interface from the original machine. So on your second machine, you may > end up with eth1 instead of eth0 or none at all! > > Depending on what distribution of linux you use[Ubuntu, Debian, Angstrom, > Arch, etc] AND what version you are using - there will be installed some > shell scripts that when you boot the system up will > 1) Check to see if network interface configuration file exists[the file > which defines MAC Address N should be called eth0] > 2) If the file does not exist, it will automatically create one using the > current configuration. > > This means that you cannot "copy" an entire linux installation from one > system and put it on another. You have to delete the network configuration > file that was automatically generated, so that a new one will become > automatically generated on the new system. > > Other alternatives are to delete that file AND to disable those programs > which automatically generate new files and just live with the possibility > of "random" network device names. > > The "difference" your referring to is that many of the different devices > on the board are assigned unique serial numbers. The hardware is > identical, it is the serial number which changes. > > > > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
