Automounting Stuff

[jrbush82]

I'm running Slackware 8.0 and I recompiled my kernel with automount support. I have made the files /etc/auto.master /etc/auto.stuff so that it knows what it needs to do. Now I'm lost. I'm supposed to be able to run autofs start or automount start or something, and it isn't there. I went and downloaded autofs and compiled/installed it and I still had no autofs command. Any ideas what to do or where to go now?

Thanks,
Jason Bush

[jrbush82]

don't want to repost same message, so I'll respond to this one and bring it to top again... still needing help...

Thanks

[Alex Cavnar, aka alc6379]

Um... just so you know, bumping up the post is usually frowned upon.

First off, don't let this offend you, but you do know that automount isn't for local filesystems, it's for NFS, right? There isn't any package I know of that can automount local filesystems...

Also, if you compiled and installed it, but you are unable to find it, it could have installed it in /usr/local, which some people don't have in their PATH. Try editing your ~/.bashrc or ~/.bash_profile (whichever you have your PATH variable set in) and set both /usr/local/bin and /usr/local/sbin into your PATH variable.

[jrbush82]

auctually, during the installation of the program, I was looking at compile information, and I noticed an error... maybe this could be a reason for some problems I'm having? At least a place to start...

make[1]: Entering directory `/home/jason/downloads/autofs-3.1.7/modules'
gcc -shared -O3 -fomit-frame-pointer -Wall -I../include -fpic -DAUTOFS_LIB_DIR=\"/usr/lib/autofs\" -DPATH_AUTOMOUNT=\"/usr/sbin/automount\" -o lookup_program.so lookup_program.c
lookup_program.c: In function `lookup_mount':
lookup_program.c:139: `OPEN_MAX' undeclared (first use in this function)
lookup_program.c:139: (Each undeclared identifier is reported only once
lookup_program.c:139: for each function it appears in.)
make[1]: *** [lookup_program.so] Error 1

I personally don't have any clue why "bringing the post to the top" is a bad thing. Oh well.. anyway, any ideas on what could be going on with that error?

Thanks,
Jason Bush

[maxl]

Originally posted by Alex Cavnar, aka alc6379:
<STRONG>Um... just so you know, bumping up the post is usually frowned upon.
</STRONG>

It is? I've been here for almost two years (despite what the name says, old one got deleted) and I've seen anyone from a beginner to a HAL bump things. I don't think it's really bad, some subjects get pushed down in a matter of an hour or so just becuase new subjects coming in.

So I mean, if you want your subject to be seen, what's wrong with bumping it? Someone new may come and have something to contribute to your problem that wasn't there when you posted before.

[jrbush82]

I would definately agree with you maxl... anyway, I have some more to add to my progress... any more help is still appreciated, as I have yet to figure out how to do this...

I have learned that you have to have the autofs daemon (automount) installed in order to use automount, so I went and installed it. I have automount support compiled into my kernel, which I know I also have to have. There is an autofs script which is supposed to start and stop it, but it doesn't work except with Red Hat or Debian, I am running Slackware. By reading stuff and looking at the autofs script for debian and red hat, I have come up with this:

/usr/sbin/automount --timeout 1 /.autofs file /etc/auto.misc

and inside the auto.misc file is:

/mnt/dvd -fstype=iso9660,ro :/dev/hdc

.....

I also tried this for the first command:

/usr/sbin/automount --timeout 1 /mnt file /etc/auto.misc

which also didn't work, but it does show automount as a process when I do ps -aux, which is the best progress yet...

Any help would be appreciated...

Thanks,
Jason Bush

[ 21 March 2002: Message edited by: jrbush82 ]

[demian]

First off, I feel bumping a thread after a certain amount of time isn't nearly as bad as crossposting.

I can't really help much here other than pointing you to this mini how-to (http://www.linuxdoc.org/HOWTO/mini/Automount.html) which you might already know about.

[mdwatts]

Originally posted by demian:
<STRONG>First off, I feel bumping a thread after a certain amount of time isn't nearly as bad as crossposting.
</STRONG>

I certainly agree.

Automounting works with nfs and local devices such as floppy drives, cdroms and zip drives.

Does /etc/rc.d/init.d/amd exist?

This is part of amd

NAME=amd
DAEMON=/usr/sbin/amd
PIDF=/var/run/$NAME.pid
MASTERMAP_NAME=amd.master
CONF_FILE=/etc/am.d/conf

Is amd what you installed?

[jrbush82]

I don't have /etc/rc.d/init.d dir, I'm running slack, its different... but as far as amd, no I didn't install it. During the compilation of my kernel it told me I need the autofs daemon, so thats what I got... I have the automount command, I just don't think I know how to use it correctly, like the script would

[Beattie]

fstab ?

[camelrider]

This is probably silly, but does /mnt/dvd exist?
;)

[jrbush82]

fstab I do have, but that doesn't have anything to do with automount and autounmounting... it just mounts it and keeps it mounted...

/mnt/dvd does exist, but when I issue the command it removes all directories within /mnt, which confuses me... and it still doesn't work. If I try to create the dir /mnt/dvd with the automount daemon running as I issued it, it says permission denied... and that is as root... reading the automount mini howto it mentions that it may not show up, so I tried cd /mnt/dvd, and it just says it doesn't exist... sheesh, I feel so close...

Jason

[demian]

Originally posted by jrbush82:
<STRONG>when I issue the command it removes all directories within /mnt, which confuses me... </STRONG>
Hmmm. I still can't offer much but I know that when you mount anything to a non empty directory the content of that directory vanishes and is replaced but the contents of the mounted medium. So apparently something is being mounted here. What does the output of mount (without any arguments) give you in this situation (after you issue the command that causes the dirs in /mnt to vanish)?

[jrbush82]

well, when I get the current mounted file systems using 'mount', automount is there, showing in /mnt using autofs, but damn if it doesn't work... here is what I get:

/dev/hda5 on / type ext2 (rw)
none on /dev/pts type devpts (rw,gid=5,mode=620)
none on /proc type proc (rw)
automount(pid2853) on /mnt type autofs (rw,fd=5,pgrp=2853,minproto=2,maxproto=4)

I am trying every combination of setups to run automount that I can, but nothing seems to be working...

[jrbush82]

I did it! wahoo! I guess I progessed on my own, but I thank you a lot for the mount tip, I didn't know that I could view my current mounts by typing mount

[demian]

:) You got me close to compiling a kernel with automounting support and see for myself how this works. Glad you figured it out.

[jrbush82]

LOL, the fact that I spent 3 days or so on something that will only save me maybe 2 seconds every now and then is kinda stupid, but it was the fact that I couldn't figure it out, not that I wanted it so bad, lol... sad