Re: modularizing some of the net code

Matthias Urlichs (smurf@smurf.noris.de)
Thu, 14 Mar 1996 22:36:38 +0100


In linux.dev.net, article <Pine.LNX.3.91.960314095047.14870C-100000@LiO=
Ns.reSEQ.unGOV>,
lilo <lilo@lions.reseq.ungov> writes:
>=20
> Each socket, and each interface, is a demand that the module be kept.=
So

Hmm... a socket usually doesn't refer to a specific interface (from the
user's point of view), it refers to a specific pair of source/destinati=
on
addresses/pports.

If you remove an interface, all the sockets are "removed" from the inte=
rface
as well (they'll have to find a different route next time you send
something on them). This code already is in the kernel and seems to wor=
k;
my ISDN driver (not the one in the current 1.3 kernel... ;-) uses this
feature.

I can't think of a reason to change that behavior.

--=20
I am an atheist, thank God!
--=20
Matthias Urlichs \ XLink-POP N=FCrnberg | EMail: urlichs@smurf.=
noris.de
Schleiermacherstra=DFe 12 \ Unix+Linux+Mac | Phone: ...please use =
email.
90491 N=FCrnberg (Germany) \ Consulting+Networking+Programming+etc'i=
ng 42
PGP: 1B 89 E2 1C 43 EA 80 44 15 D2 29 CF C6 C7 E0 DE=20
Click <A HREF=3D"http://smurf.noris.de/~smurf/finger">here</A>.