SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
(Slack 9.0) Got lilo to work, x configuration ok, gnome fine, and can dial out as root. Created a user group for dialing out, setuid'd pppd. As a non-root user I can type /usr/sbin/ppp-go and it will respond with "script failed". I'm thinking maybe a permission problem? What are the other associated ppp files and what permissions should they be? What about the options file? Do I need to do a pppsetup for a non-root user? Thx in advance.
What happens when you start
ppp-go with -d as root? Will it
then connect for the other users
if they initiate traffic, like trying to
access a webpage?
That's what I was using while still
routing my network through the modem
on dialup ;) (Slack 8.1, though)
Success, finally. Carefully following install of wvstreams through patch, and wvdial, I was able to at least get wvdial to respond. But, I had a problem in having getting wvdialconf to detect the modem. It turns out "setserial" clobbers it, afterall, wvdial is supposed to be smart. After disabling setserial (and rebooting), I followed README instructions located in the wvdial untarred directory. Modem lights doesn't respond yet, but now I can get to the net as a normal user in slack9/gnome!
Did wvdial install? I noticed some strangeness when installiing wvstreams through patch, but it did not return an error. If you're having a problem installing wvdial, I suggest starting afresh. Download wvstreams and patch from the linuxfromscratch site and see what happens. Did you notice the spelling of "crypto.patch"? The patch files need to be one level above the untarred wvstreams directory, and input the commands from the untarred wvstreams directory.
No. With the wvstreams-patches one level above your untarred wvstreams directory, type in the following from within the untarred wvstreams directory, pressing "enter" after each line:
patch -Np1 -i ../wvstreams-3.70-wvcrpyto.patch &&
patch -Np1 -i ../wvstreams-3.70-wvresolver.patch &&
make PREFIX=/usr LDFLAGS="-lcrypt" &&
make PREFIX=/usr install
After the last line, wvstreams should install. Then after wvstreams installs, then install wvdial.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.