On Mon, Aug 27, 2007 at 12:56:33PM -0600, Alberto Treviño wrote: > On Monday 27 August 2007 12:47:01 pm Andrew McNabb wrote: > > You may disagree with me, but I think that what you recommend should > > be the second item of business. > > That's fine. As long as it comes soon into the project. You don't want > to run around aimlessly for too long.
I agree completely. By the way, I think that once we get started, people will start coming up with some really clever ideas. Some of the things that we have tossed around in some preliminary brainstorming are: - On boot, the system automatically downloads configuration so that no state needs to be stored locally - Look for configuration on a USB thumb drive sitting in the machine. - Automatically detect which network interface is internal and which is external. - Host a configuration page that's accessible only on the internal interface. - Have a community page at BYU that lets you get blacklists/whitelists from other users. - Look for a wireless USB or PCI card and go into master mode if possible (i.e., the computer becomes a wireless access point). - See if it's possible to get Dansguardian to work on a Linksys wireless router. I'm sure we could come up with dozens of additional ideas. -- Andrew McNabb http://www.mcnabbs.org/andrew/ PGP Fingerprint: 8A17 B57C 6879 1863 DE55 8012 AB4D 6098 8826 6868
pgpg0pShF1y06.pgp
Description: PGP signature
-------------------- BYU Unix Users Group http://uug.byu.edu/ The opinions expressed in this message are the responsibility of their author. They are not endorsed by BYU, the BYU CS Department or BYU-UUG. ___________________________________________________________________ List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
