From: forsyth@caldo.demon.co.uk
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ppp and other
Date: Mon, 15 Jul 2002 11:11:04 +0100 [thread overview]
Message-ID: <e0d0cbb4d7a0c6c10135edca3f3b61b1@caldo.demon.co.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 193 bytes --]
why not put the parametrised ppp command line in a file and run that?
much easier than having yet another configuration file.
don't forget to make it mode 700 if it has got passwords in it.
[-- Attachment #2: Type: message/rfc822, Size: 2153 bytes --]
From: Ben <cellctl@lycos.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ppp and other
Date: Mon, 15 Jul 2002 09:32:09 GMT
Message-ID: <dd8c4466.0207141725.1068e27f@posting.google.com>
I can tell that the Bell-Labs guys don't use PPP dialup much. Not a
very refined interface for PPP...(no offense intended) Shouldn't it
at least use a configuration file to specify phone number, username,
password, baud rate, etc. then one could simply use something like:
ip/ppp <configfile> where a seperate config file could be used per
host? (Similar to BSD's ppp command) It's much easier that way than
specifying that many command switches!
next reply other threads:[~2002-07-15 10:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-15 10:11 forsyth [this message]
2002-07-15 10:11 ` andrey mirtchovski
-- strict thread matches above, loose matches on Subject: below --
2002-07-30 11:34 Russ Cox
2002-07-15 23:24 Andrey S. Kukhar
2002-07-31 9:35 ` [9fans] " Ben
2002-08-01 19:56 ` Jack Johnson
2002-08-05 23:39 ` plan9
2002-07-15 9:55 Fco.J.Ballesteros
2002-07-15 9:57 ` Axel Belinfante
2002-07-15 0:30 Andrey S. Kukhar
2002-07-14 17:38 presotto
2002-07-14 17:54 ` Scott Schwartz
2002-07-15 9:32 ` Ben
2002-07-15 14:08 ` Michael H.Collins
2002-07-14 15:20 presotto
2002-07-13 8:45 [9fans] POV-Ray andrey mirtchovski
2002-07-14 1:52 ` [9fans] ppp and other Andrey S. Kukhar
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=e0d0cbb4d7a0c6c10135edca3f3b61b1@caldo.demon.co.uk \
--to=forsyth@caldo.demon.co.uk \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).