Another issue which I'd like to point out  is why the PPP option is not
compiled into the kernel as a default option.  

Then there's the issue of why YaST needs to change permissions to kppp,
pppd and delete the resolv.conf file everytime you run it w/c results in a
"user" not being able to do dial-outs. Isn't this rather strange
considering that it is always impressed upon users not to run as "root"
except when necessary?

Here's my stupid question -- Is there something also which checks whether
there were changes done to /etc/permissions such that YaST will chnage it
back to the original?

-----------------------------------

At 10:06 AM 4/9/99 +0100, you wrote:
>
>Hello SuSE folks! My question is primary directed to Mr. Lenz Grimmer
>and SuSE developers. But if somebody knows the answer any suggestions
>will be appreciated. After I downloaded and compiled 2.2.5 kernel from
>SuSE Web Site, I can't use kppp for connection any more. Every time it
>gets frozen on "Expecting OK" from modem. The old 2.0.36 kernel works
>with kppp perfectly with the same settings. I can use minicom to connect
>when I use 2.2.5 kernel but it's not a solution. Why 2.2.5 kernel
>performs a such strange things with kppp and the modem? Lenz, did your
>developers fix this issue in the oncoming 6.1 SuSE distro? Thanks Alex
> 
>--
>To get out of this list, please send email to [EMAIL PROTECTED] with
>this text in its body: unsubscribe suse-linux-e
>Check out the SuSE-FAQ at http://www.suse.com/Support/Doku/FAQ/ and the
>archive at http://www.suse.com/Mailinglists/suse-linux-e/index.html
>
>
-----------------------------------------
Mac Q. Flores IV
Northwestern University
LinuxPowered K e r n e l  2.2.5
-----------------------------------------
--
To get out of this list, please send email to [EMAIL PROTECTED] with
this text in its body: unsubscribe suse-linux-e
Check out the SuSE-FAQ at http://www.suse.com/Support/Doku/FAQ/ and the
archive at http://www.suse.com/Mailinglists/suse-linux-e/index.html

Reply via email to