Re: Example of 'brilliant' apps?

[Bill Hacker <wbh@xxxxxxxxxxxxx>]

Erik Wikström wrote:
> "Bill Hacker" <wbh@xxxxxxxxxxxxx> wrote in message
> news:423c6f62$0$716$415eb37d@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>
>
> > Downside is that if you don't teach it not to talk to stangers, you'll
> > walk into
> > Starbucks for a coffee, pop open the lid, auto-connect to T-Mobile
> > and find some unsuspecting customer across the room has a Bluetooth
> > phone or PDA that's trying to sneak out for a little fun - and has noticed
> > your PowerBook advertising free love and internet connectivity - drive
> > sharing and chat, too if you haven't spanked it soundly.
> >
> > They really oughta teach these bot's more cautious ways before they
> > give 'em batteries.  Just 'coz you don't do x86 doesn't mean you can't get
> > ...taken advantage of ;-D
> >
> > Bill
>
>
> Well, I was hoping for something that would be able to run some scripts or
> such so that you configure your services etc. according to the network you
> are connected to, would be neat to dynamically change the firewall-rules so
> that when home for example you are more open and when in an "unknown" net
> you'd be as closed as could be.
>
> --
> Erik Wikström
Such settings are already in the Mac - should be adaptable to other *BSD's.

Ex: You start with 'Automatic', as described.  You can add multiple specific
'sets' of settings, and - lo and behold -they can have some/all of the
features of  'Automatic'.  Several of mine are identical execpt for 
selecting
specific (often off-continent) DNS for testng.

To do something similar in a *BSD, one could have 'set's of rc.conf, hosts,
and resolv.conf files and/or conditionals, and/or shell scripts that set new
over-rides and HUP stuff.

Not at all hard to implement.  Not even hard to do the probing.
IS hard to decide what to do, about it, when and where.

But that's where coding starts...  th 'what to od' more than the 'how'.


Bill



Bill