<?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>Solaris news, tips and tutorials</title>
	<atom:link href="http://www.solarisblog.org/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.solarisblog.org</link>
	<description>Blog about Solaris administration, network and security.</description>
	<lastBuildDate>Sun, 28 Apr 2013 13:32:31 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
		<item>
		<title>Upgrading a system to Oracle Solaris 11.1</title>
		<link>http://www.solarisblog.org/administration/upgrading-a-system-to-oracle-solaris-11-1/</link>
		<comments>http://www.solarisblog.org/administration/upgrading-a-system-to-oracle-solaris-11-1/#comments</comments>
		<pubDate>Sun, 28 Apr 2013 13:32:31 +0000</pubDate>
		<dc:creator>Michal</dc:creator>
				<category><![CDATA[Administration]]></category>
		<category><![CDATA[Solaris 11.1]]></category>
		<category><![CDATA[SUNWvboxguest]]></category>
		<category><![CDATA[upgrade]]></category>
		<category><![CDATA[VirtualBox]]></category>

		<guid isPermaLink="false">http://www.solarisblog.org/?p=262</guid>
		<description><![CDATA[Upgrading to Oracle Solaris 11.1 is a multistep process due to the requirement that certain system packages must be updated first in order to achieve a successful update for the remaining system packages. In order to perform successful upgrade you need to be logged in as root. 1. Update the system packages. # pkg update [...]]]></description>
		<wfw:commentRss>http://www.solarisblog.org/administration/upgrading-a-system-to-oracle-solaris-11-1/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Snoop Command Examples</title>
		<link>http://www.solarisblog.org/network/snoop-command-examples/</link>
		<comments>http://www.solarisblog.org/network/snoop-command-examples/#comments</comments>
		<pubDate>Fri, 21 May 2010 14:37:22 +0000</pubDate>
		<dc:creator>Michal</dc:creator>
				<category><![CDATA[Network]]></category>
		<category><![CDATA[snoop]]></category>

		<guid isPermaLink="false">http://www.solarisblog.org/?p=231</guid>
		<description><![CDATA[The root user can run the snoop command to capture network packets and to display their content to the screen. Captured packets can be displayed as they are received, or saved to a file for later inspection.  You can check content of this file by using snoop command. If you use snoop command without -v [...]]]></description>
		<wfw:commentRss>http://www.solarisblog.org/network/snoop-command-examples/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Enable/Disable The System Abort Sequence (Stop+A)</title>
		<link>http://www.solarisblog.org/security/enabledisable-the-system-abort-sequence-stopa/</link>
		<comments>http://www.solarisblog.org/security/enabledisable-the-system-abort-sequence-stopa/#comments</comments>
		<pubDate>Thu, 20 May 2010 23:45:12 +0000</pubDate>
		<dc:creator>Michal</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[/etc/system]]></category>
		<category><![CDATA[kbd]]></category>
		<category><![CDATA[Stop+A]]></category>

		<guid isPermaLink="false">http://www.solarisblog.org/?p=222</guid>
		<description><![CDATA[The main reason why you may need to disable the system abort sequence (Stop+A) could be security of your system. Anybody who can abort the system and bring it to OBP can eventually try to gain access to the root user account. You can disable the system abort sequence (Stop+A)  in several different ways. The [...]]]></description>
		<wfw:commentRss>http://www.solarisblog.org/security/enabledisable-the-system-abort-sequence-stopa/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Rstchown Parameter And Changing File Ownership</title>
		<link>http://www.solarisblog.org/security/the-rstchown-parameter-and-changing-file-ownership/</link>
		<comments>http://www.solarisblog.org/security/the-rstchown-parameter-and-changing-file-ownership/#comments</comments>
		<pubDate>Fri, 14 May 2010 02:10:47 +0000</pubDate>
		<dc:creator>Michal</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[/etc/system]]></category>
		<category><![CDATA[adb]]></category>
		<category><![CDATA[chgrp]]></category>
		<category><![CDATA[chown]]></category>
		<category><![CDATA[mdb]]></category>

		<guid isPermaLink="false">http://www.solarisblog.org/?p=208</guid>
		<description><![CDATA[By default, in Solaris, the owner of the file cannot use the chown command to change the owner of the file or directory. There is also restriction in using chgrp command. The owner can only use chgrp command to change the group of the file to a group, which  the owner belongs to. However, this [...]]]></description>
		<wfw:commentRss>http://www.solarisblog.org/security/the-rstchown-parameter-and-changing-file-ownership/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Display System and Hardware Data using The Prtdiag Command</title>
		<link>http://www.solarisblog.org/shell/display-system-and-hardware-data-using-the-prtdiag-command/</link>
		<comments>http://www.solarisblog.org/shell/display-system-and-hardware-data-using-the-prtdiag-command/#comments</comments>
		<pubDate>Wed, 12 May 2010 20:30:55 +0000</pubDate>
		<dc:creator>Michal</dc:creator>
				<category><![CDATA[Shell]]></category>
		<category><![CDATA[prtdiag]]></category>

		<guid isPermaLink="false">http://www.solarisblog.org/?p=204</guid>
		<description><![CDATA[The prtdiag command is very usefull tool for checking your hardware configuration. Based on the output you can tell what is inside your SUN box without opening it. This is also handy when you are dealing with SUN support. If your SUN box has Solaris 10 (SPARC or x86) prtdiag would be located at the [...]]]></description>
		<wfw:commentRss>http://www.solarisblog.org/shell/display-system-and-hardware-data-using-the-prtdiag-command/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Check Your Hardware And Software Configuration</title>
		<link>http://www.solarisblog.org/administration/check-your-hardware-and-software-configuration/</link>
		<comments>http://www.solarisblog.org/administration/check-your-hardware-and-software-configuration/#comments</comments>
		<pubDate>Wed, 12 May 2010 19:50:57 +0000</pubDate>
		<dc:creator>Michal</dc:creator>
				<category><![CDATA[Administration]]></category>
		<category><![CDATA[/etc/release]]></category>
		<category><![CDATA[psrinfo]]></category>
		<category><![CDATA[uname]]></category>

		<guid isPermaLink="false">http://www.solarisblog.org/?p=184</guid>
		<description><![CDATA[Let&#8217;s take a look how to find out all interesting information about hardware and software (Solaris OS) on your SUN box. We can start with the uname command. The most interesting options are uname -a and uname -X. $ uname -a SunOS test1 5.8 Generic_108528-26 sun4u sparc SUNW,Sun-Fire-880 $ Output above is telling me that [...]]]></description>
		<wfw:commentRss>http://www.solarisblog.org/administration/check-your-hardware-and-software-configuration/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How To Configure The /etc/gateways File</title>
		<link>http://www.solarisblog.org/network/how-to-configure-the-etcgateways-file/</link>
		<comments>http://www.solarisblog.org/network/how-to-configure-the-etcgateways-file/#comments</comments>
		<pubDate>Mon, 10 May 2010 00:35:08 +0000</pubDate>
		<dc:creator>Michal</dc:creator>
				<category><![CDATA[Network]]></category>
		<category><![CDATA[/etc/gateways]]></category>
		<category><![CDATA[route]]></category>

		<guid isPermaLink="false">http://www.solarisblog.org/?p=178</guid>
		<description><![CDATA[When in.routed is started up, it reads the /etc/gateways to possibly find and add additional static routes to routing table. Gateways should be marked passive if they are not expected to exchange routing information. Gateways marked active should have in.routed process running on that machine thus they should be willing to exchange routing information. Active [...]]]></description>
		<wfw:commentRss>http://www.solarisblog.org/network/how-to-configure-the-etcgateways-file/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Solaris 8 and 9 Patch Return Codes</title>
		<link>http://www.solarisblog.org/administration/solaris-8-and-9-patch-return-codes/</link>
		<comments>http://www.solarisblog.org/administration/solaris-8-and-9-patch-return-codes/#comments</comments>
		<pubDate>Thu, 06 May 2010 23:45:44 +0000</pubDate>
		<dc:creator>Michal</dc:creator>
				<category><![CDATA[Administration]]></category>
		<category><![CDATA[patchadd]]></category>

		<guid isPermaLink="false">http://www.solarisblog.org/?p=158</guid>
		<description><![CDATA[When adding patch to the Solaris box you sometimes get these error messages.  Here is what they all mean. Exit_code Meaning 0 No error 1 Usage error 2 Attempt to apply a patch that's already been applied 3 Effective UID is not root 4 Attempt to save original files failed 5 pkgadd failed 6 Patch [...]]]></description>
		<wfw:commentRss>http://www.solarisblog.org/administration/solaris-8-and-9-patch-return-codes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How To Control Root Access To The System</title>
		<link>http://www.solarisblog.org/security/how-to-control-root-access-to-the-system/</link>
		<comments>http://www.solarisblog.org/security/how-to-control-root-access-to-the-system/#comments</comments>
		<pubDate>Thu, 06 May 2010 02:34:45 +0000</pubDate>
		<dc:creator>Michal</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[/etc/default/login]]></category>
		<category><![CDATA[root]]></category>

		<guid isPermaLink="false">http://www.solarisblog.org/?p=151</guid>
		<description><![CDATA[You can control root access to the system by setting parameters in the /etc/default/login file. The /etc/default/login file establish default parameters for users when they log in to the system. One of the parameters you can set is CONSOLE variable. There are three possible states that restrict access to the root account: If CONSOLE variable [...]]]></description>
		<wfw:commentRss>http://www.solarisblog.org/security/how-to-control-root-access-to-the-system/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>FATAL: System Is Not Bootable, Boot Command Is Disabled</title>
		<link>http://www.solarisblog.org/administration/fatal-system-is-not-bootable-boot-command-is-disabled/</link>
		<comments>http://www.solarisblog.org/administration/fatal-system-is-not-bootable-boot-command-is-disabled/#comments</comments>
		<pubDate>Wed, 05 May 2010 19:55:05 +0000</pubDate>
		<dc:creator>Michal</dc:creator>
				<category><![CDATA[Administration]]></category>
		<category><![CDATA[auto-boot?]]></category>
		<category><![CDATA[OBP]]></category>
		<category><![CDATA[reset-all]]></category>

		<guid isPermaLink="false">http://www.solarisblog.org/?p=143</guid>
		<description><![CDATA[If you come across following error on your SUN box, do not panic. Although this message is not too informative and looks little bit scary there is easy solution how to make your system bootable again. First of all, what is the reason for that message? Main reason would be interruption of the boot process [...]]]></description>
		<wfw:commentRss>http://www.solarisblog.org/administration/fatal-system-is-not-bootable-boot-command-is-disabled/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
