From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "João Luis Meloni Assirati" <assirati@nonada.if.usp.br>
Cc: linux-kernel@vger.kernel.org
Subject: Re: /sys/class/net/eth?/carrier and uevents
Date: Mon, 29 May 2006 23:29:53 +0200 [thread overview]
Message-ID: <9a8748490605291429h32f67b53k757d6e4a0cec7675@mail.gmail.com> (raw)
In-Reply-To: <200605291807.42725.assirati@nonada.if.usp.br>
On 29/05/06, João Luis Meloni Assirati <assirati@nonada.if.usp.br> wrote:
>
> Hello,
>
Hi,
> I would like to have my network interfaces configured when plugged on the
> network cable. I know there are some daemons that do this for me (laptop-net,
> ifplugd, whereami), but it would be nice if a simple udev rule take care of
> this to me. However, as I can see with kernel 2.6.16 and udevmonitor (udev
> version 0.091), nonetheless /sys/class/net/eth?/carrier changes when I plug
> the network cable, no uevent is generated. Could this be changed so udev get
> triggered when network cables get plugged? As I am no kernel developper, this
> is only a suggestion, hoping that it would be a simple and pertinent job for
> those ho know the subject.
>
I added the 'carrier' attribute initially but never considered udev at
the time. But I can certainly see how it could be useful.
I'll take a look at adding a hotplug event when I get some spare time
(probably some time next week) - or perhaps someone else will beat me
to it :)
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
next prev parent reply other threads:[~2006-05-29 21:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-29 21:07 João Luis Meloni Assirati
2006-05-29 21:29 ` Jesper Juhl [this message]
2006-05-29 21:33 ` Arjan van de Ven
2006-05-29 21:51 ` Jesper Juhl
2006-05-29 23:02 ` João Luis Meloni Assirati
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=9a8748490605291429h32f67b53k757d6e4a0cec7675@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=assirati@nonada.if.usp.br \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®