From: "Alan E. Davis" <lngndvs@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] wvdial: dialup for users
Date: Mon, 28 Nov 2005 23:36:30 +1000 [thread overview]
Message-ID: <7bef1f890511280536h2fe0866dva87433ffde81e17c@mail.gmail.com> (raw)
In-Reply-To: <7bef1f890511280530j5df25b7r722898f3ad725b84@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2248 bytes --]
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
> >
> >
>
[-- Attachment #2: Type: text/html, Size: 3236 bytes --]
next prev parent reply other threads:[~2005-11-28 13:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-27 2:15 [gentoo-user] wvdial: dialup for users Alan E. Davis
2005-11-27 4:20 ` Dale
2005-11-27 13:19 ` John J. Foster
2005-11-28 4:24 ` Dale
2005-11-28 13:30 ` Alan E. Davis
2005-11-28 13:36 ` Alan E. Davis [this message]
2005-11-29 12:41 ` Alan E. Davis
2005-11-27 17:05 ` maxim wexler
2005-11-27 6:20 ` Nick Rout
2005-11-27 6:25 ` Norberto Bensa
2005-11-27 6:42 ` Robert Crawford
2005-11-27 14:33 ` b.n.
2005-11-27 19:09 ` Nick Rout
2005-11-27 21:21 ` Alan E. Davis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7bef1f890511280536h2fe0866dva87433ffde81e17c@mail.gmail.com \
--to=lngndvs@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox