On Fri, Aug 15, 2003 at 02:36:27PM +0300, Hen, Shmulik wrote:
> > -----Original Message-----
> > From: Dan Aloni [mailto:da-x@xxxxxxx]
> > Sent: Friday, August 15, 2003 2:15 PM
> > To: Linux Net-Dev
> > Cc: David S. Miller; Mark Huth
> > Subject: [PATCH] network device renaming sysfs fix
> >
> >
> > (repost, now will hopefully reach the mailing list)
> >
> > I believe this is a better approach for fixing the sysfs renaming
> > discrepancy. Later I'll also look into fixing the same issue
> > with sysctl.
> >
> >
> > --
> > Dan Aloni
> > da-x@xxxxxxx
> >
> >
>
> In general, it a similar thing applicable for proc fs too ?
> We just had to fix something like that in bonding, and
> it sounds odd each driver should handle this on it's own.
It is more complicated. procfs's interface to sysctl is optional -
thus sysctl's interfaces hide procfs from you. Fixing this require
changes in sysctl itself, and most probably also in the networking
code, because network devices' sysctls are not exposed in the
net/dev/core.c level.
--
Dan Aloni
da-x@xxxxxxx
|