From: Roger Zimmermann <Roger.Zimmermann@arcor.de>
To: nfs@lists.sourceforge.net
Subject: Is this possible using NFS ?
Date: Mon, 15 Aug 2005 23:13:06 +0200 [thread overview]
Message-ID: <1124140386.11051.22.camel@rudi> (raw)
Hi,
I've got a server, where a varying number of disks is connected.
The layout:
/exampledir/onedisk/sometimes-mounted/etc
/exampledir/onotherdisk/sometimes-mounted/etc
/exampledir/harddisk/always-mounted
/exampledir/otherdata
can I simply export /exampledir from the server
and mount it via NFS by clients without having each client to inform
when e.g 'onedisk' is connected or removed ?
THNX, Roger
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2005-08-15 21:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-15 21:13 Roger Zimmermann [this message]
2005-08-24 22:18 ` Is this possible using NFS ? James Yarbrough
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=1124140386.11051.22.camel@rudi \
--to=roger.zimmermann@arcor.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.