From: "Bryan J. Smith" <b.j.smith@ieee.org>
To: Dave Ingram <davei@wolfram.com>
Cc: "Bryan J. Smith" <b.j.smith@ieee.org>, nfs@lists.sourceforge.net
Subject: Re: recursive NFS export of mounted ISO images -- Automounter Maps?
Date: Wed, 23 Oct 2002 16:44:13 -0400 (EDT) [thread overview]
Message-ID: <1035405853.3db70a1d229ae@webmail.smithconcepts.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0210231520230.31286-100000@wopr.wolfram.com>
Quoting Dave Ingram <davei@wolfram.com>:
> I understand. But I think it's odd that I did the following
> successfully:
> 1. Mounted 3 ISO images from the /Source partition to /Jukebox
> 2. Added entries for each of the /Jukebox/... directories into
> 'exports'
> 3. Reloaded NFS
> 4. Successfully NFS mounted and used the files from the server
> How is that possible if one cannot cross filesystem boundaries on
> the server side? The source partition is different than the destination
> partition.
And you're mounting the source partition too, right? That should work then.
> Ah. That's provided that all your clients can deal with autofs. We
> have every *NIX flavor you can think of here. The single common
> denominator for them is NFS.
> Well, you're lucky - Linux and Solaris support autofs and have
> consistent mechanisms for configuring them. Some of our *NIX's either
> don't have anything like autofs/NIS or have completely different ways of
> configuring them.
Really? I've messed with AIX and Irix too and it had both as well.
Sometimes I've had to create maps named "auto_master_irix" and similiar, but it
worked.
> I'm still confused then how I was able to perform the experiment
> quoted earlier. From all appearances, I *did* cross filesystems (which
> as I said confuses me greatly)
If you mount _both_ the .iso source _and_ the loopback mount, it _will_ work.
> You're assuming again that all the client machines HAVE something
> even remotely like "mkisofs". A lot of them do not.
First off, mkisofs runs on _everything_ I've seen, even Windows.
Secondly, run "mkisofs" on the server, but write on the client.
> Unfortunately that just isn't how our software engineering system
> works. SQA is explicit about having the files they test be directly
> FROM the ISO image.
As an engineer myself, used to working in production testing environments, I
find this logic rather flawed. You aren't really running from the .iso image
anyway. ;-P
> Burning many CDs every day and shuffling them around is a
> nightmare, which is why we're trying to do this.
Again, I think your QA process is not exactly true.
> No, I *have* worked with automounter, under Solaris several years
> ago.
What UNIX client flavors are you running anyway?
--
Bryan J. Smith, E.I. Contact Info: http://thebs.org
A+/i-Net+/Linux+/Network+/Server+ CCNA CIWA CNA SCSA/SCWSE/SCNA
---------------------------------------------------------------
limit guilt = { psychopath,
remorse->0 innocent }
-------------------------------------------------------
This sf.net email is sponsored by: Influence the future
of Java(TM) technology. Join the Java Community
Process(SM) (JCP(SM)) program now.
http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0002en
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2002-10-23 20:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-23 19:51 recursive NFS export of mounted ISO images Dave Ingram
2002-10-23 20:07 ` seth vidal
2002-10-23 20:16 ` Dave Ingram
2002-10-23 20:19 ` seth vidal
2002-10-23 20:07 ` David B. Ritch
2002-10-23 20:17 ` recursive NFS export of mounted ISO images -- Automounter Maps? Bryan J. Smith
2002-10-23 20:29 ` Dave Ingram
2002-10-23 20:44 ` Bryan J. Smith [this message]
2002-10-23 20:55 ` Dave Ingram
2002-10-23 21:18 ` Bryan J. Smith
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=1035405853.3db70a1d229ae@webmail.smithconcepts.com \
--to=b.j.smith@ieee.org \
--cc=davei@wolfram.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.