From: Hans Deragon <hans@deragon.biz>
To: autofs@linux.kernel.org
Subject: backfstype parameter supported.
Date: Tue, 29 Jun 2004 08:40:13 -0400 [thread overview]
Message-ID: <40E1632D.1080903@deragon.biz> (raw)
Greetings.
Newbie with automount. Its been a week I tried to communicate with H. Peter
Anvin at hpa|at|zytor.com but never received any answer. I then found this
mailing list.
cachefs is not supported by Linux. In a mix Solaris/Linux environment,
where NIS is provided by Solaris, many yp maps specify cachefs as the
filesystem, but backfstype is set to nfs. Automount does not support backfstype.
Here is a exert of an entry:
.. fstype=cachefs,cachedir=<dir>,backfstype=nfs ...
I changed the code and now I have a modified 4.1.3 version which tries for
the filesystem defined with "fstype" and if this fails, "backfstype" is then
tried. It works.
My patch is not perfect though. While trying "cachefs", modprobe errors
shows up in /var/log/messages. Until backfstype also fails, ideally no error
message should be emitted. Maybe there is a way to test for the existance of
the kernel module before actually try to load it, thus avoiding error messages.
Altough I am a programmer, I do not program in C and do know pratically
nothing about system calls. I would like my patch to be accepted in the main
branch and that someone experienced with autofs clean it up.
Please comment. I would be glade to send you the patch, but first I have to
read "man patch" to figure out how to generate one. :) Its a pretty small
change to the code.
Best regards,
Hans Deragon
--
Consultant en informatique/Software Consultant
Deragon Informatique inc. Open source:
http://www.deragon.biz http://facil.qc.ca (Promotion du libre)
mailto://hans@deragon.biz http://autopoweroff.sourceforge.net (Logiciel)
next reply other threads:[~2004-06-29 12:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-29 12:40 Hans Deragon [this message]
2004-06-29 14:03 ` backfstype parameter supported raven
2004-06-29 14:40 ` Hans Deragon
2004-06-29 23:50 ` Ian Kent
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=40E1632D.1080903@deragon.biz \
--to=hans@deragon.biz \
--cc=autofs@linux.kernel.org \
/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.