GeezerVison

This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these messages) The topic of this article may not meet Wikipedia's notability guidelines for products and services. Please help demonstrate the notability of the topic by citing reliable secondary sources that are independent of the topic and provide significant coverage of it beyond a mere trivial mention. If notability cannot be shown, the article is likely to be merged, redirected, or deleted. Find sources: "Berkeley Automounter" – news · newspapers · books · scholar · JSTOR (September 2011) (Learn how and when to remove this message) This article relies excessively on references to primary sources. Please improve this article by adding secondary or tertiary sources. Find sources: "Berkeley Automounter" – news · newspapers · books · scholar · JSTOR (September 2011) (Learn how and when to remove this message) (Learn how and when to remove this message)

In computing the Berkeley Automounter (or amd) is a computer automounter daemon which first appeared in 4.4BSD in 1994. The original Berkeley automounter was created by Jan-Simon Pendry in 1989 and was donated to Berkeley.^[1] After languishing for a few years, the maintenance was picked up by Erez Zadok, who has maintained it since 1993.

The am-utils package which comprises and is included with FreeBSD, NetBSD, and OpenBSD. It is also included with a vast number of Linux distributions, including Red Hat Enterprise Linux, Fedora Core, ASPLinux, Trustix, Mandriva, and others.

The Berkeley automounter has a large number of contributors, including several who worked on the original automounter with Jan-Simon Pendry.

It is one of the oldest and more portable automounters available today, as well as the most flexible and the most widely used.

There are a few "side effects" that come with files that are mounted using automounter, these may differ depending on how the service was configured.

• Access time of automounted directories is initially set to the time automounter was used to mount them, however after the directories are accessed, this statistic changes.
• On some systems, directories are not visible until the first time they are used. This means commands such as ls will fail.
• If mounted directories are not used for a period of time, directories are unmounted.
• When automounter mounts directories, they are said to be owned by root until someone uses them, at that time the correct owner of the directory shows up.

• Am-utils Home Page (home of amd)
• RPMs from rpmfind.net