3) I tried to compile sniffit and I get "bash: configure: command not found" To work around this I have to put in the complete path of the configure script, even though my pwd is the dir where configure exists. The same goes when I try to run the binary from this dir, so I put the binary in a dir which is in my path, but why are things behaving this way?

Luis, did you try ./configure ? When you tipe a command, bash uses $PATH to find it. Usually PATH does not include actual dir ( ./ ) so when you type configure bash won't find it. You don't have to move configure, just type ./configure to tell bash to look at your actual dir first. It's not a S.u.S.E problemm. It's a sintaxis one. Hope I've been helpful. DON'T FEAR THE PENGUINS Carlos Betancourt CETI-UNET Venezuela -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e