Richard King wrote:
>
> But it occurs to me - how does chat know which port to address?? (cos' I
> think maybe it doesn't??) Does it simply use /dev/modem or what?
> Minicom works 100% - and even if I use it to initialise the modem, then
> exit minicom without resetting, chat still fails.
Strange question, are you attempting the connection as root or as a
user, possible that you may not have rw or x permissions for the various
files required to make the connection if you are running as a user.
Reguardless, make sure the /dev/modem is symb'd correctly to the
proper /dev/cuaX or /dev/ttyX then enter the following:
/usr/sbin/pppd connect '/usr/sbin/chat -v -f /etc/ppp/pppscript'
I found that when running the above as a user that chat would start,
then simply timeout because as a user you don't have read permissions
for the pppscript file which initializes the modem everytime chat is
called.
If you simply get a 'Permission denied' statement, then you don't have
execute access for the pppd. Other then that and depending on your
results and answers I can't think of anything else.
--
Ec|ipse on EFnet - [EMAIL PROTECTED] - http://www.primenet.com/~tomas
Ec|ipse@|Watcher| - http://pacific.undertow.net/~tomas/no-net.html
Slackware Linux v3.6 - Kernels 2.0.35/2.1.131
-
To get out of this list, please send email to [EMAIL PROTECTED] with
this text in its body: unsubscribe suse-linux-e
Check out the SuSE-FAQ at http://www.suse.com/Support/Doku/FAQ/ and the
archiv at http://www.suse.com/Mailinglists/suse-linux-e/index.html
