Followup:
Oh, it work, ok... until I rebooted. Then it didn't work for ordinary (non-super users) to #wvdial anymore.
Apparently, using udev and sysfs, etc., the devices are made on
boot. Funny, that I had to run MAKEDEV to make the higher
numbered nodes, like /dev/ttyS14, where my modem res
Ok: success! After changing the permissions a a BUNCH of files,
and ownerships, and even generating new groups (ppp), finally, when I
changed the ownership of /etc/wvdial to root:dialout, the setup works!
Isn't that always the way? When I finally have posted and given up, a new option occurs to
I've been plunking around with this. I tried what may be a brute
force method: change the permissions of /dev/ttyS14. But
/dev/ttyS14 is a link to /dev/tts/14. I now see that is a devfs
rendering? I thought I do not have support for devfs, and I am
trying to use something else.
Anyway, is it
John J. Foster wrote:
>On Sat, Nov 26, 2005 at 10:20:15PM -0600, Dale wrote:
>
>
>>Now wvdial, it dials out, then sits for a minute, then disconnects with
>>the error that my password is wrong, which is crap because it is
>>correct. I only got wvdial to work once on another rig. It has never
>
I haven't tried setuid for the wvdial binary. I have joined the
users to the groups "dialout" and "uucp". I have also changed the
owner of various binaries to include users, including "wvdial". I
followed someone's advice on the Inet and set pppd setuid for the group
"ppp" which I also joined al
On Sun, 27 Nov 2005 14:33:09 +
"b.n." <[EMAIL PROTECTED]> wrote:
> Alan E. Davis wrote:
> > I have tried alot of approaches. Wvdial is superior for detecting
> > hardware: it found my modem on ttyS14, where other approaches hadn't
> > found it.
> >
> > What I cannot seem to do is set up f
>
> Well, I use ppp and the comand pon and poff. It
> works pretty well.
> emerge ppp and then config with pppconfig. To
> connect, pon, to
> disconnect, poff. That would be as root, there
> should be a way to make
> users do it though. I'm not sure how.
$sudo /usr/sbin/pon(poff)
>
> Now
Alan E. Davis wrote:
I have tried alot of approaches. Wvdial is superior for detecting
hardware: it found my modem on ttyS14, where other approaches hadn't
found it.
What I cannot seem to do is set up for my family to dial in from their
accounts. I have tried changing permissions of various
On Sat, Nov 26, 2005 at 10:20:15PM -0600, Dale wrote:
>
> Now wvdial, it dials out, then sits for a minute, then disconnects with
> the error that my password is wrong, which is crap because it is
> correct. I only got wvdial to work once on another rig. It has never
> worked on this one though.
On Sat November 26 2005 9:15 pm, Alan E. Davis wrote:
> I have tried alot of approaches. Wvdial is superior for detecting
> hardware: it found my modem on ttyS14, where other approaches hadn't found
> it.
>
> What I cannot seem to do is set up for my family to dial in from their
> accounts. I hav
There are a couple of groups that you need to add your users to. -
"dialout" and "uucp".
Reading the message at the end of emerging wvdial tells you this. Also
reading the ebuild gives you the same information.
I am not criticising you, thiose messages flash by very quickly, and
reading the ebuil
Alan E. Davis wrote:
> I have tried changing permissions of various kinds, adding user
> to dialout, etc.
Add them to "tty" group ;)
--
Norberto Bensa
4544-9692
Ciudad de Buenos Aires, Argentina
--
gentoo-user@gentoo.org mailing list
Alan E. Davis wrote:
> I have tried alot of approaches. Wvdial is superior for detecting
> hardware: it found my modem on ttyS14, where other approaches hadn't
> found it.
>
> What I cannot seem to do is set up for my family to dial in from their
> accounts. I have tried changing permissions of
13 matches
Mail list logo
