From: Deedra Waters <curi0315@tampabay.rr.com>
To: speakup@braille.uwo.ca
Subject: Re: Getting Dialup Working
Date: Mon, 1 Jul 2002 17:00:00 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.3.96.1020701165642.20416C-100000@deedra> (raw)
In-Reply-To: <Pine.LNX.4.44.0207011340410.401-100000@igueths>
I did get my networking fixed. I did end up using static ips for both eth1
and the laptop.
To be perfectly honest, the problem I had mor then anything, was hearing
five different things from five different people, and not knowing enough
about it to decide who to listen to and who not to. I'd read the manpages
and documentation, but didn't understand them, and couldn't figure out how
to do things.
I'm not critisizing anyone by any means, I'm just saying that it's hard to
follow advice when you're told different things.
I will say this though, thank you to the people who got me straightened
out.:)
On Mon, 1 Jul 2002, Igor Gueths wrote:
> Are we actually going to write a now what howto? I'd like to contribute if
> we did.
>
> Explorer has caused a general protection fault in module kernel32.dll. I'm sick of Winblows!
> On Mon, 1 Jul 2002, Janina Sajka wrote:
>
> > Ah, wonderful. Guess I might have read the wvdial man page!
> > <grin>
> >
> > I'm keeping this message for the next HOWTO. I'm inspired that we
> > need a "Now What" HOWTO.
> >
> > On Mon, 1 Jul 2002, Thomas Ward wrote:
> >
> > > Hi, some comments here. There is a much easier way to configure wvdial than
> > > Janina used.
> > >
> > > As root simply type:
> > >
> > > wvdialconf /etc/wvdial.conf
> > >
> > > wvdial in 99% of the time will find, configure your modem, and all you need
> > > do is add your phone number, user name, and password.
> > > If the probe fails then you will have to go with Janina's earlier
> > > instructions.
> > >
> > >
> > >
> > >
> > >
> > >
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > >
> >
> > --
> >
> > Janina Sajka, Director
> > Technology Research and Development
> > Governmental Relations Group
> > American Foundation for the Blind (AFB)
> >
> > Email: janina@afb.net Phone: (202) 408-8175
> >
> > Chair, Accessibility SIG
> > Open Electronic Book Forum (OEBF)
> > http://www.openebook.org
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E17Orea-0006A4-00@speech.braille.uwo.ca>
` Thomas Ward
` Janina Sajka
` Igor Gueths
` Janina Sajka
` Deedra Waters [this message]
` Deedra Waters
` better configuration Patrick Turnage
` Getting Dialup Working Dietmar Segbert
` Toby Fisher
` Octavian Rasnita
` Toby Fisher
[not found] <E17Pz98-0004kZ-00@speech.braille.uwo.ca>
` Thomas D. Ward
` Octavian Rasnita
[not found] <Pine.LNX.4.44.0206301433080.30672-100000@drizzle.com>
` Janina Sajka
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=Pine.LNX.3.96.1020701165642.20416C-100000@deedra \
--to=curi0315@tampabay.rr.com \
--cc=speakup@braille.uwo.ca \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).