Hi, I've been experimenting with using Bering-uClibc as a fileserver for a few months now, mainly using the iSCSI protocol. Reviewing things again as a result of my experience I'm probably going to switch to using OpenFiler instead, since it's a better fit to my specific requirements.
While setting up my Bering-uClibc fileserver I developed a few add-on packages which might be of interest to others. They're not candidates for the "contrib" area since they require tweaks to the kernel and to uClibc, but it seems a shame to simply throw them away... They're fully configured for BuildTool & BuildPacket. I'm thinking that I could put them in my own "devel" directory on SourceForge - under http://leaf.cvs.sourceforge.net/leaf/devel/ How do I get such a directory - by becoming a member of the LEAF project? I already have a SourceForge account (davidmbrooke) so if somebody could add me to the project that would be great. My packages are nfsutils From http://nfs.sourceforge.net/ User-space tools for an NFS file server These work in conjunction with the nfsd kernel module This in turn needs "full" RPC support from uClibc portmap From http://neil.brown.name/portmap/ Provides a ONCRPC port mapper, for NFS etc. lvm2 From http://sources.redhat.com/lvm2/ User-space tools for LVM2 logical volume management Relies on Device Mapper support (user space and kernel) dev-map From http://sourceware.org/dm/ User-space Device Mapper tools for LVM2 etc. These work in conjunction with a kernel device-mapper There's also some DocBook documentation on what needs to be modified in the kernel and uClibc in order to build the packages. Regards, davidMbrooke ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ leaf-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/leaf-devel
