From: Mike Waychison <Michael.Waychison@Sun.COM>
To: linux-kernel@vger.kernel.org, autofs@linux.kernel.org
Cc: thockin@hockin.org, raven@themaw.net
Subject: [announce] Autofs NG 0.1
Date: Fri, 24 Sep 2004 20:50:58 -0400 [thread overview]
Message-ID: <4154C0F2.708@sun.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi folks,
Some of you may remember my posting of a new way to do autofs in Linux a
while back:
http://marc.theaimsgroup.com/?l=linux-kernel&m=107341940326348&w=2
Anyhow, I've gotten to the point where I have code that people can play
with. I've posted it all at http://autofsng.bkbits.net
There are two repos located there, one is the userspace bits (autofsng).
~ It has the 'utility' (automount) and the autofs usermode agent
(autofs). This tree began as a automount 3.1.7 tree, but has
drastically changed. Lots of good stuff has yet to be merged in from
the automount 4 daemon.
The kernel bits are in the linux-2.6-autofsng repository. Broken out
patches are forthcoming in the next (weeks?) [*]. It has the following
major changes to it:
- - changes to the vfsmount tree structures so that you can detach and
re-attach sub-trees of the vfsmount tree. The current implementation is
admittedly a bit gross and will require work to make it pretty (and to
get rid of having to grab a rwlock on every mntget/mntput!).
- - the addition of a mountpoint file descriptor api. I don't care for
the interface at the moment, and I'll be posting interface descriptions
later on along with broken out patches so that the interface itself can
be thought through.
- - vfs native support for expiring mountpoints (and entire subtrees of
them). There currently exists a syscall entry to specify this from
userspace as a way to easily test it. As well, you can specify expiry
information using the above mountpoint file descriptor api.
- - a new module implementing the 'autofs' filesystem called autofsng.
This filesystem will support automounting of both direct and indirect
maps. It also supports 'browsing'. Most of this magic happens using
'->follow_link' walks on directory inodes. This is ugly, but it
appears to be the best way to properly handle automounting from within
the kernel.
There does remain a good amount of work to do, and I've tried to list
things on the top of my head in the autofsng/autofs/TODO file. I'm sure
I missed stuff :\
At this point, I can run and pass a ported autofs connectathon
testsuite. I'm working on figuring out how to get the testsuite
included in the package. For comparison, both autofs3 and autofs4
couldn't handle the majority (>%95) of the tests done. As well, we've
uncovered a couple of nfs related issues that we'll be following up with
on the nfs list.
So, if you have time to spare and you care about automounting, please
have a try at using it. If you are curious enough to wade through it,
feel free to give feedback/flames/comments on the code/design/weather.
Thanks,
[*] - I know it is bad practice to pop-up out of nowhere with large
changes, but I wasn't able to get anything out much earlier due to a
variety of reasons. From now on, expect to see much traffic from me as
I feed a broken-out patchsets to the list.
- --
Mike Waychison
Sun Microsystems, Inc.
1 (650) 352-5299 voice
1 (416) 202-8336 voice
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
NOTICE: The opinions expressed in this email are held by me,
and may not represent the views of Sun Microsystems, Inc.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBVMDydQs4kOxk3/MRAnQsAJ0XHLJA/HkAHTLSPjGZU75Bc3oJiQCfUWoE
p94ERBoBhTa2jG2CJjT9Er8=
=1RaX
-----END PGP SIGNATURE-----
WARNING: multiple messages have this Message-ID (diff)
From: Mike Waychison <Michael.Waychison@Sun.COM>
To: linux-kernel@vger.kernel.org, autofs@linux.kernel.org
Cc: thockin@hockin.org, raven@themaw.net, mark.fasheh@oracle.com
Subject: [announce] Autofs NG 0.1
Date: Fri, 24 Sep 2004 20:50:58 -0400 [thread overview]
Message-ID: <4154C0F2.708@sun.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi folks,
Some of you may remember my posting of a new way to do autofs in Linux a
while back:
http://marc.theaimsgroup.com/?l=linux-kernel&m=107341940326348&w=2
Anyhow, I've gotten to the point where I have code that people can play
with. I've posted it all at http://autofsng.bkbits.net
There are two repos located there, one is the userspace bits (autofsng).
~ It has the 'utility' (automount) and the autofs usermode agent
(autofs). This tree began as a automount 3.1.7 tree, but has
drastically changed. Lots of good stuff has yet to be merged in from
the automount 4 daemon.
The kernel bits are in the linux-2.6-autofsng repository. Broken out
patches are forthcoming in the next (weeks?) [*]. It has the following
major changes to it:
- - changes to the vfsmount tree structures so that you can detach and
re-attach sub-trees of the vfsmount tree. The current implementation is
admittedly a bit gross and will require work to make it pretty (and to
get rid of having to grab a rwlock on every mntget/mntput!).
- - the addition of a mountpoint file descriptor api. I don't care for
the interface at the moment, and I'll be posting interface descriptions
later on along with broken out patches so that the interface itself can
be thought through.
- - vfs native support for expiring mountpoints (and entire subtrees of
them). There currently exists a syscall entry to specify this from
userspace as a way to easily test it. As well, you can specify expiry
information using the above mountpoint file descriptor api.
- - a new module implementing the 'autofs' filesystem called autofsng.
This filesystem will support automounting of both direct and indirect
maps. It also supports 'browsing'. Most of this magic happens using
'->follow_link' walks on directory inodes. This is ugly, but it
appears to be the best way to properly handle automounting from within
the kernel.
There does remain a good amount of work to do, and I've tried to list
things on the top of my head in the autofsng/autofs/TODO file. I'm sure
I missed stuff :\
At this point, I can run and pass a ported autofs connectathon
testsuite. I'm working on figuring out how to get the testsuite
included in the package. For comparison, both autofs3 and autofs4
couldn't handle the majority (>%95) of the tests done. As well, we've
uncovered a couple of nfs related issues that we'll be following up with
on the nfs list.
So, if you have time to spare and you care about automounting, please
have a try at using it. If you are curious enough to wade through it,
feel free to give feedback/flames/comments on the code/design/weather.
Thanks,
[*] - I know it is bad practice to pop-up out of nowhere with large
changes, but I wasn't able to get anything out much earlier due to a
variety of reasons. From now on, expect to see much traffic from me as
I feed a broken-out patchsets to the list.
- --
Mike Waychison
Sun Microsystems, Inc.
1 (650) 352-5299 voice
1 (416) 202-8336 voice
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
NOTICE: The opinions expressed in this email are held by me,
and may not represent the views of Sun Microsystems, Inc.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBVMDydQs4kOxk3/MRAnQsAJ0XHLJA/HkAHTLSPjGZU75Bc3oJiQCfUWoE
p94ERBoBhTa2jG2CJjT9Er8=
=1RaX
-----END PGP SIGNATURE-----
next reply other threads:[~2004-09-25 0:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-25 0:50 Mike Waychison [this message]
2004-09-25 0:50 ` [announce] Autofs NG 0.1 Mike Waychison
2004-09-25 0:55 ` Jeff Garzik
2004-09-29 23:16 ` Stew Smith
2004-09-29 23:16 ` Stew Smith
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=4154C0F2.708@sun.com \
--to=michael.waychison@sun.com \
--cc=autofs@linux.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raven@themaw.net \
--cc=thockin@hockin.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.