From: Chip Salzenberg <chip@pobox.com>
To: nfs@lists.sourceforge.net
Subject: Debian, SIGPIPE, "libnfsidmap", and init.d vs. umount
Date: Sat, 4 Dec 2004 17:15:04 -0500 [thread overview]
Message-ID: <20041204221504.GD6146@perlsupport.com> (raw)
Debian needs a bugfix release of nfs-utils, because of the SIGPIPE
bug. This being my job, I figured I could grab the HEAD version of
nfs-utils. And since the Debian sarge release is coming up soon (no,
really), I hoped I'd find something unlikely to crash; instead I'm
having difficulty with the build.
I gather that "libnfsidmap" is what I'll find in:
http://www.citi.umich.edu/projects/nfsv4/linux/libnfsidmap/
Is there some reason this hasn't been made part of Debian already,
seeing as how it already contains Debian build infrastructure?
Also, is it a bug or a feature that the NFS startup scripts know how
to mount special-purpose filesystems, but not unmount them?
--
Chip Salzenberg - a.k.a. - <chip@pobox.com>
People are supposed to die for freedom. Not the other way around.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2004-12-04 22:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-04 22:15 Chip Salzenberg [this message]
2004-12-06 0:34 ` Debian, SIGPIPE, "libnfsidmap", and init.d vs. umount Neil Brown
2004-12-06 0:45 ` J. Bruce Fields
2004-12-06 2:02 ` Chip Salzenberg
2004-12-06 2:05 ` Chip Salzenberg
2004-12-06 2:29 ` Neil Brown
2004-12-06 19:39 ` Steve Dickson
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=20041204221504.GD6146@perlsupport.com \
--to=chip@pobox.com \
--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.