Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262823AbTHUQ0s (ORCPT ); Thu, 21 Aug 2003 12:26:48 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262827AbTHUQ0s (ORCPT ); Thu, 21 Aug 2003 12:26:48 -0400 Received: from [66.212.224.118] ([66.212.224.118]:25870 "EHLO hemi.commfireservices.com") by vger.kernel.org with ESMTP id S262823AbTHUQ0r (ORCPT ); Thu, 21 Aug 2003 12:26:47 -0400 Date: Thu, 21 Aug 2003 11:59:45 -0400 (EDT) From: Zwane Mwaikambo X-X-Sender: zwane@montezuma.mastecende.com To: "Richard B. Johnson" Cc: Pankaj Garg , Linux kernel Subject: Re: Messaging between kernel modules and User Apps In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 641 Lines: 17 On Thu, 21 Aug 2003, Richard B. Johnson wrote: > The de facto standard for network devices is to use sockets. > For character and and block devices Unix/Linux uses the > open/poll/ioctl/read mechanisms. That sounds fine, but.. > You could send your module a pid via proc and have it send a > signal to your application as a result of an event. ... please don't even entertain such sick ideas. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/