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 resides.  (The modem is not at this place on one of the other systems I was playing around with---Knoppix, I think).  

I am now going to learn udev.  I want to anyway: I like the way Ubuntu jumps into action when a flash drive or a printer is plugged in, and so do my GNU/Linux doubting friends :-).

So far, it looks like rules for creating the device nodes include permissions components. 

I will get there eventually.  Does anyone know, right off hand, though, how to produce a rule to set up /dev/ttyS14 (/dev/tts/14 in the new nomenclature) with permissions to allow dialup by anyone in group dialout?  It works to just do the following after booting:
      # chmod o+rw /dev/tts
      # chmod 0+rw /dev/tts/14

Is this a security issue?

Thanks for the advices so far.

Alan Davis

On 11/28/05, Alan E. Davis <lngndvs@gmail.com> wrote:
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 me that works!

Thank you to everyone who made suggestions.

Alan Davis


On 11/28/05, Alan E. Davis < lngndvs@gmail.com> wrote:
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 possible my problems are related to this issue?

I see that the "Cannot open /dev/ttyS14: device or resource busy" message is a common one.  And there are almost as many proposed solutions as there are instances.  There surely would be an easy way to do such a simple thing?   Nothing works for me.

Alan Davis



On 11/28/05, Dale <dalek@exceedtech.net > wrote:
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
>>worked on this one though.  Anybody have a clue on that one?  I just
>>like to have options in case it pours instead of just a little shower.
>>
>>
>
>Hi Dale - I had the same problem until I set
>
>Stupid Mode=yes in /etc/wvdial.conf. All was fine then.
>
>John
>
>
Thanks for that tip.  I'll try that.  I like to have as many back-ups as
I can get.  If it were not for bad luck, I would have no luck at all.
Well, there is the exception of my girlfriend.  She is the best thing,
person, to happen yet.

Dale
:-)

--
To err is human, I'm most certainly human.



--
gentoo-user@gentoo.org mailing list