<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Albertech.net &#187; Linux</title>
	<atom:link href="http://albertech.net/category/linux/feed/" rel="self" type="application/rss+xml" />
	<link>http://albertech.net</link>
	<description>Guides and Reviews for WordPress, PHP, MySQL, Apache, CMS Systems, jQuery, and other Technologies</description>
	<lastBuildDate>Fri, 11 May 2012 23:39:47 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Puppet fileserver configuration with Scientific Linux 6.1 and SELINUX</title>
		<link>http://albertech.net/2012/04/puppet-fileserver-configuration-scientific-linux-6-1-and-selinux/</link>
		<comments>http://albertech.net/2012/04/puppet-fileserver-configuration-scientific-linux-6-1-and-selinux/#comments</comments>
		<pubDate>Wed, 18 Apr 2012 21:15:19 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Puppet]]></category>
		<category><![CDATA[SELINUX]]></category>
		<category><![CDATA[fileserver]]></category>
		<category><![CDATA[puppet]]></category>
		<category><![CDATA[SELinux]]></category>

		<guid isPermaLink="false">http://albertech.net/?p=943</guid>
		<description><![CDATA[The fileserver in Puppet is useful for quickly centralizing configuration files for multiple servers. It works well for serving small text configuration files to clients, but not recommended for large files since it places them into memory before sending them out. For larger files, I recommend using git or rsync instead since it doesn't affect the performance of the puppetmaster server.

After installing it on Scientific Linux 6.1, I had to go through some extra steps because of the SELINUX restrictions. Here's the steps I went through to get the Puppet fileserver working.

<span id="more-943"></span>

This guide assumes that you already have a ... ]]></description>
		<wfw:commentRss>http://albertech.net/2012/04/puppet-fileserver-configuration-scientific-linux-6-1-and-selinux/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Removing gnome from Scientific Linux</title>
		<link>http://albertech.net/2012/03/removing-gnome-from-scientific-linux/</link>
		<comments>http://albertech.net/2012/03/removing-gnome-from-scientific-linux/#comments</comments>
		<pubDate>Wed, 28 Mar 2012 19:38:02 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[remove gnome]]></category>

		<guid isPermaLink="false">http://albertech.net/?p=926</guid>
		<description><![CDATA[I recently had to remove the gnome GUI from a server running Scientific Linux (6.2) and had to go through a few steps to make it boot up properly.
<ol>
	<li>To remove Gnome from Scientific Linux, run the following command (while running outside of the GUI). This will remove all related applications related to the Gnome including Mozilla/etc.
<code>yum groupremove "GNOME Desktop Environment"</code></li>
	<li>Next, you will need to make sure your runlevel is set to 3. Otherwise, you won't be able to boot up into text mode. The run level in RedHat/CentOS/Fedora/Scientific Linux is set to 5 for Gnome/KDE. You'll need to change the ... ]]></description>
		<wfw:commentRss>http://albertech.net/2012/03/removing-gnome-from-scientific-linux/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Fix: Private key refused for SSH on new install of Fedora CentOS</title>
		<link>http://albertech.net/2012/03/fix-private-key-refused-for-ssh-on-new-install-of-fedora-centos/</link>
		<comments>http://albertech.net/2012/03/fix-private-key-refused-for-ssh-on-new-install-of-fedora-centos/#comments</comments>
		<pubDate>Thu, 01 Mar 2012 19:52:12 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Fedora]]></category>
		<category><![CDATA[ssh]]></category>

		<guid isPermaLink="false">http://albertech.net/?p=883</guid>
		<description><![CDATA[If you are setting up SSH public key authentication in a new Fedora/CentOS install, you must make sure the SELINX configuration is setup correctly for the /root/.ssh folder on the server.

The ~.ssh/ folder is not created on a new install. If you manually create the folder, set the SELINUX permissions with this command:

<code>restorecon -R -v /root/.ssh</code>

Another tip: If you are using the PuTTY Key generator to generate the public key, make sure you copy and paste the text into a single line in the /root/.ssh/authorized_keys file. Each line of the authorized_keys file should have the following: ssh-rsa (key contents) imported-openssh-key]]></description>
		<wfw:commentRss>http://albertech.net/2012/03/fix-private-key-refused-for-ssh-on-new-install-of-fedora-centos/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>VMWARE Tools install on Fedora</title>
		<link>http://albertech.net/2012/02/vmware-tools-install-on-fedora-1/</link>
		<comments>http://albertech.net/2012/02/vmware-tools-install-on-fedora-1/#comments</comments>
		<pubDate>Tue, 21 Feb 2012 23:49:46 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Fedora]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[VMWARE]]></category>
		<category><![CDATA[install vmware tools]]></category>

		<guid isPermaLink="false">http://albertech.net/?p=881</guid>
		<description><![CDATA[<strong>If you encounter the following error while installing vmware-tools in Fedora:</strong>
<blockquote><strong>Searching for a valid kernel header path...</strong>

<strong>The path "" is not valid.</strong></blockquote>
You will need the following packages installed:

<strong>gcc make kernel-headers kernel-devel</strong>

The trick is that you will need to perform at least two reboots before the vmware installer will actually find the kernel header package. You can verify the kernel install using "rpm -qa kernel*"
<ol>
	<li>yum install gcc make kernel-headers kernel-devel</li>
	<li>yum update</li>
	<li>Reboot (shutdown -r now)</li>
	<li>Run vmware-install.pl (Ex. /tmp/vmware-tools-distrib)</li>
	<li>It will probably not find the kernel header path this time around. Cancel the installer if its unable to find it again.</li>
	<li>Reboot (shutdown -r now)</li>
	<li>Run ... ]]></description>
		<wfw:commentRss>http://albertech.net/2012/02/vmware-tools-install-on-fedora-1/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Popular Linux Distributions for Web Servers</title>
		<link>http://albertech.net/2012/02/popular-linux-distributions-for-web-servers/</link>
		<comments>http://albertech.net/2012/02/popular-linux-distributions-for-web-servers/#comments</comments>
		<pubDate>Thu, 16 Feb 2012 19:08:37 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[linux distributions]]></category>
		<category><![CDATA[survey]]></category>

		<guid isPermaLink="false">http://albertech.net/?p=872</guid>
		<description><![CDATA[As of January 2012, Debian is currently the most popular Linux distribution for web servers. CentOS is a close second and Ubuntu is gaining popularity.

<strong>Debian 29.7%</strong>
<strong> CentOS 29.1%</strong>
Ubuntu 18.1%
Red Hat 12.4%
Fedora 5.1%
SuSE 3.0%
Gentoo 1.2%

<strong>Source:</strong> <a href="http://w3techs.com/blog/entry/debian_is_now_the_most_popular_linux_distribution_on_web_servers" target="_blank">http://w3techs.com/blog/entry/debian_is_now_the_most_popular_linux_distribution_on_web_servers</a>]]></description>
		<wfw:commentRss>http://albertech.net/2012/02/popular-linux-distributions-for-web-servers/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Installing nginx with PHP, MySQL, and WordPress in Fedora</title>
		<link>http://albertech.net/2011/04/installing-nginx-with-php-mysql-wordpress-in-fedora/</link>
		<comments>http://albertech.net/2011/04/installing-nginx-with-php-mysql-wordpress-in-fedora/#comments</comments>
		<pubDate>Fri, 01 Apr 2011 17:31:47 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Fedora]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[nginx]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[wordpress]]></category>
		<category><![CDATA[Fedora install]]></category>

		<guid isPermaLink="false">http://albertech.net/?p=663</guid>
		<description><![CDATA[Interested in installing nginx on a Fedora system? The configuration with nginx is more complicated than Apache since  it requires the setup of the nginx server and a separate daemon for running PHP. I prefer creating the daemon from scratch rather than going with the fpm route in Fedora 14 since there isn't official support for it. I'd certainly install the fpm package once its available in Fedora.

<strong>Why switch to nginx? </strong>

If you have a site with heavy CPU and memory load in Apache, then nginx is a great choice. I recently made the switch to nginx and have noticed a reduction in CPU and memory usage. Nginx loads static content very fast and efficiently.

Here's a graph of my nginx server load test. Courtesy of <a href="http://loadimpact.com/" target="_blank">LoadImpact</a>'s free load testing service.

<img class="alignnone size-full wp-image-666" title="nginx-blogs" src="http://albertech.net/wp-content/uploads/2011/04/nginx-blogs.png" alt="" width="544" height="335" />

The user load time on my server is minimally impacted with 50 clients viewing the site simultaneously.]]></description>
		<wfw:commentRss>http://albertech.net/2011/04/installing-nginx-with-php-mysql-wordpress-in-fedora/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>FIX: Fedora SELinux permissions for PHP file upload</title>
		<link>http://albertech.net/2011/03/fix-fedora-selinux-permissions-for-php-file-upload/</link>
		<comments>http://albertech.net/2011/03/fix-fedora-selinux-permissions-for-php-file-upload/#comments</comments>
		<pubDate>Wed, 02 Mar 2011 23:27:41 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[SELinux]]></category>

		<guid isPermaLink="false">http://albertech.net/?p=643</guid>
		<description><![CDATA[By default, SELinux will block the ability for Apache/webapps to write to files in Fedora. This is a security feature to limit what folders Apache can write to. You can notice this issue if you get errors in your Apache logs such as:

PHP Warning:  move_uploaded_file(): Unable to move '/tmp/...' to '.......'

<strong>Command to set permissions:</strong>

<code>chcon -R -t httpd_sys_rw_content_t [Name of Folder]</code>

You can check the SELinux permissions via the following command:
<code>ls -halZ</code>]]></description>
		<wfw:commentRss>http://albertech.net/2011/03/fix-fedora-selinux-permissions-for-php-file-upload/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Issues with Debian Lenny and Tomcat 5.5</title>
		<link>http://albertech.net/2010/11/issues-with-debian-lenny-and-tomcat-5-5/</link>
		<comments>http://albertech.net/2010/11/issues-with-debian-lenny-and-tomcat-5-5/#comments</comments>
		<pubDate>Tue, 16 Nov 2010 01:00:21 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[debian]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Tomcat]]></category>
		<category><![CDATA[tomcat 5.5]]></category>
		<category><![CDATA[tomcat 6]]></category>

		<guid isPermaLink="false">http://albertech.net/?p=520</guid>
		<description><![CDATA[<strong>Is your Debian install of Tomcat 5.5 not working with your Webapp?</strong>

Just a heads up for anyone with problems trying to get webapps working with Debian. I highly recommend installing Tomcat 6.0 from source. It helped clear a number of issues for me. Debian only supports Tomcat 5.5 in their package management system. I could have gone with unstable to get Tomcat 6.0, but I prefer not to deal with their folder organization layout (see below)

<strong>Here are a few resources I've used to install Tomcat 6.0 in Debian Lenny. </strong>

<ol><li>
<a href="http://www.ctrip.ufl.edu/tomcat6-debian-lenny-howto" target="_blank"><strong>How to Install Tomcat 6 in Debian Lenny</strong></a>. This is an <strong>excellent</strong> step-by-step tutorial. A+ in my book.
<li>
<a href="http://www.mysql.com/downloads/connector/j/" target="_blank"><strong>http://www.mysql.com/downloads/connector/j/</strong></a>  Connector/J, MySQL JDBC Connector download.
<li>
<a href="http://tomcat.apache.org/tomcat-6.0-doc/jndi-datasource-examples-howto.html" target="_blank"><strong>http://tomcat.apache.org/tomcat-6.0-doc/jndi-datasource-examples-howto.html</strong></a>. Tomcat 6.0 configuration with MySQL Connector/J JDBC.
</ol>

]]></description>
		<wfw:commentRss>http://albertech.net/2010/11/issues-with-debian-lenny-and-tomcat-5-5/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Fix: Webmin error &#8220;This Webmin module depends on the module phpini&#8221;</title>
		<link>http://albertech.net/2010/11/fix-webmin-error-this-webmin-module-depends-on-the-module-phpini/</link>
		<comments>http://albertech.net/2010/11/fix-webmin-error-this-webmin-module-depends-on-the-module-phpini/#comments</comments>
		<pubDate>Tue, 09 Nov 2010 17:49:42 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[debian]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[webmin]]></category>

		<guid isPermaLink="false">http://albertech.net/?p=514</guid>
		<description><![CDATA[Upon updating Webmin, I noticed that there is a new package dependency that breaks the updates.

To fix, you will need to get the phpini package from Webmin <a href="http://www.webmin.com/standard.html">http://www.webmin.com/standard.html</a> and extract the folder to your Webmin system folder. In Debian, its located in /usr/share/webmin/   This should also apply to any other Webmin packages that are missing from your system.]]></description>
		<wfw:commentRss>http://albertech.net/2010/11/fix-webmin-error-this-webmin-module-depends-on-the-module-phpini/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Fix: installing scponly on Debian 5.0</title>
		<link>http://albertech.net/2010/10/fix-installing-scponly-on-debian-5-0/</link>
		<comments>http://albertech.net/2010/10/fix-installing-scponly-on-debian-5-0/#comments</comments>
		<pubDate>Wed, 06 Oct 2010 00:37:51 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[debian]]></category>
		<category><![CDATA[Linux]]></category>

		<guid isPermaLink="false">http://albertech.net/?p=470</guid>
		<description><![CDATA[Scponly is used for chroot to limit server access for SSH and SFTP users. Unfortunately, the Debian package for scponly does not work with Debian 5.0.

If you upgraded from Debian 4 to Debian 5 and are using scponly, you may notice that the clients are unable to connect. Possible error messages include:
<ul>
	<li>"failed WinSCP compatibility mode" error message</li>
	<li>WinSCP closes unexpectedly after authenticating</li>
	<li>Connection failure after successful authentication</li>
	<li>Client logs two attempts to connect to the /home/username home directory before failing
<span id="more-470"></span></li>
</ul>
<strong>The fix is to remove scponly package in Debian and install a newer version from source code. Download the scponly source at:
</strong>

<a href="http://sublimation.org/scponly/wiki/index.php/Main_Page" ... ]]></description>
		<wfw:commentRss>http://albertech.net/2010/10/fix-installing-scponly-on-debian-5-0/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

