From: Stephen Hemminger <shemminger@vyatta.com>
To: "Kirill A. Shutemov" <kirill@shutemov.name>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
James Morris <jmorris@namei.org>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
Patrick McHardy <kaber@trash.net>,
Greg Kroah-Hartman <gregkh@suse.de>,
Kay Sievers <kay.sievers@vrfy.org>,
Alexey Gladkov <gladkov.alexey@gmail.com>
Subject: Re: [RFD] Network configuration data in sysfs
Date: Mon, 24 Oct 2011 22:17:01 +0200 [thread overview]
Message-ID: <20111024221701.0775d227@s6510.linuxnetplumber.net> (raw)
In-Reply-To: <20111023233558.GA23264@shutemov.name>
On Mon, 24 Oct 2011 02:35:58 +0300
"Kirill A. Shutemov" <kirill@shutemov.name> wrote:
> Hi,
>
> Currently there's no way to set or inspect network configuration (protocol
> addresses, routes, etc.) through sysfs. Yes, we have netlink interface for
> this, but sysfs has advantage:
>
> - change or inspect network configuration using standard unix utilities
> (echo, cat, etc.). It's useful at least in restricted environment where
> no special utilities available -- initrd or stripped down busybox.
Last I checked busybox had a stripped down version of iproute arealdy.
> - transparent udev support. It would be nice to get this information to
> udev.
>
> Is there something fundamental preventing us to have sysfs interface for
> network configuration?
>
Sysfs does not support the concept of transactions. Many network operations
require setting multiple values at a time; which is why a message interface
like netlink works much better.
prev parent reply other threads:[~2011-10-24 20:17 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
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 [this message]
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=20111024221701.0775d227@s6510.linuxnetplumber.net \
--to=shemminger@vyatta.com \
--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=kirill@shutemov.name \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.