autofs design doc ?

autofs design doc ?

[Thierry BULTEL]

[-- Attachment #1.1: Type: text/plain, Size: 741 bytes --]


 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.

What I would like to understand, above all, is the detailed interaction 
scheme between automount and the kernel.
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.

Any help would be really appreciated !

Thanks,
Thierry Bultel 

[-- Attachment #1.2: Type: text/html, Size: 907 bytes --]

[-- Attachment #2: Type: text/plain, Size: 140 bytes --]

_______________________________________________
autofs mailing list
autofs@linux.kernel.org
http://linux.kernel.org/mailman/listinfo/autofs

Re: autofs design doc ?

[Jeff Moyer]

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