--- /dev/null
+ Am-utils Frequently Asked Questions
+
+Note: we started this FAQ only on March 15, 2005; so it's not long or
+comprehensive, yet. Amd is much older than that, and so there's a lot of
+information that's already available in other forms. If this FAQ doesn't
+answer your questions, see information in the following sources:
+
+1. The Am-utils book: http://www.am-utils.org/docs/amd-book/
+
+2. The Am-utils user manual, which is part of the distribution and is also
+ available from www.am-utils.org.
+
+3. The www.am-utils.org Web site resources, especially the "am-utils" mailing
+ list (and its archives).
+
+4. In the am-utils distribution (always use the latest ones), see all of the
+ various README files (README, README.autofs, README.ldap, README.osx, and
+ README.y2k). The "BUGS" file also lists useful information about bugs
+ and problems with specific OSs which affect Amd. All of these text files
+ are also available from www.am-utils.org.
+
+5. Some FAQ questions (including newbie questions) are available here:
+ http://www.kernelcorp.com/resources_faqs.html
+
+6. Some problems are known bugs but have not been fixed yet: this are
+ listed in bugzilla in https://bugzilla.am-utils.org/
+
+If you have additions to this FAQ, please let us know at
+am-utils@am-utils.org.
+
+Thank you,
+The Am-utils development team.
+
+<FAQ>
+
+*** Linux Questions
+
+Q1. When I use Amd with Autofs and I restart Amd, how come it cannot remount
+ the Autofs partitions?
+
+A1. This is a limitation of the Linux Autofs kernel module (for both autofs
+ v2. and v3). The Linux Autofs does not allow restarting automounted
+ points. There's nothing Amd can do about this. In fact, the same
+ problem exists if you use the userland "automount" daemon instead of
+ Amd. Hopefully Autofs-v4 or the separate effort of Autofs-NG will
+ address this serious problem.
+
+ Note that Amd itself can restart autofs automounted points just fine on
+ OSs that support it, for example Solaris.
+
+
+Q2. When I use Amd, I get this console message frequently: "mount version
+ older than kernel." Is it a problem?
+
+A2. No, it's a harmless warning message that the Linux kernel prints for NFS
+ mounts. The intent was to alert administrators that the kernel has
+ supposedly a different version of the mount(2) code than a userland
+ program used. This happens if you compile Amd against kernel headers
+ that are different than the kernel you're running. If the message
+ really bothers you, then one way to "fix" the problem is to recompile
+ Amd against the same kernel headers as the running kernel.
+
+ Nevertheless, it is a relatively useless message because as far as we
+ know, the NFS v2 and v3 mount codes have been in perfect sync between
+ the userland and kernel sides, and were "standardized" for years
+ already. This warning message caused more unnecessary worry among
+ administrators than helping alert them to legitimate problems.
+
+</FAQ>
i386-pc-linux-rh8.0 ezk ezk ezk ezk -
i386-pc-linux-rh9 ion ion ion ion ion
i386-pc-linux-rhel3 ezk ezk ezk ezk -
+i386-pc-linux-rhel4 ezk ezk ezk ezk -
i386-pc-linux-suse8.2 ezk ezk ezk ezk -
i386-pc-linux-suse9.1 ezk ezk ezk ezk -
i386-pc-solaris2.10 ro ro ro - -
mipsel-unknown-linux-rhPS2 ezk ezk ezk ezk -
powerpc-apple-darwin7.6.0 ezk ezk ezk ezk -
powerpc-apple-darwin7.7.0 ezk ezk ezk ezk -
+powerpc-apple-darwin7.8.0 ezk ezk ezk ezk -
powerpc-ibm-aix5.1.0.0 ion ion ion ion[X] ion[1,2]
powerpc-ibm-aix5.2.0.0 ezk ezk ezk ezk -
powerpc-ibm-aix5.3.0.0 ezk ezk ezk ezk -
am-utils-clean: clean maintainer-clean-aminfo maintainer-clean-vti
# personal rule for Erez Zadok to generate and install html docs
-alldocs: ps install-NEWS install-INSTALL install-ChangeLog install-AUTHORS install-tasks install-autofs install-y2k install-BUGS install-html install-ps install-MIRRORS
+alldocs: ps install-NEWS install-INSTALL install-ChangeLog install-AUTHORS install-tasks install-autofs install-y2k install-ldap install-osx install-BUGS install-FAQ install-html install-ps install-MIRRORS
AMU_HTML_TOP=$(HOME)/proj/www/docs/am-utils
install-html: $(AMU_HTML_TOP)/am-utils-all.html
$(AMU_HTML_TOP)/y2k.txt: $(top_srcdir)/README.y2k
install -c -m 644 $< $@
+install-ldap: $(AMU_HTML_TOP)/ldap.txt
+$(AMU_HTML_TOP)/ldap.txt: $(top_srcdir)/README.ldap
+ install -c -m 644 $< $@
+
+install-osx: $(AMU_HTML_TOP)/osx.txt
+$(AMU_HTML_TOP)/osx.txt: $(top_srcdir)/README.osx
+ install -c -m 644 $< $@
+
install-BUGS: $(AMU_HTML_TOP)/BUGS.txt
$(AMU_HTML_TOP)/BUGS.txt: $(top_srcdir)/BUGS
install -c -m 644 $< $@
+install-FAQ: $(AMU_HTML_TOP)/FAQ.txt
+$(AMU_HTML_TOP)/FAQ.txt: $(top_srcdir)/FAQ
+ install -c -m 644 $< $@
+
install-MIRRORS: $(AMU_HTML_TOP)/MIRRORS.txt $(AMU_HTML_TOP)/MIRRORS.html
$(AMU_HTML_TOP)/MIRRORS.txt: $(top_srcdir)/MIRRORS.txt
install -c -m 644 $< $@
- linux support for ext3
-- support executable maps: run a program/script and use its output as the
- map data.
-
- be able to pass generic mount options to systems w/ a mount(2) that
supports it (Linux). Perhaps genopt="foo,bar" syntax.
"=" sign. Note this isn't so trivial because 'value' may include "="
signs.
+- NFSv4 support (such a short "tasks" entry given how much work it is :-)
+
+
* documentation
- document what can and what can't be a top-level mount type (i.e. a
map-backed or map-holding type). Currently that's toplvl, auto, and
- nfsx status unknown
- local filesystems (ufs, etc) status unknown
+FreeBSD:
+- just do it
+
All:
- mntfs->mf_fo->opt_fs can contain garbage sometimes??
projects / am-utils-6.1.git / commitdiff