From: Amit Gud <agud@redhat.com>
To: Neil Brown <neilb@suse.de>
Cc: nfs@lists.sourceforge.net, Steve Dickson <SteveD@redhat.com>
Subject: [PATCH 0 / 2] Move NFS mount code from util-linux to nfs-utils
Date: Thu, 08 Jun 2006 15:05:27 -0400 [thread overview]
Message-ID: <448874F7.1070504@redhat.com> (raw)
Hello Neil,
Here are the patches for nfs-utils part to move the NFS mount code from
util-linux to nfs-utils. Let me know if there are any issues.
Patch description is below:
---
Moves the NFS mount code out of util-linux to nfs-utils. The primary
reason being ease of maintainability, and keeping util-linux away from
all the filesystem-specifc worries.
Adds a new directory 'mount' under utils. Creates a binary mount.nfs.
Three symbolic links are created to this binary - mount.nfs4, umount.nfs
and umount.nfs4. It is simpler and avoids code duplication (or overhead
of fork->exec) by keeping umount code in a single binary along with the
mount code. Mount code uses umount to handle certain fail cases. It also
makes sense to keep single binary for all the versions of the NFS, as
opposed to having seperate binaries mount.nfs and mount.nfs4, since the
code falls back to lower version if mounting with v4 fails. Adds two man
pages - mount.nfs(8) and umount.nfs(8).
Patches are split into two parts:
[1/2] nfsmount-migration-to-nfsutils-v2.patch
[2/2] nfsmount-migration-to-nfsutils-support-v2.patch
After applying the patches, do 'sh autogen.sh' before configuring and
compiling.
---
AG
--
May the source be with you.
http://www.cis.ksu.edu/~gud
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
reply other threads:[~2006-06-08 19:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=448874F7.1070504@redhat.com \
--to=agud@redhat.com \
--cc=SteveD@redhat.com \
--cc=neilb@suse.de \
--cc=nfs@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.