> Buchan Milne wrote:
>> Bryan Whitehead wrote:
>>

>>>>>>am-utils is a very much-needed package for Linux to integrate into
>>>>>> big "UNIX shops".
>>>>>>
>>>>>>NASA/JPL (at least in my section) is a big "UNIX Shop". Wiothout
>>>>>> am-utils we are pretty screwed... is there a reason this package
>>>>>> was removed from 9.2 ? Has it just been renamed?
>>>>>>
>>>>>
>>>>>BTW, this package was removed from 9.1 also. I made my own RPM from
>>>>> the only in 9.0, but it's still a hassle.
>>>>>
>>>>>When I reccomend Mandrake to other admins the first thing they ask
>>>>> is "Where fsck is am-utils"? I then send them some RPM's... But it
>>>>> would be nice if it was shipped standard...
>>>>
>>>>And you are using it instead of autofs because...?
>>>>
>>>
>>>Because autofs is very limited. Example:
>>>
>> [EMAIL PROTECTED] bgmilne]$ cd /net/hermes
>> [EMAIL PROTECTED] hermes]$ ls
>> home/
>
>
> does hermes only export one mountpoint?

Yes, actually it's /home/projects ...

> Here is a typical machine at
> JPL: [EMAIL PROTECTED] ~]$ cd /net/s383
> [EMAIL PROTECTED] s383]$ ls
> export/
> [EMAIL PROTECTED] s383]$ ls export/
> home1/  home6/  proj1/   proj14/  proj2/   proj24/  proj29/  proj5/
> home2/  home7/  proj10/  proj15/  proj20/  proj25/  proj3/   proj6/
> home3/  home8/  proj11/  proj17/  proj21/  proj26/  proj30/  proj7/
> home4/  mail/   proj12/  proj18/  proj22/  proj27/  proj31/  proj8/
> home5/  opt/    proj13/  proj19/  proj23/  proj28/  proj4/   proj9/
> [EMAIL PROTECTED] s383]$
>
> home1, home2, etc etc are all different disk arrays and mount points
> with different export options to different machines.
>
>
>> [EMAIL PROTECTED] hermes]$ cd /net/hercules
>> [EMAIL PROTECTED] hercules]$ ls
>> home/
>> [EMAIL PROTECTED] hercules]$ ls home/
>> groups/  projects/  users/
>> [EMAIL PROTECTED] hercules]$ cd ../ftp
>> [EMAIL PROTECTED] ftp]$ ls
>> var/
>
>> (using the default autofs config, plus our own maps in LDAP which
>> handle /cae - ordinarily I don't ever go in /net since most stuff I
>> need is under /cae and linked into /home, so these were automounted by
>> autofs)
>>
>
> Thanks for showing me the world of "every machine has a LDAP entry".

Automount maps have nothing to do with machine entries in LDAP, but each
automount entry would need an LDAP entry:
$ ldapsearch -x "(objectclass=automountmap)" -LLL
dn: ou=auto.cae,ou=Mounts,dc=cae,dc=co,dc=za
objectClass: top
objectClass: automountMap
ou: auto.cae

dn: ou=auto.master,ou=Mounts,dc=cae,dc=co,dc=za
objectClass: top
objectClass: automountMap
ou: auto.master

$ ldapsearch -x "(objectclass=automount)" -LLL
dn: cn=users, ou=auto.cae,ou=Mounts,dc=cae,dc=co,dc=za
objectClass: automount
automountInformation: -rw,hard,nosuid,rsize=8192,wsize=8192
hercules:/home/users
cn: users

dn: cn=groups, ou=auto.cae,ou=Mounts,dc=cae,dc=co,dc=za
objectClass: automount
automountInformation: -rw,hard,nosuid,rsize=8192,wsize=8192  
hercules:/home/groups
cn: groups

dn: cn=projects, ou=auto.cae,ou=Mounts,dc=cae,dc=co,dc=za
objectClass: automount
automountInformation: -rw,hard,nosuid,rsize=8192,wsize=8192  
hermes:/home/projects
cn: projects

dn: cn=/net, ou=auto.master,ou=Mounts,dc=cae,dc=co,dc=za
objectClass: automount
automountInformation:: L2V0Yy9hdXRvLm5ldAktLXRpbWVvdXQ9NjA=
cn: /net

dn: cn=/cae, ou=auto.master,ou=Mounts,dc=cae,dc=co,dc=za
objectClass: automount
automountInformation: ldap:dc=cae,dc=co,dc=za
cn: /cae


>
> But I live in the world of NIS and DNS name resolution; with the
> addition of possible exports that are associated with neither...
>
>> The defualt config also has some things under /misc (cdrom,floppy).
>>
>> BTW, if you choose LDAP auth during install, you should now get autofs
>> installed, and if you have LDAP automount maps setup well, they should
>> work out-the-box (I still need to test this though ...).
>>
>> Maybe David Walser can comment on some of these actions would be
>> worthwhile for NIS also (although it may be too late).
>>
>
> If you can show me how I can get this working with autofs (with NIS or
> without NIS)... Then I'll eat crow and shutup...
>
> Now lets say a computer outside your org (not in your LDAP, or NIS)
> exports NFS to you; can you do this:
>
> cd /net/<some-machine.jpl.nasa.gov>/ and browse?

[EMAIL PROTECTED] bgmilne]$ ls /net
[EMAIL PROTECTED] bgmilne]$ ls /net/hercules
home/
[EMAIL PROTECTED] bgmilne]$ ls /net/hercules/home
groups/  projects/  users/
[EMAIL PROTECTED] bgmilne]$ /usr/sbin/showmount -e hercules
Export list for hercules:
/home/users    146.232.174.0/255.255.255.0
/home/groups   146.232.174.0/255.255.255.0
/home/projects 146.232.174.0/255.255.255.0

(yes, we only have 3 large filesystems on this box, and one larger one on
hermes - our other file server :-()

>
> What about an IP?
>
> [EMAIL PROTECTED] ~]$ cd /net/137.78.61.94/
> [EMAIL PROTECTED] 137.78.61.94]$ ls
> export/
> [EMAIL PROTECTED] 137.78.61.94]$
>

[EMAIL PROTECTED] bgmilne]$ ls /net/146.232.174.19/
var/
[EMAIL PROTECTED] bgmilne]$ /usr/sbin/showmount -e 146.232.174.19
Export list for 146.232.174.19:
/var/ftp/pub 146.232.174.0/255.255.255.0

(146.232.174.19 = internal ftp server)

> With am-utils I can browse any machine in the world that allows me to
> NFS mount regardless of it's entry in NIS or LDAP or DNS or "autofs
> map"...

As you will see, the only entries in our LDAP automount maps are those we
need all the time (/home/{users,groups,projects}) on most machines (the
ones people need to be sure of, so we can modify the LDAP automount
entries and be sure each machine will use the correct share on next
access), I have done no configuration on /net and /misc (just using the
default auto.master, auto.net, auto.misc - LDAP stuff is picked up
automagically without *any* configuration besides that done during
installation for LDAP auth).

I can browse any machine our firewall will let me use NFS/portmap to ...

We aren't a "big unix shop" (we have more Windows boxen), but I still
haven't seen anything am-utils can do that autofs can't.

Regards,
Buchan


*****************************************************************
Please click on http://www.cae.co.za/disclaimer.htm to read our
e-mail disclaimer or send an e-mail to [EMAIL PROTECTED] for a copy.
*****************************************************************

Reply via email to