Eric L. Green wrote:

Please don't! Just use YaST to set up your nameserver!

Not needed. Just add the user to the "uucp" group and the "dialout" group.

...

3. chown root.root /usr/sbin/pppd

PLEASE please don't! It's already chown'ed and chmod'ed! The SuSE people did this one right (unlike Red Hat, sigh).

...

8. put the ezppp binary in each dialout users home directory and let them own it.

Err, just stick it into /usr/local/bin. The setup file(s) will still be stored into each dialout users' home directory.

Or better yet, just download the "ezppp" rpm from ftp.redhat.com and let 'rpm' manage where it is installed.

The chmod's and chown's are NOT needed with SuSE. I dialout just fine using ezppp with the default permissions. Just add the user to the "dialout" and "uucp" groups. The chmod's and chown's are only needed with distributions (such as Red Hat) that don't have pppd already chown'ed, chgrp'ed, and chmod'ed with the proper permissions.

Well Gary, thanks for pointing all this out.!!!!! To be honest, I have been having trouble with security and Suse, the way I had it set up. Yesterday after I posted that message, I was online for about an hour, and after rebooting.........MY ROOT PASSWORD was gone!!!!! The login would accept my users password, but not root. Someone did something while I was online. I only had the yast security set to easy, but it is scary to realize how vulnerable you can be with a faulty setup. What do you think happened, did they knock out my shadowed password? I'm learning the hard way. -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e