From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 22 Oct 2002 21:38:39 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 22 Oct 2002 21:38:39 -0400 Received: from adsl-64-166-241-227.dsl.snfc21.pacbell.net ([64.166.241.227]:27301 "EHLO www.hockin.org") by vger.kernel.org with ESMTP id ; Tue, 22 Oct 2002 21:38:21 -0400 From: Tim Hockin Message-Id: <200210230144.g9N1iDx11822@www.hockin.org> Subject: Re: rtnetlink interface state monitoring problems. To: hadi@cyberus.ca (jamal) Date: Tue, 22 Oct 2002 18:44:13 -0700 (PDT) Cc: dwmw2@infradead.org (David Woodhouse), linux-kernel@vger.kernel.org, netdev@oss.sgi.com In-Reply-To: from "jamal" at Oct 22, 2002 08:59:22 PM X-Mailer: ELM [version 2.5 PL3] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > If not, it probably time for someone to write a generic notification > scheme via netlink. How generic? I need to pay some attention to cleaning up the next version of the link-changes via netlink patch that was discussed last week or the week before. What kind of generic are you thinking about? :)