On Wed, Jul 05, 2006 at 02:29:31PM -0400, Josef Sipek wrote: > On Wed, Jul 05, 2006 at 11:21:05AM -0700, Vladimir V. Kolpakov wrote: > > On Wed, Jul 05, 2006 at 01:49:56PM -0400, Josef Sipek wrote: > > > I would also like something like libunionfs to appear after the switch to > > > the new method. This would be a lot like libusb (which allows developers > > > to > > > easily access USB device info & data from userspace without having to > > > manually parse /sys and(?) /proc). > > > > How about generic, say libANYsys, > > configurable with plain text files? > > Please explain.
Yeah, shorter is not always better ;) Step 1. In case libunionfs is a way similar to libusb, why don't merge them at the first place? Okay, let's say we create generic lib for data access via sysfs, combining libunionfs+libusb demands. Step 2. Once libANYsys (libsysfs?) is created, how to manage specific devices configuration? External [re]loadable configuration comes into play, resource manager, hotplug devices, etc... Step 3. (or step 0?) Let's look around to see whether libsysfs already has implemented some or out needs. Still confusing? --w _______________________________________________ unionfs mailing list [email protected] http://www.fsl.cs.sunysb.edu/mailman/listinfo/unionfs
