From: Stephen Hemminger <shemminger@osdl.org>
To: "Catalin(ux aka Dino) BOIE" <util@deuroconsult.ro>
Cc: netdev@oss.sgi.com
Subject: Re: Why /sys/class/net/*/features is read-only?
Date: Mon, 23 May 2005 09:28:27 -0700 [thread overview]
Message-ID: <20050523092827.7883af33@dxpl.pdx.osdl.net> (raw)
In-Reply-To: <Pine.LNX.4.62.0505201346420.29305@webhosting.rdsbv.ro>
On Mon, 23 May 2005 10:46:50 +0300 (EEST)
"Catalin(ux aka Dino) BOIE" <util@deuroconsult.ro> wrote:
> Hello!
>
> Why features file is read-only. If an admin want to force some attributes,
> we can let them, right?
>
Leave it read-only because the hardware may not want to allow them on that flavor and so it would
have to be device specific.
next prev parent reply other threads:[~2005-05-23 16:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-23 7:46 Why /sys/class/net/*/features is read-only? Catalin(ux aka Dino) BOIE
2005-05-23 16:28 ` Stephen Hemminger [this message]
2005-05-23 20:49 ` Catalin(ux aka Dino) BOIE
2005-05-23 20:53 ` David S. Miller
2005-05-23 21:33 ` Catalin(ux aka Dino) BOIE
2005-05-23 21:51 ` David S. Miller
2005-05-23 21:53 ` Catalin(ux aka Dino) BOIE
2005-05-23 20:55 ` 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=20050523092827.7883af33@dxpl.pdx.osdl.net \
--to=shemminger@osdl.org \
--cc=netdev@oss.sgi.com \
--cc=util@deuroconsult.ro \
/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).