<?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 10</title>
	<atom:link href="http://blog.dispatched.ch/tag/solaris-10/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>Juno on Solaris 10</title>
		<link>http://blog.dispatched.ch/2009/05/18/juno-on-solaris-10/</link>
		<comments>http://blog.dispatched.ch/2009/05/18/juno-on-solaris-10/#comments</comments>
		<pubDate>Mon, 18 May 2009 13:23:30 +0000</pubDate>
		<dc:creator>Alain M. Lafon</dc:creator>
				<category><![CDATA[articles]]></category>
		<category><![CDATA[Compile Python]]></category>
		<category><![CDATA[howto]]></category>
		<category><![CDATA[Juno]]></category>
		<category><![CDATA[lightweight]]></category>
		<category><![CDATA[python]]></category>
		<category><![CDATA[Solaris 10]]></category>
		<category><![CDATA[tutorial]]></category>
		<category><![CDATA[webframework]]></category>

		<guid isPermaLink="false">http://blog.dispatched.ch/?p=753</guid>
		<description><![CDATA[Juno is an incredibly lightweight webframework. Using Python as backend, it fullfills my very need for just about every small application I want to deploy against the web. It has no need for big runtimes on the server, no files to configure a great many files and most importantly: there&#8217;s no coding overhead &#8211; the [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://brianreily.com/project/juno" class="broken_link">Juno</a> is an incredibly lightweight webframework. Using Python as backend, it fullfills my very need for just about every small application I want to deploy against the web. It has no need for big runtimes on the server, no files to configure a great many files and most importantly: there&#8217;s no coding overhead &#8211; the programmer defines only the distinctively wanted features.<br />
However, installing Juno on Solaris 10 isn&#8217;t quite as easy as described in Junos&#8217; documentation. Solaris ships with Python 2.4, but Juno depends in Jinja2(a templating engine) which itself depends on Python 2.5+. Even installing Blastwave&#8217;s or Sunfreeware&#8217;s version won&#8217;t help. But that&#8217;s no biggie since compiling your own Python is incredibly easy.</p>
<ol>
<li>Get, compile and install Python (I have used version 2.5.4)
<ul>
<li><a href="http://www.python.org/download/releases/" target="_blank">http://www.python.org/download/releases/</a></li>
<li>unpack</li>
<li>make sure you have a recent version of GCC installed</li>
<li>./configure &amp;&amp; make &amp;&amp; make install</li>
<li>as a result Python will be installed in /usr/local</li>
</ul>
</li>
<p></p>
<li>Get, compile and install Setuptools
<ul>
<li><a href="http://pypi.python.org/pypi/setuptools" target="_self">http://pypi.python.org/pypi/setuptools</a></li>
<li>unpack</li>
<li>python setup.py install</li>
</ul>
<p>
</li>
<li> Get, compile and install  pysqlite
<ul>
<li><a href="http://oss.itsystementwicklung.de/trac/pysqlite/wiki/WikiStart#Downloads" target="_blank">http://oss.itsystementwicklung.de/trac/pysqlite/wiki/WikiStart#Downloads</a></li>
<li>unpack</li>
<li>add line &#8220;library_dirs=/usr/local/lib&#8221; to pysqlite-x.y.z/setup.cfg</li>
<li>globally export your library paths:
<li>LD_LIBRARY_PATH=/opt/csw/lib/:/usr/lib/:/lib/:/usr/local/lib:$LD_LIBRARY_PATH ; export LD_LIBRARY_PATH</li>
<li>python setup.py install</li>
</ul>
</li>
<li>easy_install install sqlalchemy
</li>
<p></p>
<li>easy_install jinja2</li>
<p></p>
<li>Get, compile and install Juno
<ul>
<li><a href="http://brianreily.com/project/juno" target="_blank" class="broken_link"> http://brianreily.com/project/juno</a></li>
<li>python setup.py install</li>
</ul>
<p>
</li>
</ol>
<p>Enjoy.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.dispatched.ch/2009/05/18/juno-on-solaris-10/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>NVIDIA TV Out (Solaris)</title>
		<link>http://blog.dispatched.ch/2008/10/04/nvidia-tv-out-solaris/</link>
		<comments>http://blog.dispatched.ch/2008/10/04/nvidia-tv-out-solaris/#comments</comments>
		<pubDate>Sat, 04 Oct 2008 16:21:53 +0000</pubDate>
		<dc:creator>Alain M. Lafon</dc:creator>
				<category><![CDATA[articles]]></category>
		<category><![CDATA[NVIDIA]]></category>
		<category><![CDATA[Solaris 10]]></category>
		<category><![CDATA[TV]]></category>
		<category><![CDATA[TV OUT]]></category>

		<guid isPermaLink="false">http://gefechtsdienst.de/?p=100</guid>
		<description><![CDATA[Solaris Express in any recent version will have out of the box NVidia support if you install the Developer Edition or the Community Release. This driver doesn&#8217;t differ (at least as far as I know) from the Linux device driver, so setting up secondary screens and tv-outs is quite the same. There even is a [...]]]></description>
			<content:encoded><![CDATA[<p>Solaris Express in any recent version will have out of the box NVidia support if you install the Developer Edition or the Community Release. This driver doesn&#8217;t differ (at least as far as I know) from the Linux device driver, so setting up secondary screens and tv-outs is quite the same. There even is a preinstalled tool &#8220;nvidia-settings&#8221; which might help you do the job, but it didn&#8217;t help me that much since you have to implement at least the second screen by hand in your X configuration file.<br />
Before you begin, make a backup of your working /etc/X11/xorg.conf file.<br />
We will now take a look at how this xorg.conf file has to be changed for TV-Out support.</p>
<ul>
<li> Change the &#8220;Device&#8221; section that it looks like this:
<pre class="box">
Section "Device"
    Identifier              "Videocard0"
    Driver                  "nvidia"
    # optional (find out with "$ Xorg -scanpci")
    BusID                  "[Your BusID, e.g.: PCI:2:0:0]"
    Screen                0
EndSection
</pre>
<li> Add a new &#8220;Device&#8221; section for the TV, just like the one before, but change &#8220;Screen 0&#8243; to &#8220;Screen 1&#8243; and &#8220;Videocard0&#8243; to &#8220;Videocard1&#8243;
<li> Change the &#8220;Monitor&#8221; section as follows:
<pre class="box">
Section "Monitor"
   Identifier        "Monitor0"
   HorizSync      30.0 - 100.0       #adjust to your monitor
   VertRefresh   50.0 - 94.0         #adjust to your monitor
   Option            "DPMS"
EndSection
</pre>
<li>  Add a new &#8220;Monitor&#8221; section for the TV, just like the one before, but change &#8220;Monitor0&#8243; to &#8220;Monitor1&#8243;
<li> Now we configure the possible resolutions for CRT and TV
<p>You will have to adjust them to your liking. &#8220;Screen0&#8243; deals with the CRT, &#8220;Screen1&#8243; with the TV.</p>
<pre class="box">

Section "Screen"
    Identifier     "Screen0"
    Device         "Videocard0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "metamodes" "CRT: 1600x1200 +0+0; CRT: 1400x1050 +0+0;
    CRT: 1280x1024 +0+0; CRT: 1024x768 +0+0; CRT: 800x600 +0+0;
    CRT: 640x480 +0+0"
    SubSection     "Display"
        Depth       24
        Modes      "1600x1200" "1280x1024" "1024x768" "800x600" "640x480"
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen1"
    Device         "Videocard1"
    Monitor        "Monitor1"
    DefaultDepth    24
    Option         "metamodes" "TV: 1024x768 +0+0"
    SubSection     "Display"
        Depth       24
        Modes      "1600x1200" "1280x1024" "1024x768" "800x600" "640x480"
    EndSubSection
EndSection
</pre>
<li> Now you we are physically set up and can define a Serverlayout which defines how the monitors do correspond to each other.<br />
In this example the CRT will be the primary monitor whereas the TV can be reached by dragging the mouse cursor out the left side of your monitor.</p>
<pre class="box">
Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 1024 0
    Screen      1  "Screen1" LeftOf "Screen0"
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
EndSection
</pre>
</ul>
<p>Now we are all done. Save xorg.conf and restart your Xserver(in Solaris logging out and in again will do the job).<br />
A working copy of my file as an example can be downloaded <a href="http://blogs.sun.com/preek/resource/xorg.conf">here</a>.</p>
</td>
</tr>
</table>
]]></content:encoded>
			<wfw:commentRss>http://blog.dispatched.ch/2008/10/04/nvidia-tv-out-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>
	</channel>
</rss>
