<?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/Brian</link>
		<description>From Sfvlug</description>
		<language>en</language>
		<generator>MediaWiki 1.15.1</generator>
		<lastBuildDate>Mon, 22 Jun 2026 13:49:01 GMT</lastBuildDate>
		<item>
			<title>Scale 2009</title>
			<link>http://72.14.177.54/SFVLUG/Scale_2009</link>
			<description>&lt;p&gt;Brian:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Voice Triggers&lt;br /&gt;
&lt;br /&gt;
DD-WRT&lt;br /&gt;
&lt;br /&gt;
Media server&lt;br /&gt;
&lt;br /&gt;
Asterisk&lt;br /&gt;
&lt;br /&gt;
Network storage&lt;br /&gt;
&lt;br /&gt;
Wifi security&lt;br /&gt;
&lt;br /&gt;
Zoneminder&lt;br /&gt;
&lt;br /&gt;
Custom distro&lt;br /&gt;
&lt;br /&gt;
Linux on old hardware&lt;br /&gt;
&lt;br /&gt;
Linux on Apple hardware&lt;br /&gt;
&lt;br /&gt;
Space-saving techniques&lt;br /&gt;
&lt;br /&gt;
Virtualization&lt;br /&gt;
&lt;br /&gt;
Fast booting&lt;br /&gt;
&lt;br /&gt;
GRUB&lt;br /&gt;
&lt;br /&gt;
Apt-proxy&lt;/div&gt;</description>
			<pubDate>Sun, 18 Jan 2009 06:31:26 GMT</pubDate>			<dc:creator>Brian</dc:creator>			<comments>http://72.14.177.54/SFVLUG/Talk:Scale_2009</comments>		</item>
		<item>
			<title>SCALE</title>
			<link>http://72.14.177.54/SFVLUG/SCALE</link>
			<description>&lt;p&gt;Brian:&amp;#32;/* Preparation For SCALE-7x */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page is a discussion on the SCALE events and our participation.&lt;br /&gt;
= Preparation For SCALE-7x=&lt;br /&gt;
&lt;br /&gt;
'''Hi all, it's that time again, we are getting ready for this year's SCALE http://scale7x.socallinuxexpo.org/&lt;br /&gt;
'''&lt;br /&gt;
&lt;br /&gt;
This year in addition to our usual Psyche demo we are also going to spotlight some smaller projects too. Our overall theme is about using GNU/Linux/FLOSS in the home and small business, basically SOHO + personal use. The current working title is &amp;quot;Using Linux In The Home And Small Business Environment&amp;quot; but we still have a couple of days to come up with something better. If you have a favorite application, or more broadly any set of tools or applications, that you think might make a cool presentation please contact Brian or Kurt. You don't need to have an elaborate polished demo, just something you think visitors to SCALE might find interesting. You don't need to even attend the event as long as it is a presentation that fits in the theme, and our theme is quite broad and could include just about anything that could be useful to a small business or for personal use.&lt;br /&gt;
&lt;br /&gt;
Please check back, we will be adding more content here as things progress. Please feel free to post suggestions, comments or questions here, in IRC or in the sfvlug mailing list.&lt;br /&gt;
&lt;br /&gt;
[[Scale 2009]]&lt;br /&gt;
&lt;br /&gt;
== A Bit Of Reflection On SCALE 5x ==&lt;br /&gt;
&lt;br /&gt;
I consider our presence at SCALE 5x a success despite the fact that we were unable to present our Psyche demo this year after failing to achieve a satisfactory recognition rate with Sphinx2, the speech recognition engine we had been using in the past. I had a chance to spend more time soaking in the event by concentrating more on the interaction with visitors to our booth than in putting on a presentation. I got a chance to meet a lot of nice folks and while it would be nice to have an attraction to draw in more folks I was reminded that our focus needs to be as much on community as it is on the technology itself.&lt;br /&gt;
&lt;br /&gt;
I have a few suggestions I have based on my experience that might help us grow as a community through our presence at future SCALE events. Some of these suggestions have been discussed in the past but for one reason or another haven't been implemented.&lt;br /&gt;
&lt;br /&gt;
* Printed Handouts - This year we provided printed hand outs with a map to our normal venues. This could be improved to include more information about our organization. Other information about Linux and open source software could be made available.&lt;br /&gt;
&lt;br /&gt;
* Better Signs - We had our SFVLUG Tux poster but some folks didn't understand who or what we were easily from our signs.&lt;br /&gt;
&lt;br /&gt;
* Branding - It would be great if we could provide stickers, or other low cost swag with name and URL included&lt;br /&gt;
&lt;br /&gt;
* Scheduled Participation - I had plenty of help with the booth but it would have been nice to have known in advance when I'd be able to attend a presentation or go to the bathroom.&lt;br /&gt;
&lt;br /&gt;
* Printer - There were many times it would have been handy to print out information for a visitor.&lt;br /&gt;
&lt;br /&gt;
* CD/DVD Burner - I burned a few to hand out, mostly Knoppix 5.1.1 and Open CD for Windoze. It would be nice to continue this practice but a bit more on purpose.&lt;br /&gt;
--[[User:Miasma|Miasma]] 23:07, 13 February 2007 (EST)&lt;/div&gt;</description>
			<pubDate>Sun, 18 Jan 2009 06:28:40 GMT</pubDate>			<dc:creator>Brian</dc:creator>			<comments>http://72.14.177.54/SFVLUG/Talk:SCALE</comments>		</item>
		<item>
			<title>Code Vault</title>
			<link>http://72.14.177.54/SFVLUG/Code_Vault</link>
			<description>&lt;p&gt;Brian:&amp;#32;/* Index */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Here is a list of bash script or other short and simple code that has been donated by our members.&lt;br /&gt;
&lt;br /&gt;
=Index=&lt;br /&gt;
NOTE: Please come in here and separate your code by username. I did this quick, shoot me if I made mistakes.&lt;br /&gt;
&lt;br /&gt;
''What is the point of separating the code by username? In Wiki, all of the pages can be edited by anyone, so laying claim to a page is rather not the idea.''&lt;br /&gt;
&lt;br /&gt;
==[[user:Brian|Brian]]==&lt;br /&gt;
====[[Process Substitution]]====&lt;br /&gt;
&lt;br /&gt;
==[[user:G4rlic|G4rlic]]==&lt;br /&gt;
====[[Mail Scrub]]====&lt;br /&gt;
====[[Python File Slicing]]====&lt;br /&gt;
====[[Low Power Boot]]====&lt;br /&gt;
&lt;br /&gt;
==[[user:JeffCarlson|JeffCarlson]]==&lt;br /&gt;
====[[Email Dictionary Attack]]====&lt;br /&gt;
&lt;br /&gt;
==[[user: Charles Wyble| Charles Wyble]]==&lt;br /&gt;
====[[Access to HTML]]====&lt;br /&gt;
&lt;br /&gt;
==[[user: Livinded|livinded]]==&lt;br /&gt;
====[[Caesar Cipher]]====&lt;/div&gt;</description>
			<pubDate>Fri, 06 Apr 2007 08:13:40 GMT</pubDate>			<dc:creator>Brian</dc:creator>			<comments>http://72.14.177.54/SFVLUG/Talk:Code_Vault</comments>		</item>
		<item>
			<title>Process Substitution</title>
			<link>http://72.14.177.54/SFVLUG/Process_Substitution</link>
			<description>&lt;p&gt;Brian:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Here is a quick tip on a way to use process substitution. I'll try to add more later.&lt;br /&gt;
&lt;br /&gt;
If you have two files, each with an unordered list of information, and you want to see what is unique to one file or the other, you might be tempted to do the following:&lt;br /&gt;
&lt;br /&gt;
 sort file1 &amp;gt; file1.sorted&lt;br /&gt;
 sort file2 &amp;gt; file2.sorted&lt;br /&gt;
 diff file1.sorted file2.sorted&lt;br /&gt;
&lt;br /&gt;
With process substitution, you can do this in a single line:&lt;br /&gt;
&lt;br /&gt;
 diff &amp;lt;( sort file1 ) &amp;lt;( sort file2 )&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;&amp;lt;(&amp;quot; is a token, so there must be no space between the characters, just like &amp;quot;$(&amp;quot; for variable substitution.&lt;/div&gt;</description>
			<pubDate>Tue, 05 Dec 2006 00:32:36 GMT</pubDate>			<dc:creator>Brian</dc:creator>			<comments>http://72.14.177.54/SFVLUG/Talk:Process_Substitution</comments>		</item>
		<item>
			<title>Process Substitution</title>
			<link>http://72.14.177.54/SFVLUG/Process_Substitution</link>
			<description>&lt;p&gt;Brian:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Here is a quick tip on a way to use process substitution. I'll try to add more later.&lt;br /&gt;
&lt;br /&gt;
If you have two files, each with an unordered list of information, and you want to see what is unique to one file or the other, you might be tempted to do the following:&lt;br /&gt;
&lt;br /&gt;
sort file1 &amp;gt; file1.sorted&lt;br /&gt;
sort file2 &amp;gt; file2.sorted&lt;br /&gt;
diff file1.sorted file2.sorted&lt;br /&gt;
&lt;br /&gt;
With process substitution, you can do this in a single line:&lt;br /&gt;
&lt;br /&gt;
diff &amp;lt;( sort file1 ) &amp;lt;( sort file2 )&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;&amp;lt;(&amp;quot; is a token, so there must be no space between the characters, just like &amp;quot;$(&amp;quot; for variable substitution.&lt;/div&gt;</description>
			<pubDate>Tue, 05 Dec 2006 00:32:14 GMT</pubDate>			<dc:creator>Brian</dc:creator>			<comments>http://72.14.177.54/SFVLUG/Talk:Process_Substitution</comments>		</item>
		<item>
			<title>Code Vault</title>
			<link>http://72.14.177.54/SFVLUG/Code_Vault</link>
			<description>&lt;p&gt;Brian:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;What is the best way to contribute code? Should it just be placed here or should a seperate page be created?&lt;br /&gt;
&lt;br /&gt;
Good question, I had intended to leave a lot of that type of decision up to whoever posted something but since this is going to be a community page it might be better to keep it less cluttered so I will suggest making a brief statement here about the code and a link to the page where the actual code lives. The discussion tab [[Talk:Code Vault]] can be used for comments rather than making further clutter here. If you haven't gotten the copyright holder's permission to use the code the link should be to the original source.&lt;br /&gt;
&lt;br /&gt;
Here are some examples to give everyone a better idea, we can clean this area up later once we get more contributions:&lt;br /&gt;
&lt;br /&gt;
(Let's say I'm not about the license and don't know if it is OK to reproduce.)&lt;br /&gt;
&lt;br /&gt;
== Hello World ==&lt;br /&gt;
Hi all, I found this great little script, it is a Bash script you can run at the command line and it actually will print &amp;quot;Hello World&amp;quot; to your terminal.  You can find it here:&lt;br /&gt;
http://tldp.org/HOWTO/Bash-Prog-Intro-HOWTO-2.html#ss2.1&lt;br /&gt;
&lt;br /&gt;
(Now, let's say I wrote it myself or have permission to reproduce.)&lt;br /&gt;
== Hello World ==&lt;br /&gt;
Guyz! I wrote this killer app that will actually print &amp;quot;Hello World&amp;quot; from the command line. Check it out!&lt;br /&gt;
[[Hello World]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Access Database to HTML ==&lt;br /&gt;
I have written a bash script that converts Access databases to HTML.&lt;br /&gt;
[http://thewybles.com/~charles/me/code/mdb2html.sh.txt Source Code] &lt;br /&gt;
&lt;br /&gt;
I know of at least two people in the LUG who were interested in this functionality. Code is GPL.&lt;br /&gt;
&lt;br /&gt;
== Process Substitution (or, how to do more with less effort) ==&lt;br /&gt;
[[Process Substitution]] is a good way to do things in a single line of script or at the command line, that would otherwise take extra work like writing to temp files.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Return to [[Main Page]]&lt;/div&gt;</description>
			<pubDate>Tue, 05 Dec 2006 00:28:16 GMT</pubDate>			<dc:creator>Brian</dc:creator>			<comments>http://72.14.177.54/SFVLUG/Talk:Code_Vault</comments>		</item>
		<item>
			<title>User:Brian</title>
			<link>http://72.14.177.54/SFVLUG/User:Brian</link>
			<description>&lt;p&gt;Brian:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Hi, this is my page. See if it changes ever.&lt;/div&gt;</description>
			<pubDate>Tue, 05 Dec 2006 00:25:31 GMT</pubDate>			<dc:creator>Brian</dc:creator>			<comments>http://72.14.177.54/SFVLUG/User_talk:Brian</comments>		</item>
	</channel>
</rss>