From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: David Miller <davem@davemloft.net>
Cc: kay.sievers@vrfy.org, netdev@vger.kernel.org,
kuznet@ms2.inr.ac.ru, jmorris@namei.org, yoshfuji@linux-ipv6.org,
kaber@trash.net, gregkh@suse.de, gladkov.alexey@gmail.com
Subject: Re: [RFD] Network configuration data in sysfs
Date: Mon, 24 Oct 2011 07:24:00 +0300 [thread overview]
Message-ID: <20111024042400.GA31344@shutemov.name> (raw)
In-Reply-To: <20111023.232416.1038111296509565828.davem@davemloft.net>
On Sun, Oct 23, 2011 at 11:24:16PM -0400, David Miller wrote:
> From: "Kirill A. Shutemov" <kirill@shutemov.name>
> Date: Mon, 24 Oct 2011 04:34:07 +0300
>
> > On Sun, Oct 23, 2011 at 08:49:43PM -0400, David Miller wrote:
> >> From: "Kirill A. Shutemov" <kirill@shutemov.name>
> >> Date: Mon, 24 Oct 2011 02:35:58 +0300
> >>
> >> > Is there something fundamental preventing us to have sysfs interface for
> >> > network configuration?
> >>
> >> Netlink already provides everything sysfs would potentially provide as
> >> well as event tracking.
> >
> > Not everything. You still need special utilities to view/change the
> > configuration.
>
> You can use netlink to perform any configuration change you want, or
> to view any network configuration setting.
You need /sbin/ip or similar tool to do this, right?
--
Kirill A. Shutemov
next prev parent reply other threads:[~2011-10-24 4:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-23 23:35 [RFD] Network configuration data in sysfs Kirill A. Shutemov
2011-10-24 0:49 ` David Miller
2011-10-24 1:34 ` Kirill A. Shutemov
2011-10-24 3:24 ` David Miller
2011-10-24 4:24 ` Kirill A. Shutemov [this message]
2011-10-24 4:59 ` David Miller
2011-10-24 12:46 ` Kay Sievers
2011-10-24 23:54 ` Alexey Gladkov
2011-10-25 7:57 ` Kay Sievers
2011-10-24 20:17 ` Stephen Hemminger
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=20111024042400.GA31344@shutemov.name \
--to=kirill@shutemov.name \
--cc=davem@davemloft.net \
--cc=gladkov.alexey@gmail.com \
--cc=gregkh@suse.de \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kay.sievers@vrfy.org \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.org \
/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).