On Tue, Jul 29, 2014 at 9:50 AM, Martin Møller Skarbiniks Pedersen < [email protected]> wrote:
> 203.3 autofs > Because is it widely used anymore ? I haven't touch it for many years. > Huh? It's widely and heavily used, especially in departmental networks where there are clear, network-based storage. Heck, with the revolution in software-defined storage, they are making a _huge_ comeback. E.g., things like Red Hat Storage (Gluster) can share out via NFSv3, so workstations can mount it, that is also the results store for Hadoop. I would say automounter maps in IdM (IPA) is probably the #3 thing I'm asked about after centralized SSH keys and sudoers files. People still have a real need for automounted NFS and other paths in a network, and autofs -- especially via published LDAP maps. I.e., saying one doesn't need to know about autofs in the POSIX world (given the common publication of maps into LDAP trees) is like saying one doesn't need to know about UNC handling in the Windows world (given the common publication of maps into AD domains). Even if most people are using a GUI, and browsing via NFS 4.x these days (which can be encapsulated completely over 2049/tcp), there is a reason for LPIC-2 to know what the heck an automounter map looks like. That way when a fellow admin runs a "getent auto.home" or "getent (othermap)" to get the published maps for their IPA domain or LDAP tree, they don't look like a deer in headlights. ;) The only question for the future is how much will the userspace autofs will be used when systemd also handles automounter capability. But given the systemd focus is more limited, I still see autofs being around for enterprise-wide maps. 205.1 arp > I don't think it belongs here. And it isn't that useful. > Ummm ... isn't that useful? I still use it heavily for troubleshooting. -- bjs
_______________________________________________ lpi-examdev mailing list [email protected] http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
