linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sean Reifschneider <jafo-hotplug@tummy.com>
To: linux-hotplug@vger.kernel.org
Subject: Patch to allow local net startup.
Date: Sun, 01 Aug 2004 20:23:49 +0000	[thread overview]
Message-ID: <20040801202008.GA7885@tummy.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 849 bytes --]

Attached is a patch which looks for "/etc/hotplug/net-local", and uses
that in preference to "ifup" or other distro-specific configs to bring
the interface up.  I added this to a local copy because it seems to be
the only way I can get my own script to run for bringing up a hotplug
wireless interface.  Unfortunately, just listing some iwconfig arguments
isn't really that useful for the mobile user, I have a script that
configures itself differently depending on where it detects I am.

Some sort of mechanism for allowing users to wedge into the
initialization is really needed.

Sean
-- 
 Resistance isn't futile.  It's voltage over amperage.
Sean Reifschneider, Member of Technical Staff <jafo@tummy.com>
tummy.com, ltd. - Linux Consulting since 1995.  Qmail, Python, SysAdmin
      Back off man. I'm a scientist.   http://HackingSociety.org/

[-- Attachment #2: hotplug-netlocal.patch --]
[-- Type: text/plain, Size: 493 bytes --]

--- admin/etc/hotplug/net.agent.old	2004-08-01 14:11:35.000000000 -0600
+++ admin/etc/hotplug/net.agent	2004-08-01 14:13:43.000000000 -0600
@@ -62,8 +62,12 @@
 		fi;
 	    fi
 
-	    # RedHat and similar
 	    export IN_HOTPLUG=1
+	    # user-configured startup
+	    if [ -x /etc/hotplug/net-local.agent ]; then
+                exec /etc/hotplug/net-local.agent
+
+	    # RedHat and similar
 	    if [ -x /sbin/ifup ]; then
 		debug_mesg invoke ifup $INTERFACE
 		exec /sbin/ifup $INTERFACE

                 reply	other threads:[~2004-08-01 20:23 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20040801202008.GA7885@tummy.com \
    --to=jafo-hotplug@tummy.com \
    --cc=linux-hotplug@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 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).