version 1.2, 2016/08/26 07:50:59
|
version 1.9, 2019/12/12 16:37:13
|
Line 3
|
Line 3
|
title="New automounter" |
title="New automounter" |
|
|
contact=""" |
contact=""" |
[tech-kern](mailto:tech-kern@NetBSD.org), |
[tech-kern](mailto:tech-kern@NetBSD.org) |
[tech-net](mailto:tech-net@NetBSD.org) |
|
""" |
""" |
|
|
mentors=""" |
mentors=""" |
Line 13 mentors="""
|
Line 12 mentors="""
|
category="filesystems" |
category="filesystems" |
difficulty="medium" |
difficulty="medium" |
duration="3 months" |
duration="3 months" |
|
done_by="Tomohiro Kusumi <tkusumi@netbsd.org> (a port from DragonFlyBSD which was a port from FreeBSD)" |
|
|
description=""" |
description=""" |
NetBSD currently uses amd for automatically mounting (network) file systems. This software package implements an automounter file system as a userland NFS daemon. While this generally works it has major drawbacks: |
NetBSD currently uses amd for automatically mounting (network) file systems. This software package implements an automounter file system as a userland NFS daemon. While this generally works it has major drawbacks: |
Line 34 compatible. (One could also write a new
|
Line 34 compatible. (One could also write a new
|
like a dominant strategy.) |
like a dominant strategy.) |
|
|
Another possible approach is a new userland daemon using puffs. |
Another possible approach is a new userland daemon using puffs. |
|
|
|
Note that automount configuration is a complex and largely unsolved |
|
problem. While it's desirable to be compatible with existing |
|
automounter configuration (because often organizations like to |
|
distribute automounter maps through NIS or other facilities) it's also |
|
desirable to have a simple, comprehensible, and cogent configuration |
|
scheme and these desires are rather at odds. |
""" |
""" |
]] |
]] |
|
|
[[!tag gsoc]] |
|