Peter Buckingham wrote:
> The idea is this script would be run after the successful configuration
> of the interface.
There can be multiple interfaces in a system. So using the
term of NWAM, I guess what you want is to have the script
executed after NWAM picks the Environment suitable for the
network configuration. And Environment can be considered as
a set of network services to be enabled and some related info.
> The idea is that we have a hook that the user can create a script to do
> anything they want. It could modify gnome's gconf setup for the proxy,
> it could modify the system-wide profile to add proxy settings. It could
> even detect that I'm now on an external network and begin to configure
> punchin or the like too.
>
> The idea is that we give the users the ability to do things that they
> want rather than locking them into a standard way of doing things.
>
> If I can have a custom script that will execute on the network changes I
> can decide my comfort level of support, eg it's ok for me to hack the
> gconf files of user X because it's me, but if NWAM did this in a general
> way it would probably be a security hole/problem that we wouldn't want
> to provide.
What input does the script need? Or the script just got
executed after NWAM picks the Environment and the script will
try to find out everything it needs to know about?
I think it is reasonable to have this feature in NWAM. If
people see a problem, please comment.
--
K. Poon.
[EMAIL PROTECTED]
_______________________________________________
networking-discuss mailing list
[email protected]
