From: Jeff Moyer <jmoyer@redhat.com>
To: Thierry BULTEL <thierry.bultel@wanadoo.fr>
Cc: autofs@linux.kernel.org
Subject: Re: autofs design doc ?
Date: Mon, 25 Aug 2008 09:26:04 -0400 [thread overview]
Message-ID: <x49wsi5i5ub.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <15446204.32971219413074178.JavaMail.www@wwinf2610> (Thierry BULTEL's message of "Fri, 22 Aug 2008 15:51:14 +0200 (CEST)")
Thierry BULTEL <thierry.bultel@wanadoo.fr> writes:
> Hi all,
>
> I am currently looking at autofs, and I would be interested to know if
> there exist such a documentation. Namely, I am performing a kind of
> reverse-engineering on both the daemon and the kernel parts.
This will give you the general overview:
http://people.redhat.com/~jmoyer/autofs-linux_kongress-2005.pdf
A slightly newer one is available in the OLS 2006 proceedings, here:
http://www.linuxsymposium.org/2006/linuxsymposium_procv2.pdf
> What I would like to understand, above all, is the detailed interaction
> scheme between automount and the kernel.
See above, ask questions after you've read that.
> I have understood that automount was receiving orders through a pipe,
> and replying with ioctls, but I still do not have the complete vision
> of the nature and timing of the messages. What are the respective
> responsibilities of both parts ? Also, I am still asking myself why a
> user daemon is used, and why not everything is not done in the kernel.
The autofs file system traps lookup requests. It then passes the
requests on to the userspace daemon to perform the actual lookup of the
key in the automount map and to then perform the mount. This is done in
a userspace daemon because it is too complex to be handled in the
kernel.
Cheers,
Jeff
prev parent reply other threads:[~2008-08-25 13:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-22 13:51 autofs design doc ? Thierry BULTEL
2008-08-25 13:26 ` Jeff Moyer [this message]
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=x49wsi5i5ub.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=autofs@linux.kernel.org \
--cc=thierry.bultel@wanadoo.fr \
/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.