Hello List,
I am updated to latest (3.5) KDE from kde-redhat repository.When I run kppp,(sudo /usr/sbin/kppp), set correct modem port and ISP account.It just can't dial.
When I checked in the configure dialogs,under 'modem commands',nothing is listed. Kppp has forgotten all the modem initialisation strings!
Now, I run it as user,again the same.No initialisation strings.I give the chosen modem a name,save it and go to create a new modem,all the initialisation strings are there.But I cannot run it as I have no access right to modem as a user.
I go back and sudo again.This time,with the same procedure,there is no luck.Kppp doesn't know anything about modem initialisation.
By the By, latest linux creates ownership for the user on all devices like cdrom,floppy.
[pbhat@sidharth ~]$ ls -l /dev/hdc brw------- 1 pbhat disk 22, 0 Dec 30 2005 /dev/hdc [pbhat@sidharth ~]$ ls -l /dev/fd0 brw-rw---- 1 pbhat floppy 2, 0 Dec 30 2005 /dev/fd0
[pbhat@sidharth ~]$ ls -l /dev/ttySL0 lrwxrwxrwx 1 root root 10 Dec 30 14:26 /dev/ttySL0 -> /dev/pts/1 [pbhat@sidharth ~]$ ls -l /dev/pts/1 crw-rw---- 1 root uucp 136, 1 Dec 30 15:45 /dev/pts/1
why not on modem? Is it safe to add normal users to 'uucp' group? or change modem group to a new group like 'dialout' and make users its members ?
I can 'sudo wvdial' successfully.
Thanks,
Parameshwara Bhat
On Sat, Dec 31, 2005 at 06:25:40AM +0530, Parameshwara Bhat wrote:
Hello List,
I am updated to latest (3.5) KDE from kde-redhat repository.When I run kppp,(sudo /usr/sbin/kppp), set correct modem port and ISP account.It just can't dial.
When I checked in the configure dialogs,under 'modem commands',nothing is listed. Kppp has forgotten all the modem initialisation strings!
Now, I run it as user,again the same.No initialisation strings.I give the chosen modem a name,save it and go to create a new modem,all the initialisation strings are there.But I cannot run it as I have no access right to modem as a user.
Stop me if you know this. There are 2 kppp files on the machine. /usr/sbin/kppp is the actual program. /usr/bin/kppp is really a link to consolehelper and is set up for the user to run kppp. However, I have only had success setting /usr/sbin/kppp to SUID and running it as a normal user.
I go back and sudo again.This time,with the same procedure,there is no luck.Kppp doesn't know anything about modem initialisation.
By the By, latest linux creates ownership for the user on all devices like cdrom,floppy.
[pbhat@sidharth ~]$ ls -l /dev/hdc brw------- 1 pbhat disk 22, 0 Dec 30 2005 /dev/hdc [pbhat@sidharth ~]$ ls -l /dev/fd0 brw-rw---- 1 pbhat floppy 2, 0 Dec 30 2005 /dev/fd0
[pbhat@sidharth ~]$ ls -l /dev/ttySL0 lrwxrwxrwx 1 root root 10 Dec 30 14:26 /dev/ttySL0 -> /dev/pts/1 [pbhat@sidharth ~]$ ls -l /dev/pts/1 crw-rw---- 1 root uucp 136, 1 Dec 30 15:45 /dev/pts/1
why not on modem? Is it safe to add normal users to 'uucp' group? or change modem group to a new group like 'dialout' and make users its members ?
I can 'sudo wvdial' successfully.
Thanks,
Parameshwara Bhat
-- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
akonstam@trinity.edu wrote:
On Sat, Dec 31, 2005 at 06:25:40AM +0530, Parameshwara Bhat wrote:
Hello List,
I am updated to latest (3.5) KDE from kde-redhat repository.When I run kppp,(sudo /usr/sbin/kppp), set correct modem port and ISP account.It just can't dial.
When I checked in the configure dialogs,under 'modem commands',nothing is listed. Kppp has forgotten all the modem initialisation strings!
Now, I run it as user,again the same.No initialisation strings.I give the chosen modem a name,save it and go to create a new modem,all the initialisation strings are there.But I cannot run it as I have no access right to modem as a user.
Stop me if you know this. There are 2 kppp files on the machine. /usr/sbin/kppp is the actual program. /usr/bin/kppp is really a link to consolehelper and is set up for the user to run kppp. However, I have only had success setting /usr/sbin/kppp to SUID and running it as a normal user.
The symlink to consolehelper is Red Hat's way to wrap stuff that ordinarily requires root privilege (such shutdown and halt) and control their use with PAM.
This allows, for example, you to halt the system with the halt command if you're logged in from a virtual console, but not if you've connected using ssh. If PAM says you can do it, consolehelper execs the same-named program fron /sbin (and maybe from other sbin directories, I don't recall).
I think this is documented in the consolehelper package; if not, browse the EL docs on Red Hat's website.
Stop me if you know this. There are 2 kppp files on the machine. /usr/sbin/kppp is the actual program. /usr/bin/kppp is really a link to consolehelper and is set up for the user to run kppp. However, I have only had success setting /usr/sbin/kppp to SUID and running it as a normal user.
The symlink to consolehelper is Red Hat's way to wrap stuff that ordinarily requires root privilege (such shutdown and halt) and control their use with PAM.
This allows, for example, you to halt the system with the halt command if you're logged in from a virtual console, but not if you've connected using ssh. If PAM says you can do it, consolehelper execs the same-named program fron /sbin (and maybe from other sbin directories, I don't recall).
I think this is documented in the consolehelper package; if not, browse the EL docs on Red Hat's website.
I agree with the above explanation of console helper but in relation to kppp my experience that a SUID /user/sbin/kppp works better.
-
akonstam＠trinity.edu -
John Summerfield -
Parameshwara Bhat