Adam Borowski <[email protected]> writes: > On Tue, Nov 08, 2016 at 04:00:10PM +0000, Rainer Weikusat wrote: >> It's pretty easy to fix this: >> >> - assign a sequence number to each driver load event reflecting >> the device detection order >> >> - use a module loading program (really a modprobe wrapper) >> utilizing these sequence numbers to work out the order modules >> should be loaded in >> >> The implementation I'm using does this by creating a file whose name is >> the sequence number of the driver to load next in a subdirectory of >> /dev. Concurrently started driver loaders use dnotify[*] to watch this >> directory and 'do their thing' once their sequence number >> appears. Afterwards, the instance which finished its work delete its >> sequence number file and creates the next one. > > This would work only if every of your network cards uses a different driver.
This works. It doesn't solve the problem of Dell cross-connecting different NICs of the same type but it's not supposed to. _______________________________________________ Dng mailing list [email protected] https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
