All of lore.kernel.org
 help / color / mirror / Atom feed
From: bfc <chappaquasuite@yahoo.com>
To: linux-ppp@vger.kernel.org
Subject: Re: if-up et al script relocation
Date: Thu, 14 Feb 2008 02:16:53 +0000	[thread overview]
Message-ID: <15472625.post@talk.nabble.com> (raw)
In-Reply-To: <15468731.post@talk.nabble.com>



Thanks everyone.

We've been using a custom build for some time, and wanted to get away from
that.  Inertia being what it is, we let an
old version linger for too long (2.4.1?) and now need to move to 2.4.4 for
various fixes and its structureed differently enough
to cause a bit of real work.

I meant ip-up ip-down... not if-up if-down, DUH.  (I've made this mistake
repeatedly.)

The plugin is an interesting thought, though perhaps beyond the current
scope/schedule.  At least that would let us
continue moving forward as new pppd versions came out (we just follow RHEL
versions).

So I guess it comes down to customizing any existing ip-up/ip-down/auth-up
scripts (based on the tty), but I do like the thought of combining all of
our logic into one script.  That would reduce the clutter, and could look
something like a service script.
It can be a switch on the action, doing our little things based on the
arguments we need.

Thanks again for your responses!
-- 
View this message in context: http://www.nabble.com/if-up-et-al-script-relocation-tp15468731p15472625.html
Sent from the linux-ppp mailing list archive at Nabble.com.


      parent reply	other threads:[~2008-02-14  2:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-13 21:46 if-up et al script relocation bfc
2008-02-13 22:04 ` Marco d'Itri
2008-02-13 22:19 ` Eugene Paskevich
2008-02-13 22:20 ` James Cameron
2008-02-14  2:16 ` bfc [this message]

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=15472625.post@talk.nabble.com \
    --to=chappaquasuite@yahoo.com \
    --cc=linux-ppp@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.