Thanks Eric,
I'll add the sources under
/leaf.cvs.sourceforge.net/leaf/src/bering-uclibc/contrib/
as you suggest. At the moment I have a single document which covers all
of the packages. I'll look at how best to divide that up across the four
- or at least split apart the NFS and LVM2 aspects.
In terms of dependencies:
NFS needs:
- In the uClibc .config file:
UCLIB_HAS_FULL_RPC=Y
- In the Kernel .config file:
CONFIG_NFSD=m (for the kernel NFS server code)
CONFIG_NFSD_V3=y(otherwise only get NFS V2)
CONFIG_NFSD_TCP=y (optional - only for NFS over TCP)
CONFIG_LOCKD_V4=y (automatically set)
LVM2 itself doesn't need much, but it does need the kernel Device
Mapper, which comes as a kernel source patch. There's a 2.4 kernel
patchset available here: http://sources.redhat.com/dm/patches.html which
I used successfully. Once the patch is applied, a couple of new kernel
modules can be built: CONFIG_BLK_DEV_DM=m and CONFIG_BLK_DEV_DM_MIRROR=m
LVM1, on the other hand, would have only required a new kernel module
since I believe it does more of the work in user space. I chose to go
with LVM2 for compatibility with the syntax and capabilities I know from
e.g. Fedora, and for the extra flexibility that the Device Mapper
provides.
David
On Wed, 2008-03-19 at 09:18 +0100, Eric Spakman wrote:
Hi David,
Very nice!
NFS support indeed needs an uClibc change (which adds a lot of size), but
LVM2 only needs a kernel module AFAIK so would be an easy one.
Anyway, people who need NFS server support can create there own packages
if they like with the provided documentation.
The setup can be added to
leaf.cvs.sourceforge.net/leaf/src/bering-uclibc/contrib/ which you can do
with your sourceforge account. Or you can send me the sources and I can
add it. It would be a pity if the setup would get lost.
Eric
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/vse012070mrt/direct/01/
___
leaf-devel mailing list leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel
