From: Stephen Hemminger <[email protected]>
Date: Wed, 13 Dec 2006 15:41:25 -0800
> But what if other network device is not a module. We want loopback
> to be first. so it needs to be before other device_initcall's
There is zero evidence that loopback must be first.
I was not able to provide any after my study of the code last night,
and I haven't seen any concrete proof shown today either.
You mentioned "the dst code" relies on ifindex==1, what exactly do you
mean by that? Give specific code examples instead of ambiguous and
non-specific references.
And this claim doesn't make any sense, because anyone who looks at
drivers/net/Makefile can see that several drivers are linked in way
before Space.o, and thus when built statically would today end up in
the device list way before the loopback driver. So it can't be
"broken" by Adrian's change, since it's already not putting loopback
first and we can prove this! :-)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]