On Thu, 2006-04-13 at 14:11 -0400, David Hollis wrote:
> On Thu, 2006-04-13 at 07:01 -0400, Jon Nettleton wrote:
>
> > 1) catch Network state changes, obviously through the NetworkManager.
> > Base different locations off of default route ip and hardware address,
> > if wireless maybe essid?
> > 2) Needs a privileged and unprivileged interface. Some apps like ntpd,
> > iptables, cups, network filesystems, general services, all need to be
> > setup by root. Others, gweather, default printer, network servers
> > (gnome-vfs), mail settings, screensaver timeout, are user specific.
> > 3) No reason to be a daemon running all the time. We have
> > NetworkManagerDispatcher already running, why not use that? This also
> > doesn't need to be super fast or small, allowing higher level languages
> > to be used.
>
> A similar app on the Windows side (for IBM systems anyway) would be IBM
> Access Connections. It's actually a pretty evil app, but it's
> intentions are pretty good. Based on your location profile, you can
> specify your default printer, drive mappings, whether or not to enable
> File & Print sharing, etc.
Being able to switch yum{, repo} configurations comes to mind as a
useful function along the same lines. I have local mirrors available on
some networks, not on others. These can be handled with dispatcher.d
scripts, but would a user helper be beneficial?
--
Paul W. Frields, RHCE http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
Fedora Documentation Project: http://fedora.redhat.com/projects/docs/
Attachment:
signature.asc
Description: This is a digitally signed message part
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
