From: Dan Aloni <da-x@gmx.net>
To: "Hen, Shmulik" <shmulik.hen@intel.com>
Cc: Linux Net-Dev <netdev@oss.sgi.com>,
"David S. Miller" <davem@redhat.com>,
Mark Huth <mhuth@mvista.com>
Subject: Re: [PATCH] network device renaming sysfs fix
Date: Fri, 15 Aug 2003 14:45:07 +0300 [thread overview]
Message-ID: <20030815114507.GA5929@callisto.yi.org> (raw)
In-Reply-To: <E791C176A6139242A988ABA8B3D9B38A014C949E@hasmsx403.iil.intel.com>
On Fri, Aug 15, 2003 at 02:36:27PM +0300, Hen, Shmulik wrote:
> > -----Original Message-----
> > From: Dan Aloni [mailto:da-x@gmx.net]
> > 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@gmx.net
> >
> >
>
> 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@gmx.net
next prev parent reply other threads:[~2003-08-15 11:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-15 11:36 [PATCH] network device renaming sysfs fix Hen, Shmulik
2003-08-15 11:45 ` Dan Aloni [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-15 11:15 Dan Aloni
2003-08-15 16:37 ` Stephen Hemminger
2003-08-15 16:50 ` Dan Aloni
2003-08-16 14:40 ` David S. Miller
2003-08-17 7:13 ` Dan Aloni
2003-08-15 18:09 ` Mark Huth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030815114507.GA5929@callisto.yi.org \
--to=da-x@gmx.net \
--cc=davem@redhat.com \
--cc=mhuth@mvista.com \
--cc=netdev@oss.sgi.com \
--cc=shmulik.hen@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).