In this article we are going to explore the fascinating history of Berkeley Automounter, a topic that has captured the attention of millions of people over the years. From its origins to its impact on today's society, Berkeley Automounter has played a crucial role in shaping our way of understanding the world. Throughout this article, we will examine in detail the most relevant aspects of Berkeley Automounter, from its first manifestations to the most recent innovations that have revolutionized the way we perceive it. Additionally, we will discover how Berkeley Automounter has left his mark on popular culture, influencing everything from art and fashion to politics and technology. Get ready to immerse yourself in the exciting universe of Berkeley Automounter and discover everything this phenomenon has to offer us.
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)
|
Developer(s) | Erez Zadok |
---|---|
Stable release | 6.2
/ Oct 30, 2014 |
Operating system | Cross-platform |
Type | NFS Automounter |
License | BSD License |
Website | http://www.am-utils.org/ |
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.[citation needed]
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.