From: Scott Mcdermott <smcdermott@questra.com>
To: nfs@lists.sourceforge.net
Subject: (autofs) Re: Direct mounts on Linux
Date: Mon, 20 Jan 2003 22:08:51 -0500 [thread overview]
Message-ID: <20030121030851.GG10369@questra.com> (raw)
In-Reply-To: <p5vg0jz08z.fsf@lemming.engeast.baynetworks.com>
Paul Smith on Mon 20/01 21:48 -0500:
> I know that am-utils doesn't support it,
hmm direct mounts? well according to the docs:
The Linux kernels don't support Amd's direct mounts very well,
leading to erratic behavior: shares that don't get remounted
after the first timeout, inability to restart Amd because its
mount points cannot be unmounted, etc. There are some kernel
patches on the am-utils Web site, which solve these problems.
(I think this is talking about using the autofs support in beta
am-utils)
so I guess you need a patch, hmph.
> Well... except for direct mounts. We can all agree that they are evil
> and they suck, but the fact remains there are a lot of them out there
> and they are often hard to get rid of...
I don't agree that they are evil or that they suck. Some mounts are
static and won't change, and just a simple mount will suffice. What's
wrong with using a direct mount in this case (maybe /home/ or
/var/spool/mail/)? Is there a real argument against this besides "the
performance sucks when the directory gets large" (which is an admin
decision I think). I don't really know, we don't have large enough
directories that it becomes a problem. One other good thing about
direct mounts is that you can immediately `ls' the directory and see all
the possible entries, but this could be implemented in other ways.
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-01-21 3:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-20 18:02 Direct mounts on Linux Paul Smith
2003-01-20 21:41 ` Scott Mcdermott
2003-01-21 2:48 ` Paul Smith
2003-01-21 3:08 ` Scott Mcdermott [this message]
2003-01-21 3:53 ` (autofs) " Paul Smith
2003-01-21 4:03 ` Scott Mcdermott
2003-01-21 6:05 ` Paul Smith
2003-01-21 6:48 ` Scott Mcdermott
2003-01-21 7:05 ` Paul Smith
2003-01-21 7:23 ` [OT] " Scott Mcdermott
2003-01-21 7:59 ` Paul Smith
2003-01-21 22:59 ` Ion Badulescu
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=20030121030851.GG10369@questra.com \
--to=smcdermott@questra.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.