<?xml version="1.0"?>
<?xml-stylesheet type="text/css" href="http://72.14.177.54/skins/common/feed.css?207"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
	<channel>
		<title>Sfvlug - User contributions [en]</title>
		<link>http://72.14.177.54/SFVLUG/Special:Contributions/Koopa</link>
		<description>From Sfvlug</description>
		<language>en</language>
		<generator>MediaWiki 1.15.1</generator>
		<lastBuildDate>Tue, 16 Jun 2026 20:48:14 GMT</lastBuildDate>
		<item>
			<title>Pending</title>
			<link>http://72.14.177.54/SFVLUG/Pending</link>
			<description>&lt;p&gt;Koopa:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</description>
			<pubDate>Fri, 15 Dec 2006 01:08:31 GMT</pubDate>			<dc:creator>Koopa</dc:creator>			<comments>http://72.14.177.54/SFVLUG/Talk:Pending</comments>		</item>
		<item>
			<title>Pending</title>
			<link>http://72.14.177.54/SFVLUG/Pending</link>
			<description>&lt;p&gt;Koopa:&amp;#32;/* Newbie Command line Essentials (Learn these now!) */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;''Under Construction!'' (recategorise, review, augment, and add descriptions after more sleep)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Useful Info (Optional but worth learning as you go!)==&lt;br /&gt;
&lt;br /&gt;
Note: These your should pursue in your own time using the commands listed above for additional information!&lt;br /&gt;
&lt;br /&gt;
 General: alias, free, jobs, fg, dmesg, uname, xargs&lt;br /&gt;
 Pattern Matching: grep, rgrep, egrep, fgrep&lt;br /&gt;
 Process: top, ps, pgrep, nice, renice, kill, pkill, killall&lt;br /&gt;
 Network: route, traceroute, arp, netstat, ping&lt;br /&gt;
 File and Filesystem: cp, mv, rm, ls, cd, chmod, chown, cat, du, df, lsof, touch&lt;br /&gt;
 Conveniences: ssh-agent, keychains, screen&lt;br /&gt;
 Debian Package Manager: apt-get, dpkg, apt-cache, apt-file (Note: Debian based distribution specific)&lt;br /&gt;
 Files and File Locations: /etc/passwd, /etc/hosts, /etc/hosts.allow, /etc/hosts.deny, /etc/hostname, /etc/resolv.conf, /etc/groups,&lt;br /&gt;
                           /etc/fstab, /etc/modules, ~/.bashrc, ~/.bash_profile, ~/.bash_aliases&lt;/div&gt;</description>
			<pubDate>Fri, 15 Dec 2006 01:08:10 GMT</pubDate>			<dc:creator>Koopa</dc:creator>			<comments>http://72.14.177.54/SFVLUG/Talk:Pending</comments>		</item>
		<item>
			<title>Newbie Command Line Essentials</title>
			<link>http://72.14.177.54/SFVLUG/Newbie_Command_Line_Essentials</link>
			<description>&lt;p&gt;Koopa:&amp;#32;/* Newbie Command line Essentials (Learn these now!) */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If you don't know your commandline very well at least know the tools that you have at your disposal to find the information and operate most efficiently. This section will contain only the entries that will enable you to maximize your productivity at the command line. &lt;br /&gt;
&lt;br /&gt;
Search and documentation tools are some of the most important tools you can learn on your box heres a brief list of a few of the most popular, all of which can be accessed through your terminal (xterm, rxvt, etc...) or console (&amp;lt;ctrl&amp;gt;&amp;lt;alt&amp;gt;F1...F6). Note: Commands in no particular order examples not applicable in all distributions or setups.&lt;br /&gt;
&lt;br /&gt;
'''Info'''&lt;br /&gt;
&lt;br /&gt;
 man - an interface to the on-line reference manuals (ex: man hier)&lt;br /&gt;
 find - search the manual page names and descriptions (ex: find ~ -name '*.mp3')&lt;br /&gt;
 locate - security Enhanced version of the GNU Locate (ex: locate hosts)&lt;br /&gt;
 updatedb - update the slocate database (ex: updatedb&amp;amp;)&lt;br /&gt;
 which - locate a command (ex: which ifconfig)&lt;br /&gt;
 whereis - locate the binary, source, and manual page files for a command (ex. whereis ifconfig)&lt;br /&gt;
 hier - description of the file system hierarchy (ex. man hier)&lt;br /&gt;
 apropos - search the manual page names and descriptions (ex. apropos &amp;lt;keyword&amp;gt;)&lt;br /&gt;
 less - page through text one screenful at a time allowing for forward and backward movement in the file (ex. less&lt;br /&gt;
 /usr/share/doc/debian/debian-manifesto)&lt;br /&gt;
 su - change user ID or become super-user (ex. su - &amp;lt;passwd&amp;gt;)&lt;br /&gt;
 sudo - execute a command as another user (ex. sudo /etc/init.d/networking)&lt;br /&gt;
 history - display the list of commands previously typed (ex. history)&lt;br /&gt;
&lt;br /&gt;
'''Keystrokes'''&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;ctrl&amp;gt;r - reverse keyword search of the command history (ex. &amp;lt;ctrl&amp;gt;r&amp;lt;keyword&amp;gt;&lt;br /&gt;
 / - search forward for occurance of keyword in a manpage, many editors and pagers (ex. /&amp;lt;keyword&amp;gt;)&lt;br /&gt;
 ? - search backward for occurance of keyword in a manpage, many editors and pagers (ex. ?&amp;lt;keyword&amp;gt;)&lt;br /&gt;
 n - continue to the next occurance of the keyword searches listed above (ex. n)&lt;br /&gt;
&lt;br /&gt;
'''Network'''&lt;br /&gt;
 ifconfig - configure a network interface (ex. ifconfig eth0 192.168.0.2)&lt;br /&gt;
 route - show / manipulate the IP routing table (ex. route add -net default gw 192.168.0.1)&lt;br /&gt;
 iwconfig - configure a wireless network interface (ex. iwconfig eth2 essid GaylesPerk channel 11 mode auto)&lt;br /&gt;
 iwlist - get more detailed wireless information from a wireless interface (ex. iwlist eth2 scan)&lt;br /&gt;
 ifup - bring a network interface up (ex. ifup eth0)&lt;br /&gt;
 ifdown - take a network interface down (ex. ifdown eth0)&lt;br /&gt;
&lt;br /&gt;
'''Paths'''&lt;br /&gt;
&lt;br /&gt;
 /usr/share/doc, /usr/local/doc - documentation paths&lt;br /&gt;
 /var/log - path of all your log files&lt;br /&gt;
 /etc - most of your config files&lt;br /&gt;
 /etc/init.d - system service control scripts&lt;br /&gt;
 ~ - an abbreviation of your home directory (long form: /home/user)&lt;br /&gt;
 / - root path, the base/parent path of all paths&lt;br /&gt;
 . - current working directory&lt;br /&gt;
 ./ - path based off of the current working directory&lt;br /&gt;
 ../ - parent path &lt;br /&gt;
 &lt;br /&gt;
'''Special Characters'''&lt;br /&gt;
&lt;br /&gt;
 Note: not all essential but all worth learning early&lt;br /&gt;
 | - pipeline command, the standard output of one command is connected to the standard input of another command&lt;br /&gt;
     (ie take the output of one  command and send it to another)&lt;br /&gt;
 \\ - preserves the literal value of the command that follows, except newline&lt;br /&gt;
     (takes any special characters and turns them into something akin to text characters)&lt;br /&gt;
 &amp;amp; - if a command is terminated by the control operator &amp;amp;, the shell executes the command in the background in a subshell &lt;br /&gt;
 &amp;amp;&amp;amp; and || - the control operators &amp;amp;&amp;amp; and ││ denote AND lists and OR lists, respectively. An AND list has the form:&lt;br /&gt;
     command1 &amp;amp;&amp;amp; command2 (Note: command2  is  executed if, and only if, command1 returns an exit status of zero)&lt;br /&gt;
 ; - commands separated by a ; are executed sequentially&lt;br /&gt;
&lt;br /&gt;
==Useful Info (Optional but worth learning as you go!)==&lt;br /&gt;
&lt;br /&gt;
Note: These your should pursue in your own time using the commands listed above for additional information!&lt;br /&gt;
&lt;br /&gt;
 General: alias, free, jobs, fg, dmesg, uname, xargs&lt;br /&gt;
 Pattern Matching: grep, rgrep, egrep, fgrep&lt;br /&gt;
 Process: top, ps, pgrep, nice, renice, kill, pkill, killall&lt;br /&gt;
 Network: route, traceroute, arp, netstat, ping&lt;br /&gt;
 File and Filesystem: cp, mv, rm, ls, cd, chmod, chown, cat, du, df, lsof, touch&lt;br /&gt;
 Conveniences: ssh-agent, keychains, screen&lt;br /&gt;
 Debian Package Manager: apt-get, dpkg, apt-cache, apt-file (Note: Debian based distribution specific)&lt;br /&gt;
 Files and File Locations: /etc/passwd, /etc/hosts, /etc/hosts.allow, /etc/hosts.deny, /etc/hostname, /etc/resolv.conf, /etc/groups,&lt;br /&gt;
                           /etc/fstab, /etc/modules, ~/.bashrc, ~/.bash_profile, ~/.bash_aliases&lt;/div&gt;</description>
			<pubDate>Fri, 15 Dec 2006 01:06:26 GMT</pubDate>			<dc:creator>Koopa</dc:creator>			<comments>http://72.14.177.54/SFVLUG/Talk:Newbie_Command_Line_Essentials</comments>		</item>
		<item>
			<title>Newbie Command Line Essentials</title>
			<link>http://72.14.177.54/SFVLUG/Newbie_Command_Line_Essentials</link>
			<description>&lt;p&gt;Koopa:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Newbie Command line Essentials (Learn these now!)==&lt;br /&gt;
&lt;br /&gt;
If you don't know your commandline very well at least know the tools that you have at your disposal to find the information and operate most efficiently. This section will contain only the entries that will enable you to maximize your productivity at the command line. &lt;br /&gt;
&lt;br /&gt;
Search and documentation tools are some of the most important tools you can learn on your box heres a brief list of a few of the most popular, all of which can be accessed through your terminal (xterm, rxvt, etc...) or console (&amp;lt;ctrl&amp;gt;&amp;lt;alt&amp;gt;F1...F6). Note: Commands in no particular order examples not applicable in all distributions or setups.&lt;br /&gt;
&lt;br /&gt;
'''Info'''&lt;br /&gt;
&lt;br /&gt;
 man - an interface to the on-line reference manuals (ex: man hier)&lt;br /&gt;
 find - search the manual page names and descriptions (ex: find ~ -name '*.mp3')&lt;br /&gt;
 locate - security Enhanced version of the GNU Locate (ex: locate hosts)&lt;br /&gt;
 updatedb - update the slocate database (ex: updatedb&amp;amp;)&lt;br /&gt;
 which - locate a command (ex: which ifconfig)&lt;br /&gt;
 whereis - locate the binary, source, and manual page files for a command (ex. whereis ifconfig)&lt;br /&gt;
 hier - description of the file system hierarchy (ex. man hier)&lt;br /&gt;
 apropos - search the manual page names and descriptions (ex. apropos &amp;lt;keyword&amp;gt;)&lt;br /&gt;
 less - page through text one screenful at a time allowing for forward and backward movement in the file (ex. less&lt;br /&gt;
 /usr/share/doc/debian/debian-manifesto)&lt;br /&gt;
 su - change user ID or become super-user (ex. su - &amp;lt;passwd&amp;gt;)&lt;br /&gt;
 sudo - execute a command as another user (ex. sudo /etc/init.d/networking)&lt;br /&gt;
 history - display the list of commands previously typed (ex. history)&lt;br /&gt;
&lt;br /&gt;
'''Keystrokes'''&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;ctrl&amp;gt;r - reverse keyword search of the command history (ex. &amp;lt;ctrl&amp;gt;r&amp;lt;keyword&amp;gt;&lt;br /&gt;
 / - search forward for occurance of keyword in a manpage, many editors and pagers (ex. /&amp;lt;keyword&amp;gt;)&lt;br /&gt;
 ? - search backward for occurance of keyword in a manpage, many editors and pagers (ex. ?&amp;lt;keyword&amp;gt;)&lt;br /&gt;
 n - continue to the next occurance of the keyword searches listed above (ex. n)&lt;br /&gt;
&lt;br /&gt;
'''Network'''&lt;br /&gt;
 ifconfig - configure a network interface (ex. ifconfig eth0 192.168.0.2)&lt;br /&gt;
 route - show / manipulate the IP routing table (ex. route add -net default gw 192.168.0.1)&lt;br /&gt;
 iwconfig - configure a wireless network interface (ex. iwconfig eth2 essid GaylesPerk channel 11 mode auto)&lt;br /&gt;
 iwlist - get more detailed wireless information from a wireless interface (ex. iwlist eth2 scan)&lt;br /&gt;
 ifup - bring a network interface up (ex. ifup eth0)&lt;br /&gt;
 ifdown - take a network interface down (ex. ifdown eth0)&lt;br /&gt;
&lt;br /&gt;
'''Paths'''&lt;br /&gt;
&lt;br /&gt;
 /usr/share/doc, /usr/local/doc - documentation paths&lt;br /&gt;
 /var/log - path of all your log files&lt;br /&gt;
 /etc - most of your config files&lt;br /&gt;
 /etc/init.d - system service control scripts&lt;br /&gt;
 ~ - an abbreviation of your home directory (long form: /home/user)&lt;br /&gt;
 / - root path, the base/parent path of all paths&lt;br /&gt;
 . - current working directory&lt;br /&gt;
 ./ - path based off of the current working directory&lt;br /&gt;
 ../ - parent path &lt;br /&gt;
 &lt;br /&gt;
'''Special Characters'''&lt;br /&gt;
&lt;br /&gt;
 Note: not all essential but all worth learning early&lt;br /&gt;
 | - pipeline command, the standard output of one command is connected to the standard input of another command&lt;br /&gt;
     (ie take the output of one  command and send it to another)&lt;br /&gt;
 \\ - preserves the literal value of the command that follows, except newline&lt;br /&gt;
     (takes any special characters and turns them into something akin to text characters)&lt;br /&gt;
 &amp;amp; - if a command is terminated by the control operator &amp;amp;, the shell executes the command in the background in a subshell &lt;br /&gt;
 &amp;amp;&amp;amp; and || - the control operators &amp;amp;&amp;amp; and ││ denote AND lists and OR lists, respectively. An AND list has the form:&lt;br /&gt;
     command1 &amp;amp;&amp;amp; command2 (Note: command2  is  executed if, and only if, command1 returns an exit status of zero)&lt;br /&gt;
 ; - commands separated by a ; are executed sequentially&lt;br /&gt;
&lt;br /&gt;
==Useful Info (Optional but worth learning as you go!)==&lt;br /&gt;
&lt;br /&gt;
Note: These your should pursue in your own time using the commands listed above for additional information!&lt;br /&gt;
&lt;br /&gt;
 General: alias, free, jobs, fg, dmesg, uname, xargs&lt;br /&gt;
 Pattern Matching: grep, rgrep, egrep, fgrep&lt;br /&gt;
 Process: top, ps, pgrep, nice, renice, kill, pkill, killall&lt;br /&gt;
 Network: route, traceroute, arp, netstat, ping&lt;br /&gt;
 File and Filesystem: cp, mv, rm, ls, cd, chmod, chown, cat, du, df, lsof, touch&lt;br /&gt;
 Conveniences: ssh-agent, keychains, screen&lt;br /&gt;
 Debian Package Manager: apt-get, dpkg, apt-cache, apt-file (Note: Debian based distribution specific)&lt;br /&gt;
 Files and File Locations: /etc/passwd, /etc/hosts, /etc/hosts.allow, /etc/hosts.deny, /etc/hostname, /etc/resolv.conf, /etc/groups,&lt;br /&gt;
                           /etc/fstab, /etc/modules, ~/.bashrc, ~/.bash_profile, ~/.bash_aliases&lt;/div&gt;</description>
			<pubDate>Fri, 15 Dec 2006 01:04:17 GMT</pubDate>			<dc:creator>Koopa</dc:creator>			<comments>http://72.14.177.54/SFVLUG/Talk:Newbie_Command_Line_Essentials</comments>		</item>
		<item>
			<title>Newbie Resources</title>
			<link>http://72.14.177.54/SFVLUG/Newbie_Resources</link>
			<description>&lt;p&gt;Koopa:&amp;#32;/* Newbie Resources */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Newbie Resources==&lt;br /&gt;
&lt;br /&gt;
Here are some links that may be of particular interest to those who are new to Linux and the Open Source community and want to learn more.&lt;br /&gt;
&lt;br /&gt;
Before we get too far, the first thing to learn is that Google is indeed your friend. Here is a link to Google's special Linux search:&lt;br /&gt;
http://www.google.com/linux Google the Linux way. This should be your primary general resource, that is why it is placed here at the top of this list.&lt;br /&gt;
&lt;br /&gt;
Before you start bothering your friends or strangers the first thing to learn is how to ask questions that will return useful information and also won't make people upset. You don't want to alienate the people best able to answer questions with answers not found anywhere in print. This guide should be viewed before posting questions to forums, newsgroups, mailing lists, etc. It is appropriate reading for computer users of all skill levels. http://www.catb.org/~esr/faqs/smart-questions.html The author, [http://www.catb.org/~esr/ Eric S. Raymond] also has some other FAQs and HOWTOs at http://www.catb.org/~esr/faqs/ his emphasis in on bringing people to a high technical level and may contain information specific to IT professionals and people that want to become IT professionals.&lt;br /&gt;
&lt;br /&gt;
If you haven't yet installed Linux or are looking to change to a different flavor of Linux this site has good up to date information on what is available. http://distrowatch.com/ Another great download resource is http://www.ibiblio.org/pub/linux/ with much Linux software available for download from their servers. You can also find documentation at http://tldp.org/ at a different URL but same folks. They are a collaboration of the center for the public domain and [http://www.unc.edu/ unc-ch] with many free and open resources besides software. http://www.ibiblio.org/&lt;br /&gt;
&lt;br /&gt;
A good set of online Linux courses can be found over at [http://www.linux.org Linux.org] That's a great jumping off site for Linux users of all levels. It is where I (Charles Wyble) spent the majority of my online research time in the first year of using Linux.&lt;br /&gt;
&lt;br /&gt;
* [http://www.linux.org/lessons/beginner/index.html Beginner Course]&lt;br /&gt;
* [http://www.linux.org/lessons/interm/index.html Intermediate Course]&lt;br /&gt;
* [http://www.linux.org/lessons/advanced/index.html Advanced Course]&lt;br /&gt;
&lt;br /&gt;
Local Tutorials:&lt;br /&gt;
===[[Newbie Command Line Essentials]]===&lt;br /&gt;
&lt;br /&gt;
==Software Resources==&lt;br /&gt;
So if your new to Linux you probably want an idea of what software you can use with it. Now you can't just go down to your local computer store and buy software for Linux. However you can find software on the internet. The two most popluar sites for finding/downloading software are:&lt;br /&gt;
&lt;br /&gt;
*[http://http://freshmeat.net/ Freshmeat.net] A site that tracks releases of several thousand packages. A great site to simply browse and see the wide variety of software available. &lt;br /&gt;
&lt;br /&gt;
*[http://sourceforge.net Source Forge (also known as SF)] This site is used to host free/open source software. It is hands down the most popular hosting site out there. I (Charles) host multiple open source projects on the site. &lt;br /&gt;
&lt;br /&gt;
The third way to find software is the package management system in your distrubtution. What I like to do when searching for software is to go on Freshmeat/SF and do a keyword search. I then sort on various criteria (popularity/last update etc). I then open up the websites associated with the software in various tabs. Once I have selected some canidates I install them via my package manager. I use [http://www.debian.org Debian] based distrubutions which contain some 15,000 software packages for easy installation. Others in the LUG use [http://fedora.redhat.com/ Fedora] It all comes down to a matter of taste :)&lt;/div&gt;</description>
			<pubDate>Fri, 15 Dec 2006 01:03:17 GMT</pubDate>			<dc:creator>Koopa</dc:creator>			<comments>http://72.14.177.54/SFVLUG/Talk:Newbie_Resources</comments>		</item>
		<item>
			<title>SCALE</title>
			<link>http://72.14.177.54/SFVLUG/SCALE</link>
			<description>&lt;p&gt;Koopa:&amp;#32;/* Meeting Approach */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Alternatives ==&lt;br /&gt;
&lt;br /&gt;
Voice Synthesis Possibilities:&lt;br /&gt;
&lt;br /&gt;
 log watchers&lt;br /&gt;
 service checkers&lt;br /&gt;
 status checkers&lt;br /&gt;
 state checkers&lt;br /&gt;
 harverster readers&lt;br /&gt;
 ebook readers&lt;br /&gt;
 documentation readers&lt;br /&gt;
 security monitors&lt;br /&gt;
 etc...&lt;br /&gt;
&lt;br /&gt;
Voice Recognition Possibilities:&lt;br /&gt;
&lt;br /&gt;
 Pursue a different voice recognition engine&lt;br /&gt;
 Pursue a different voice recognition version&lt;br /&gt;
 Contact CMU to determine sphinx2 status&lt;br /&gt;
 Contact CMU to determine possible/best alternative&lt;br /&gt;
&lt;br /&gt;
===Comment===&lt;br /&gt;
These are good ideas no matter the result of any attempt to improve on Sphinx2. --[[User:Miasma|Miasma]] 19:42, 24 November 2006 (EST)&lt;br /&gt;
&lt;br /&gt;
Non Voice Possibilities:&lt;br /&gt;
&lt;br /&gt;
 Script Automation&lt;br /&gt;
 Bluetooth Presentation/Automation&lt;br /&gt;
 Legalish Wifi Related Items&lt;br /&gt;
&lt;br /&gt;
== SCALE Project Meeting Approach ==&lt;br /&gt;
&lt;br /&gt;
1. Come to table with discussed project possibilities and any backround/code thats available.&lt;br /&gt;
&lt;br /&gt;
2. Set precedent for the meeting stating it won't be a social meeting and socializers will be asked to leave.&lt;br /&gt;
&lt;br /&gt;
3. Field the groups capabilities&lt;br /&gt;
 interests&lt;br /&gt;
 coding level&lt;br /&gt;
 languages&lt;br /&gt;
 topic experience level&lt;br /&gt;
 no of weekly hours they can devote&lt;br /&gt;
 contact information (preferably telephone numbers in an effort to establish perceived accountability and show we're&lt;br /&gt;
                      serious about time based progress)&lt;br /&gt;
4. Discuss potential project viability and fallback given the limited time alloted (perhaps consider working 2 projects at once).&lt;br /&gt;
&lt;br /&gt;
5. Open floor to alternative projects not discussed in case the group feels theres something with more potential.&lt;br /&gt;
&lt;br /&gt;
6. Decide which project is most suitable based on the groups skills, desires, and most importantly donated time available.&lt;br /&gt;
&lt;br /&gt;
7. Possibly have a mini intro to next meeting to try to bring some people up to speed on a given language&lt;br /&gt;
&lt;br /&gt;
8. Write pseudocode to determine what code is needed. Assign Classes/Methods/Functions to groups members based on&lt;br /&gt;
the pseudocode spec (ie we need these classes and these methods/functions which takes this as input and returns &lt;br /&gt;
output in this form). &lt;br /&gt;
&lt;br /&gt;
9. Create meeting outline before meeting stating the amount of time you'd like to spend discussing each item (adhereing to the &lt;br /&gt;
alloted time on the more irrelevant issues that might sidetrack discussion).&lt;br /&gt;
&lt;br /&gt;
10. Setup some mechanism of peer review (easiest method would be to assign any one part of the project to multiple people&lt;br /&gt;
hopefully we'll see results from at least one of them).&lt;br /&gt;
&lt;br /&gt;
11. Have definate plan and timetable for all actions when leaving the meeting, make sure people understand their task, what it entails,&lt;br /&gt;
the time it might take, and its due date. Also discuss alternatives to critical action items. &lt;br /&gt;
&lt;br /&gt;
12. Set precedent for problem solving. If you can't accomplish this task, what alerternatives can YOU as part of the group recommend&lt;br /&gt;
or persue to achieve this goal by the deadline.&lt;br /&gt;
&lt;br /&gt;
13. Communication! Point to sfvlug wiki, request that people spend 2 min daily checking out the SCALE projects state.&lt;br /&gt;
&lt;br /&gt;
14. Write everything down!&lt;br /&gt;
&lt;br /&gt;
15. Hand people a physical piece of paper with their task written on it. They won't forget and there won't be question as to what their&lt;br /&gt;
task was. Record the task in the project ledger.&lt;br /&gt;
&lt;br /&gt;
16. Post meeting notes (minus contact information that can't be made public) and whose in charge of which task or tasks to enable perfect&lt;br /&gt;
information and dialoging.&lt;br /&gt;
&lt;br /&gt;
17. Set a precedent to try to accomplish your assigned task as quickly as possible to enable task reassignment in the event they can&lt;br /&gt;
no longer accomplish their task (this might give people too much of an out and they may take the task alot less seriously if this is &lt;br /&gt;
even discussed, possibly only state to accomplish your task well before the deadline).&lt;br /&gt;
&lt;br /&gt;
18. Socialization can occur before or after the meeting!&lt;br /&gt;
&lt;br /&gt;
===Comment===&lt;br /&gt;
My assumption is that all this would be accomplished in a meeting proposed in the following section. We should probably bring this up at the next regular meeting to see how many would be willing and able to spend some time on this project. --[[User:Miasma|Miasma]] 19:47, 24 November 2006 (EST)&lt;br /&gt;
&lt;br /&gt;
== Timetable ==&lt;br /&gt;
&lt;br /&gt;
Max 7 weeks losing thansgiving and xmas/newyears weeks to relatives and responsibilities and the fact that the SCALE&lt;br /&gt;
meeting hasn't even been announced. &lt;br /&gt;
&lt;br /&gt;
== Action Items ==&lt;br /&gt;
&lt;br /&gt;
Have a SCALE related meeting ASAP&lt;br /&gt;
Bring project options to the table at the meeting annoucement in hopes to limit the groups discussion in a nonstructured meeting environment.&lt;br /&gt;
&lt;br /&gt;
===About This Document===&lt;br /&gt;
&lt;br /&gt;
This is all off the top of the head atm if its severity or content is wrong tweak it. I'm tired of typing this stuff so hopefully &lt;br /&gt;
I'll get back to this later (or someone else will).&lt;/div&gt;</description>
			<pubDate>Wed, 13 Dec 2006 10:38:35 GMT</pubDate>			<dc:creator>Koopa</dc:creator>			<comments>http://72.14.177.54/SFVLUG/Talk:SCALE</comments>		</item>
		<item>
			<title>SCALE</title>
			<link>http://72.14.177.54/SFVLUG/SCALE</link>
			<description>&lt;p&gt;Koopa:&amp;#32;/* Alternatives */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Alternatives ==&lt;br /&gt;
&lt;br /&gt;
Voice Synthesis Possibilities:&lt;br /&gt;
&lt;br /&gt;
 log watchers&lt;br /&gt;
 service checkers&lt;br /&gt;
 status checkers&lt;br /&gt;
 state checkers&lt;br /&gt;
 harverster readers&lt;br /&gt;
 ebook readers&lt;br /&gt;
 documentation readers&lt;br /&gt;
 security monitors&lt;br /&gt;
 etc...&lt;br /&gt;
&lt;br /&gt;
Voice Recognition Possibilities:&lt;br /&gt;
&lt;br /&gt;
 Pursue a different voice recognition engine&lt;br /&gt;
 Pursue a different voice recognition version&lt;br /&gt;
 Contact CMU to determine sphinx2 status&lt;br /&gt;
 Contact CMU to determine possible/best alternative&lt;br /&gt;
&lt;br /&gt;
===Comment===&lt;br /&gt;
These are good ideas no matter the result of any attempt to improve on Sphinx2. --[[User:Miasma|Miasma]] 19:42, 24 November 2006 (EST)&lt;br /&gt;
&lt;br /&gt;
Non Voice Possibilities:&lt;br /&gt;
&lt;br /&gt;
 Script Automation&lt;br /&gt;
 Bluetooth Presentation/Automation&lt;br /&gt;
 Legalish Wifi Related Items&lt;br /&gt;
&lt;br /&gt;
== Meeting Approach ==&lt;br /&gt;
&lt;br /&gt;
1. Come to table with discussed project possibilities and any backround/code thats available.&lt;br /&gt;
&lt;br /&gt;
2. Set precedent for the meeting stating it won't be a social meeting and socializers will be asked to leave.&lt;br /&gt;
&lt;br /&gt;
3. Field the groups capabilities&lt;br /&gt;
 interests&lt;br /&gt;
 coding level&lt;br /&gt;
 languages&lt;br /&gt;
 topic experience level&lt;br /&gt;
 no of weekly hours they can devote&lt;br /&gt;
 contact information (preferably telephone numbers in an effort to establish perceived accountability and show we're&lt;br /&gt;
                      serious about time based progress)&lt;br /&gt;
4. Discuss potential project viability and fallback given the limited time alloted (perhaps consider working 2 projects at once).&lt;br /&gt;
&lt;br /&gt;
5. Open floor to alternative projects not discussed in case the group feels theres something with more potential.&lt;br /&gt;
&lt;br /&gt;
6. Decide which project is most suitable based on the groups skills, desires, and most importantly donated time available.&lt;br /&gt;
&lt;br /&gt;
7. Possibly have a mini intro to next meeting to try to bring some people up to speed on a given language&lt;br /&gt;
&lt;br /&gt;
8. Write pseudocode to determine what code is needed. Assign Classes/Methods/Functions to groups members based on&lt;br /&gt;
the pseudocode spec (ie we need these classes and these methods/functions which takes this as input and returns &lt;br /&gt;
output in this form). &lt;br /&gt;
&lt;br /&gt;
9. Create meeting outline before meeting stating the amount of time you'd like to spend discussing each item (adhereing to the &lt;br /&gt;
alloted time on the more irrelevant issues that might sidetrack discussion).&lt;br /&gt;
&lt;br /&gt;
10. Setup some mechanism of peer review (easiest method would be to assign any one part of the project to multiple people&lt;br /&gt;
hopefully we'll see results from at least one of them).&lt;br /&gt;
&lt;br /&gt;
11. Have definate plan and timetable for all actions when leaving the meeting, make sure people understand their task, what it entails,&lt;br /&gt;
the time it might take, and its due date. Also discuss alternatives to critical action items. &lt;br /&gt;
&lt;br /&gt;
12. Set precedent for problem solving. If you can't accomplish this task, what alerternatives can YOU as part of the group recommend&lt;br /&gt;
or persue to achieve this goal by the deadline.&lt;br /&gt;
&lt;br /&gt;
13. Communication! Point to sfvlug wiki, request that people spend 2 min daily checking out the SCALE projects state.&lt;br /&gt;
&lt;br /&gt;
14. Write everything down!&lt;br /&gt;
&lt;br /&gt;
15. Hand people a physical piece of paper with their task written on it. They won't forget and there won't be question as to what their&lt;br /&gt;
task was. Record the task in the project ledger.&lt;br /&gt;
&lt;br /&gt;
16. Post meeting notes (minus contact information that can't be made public) and whose in charge of which task or tasks to enable perfect&lt;br /&gt;
information and dialoging.&lt;br /&gt;
&lt;br /&gt;
17. Set a precedent to try to accomplish your assigned task as quickly as possible to enable task reassignment in the event they can&lt;br /&gt;
no longer accomplish their task (this might give people too much of an out and they may take the task alot less seriously if this is &lt;br /&gt;
even discussed, possibly only state to accomplish your task well before the deadline).&lt;br /&gt;
&lt;br /&gt;
18. Socialization can occur before or after the meeting!&lt;br /&gt;
&lt;br /&gt;
===Comment===&lt;br /&gt;
My assumption is that all this would be accomplished in a meeting proposed in the following section. We should probably bring this up at the next regular meeting to see how many would be willing and able to spend some time on this project. --[[User:Miasma|Miasma]] 19:47, 24 November 2006 (EST)&lt;br /&gt;
&lt;br /&gt;
== Timetable ==&lt;br /&gt;
&lt;br /&gt;
Max 7 weeks losing thansgiving and xmas/newyears weeks to relatives and responsibilities and the fact that the SCALE&lt;br /&gt;
meeting hasn't even been announced. &lt;br /&gt;
&lt;br /&gt;
== Action Items ==&lt;br /&gt;
&lt;br /&gt;
Have a SCALE related meeting ASAP&lt;br /&gt;
Bring project options to the table at the meeting annoucement in hopes to limit the groups discussion in a nonstructured meeting environment.&lt;br /&gt;
&lt;br /&gt;
===About This Document===&lt;br /&gt;
&lt;br /&gt;
This is all off the top of the head atm if its severity or content is wrong tweak it. I'm tired of typing this stuff so hopefully &lt;br /&gt;
I'll get back to this later (or someone else will).&lt;/div&gt;</description>
			<pubDate>Wed, 13 Dec 2006 10:37:28 GMT</pubDate>			<dc:creator>Koopa</dc:creator>			<comments>http://72.14.177.54/SFVLUG/Talk:SCALE</comments>		</item>
		<item>
			<title>SCALE</title>
			<link>http://72.14.177.54/SFVLUG/SCALE</link>
			<description>&lt;p&gt;Koopa:&amp;#32;/* Meeting Approach */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Alternatives ==&lt;br /&gt;
&lt;br /&gt;
Voice Synthesis Possibilities:&lt;br /&gt;
&lt;br /&gt;
 log watchers&lt;br /&gt;
 service checkers&lt;br /&gt;
 status checkers&lt;br /&gt;
 state checkers&lt;br /&gt;
 harverster readers&lt;br /&gt;
 ebook readers&lt;br /&gt;
 documentation readers&lt;br /&gt;
 security monitors&lt;br /&gt;
 bluetooth automation&lt;br /&gt;
 etc...&lt;br /&gt;
&lt;br /&gt;
Voice Recognition Possibilities:&lt;br /&gt;
&lt;br /&gt;
 Pursue a different voice recognition engine&lt;br /&gt;
 Pursue a different voice recognition version&lt;br /&gt;
 Contact CMU to determine sphinx2 status&lt;br /&gt;
 Contact CMU to determine possible/best alternative&lt;br /&gt;
&lt;br /&gt;
===Comment===&lt;br /&gt;
These are good ideas no matter the result of any attempt to improve on Sphinx2. --[[User:Miasma|Miasma]] 19:42, 24 November 2006 (EST)&lt;br /&gt;
&lt;br /&gt;
== Meeting Approach ==&lt;br /&gt;
&lt;br /&gt;
1. Come to table with discussed project possibilities and any backround/code thats available.&lt;br /&gt;
&lt;br /&gt;
2. Set precedent for the meeting stating it won't be a social meeting and socializers will be asked to leave.&lt;br /&gt;
&lt;br /&gt;
3. Field the groups capabilities&lt;br /&gt;
 interests&lt;br /&gt;
 coding level&lt;br /&gt;
 languages&lt;br /&gt;
 topic experience level&lt;br /&gt;
 no of weekly hours they can devote&lt;br /&gt;
 contact information (preferably telephone numbers in an effort to establish perceived accountability and show we're&lt;br /&gt;
                      serious about time based progress)&lt;br /&gt;
4. Discuss potential project viability and fallback given the limited time alloted (perhaps consider working 2 projects at once).&lt;br /&gt;
&lt;br /&gt;
5. Open floor to alternative projects not discussed in case the group feels theres something with more potential.&lt;br /&gt;
&lt;br /&gt;
6. Decide which project is most suitable based on the groups skills, desires, and most importantly donated time available.&lt;br /&gt;
&lt;br /&gt;
7. Possibly have a mini intro to next meeting to try to bring some people up to speed on a given language&lt;br /&gt;
&lt;br /&gt;
8. Write pseudocode to determine what code is needed. Assign Classes/Methods/Functions to groups members based on&lt;br /&gt;
the pseudocode spec (ie we need these classes and these methods/functions which takes this as input and returns &lt;br /&gt;
output in this form). &lt;br /&gt;
&lt;br /&gt;
9. Create meeting outline before meeting stating the amount of time you'd like to spend discussing each item (adhereing to the &lt;br /&gt;
alloted time on the more irrelevant issues that might sidetrack discussion).&lt;br /&gt;
&lt;br /&gt;
10. Setup some mechanism of peer review (easiest method would be to assign any one part of the project to multiple people&lt;br /&gt;
hopefully we'll see results from at least one of them).&lt;br /&gt;
&lt;br /&gt;
11. Have definate plan and timetable for all actions when leaving the meeting, make sure people understand their task, what it entails,&lt;br /&gt;
the time it might take, and its due date. Also discuss alternatives to critical action items. &lt;br /&gt;
&lt;br /&gt;
12. Set precedent for problem solving. If you can't accomplish this task, what alerternatives can YOU as part of the group recommend&lt;br /&gt;
or persue to achieve this goal by the deadline.&lt;br /&gt;
&lt;br /&gt;
13. Communication! Point to sfvlug wiki, request that people spend 2 min daily checking out the SCALE projects state.&lt;br /&gt;
&lt;br /&gt;
14. Write everything down!&lt;br /&gt;
&lt;br /&gt;
15. Hand people a physical piece of paper with their task written on it. They won't forget and there won't be question as to what their&lt;br /&gt;
task was. Record the task in the project ledger.&lt;br /&gt;
&lt;br /&gt;
16. Post meeting notes (minus contact information that can't be made public) and whose in charge of which task or tasks to enable perfect&lt;br /&gt;
information and dialoging.&lt;br /&gt;
&lt;br /&gt;
17. Set a precedent to try to accomplish your assigned task as quickly as possible to enable task reassignment in the event they can&lt;br /&gt;
no longer accomplish their task (this might give people too much of an out and they may take the task alot less seriously if this is &lt;br /&gt;
even discussed, possibly only state to accomplish your task well before the deadline).&lt;br /&gt;
&lt;br /&gt;
18. Socialization can occur before or after the meeting!&lt;br /&gt;
&lt;br /&gt;
===Comment===&lt;br /&gt;
My assumption is that all this would be accomplished in a meeting proposed in the following section. We should probably bring this up at the next regular meeting to see how many would be willing and able to spend some time on this project. --[[User:Miasma|Miasma]] 19:47, 24 November 2006 (EST)&lt;br /&gt;
&lt;br /&gt;
== Timetable ==&lt;br /&gt;
&lt;br /&gt;
Max 7 weeks losing thansgiving and xmas/newyears weeks to relatives and responsibilities and the fact that the SCALE&lt;br /&gt;
meeting hasn't even been announced. &lt;br /&gt;
&lt;br /&gt;
== Action Items ==&lt;br /&gt;
&lt;br /&gt;
Have a SCALE related meeting ASAP&lt;br /&gt;
Bring project options to the table at the meeting annoucement in hopes to limit the groups discussion in a nonstructured meeting environment.&lt;br /&gt;
&lt;br /&gt;
===About This Document===&lt;br /&gt;
&lt;br /&gt;
This is all off the top of the head atm if its severity or content is wrong tweak it. I'm tired of typing this stuff so hopefully &lt;br /&gt;
I'll get back to this later (or someone else will).&lt;/div&gt;</description>
			<pubDate>Wed, 13 Dec 2006 10:34:46 GMT</pubDate>			<dc:creator>Koopa</dc:creator>			<comments>http://72.14.177.54/SFVLUG/Talk:SCALE</comments>		</item>
		<item>
			<title>SCALE</title>
			<link>http://72.14.177.54/SFVLUG/SCALE</link>
			<description>&lt;p&gt;Koopa:&amp;#32;/* Meeting Approach */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Alternatives ==&lt;br /&gt;
&lt;br /&gt;
Voice Synthesis Possibilities:&lt;br /&gt;
&lt;br /&gt;
 log watchers&lt;br /&gt;
 service checkers&lt;br /&gt;
 status checkers&lt;br /&gt;
 state checkers&lt;br /&gt;
 harverster readers&lt;br /&gt;
 ebook readers&lt;br /&gt;
 documentation readers&lt;br /&gt;
 security monitors&lt;br /&gt;
 bluetooth automation&lt;br /&gt;
 etc...&lt;br /&gt;
&lt;br /&gt;
Voice Recognition Possibilities:&lt;br /&gt;
&lt;br /&gt;
 Pursue a different voice recognition engine&lt;br /&gt;
 Pursue a different voice recognition version&lt;br /&gt;
 Contact CMU to determine sphinx2 status&lt;br /&gt;
 Contact CMU to determine possible/best alternative&lt;br /&gt;
&lt;br /&gt;
===Comment===&lt;br /&gt;
These are good ideas no matter the result of any attempt to improve on Sphinx2. --[[User:Miasma|Miasma]] 19:42, 24 November 2006 (EST)&lt;br /&gt;
&lt;br /&gt;
== Meeting Approach ==&lt;br /&gt;
&lt;br /&gt;
1. Come to table with discussed project possibilities and any backround/code thats available.&lt;br /&gt;
&lt;br /&gt;
2. Set precedent for the meeting stating it won't be a social meeting and socializers will be asked to leave.&lt;br /&gt;
&lt;br /&gt;
3. Field the groups capabilities&lt;br /&gt;
 interests&lt;br /&gt;
 coding level&lt;br /&gt;
 languages&lt;br /&gt;
 topic experience level&lt;br /&gt;
 no of weekly hours they can devote&lt;br /&gt;
 contact information (preferably telephone numbers in an effort to establish perceived accountability and show we're&lt;br /&gt;
                      serious about time based progress)&lt;br /&gt;
 &lt;br /&gt;
4. Discuss potential project viability and fallback given the limited time alloted (perhaps consider working 2 projects at once).&lt;br /&gt;
&lt;br /&gt;
5. Open floor to alternative projects not discussed in case the group feels theres something with more potential.&lt;br /&gt;
&lt;br /&gt;
6. Decide which project is most suitable based on the groups skills, desires, and most importantly donated time available.&lt;br /&gt;
&lt;br /&gt;
7. Possibly have a mini intro to next meeting to try to bring some people up to speed on a given language&lt;br /&gt;
&lt;br /&gt;
8. Write pseudocode to determine what code is needed. Assign Classes/Methods/Functions to groups members based on&lt;br /&gt;
the pseudocode spec (ie we need these classes and these methods/functions which takes this as input and returns &lt;br /&gt;
output in this form). &lt;br /&gt;
&lt;br /&gt;
9. Create meeting outline before meeting stating the amount of time you'd like to spend discussing each item (adhereing to the &lt;br /&gt;
alloted time on the more irrelevant issues that might sidetrack discussion).&lt;br /&gt;
&lt;br /&gt;
10. Setup some mechanism of peer review (easiest method would be to assign any one part of the project to multiple people&lt;br /&gt;
hopefully we'll see results from at least one of them).&lt;br /&gt;
&lt;br /&gt;
11. Have definate plan and timetable for all actions when leaving the meeting, make sure people understand their task, what it entails,&lt;br /&gt;
the time it might take, and its due date. Also discuss alternatives to critical action items. &lt;br /&gt;
&lt;br /&gt;
12. Set precedent for problem solving. If you can't accomplish this task, what alerternatives can YOU as part of the group recommend&lt;br /&gt;
or persue to achieve this goal by the deadline.&lt;br /&gt;
&lt;br /&gt;
13. Communication! Point to sfvlug wiki, request that people spend 2 min daily checking out the SCALE projects state.&lt;br /&gt;
&lt;br /&gt;
14. Write everything down!&lt;br /&gt;
&lt;br /&gt;
15. Hand people a physical piece of paper with their task written on it. They won't forget and there won't be question as to what their&lt;br /&gt;
task was. Record the task in the project ledger.&lt;br /&gt;
&lt;br /&gt;
16. Post meeting notes (minus contact information that can't be made public) and whose in charge of which task or tasks to enable perfect&lt;br /&gt;
information and dialoging.&lt;br /&gt;
&lt;br /&gt;
17. Set a precedent to try to accomplish your assigned task as quickly as possible to enable task reassignment in the event they can&lt;br /&gt;
no longer accomplish their task (this might give people too much of an out and they may take the task alot less seriously if this is &lt;br /&gt;
even discussed, possibly only state to accomplish your task well before the deadline).&lt;br /&gt;
&lt;br /&gt;
18. Socialization can occur before or after the meeting!&lt;br /&gt;
&lt;br /&gt;
===Comment===&lt;br /&gt;
My assumption is that all this would be accomplished in a meeting proposed in the following section. We should probably bring this up at the next regular meeting to see how many would be willing and able to spend some time on this project. --[[User:Miasma|Miasma]] 19:47, 24 November 2006 (EST)&lt;br /&gt;
&lt;br /&gt;
== Timetable ==&lt;br /&gt;
&lt;br /&gt;
Max 7 weeks losing thansgiving and xmas/newyears weeks to relatives and responsibilities and the fact that the SCALE&lt;br /&gt;
meeting hasn't even been announced. &lt;br /&gt;
&lt;br /&gt;
== Action Items ==&lt;br /&gt;
&lt;br /&gt;
Have a SCALE related meeting ASAP&lt;br /&gt;
Bring project options to the table at the meeting annoucement in hopes to limit the groups discussion in a nonstructured meeting environment.&lt;br /&gt;
&lt;br /&gt;
===About This Document===&lt;br /&gt;
&lt;br /&gt;
This is all off the top of the head atm if its severity or content is wrong tweak it. I'm tired of typing this stuff so hopefully &lt;br /&gt;
I'll get back to this later (or someone else will).&lt;/div&gt;</description>
			<pubDate>Wed, 13 Dec 2006 10:34:35 GMT</pubDate>			<dc:creator>Koopa</dc:creator>			<comments>http://72.14.177.54/SFVLUG/Talk:SCALE</comments>		</item>
		<item>
			<title>SCALE</title>
			<link>http://72.14.177.54/SFVLUG/SCALE</link>
			<description>&lt;p&gt;Koopa:&amp;#32;/* Meeting Approach */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Alternatives ==&lt;br /&gt;
&lt;br /&gt;
Voice Synthesis Possibilities:&lt;br /&gt;
&lt;br /&gt;
 log watchers&lt;br /&gt;
 service checkers&lt;br /&gt;
 status checkers&lt;br /&gt;
 state checkers&lt;br /&gt;
 harverster readers&lt;br /&gt;
 ebook readers&lt;br /&gt;
 documentation readers&lt;br /&gt;
 security monitors&lt;br /&gt;
 bluetooth automation&lt;br /&gt;
 etc...&lt;br /&gt;
&lt;br /&gt;
Voice Recognition Possibilities:&lt;br /&gt;
&lt;br /&gt;
 Pursue a different voice recognition engine&lt;br /&gt;
 Pursue a different voice recognition version&lt;br /&gt;
 Contact CMU to determine sphinx2 status&lt;br /&gt;
 Contact CMU to determine possible/best alternative&lt;br /&gt;
&lt;br /&gt;
===Comment===&lt;br /&gt;
These are good ideas no matter the result of any attempt to improve on Sphinx2. --[[User:Miasma|Miasma]] 19:42, 24 November 2006 (EST)&lt;br /&gt;
&lt;br /&gt;
== Meeting Approach ==&lt;br /&gt;
&lt;br /&gt;
1. Come to table with discussed project possibilities and any backround/code thats available.&lt;br /&gt;
&lt;br /&gt;
2. Set precedent for the meeting stating it won't be a social meeting and socializers will be asked to leave.&lt;br /&gt;
&lt;br /&gt;
3. Field the groups capabilities&lt;br /&gt;
 interests&lt;br /&gt;
 coding level&lt;br /&gt;
 languages&lt;br /&gt;
 topic experience level&lt;br /&gt;
 no of weekly hours they can devote&lt;br /&gt;
 contact information (preferably telephone numbers in an effort to establish perceived accountability and show we're&lt;br /&gt;
 serious about time based progress)&lt;br /&gt;
  &lt;br /&gt;
4. Discuss potential project viability and fallback given the limited time alloted (perhaps consider working 2 projects at once).&lt;br /&gt;
&lt;br /&gt;
5. Open floor to alternative projects not discussed in case the group feels theres something with more potential.&lt;br /&gt;
&lt;br /&gt;
6. Decide which project is most suitable based on the groups skills, desires, and most importantly donated time available.&lt;br /&gt;
&lt;br /&gt;
7. Possibly have a mini intro to next meeting to try to bring some people up to speed on a given language&lt;br /&gt;
&lt;br /&gt;
8. Write pseudocode to determine what code is needed. Assign Classes/Methods/Functions to groups members based on&lt;br /&gt;
the pseudocode spec (ie we need these classes and these methods/functions which takes this as input and returns &lt;br /&gt;
output in this form). &lt;br /&gt;
&lt;br /&gt;
9. Create meeting outline before meeting stating the amount of time you'd like to spend discussing each item (adhereing to the &lt;br /&gt;
alloted time on the more irrelevant issues that might sidetrack discussion).&lt;br /&gt;
&lt;br /&gt;
10. Setup some mechanism of peer review (easiest method would be to assign any one part of the project to multiple people&lt;br /&gt;
hopefully we'll see results from at least one of them).&lt;br /&gt;
&lt;br /&gt;
11. Have definate plan and timetable for all actions when leaving the meeting, make sure people understand their task, what it entails,&lt;br /&gt;
the time it might take, and its due date. Also discuss alternatives to critical action items. &lt;br /&gt;
&lt;br /&gt;
12. Set precedent for problem solving. If you can't accomplish this task, what alerternatives can YOU as part of the group recommend&lt;br /&gt;
or persue to achieve this goal by the deadline.&lt;br /&gt;
&lt;br /&gt;
13. Communication! Point to sfvlug wiki, request that people spend 2 min daily checking out the SCALE projects state.&lt;br /&gt;
&lt;br /&gt;
14. Write everything down!&lt;br /&gt;
&lt;br /&gt;
15. Hand people a physical piece of paper with their task written on it. They won't forget and there won't be question as to what their&lt;br /&gt;
task was. Record the task in the project ledger.&lt;br /&gt;
&lt;br /&gt;
16. Post meeting notes (minus contact information that can't be made public) and whose in charge of which task or tasks to enable perfect&lt;br /&gt;
information and dialoging.&lt;br /&gt;
&lt;br /&gt;
17. Set a precedent to try to accomplish your assigned task as quickly as possible to enable task reassignment in the event they can&lt;br /&gt;
no longer accomplish their task (this might give people too much of an out and they may take the task alot less seriously if this is &lt;br /&gt;
even discussed, possibly only state to accomplish your task well before the deadline).&lt;br /&gt;
&lt;br /&gt;
18. Socialization can occur before or after the meeting!&lt;br /&gt;
&lt;br /&gt;
===Comment===&lt;br /&gt;
My assumption is that all this would be accomplished in a meeting proposed in the following section. We should probably bring this up at the next regular meeting to see how many would be willing and able to spend some time on this project. --[[User:Miasma|Miasma]] 19:47, 24 November 2006 (EST)&lt;br /&gt;
&lt;br /&gt;
== Timetable ==&lt;br /&gt;
&lt;br /&gt;
Max 7 weeks losing thansgiving and xmas/newyears weeks to relatives and responsibilities and the fact that the SCALE&lt;br /&gt;
meeting hasn't even been announced. &lt;br /&gt;
&lt;br /&gt;
== Action Items ==&lt;br /&gt;
&lt;br /&gt;
Have a SCALE related meeting ASAP&lt;br /&gt;
Bring project options to the table at the meeting annoucement in hopes to limit the groups discussion in a nonstructured meeting environment.&lt;br /&gt;
&lt;br /&gt;
===About This Document===&lt;br /&gt;
&lt;br /&gt;
This is all off the top of the head atm if its severity or content is wrong tweak it. I'm tired of typing this stuff so hopefully &lt;br /&gt;
I'll get back to this later (or someone else will).&lt;/div&gt;</description>
			<pubDate>Wed, 13 Dec 2006 10:34:15 GMT</pubDate>			<dc:creator>Koopa</dc:creator>			<comments>http://72.14.177.54/SFVLUG/Talk:SCALE</comments>		</item>
		<item>
			<title>SCALE</title>
			<link>http://72.14.177.54/SFVLUG/SCALE</link>
			<description>&lt;p&gt;Koopa:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Alternatives ==&lt;br /&gt;
&lt;br /&gt;
Voice Synthesis Possibilities:&lt;br /&gt;
&lt;br /&gt;
 log watchers&lt;br /&gt;
 service checkers&lt;br /&gt;
 status checkers&lt;br /&gt;
 state checkers&lt;br /&gt;
 harverster readers&lt;br /&gt;
 ebook readers&lt;br /&gt;
 documentation readers&lt;br /&gt;
 security monitors&lt;br /&gt;
 bluetooth automation&lt;br /&gt;
 etc...&lt;br /&gt;
&lt;br /&gt;
Voice Recognition Possibilities:&lt;br /&gt;
&lt;br /&gt;
 Pursue a different voice recognition engine&lt;br /&gt;
 Pursue a different voice recognition version&lt;br /&gt;
 Contact CMU to determine sphinx2 status&lt;br /&gt;
 Contact CMU to determine possible/best alternative&lt;br /&gt;
&lt;br /&gt;
===Comment===&lt;br /&gt;
These are good ideas no matter the result of any attempt to improve on Sphinx2. --[[User:Miasma|Miasma]] 19:42, 24 November 2006 (EST)&lt;br /&gt;
&lt;br /&gt;
== Meeting Approach ==&lt;br /&gt;
&lt;br /&gt;
1. Come to table with discussed project possibilities and any backround/code thats available.&lt;br /&gt;
&lt;br /&gt;
2. Set precedent for the meeting stating it won't be a social meeting and socializers will be asked to leave.&lt;br /&gt;
&lt;br /&gt;
3. Field the groups capabilities&lt;br /&gt;
 interests&lt;br /&gt;
 coding level&lt;br /&gt;
 languages&lt;br /&gt;
 topic experience level&lt;br /&gt;
 no of weekly hours they can devote&lt;br /&gt;
 contact information (preferably telephone numbers in an effort to establish perceived accountability and show we're serious about time based progress)&lt;br /&gt;
  &lt;br /&gt;
4. Discuss potential project viability and fallback given the limited time alloted (perhaps consider working 2 projects at once).&lt;br /&gt;
&lt;br /&gt;
5. Open floor to alternative projects not discussed in case the group feels theres something with more potential.&lt;br /&gt;
&lt;br /&gt;
6. Decide which project is most suitable based on the groups skills, desires, and most importantly donated time available.&lt;br /&gt;
&lt;br /&gt;
7. Possibly have a mini intro to next meeting to try to bring some people up to speed on a given language&lt;br /&gt;
&lt;br /&gt;
8. Write pseudocode to determine what code is needed. Assign Classes/Methods/Functions to groups members based on&lt;br /&gt;
the pseudocode spec (ie we need these classes and these methods/functions which takes this as input and returns &lt;br /&gt;
output in this form). &lt;br /&gt;
&lt;br /&gt;
9. Create meeting outline before meeting stating the amount of time you'd like to spend discussing each item (adhereing to the &lt;br /&gt;
alloted time on the more irrelevant issues that might sidetrack discussion).&lt;br /&gt;
&lt;br /&gt;
10. Setup some mechanism of peer review (easiest method would be to assign any one part of the project to multiple people&lt;br /&gt;
hopefully we'll see results from at least one of them).&lt;br /&gt;
&lt;br /&gt;
11. Have definate plan and timetable for all actions when leaving the meeting, make sure people understand their task, what it entails,&lt;br /&gt;
the time it might take, and its due date. Also discuss alternatives to critical action items. &lt;br /&gt;
&lt;br /&gt;
12. Set precedent for problem solving. If you can't accomplish this task, what alerternatives can YOU as part of the group recommend&lt;br /&gt;
or persue to achieve this goal by the deadline.&lt;br /&gt;
&lt;br /&gt;
13. Communication! Point to sfvlug wiki, request that people spend 2 min daily checking out the SCALE projects state.&lt;br /&gt;
&lt;br /&gt;
14. Write everything down!&lt;br /&gt;
&lt;br /&gt;
15. Hand people a physical piece of paper with their task written on it. They won't forget and there won't be question as to what their&lt;br /&gt;
task was. Record the task in the project ledger.&lt;br /&gt;
&lt;br /&gt;
16. Post meeting notes (minus contact information that can't be made public) and whose in charge of which task or tasks to enable perfect&lt;br /&gt;
information and dialoging.&lt;br /&gt;
&lt;br /&gt;
17. Set a precedent to try to accomplish your assigned task as quickly as possible to enable task reassignment in the event they can&lt;br /&gt;
no longer accomplish their task (this might give people too much of an out and they may take the task alot less seriously if this is &lt;br /&gt;
even discussed, possibly only state to accomplish your task well before the deadline).&lt;br /&gt;
&lt;br /&gt;
18. Socialization can occur before or after the meeting!&lt;br /&gt;
&lt;br /&gt;
===Comment===&lt;br /&gt;
My assumption is that all this would be accomplished in a meeting proposed in the following section. We should probably bring this up at the next regular meeting to see how many would be willing and able to spend some time on this project. --[[User:Miasma|Miasma]] 19:47, 24 November 2006 (EST)&lt;br /&gt;
&lt;br /&gt;
== Timetable ==&lt;br /&gt;
&lt;br /&gt;
Max 7 weeks losing thansgiving and xmas/newyears weeks to relatives and responsibilities and the fact that the SCALE&lt;br /&gt;
meeting hasn't even been announced. &lt;br /&gt;
&lt;br /&gt;
== Action Items ==&lt;br /&gt;
&lt;br /&gt;
Have a SCALE related meeting ASAP&lt;br /&gt;
Bring project options to the table at the meeting annoucement in hopes to limit the groups discussion in a nonstructured meeting environment.&lt;br /&gt;
&lt;br /&gt;
===About This Document===&lt;br /&gt;
&lt;br /&gt;
This is all off the top of the head atm if its severity or content is wrong tweak it. I'm tired of typing this stuff so hopefully &lt;br /&gt;
I'll get back to this later (or someone else will).&lt;/div&gt;</description>
			<pubDate>Wed, 13 Dec 2006 10:33:43 GMT</pubDate>			<dc:creator>Koopa</dc:creator>			<comments>http://72.14.177.54/SFVLUG/Talk:SCALE</comments>		</item>
		<item>
			<title>SCALE</title>
			<link>http://72.14.177.54/SFVLUG/SCALE</link>
			<description>&lt;p&gt;Koopa:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Alternatives===&lt;br /&gt;
&lt;br /&gt;
Voice Synthesis Possibilities:&lt;br /&gt;
&lt;br /&gt;
 log watchers&lt;br /&gt;
 service checkers&lt;br /&gt;
 status checkers&lt;br /&gt;
 state checkers&lt;br /&gt;
 harverster readers&lt;br /&gt;
 ebook readers&lt;br /&gt;
 documentation readers&lt;br /&gt;
 security monitors&lt;br /&gt;
 bluetooth automation&lt;br /&gt;
 etc...&lt;br /&gt;
&lt;br /&gt;
Voice Recognition Possibilities:&lt;br /&gt;
&lt;br /&gt;
 Pursue a different voice recognition engine&lt;br /&gt;
 Pursue a different voice recognition version&lt;br /&gt;
 Contact CMU to determine sphinx2 status&lt;br /&gt;
 Contact CMU to determine possible/best alternative&lt;br /&gt;
&lt;br /&gt;
===Comment===&lt;br /&gt;
These are good ideas no matter the result of any attempt to improve on Sphinx2. --[[User:Miasma|Miasma]] 19:42, 24 November 2006 (EST)&lt;br /&gt;
&lt;br /&gt;
===Meeting Approach===&lt;br /&gt;
&lt;br /&gt;
1. Come to table with discussed project possibilities and any backround/code thats available.&lt;br /&gt;
&lt;br /&gt;
2. Set precedent for the meeting stating it won't be a social meeting and socializers will be asked to leave.&lt;br /&gt;
&lt;br /&gt;
3. Field the groups capabilities&lt;br /&gt;
 interests&lt;br /&gt;
 coding level&lt;br /&gt;
 languages&lt;br /&gt;
 topic experience level&lt;br /&gt;
 no of weekly hours they can devote&lt;br /&gt;
 contact information (preferably telephone numbers in an effort to establish perceived accountability and show we're serious about time based progress)&lt;br /&gt;
  &lt;br /&gt;
4. Discuss potential project viability and fallback given the limited time alloted (perhaps consider working 2 projects at once).&lt;br /&gt;
&lt;br /&gt;
5. Open floor to alternative projects not discussed in case the group feels theres something with more potential.&lt;br /&gt;
&lt;br /&gt;
6. Decide which project is most suitable based on the groups skills, desires, and most importantly donated time available.&lt;br /&gt;
&lt;br /&gt;
7. Possibly have a mini intro to next meeting to try to bring some people up to speed on a given language&lt;br /&gt;
&lt;br /&gt;
8. Write pseudocode to determine what code is needed. Assign Classes/Methods/Functions to groups members based on&lt;br /&gt;
the pseudocode spec (ie we need these classes and these methods/functions which takes this as input and returns &lt;br /&gt;
output in this form). &lt;br /&gt;
&lt;br /&gt;
9. Create meeting outline before meeting stating the amount of time you'd like to spend discussing each item (adhereing to the &lt;br /&gt;
alloted time on the more irrelevant issues that might sidetrack discussion).&lt;br /&gt;
&lt;br /&gt;
10. Setup some mechanism of peer review (easiest method would be to assign any one part of the project to multiple people&lt;br /&gt;
hopefully we'll see results from at least one of them).&lt;br /&gt;
&lt;br /&gt;
11. Have definate plan and timetable for all actions when leaving the meeting, make sure people understand their task, what it entails,&lt;br /&gt;
the time it might take, and its due date. Also discuss alternatives to critical action items. &lt;br /&gt;
&lt;br /&gt;
12. Set precedent for problem solving. If you can't accomplish this task, what alerternatives can YOU as part of the group recommend&lt;br /&gt;
or persue to achieve this goal by the deadline.&lt;br /&gt;
&lt;br /&gt;
13. Communication! Point to sfvlug wiki, request that people spend 2 min daily checking out the SCALE projects state.&lt;br /&gt;
&lt;br /&gt;
14. Write everything down!&lt;br /&gt;
&lt;br /&gt;
15. Hand people a physical piece of paper with their task written on it. They won't forget and there won't be question as to what their&lt;br /&gt;
task was. Record the task in the project ledger.&lt;br /&gt;
&lt;br /&gt;
16. Post meeting notes (minus contact information that can't be made public) and whose in charge of which task or tasks to enable perfect&lt;br /&gt;
information and dialoging.&lt;br /&gt;
&lt;br /&gt;
17. Set a precedent to try to accomplish your assigned task as quickly as possible to enable task reassignment in the event they can&lt;br /&gt;
no longer accomplish their task (this might give people too much of an out and they may take the task alot less seriously if this is &lt;br /&gt;
even discussed, possibly only state to accomplish your task well before the deadline).&lt;br /&gt;
&lt;br /&gt;
18. Socialization can occur before or after the meeting!&lt;br /&gt;
&lt;br /&gt;
===Comment===&lt;br /&gt;
My assumption is that all this would be accomplished in a meeting proposed in the following section. We should probably bring this up at the next regular meeting to see how many would be willing and able to spend some time on this project. --[[User:Miasma|Miasma]] 19:47, 24 November 2006 (EST)&lt;br /&gt;
&lt;br /&gt;
===Timetable===&lt;br /&gt;
&lt;br /&gt;
Max 7 weeks losing thansgiving and xmas/newyears weeks to relatives and responsibilities and the fact that the SCALE&lt;br /&gt;
meeting hasn't even been announced. &lt;br /&gt;
&lt;br /&gt;
===Action Items===&lt;br /&gt;
&lt;br /&gt;
Have a SCALE related meeting ASAP&lt;br /&gt;
Bring project options to the table at the meeting annoucement in hopes to limit the groups discussion in a nonstructured meeting environment.&lt;br /&gt;
&lt;br /&gt;
===About This Document===&lt;br /&gt;
&lt;br /&gt;
This is all off the top of the head atm if its severity or content is wrong tweak it. I'm tired of typing this stuff so hopefully &lt;br /&gt;
I'll get back to this later (or someone else will).&lt;/div&gt;</description>
			<pubDate>Wed, 13 Dec 2006 10:32:38 GMT</pubDate>			<dc:creator>Koopa</dc:creator>			<comments>http://72.14.177.54/SFVLUG/Talk:SCALE</comments>		</item>
		<item>
			<title>Psyche Project</title>
			<link>http://72.14.177.54/SFVLUG/Psyche_Project</link>
			<description>&lt;p&gt;Koopa:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Psyche Project Page==&lt;br /&gt;
&lt;br /&gt;
Psyche is a project we started for [http://www.socallinuxexpo.org/scale5x/ SCALE] in 2003. It was designed to demonstrate speech recognition and speech synthesis on the GNU/Linux platform. We had lines of people waiting to talk to Psyche at the show. Since it was such a big hit and we will continue as long as interest holds up.&lt;br /&gt;
&lt;br /&gt;
In the tradition of *nix programming Psyche itself is basically just a glue that cobbles together some existing tools. The main components being [http://cmusphinx.sourceforge.net/html/cmusphinx.php Sphinx] and [http://www.speech.cs.cmu.edu/festival/ Festival] along with a few other tools to provide a system of speech recognition and speech synthesis on a Linux based PC. Most of the original code was written in [http://www.python.org/ Python] by Steve Petrovits &amp;amp; Rick Wang. Since then we have made improvements including a new module that reads IRC chat logs aloud in real time as they arrive.&lt;br /&gt;
&lt;br /&gt;
If you are fluent in [http://www.python.org/ Python] or would like to become fluent this is a great project to join. You can find some project files [http://forpractice.com/sfvlug/psyche/ here]. You can download all the necessary files in a tarball at: http://forpractice.com/sfvlug/psyche/psyche.tar.gz&lt;br /&gt;
&lt;br /&gt;
More to follow soon!&lt;br /&gt;
&lt;br /&gt;
The following contribution by Steve with comments by Kurt regarding the status of the Psyche project:&lt;br /&gt;
== Status ==&lt;br /&gt;
&lt;br /&gt;
PSYCHE is unviable in its current state. The only possible way to remedy this solution would be to contact CMU and ask them whats up.&lt;br /&gt;
Given the fact that no ones expressed any interest in pursing anything SCALE related whatsoever I doubt this will happen in&lt;br /&gt;
the time left before the expo in February.&lt;br /&gt;
&lt;br /&gt;
===Comment===&lt;br /&gt;
I'll try contacting someone at CMU this next week. Perhaps we should consider backup plans no matter the results of any attempt to get Sphinx2 working better. This has been a continuing problem. --[[User:Miasma|Miasma]] 19:40, 24 November 2006 (EST)&lt;/div&gt;</description>
			<pubDate>Wed, 13 Dec 2006 10:29:30 GMT</pubDate>			<dc:creator>Koopa</dc:creator>			<comments>http://72.14.177.54/SFVLUG/Talk:Psyche_Project</comments>		</item>
		<item>
			<title>SCALE</title>
			<link>http://72.14.177.54/SFVLUG/SCALE</link>
			<description>&lt;p&gt;Koopa:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Comment===&lt;br /&gt;
I'd think all the following lines really belong in a SCALE specific section under sfvlug projects and not here? --[[User:Koopa|Koopa]] 04:03, 13 December 2006 (EST)&lt;br /&gt;
&lt;br /&gt;
== Possible Alternatives ==&lt;br /&gt;
&lt;br /&gt;
Voice Synthesis Possibilities:&lt;br /&gt;
&lt;br /&gt;
 log watchers&lt;br /&gt;
 service checkers&lt;br /&gt;
 status checkers&lt;br /&gt;
 state checkers&lt;br /&gt;
 harverster readers&lt;br /&gt;
 ebook readers&lt;br /&gt;
 documentation readers&lt;br /&gt;
 security monitors&lt;br /&gt;
 etc...&lt;br /&gt;
&lt;br /&gt;
Voice Recognition Possibilities:&lt;br /&gt;
&lt;br /&gt;
 Pursue a different voice recognition engine&lt;br /&gt;
 Pursue a different voice recognition version&lt;br /&gt;
 Contact CMU to determine sphinx2 status&lt;br /&gt;
 Contact CMU to determine possible/best alternative&lt;br /&gt;
===Comment===&lt;br /&gt;
These are good ideas no matter the result of any attempt to improve on Sphinx2. --[[User:Miasma|Miasma]] 19:42, 24 November 2006 (EST)&lt;br /&gt;
&lt;br /&gt;
== Approach ==&lt;br /&gt;
&lt;br /&gt;
1. Come to table with discussed project possibilities and any backround/code thats available.&lt;br /&gt;
&lt;br /&gt;
2. Set precedent for the meeting stating it won't be a social meeting and socializers will be asked to leave.&lt;br /&gt;
&lt;br /&gt;
3. Field the groups capabilities&lt;br /&gt;
 interests&lt;br /&gt;
 coding level&lt;br /&gt;
 languages&lt;br /&gt;
 topic experience level&lt;br /&gt;
 no of weekly hours they can devote&lt;br /&gt;
 contact information (preferably telephone numbers in an effort to establish perceived accountability and show we're serious about time based progress)&lt;br /&gt;
  &lt;br /&gt;
4. Discuss potential project viability and fallback given the limited time alloted (perhaps consider working 2 projects at once).&lt;br /&gt;
&lt;br /&gt;
5. Open floor to alternative projects not discussed in case the group feels theres something with more potential.&lt;br /&gt;
&lt;br /&gt;
6. Decide which project is most suitable based on the groups skills, desires, and most importantly donated time available.&lt;br /&gt;
&lt;br /&gt;
7. Possibly have a mini intro to next meeting to try to bring some people up to speed on a given language&lt;br /&gt;
&lt;br /&gt;
8. Write pseudocode to determine what code is needed. Assign Classes/Methods/Functions to groups members based on&lt;br /&gt;
the pseudocode spec (ie we need these classes and these methods/functions which takes this as input and returns &lt;br /&gt;
output in this form). &lt;br /&gt;
&lt;br /&gt;
9. Create meeting outline before meeting stating the amount of time you'd like to spend discussing each item (adhereing to the &lt;br /&gt;
alloted time on the more irrelevant issues that might sidetrack discussion).&lt;br /&gt;
&lt;br /&gt;
10. Setup some mechanism of peer review (easiest method would be to assign any one part of the project to multiple people&lt;br /&gt;
hopefully we'll see results from at least one of them).&lt;br /&gt;
&lt;br /&gt;
11. Have definate plan and timetable for all actions when leaving the meeting, make sure people understand their task, what it entails,&lt;br /&gt;
the time it might take, and its due date. Also discuss alternatives to critical action items. &lt;br /&gt;
&lt;br /&gt;
12. Set precedent for problem solving. If you can't accomplish this task, what alerternatives can YOU as part of the group recommend&lt;br /&gt;
or persue to achieve this goal by the deadline.&lt;br /&gt;
&lt;br /&gt;
13. Communication! Point to sfvlug wiki, request that people spend 2 min daily checking out the SCALE projects state.&lt;br /&gt;
&lt;br /&gt;
14. Write everything down!&lt;br /&gt;
&lt;br /&gt;
15. Hand people a physical piece of paper with their task written on it. They won't forget and there won't be question as to what their&lt;br /&gt;
task was. Record the task in the project ledger.&lt;br /&gt;
&lt;br /&gt;
16. Post meeting notes (minus contact information that can't be made public) and whose in charge of which task or tasks to enable perfect&lt;br /&gt;
information and dialoging.&lt;br /&gt;
&lt;br /&gt;
17. Set a precedent to try to accomplish your assigned task as quickly as possible to enable task reassignment in the event they can&lt;br /&gt;
no longer accomplish their task (this might give people too much of an out and they may take the task alot less seriously if this is &lt;br /&gt;
even discussed, possibly only state to accomplish your task well before the deadline).&lt;br /&gt;
&lt;br /&gt;
18. Socialization can occur before or after the meeting!&lt;br /&gt;
&lt;br /&gt;
===Comment===&lt;br /&gt;
My assumption is that all this would be accomplished in a meeting proposed in the following section. We should probably bring this up at the next regular meeting to see how many would be willing and able to spend some time on this project. --[[User:Miasma|Miasma]] 19:47, 24 November 2006 (EST)&lt;br /&gt;
&lt;br /&gt;
== Timetable ==&lt;br /&gt;
&lt;br /&gt;
Max 7 weeks losing thansgiving and xmas/newyears weeks to relatives and responsibilities and the fact that the SCALE&lt;br /&gt;
meeting hasn't even been announced. &lt;br /&gt;
&lt;br /&gt;
== Action Items ==&lt;br /&gt;
&lt;br /&gt;
Have a SCALE related meeting ASAP&lt;br /&gt;
Bring project options to the table at the meeting annoucement in hopes to limit the groups discussion in a nonstructured meeting environment.&lt;br /&gt;
&lt;br /&gt;
== About This Document ==&lt;br /&gt;
&lt;br /&gt;
This is all off the top of the head atm if its severity or content is wrong tweak it. I'm tired of typing this stuff so hopefully &lt;br /&gt;
I'll get back to this later (or someone else will).&lt;/div&gt;</description>
			<pubDate>Wed, 13 Dec 2006 10:28:03 GMT</pubDate>			<dc:creator>Koopa</dc:creator>			<comments>http://72.14.177.54/SFVLUG/Talk:SCALE</comments>		</item>
		<item>
			<title>SCALE Project Page</title>
			<link>http://72.14.177.54/SFVLUG/SCALE_Project_Page</link>
			<description>&lt;p&gt;Koopa:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</description>
			<pubDate>Wed, 13 Dec 2006 10:26:51 GMT</pubDate>			<dc:creator>Koopa</dc:creator>			<comments>http://72.14.177.54/SFVLUG/Talk:SCALE_Project_Page</comments>		</item>
		<item>
			<title>Main Page</title>
			<link>http://72.14.177.54/SFVLUG/Main_Page</link>
			<description>&lt;p&gt;Koopa:&amp;#32;/* SCALE Project Page */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
Welcome to the San Fernando Valley Linux Users Group (SFVLUG) wiki. This site is currently hosted by [http://www.editthis.info EditThis] using [http://www.mediawiki.org/ MediaWiki] software. We will decide whether or not to keep it going here or move it to our own server once our own server is up to speed.&lt;br /&gt;
&lt;br /&gt;
Our primary site is [http://www.sfvlug.org www.sfvlug.org] and any information found there is to be considered authoritative. Please use any information in it over this site in the case of conflicting information. This site is not secure and can be edited by someone without authority.&lt;br /&gt;
&lt;br /&gt;
==Announcements==&lt;br /&gt;
&lt;br /&gt;
===[[Meetings]]===  announcements for membership meetings and events provided by SFVLUG&lt;br /&gt;
&lt;br /&gt;
===[[Presentations]]===  Presentation page. Links to resources and slides.&lt;br /&gt;
&lt;br /&gt;
===[[Special Interest Groups]]=== subgroups of SFVLUG with an interest in a particular area(s) relating to F/OSS&lt;br /&gt;
&lt;br /&gt;
===[[SFVLUG:Community Portal | Community Portal]]=== external links to the open source community in cyberspace&lt;br /&gt;
&lt;br /&gt;
==Resources==&lt;br /&gt;
&lt;br /&gt;
===[[Newbie Resources]]=== resources for those new to GNU/Linux and/or open source software&lt;br /&gt;
&lt;br /&gt;
===[[Classes]]=== instruction beyond one time presentations&lt;br /&gt;
&lt;br /&gt;
===[[Code Vault]]=== looking for or wanting to donate any bash script or other short and simple code, check this out&lt;br /&gt;
&lt;br /&gt;
===[[People Page]]=== personal pages for members&lt;br /&gt;
&lt;br /&gt;
==Projects==&lt;br /&gt;
&lt;br /&gt;
===[[Project Page]]=== Active and proposed projects, includes discussion.&lt;br /&gt;
&lt;br /&gt;
===[[SCALE]]=== SCALE discussion (status, current and future projects, methods, etc)&lt;br /&gt;
&lt;br /&gt;
==Help==&lt;br /&gt;
&lt;br /&gt;
===[[Wiki Specific Info]]=== info on the wiki software used for this site&lt;br /&gt;
&lt;br /&gt;
==[[Sandbox]]== Use this area for training and experimentation&lt;br /&gt;
&lt;br /&gt;
==[[Pending]]== Use this area to develop content thats not yet ready for public viewing&lt;br /&gt;
&lt;br /&gt;
==About Us==&lt;br /&gt;
We are a very loosely organized group of GNU/Linux and open source software enthusiasts, that live/work/meet in the San Fernando Valley, a suburb of Los Angeles in Southern Californina. You don't actually need to live in the Valley to join, but attending meetings is more difficult if you don't. Please see our [[Announcements]] page for more information on meetings. If you can't attend regular meetings you can still get involved here at this wiki, or in our IRC chat on [http://freenode.net/ freenode] in #sfvlug.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
==Copyleft==&lt;br /&gt;
We need to work out copyright/copyleft/public domain issues, so we can include material with restricted licenses, but at this time you should consider any submission to this site as being in the public domain. Do not post copyrighted material to this site no matter what license without the permission of the copyright holder. Any license restricts what you can and can not do with the material, even the GPL. If you need to reference copyrighted material and can't get permission please use an external link to the original material.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Thank you for visiting the SFVLUG wiki.'''&lt;/div&gt;</description>
			<pubDate>Wed, 13 Dec 2006 10:24:51 GMT</pubDate>			<dc:creator>Koopa</dc:creator>			<comments>http://72.14.177.54/SFVLUG/Talk:Main_Page</comments>		</item>
		<item>
			<title>SCALE Project Page</title>
			<link>http://72.14.177.54/SFVLUG/SCALE_Project_Page</link>
			<description>&lt;p&gt;Koopa:&amp;#32;/* Psyche Project */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Projects===&lt;br /&gt;
&lt;br /&gt;
====[[Psyche Project]]==== our SCALE speech recognition and systhesis project&lt;br /&gt;
&lt;br /&gt;
===Alternatives===&lt;br /&gt;
&lt;br /&gt;
Voice Synthesis Possibilities:&lt;br /&gt;
&lt;br /&gt;
 log watchers&lt;br /&gt;
 service checkers&lt;br /&gt;
 status checkers&lt;br /&gt;
 state checkers&lt;br /&gt;
 harverster readers&lt;br /&gt;
 ebook readers&lt;br /&gt;
 documentation readers&lt;br /&gt;
 security monitors&lt;br /&gt;
 etc...&lt;br /&gt;
&lt;br /&gt;
Voice Recognition Possibilities:&lt;br /&gt;
&lt;br /&gt;
 Pursue a different voice recognition engine&lt;br /&gt;
 Pursue a different voice recognition version&lt;br /&gt;
 Contact CMU to determine sphinx2 status&lt;br /&gt;
 Contact CMU to determine possible/best alternative&lt;br /&gt;
===Comment===&lt;br /&gt;
These are good ideas no matter the result of any attempt to improve on Sphinx2. --[[User:Miasma|Miasma]] 19:42, 24 November 2006 (EST)&lt;/div&gt;</description>
			<pubDate>Wed, 13 Dec 2006 10:22:54 GMT</pubDate>			<dc:creator>Koopa</dc:creator>			<comments>http://72.14.177.54/SFVLUG/Talk:SCALE_Project_Page</comments>		</item>
		<item>
			<title>SCALE Project Page</title>
			<link>http://72.14.177.54/SFVLUG/SCALE_Project_Page</link>
			<description>&lt;p&gt;Koopa:&amp;#32;/* SCALE Alternatives */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;====[[Psyche Project]]==== our SCALE speech recognition and systhesis project&lt;br /&gt;
&lt;br /&gt;
===Alternatives===&lt;br /&gt;
&lt;br /&gt;
Voice Synthesis Possibilities:&lt;br /&gt;
&lt;br /&gt;
 log watchers&lt;br /&gt;
 service checkers&lt;br /&gt;
 status checkers&lt;br /&gt;
 state checkers&lt;br /&gt;
 harverster readers&lt;br /&gt;
 ebook readers&lt;br /&gt;
 documentation readers&lt;br /&gt;
 security monitors&lt;br /&gt;
 etc...&lt;br /&gt;
&lt;br /&gt;
Voice Recognition Possibilities:&lt;br /&gt;
&lt;br /&gt;
 Pursue a different voice recognition engine&lt;br /&gt;
 Pursue a different voice recognition version&lt;br /&gt;
 Contact CMU to determine sphinx2 status&lt;br /&gt;
 Contact CMU to determine possible/best alternative&lt;br /&gt;
===Comment===&lt;br /&gt;
These are good ideas no matter the result of any attempt to improve on Sphinx2. --[[User:Miasma|Miasma]] 19:42, 24 November 2006 (EST)&lt;/div&gt;</description>
			<pubDate>Wed, 13 Dec 2006 10:22:36 GMT</pubDate>			<dc:creator>Koopa</dc:creator>			<comments>http://72.14.177.54/SFVLUG/Talk:SCALE_Project_Page</comments>		</item>
		<item>
			<title>SCALE Project Page</title>
			<link>http://72.14.177.54/SFVLUG/SCALE_Project_Page</link>
			<description>&lt;p&gt;Koopa:&amp;#32;/* Psyche Project */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;====[[Psyche Project]]==== our SCALE speech recognition and systhesis project&lt;br /&gt;
&lt;br /&gt;
== SCALE Alternatives ==&lt;br /&gt;
&lt;br /&gt;
Voice Synthesis Possibilities:&lt;br /&gt;
&lt;br /&gt;
 log watchers&lt;br /&gt;
 service checkers&lt;br /&gt;
 status checkers&lt;br /&gt;
 state checkers&lt;br /&gt;
 harverster readers&lt;br /&gt;
 ebook readers&lt;br /&gt;
 documentation readers&lt;br /&gt;
 security monitors&lt;br /&gt;
 etc...&lt;br /&gt;
&lt;br /&gt;
Voice Recognition Possibilities:&lt;br /&gt;
&lt;br /&gt;
 Pursue a different voice recognition engine&lt;br /&gt;
 Pursue a different voice recognition version&lt;br /&gt;
 Contact CMU to determine sphinx2 status&lt;br /&gt;
 Contact CMU to determine possible/best alternative&lt;br /&gt;
===Comment===&lt;br /&gt;
These are good ideas no matter the result of any attempt to improve on Sphinx2. --[[User:Miasma|Miasma]] 19:42, 24 November 2006 (EST)&lt;/div&gt;</description>
			<pubDate>Wed, 13 Dec 2006 09:11:18 GMT</pubDate>			<dc:creator>Koopa</dc:creator>			<comments>http://72.14.177.54/SFVLUG/Talk:SCALE_Project_Page</comments>		</item>
		<item>
			<title>SCALE Project Page</title>
			<link>http://72.14.177.54/SFVLUG/SCALE_Project_Page</link>
			<description>&lt;p&gt;Koopa:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;====[[Psyche Project]]==== our SCALE speech recognition and systhesis project&lt;/div&gt;</description>
			<pubDate>Wed, 13 Dec 2006 09:09:37 GMT</pubDate>			<dc:creator>Koopa</dc:creator>			<comments>http://72.14.177.54/SFVLUG/Talk:SCALE_Project_Page</comments>		</item>
		<item>
			<title>Main Page</title>
			<link>http://72.14.177.54/SFVLUG/Main_Page</link>
			<description>&lt;p&gt;Koopa:&amp;#32;/* Projects */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
Welcome to the San Fernando Valley Linux Users Group (SFVLUG) wiki. This site is currently hosted by [http://www.editthis.info EditThis] using [http://www.mediawiki.org/ MediaWiki] software. We will decide whether or not to keep it going here or move it to our own server once our own server is up to speed.&lt;br /&gt;
&lt;br /&gt;
Our primary site is [http://www.sfvlug.org www.sfvlug.org] and any information found there is to be considered authoritative. Please use any information in it over this site in the case of conflicting information. This site is not secure and can be edited by someone without authority.&lt;br /&gt;
&lt;br /&gt;
==Announcements==&lt;br /&gt;
&lt;br /&gt;
===[[Meetings]]===  announcements for membership meetings and events provided by SFVLUG&lt;br /&gt;
&lt;br /&gt;
===[[Presentations]]===  Presentation page. Links to resources and slides.&lt;br /&gt;
&lt;br /&gt;
===[[Special Interest Groups]]=== subgroups of SFVLUG with an interest in a particular area(s) relating to F/OSS&lt;br /&gt;
&lt;br /&gt;
===[[SFVLUG:Community Portal | Community Portal]]=== external links to the open source community in cyberspace&lt;br /&gt;
&lt;br /&gt;
==Resources==&lt;br /&gt;
&lt;br /&gt;
===[[Newbie Resources]]=== resources for those new to GNU/Linux and/or open source software&lt;br /&gt;
&lt;br /&gt;
===[[Classes]]=== instruction beyond one time presentations&lt;br /&gt;
&lt;br /&gt;
===[[Code Vault]]=== looking for or wanting to donate any bash script or other short and simple code, check this out&lt;br /&gt;
&lt;br /&gt;
===[[People Page]]=== personal pages for members&lt;br /&gt;
&lt;br /&gt;
==Projects==&lt;br /&gt;
&lt;br /&gt;
===[[Project Page]]=== Active and proposed projects, includes discussion.&lt;br /&gt;
&lt;br /&gt;
===[[SCALE Project Page]]=== SCALE discussion (status, current and future projects, methods, etc)&lt;br /&gt;
&lt;br /&gt;
==Help==&lt;br /&gt;
&lt;br /&gt;
===[[Wiki Specific Info]]=== info on the wiki software used for this site&lt;br /&gt;
&lt;br /&gt;
==[[Sandbox]]== Use this area for training and experimentation&lt;br /&gt;
&lt;br /&gt;
==[[Pending]]== Use this area to develop content thats not yet ready for public viewing&lt;br /&gt;
&lt;br /&gt;
==About Us==&lt;br /&gt;
We are a very loosely organized group of GNU/Linux and open source software enthusiasts, that live/work/meet in the San Fernando Valley, a suburb of Los Angeles in Southern Californina. You don't actually need to live in the Valley to join, but attending meetings is more difficult if you don't. Please see our [[Announcements]] page for more information on meetings. If you can't attend regular meetings you can still get involved here at this wiki, or in our IRC chat on [http://freenode.net/ freenode] in #sfvlug.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
==Copyleft==&lt;br /&gt;
We need to work out copyright/copyleft/public domain issues, so we can include material with restricted licenses, but at this time you should consider any submission to this site as being in the public domain. Do not post copyrighted material to this site no matter what license without the permission of the copyright holder. Any license restricts what you can and can not do with the material, even the GPL. If you need to reference copyrighted material and can't get permission please use an external link to the original material.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Thank you for visiting the SFVLUG wiki.'''&lt;/div&gt;</description>
			<pubDate>Wed, 13 Dec 2006 09:09:26 GMT</pubDate>			<dc:creator>Koopa</dc:creator>			<comments>http://72.14.177.54/SFVLUG/Talk:Main_Page</comments>		</item>
		<item>
			<title>Main Page</title>
			<link>http://72.14.177.54/SFVLUG/Main_Page</link>
			<description>&lt;p&gt;Koopa:&amp;#32;/* Projects */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
Welcome to the San Fernando Valley Linux Users Group (SFVLUG) wiki. This site is currently hosted by [http://www.editthis.info EditThis] using [http://www.mediawiki.org/ MediaWiki] software. We will decide whether or not to keep it going here or move it to our own server once our own server is up to speed.&lt;br /&gt;
&lt;br /&gt;
Our primary site is [http://www.sfvlug.org www.sfvlug.org] and any information found there is to be considered authoritative. Please use any information in it over this site in the case of conflicting information. This site is not secure and can be edited by someone without authority.&lt;br /&gt;
&lt;br /&gt;
==Announcements==&lt;br /&gt;
&lt;br /&gt;
===[[Meetings]]===  announcements for membership meetings and events provided by SFVLUG&lt;br /&gt;
&lt;br /&gt;
===[[Presentations]]===  Presentation page. Links to resources and slides.&lt;br /&gt;
&lt;br /&gt;
===[[Special Interest Groups]]=== subgroups of SFVLUG with an interest in a particular area(s) relating to F/OSS&lt;br /&gt;
&lt;br /&gt;
===[[SFVLUG:Community Portal | Community Portal]]=== external links to the open source community in cyberspace&lt;br /&gt;
&lt;br /&gt;
==Resources==&lt;br /&gt;
&lt;br /&gt;
===[[Newbie Resources]]=== resources for those new to GNU/Linux and/or open source software&lt;br /&gt;
&lt;br /&gt;
===[[Classes]]=== instruction beyond one time presentations&lt;br /&gt;
&lt;br /&gt;
===[[Code Vault]]=== looking for or wanting to donate any bash script or other short and simple code, check this out&lt;br /&gt;
&lt;br /&gt;
===[[People Page]]=== personal pages for members&lt;br /&gt;
&lt;br /&gt;
==Projects==&lt;br /&gt;
&lt;br /&gt;
===[[Project Page]]=== Active and proposed projects, includes discussion.&lt;br /&gt;
&lt;br /&gt;
===[[SCALE Project Page]]=== SCALE discussion (status, current and future projects, methods, etc)&lt;br /&gt;
&lt;br /&gt;
====[[Psyche Project]]==== our SCALE speech recognition and systhesis project&lt;br /&gt;
&lt;br /&gt;
==Help==&lt;br /&gt;
&lt;br /&gt;
===[[Wiki Specific Info]]=== info on the wiki software used for this site&lt;br /&gt;
&lt;br /&gt;
==[[Sandbox]]== Use this area for training and experimentation&lt;br /&gt;
&lt;br /&gt;
==[[Pending]]== Use this area to develop content thats not yet ready for public viewing&lt;br /&gt;
&lt;br /&gt;
==About Us==&lt;br /&gt;
We are a very loosely organized group of GNU/Linux and open source software enthusiasts, that live/work/meet in the San Fernando Valley, a suburb of Los Angeles in Southern Californina. You don't actually need to live in the Valley to join, but attending meetings is more difficult if you don't. Please see our [[Announcements]] page for more information on meetings. If you can't attend regular meetings you can still get involved here at this wiki, or in our IRC chat on [http://freenode.net/ freenode] in #sfvlug.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
==Copyleft==&lt;br /&gt;
We need to work out copyright/copyleft/public domain issues, so we can include material with restricted licenses, but at this time you should consider any submission to this site as being in the public domain. Do not post copyrighted material to this site no matter what license without the permission of the copyright holder. Any license restricts what you can and can not do with the material, even the GPL. If you need to reference copyrighted material and can't get permission please use an external link to the original material.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Thank you for visiting the SFVLUG wiki.'''&lt;/div&gt;</description>
			<pubDate>Wed, 13 Dec 2006 09:09:06 GMT</pubDate>			<dc:creator>Koopa</dc:creator>			<comments>http://72.14.177.54/SFVLUG/Talk:Main_Page</comments>		</item>
		<item>
			<title>Psyche Project</title>
			<link>http://72.14.177.54/SFVLUG/Psyche_Project</link>
			<description>&lt;p&gt;Koopa:&amp;#32;/* Possible Alternatives */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Psyche Project Page==&lt;br /&gt;
&lt;br /&gt;
Psyche is a project we started for [http://www.socallinuxexpo.org/scale5x/ SCALE] in 2003. It was designed to demonstrate speech recognition and speech synthesis on the GNU/Linux platform. We had lines of people waiting to talk to Psyche at the show. Since it was such a big hit and we will continue as long as interest holds up.&lt;br /&gt;
&lt;br /&gt;
In the tradition of *nix programming Psyche itself is basically just a glue that cobbles together some existing tools. The main components being [http://cmusphinx.sourceforge.net/html/cmusphinx.php Sphinx] and [http://www.speech.cs.cmu.edu/festival/ Festival] along with a few other tools to provide a system of speech recognition and speech synthesis on a Linux based PC. Most of the original code was written in [http://www.python.org/ Python] by Steve Petrovits &amp;amp; Rick Wang. Since then we have made improvements including a new module that reads IRC chat logs aloud in real time as they arrive.&lt;br /&gt;
&lt;br /&gt;
If you are fluent in [http://www.python.org/ Python] or would like to become fluent this is a great project to join. You can find some project files [http://forpractice.com/sfvlug/psyche/ here]. You can download all the necessary files in a tarball at: http://forpractice.com/sfvlug/psyche/psyche.tar.gz&lt;br /&gt;
&lt;br /&gt;
More to follow soon!&lt;br /&gt;
&lt;br /&gt;
The following contribution by Steve with comments by Kurt regarding the status of the Psyche project:&lt;br /&gt;
== Status ==&lt;br /&gt;
&lt;br /&gt;
PSYCHE is unviable in its current state. The only possible way to remedy this solution would be to contact CMU and ask them whats up.&lt;br /&gt;
Given the fact that no ones expressed any interest in pursing anything SCALE related whatsoever I doubt this will happen in&lt;br /&gt;
the time left before the expo in February.&lt;br /&gt;
&lt;br /&gt;
===Comment===&lt;br /&gt;
I'll try contacting someone at CMU this next week. Perhaps we should consider backup plans no matter the results of any attempt to get Sphinx2 working better. This has been a continuing problem. --[[User:Miasma|Miasma]] 19:40, 24 November 2006 (EST)&lt;br /&gt;
&lt;br /&gt;
===Comment===&lt;br /&gt;
I'd think all the following lines really belong in a SCALE specific section under sfvlug projects and not here? --[[User:Koopa|Koopa]] 04:03, 13 December 2006 (EST)&lt;br /&gt;
&lt;br /&gt;
== Possible Alternatives ==&lt;br /&gt;
&lt;br /&gt;
Voice Synthesis Possibilities:&lt;br /&gt;
&lt;br /&gt;
 log watchers&lt;br /&gt;
 service checkers&lt;br /&gt;
 status checkers&lt;br /&gt;
 state checkers&lt;br /&gt;
 harverster readers&lt;br /&gt;
 ebook readers&lt;br /&gt;
 documentation readers&lt;br /&gt;
 security monitors&lt;br /&gt;
 etc...&lt;br /&gt;
&lt;br /&gt;
Voice Recognition Possibilities:&lt;br /&gt;
&lt;br /&gt;
 Pursue a different voice recognition engine&lt;br /&gt;
 Pursue a different voice recognition version&lt;br /&gt;
 Contact CMU to determine sphinx2 status&lt;br /&gt;
 Contact CMU to determine possible/best alternative&lt;br /&gt;
===Comment===&lt;br /&gt;
These are good ideas no matter the result of any attempt to improve on Sphinx2. --[[User:Miasma|Miasma]] 19:42, 24 November 2006 (EST)&lt;br /&gt;
&lt;br /&gt;
== Approach ==&lt;br /&gt;
&lt;br /&gt;
1. Come to table with discussed project possibilities and any backround/code thats available.&lt;br /&gt;
&lt;br /&gt;
2. Set precedent for the meeting stating it won't be a social meeting and socializers will be asked to leave.&lt;br /&gt;
&lt;br /&gt;
3. Field the groups capabilities&lt;br /&gt;
 interests&lt;br /&gt;
 coding level&lt;br /&gt;
 languages&lt;br /&gt;
 topic experience level&lt;br /&gt;
 no of weekly hours they can devote&lt;br /&gt;
 contact information (preferably telephone numbers in an effort to establish perceived accountability and show we're serious about time based progress)&lt;br /&gt;
  &lt;br /&gt;
4. Discuss potential project viability and fallback given the limited time alloted (perhaps consider working 2 projects at once).&lt;br /&gt;
&lt;br /&gt;
5. Open floor to alternative projects not discussed in case the group feels theres something with more potential.&lt;br /&gt;
&lt;br /&gt;
6. Decide which project is most suitable based on the groups skills, desires, and most importantly donated time available.&lt;br /&gt;
&lt;br /&gt;
7. Possibly have a mini intro to next meeting to try to bring some people up to speed on a given language&lt;br /&gt;
&lt;br /&gt;
8. Write pseudocode to determine what code is needed. Assign Classes/Methods/Functions to groups members based on&lt;br /&gt;
the pseudocode spec (ie we need these classes and these methods/functions which takes this as input and returns &lt;br /&gt;
output in this form). &lt;br /&gt;
&lt;br /&gt;
9. Create meeting outline before meeting stating the amount of time you'd like to spend discussing each item (adhereing to the &lt;br /&gt;
alloted time on the more irrelevant issues that might sidetrack discussion).&lt;br /&gt;
&lt;br /&gt;
10. Setup some mechanism of peer review (easiest method would be to assign any one part of the project to multiple people&lt;br /&gt;
hopefully we'll see results from at least one of them).&lt;br /&gt;
&lt;br /&gt;
11. Have definate plan and timetable for all actions when leaving the meeting, make sure people understand their task, what it entails,&lt;br /&gt;
the time it might take, and its due date. Also discuss alternatives to critical action items. &lt;br /&gt;
&lt;br /&gt;
12. Set precedent for problem solving. If you can't accomplish this task, what alerternatives can YOU as part of the group recommend&lt;br /&gt;
or persue to achieve this goal by the deadline.&lt;br /&gt;
&lt;br /&gt;
13. Communication! Point to sfvlug wiki, request that people spend 2 min daily checking out the SCALE projects state.&lt;br /&gt;
&lt;br /&gt;
14. Write everything down!&lt;br /&gt;
&lt;br /&gt;
15. Hand people a physical piece of paper with their task written on it. They won't forget and there won't be question as to what their&lt;br /&gt;
task was. Record the task in the project ledger.&lt;br /&gt;
&lt;br /&gt;
16. Post meeting notes (minus contact information that can't be made public) and whose in charge of which task or tasks to enable perfect&lt;br /&gt;
information and dialoging.&lt;br /&gt;
&lt;br /&gt;
17. Set a precedent to try to accomplish your assigned task as quickly as possible to enable task reassignment in the event they can&lt;br /&gt;
no longer accomplish their task (this might give people too much of an out and they may take the task alot less seriously if this is &lt;br /&gt;
even discussed, possibly only state to accomplish your task well before the deadline).&lt;br /&gt;
&lt;br /&gt;
18. Socialization can occur before or after the meeting!&lt;br /&gt;
&lt;br /&gt;
===Comment===&lt;br /&gt;
My assumption is that all this would be accomplished in a meeting proposed in the following section. We should probably bring this up at the next regular meeting to see how many would be willing and able to spend some time on this project. --[[User:Miasma|Miasma]] 19:47, 24 November 2006 (EST)&lt;br /&gt;
&lt;br /&gt;
== Timetable ==&lt;br /&gt;
&lt;br /&gt;
Max 7 weeks losing thansgiving and xmas/newyears weeks to relatives and responsibilities and the fact that the SCALE&lt;br /&gt;
meeting hasn't even been announced. &lt;br /&gt;
&lt;br /&gt;
== Action Items ==&lt;br /&gt;
&lt;br /&gt;
Have a SCALE related meeting ASAP&lt;br /&gt;
Bring project options to the table at the meeting annoucement in hopes to limit the groups discussion in a nonstructured meeting environment.&lt;br /&gt;
&lt;br /&gt;
== About This Document ==&lt;br /&gt;
&lt;br /&gt;
This is all off the top of the head atm if its severity or content is wrong tweak it. I'm tired of typing this stuff so hopefully &lt;br /&gt;
I'll get back to this later (or someone else will).&lt;/div&gt;</description>
			<pubDate>Wed, 13 Dec 2006 09:03:23 GMT</pubDate>			<dc:creator>Koopa</dc:creator>			<comments>http://72.14.177.54/SFVLUG/Talk:Psyche_Project</comments>		</item>
		<item>
			<title>Pending</title>
			<link>http://72.14.177.54/SFVLUG/Pending</link>
			<description>&lt;p&gt;Koopa:&amp;#32;/* Additional Useful Info You Should Learn */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;''Under Construction!'' (recategorise, review, augment, and add descriptions after more sleep)&lt;br /&gt;
&lt;br /&gt;
==Newbie Command line Essentials (Learn these now!)==&lt;br /&gt;
&lt;br /&gt;
If you don't know your commandline very well at least know the tools that you have at your disposal to find the information and operate most efficiently. This section will contain only the entries that will enable you to maximize your productivity at the command line. &lt;br /&gt;
&lt;br /&gt;
Search and documentation tools are some of the most important tools you can learn on your box heres a brief list of a few of the most popular, all of which can be accessed through your terminal (xterm, rxvt, etc...) or console (&amp;lt;ctrl&amp;gt;&amp;lt;alt&amp;gt;F1...F6). Note: Commands in no particular order examples not applicable in all distributions or setups.&lt;br /&gt;
&lt;br /&gt;
'''Info'''&lt;br /&gt;
&lt;br /&gt;
 man - an interface to the on-line reference manuals (ex: man hier)&lt;br /&gt;
 find - search the manual page names and descriptions (ex: find ~ -name '*.mp3')&lt;br /&gt;
 locate - security Enhanced version of the GNU Locate (ex: locate hosts)&lt;br /&gt;
 updatedb - update the slocate database (ex: updatedb&amp;amp;)&lt;br /&gt;
 which - locate a command (ex: which ifconfig)&lt;br /&gt;
 whereis - locate the binary, source, and manual page files for a command (ex. whereis ifconfig)&lt;br /&gt;
 hier - description of the file system hierarchy (ex. man hier)&lt;br /&gt;
 apropos - search the manual page names and descriptions (ex. apropos &amp;lt;keyword&amp;gt;)&lt;br /&gt;
 less - page through text one screenful at a time allowing for forward and backward movement in the file (ex. less&lt;br /&gt;
 /usr/share/doc/debian/debian-manifesto)&lt;br /&gt;
 su - change user ID or become super-user (ex. su - &amp;lt;passwd&amp;gt;)&lt;br /&gt;
 sudo - execute a command as another user (ex. sudo /etc/init.d/networking)&lt;br /&gt;
 history - display the list of commands previously typed (ex. history)&lt;br /&gt;
&lt;br /&gt;
'''Keystrokes'''&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;ctrl&amp;gt;r - reverse keyword search of the command history (ex. &amp;lt;ctrl&amp;gt;r&amp;lt;keyword&amp;gt;&lt;br /&gt;
 / - search forward for occurance of keyword in a manpage, many editors and pagers (ex. /&amp;lt;keyword&amp;gt;)&lt;br /&gt;
 ? - search backward for occurance of keyword in a manpage, many editors and pagers (ex. ?&amp;lt;keyword&amp;gt;)&lt;br /&gt;
 n - continue to the next occurance of the keyword searches listed above (ex. n)&lt;br /&gt;
&lt;br /&gt;
'''Network'''&lt;br /&gt;
 ifconfig - configure a network interface (ex. ifconfig eth0 192.168.0.2)&lt;br /&gt;
 route - show / manipulate the IP routing table (ex. route add -net default gw 192.168.0.1)&lt;br /&gt;
 iwconfig - configure a wireless network interface (ex. iwconfig eth2 essid GaylesPerk channel 11 mode auto)&lt;br /&gt;
 iwlist - get more detailed wireless information from a wireless interface (ex. iwlist eth2 scan)&lt;br /&gt;
 ifup - bring a network interface up (ex. ifup eth0)&lt;br /&gt;
 ifdown - take a network interface down (ex. ifdown eth0)&lt;br /&gt;
&lt;br /&gt;
'''Paths'''&lt;br /&gt;
&lt;br /&gt;
 /usr/share/doc, /usr/local/doc - documentation paths&lt;br /&gt;
 /var/log - path of all your log files&lt;br /&gt;
 /etc - most of your config files&lt;br /&gt;
 /etc/init.d - system service control scripts&lt;br /&gt;
 ~ - an abbreviation of your home directory (long form: /home/user)&lt;br /&gt;
 / - root path, the base/parent path of all paths&lt;br /&gt;
 . - current working directory&lt;br /&gt;
 ./ - path based off of the current working directory&lt;br /&gt;
 ../ - parent path &lt;br /&gt;
 &lt;br /&gt;
'''Special Characters'''&lt;br /&gt;
&lt;br /&gt;
 Note: not all essential but all worth learning early&lt;br /&gt;
 | - pipeline command, the standard output of one command is connected to the standard input of another command&lt;br /&gt;
     (ie take the output of one  command and send it to another)&lt;br /&gt;
 \\ - preserves the literal value of the command that follows, except newline&lt;br /&gt;
     (takes any special characters and turns them into something akin to text characters)&lt;br /&gt;
 &amp;amp; - if a command is terminated by the control operator &amp;amp;, the shell executes the command in the background in a subshell &lt;br /&gt;
 &amp;amp;&amp;amp; and || - the control operators &amp;amp;&amp;amp; and ││ denote AND lists and OR lists, respectively. An AND list has the form:&lt;br /&gt;
     command1 &amp;amp;&amp;amp; command2 (Note: command2  is  executed if, and only if, command1 returns an exit status of zero)&lt;br /&gt;
 ; - commands separated by a ; are executed sequentially&lt;br /&gt;
&lt;br /&gt;
==Useful Info (Optional but worth learning as you go!)==&lt;br /&gt;
&lt;br /&gt;
Note: These your should pursue in your own time using the commands listed above for additional information!&lt;br /&gt;
&lt;br /&gt;
 General: alias, free, jobs, fg, dmesg, uname, xargs&lt;br /&gt;
 Pattern Matching: grep, rgrep, egrep, fgrep&lt;br /&gt;
 Process: top, ps, pgrep, nice, renice, kill, pkill, killall&lt;br /&gt;
 Network: route, traceroute, arp, netstat, ping&lt;br /&gt;
 File and Filesystem: cp, mv, rm, ls, cd, chmod, chown, cat, du, df, lsof, touch&lt;br /&gt;
 Conveniences: ssh-agent, keychains, screen&lt;br /&gt;
 Debian Package Manager: apt-get, dpkg, apt-cache, apt-file (Note: Debian based distribution specific)&lt;br /&gt;
 Files and File Locations: /etc/passwd, /etc/hosts, /etc/hosts.allow, /etc/hosts.deny, /etc/hostname, /etc/resolv.conf, /etc/groups,&lt;br /&gt;
                           /etc/fstab, /etc/modules, ~/.bashrc, ~/.bash_profile, ~/.bash_aliases&lt;/div&gt;</description>
			<pubDate>Wed, 13 Dec 2006 08:54:21 GMT</pubDate>			<dc:creator>Koopa</dc:creator>			<comments>http://72.14.177.54/SFVLUG/Talk:Pending</comments>		</item>
		<item>
			<title>Pending</title>
			<link>http://72.14.177.54/SFVLUG/Pending</link>
			<description>&lt;p&gt;Koopa:&amp;#32;/* Newbie Command line Essentials (Learn these now!) */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;''Under Construction!'' (recategorise, review, augment, and add descriptions after more sleep)&lt;br /&gt;
&lt;br /&gt;
==Newbie Command line Essentials (Learn these now!)==&lt;br /&gt;
&lt;br /&gt;
If you don't know your commandline very well at least know the tools that you have at your disposal to find the information and operate most efficiently. This section will contain only the entries that will enable you to maximize your productivity at the command line. &lt;br /&gt;
&lt;br /&gt;
Search and documentation tools are some of the most important tools you can learn on your box heres a brief list of a few of the most popular, all of which can be accessed through your terminal (xterm, rxvt, etc...) or console (&amp;lt;ctrl&amp;gt;&amp;lt;alt&amp;gt;F1...F6). Note: Commands in no particular order examples not applicable in all distributions or setups.&lt;br /&gt;
&lt;br /&gt;
'''Info'''&lt;br /&gt;
&lt;br /&gt;
 man - an interface to the on-line reference manuals (ex: man hier)&lt;br /&gt;
 find - search the manual page names and descriptions (ex: find ~ -name '*.mp3')&lt;br /&gt;
 locate - security Enhanced version of the GNU Locate (ex: locate hosts)&lt;br /&gt;
 updatedb - update the slocate database (ex: updatedb&amp;amp;)&lt;br /&gt;
 which - locate a command (ex: which ifconfig)&lt;br /&gt;
 whereis - locate the binary, source, and manual page files for a command (ex. whereis ifconfig)&lt;br /&gt;
 hier - description of the file system hierarchy (ex. man hier)&lt;br /&gt;
 apropos - search the manual page names and descriptions (ex. apropos &amp;lt;keyword&amp;gt;)&lt;br /&gt;
 less - page through text one screenful at a time allowing for forward and backward movement in the file (ex. less&lt;br /&gt;
 /usr/share/doc/debian/debian-manifesto)&lt;br /&gt;
 su - change user ID or become super-user (ex. su - &amp;lt;passwd&amp;gt;)&lt;br /&gt;
 sudo - execute a command as another user (ex. sudo /etc/init.d/networking)&lt;br /&gt;
 history - display the list of commands previously typed (ex. history)&lt;br /&gt;
&lt;br /&gt;
'''Keystrokes'''&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;ctrl&amp;gt;r - reverse keyword search of the command history (ex. &amp;lt;ctrl&amp;gt;r&amp;lt;keyword&amp;gt;&lt;br /&gt;
 / - search forward for occurance of keyword in a manpage, many editors and pagers (ex. /&amp;lt;keyword&amp;gt;)&lt;br /&gt;
 ? - search backward for occurance of keyword in a manpage, many editors and pagers (ex. ?&amp;lt;keyword&amp;gt;)&lt;br /&gt;
 n - continue to the next occurance of the keyword searches listed above (ex. n)&lt;br /&gt;
&lt;br /&gt;
'''Network'''&lt;br /&gt;
 ifconfig - configure a network interface (ex. ifconfig eth0 192.168.0.2)&lt;br /&gt;
 route - show / manipulate the IP routing table (ex. route add -net default gw 192.168.0.1)&lt;br /&gt;
 iwconfig - configure a wireless network interface (ex. iwconfig eth2 essid GaylesPerk channel 11 mode auto)&lt;br /&gt;
 iwlist - get more detailed wireless information from a wireless interface (ex. iwlist eth2 scan)&lt;br /&gt;
 ifup - bring a network interface up (ex. ifup eth0)&lt;br /&gt;
 ifdown - take a network interface down (ex. ifdown eth0)&lt;br /&gt;
&lt;br /&gt;
'''Paths'''&lt;br /&gt;
&lt;br /&gt;
 /usr/share/doc, /usr/local/doc - documentation paths&lt;br /&gt;
 /var/log - path of all your log files&lt;br /&gt;
 /etc - most of your config files&lt;br /&gt;
 /etc/init.d - system service control scripts&lt;br /&gt;
 ~ - an abbreviation of your home directory (long form: /home/user)&lt;br /&gt;
 / - root path, the base/parent path of all paths&lt;br /&gt;
 . - current working directory&lt;br /&gt;
 ./ - path based off of the current working directory&lt;br /&gt;
 ../ - parent path &lt;br /&gt;
 &lt;br /&gt;
'''Special Characters'''&lt;br /&gt;
&lt;br /&gt;
 Note: not all essential but all worth learning early&lt;br /&gt;
 | - pipeline command, the standard output of one command is connected to the standard input of another command&lt;br /&gt;
     (ie take the output of one  command and send it to another)&lt;br /&gt;
 \\ - preserves the literal value of the command that follows, except newline&lt;br /&gt;
     (takes any special characters and turns them into something akin to text characters)&lt;br /&gt;
 &amp;amp; - if a command is terminated by the control operator &amp;amp;, the shell executes the command in the background in a subshell &lt;br /&gt;
 &amp;amp;&amp;amp; and || - the control operators &amp;amp;&amp;amp; and ││ denote AND lists and OR lists, respectively. An AND list has the form:&lt;br /&gt;
     command1 &amp;amp;&amp;amp; command2 (Note: command2  is  executed if, and only if, command1 returns an exit status of zero)&lt;br /&gt;
 ; - commands separated by a ; are executed sequentially&lt;br /&gt;
&lt;br /&gt;
==Additional Useful Info You Should Learn==&lt;br /&gt;
&lt;br /&gt;
Note: These your should pursue in your own time using the commands listed above for additional information!&lt;br /&gt;
&lt;br /&gt;
 General: alias, free, jobs, fg, dmesg, uname, xargs&lt;br /&gt;
 Pattern Matching: grep, rgrep, egrep, fgrep&lt;br /&gt;
 Process: top, ps, pgrep, nice, renice, kill, pkill, killall&lt;br /&gt;
 Network: route, traceroute, arp, netstat, ping&lt;br /&gt;
 File and Filesystem: cp, mv, rm, ls, cd, chmod, chown, cat, du, df, lsof&lt;br /&gt;
 Conveniences: ssh-agent, keychains, screen&lt;br /&gt;
 Debian Package Manager: apt-get, dpkg, apt-cache, apt-file (Note: Debian based distribution specific)&lt;br /&gt;
 Files and File Locations: /etc/passwd, /etc/hosts, /etc/hosts.allow, /etc/hosts.deny, /etc/hostname, /etc/resolv.conf, /etc/groups,&lt;br /&gt;
                           /etc/fstab, /etc/modules, ~/.bashrc, ~/.bash_profile, ~/.bash_aliases&lt;/div&gt;</description>
			<pubDate>Wed, 13 Dec 2006 08:50:53 GMT</pubDate>			<dc:creator>Koopa</dc:creator>			<comments>http://72.14.177.54/SFVLUG/Talk:Pending</comments>		</item>
		<item>
			<title>Pending</title>
			<link>http://72.14.177.54/SFVLUG/Pending</link>
			<description>&lt;p&gt;Koopa:&amp;#32;/* Newbie Command line Essentials */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;''Under Construction!'' (recategorise, review, augment, and add descriptions after more sleep)&lt;br /&gt;
&lt;br /&gt;
==Newbie Command line Essentials (Learn these now!)==&lt;br /&gt;
&lt;br /&gt;
If you don't know your commandline very well at least know the tools that you have at your disposal to find the information and operate most efficiently. This section will contain only the entries that will enable you to maximize your productivity at the command line. &lt;br /&gt;
&lt;br /&gt;
Search and documentation tools are some of the most important tools you can learn on your box heres a brief list of a few of the most popular, all of which can be accessed through your terminal (xterm, rxvt, etc...) or console (&amp;lt;ctrl&amp;gt;&amp;lt;alt&amp;gt;F1...F6). Note: Commands in no particular order examples not applicable in all distributions or setups.&lt;br /&gt;
&lt;br /&gt;
'''Info'''&lt;br /&gt;
 man - an interface to the on-line reference manuals (ex: man hier)&lt;br /&gt;
 find - search the manual page names and descriptions (ex: find ~ -name '*.mp3')&lt;br /&gt;
 locate - security Enhanced version of the GNU Locate (ex: locate hosts)&lt;br /&gt;
 updatedb - update the slocate database (ex: updatedb&amp;amp;)&lt;br /&gt;
 which - locate a command (ex: which ifconfig)&lt;br /&gt;
 whereis - locate the binary, source, and manual page files for a command (ex. whereis ifconfig)&lt;br /&gt;
 hier - description of the file system hierarchy (ex. man hier)&lt;br /&gt;
 apropos - search the manual page names and descriptions (ex. apropos &amp;lt;keyword&amp;gt;)&lt;br /&gt;
 less - page through text one screenful at a time allowing for forward and backward movement in the file (ex. less&lt;br /&gt;
 /usr/share/doc/debian/debian-manifesto)&lt;br /&gt;
 su - change user ID or become super-user (ex. su - &amp;lt;passwd&amp;gt;)&lt;br /&gt;
 sudo - execute a command as another user (ex. sudo /etc/init.d/networking)&lt;br /&gt;
 history - display the list of commands previously typed (ex. history)&lt;br /&gt;
&lt;br /&gt;
'''Keystrokes'''&lt;br /&gt;
 &amp;lt;ctrl&amp;gt;r - reverse keyword search of the command history (ex. &amp;lt;ctrl&amp;gt;r&amp;lt;keyword&amp;gt;&lt;br /&gt;
 / - search forward for occurance of keyword in a manpage, many editors and pagers (ex. /&amp;lt;keyword&amp;gt;)&lt;br /&gt;
 ? - search backward for occurance of keyword in a manpage, many editors and pagers (ex. ?&amp;lt;keyword&amp;gt;)&lt;br /&gt;
 n - continue to the next occurance of the keyword searches listed above (ex. n)&lt;br /&gt;
&lt;br /&gt;
'''Network'''&lt;br /&gt;
 ifconfig - configure a network interface (ex. ifconfig eth0 192.168.0.2)&lt;br /&gt;
 route - show / manipulate the IP routing table (ex. route add -net default gw 192.168.0.1)&lt;br /&gt;
 iwconfig - configure a wireless network interface (ex. iwconfig eth2 essid GaylesPerk channel 11 mode auto)&lt;br /&gt;
 iwlist - get more detailed wireless information from a wireless interface (ex. iwlist eth2 scan)&lt;br /&gt;
 ifup - bring a network interface up (ex. ifup eth0)&lt;br /&gt;
 ifdown - take a network interface down (ex. ifdown eth0)&lt;br /&gt;
&lt;br /&gt;
'''Paths'''&lt;br /&gt;
 /usr/share/doc, /usr/local/doc - documentation paths&lt;br /&gt;
 /var/log - path of all your log files&lt;br /&gt;
 /etc - most of your config files&lt;br /&gt;
 /etc/init.d - system service control scripts&lt;br /&gt;
 ~ - an abbreviation of your home directory (long form: /home/user)&lt;br /&gt;
 / - root path, the base/parent path of all paths&lt;br /&gt;
 . - current working directory&lt;br /&gt;
 ./ - path based off of the current working directory&lt;br /&gt;
 ../ - parent path &lt;br /&gt;
 &lt;br /&gt;
'''Special Characters'''&lt;br /&gt;
&lt;br /&gt;
 Note: not all essential but all worth learning early&lt;br /&gt;
 | - pipeline command, the standard output of one command is connected to the standard input of another command&lt;br /&gt;
     (ie take the output of one  command and send it to another)&lt;br /&gt;
 \\ - preserves the literal value of the command that follows, except newline&lt;br /&gt;
     (takes any special characters and turns them into something akin to text characters)&lt;br /&gt;
 &amp;amp; - if a command is terminated by the control operator &amp;amp;, the shell executes the command in the background in a subshell &lt;br /&gt;
 &amp;amp;&amp;amp; and || - the control operators &amp;amp;&amp;amp; and ││ denote AND lists and OR lists, respectively. An AND list has the form:&lt;br /&gt;
     command1 &amp;amp;&amp;amp; command2 (Note: command2  is  executed if, and only if, command1 returns an exit status of zero)&lt;br /&gt;
 ; - commands separated by a ; are executed sequentially&lt;br /&gt;
&lt;br /&gt;
==Additional Useful Info You Should Learn==&lt;br /&gt;
&lt;br /&gt;
Note: These your should pursue in your own time using the commands listed above for additional information!&lt;br /&gt;
&lt;br /&gt;
 General: alias, free, jobs, fg, dmesg, uname, xargs&lt;br /&gt;
 Pattern Matching: grep, rgrep, egrep, fgrep&lt;br /&gt;
 Process: top, ps, pgrep, nice, renice, kill, pkill, killall&lt;br /&gt;
 Network: route, traceroute, arp, netstat, ping&lt;br /&gt;
 File and Filesystem: cp, mv, rm, ls, cd, chmod, chown, cat, du, df, lsof&lt;br /&gt;
 Conveniences: ssh-agent, keychains, screen&lt;br /&gt;
 Debian Package Manager: apt-get, dpkg, apt-cache, apt-file (Note: Debian based distribution specific)&lt;br /&gt;
 Files and File Locations: /etc/passwd, /etc/hosts, /etc/hosts.allow, /etc/hosts.deny, /etc/hostname, /etc/resolv.conf, /etc/groups,&lt;br /&gt;
                           /etc/fstab, /etc/modules, ~/.bashrc, ~/.bash_profile, ~/.bash_aliases&lt;/div&gt;</description>
			<pubDate>Wed, 13 Dec 2006 08:50:18 GMT</pubDate>			<dc:creator>Koopa</dc:creator>			<comments>http://72.14.177.54/SFVLUG/Talk:Pending</comments>		</item>
		<item>
			<title>Pending</title>
			<link>http://72.14.177.54/SFVLUG/Pending</link>
			<description>&lt;p&gt;Koopa:&amp;#32;/* Additional Useful Commands */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;''Under Construction!'' (recategorise, review, augment, and add descriptions after more sleep)&lt;br /&gt;
&lt;br /&gt;
==Newbie Command line Essentials==&lt;br /&gt;
&lt;br /&gt;
If you don't know your commandline very well at least know the tools that you have at your disposal to find the information and operate most efficiently. This section will contain only the entries that will enable you to maximize your productivity at the command line. &lt;br /&gt;
&lt;br /&gt;
Search and documentation tools are some of the most important tools you can learn on your box heres a brief list of a few of the most popular, all of which can be accessed through your terminal (xterm, rxvt, etc...) or console (&amp;lt;ctrl&amp;gt;&amp;lt;alt&amp;gt;F1...F6). Note: Commands in no particular order examples not applicable in all distributions or setups.&lt;br /&gt;
&lt;br /&gt;
'''Info'''&lt;br /&gt;
 man - an interface to the on-line reference manuals (ex: man hier)&lt;br /&gt;
 find - search the manual page names and descriptions (ex: find ~ -name '*.mp3')&lt;br /&gt;
 locate - security Enhanced version of the GNU Locate (ex: locate hosts)&lt;br /&gt;
 updatedb - update the slocate database (ex: updatedb&amp;amp;)&lt;br /&gt;
 which - locate a command (ex: which ifconfig)&lt;br /&gt;
 whereis - locate the binary, source, and manual page files for a command (ex. whereis ifconfig)&lt;br /&gt;
 hier - description of the file system hierarchy (ex. man hier)&lt;br /&gt;
 apropos - search the manual page names and descriptions (ex. apropos &amp;lt;keyword&amp;gt;)&lt;br /&gt;
 less - page through text one screenful at a time allowing for forward and backward movement in the file (ex. less&lt;br /&gt;
 /usr/share/doc/debian/debian-manifesto)&lt;br /&gt;
 su - change user ID or become super-user (ex. su - &amp;lt;passwd&amp;gt;)&lt;br /&gt;
 sudo - execute a command as another user (ex. sudo /etc/init.d/networking)&lt;br /&gt;
 history - display the list of commands previously typed (ex. history)&lt;br /&gt;
&lt;br /&gt;
'''Keystrokes'''&lt;br /&gt;
 &amp;lt;ctrl&amp;gt;r - reverse keyword search of the command history (ex. &amp;lt;ctrl&amp;gt;r&amp;lt;keyword&amp;gt;&lt;br /&gt;
 / - search forward for occurance of keyword in a manpage, many editors and pagers (ex. /&amp;lt;keyword&amp;gt;)&lt;br /&gt;
 ? - search backward for occurance of keyword in a manpage, many editors and pagers (ex. ?&amp;lt;keyword&amp;gt;)&lt;br /&gt;
 n - continue to the next occurance of the keyword searches listed above (ex. n)&lt;br /&gt;
&lt;br /&gt;
'''Network'''&lt;br /&gt;
 ifconfig - configure a network interface (ex. ifconfig eth0 192.168.0.2)&lt;br /&gt;
 route - show / manipulate the IP routing table (ex. route add -net default gw 192.168.0.1)&lt;br /&gt;
 iwconfig - configure a wireless network interface (ex. iwconfig eth2 essid GaylesPerk channel 11 mode auto)&lt;br /&gt;
 iwlist - get more detailed wireless information from a wireless interface (ex. iwlist eth2 scan)&lt;br /&gt;
 ifup - bring a network interface up (ex. ifup eth0)&lt;br /&gt;
 ifdown - take a network interface down (ex. ifdown eth0)&lt;br /&gt;
&lt;br /&gt;
==Additional Useful Info You Should Learn==&lt;br /&gt;
&lt;br /&gt;
Note: These your should pursue in your own time using the commands listed above for additional information!&lt;br /&gt;
&lt;br /&gt;
 General: alias, free, jobs, fg, dmesg, uname, xargs&lt;br /&gt;
 Pattern Matching: grep, rgrep, egrep, fgrep&lt;br /&gt;
 Process: top, ps, pgrep, nice, renice, kill, pkill, killall&lt;br /&gt;
 Network: route, traceroute, arp, netstat, ping&lt;br /&gt;
 File and Filesystem: cp, mv, rm, ls, cd, chmod, chown, cat, du, df, lsof&lt;br /&gt;
 Conveniences: ssh-agent, keychains, screen&lt;br /&gt;
 Debian Package Manager: apt-get, dpkg, apt-cache, apt-file (Note: Debian based distribution specific)&lt;br /&gt;
 Files and File Locations: /etc/passwd, /etc/hosts, /etc/hosts.allow, /etc/hosts.deny, /etc/hostname, /etc/resolv.conf, /etc/groups,&lt;br /&gt;
                           /etc/fstab, /etc/modules, ~/.bashrc, ~/.bash_profile, ~/.bash_aliases&lt;/div&gt;</description>
			<pubDate>Wed, 13 Dec 2006 08:29:04 GMT</pubDate>			<dc:creator>Koopa</dc:creator>			<comments>http://72.14.177.54/SFVLUG/Talk:Pending</comments>		</item>
		<item>
			<title>Pending</title>
			<link>http://72.14.177.54/SFVLUG/Pending</link>
			<description>&lt;p&gt;Koopa:&amp;#32;/* Newbie Command line Essentials */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;''Under Construction!'' (recategorise, review, augment, and add descriptions after more sleep)&lt;br /&gt;
&lt;br /&gt;
==Newbie Command line Essentials==&lt;br /&gt;
&lt;br /&gt;
If you don't know your commandline very well at least know the tools that you have at your disposal to find the information and operate most efficiently. This section will contain only the entries that will enable you to maximize your productivity at the command line. &lt;br /&gt;
&lt;br /&gt;
Search and documentation tools are some of the most important tools you can learn on your box heres a brief list of a few of the most popular, all of which can be accessed through your terminal (xterm, rxvt, etc...) or console (&amp;lt;ctrl&amp;gt;&amp;lt;alt&amp;gt;F1...F6). Note: Commands in no particular order examples not applicable in all distributions or setups.&lt;br /&gt;
&lt;br /&gt;
'''Info'''&lt;br /&gt;
 man - an interface to the on-line reference manuals (ex: man hier)&lt;br /&gt;
 find - search the manual page names and descriptions (ex: find ~ -name '*.mp3')&lt;br /&gt;
 locate - security Enhanced version of the GNU Locate (ex: locate hosts)&lt;br /&gt;
 updatedb - update the slocate database (ex: updatedb&amp;amp;)&lt;br /&gt;
 which - locate a command (ex: which ifconfig)&lt;br /&gt;
 whereis - locate the binary, source, and manual page files for a command (ex. whereis ifconfig)&lt;br /&gt;
 hier - description of the file system hierarchy (ex. man hier)&lt;br /&gt;
 apropos - search the manual page names and descriptions (ex. apropos &amp;lt;keyword&amp;gt;)&lt;br /&gt;
 less - page through text one screenful at a time allowing for forward and backward movement in the file (ex. less&lt;br /&gt;
 /usr/share/doc/debian/debian-manifesto)&lt;br /&gt;
 su - change user ID or become super-user (ex. su - &amp;lt;passwd&amp;gt;)&lt;br /&gt;
 sudo - execute a command as another user (ex. sudo /etc/init.d/networking)&lt;br /&gt;
 history - display the list of commands previously typed (ex. history)&lt;br /&gt;
&lt;br /&gt;
'''Keystrokes'''&lt;br /&gt;
 &amp;lt;ctrl&amp;gt;r - reverse keyword search of the command history (ex. &amp;lt;ctrl&amp;gt;r&amp;lt;keyword&amp;gt;&lt;br /&gt;
 / - search forward for occurance of keyword in a manpage, many editors and pagers (ex. /&amp;lt;keyword&amp;gt;)&lt;br /&gt;
 ? - search backward for occurance of keyword in a manpage, many editors and pagers (ex. ?&amp;lt;keyword&amp;gt;)&lt;br /&gt;
 n - continue to the next occurance of the keyword searches listed above (ex. n)&lt;br /&gt;
&lt;br /&gt;
'''Network'''&lt;br /&gt;
 ifconfig - configure a network interface (ex. ifconfig eth0 192.168.0.2)&lt;br /&gt;
 route - show / manipulate the IP routing table (ex. route add -net default gw 192.168.0.1)&lt;br /&gt;
 iwconfig - configure a wireless network interface (ex. iwconfig eth2 essid GaylesPerk channel 11 mode auto)&lt;br /&gt;
 iwlist - get more detailed wireless information from a wireless interface (ex. iwlist eth2 scan)&lt;br /&gt;
 ifup - bring a network interface up (ex. ifup eth0)&lt;br /&gt;
 ifdown - take a network interface down (ex. ifdown eth0)&lt;br /&gt;
&lt;br /&gt;
==Additional Useful Commands==&lt;br /&gt;
&lt;br /&gt;
'''Search, Documentation and General Information Related Tools:'''&lt;br /&gt;
 alias&lt;br /&gt;
 du&lt;br /&gt;
 df&lt;br /&gt;
 free&lt;br /&gt;
 top&lt;br /&gt;
 lsof&lt;br /&gt;
 help  Display helpful information about the builtin commands&lt;br /&gt;
&lt;br /&gt;
'''Networking Information and Related Tools:'''&lt;br /&gt;
 hostname&lt;br /&gt;
 ping&lt;br /&gt;
 route&lt;br /&gt;
 traceroute&lt;br /&gt;
 arp&lt;br /&gt;
 netstat&lt;br /&gt;
&lt;br /&gt;
'''Files You Should Know Exist:'''&lt;br /&gt;
 passwd&lt;br /&gt;
 hosts&lt;br /&gt;
 hosts.allow&lt;br /&gt;
 hosts.deny&lt;br /&gt;
 hostname&lt;br /&gt;
 version&lt;br /&gt;
 resolv.conf&lt;br /&gt;
 groups&lt;br /&gt;
 .bash_profile&lt;br /&gt;
 .bashrc&lt;br /&gt;
 .bash_aliases&lt;br /&gt;
 fstab&lt;br /&gt;
 modules.conf&lt;br /&gt;
 dhclient.conf&lt;br /&gt;
&lt;br /&gt;
'''Paths You Should Know Exist:'''&lt;br /&gt;
Note: see man hier for general overview&lt;br /&gt;
&lt;br /&gt;
 /usr/share/doc&lt;br /&gt;
 /usr/local/doc&lt;br /&gt;
 /var/log&lt;br /&gt;
 /etc&lt;br /&gt;
 /etc/init.d&lt;br /&gt;
 /etc/alternatives&lt;br /&gt;
 &lt;br /&gt;
'''Conveniences:'''&lt;br /&gt;
 ssh-agent&lt;br /&gt;
 keychains&lt;br /&gt;
 screen&lt;br /&gt;
 &lt;br /&gt;
'''Basics:'''&lt;br /&gt;
 cp&lt;br /&gt;
 mv&lt;br /&gt;
 rm&lt;br /&gt;
 ls&lt;br /&gt;
 cd&lt;br /&gt;
 chmod&lt;br /&gt;
 chown&lt;br /&gt;
 cat&lt;br /&gt;
&lt;br /&gt;
'''Essential Keystrokes:'''&lt;br /&gt;
;&lt;br /&gt;
 ?&lt;br /&gt;
 *&lt;br /&gt;
 ~&lt;br /&gt;
 .&lt;br /&gt;
 ./&lt;br /&gt;
 |&lt;br /&gt;
 n&lt;br /&gt;
 &amp;lt;ctrl&amp;gt;r&lt;br /&gt;
 !      Start  a  history substitution, except when followed by a blank,&lt;br /&gt;
 !n&lt;br /&gt;
 !-n&lt;br /&gt;
 !!&lt;br /&gt;
 !string&lt;br /&gt;
 !?string/n&lt;br /&gt;
 less v&lt;br /&gt;
 &lt;br /&gt;
addme&lt;br /&gt;
 grep rgrep egrep fgrep&lt;br /&gt;
 xargs&lt;br /&gt;
 su &lt;br /&gt;
 sudo&lt;br /&gt;
 package manager commands just names not all the options better kept in a different nonessential ref&lt;/div&gt;</description>
			<pubDate>Wed, 13 Dec 2006 07:28:29 GMT</pubDate>			<dc:creator>Koopa</dc:creator>			<comments>http://72.14.177.54/SFVLUG/Talk:Pending</comments>		</item>
		<item>
			<title>Pending</title>
			<link>http://72.14.177.54/SFVLUG/Pending</link>
			<description>&lt;p&gt;Koopa:&amp;#32;/* Newbie Command line Essentials */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;''Under Construction!'' (recategorise, review, augment, and add descriptions after more sleep)&lt;br /&gt;
&lt;br /&gt;
==Newbie Command line Essentials==&lt;br /&gt;
&lt;br /&gt;
If you don't know your commandline very well at least know the tools that you have at your disposal to find the information and operate most efficiently. This section will contain only the entries that will enable you to maximize your productivity at the command line. &lt;br /&gt;
&lt;br /&gt;
Search and documentation tools are some of the most important tools you can learn on your box heres a brief list of a few of the most popular, all of which can be accessed through your terminal (xterm, rxvt, etc...) or console (&amp;lt;ctrl&amp;gt;&amp;lt;alt&amp;gt;F1...F6).&lt;br /&gt;
&lt;br /&gt;
 man - an interface to the on-line reference manuals (ex: man hier)&lt;br /&gt;
 find - search the manual page names and descriptions (ex: find ~ -name '*.mp3')&lt;br /&gt;
 locate - security Enhanced version of the GNU Locate (ex: locate hosts)&lt;br /&gt;
 updatedb - update the slocate database (ex: updatedb&amp;amp;)&lt;br /&gt;
 which - locate a command (ex: which ifconfig)&lt;br /&gt;
 whereis - locate the binary, source, and manual page files for a command (ex. whereis ifconfig)&lt;br /&gt;
 hier - description of the file system hierarchy (ex. man hier)&lt;br /&gt;
 apropos - search the manual page names and descriptions (ex. apropos &amp;lt;keyword&amp;gt;)&lt;br /&gt;
 less - page through text one screenful at a time allowing for forward and backward movement in the file (ex. less /usr/share/doc/debian/debian-manifesto)&lt;br /&gt;
 su - change user ID or become super-user (ex. su - &amp;lt;passwd&amp;gt;)&lt;br /&gt;
 sudo - execute a command as another user (ex. sudo /etc/init.d/networking)&lt;br /&gt;
&lt;br /&gt;
 history - display the list of commands previously typed (ex. history)&lt;br /&gt;
 &amp;lt;ctrl&amp;gt;r&lt;br /&gt;
 &lt;br /&gt;
 / - search forward for occurance of keyword in a manpage, many editors and pagers (ex. /&amp;lt;keyword&amp;gt;)&lt;br /&gt;
 ? - search backward for occurance of keyword in a manpage, many editors and pagers (ex. ?&amp;lt;keyword&amp;gt;)&lt;br /&gt;
 n - continue to the next occurance of the keyword searches listed above (ex. n)&lt;br /&gt;
&lt;br /&gt;
'''The basic command line essentials needed to bring up a network interface to connect to the internet'''&lt;br /&gt;
 ifconfig - configure a network interface (ex. ifconfig eth0 192.168.0.2)&lt;br /&gt;
 route - show / manipulate the IP routing table (ex. route add -net default gw 192.168.0.1)&lt;br /&gt;
 iwconfig - configure a wireless network interface (ex. iwconfig eth2 essid GaylesPerk channel 11 mode auto)&lt;br /&gt;
 iwlist - get more detailed wireless information from a wireless interface (ex. iwlist eth2 scan)&lt;br /&gt;
 ifup - bring a network interface up (ex. ifup eth0)&lt;br /&gt;
 ifdown - take a network interface down (ex. ifdown eth0)&lt;br /&gt;
&lt;br /&gt;
==Additional Useful Commands==&lt;br /&gt;
&lt;br /&gt;
'''Search, Documentation and General Information Related Tools:'''&lt;br /&gt;
 alias&lt;br /&gt;
 du&lt;br /&gt;
 df&lt;br /&gt;
 free&lt;br /&gt;
 top&lt;br /&gt;
 lsof&lt;br /&gt;
 help  Display helpful information about the builtin commands&lt;br /&gt;
&lt;br /&gt;
'''Networking Information and Related Tools:'''&lt;br /&gt;
 hostname&lt;br /&gt;
 ping&lt;br /&gt;
 route&lt;br /&gt;
 traceroute&lt;br /&gt;
 arp&lt;br /&gt;
 netstat&lt;br /&gt;
&lt;br /&gt;
'''Files You Should Know Exist:'''&lt;br /&gt;
 passwd&lt;br /&gt;
 hosts&lt;br /&gt;
 hosts.allow&lt;br /&gt;
 hosts.deny&lt;br /&gt;
 hostname&lt;br /&gt;
 version&lt;br /&gt;
 resolv.conf&lt;br /&gt;
 groups&lt;br /&gt;
 .bash_profile&lt;br /&gt;
 .bashrc&lt;br /&gt;
 .bash_aliases&lt;br /&gt;
 fstab&lt;br /&gt;
 modules.conf&lt;br /&gt;
 dhclient.conf&lt;br /&gt;
&lt;br /&gt;
'''Paths You Should Know Exist:'''&lt;br /&gt;
Note: see man hier for general overview&lt;br /&gt;
&lt;br /&gt;
 /usr/share/doc&lt;br /&gt;
 /usr/local/doc&lt;br /&gt;
 /var/log&lt;br /&gt;
 /etc&lt;br /&gt;
 /etc/init.d&lt;br /&gt;
 /etc/alternatives&lt;br /&gt;
 &lt;br /&gt;
'''Conveniences:'''&lt;br /&gt;
 ssh-agent&lt;br /&gt;
 keychains&lt;br /&gt;
 screen&lt;br /&gt;
 &lt;br /&gt;
'''Basics:'''&lt;br /&gt;
 cp&lt;br /&gt;
 mv&lt;br /&gt;
 rm&lt;br /&gt;
 ls&lt;br /&gt;
 cd&lt;br /&gt;
 chmod&lt;br /&gt;
 chown&lt;br /&gt;
 cat&lt;br /&gt;
&lt;br /&gt;
'''Essential Keystrokes:'''&lt;br /&gt;
;&lt;br /&gt;
 ?&lt;br /&gt;
 *&lt;br /&gt;
 ~&lt;br /&gt;
 .&lt;br /&gt;
 ./&lt;br /&gt;
 |&lt;br /&gt;
 n&lt;br /&gt;
 &amp;lt;ctrl&amp;gt;r&lt;br /&gt;
 !      Start  a  history substitution, except when followed by a blank,&lt;br /&gt;
 !n&lt;br /&gt;
 !-n&lt;br /&gt;
 !!&lt;br /&gt;
 !string&lt;br /&gt;
 !?string/n&lt;br /&gt;
 less v&lt;br /&gt;
 &lt;br /&gt;
addme&lt;br /&gt;
 grep rgrep egrep fgrep&lt;br /&gt;
 xargs&lt;br /&gt;
 su &lt;br /&gt;
 sudo&lt;br /&gt;
 package manager commands just names not all the options better kept in a different nonessential ref&lt;/div&gt;</description>
			<pubDate>Wed, 13 Dec 2006 07:19:38 GMT</pubDate>			<dc:creator>Koopa</dc:creator>			<comments>http://72.14.177.54/SFVLUG/Talk:Pending</comments>		</item>
		<item>
			<title>Pending</title>
			<link>http://72.14.177.54/SFVLUG/Pending</link>
			<description>&lt;p&gt;Koopa:&amp;#32;/* Additional Useful Commands */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;''Under Construction!'' (recategorise, review, augment, and add descriptions after more sleep)&lt;br /&gt;
&lt;br /&gt;
==Newbie Command line Essentials==&lt;br /&gt;
&lt;br /&gt;
If you don't know your commandline very well at least know the tools that you have at your disposal to find the information and operate most efficiently. This section will contain only the entries that will enable you to maximize your productivity at the command line. &lt;br /&gt;
&lt;br /&gt;
Search and documentation tools are some of the most important tools you can learn on your box heres a brief list of a few of the most popular, all of which can be accessed through your terminal (xterm, rxvt, etc...) or console (&amp;lt;ctrl&amp;gt;&amp;lt;alt&amp;gt;F1...F6).&lt;br /&gt;
&lt;br /&gt;
hrm maybe I should restructure with a few examples of each for this part&lt;br /&gt;
&lt;br /&gt;
''' Search, Documentation and General Information Essential Tools:'''&lt;br /&gt;
 man - an interface to the on-line reference manuals (usage: man &amp;lt;manual page&amp;gt;)&lt;br /&gt;
 find - search the manual page names and descriptions (usage: find &amp;lt;path&amp;gt; -name &amp;lt;pattern&amp;gt;)&lt;br /&gt;
 locate - Security Enhanced version of the GNU Locate (usage:)&lt;br /&gt;
 updatedb - update the slocate database&lt;br /&gt;
 which - locate a command&lt;br /&gt;
 whereis - locate the binary, source, and manual page files for a command&lt;br /&gt;
 hier - Description of the file system hierarchy&lt;br /&gt;
 apropos - search the manual page names and descriptions&lt;br /&gt;
 history -&lt;br /&gt;
 &amp;lt;ctrl&amp;gt;r&lt;br /&gt;
;&lt;br /&gt;
 *&lt;br /&gt;
 n&lt;br /&gt;
 less&lt;br /&gt;
&lt;br /&gt;
'''Networking Information and Related Essential Tools:'''&lt;br /&gt;
 ifconfig - configure a network interface&lt;br /&gt;
 route - show / manipulate the IP routing table&lt;br /&gt;
 iwconfig - configure a wireless network interface&lt;br /&gt;
 iwlist - Get more detailed wireless information from a wireless interface&lt;br /&gt;
 ifup - bring a network interface up&lt;br /&gt;
 ifdown - take a network interface down&lt;br /&gt;
&lt;br /&gt;
==Additional Useful Commands==&lt;br /&gt;
&lt;br /&gt;
'''Search, Documentation and General Information Related Tools:'''&lt;br /&gt;
 alias&lt;br /&gt;
 du&lt;br /&gt;
 df&lt;br /&gt;
 free&lt;br /&gt;
 top&lt;br /&gt;
 lsof&lt;br /&gt;
 help  Display helpful information about the builtin commands&lt;br /&gt;
&lt;br /&gt;
'''Networking Information and Related Tools:'''&lt;br /&gt;
 hostname&lt;br /&gt;
 ping&lt;br /&gt;
 route&lt;br /&gt;
 traceroute&lt;br /&gt;
 arp&lt;br /&gt;
 netstat&lt;br /&gt;
&lt;br /&gt;
'''Files You Should Know Exist:'''&lt;br /&gt;
 passwd&lt;br /&gt;
 hosts&lt;br /&gt;
 hosts.allow&lt;br /&gt;
 hosts.deny&lt;br /&gt;
 hostname&lt;br /&gt;
 version&lt;br /&gt;
 resolv.conf&lt;br /&gt;
 groups&lt;br /&gt;
 .bash_profile&lt;br /&gt;
 .bashrc&lt;br /&gt;
 .bash_aliases&lt;br /&gt;
 fstab&lt;br /&gt;
 modules.conf&lt;br /&gt;
 dhclient.conf&lt;br /&gt;
&lt;br /&gt;
'''Paths You Should Know Exist:'''&lt;br /&gt;
Note: see man hier for general overview&lt;br /&gt;
&lt;br /&gt;
 /usr/share/doc&lt;br /&gt;
 /usr/local/doc&lt;br /&gt;
 /var/log&lt;br /&gt;
 /etc&lt;br /&gt;
 /etc/init.d&lt;br /&gt;
 /etc/alternatives&lt;br /&gt;
 &lt;br /&gt;
'''Conveniences:'''&lt;br /&gt;
 ssh-agent&lt;br /&gt;
 keychains&lt;br /&gt;
 screen&lt;br /&gt;
 &lt;br /&gt;
'''Basics:'''&lt;br /&gt;
 cp&lt;br /&gt;
 mv&lt;br /&gt;
 rm&lt;br /&gt;
 ls&lt;br /&gt;
 cd&lt;br /&gt;
 chmod&lt;br /&gt;
 chown&lt;br /&gt;
 cat&lt;br /&gt;
&lt;br /&gt;
'''Essential Keystrokes:'''&lt;br /&gt;
;&lt;br /&gt;
 ?&lt;br /&gt;
 *&lt;br /&gt;
 ~&lt;br /&gt;
 .&lt;br /&gt;
 ./&lt;br /&gt;
 |&lt;br /&gt;
 n&lt;br /&gt;
 &amp;lt;ctrl&amp;gt;r&lt;br /&gt;
 !      Start  a  history substitution, except when followed by a blank,&lt;br /&gt;
 !n&lt;br /&gt;
 !-n&lt;br /&gt;
 !!&lt;br /&gt;
 !string&lt;br /&gt;
 !?string/n&lt;br /&gt;
 less v&lt;br /&gt;
 &lt;br /&gt;
addme&lt;br /&gt;
 grep rgrep egrep fgrep&lt;br /&gt;
 xargs&lt;br /&gt;
 su &lt;br /&gt;
 sudo&lt;br /&gt;
 package manager commands just names not all the options better kept in a different nonessential ref&lt;/div&gt;</description>
			<pubDate>Wed, 13 Dec 2006 06:55:42 GMT</pubDate>			<dc:creator>Koopa</dc:creator>			<comments>http://72.14.177.54/SFVLUG/Talk:Pending</comments>		</item>
		<item>
			<title>Pending</title>
			<link>http://72.14.177.54/SFVLUG/Pending</link>
			<description>&lt;p&gt;Koopa:&amp;#32;/* Newbie Command line Essentials */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;''Under Construction!'' (recategorise, review, augment, and add descriptions after more sleep)&lt;br /&gt;
&lt;br /&gt;
==Newbie Command line Essentials==&lt;br /&gt;
&lt;br /&gt;
If you don't know your commandline very well at least know the tools that you have at your disposal to find the information and operate most efficiently. This section will contain only the entries that will enable you to maximize your productivity at the command line. &lt;br /&gt;
&lt;br /&gt;
Search and documentation tools are some of the most important tools you can learn on your box heres a brief list of a few of the most popular, all of which can be accessed through your terminal (xterm, rxvt, etc...) or console (&amp;lt;ctrl&amp;gt;&amp;lt;alt&amp;gt;F1...F6).&lt;br /&gt;
&lt;br /&gt;
hrm maybe I should restructure with a few examples of each for this part&lt;br /&gt;
&lt;br /&gt;
''' Search, Documentation and General Information Essential Tools:'''&lt;br /&gt;
 man - an interface to the on-line reference manuals (usage: man &amp;lt;manual page&amp;gt;)&lt;br /&gt;
 find - search the manual page names and descriptions (usage: find &amp;lt;path&amp;gt; -name &amp;lt;pattern&amp;gt;)&lt;br /&gt;
 locate - Security Enhanced version of the GNU Locate (usage:)&lt;br /&gt;
 updatedb - update the slocate database&lt;br /&gt;
 which - locate a command&lt;br /&gt;
 whereis - locate the binary, source, and manual page files for a command&lt;br /&gt;
 hier - Description of the file system hierarchy&lt;br /&gt;
 apropos - search the manual page names and descriptions&lt;br /&gt;
 history -&lt;br /&gt;
 &amp;lt;ctrl&amp;gt;r&lt;br /&gt;
;&lt;br /&gt;
 *&lt;br /&gt;
 n&lt;br /&gt;
 less&lt;br /&gt;
&lt;br /&gt;
'''Networking Information and Related Essential Tools:'''&lt;br /&gt;
 ifconfig - configure a network interface&lt;br /&gt;
 route - show / manipulate the IP routing table&lt;br /&gt;
 iwconfig - configure a wireless network interface&lt;br /&gt;
 iwlist - Get more detailed wireless information from a wireless interface&lt;br /&gt;
 ifup - bring a network interface up&lt;br /&gt;
 ifdown - take a network interface down&lt;br /&gt;
&lt;br /&gt;
==Additional Useful Commands==&lt;br /&gt;
&lt;br /&gt;
'''Search, Documentation and General Information Related Tools:'''&lt;br /&gt;
 bash - GNU Bourne-Again SHell&lt;br /&gt;
 alias&lt;br /&gt;
 less&lt;br /&gt;
 more&lt;br /&gt;
 du&lt;br /&gt;
 df&lt;br /&gt;
 free&lt;br /&gt;
 top&lt;br /&gt;
 lsof&lt;br /&gt;
 help  Display helpful information about the builtin commands&lt;br /&gt;
&lt;br /&gt;
'''Networking Information and Related Tools:'''&lt;br /&gt;
 hostname&lt;br /&gt;
 ping&lt;br /&gt;
 route&lt;br /&gt;
 traceroute&lt;br /&gt;
 arp&lt;br /&gt;
 ifup/down&lt;br /&gt;
 ifconfig&lt;br /&gt;
 iwconfig&lt;br /&gt;
 iwlist&lt;br /&gt;
 netstat&lt;br /&gt;
&lt;br /&gt;
'''Files You Should Know Exist:'''&lt;br /&gt;
 passwd&lt;br /&gt;
 hosts&lt;br /&gt;
 hosts.allow&lt;br /&gt;
 hosts.deny&lt;br /&gt;
 hostname&lt;br /&gt;
 version&lt;br /&gt;
 resolv.conf&lt;br /&gt;
 groups&lt;br /&gt;
 .bash_profile&lt;br /&gt;
 .bashrc&lt;br /&gt;
 .bash_aliases&lt;br /&gt;
 fstab&lt;br /&gt;
 modules.conf&lt;br /&gt;
 dhclient.conf&lt;br /&gt;
&lt;br /&gt;
'''Paths You Should Know Exist:'''&lt;br /&gt;
Note: see man hier for general overview&lt;br /&gt;
&lt;br /&gt;
 /usr/share/doc&lt;br /&gt;
 /usr/local/doc&lt;br /&gt;
 /var/log&lt;br /&gt;
 /etc&lt;br /&gt;
 /etc/init.d&lt;br /&gt;
 /etc/alternatives&lt;br /&gt;
 &lt;br /&gt;
'''Conveniences:'''&lt;br /&gt;
 history&lt;br /&gt;
 ssh-agent&lt;br /&gt;
 keychains&lt;br /&gt;
 screen&lt;br /&gt;
 &lt;br /&gt;
'''Basics:'''&lt;br /&gt;
 cp&lt;br /&gt;
 mv&lt;br /&gt;
 rm&lt;br /&gt;
 ls&lt;br /&gt;
 cd&lt;br /&gt;
 chmod&lt;br /&gt;
 chown&lt;br /&gt;
 cat&lt;br /&gt;
&lt;br /&gt;
'''Essential Keystrokes:'''&lt;br /&gt;
;&lt;br /&gt;
 ?&lt;br /&gt;
 *&lt;br /&gt;
 ~&lt;br /&gt;
 .&lt;br /&gt;
 ./&lt;br /&gt;
 |&lt;br /&gt;
 n&lt;br /&gt;
 &amp;lt;ctrl&amp;gt;r&lt;br /&gt;
 !      Start  a  history substitution, except when followed by a blank,&lt;br /&gt;
 !n&lt;br /&gt;
 !-n&lt;br /&gt;
 !!&lt;br /&gt;
 !string&lt;br /&gt;
 !?string/n&lt;br /&gt;
 less v&lt;br /&gt;
 &lt;br /&gt;
addme&lt;br /&gt;
 grep rgrep egrep fgrep&lt;br /&gt;
 xargs&lt;br /&gt;
 su &lt;br /&gt;
 sudo&lt;br /&gt;
 package manager commands just names not all the options better kept in a different nonessential ref&lt;/div&gt;</description>
			<pubDate>Wed, 13 Dec 2006 06:53:42 GMT</pubDate>			<dc:creator>Koopa</dc:creator>			<comments>http://72.14.177.54/SFVLUG/Talk:Pending</comments>		</item>
		<item>
			<title>Pending</title>
			<link>http://72.14.177.54/SFVLUG/Pending</link>
			<description>&lt;p&gt;Koopa:&amp;#32;/* Newbie Command line Essentials */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;''Under Construction!'' (recategorise, review, augment, and add descriptions after more sleep)&lt;br /&gt;
&lt;br /&gt;
==Newbie Command line Essentials==&lt;br /&gt;
&lt;br /&gt;
If you don't know your commandline very well at least know the tools that you have at your disposal to find the information and operate most efficiently. This section will contain only the entries that will enable you to maximize your productivity at the command line. &lt;br /&gt;
&lt;br /&gt;
Search and documentation tools are some of the most important tools you can learn on your box heres a brief list of a few of the most popular, all of which can be accessed through your terminal (xterm, rxvt, etc...) or console (&amp;lt;ctrl&amp;gt;&amp;lt;alt&amp;gt;F1...F6).&lt;br /&gt;
&lt;br /&gt;
''' Search, Documentation and General Information Essential Tools:'''&lt;br /&gt;
 man - an interface to the on-line reference manuals (usage: man &amp;lt;manual page&amp;gt;)&lt;br /&gt;
 find - search the manual page names and descriptions (usage: find &amp;lt;path&amp;gt; -name &amp;lt;pattern&amp;gt;)&lt;br /&gt;
 locate - Security Enhanced version of the GNU Locate (usage:)&lt;br /&gt;
 updatedb - update the slocate database&lt;br /&gt;
 which - locate a command&lt;br /&gt;
 whereis - locate the binary, source, and manual page files for a command&lt;br /&gt;
 hier - Description of the file system hierarchy&lt;br /&gt;
 apropos - search the manual page names and descriptions&lt;br /&gt;
&lt;br /&gt;
'''Networking Information and Related Essential Tools:'''&lt;br /&gt;
 ifconfig - configure a network interface&lt;br /&gt;
 route - show / manipulate the IP routing table&lt;br /&gt;
 iwconfig - configure a wireless network interface&lt;br /&gt;
 iwlist - Get more detailed wireless information from a wireless interface&lt;br /&gt;
 ifup - bring a network interface up&lt;br /&gt;
 ifdown - take a network interface down&lt;br /&gt;
&lt;br /&gt;
==Additional Useful Commands==&lt;br /&gt;
&lt;br /&gt;
'''Search, Documentation and General Information Related Tools:'''&lt;br /&gt;
 bash - GNU Bourne-Again SHell&lt;br /&gt;
 alias&lt;br /&gt;
 less&lt;br /&gt;
 more&lt;br /&gt;
 du&lt;br /&gt;
 df&lt;br /&gt;
 free&lt;br /&gt;
 top&lt;br /&gt;
 lsof&lt;br /&gt;
 help  Display helpful information about the builtin commands&lt;br /&gt;
&lt;br /&gt;
'''Networking Information and Related Tools:'''&lt;br /&gt;
 hostname&lt;br /&gt;
 ping&lt;br /&gt;
 route&lt;br /&gt;
 traceroute&lt;br /&gt;
 arp&lt;br /&gt;
 ifup/down&lt;br /&gt;
 ifconfig&lt;br /&gt;
 iwconfig&lt;br /&gt;
 iwlist&lt;br /&gt;
 netstat&lt;br /&gt;
&lt;br /&gt;
'''Files You Should Know Exist:'''&lt;br /&gt;
 passwd&lt;br /&gt;
 hosts&lt;br /&gt;
 hosts.allow&lt;br /&gt;
 hosts.deny&lt;br /&gt;
 hostname&lt;br /&gt;
 version&lt;br /&gt;
 resolv.conf&lt;br /&gt;
 groups&lt;br /&gt;
 .bash_profile&lt;br /&gt;
 .bashrc&lt;br /&gt;
 .bash_aliases&lt;br /&gt;
 fstab&lt;br /&gt;
 modules.conf&lt;br /&gt;
 dhclient.conf&lt;br /&gt;
&lt;br /&gt;
'''Paths You Should Know Exist:'''&lt;br /&gt;
Note: see man hier for general overview&lt;br /&gt;
&lt;br /&gt;
 /usr/share/doc&lt;br /&gt;
 /usr/local/doc&lt;br /&gt;
 /var/log&lt;br /&gt;
 /etc&lt;br /&gt;
 /etc/init.d&lt;br /&gt;
 /etc/alternatives&lt;br /&gt;
 &lt;br /&gt;
'''Conveniences:'''&lt;br /&gt;
 history&lt;br /&gt;
 ssh-agent&lt;br /&gt;
 keychains&lt;br /&gt;
 screen&lt;br /&gt;
 &lt;br /&gt;
'''Basics:'''&lt;br /&gt;
 cp&lt;br /&gt;
 mv&lt;br /&gt;
 rm&lt;br /&gt;
 ls&lt;br /&gt;
 cd&lt;br /&gt;
 chmod&lt;br /&gt;
 chown&lt;br /&gt;
 cat&lt;br /&gt;
&lt;br /&gt;
'''Essential Keystrokes:'''&lt;br /&gt;
;&lt;br /&gt;
 ?&lt;br /&gt;
 *&lt;br /&gt;
 ~&lt;br /&gt;
 .&lt;br /&gt;
 ./&lt;br /&gt;
 |&lt;br /&gt;
 n&lt;br /&gt;
 &amp;lt;ctrl&amp;gt;r&lt;br /&gt;
 !      Start  a  history substitution, except when followed by a blank,&lt;br /&gt;
 !n&lt;br /&gt;
 !-n&lt;br /&gt;
 !!&lt;br /&gt;
 !string&lt;br /&gt;
 !?string/n&lt;br /&gt;
 less v&lt;br /&gt;
 &lt;br /&gt;
addme&lt;br /&gt;
 grep rgrep egrep fgrep&lt;br /&gt;
 xargs&lt;br /&gt;
 su &lt;br /&gt;
 sudo&lt;br /&gt;
 package manager commands just names not all the options better kept in a different nonessential ref&lt;/div&gt;</description>
			<pubDate>Wed, 13 Dec 2006 06:51:53 GMT</pubDate>			<dc:creator>Koopa</dc:creator>			<comments>http://72.14.177.54/SFVLUG/Talk:Pending</comments>		</item>
		<item>
			<title>Pending</title>
			<link>http://72.14.177.54/SFVLUG/Pending</link>
			<description>&lt;p&gt;Koopa:&amp;#32;/* Newbie Command line Essentials */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;''Under Construction!'' (recategorise, review, augment, and add descriptions after more sleep)&lt;br /&gt;
&lt;br /&gt;
==Newbie Command line Essentials==&lt;br /&gt;
&lt;br /&gt;
If you don't know your commandline very well at least know the tools that you have at your disposal to find the information and operate most efficiently. This section will contain only the entries that will enable you to maximize your productivity at the command line. &lt;br /&gt;
&lt;br /&gt;
Search and documentation tools are some of the most important tools you can learn on your box heres a brief list of a few of the most popular, all of which can be accessed through your terminal (xterm, rxvt, etc...) or console (&amp;lt;ctrl&amp;gt;&amp;lt;alt&amp;gt;F1...F6).&lt;br /&gt;
&lt;br /&gt;
''' Search, Documentation and General Information Essential Tools:'''&lt;br /&gt;
 man - an interface to the on-line reference manuals&lt;br /&gt;
 find - search the manual page names and descriptionsq&lt;br /&gt;
 locate - Security Enhanced version of the GNU Locate&lt;br /&gt;
 updatedb - update the slocate database&lt;br /&gt;
 which - locate a command&lt;br /&gt;
 whereis - locate the binary, source, and manual page files for a command&lt;br /&gt;
 hier - Description of the file system hierarchy&lt;br /&gt;
 apropos - search the manual page names and descriptions&lt;br /&gt;
&lt;br /&gt;
'''Networking Information and Related Essential Tools:'''&lt;br /&gt;
 ifconfig - configure a network interface&lt;br /&gt;
 route - show / manipulate the IP routing table&lt;br /&gt;
 iwconfig - configure a wireless network interface&lt;br /&gt;
 iwlist - Get more detailed wireless information from a wireless interface&lt;br /&gt;
 ifup - bring a network interface up&lt;br /&gt;
 ifdown - take a network interface down&lt;br /&gt;
&lt;br /&gt;
==Additional Useful Commands==&lt;br /&gt;
&lt;br /&gt;
'''Search, Documentation and General Information Related Tools:'''&lt;br /&gt;
 bash - GNU Bourne-Again SHell&lt;br /&gt;
 alias&lt;br /&gt;
 less&lt;br /&gt;
 more&lt;br /&gt;
 du&lt;br /&gt;
 df&lt;br /&gt;
 free&lt;br /&gt;
 top&lt;br /&gt;
 lsof&lt;br /&gt;
 help  Display helpful information about the builtin commands&lt;br /&gt;
&lt;br /&gt;
'''Networking Information and Related Tools:'''&lt;br /&gt;
 hostname&lt;br /&gt;
 ping&lt;br /&gt;
 route&lt;br /&gt;
 traceroute&lt;br /&gt;
 arp&lt;br /&gt;
 ifup/down&lt;br /&gt;
 ifconfig&lt;br /&gt;
 iwconfig&lt;br /&gt;
 iwlist&lt;br /&gt;
 netstat&lt;br /&gt;
&lt;br /&gt;
'''Files You Should Know Exist:'''&lt;br /&gt;
 passwd&lt;br /&gt;
 hosts&lt;br /&gt;
 hosts.allow&lt;br /&gt;
 hosts.deny&lt;br /&gt;
 hostname&lt;br /&gt;
 version&lt;br /&gt;
 resolv.conf&lt;br /&gt;
 groups&lt;br /&gt;
 .bash_profile&lt;br /&gt;
 .bashrc&lt;br /&gt;
 .bash_aliases&lt;br /&gt;
 fstab&lt;br /&gt;
 modules.conf&lt;br /&gt;
 dhclient.conf&lt;br /&gt;
&lt;br /&gt;
'''Paths You Should Know Exist:'''&lt;br /&gt;
Note: see man hier for general overview&lt;br /&gt;
&lt;br /&gt;
 /usr/share/doc&lt;br /&gt;
 /usr/local/doc&lt;br /&gt;
 /var/log&lt;br /&gt;
 /etc&lt;br /&gt;
 /etc/init.d&lt;br /&gt;
 /etc/alternatives&lt;br /&gt;
 &lt;br /&gt;
'''Conveniences:'''&lt;br /&gt;
 history&lt;br /&gt;
 ssh-agent&lt;br /&gt;
 keychains&lt;br /&gt;
 screen&lt;br /&gt;
 &lt;br /&gt;
'''Basics:'''&lt;br /&gt;
 cp&lt;br /&gt;
 mv&lt;br /&gt;
 rm&lt;br /&gt;
 ls&lt;br /&gt;
 cd&lt;br /&gt;
 chmod&lt;br /&gt;
 chown&lt;br /&gt;
 cat&lt;br /&gt;
&lt;br /&gt;
'''Essential Keystrokes:'''&lt;br /&gt;
;&lt;br /&gt;
 ?&lt;br /&gt;
 *&lt;br /&gt;
 ~&lt;br /&gt;
 .&lt;br /&gt;
 ./&lt;br /&gt;
 |&lt;br /&gt;
 n&lt;br /&gt;
 &amp;lt;ctrl&amp;gt;r&lt;br /&gt;
 !      Start  a  history substitution, except when followed by a blank,&lt;br /&gt;
 !n&lt;br /&gt;
 !-n&lt;br /&gt;
 !!&lt;br /&gt;
 !string&lt;br /&gt;
 !?string/n&lt;br /&gt;
 less v&lt;br /&gt;
 &lt;br /&gt;
addme&lt;br /&gt;
 grep rgrep egrep fgrep&lt;br /&gt;
 xargs&lt;br /&gt;
 su &lt;br /&gt;
 sudo&lt;br /&gt;
 package manager commands just names not all the options better kept in a different nonessential ref&lt;/div&gt;</description>
			<pubDate>Wed, 13 Dec 2006 06:45:52 GMT</pubDate>			<dc:creator>Koopa</dc:creator>			<comments>http://72.14.177.54/SFVLUG/Talk:Pending</comments>		</item>
		<item>
			<title>Pending</title>
			<link>http://72.14.177.54/SFVLUG/Pending</link>
			<description>&lt;p&gt;Koopa:&amp;#32;/* Newbie Commandline Essentials */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;''Under Construction!'' (recategorise, review, augment, and add descriptions after more sleep)&lt;br /&gt;
&lt;br /&gt;
==Newbie Command line Essentials==&lt;br /&gt;
&lt;br /&gt;
If you don't know your commandline very well at least know the tools that you have at your disposal to find the information and operate most efficiently. This section will contain only the entries that will enable you to maximize your productivity at the command line. &lt;br /&gt;
&lt;br /&gt;
Search and documentation tools are some of the most important tools you can learn on your box heres a brief list of a few of the most popular, all of which can be accessed through your terminal (xterm, rxvt, etc...) or console (&amp;lt;ctrl&amp;gt;&amp;lt;alt&amp;gt;F1...F6).&lt;br /&gt;
&lt;br /&gt;
'''Search, Documentation and General Information Essential Tools:'''&lt;br /&gt;
 man - an interface to the on-line reference manuals&lt;br /&gt;
 find - search the manual page names and descriptionsq&lt;br /&gt;
 locate - Security Enhanced version of the GNU Locate&lt;br /&gt;
 updatedb - update the slocate database&lt;br /&gt;
 which - locate a command&lt;br /&gt;
 whereis - locate the binary, source, and manual page files for a command&lt;br /&gt;
 hier - Description of the file system hierarchy&lt;br /&gt;
 apropos - &lt;br /&gt;
&lt;br /&gt;
'''Networking Information and Related Essential Tools:'''&lt;br /&gt;
 ifconfig&lt;br /&gt;
 route&lt;br /&gt;
 iwconfig&lt;br /&gt;
 ifup&lt;br /&gt;
 ifdown&lt;br /&gt;
&lt;br /&gt;
==Additional Useful Commands==&lt;br /&gt;
&lt;br /&gt;
'''Search, Documentation and General Information Related Tools:'''&lt;br /&gt;
 bash - GNU Bourne-Again SHell&lt;br /&gt;
 alias&lt;br /&gt;
 less&lt;br /&gt;
 more&lt;br /&gt;
 du&lt;br /&gt;
 df&lt;br /&gt;
 free&lt;br /&gt;
 top&lt;br /&gt;
 lsof&lt;br /&gt;
 help  Display helpful information about the builtin commands&lt;br /&gt;
&lt;br /&gt;
'''Networking Information and Related Tools:'''&lt;br /&gt;
 hostname&lt;br /&gt;
 ping&lt;br /&gt;
 route&lt;br /&gt;
 traceroute&lt;br /&gt;
 arp&lt;br /&gt;
 ifup/down&lt;br /&gt;
 ifconfig&lt;br /&gt;
 iwconfig&lt;br /&gt;
 iwlist&lt;br /&gt;
 netstat&lt;br /&gt;
&lt;br /&gt;
'''Files You Should Know Exist:'''&lt;br /&gt;
 passwd&lt;br /&gt;
 hosts&lt;br /&gt;
 hosts.allow&lt;br /&gt;
 hosts.deny&lt;br /&gt;
 hostname&lt;br /&gt;
 version&lt;br /&gt;
 resolv.conf&lt;br /&gt;
 groups&lt;br /&gt;
 .bash_profile&lt;br /&gt;
 .bashrc&lt;br /&gt;
 .bash_aliases&lt;br /&gt;
 fstab&lt;br /&gt;
 modules.conf&lt;br /&gt;
 dhclient.conf&lt;br /&gt;
&lt;br /&gt;
'''Paths You Should Know Exist:'''&lt;br /&gt;
Note: see man hier for general overview&lt;br /&gt;
&lt;br /&gt;
 /usr/share/doc&lt;br /&gt;
 /usr/local/doc&lt;br /&gt;
 /var/log&lt;br /&gt;
 /etc&lt;br /&gt;
 /etc/init.d&lt;br /&gt;
 /etc/alternatives&lt;br /&gt;
 &lt;br /&gt;
'''Conveniences:'''&lt;br /&gt;
 history&lt;br /&gt;
 ssh-agent&lt;br /&gt;
 keychains&lt;br /&gt;
 screen&lt;br /&gt;
 &lt;br /&gt;
'''Basics:'''&lt;br /&gt;
 cp&lt;br /&gt;
 mv&lt;br /&gt;
 rm&lt;br /&gt;
 ls&lt;br /&gt;
 cd&lt;br /&gt;
 chmod&lt;br /&gt;
 chown&lt;br /&gt;
 cat&lt;br /&gt;
&lt;br /&gt;
'''Essential Keystrokes:'''&lt;br /&gt;
;&lt;br /&gt;
 ?&lt;br /&gt;
 *&lt;br /&gt;
 ~&lt;br /&gt;
 .&lt;br /&gt;
 ./&lt;br /&gt;
 |&lt;br /&gt;
 n&lt;br /&gt;
 &amp;lt;ctrl&amp;gt;r&lt;br /&gt;
 !      Start  a  history substitution, except when followed by a blank,&lt;br /&gt;
 !n&lt;br /&gt;
 !-n&lt;br /&gt;
 !!&lt;br /&gt;
 !string&lt;br /&gt;
 !?string/n&lt;br /&gt;
 less v&lt;br /&gt;
 &lt;br /&gt;
addme&lt;br /&gt;
 grep rgrep egrep fgrep&lt;br /&gt;
 xargs&lt;br /&gt;
 su &lt;br /&gt;
 sudo&lt;br /&gt;
 package manager commands just names not all the options better kept in a different nonessential ref&lt;/div&gt;</description>
			<pubDate>Wed, 13 Dec 2006 06:35:05 GMT</pubDate>			<dc:creator>Koopa</dc:creator>			<comments>http://72.14.177.54/SFVLUG/Talk:Pending</comments>		</item>
		<item>
			<title>Pending</title>
			<link>http://72.14.177.54/SFVLUG/Pending</link>
			<description>&lt;p&gt;Koopa:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Newbie Commandline Essentials==&lt;br /&gt;
&lt;br /&gt;
''Under Construction!'' (recategorise, review, augment, and add descriptions after more sleep)&lt;br /&gt;
&lt;br /&gt;
If you don't know your commandline very well at least know the tools that you have at your disposal to find the information and operate most efficiently. This section will contain only the entries that will enable you to maximize your productivity at the command line. &lt;br /&gt;
&lt;br /&gt;
Search and documentation tools are some of the most important tools you can learn on your box heres a brief list of a few of the most popular, all of which can be accessed through your terminal (xterm, rxvt, etc...) or console (&amp;lt;ctrl&amp;gt;&amp;lt;alt&amp;gt;F1...F6).&lt;br /&gt;
&lt;br /&gt;
'''Search, Documentation and General Information Related Tools:'''&lt;br /&gt;
 man&lt;br /&gt;
 find&lt;br /&gt;
 locate&lt;br /&gt;
 updatedb&lt;br /&gt;
 which&lt;br /&gt;
 whereis&lt;br /&gt;
 hier&lt;br /&gt;
 man man&lt;br /&gt;
 man bash&lt;br /&gt;
 help&lt;br /&gt;
 alias&lt;br /&gt;
 less&lt;br /&gt;
 more&lt;br /&gt;
 du&lt;br /&gt;
 df&lt;br /&gt;
 free&lt;br /&gt;
 top&lt;br /&gt;
 lsof&lt;br /&gt;
 &lt;br /&gt;
'''Networking Information and Related Tools:'''&lt;br /&gt;
 hostname&lt;br /&gt;
 ping&lt;br /&gt;
 route&lt;br /&gt;
 traceroute&lt;br /&gt;
 arp&lt;br /&gt;
 ifup/down&lt;br /&gt;
 ifconfig&lt;br /&gt;
 iwconfig&lt;br /&gt;
 iwlist&lt;br /&gt;
 netstat&lt;br /&gt;
&lt;br /&gt;
'''Files You Should Know Exist:'''&lt;br /&gt;
 passwd&lt;br /&gt;
 hosts&lt;br /&gt;
 hosts.allow&lt;br /&gt;
 hosts.deny&lt;br /&gt;
 hostname&lt;br /&gt;
 version&lt;br /&gt;
 resolv.conf&lt;br /&gt;
 groups&lt;br /&gt;
 .bash_profile&lt;br /&gt;
 .bashrc&lt;br /&gt;
 .bash_aliases&lt;br /&gt;
 fstab&lt;br /&gt;
 modules.conf&lt;br /&gt;
 dhclient.conf&lt;br /&gt;
&lt;br /&gt;
'''Paths You Should Know Exist:'''&lt;br /&gt;
Note: see man hier for general overview&lt;br /&gt;
&lt;br /&gt;
 /usr/share/doc&lt;br /&gt;
 /usr/local/doc&lt;br /&gt;
 /var/log&lt;br /&gt;
 /etc&lt;br /&gt;
 /etc/init.d&lt;br /&gt;
 /etc/alternatives&lt;br /&gt;
 &lt;br /&gt;
'''Conveniences:'''&lt;br /&gt;
 history&lt;br /&gt;
 ssh-agent&lt;br /&gt;
 keychains&lt;br /&gt;
 screen&lt;br /&gt;
 &lt;br /&gt;
'''Basics:'''&lt;br /&gt;
 cp&lt;br /&gt;
 mv&lt;br /&gt;
 rm&lt;br /&gt;
 ls&lt;br /&gt;
 cd&lt;br /&gt;
 chmod&lt;br /&gt;
 chown&lt;br /&gt;
 cat&lt;br /&gt;
&lt;br /&gt;
'''Essential Keystrokes:'''&lt;br /&gt;
;&lt;br /&gt;
 ?&lt;br /&gt;
 *&lt;br /&gt;
 ~&lt;br /&gt;
 .&lt;br /&gt;
 ./&lt;br /&gt;
 |&lt;br /&gt;
 n&lt;br /&gt;
 &amp;lt;ctrl&amp;gt;r&lt;br /&gt;
 !      Start  a  history substitution, except when followed by a blank,&lt;br /&gt;
 !n&lt;br /&gt;
 !-n&lt;br /&gt;
 !!&lt;br /&gt;
 !string&lt;br /&gt;
 !?string/n&lt;br /&gt;
 less v&lt;br /&gt;
 &lt;br /&gt;
addme&lt;br /&gt;
 grep rgrep egrep fgrep&lt;br /&gt;
 xargs&lt;br /&gt;
 su &lt;br /&gt;
 sudo&lt;br /&gt;
 package manager commands just names not all the options better kept in a different nonessential ref&lt;/div&gt;</description>
			<pubDate>Wed, 22 Nov 2006 22:12:52 GMT</pubDate>			<dc:creator>Koopa</dc:creator>			<comments>http://72.14.177.54/SFVLUG/Talk:Pending</comments>		</item>
		<item>
			<title>Pending</title>
			<link>http://72.14.177.54/SFVLUG/Pending</link>
			<description>&lt;p&gt;Koopa:&amp;#32;/* Newbie Commandline Essentials */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Newbie Commandline Essentials==&lt;br /&gt;
&lt;br /&gt;
''Under Construction!'' (recategorise, review, augment, and add descriptions after more sleep)&lt;br /&gt;
&lt;br /&gt;
If you don't know your commandline very well at least know the tools that you have at your disposal to find the information.&lt;br /&gt;
&lt;br /&gt;
Search and documentation tools are some of the most important tools you can learn on your box heres a brief list of a few of the most popular, all of which can be accessed through your terminal (xterm, rxvt, etc...) or console (&amp;lt;ctrl&amp;gt;&amp;lt;alt&amp;gt;F1...F6).&lt;br /&gt;
&lt;br /&gt;
'''Search, Documentation and General Information Related Tools:'''&lt;br /&gt;
 man&lt;br /&gt;
 find&lt;br /&gt;
 locate&lt;br /&gt;
 updatedb&lt;br /&gt;
 which&lt;br /&gt;
 whereis&lt;br /&gt;
 hier&lt;br /&gt;
 man man&lt;br /&gt;
 man bash&lt;br /&gt;
 help&lt;br /&gt;
 alias&lt;br /&gt;
 less&lt;br /&gt;
 more&lt;br /&gt;
 du&lt;br /&gt;
 df&lt;br /&gt;
 free&lt;br /&gt;
 top&lt;br /&gt;
 lsof&lt;br /&gt;
 &lt;br /&gt;
'''Networking Information and Related Tools:'''&lt;br /&gt;
 hostname&lt;br /&gt;
 ping&lt;br /&gt;
 route&lt;br /&gt;
 traceroute&lt;br /&gt;
 arp&lt;br /&gt;
 ifup/down&lt;br /&gt;
 ifconfig&lt;br /&gt;
 iwconfig&lt;br /&gt;
 iwlist&lt;br /&gt;
 netstat&lt;br /&gt;
&lt;br /&gt;
'''Files You Should Know Exist:'''&lt;br /&gt;
 passwd&lt;br /&gt;
 hosts&lt;br /&gt;
 hosts.allow&lt;br /&gt;
 hosts.deny&lt;br /&gt;
 hostname&lt;br /&gt;
 version&lt;br /&gt;
 resolv.conf&lt;br /&gt;
 groups&lt;br /&gt;
 .bash_profile&lt;br /&gt;
 .bashrc&lt;br /&gt;
 .bash_aliases&lt;br /&gt;
 fstab&lt;br /&gt;
 modules.conf&lt;br /&gt;
 dhclient.conf&lt;br /&gt;
&lt;br /&gt;
'''Paths You Should Know Exist:'''&lt;br /&gt;
Note: see man hier for general overview&lt;br /&gt;
&lt;br /&gt;
 /usr/share/doc&lt;br /&gt;
 /usr/local/doc&lt;br /&gt;
 /var/log&lt;br /&gt;
 /etc&lt;br /&gt;
 /etc/init.d&lt;br /&gt;
 /etc/alternatives&lt;br /&gt;
 &lt;br /&gt;
'''Conveniences:'''&lt;br /&gt;
 history&lt;br /&gt;
 ssh-agent&lt;br /&gt;
 keychains&lt;br /&gt;
 screen&lt;br /&gt;
 &lt;br /&gt;
'''Basics:'''&lt;br /&gt;
 cp&lt;br /&gt;
 mv&lt;br /&gt;
 rm&lt;br /&gt;
 ls&lt;br /&gt;
 cd&lt;br /&gt;
 chmod&lt;br /&gt;
 chown&lt;br /&gt;
 cat&lt;br /&gt;
&lt;br /&gt;
'''Essential Keystrokes:'''&lt;br /&gt;
;&lt;br /&gt;
 ?&lt;br /&gt;
 *&lt;br /&gt;
 ~&lt;br /&gt;
 .&lt;br /&gt;
 ./&lt;br /&gt;
 |&lt;br /&gt;
 n&lt;br /&gt;
 &amp;lt;ctrl&amp;gt;r&lt;br /&gt;
 !      Start  a  history substitution, except when followed by a blank,&lt;br /&gt;
 !n&lt;br /&gt;
 !-n&lt;br /&gt;
 !!&lt;br /&gt;
 !string&lt;br /&gt;
 !?string/n&lt;br /&gt;
 less v&lt;br /&gt;
 &lt;br /&gt;
addme&lt;br /&gt;
 grep rgrep egrep fgrep&lt;br /&gt;
 xargs&lt;br /&gt;
 su &lt;br /&gt;
 sudo&lt;br /&gt;
 package manager commands just names not all the options better kept in a different nonessential ref&lt;/div&gt;</description>
			<pubDate>Wed, 22 Nov 2006 22:10:04 GMT</pubDate>			<dc:creator>Koopa</dc:creator>			<comments>http://72.14.177.54/SFVLUG/Talk:Pending</comments>		</item>
		<item>
			<title>Pending</title>
			<link>http://72.14.177.54/SFVLUG/Pending</link>
			<description>&lt;p&gt;Koopa:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Newbie Commandline Essentials==&lt;br /&gt;
&lt;br /&gt;
''Under Construction!'' (recategorise, review, augment, and add descriptions after more sleep)&lt;br /&gt;
&lt;br /&gt;
If you don't know your commandline very well at least know the tools that you have at your disposal to find the information.&lt;br /&gt;
&lt;br /&gt;
Search and documentation tools are some of the most important tools you can learn on your box heres a brief list of a few of the most popular, all of which can be accessed through your terminal (xterm, rxvt, etc...) or console (&amp;lt;ctrl&amp;gt;&amp;lt;alt&amp;gt;F1...F6).&lt;br /&gt;
&lt;br /&gt;
'''Search, Documentation and General Information Related Tools:'''&lt;br /&gt;
 man&lt;br /&gt;
 find&lt;br /&gt;
 locate&lt;br /&gt;
 updatedb&lt;br /&gt;
 which&lt;br /&gt;
 whereis&lt;br /&gt;
 hier&lt;br /&gt;
 man man&lt;br /&gt;
 man bash&lt;br /&gt;
 help&lt;br /&gt;
 alias&lt;br /&gt;
 less&lt;br /&gt;
 more&lt;br /&gt;
 du&lt;br /&gt;
 df&lt;br /&gt;
 free&lt;br /&gt;
 top&lt;br /&gt;
 lsof&lt;br /&gt;
 &lt;br /&gt;
'''Networking Information and Related Tools:'''&lt;br /&gt;
 hostname&lt;br /&gt;
 ping&lt;br /&gt;
 route&lt;br /&gt;
 traceroute&lt;br /&gt;
 arp&lt;br /&gt;
 ifup/down&lt;br /&gt;
 ifconfig&lt;br /&gt;
 iwconfig&lt;br /&gt;
 iwlist&lt;br /&gt;
 netstat&lt;br /&gt;
&lt;br /&gt;
'''Files You Should Know Exist:'''&lt;br /&gt;
 passwd&lt;br /&gt;
 hosts&lt;br /&gt;
 hosts.allow&lt;br /&gt;
 hosts.deny&lt;br /&gt;
 hostname&lt;br /&gt;
 version&lt;br /&gt;
 resolv.conf&lt;br /&gt;
 groups&lt;br /&gt;
 .bash_profile&lt;br /&gt;
 .bashrc&lt;br /&gt;
 .bash_aliases&lt;br /&gt;
 fstab&lt;br /&gt;
 modules.conf&lt;br /&gt;
 dhclient.conf&lt;br /&gt;
&lt;br /&gt;
'''Paths You Should Know Exist:'''&lt;br /&gt;
Note: see man hier for general overview&lt;br /&gt;
&lt;br /&gt;
 /usr/share/doc&lt;br /&gt;
 /usr/local/doc&lt;br /&gt;
 /var/log&lt;br /&gt;
 /etc&lt;br /&gt;
 /etc/init.d&lt;br /&gt;
 /etc/alternatives&lt;br /&gt;
 &lt;br /&gt;
'''Conveniences:'''&lt;br /&gt;
 history&lt;br /&gt;
 ssh-agent&lt;br /&gt;
 keychains&lt;br /&gt;
 screen&lt;br /&gt;
 &lt;br /&gt;
'''Basics:'''&lt;br /&gt;
 cp&lt;br /&gt;
 mv&lt;br /&gt;
 rm&lt;br /&gt;
 ls&lt;br /&gt;
 cd&lt;br /&gt;
 chmod&lt;br /&gt;
 chown&lt;br /&gt;
 cat&lt;br /&gt;
&lt;br /&gt;
'''Essential Keystrokes:'''&lt;br /&gt;
;&lt;br /&gt;
?&lt;br /&gt;
*&lt;br /&gt;
~&lt;br /&gt;
.&lt;br /&gt;
./&lt;br /&gt;
|&lt;br /&gt;
n&lt;br /&gt;
&amp;lt;ctrl&amp;gt;r&lt;br /&gt;
!      Start  a  history substitution, except when followed by a blank,&lt;br /&gt;
!n&lt;br /&gt;
!-n&lt;br /&gt;
!!&lt;br /&gt;
!string&lt;br /&gt;
!?string/n&lt;br /&gt;
less v&lt;br /&gt;
&lt;br /&gt;
addme&lt;br /&gt;
grep rgrep egrep fgrep&lt;br /&gt;
xargs&lt;br /&gt;
su &lt;br /&gt;
sudo&lt;br /&gt;
package manager commands just names not all the options better kept in a different nonessential ref&lt;/div&gt;</description>
			<pubDate>Wed, 22 Nov 2006 22:09:10 GMT</pubDate>			<dc:creator>Koopa</dc:creator>			<comments>http://72.14.177.54/SFVLUG/Talk:Pending</comments>		</item>
		<item>
			<title>Newbie Resources</title>
			<link>http://72.14.177.54/SFVLUG/Newbie_Resources</link>
			<description>&lt;p&gt;Koopa:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Newbie Resources==&lt;br /&gt;
&lt;br /&gt;
Here are some links that may be of particular interest to those who are new to Linux and the Open Source community and want to learn more.&lt;br /&gt;
&lt;br /&gt;
Before we get too far, the first thing to learn is that Google is indeed your friend. Here is a link to Google's special Linux search:&lt;br /&gt;
http://www.google.com/linux Google the Linux way. This should be your primary general resource, that is why it is placed here at the top of this list.&lt;br /&gt;
&lt;br /&gt;
Before you start bothering your friends or strangers the first thing to learn is how to ask questions that will return useful information and also won't make people upset. You don't want to alienate the people best able to answer questions with answers not found anywhere in print. This guide should be viewed before posting questions to forums, newsgroups, mailing lists, etc. It is appropriate reading for computer users of all skill levels. http://www.catb.org/~esr/faqs/smart-questions.html The author, [http://www.catb.org/~esr/ Eric S. Raymond] also has some other FAQs and HOWTOs at http://www.catb.org/~esr/faqs/ his emphasis in on bringing people to a high technical level and may contain information specific to IT professionals and people that want to become IT professionals.&lt;br /&gt;
&lt;br /&gt;
If you haven't yet installed Linux or are looking to change to a different flavor of Linux this site has good up to date information on what is available. http://distrowatch.com/ Another great download resource is http://www.ibiblio.org/pub/linux/ with much Linux software available for download from their servers. You can also find documentation at http://tldp.org/ at a different URL but same folks. They are a collaboration of the center for the public domain and [http://www.unc.edu/ unc-ch] with many free and open resources besides software. http://www.ibiblio.org/&lt;br /&gt;
&lt;br /&gt;
A good set of online Linux courses can be found over at [http://www.linux.org Linux.org] That's a great jumping off site for Linux users of all levels. It is where I (Charles Wyble) spent the majority of my online research time in the first year of using Linux.&lt;br /&gt;
&lt;br /&gt;
* [http://www.linux.org/lessons/beginner/index.html Beginner Course]&lt;br /&gt;
* [http://www.linux.org/lessons/interm/index.html Intermediate Course]&lt;br /&gt;
* [http://www.linux.org/lessons/advanced/index.html Advanced Course]&lt;br /&gt;
&lt;br /&gt;
==Software Resources==&lt;br /&gt;
So if your new to Linux you probably want an idea of what software you can use with it. Now you can't just go down to your local computer store and buy software for Linux. However you can find software on the internet. The two most popluar sites for finding/downloading software are:&lt;br /&gt;
&lt;br /&gt;
*[http://http://freshmeat.net/ Freshmeat.net] A site that tracks releases of several thousand packages. A great site to simply browse and see the wide variety of software available. &lt;br /&gt;
&lt;br /&gt;
*[http://sourceforge.net Source Forge (also known as SF)] This site is used to host free/open source software. It is hands down the most popular hosting site out there. I (Charles) host multiple open source projects on the site. &lt;br /&gt;
&lt;br /&gt;
The third way to find software is the package management system in your distrubtution. What I like to do when searching for software is to go on Freshmeat/SF and do a keyword search. I then sort on various criteria (popularity/last update etc). I then open up the websites associated with the software in various tabs. Once I have selected some canidates I install them via my package manager. I use [http://www.debian.org Debian] based distrubutions which contain some 15,000 software packages for easy installation. Others in the LUG use [http://fedora.redhat.com/ Fedora] It all comes down to a matter of taste :)&lt;/div&gt;</description>
			<pubDate>Wed, 22 Nov 2006 22:02:05 GMT</pubDate>			<dc:creator>Koopa</dc:creator>			<comments>http://72.14.177.54/SFVLUG/Talk:Newbie_Resources</comments>		</item>
		<item>
			<title>Main Page</title>
			<link>http://72.14.177.54/SFVLUG/Main_Page</link>
			<description>&lt;p&gt;Koopa:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
&lt;br /&gt;
==San Fernando Valley Linux Users Group==&lt;br /&gt;
&lt;br /&gt;
Welcome to the San Fernando Valley Linux Users Group (SFVLUG) wiki. This site is currently hosted by [http://www.editthis.info EditThis] using [http://www.mediawiki.org/ MediaWiki] software. We will decide whether or not to keep it going here or move it to our own server once our own server is up to speed.&lt;br /&gt;
&lt;br /&gt;
Our primary site is [http://www.sfvlug.org www.sfvlug.org] and any information found there is to be considered authoritative. Please use any information in it over this site in the case of conflicting information. This site is not secure and can be edited by someone without authority.&lt;br /&gt;
&lt;br /&gt;
Hey Everyone! This LUG and this wiki will only be what '''you''' help it to become. Get involved, be a giver and not just a taker. It doesn't matter how large or small your contribution but if we don't get more involvement besides from a small hand full of people those people are going to burn out and we will all lose an important resource.&lt;br /&gt;
&lt;br /&gt;
====[[Announcements]]====  announcements for membership meetings and events provided by SFVLUG&lt;br /&gt;
&lt;br /&gt;
====[[Presentations]]====  Presentation page. Links to resources and slides.&lt;br /&gt;
&lt;br /&gt;
====[[Newbie Resources]]==== resources for those new to GNU/Linux and/or open source software&lt;br /&gt;
&lt;br /&gt;
====[[Psyche Project]]==== our SCALE speech recognition and systhesis project&lt;br /&gt;
&lt;br /&gt;
====[[Classes]]==== instruction beyond one time presentations&lt;br /&gt;
&lt;br /&gt;
====[[Special Interest Groups]]==== subgroups of SFVLUG with an interest in a particular area(s) relating to F/OSS&lt;br /&gt;
&lt;br /&gt;
====[[Code Vault]]==== looking for or wanting to donate any bash script or other short and simple code, check this out&lt;br /&gt;
&lt;br /&gt;
====[[Wiki Specific Info]]==== info on the wiki software used for this site&lt;br /&gt;
&lt;br /&gt;
====[[SFVLUG:Community Portal | Community Portal]]==== external links to the open source community in cyberspace&lt;br /&gt;
&lt;br /&gt;
====[[People Page]]==== personal pages for members&lt;br /&gt;
&lt;br /&gt;
====[[Sandbox]]==== Use this area for training and experimentation&lt;br /&gt;
&lt;br /&gt;
====[[Pending]]==== Use this are to develop content thats not yet ready for public viewing&lt;br /&gt;
&lt;br /&gt;
====About Us====&lt;br /&gt;
&lt;br /&gt;
We are a very loosely organized group of GNU/Linux and open source software enthusiasts, that live/work/meet in the San Fernando Valley, a suburb of Los Angeles in Southern Californina. You don't actually need to live in the Valley to join, but attending meetings is more difficult if you don't. Please see our [[Announcements]] page for more information on meetings. If you can't attend regular meetings you can still get involved here at this wiki, or in our IRC chat on [http://freenode.net/ freenode] in #sfvlug.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
===Copyleft===&lt;br /&gt;
We need to work out copyright/copyleft/public domain issues, so we can include material with restricted licenses, but at this time you should consider any submission to this site as being in the public domain. Do not post copyrighted material to this site no matter what license without the permission of the copyright holder. Any license restricts what you can and can not do with the material, even the GPL. If you need to reference copyrighted material and can't get permission please use an external link to the original material.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Thank you for visiting the SFVLUG wiki.'''&lt;/div&gt;</description>
			<pubDate>Wed, 22 Nov 2006 22:01:05 GMT</pubDate>			<dc:creator>Koopa</dc:creator>			<comments>http://72.14.177.54/SFVLUG/Talk:Main_Page</comments>		</item>
		<item>
			<title>Newbie Resources</title>
			<link>http://72.14.177.54/SFVLUG/Newbie_Resources</link>
			<description>&lt;p&gt;Koopa:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Newbie Resources==&lt;br /&gt;
&lt;br /&gt;
Here are some links that may be of particular interest to those who are new to Linux and the Open Source community and want to learn more.&lt;br /&gt;
&lt;br /&gt;
Before we get too far, the first thing to learn is that Google is indeed your friend. Here is a link to Google's special Linux search:&lt;br /&gt;
http://www.google.com/linux Google the Linux way. This should be your primary general resource, that is why it is placed here at the top of this list.&lt;br /&gt;
&lt;br /&gt;
Before you start bothering your friends or strangers the first thing to learn is how to ask questions that will return useful information and also won't make people upset. You don't want to alienate the people best able to answer questions with answers not found anywhere in print. This guide should be viewed before posting questions to forums, newsgroups, mailing lists, etc. It is appropriate reading for computer users of all skill levels. http://www.catb.org/~esr/faqs/smart-questions.html The author, [http://www.catb.org/~esr/ Eric S. Raymond] also has some other FAQs and HOWTOs at http://www.catb.org/~esr/faqs/ his emphasis in on bringing people to a high technical level and may contain information specific to IT professionals and people that want to become IT professionals.&lt;br /&gt;
&lt;br /&gt;
If you haven't yet installed Linux or are looking to change to a different flavor of Linux this site has good up to date information on what is available. http://distrowatch.com/ Another great download resource is http://www.ibiblio.org/pub/linux/ with much Linux software available for download from their servers. You can also find documentation at http://tldp.org/ at a different URL but same folks. They are a collaboration of the center for the public domain and [http://www.unc.edu/ unc-ch] with many free and open resources besides software. http://www.ibiblio.org/&lt;br /&gt;
&lt;br /&gt;
A good set of online Linux courses can be found over at [http://www.linux.org Linux.org] That's a great jumping off site for Linux users of all levels. It is where I (Charles Wyble) spent the majority of my online research time in the first year of using Linux.&lt;br /&gt;
&lt;br /&gt;
* [http://www.linux.org/lessons/beginner/index.html Beginner Course]&lt;br /&gt;
* [http://www.linux.org/lessons/interm/index.html Intermediate Course]&lt;br /&gt;
* [http://www.linux.org/lessons/advanced/index.html Advanced Course]&lt;br /&gt;
&lt;br /&gt;
==Software Resources==&lt;br /&gt;
So if your new to Linux you probably want an idea of what software you can use with it. Now you can't just go down to your local computer store and buy software for Linux. However you can find software on the internet. The two most popluar sites for finding/downloading software are:&lt;br /&gt;
&lt;br /&gt;
*[http://http://freshmeat.net/ Freshmeat.net] A site that tracks releases of several thousand packages. A great site to simply browse and see the wide variety of software available. &lt;br /&gt;
&lt;br /&gt;
*[http://sourceforge.net Source Forge (also known as SF)] This site is used to host free/open source software. It is hands down the most popular hosting site out there. I (Charles) host multiple open source projects on the site. &lt;br /&gt;
&lt;br /&gt;
The third way to find software is the package management system in your distrubtution. What I like to do when searching for software is to go on Freshmeat/SF and do a keyword search. I then sort on various criteria (popularity/last update etc). I then open up the websites associated with the software in various tabs. Once I have selected some canidates I install them via my package manager. I use [http://www.debian.org Debian] based distrubutions which contain some 15,000 software packages for easy installation. Others in the LUG use [http://fedora.redhat.com/ Fedora] It all comes down to a matter of taste :)&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==Newbie Commandline Essentials==&lt;br /&gt;
&lt;br /&gt;
''Under Construction!'' (recategorise and review after more sleep looks really bad atm)&lt;br /&gt;
&lt;br /&gt;
If you don't know your commandline very well at least know the tools that you have at your disposal to find the information.&lt;br /&gt;
&lt;br /&gt;
Search and documentation tools are some of the most important tools you can learn on your box heres a brief list of a few of the most popular, all of which can be accessed through your terminal (xterm, rxvt, etc...) or console (&amp;lt;ctrl&amp;gt;&amp;lt;alt&amp;gt;F1...F6).&lt;br /&gt;
&lt;br /&gt;
'''Search, Documentation and General Information Related Tools:'''&lt;br /&gt;
 man&lt;br /&gt;
 find&lt;br /&gt;
 locate&lt;br /&gt;
 updatedb&lt;br /&gt;
 which&lt;br /&gt;
 whereis&lt;br /&gt;
 hier&lt;br /&gt;
 man man&lt;br /&gt;
 man bash&lt;br /&gt;
 help&lt;br /&gt;
 alias&lt;br /&gt;
 less&lt;br /&gt;
 more&lt;br /&gt;
 du&lt;br /&gt;
 df&lt;br /&gt;
 free&lt;br /&gt;
 top&lt;br /&gt;
 lsof&lt;br /&gt;
 &lt;br /&gt;
'''Networking Information and Related Tools:'''&lt;br /&gt;
 hostname&lt;br /&gt;
 ping&lt;br /&gt;
 route&lt;br /&gt;
 traceroute&lt;br /&gt;
 arp&lt;br /&gt;
 ifup/down&lt;br /&gt;
 ifconfig&lt;br /&gt;
 iwconfig&lt;br /&gt;
 iwlist&lt;br /&gt;
 netstat&lt;br /&gt;
&lt;br /&gt;
'''Files You Should Know Exist:'''&lt;br /&gt;
 passwd&lt;br /&gt;
 hosts&lt;br /&gt;
 hosts.allow&lt;br /&gt;
 hosts.deny&lt;br /&gt;
 hostname&lt;br /&gt;
 version&lt;br /&gt;
 resolv.conf&lt;br /&gt;
 groups&lt;br /&gt;
 .bash_profile&lt;br /&gt;
 .bashrc&lt;br /&gt;
 .bash_aliases&lt;br /&gt;
 fstab&lt;br /&gt;
 modules.conf&lt;br /&gt;
 dhclient.conf&lt;br /&gt;
&lt;br /&gt;
'''Paths You Should Know Exist:'''&lt;br /&gt;
Note: see man hier for general overview&lt;br /&gt;
&lt;br /&gt;
 /usr/share/doc&lt;br /&gt;
 /usr/local/doc&lt;br /&gt;
 /var/log&lt;br /&gt;
 /etc&lt;br /&gt;
 /etc/init.d&lt;br /&gt;
 /etc/alternatives&lt;br /&gt;
 &lt;br /&gt;
'''Conveniences:'''&lt;br /&gt;
 history&lt;br /&gt;
 ssh-agent&lt;br /&gt;
 keychains&lt;br /&gt;
 screen&lt;br /&gt;
 &lt;br /&gt;
'''Basics:'''&lt;br /&gt;
 cp&lt;br /&gt;
 mv&lt;br /&gt;
 rm&lt;br /&gt;
 ls&lt;br /&gt;
 cd&lt;br /&gt;
 chmod&lt;br /&gt;
 chown&lt;br /&gt;
 cat&lt;/div&gt;</description>
			<pubDate>Wed, 22 Nov 2006 21:51:50 GMT</pubDate>			<dc:creator>Koopa</dc:creator>			<comments>http://72.14.177.54/SFVLUG/Talk:Newbie_Resources</comments>		</item>
	</channel>
</rss>