Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262645AbVCSSAW (ORCPT ); Sat, 19 Mar 2005 13:00:22 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262647AbVCSSAW (ORCPT ); Sat, 19 Mar 2005 13:00:22 -0500 Received: from linux01.gwdg.de ([134.76.13.21]:42428 "EHLO linux01.gwdg.de") by vger.kernel.org with ESMTP id S262645AbVCSSAS (ORCPT ); Sat, 19 Mar 2005 13:00:18 -0500 Date: Sat, 19 Mar 2005 19:00:00 +0100 (MET) From: Jan Engelhardt To: linux-kernel@vger.kernel.org Subject: Relayfs question Message-ID: 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: 864 Lines: 25 Hello, according to the relayfs description on opersys.com, |As the Linux kernel matures, there is an ever increasing number of facilities |and tools that need to relay large amounts of data from kernel space to user |space. Up to this point, each of these has had its own mechanism for relaying |data. To supersede the individual mechanisms, we introduce the "high-speed |data relay filesystem" (relayfs). As such, things like LTT, printk, EVLog, |etc. This sounds to me like it would obsolete most character-based devices, e.g. random and urandom. What do the relayfs developers say to this? Jan Engelhardt -- - 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/