I started looking at this today. You are right about the tight
connection, but it seems cleaner now as you suggest. net/802/tr.c
requires ipv4. But it removes 65K off the compressed kernel.
> root@localhost.rutgers.edu <root@localhost.rutgers.edu> writes:
> >It would also be nice if ipv4 was also available as a module (since it is
> >very large, but except for nfs root apps it could be loaded by kerneld).
>
> I took a run at making ipv4 a module last fall and gave up on it.
> There were just to many dependencies in the rest of the kernel on
> internal bits and pieces of ipv4. Things might be a bit cleaner now,
> but I expect there is at least still a tight connection between the
> ethernet layer and the ipv4 code. Probably I should put this on the
> list of things to do with the ipv4 code, but it's going to be near
> the bottom of the list...
Well, there are probably 50+ revisions before the next code freeze ... :).
tz@execpc.com
finger tz@execpc.com for PGP key