<?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>Alain M. Lafon &#187; Solaris</title>
	<atom:link href="http://blog.dispatched.ch/tag/solaris/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.dispatched.ch</link>
	<description>code, life and struggles thereof</description>
	<lastBuildDate>Wed, 18 Aug 2010 14:58:50 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>TexLive on Solaris 10</title>
		<link>http://blog.dispatched.ch/2008/10/04/texlive-on-solaris-10/</link>
		<comments>http://blog.dispatched.ch/2008/10/04/texlive-on-solaris-10/#comments</comments>
		<pubDate>Sat, 04 Oct 2008 16:23:20 +0000</pubDate>
		<dc:creator>Alain M. Lafon</dc:creator>
				<category><![CDATA[articles]]></category>
		<category><![CDATA[Solaris]]></category>
		<category><![CDATA[TexLive]]></category>

		<guid isPermaLink="false">http://gefechtsdienst.de/?p=107</guid>
		<description><![CDATA[TexLive is a very decent Latex implementation, however if you want to write DIN conformable letters using g-brief you might get an error message like that: ! LaTeX Error: Command \Telefon already defined.Or name \end... illegal, see p.192 of the manual. See the LaTeX manual or LaTeX Companion for explanation.Type H for immediate help. ... [...]]]></description>
			<content:encoded><![CDATA[<p><a href="www.tug.org/texlive/" class="broken_link">TexLive</a> is a very decent Latex implementation, however if you want to write DIN conformable letters using g-brief you might get an error message like that:</p>
<pre class="box">! LaTeX Error: Command \Telefon already defined.Or name \end... illegal, see p.192 of the manual.

See the LaTeX manual or LaTeX Companion for explanation.Type  H   for immediate help. ...

l.48 \newcommand\Telefon{\mvchr{84}}</pre>
<p>This bug is in g-brief with newer versions of <em>marvosym.sty</em>. So all you have to do is edit line 48 of /texlive/texmf-dist/tex/marvosym.sty and uncomment it.</p>
<p>This bug might affect all unices, not only Solaris.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.dispatched.ch/2008/10/04/texlive-on-solaris-10/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Sun RAY with PS2 Keyboards</title>
		<link>http://blog.dispatched.ch/2008/10/04/sun-ray-with-ps2-keyboards/</link>
		<comments>http://blog.dispatched.ch/2008/10/04/sun-ray-with-ps2-keyboards/#comments</comments>
		<pubDate>Sat, 04 Oct 2008 16:22:53 +0000</pubDate>
		<dc:creator>Alain M. Lafon</dc:creator>
				<category><![CDATA[articles]]></category>
		<category><![CDATA[installation]]></category>
		<category><![CDATA[keyboard]]></category>
		<category><![CDATA[ps2]]></category>
		<category><![CDATA[setup]]></category>
		<category><![CDATA[Solaris]]></category>
		<category><![CDATA[sun ray]]></category>

		<guid isPermaLink="false">http://gefechtsdienst.de/?p=105</guid>
		<description><![CDATA[SUN Ray with PS2 keyboards If you want to hook up a Sun Ray at home, you might want to use your favourite old PS2 keyboard attached via some USB connector. Depending on your keyboard layout you might be disappointed by the result, because it will be standard US. That&#8217;s because the PS2 keyboard isn&#8217;t [...]]]></description>
			<content:encoded><![CDATA[<p><b>SUN Ray with PS2 keyboards</b><br />
If you want to hook up a Sun Ray at home, you might want to use your favourite old PS2 keyboard attached via some USB connector. Depending on your keyboard layout you might be disappointed by the result, because it will be standard US. That&#8217;s because the PS2 keyboard isn&#8217;t designed for the Ray clients and won&#8217;t prompt back a valid layout to the server which will then assume a standard scenario.<br />
There is a simple solution to this problem; in the file &#8220;/usr/openwin/etc/keytables/keytable.map&#8221; edit the entry</p>
<pre class="box">

6      0       US6.kt
</pre>
<p>and rewrite it to your favourite layout(British English in this case)</p>
<pre class="box">
6       0      UK6.kt
</pre>
<p>There is one drawback however; from this point on this is going to be the single standard fallback layout for all keyboards hooked via SUN Ray clients to your server which won&#8217;t report a valid layout themselves. So if you want to use different layouts on different clients you might want to check the xkb option in &#8220;/opt/SUNWut/bin/utxconfig&#8221;, which I haven&#8217;t done until now.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.dispatched.ch/2008/10/04/sun-ray-with-ps2-keyboards/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Multiple IP addresses on one interface (Solaris)</title>
		<link>http://blog.dispatched.ch/2008/10/04/multiple-ip-addresses-on-one-interface-solaris/</link>
		<comments>http://blog.dispatched.ch/2008/10/04/multiple-ip-addresses-on-one-interface-solaris/#comments</comments>
		<pubDate>Sat, 04 Oct 2008 16:20:53 +0000</pubDate>
		<dc:creator>Alain M. Lafon</dc:creator>
				<category><![CDATA[articles]]></category>
		<category><![CDATA[interface]]></category>
		<category><![CDATA[interfaces]]></category>
		<category><![CDATA[ip adress]]></category>
		<category><![CDATA[multiple ip adresses]]></category>
		<category><![CDATA[Solaris]]></category>

		<guid isPermaLink="false">http://gefechtsdienst.de/?p=98</guid>
		<description><![CDATA[Like we mentioned earlier we are in the middle of configuring a Fire 280R server for our needs. Yesterday we finally were able to patch some real Internet addresses on the NICs, as well as new local addresses, so now we finally are online^^ While configuring we figured that there are at least three potential [...]]]></description>
			<content:encoded><![CDATA[<p>	Like we mentioned earlier we are in the middle of configuring a Fire 280R server for our needs. Yesterday we finally were able to patch some real Internet addresses on the NICs, as well as new local addresses, so now we finally are online^^<br />
While configuring we figured that there are at least three potential needs to assign multiple IP addresses to a single interface.</p>
<p>1. To do a quick test where the configuration won&#8217;t have to survive a reboot<br />
2. On an interface in a global zone<br />
3. On an interface in a non-global zone</p>
<p>These are the solutions we used:</p>
<p><b>1</b></p>
<pre class="box">
$ ifconfig abrX:Y plumb
</pre>
<p>while &#8220;abrX&#8221; is the abbreviation for an installed interface.<br />
Now you can use the new interface abrX:Y as you want.</p>
<p><b>2</b><br />
We needed it to have an an external(Internet) and an internal address. So we made an entry in <em>/etc/hosts</em> for the primary address in the old fashioned way(we do not yet use NWAM):</p>
<pre class="box">
10.5.250.100    fire
</pre>
<p>while we put the other addresses in <em>/etc/hostname.abrX</em>:</p>
<pre class="box">
fire
addif 141.72.100.100/24
</pre>
<p>where /24 implies: netmask ffffff00 broadcast 141.72.100.255</p>
<p><b>3</b><br />
We wanted the interfaces to be visible from the global zone via a local address while being available from the Internet. Therefore we defined a local address as in <em>2</em> via /etc/hosts and /etc/hostname.abrX, but we also included the Internet address in the zone configuration:</p>
<pre class="box">
$ zonecfg -z zone1
zonecfg:zone1> select net physical=abrX
zonecfg:zone1:net> set address= 141.72.100.101/24
zonecfg:zone1:net> end
zonecfg:zone1> commit
zonecfg:zone1> exit
</pre>
<p>
We will now take a look at IP instances, because using them we can achieve to only have the non-global zones visible in the Internet, while the global zone is only vulnerable in the local subnet.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.dispatched.ch/2008/10/04/multiple-ip-addresses-on-one-interface-solaris/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>First installation troubles (Solaris)</title>
		<link>http://blog.dispatched.ch/2008/10/04/first-installation-troubles-solaris/</link>
		<comments>http://blog.dispatched.ch/2008/10/04/first-installation-troubles-solaris/#comments</comments>
		<pubDate>Sat, 04 Oct 2008 16:19:28 +0000</pubDate>
		<dc:creator>Alain M. Lafon</dc:creator>
				<category><![CDATA[articles]]></category>
		<category><![CDATA[installation]]></category>
		<category><![CDATA[opensolaris]]></category>
		<category><![CDATA[Solaris]]></category>
		<category><![CDATA[Solaris 10]]></category>

		<guid isPermaLink="false">http://gefechtsdienst.de/?p=92</guid>
		<description><![CDATA[Various small problems VIM / Cursor Keys If you wonder why VIM keeps writing &#8216;A&#8217;, &#8216;B&#8217;, &#8216;C&#8217;, &#8216;D&#8217; on your screen when it is supposed just to move the cursor in writing mode, the answer is that the cursor keys are not being mapped the right way. The solution is to extend your favourite .vimrc [...]]]></description>
			<content:encoded><![CDATA[<h1>Various small problems</h1>
</p>
<p><b>VIM / Cursor Keys</b><br />
If you wonder why VIM keeps writing &#8216;A&#8217;, &#8216;B&#8217;, &#8216;C&#8217;, &#8216;D&#8217; on your screen when it is supposed just to move the cursor in writing mode, the answer is that the cursor keys are not being mapped the right way. The solution is to extend your favourite .vimrc file with:</p>
<pre class="box">
map! ^[OD ^[h
map! ^[OC ^[l
map! ^[OA ^[k
map! ^[OB ^[j
</pre>
<p><b>&#8220;/usr/ucb/cc: language optional software package not installed&#8221;</b><br />
/usr/ucb/cc is only a wrapper to a real C compiler. Solaris 10 won&#8217;t have a C compiler preinstalled, normally. This means that you will have to install it yourself (Sun Studio would be a good idea, too). All you have to see to then is that your PATH is set correctly; meaning that /usr/ucb is either deleted or after your real compiler.</p>
<p></p>
<p><b>&#8220;WARNING: loghost could not be resolved.&#8221;</b><br />
That&#8217;s because your syslogd doesn&#8217;t have a defined host to work on. To fix it simply add &#8220;loghost&#8221; to your 127.0.0.1 entry in the /etc/hosts file</p>
<pre class="box">
127.0.0.1       localhost loghost
</pre>
<p><b>&#8220;Sendmail: My unqualified host name (domain) unknown;&#8221;</b><br />
If you get this warning on computer startup, then you haven&#8217;t configured a fully qualified domain name for your system. If you don&#8217;t need a mailing system on your computer the solution is easy by simply disabling the service via:</p>
<pre class="box">
svcadm disable sendmail
</pre>
<p>If you need a working mailsystem, there is a <a href="http://www.sun.com/bigadmin/features/articles/config_sendmail.html">howto</a> from SUN.
          </td>
</tr>
</table>
]]></content:encoded>
			<wfw:commentRss>http://blog.dispatched.ch/2008/10/04/first-installation-troubles-solaris/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>AMP stack in Solaris 05/08</title>
		<link>http://blog.dispatched.ch/2008/10/04/amp-stack-in-solaris-0508/</link>
		<comments>http://blog.dispatched.ch/2008/10/04/amp-stack-in-solaris-0508/#comments</comments>
		<pubDate>Sat, 04 Oct 2008 16:18:27 +0000</pubDate>
		<dc:creator>Alain M. Lafon</dc:creator>
				<category><![CDATA[articles]]></category>
		<category><![CDATA[amp]]></category>
		<category><![CDATA[lamp]]></category>
		<category><![CDATA[samp]]></category>
		<category><![CDATA[Solaris]]></category>

		<guid isPermaLink="false">http://gefechtsdienst.de/?p=90</guid>
		<description><![CDATA[Most webservers do have a need for a decent AMP stack, but Solaris 05/08 doesn&#8217;t quite offer a solution out of the box, but if you know where to look you&#8217;re not far away from having a fine implementation. MySQL5I have made good experiences using MySQL5 from blastwave. Unfortunately it doesn&#8217;t run out of the [...]]]></description>
			<content:encoded><![CDATA[<p>Most webservers do have a need for a decent AMP stack, but Solaris 05/08 doesn&#8217;t quite offer a solution out of the box, but if you know where to look you&#8217;re not far away from having a fine implementation.</p>
<ul></li>
<li><strong>MySQL5</strong>I have made good experiences using MySQL5 from <a href="http://www.blastwave.org">blastwave</a>. Unfortunately it doesn&#8217;t run out of the box even tough it integrates nicely with SMF. When mysql is being called after installation you will see this error message:
<pre class="box">Warning: mysql(): Can't connect to local MySQL server through socket '/tmp/mysql.sock'</pre>
<p>The simple reason is that cswmysql5 couldn&#8217;t start properly, because there is no default config file. After copying the config file to the right location you can start the installation:</p>
<pre class="box">$ cp /opt/csw/mysql5share/mysql/my-small.cnf /opt/csw/mysql5/my.cnf
$ /opt/csw/mysql5/bin/mysql_install_db
...
$ chown -R mysql:mysql /opt/csw/mysql5/var
$ svcadm disable cswmysql5; svcadm enable cswmysql5</pre>
</li>
<li><strong>Apache2</strong>
<pre class="box">$ pkg-get install apache2</pre>
</li>
<li><strong>PHP</strong>
<pre class="box">$ pkg-get install php5</pre>
</li>
<li><strong>Needed modules</strong>
<pre class="box">$ pkg-get install ap2_modphp5
$ pkg-get install php5_gd
$ pkg-get install
php5_mysql</pre>
<p>Now all that&#8217;s left is to integrate PHP support into apache which is done by adding the following lines in your /opt/csw/apache2/etc/httpd.conf:</p>
<pre class="box">LoadModule php5_module /opt/csw/apache2/libexec/libphp5.so
&lt;IfModule mod_php5.c&gt;
  AddType application/x-httpd-php .php .phtml .php3
  AddType application/x-httpd-php-source .phps
&lt;/IfModule&gt;</pre>
<p>Now disable apache2, restart cswapache2 and you&#8217;re done.
</ul>
]]></content:encoded>
			<wfw:commentRss>http://blog.dispatched.ch/2008/10/04/amp-stack-in-solaris-0508/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
