Message-Id: <200308211951.h7LJpFI30326@cambot.circlemud.org>
cc: linux-kernel@vger.kernel.org, fusd-announce@lists.sourceforge.net
Subject: Re: [ANNOUNCE] FUSD v1.10 now available 
In-Reply-To: <200308202253.h7KMrn116585@cambot.circlemud.org> 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <30324.1061495475.1@cambot.lecs.cs.ucla.edu>
Date: Thu, 21 Aug 2003 12:51:15 -0700
From: Jeremy Elson <jelson@circlemud.org>
To: unlisted-recipients:; (no To-header on input)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1636
Lines: 44

Oops, someone pointed out that I forgot the URL in my announcement.
For those who don't want to use Google :-), it is:

http://www.circlemud.org/~jelson/software/fusd

Best,
Jeremy

Jeremy Elson writes:
>We're happy to announce release 1.10 of FUSD, the Linux Framework for
>User-Space Devices.
>
>If you have a Linux 2.4 kernel running devfs, FUSD is a combination of
>Linux kernel module and userspace library that lets you write
>userspace programs that can act as character device drivers for files
>under /dev.  Your program reigsters the device with the kernel module;
>then, it proxies system calls (e.g.,  open(), read()...) to your
>program.  Your userspace program can respond to these system calls as
>a kernel module would.  Strict error checking at the user/kernel
>boundary prevents such userspace drivers from corrupting each other,
>the kernel, or even the processes using the devices they manage.
>
>v1.10 has a number of enhancements, including:
>  -- Now safe for SMP and preemptible kernels
>
>  -- Includes both C and Python bindings
>
>  -- /dev/fusd/status device shows a summary of devices registered and
>     in use
>
>  -- Updated documentation and various other bugfixes
>
>
>Unfortunately, FUSD does NOT work under later 2.5 or any 2.6 kernels.
>The recent changes to the devfs API break FUSD in a way that we
>haven't yet looked into fixing.
>
>Regards,
>Jeremy
-
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/