<?xml version="1.0" encoding="utf-8"?><?xml-stylesheet title="XSL formatting" type="text/xsl" href="http://blog.thilelli.net/feed/rss2/xslt" ?><rss version="2.0"
  xmlns:dc="http://purl.org/dc/elements/1.1/"
  xmlns:content="http://purl.org/rss/1.0/modules/content/"
  xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
  <title>blog'o thnet  - Comments</title>
  <link>http://blog.thilelli.net/</link>
  <atom:link href="http://blog.thilelli.net/feed/rss2/comments" rel="self" type="application/rss+xml"/>
  <description>thnet, the blog of Julien Gabel
What is to say about my (mostly) IT-related world these days</description>
  <language>en</language>
  <pubDate>Sun, 16 Nov 2008 20:29:11 +0100</pubDate>
  <copyright>Copyright© 2002-2008, Julien Gabel</copyright>
  <docs>http://blogs.law.harvard.edu/tech/rss</docs>
  <generator>Dotclear</generator>
  
    
    
    <item>
    <title>Solaris vs. RHEL Costs And Features Comparisons - Julien Gabel</title>
    <link>http://blog.thilelli.net/post/2008/10/26/Solaris-vs-RHEL-Costs-And-Features-Comparisons#c8357295</link>
    <guid isPermaLink="false">urn:md5:1cc7d7b59f83dc729058b536d073279d</guid>
    <pubDate>Fri, 14 Nov 2008 19:05:21 +0100</pubDate>
    <dc:creator>Julien Gabel</dc:creator>
    
    <description>&lt;p&gt;Hi Jim,&lt;/p&gt;
&lt;p&gt;Thank you for posting this comment, for your updated chart, and your great
inputs as a Solaris, and OpenSolaris evangelist. Keep up the good work!&lt;/p&gt;</description>
  </item>
      
    
    <item>
    <title>Solaris vs. RHEL Costs And Features Comparisons - Jim Laurent</title>
    <link>http://blog.thilelli.net/post/2008/10/26/Solaris-vs-RHEL-Costs-And-Features-Comparisons#c8356607</link>
    <guid isPermaLink="false">urn:md5:3512f40f0d15aa1dee18d572a37500ff</guid>
    <pubDate>Thu, 13 Nov 2008 23:00:40 +0100</pubDate>
    <dc:creator>Jim Laurent</dc:creator>
    
    <description>&lt;p&gt;Julian,&lt;/p&gt;
&lt;p&gt;Thanks for posting this. I've actually created an updated version of the
Solaris/RHEL comparison chart since the posting you referenced.&lt;/p&gt;
&lt;p&gt;The new chart includes OpenSolaris and Windows 2003 server and can be found
at:&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://blogs.sun.com/jimlaurent/entry/comparing_solaris_opensolaris_red_hat&quot; title=&quot;http://blogs.sun.com/jimlaurent/entry/comparing_solaris_opensolaris_red_hat&quot; rel=&quot;nofollow&quot;&gt;http://blogs.sun.com/jimlaurent/ent...&lt;/a&gt;&lt;/p&gt;</description>
  </item>
      
    
    <item>
    <title>Announcing Solaris 10 10/08 - Mick Russom</title>
    <link>http://blog.thilelli.net/post/2008/09/16/Announcing-Solaris-10-10/08#c8345732</link>
    <guid isPermaLink="false">urn:md5:2cf4b7e7d0e518f836c0eb48271d1344</guid>
    <pubDate>Tue, 28 Oct 2008 22:55:39 +0100</pubDate>
    <dc:creator>Mick Russom</dc:creator>
    
    <description>&lt;p&gt;Is the install process on x86 still a 32-bit kernel ?&lt;/p&gt;
&lt;p&gt;If Sun hasn't fixed the &amp;quot;I'm too stupid to install on disk with 1TB or
larger partitions&amp;quot; I'm going to be really pissed.&lt;/p&gt;
&lt;p&gt;I really wish Sun would dump the 32-bit installer, the time has come.&lt;/p&gt;</description>
  </item>
      
    
    <item>
    <title>Discrepancies Between df And du Outputs - Julien Gabel</title>
    <link>http://blog.thilelli.net/post/2008/10/18/Discrepancies-Between-df-And-du-Outputs#c8339570</link>
    <guid isPermaLink="false">urn:md5:81ebb4c16ecd5f8cec2e6d835b65cf04</guid>
    <pubDate>Sun, 19 Oct 2008 21:31:41 +0200</pubDate>
    <dc:creator>Julien Gabel</dc:creator>
    
    <description>&lt;p&gt;Thank you, Irwan, for your comment. By &lt;em&gt;truncate the unlinked file&lt;/em&gt;,
I mean something such as &lt;code&gt;cat /dev/null &amp;gt; /proc/1252/fd/3&lt;/code&gt;, in my
previous example.&lt;/p&gt;</description>
  </item>
      
    
    <item>
    <title>Discrepancies Between df And du Outputs - Irwan</title>
    <link>http://blog.thilelli.net/post/2008/10/18/Discrepancies-Between-df-And-du-Outputs#c8339421</link>
    <guid isPermaLink="false">urn:md5:c0862355a3fb0be2e8303c4c0f33bfb0</guid>
    <pubDate>Sun, 19 Oct 2008 17:38:28 +0200</pubDate>
    <dc:creator>Irwan</dc:creator>
    
    <description>&lt;p&gt;Nice post! I'm also facing this situation when working in a complex
enterprise environment. Could you elaborate more on 'Truncate the unlinked
file' and probably give an example?&lt;/p&gt;</description>
  </item>
      
    
    <item>
    <title>Fake the hostid of a Solaris Zone - Julien Gabel</title>
    <link>http://blog.thilelli.net/post/2006/06/17/Fake-the-hostid-of-a-Solaris-Zone#c8331977</link>
    <guid isPermaLink="false">urn:md5:e835cf6d358dd36c8a0e237196902f0d</guid>
    <pubDate>Sun, 05 Oct 2008 21:00:42 +0200</pubDate>
    <dc:creator>Julien Gabel</dc:creator>
    
    <description>&lt;p&gt;Well, this solution is not the proper, and with recent Solaris releases you
can do the same thing as with the &lt;code&gt;zhostid&lt;/code&gt;, but directly from the
&lt;a href=&quot;http://blog.thilelli.net/post/2008/10/06/Fake-The-hostid-Of-A-Solaris-Zone-Updated&quot; hreflang=&quot;en&quot; rel=&quot;nofollow&quot;&gt;non-global zone&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Using the &lt;code&gt;LD_PRELOAD&lt;/code&gt; trick, didn't forget to unset the variable
just after executing the &lt;code&gt;hostid&lt;/code&gt; command.&lt;/p&gt;</description>
  </item>
      
    
    <item>
    <title>Fake the hostid of a Solaris Zone - gerard</title>
    <link>http://blog.thilelli.net/post/2006/06/17/Fake-the-hostid-of-a-Solaris-Zone#c8330959</link>
    <guid isPermaLink="false">urn:md5:e244841901f2a3b628d9e82c381fb3e1</guid>
    <pubDate>Fri, 03 Oct 2008 09:48:40 +0200</pubDate>
    <dc:creator>gerard</dc:creator>
    
    <description>&lt;p&gt;hello,&lt;br /&gt;
i'm trying the second solution, it works for hostid, but fails with other
commands:&lt;br /&gt;
reglisse-root% ptree 11984&lt;br /&gt;
ld.so.1: ptree: fatal: /tmp/newhostid.so: wrong ELF class: ELFCLASS32&lt;br /&gt;
Killed&lt;br /&gt;
reglisse-root% ldd /usr/bin/ptree&lt;br /&gt;
/tmp/newhostid.so&lt;br /&gt;
libc.so.1 =&amp;gt; /lib/libc.so.1&lt;br /&gt;
libgcc_s.so.1 =&amp;gt; /usr/sfw/lib/libgcc_s.so.1&lt;br /&gt;
libm.so.2 =&amp;gt; /lib/libm.so.2&lt;br /&gt;
/platform/SUNW,Sun-Fire-T200/lib/libc_psr.so.1&lt;/p&gt;
&lt;p&gt;any idea?&lt;/p&gt;
&lt;p&gt;thanks,&lt;/p&gt;</description>
  </item>
      
    
    <item>
    <title>How to Patch a Live System Mirrored with SVM - Julien Gabel</title>
    <link>http://blog.thilelli.net/post/2006/05/01/How-to-Patch-a-Live-System-Mirrored-with-SVM#c8259562</link>
    <guid isPermaLink="false">urn:md5:0e6ed8eb67b5078b3ab449070e3d9f6a</guid>
    <pubDate>Fri, 25 Jul 2008 22:00:56 +0200</pubDate>
    <dc:creator>Julien Gabel</dc:creator>
    
    <description>&lt;p&gt;Absolutely. In fact, we proceed in a similar way right now. The point is, it
was not planned beforehand on the system I worked on in this post to used Live
Upgrade to update/upgrade the environment. Thank you for your comments.&lt;/p&gt;</description>
  </item>
      
    
    <item>
    <title>How to Patch a Live System Mirrored with SVM - GMO</title>
    <link>http://blog.thilelli.net/post/2006/05/01/How-to-Patch-a-Live-System-Mirrored-with-SVM#c8259519</link>
    <guid isPermaLink="false">urn:md5:7883ffece7243153ca6099ecf6cd43b0</guid>
    <pubDate>Fri, 25 Jul 2008 21:07:49 +0200</pubDate>
    <dc:creator>GMO</dc:creator>
    
    <description>&lt;p&gt;Hmm, we do it a little different than this. We simply create one BE on slice
0 of drive #1 and mirror it to slice 0 of drive #2. We then format another
slice (say slice #6) and make it the same size as slice 0. This will be our
Secondary BE and it is mirrored to slice 6 of drive #2. This way we never break
a mirror (which leaves the system vulnerable during the patching period and we
keep our old BE around until we patch again.&lt;/p&gt;
&lt;p&gt;GMO&lt;/p&gt;</description>
  </item>
      
    
    <item>
    <title>How to Patch a Live System Mirrored with SVM - Julien Gabel</title>
    <link>http://blog.thilelli.net/post/2006/05/01/How-to-Patch-a-Live-System-Mirrored-with-SVM#c8258138</link>
    <guid isPermaLink="false">urn:md5:9ef535237bbbd5427e56ae7a74f222ab</guid>
    <pubDate>Thu, 24 Jul 2008 15:58:43 +0200</pubDate>
    <dc:creator>Julien Gabel</dc:creator>
    
    <description>&lt;p&gt;The fact is &lt;code&gt;fsck&lt;/code&gt; works as excepted using the raw device, the
block device or the mount point (if known from the &lt;code&gt;/etc/vfstab&lt;/code&gt;
configuration file). But you are right, the proper way is to mention the raw
device as argument--from the &lt;code&gt;fsck&lt;/code&gt; manual page:&lt;/p&gt;
&lt;blockquote&gt;special represents the character special device on which the file
system resides, for example, /dev/rdsk/c1t0d0s7. Note: the character special
device, not the block special device, should be used. fsck will not work if the
block device is mounted.&lt;/blockquote&gt;</description>
  </item>
      
    
    <item>
    <title>How to Patch a Live System Mirrored with SVM - Mike Purton</title>
    <link>http://blog.thilelli.net/post/2006/05/01/How-to-Patch-a-Live-System-Mirrored-with-SVM#c8258016</link>
    <guid isPermaLink="false">urn:md5:7f563e3f5a009a381f0d4ea84df4e7db</guid>
    <pubDate>Thu, 24 Jul 2008 13:13:18 +0200</pubDate>
    <dc:creator>Mike Purton</dc:creator>
    
    <description>&lt;p&gt;Great doc very helpful :-)&lt;/p&gt;
&lt;p&gt;My only comment is on the fsck command, you seem to be running fsck on the
block device /dev/dsk rather than the raw device /dev/rdsk&lt;/p&gt;
&lt;p&gt;Regards&lt;/p&gt;
&lt;p&gt;Mike&lt;/p&gt;</description>
  </item>
      
    
    <item>
    <title>Getting Emulex HBA Information on a GNU/Linux System - suresh</title>
    <link>http://blog.thilelli.net/post/2007/06/09/Getting-Emulex-HBA-Information-on-a-GNU/Linux-System#c8190102</link>
    <guid isPermaLink="false">urn:md5:8c6aba766a6f68331134ecb3143255cb</guid>
    <pubDate>Tue, 17 Jun 2008 13:25:51 +0200</pubDate>
    <dc:creator>suresh</dc:creator>
    
    <description>&lt;p&gt;It was really nice article Julian. People like me are searching for lot of
information since I'm getting into storage side. Please do write such
information often.&lt;/p&gt;</description>
  </item>
      
    
    <item>
    <title>Comparison: EMC PowerPath vs. GNU/Linux dm-multipath - Julien Gabel</title>
    <link>http://blog.thilelli.net/post/2009/02/09/Comparison%3A-EMC-PowerPath-vs-GNU/Linux-dm-multipath#c8178118</link>
    <guid isPermaLink="false">urn:md5:70efa6436b71082a469f674471689818</guid>
    <pubDate>Sun, 08 Jun 2008 17:55:52 +0200</pubDate>
    <dc:creator>Julien Gabel</dc:creator>
    
    <description>&lt;p&gt;As for EMC PowerPath, it can update its configuration on LUN name change if
used with CLARiiON system. I don't know if it is possible for other storage
provider (but this not important from PowerPath point o view). The final aim is
to be able to properly discover multipath devices, which generally operate
under LVM management: in this case, both solutions are usable nevertheless.&lt;/p&gt;
&lt;p&gt;What really matter is that the multipath device follow automatically device
name change (whatever the name is), and LUN renumbering. It doesn't really
matter how is named the device if the multipath software can't recognize it
(unless for human intervention in case of a software failure in order to
reconfigure it properly). If the alias capability is the solution to do that
with dm-multipath, that is a good news.&lt;/p&gt;</description>
  </item>
      
    
    <item>
    <title>Comparison: EMC PowerPath vs. GNU/Linux dm-multipath - someone</title>
    <link>http://blog.thilelli.net/post/2009/02/09/Comparison%3A-EMC-PowerPath-vs-GNU/Linux-dm-multipath#c8177136</link>
    <guid isPermaLink="false">urn:md5:2872bb269a67f37d8f2b2c478cc8afa1</guid>
    <pubDate>Sat, 07 Jun 2008 15:20:55 +0200</pubDate>
    <dc:creator>someone</dc:creator>
    
    <description>&lt;p&gt;One of the nice things I've found with multipathd is that you can alias
devices based on their unique LUN ID (using the &amp;quot;alias&amp;quot; directive, I can end up
with a /dev/mapper/SAN_LUN3 etc based on the unique ID of the LUN). This way
you can be sure that the same LUN will have the same name across multiple
hosts, between boots, after removing or adding LUNS etc. I haven't been able to
replicate this using powerpath? Does anyone know if there is a way? It seems it
just picks the emcpower&amp;lt;a,b,c,d...&amp;gt; names however it wants? i.e. if I
attach 4 LUNS to one host then the same LUNs to another, in each case the LUNs
will be different devices?&lt;/p&gt;</description>
  </item>
      
    
    <item>
    <title>Comparison: EMC PowerPath vs. GNU/Linux dm-multipath - Julien Gabel</title>
    <link>http://blog.thilelli.net/post/2009/02/09/Comparison%3A-EMC-PowerPath-vs-GNU/Linux-dm-multipath#c8140721</link>
    <guid isPermaLink="false">urn:md5:b45ba2deeec4a8a867f2bc724ca6b035</guid>
    <pubDate>Fri, 16 May 2008 21:07:51 +0200</pubDate>
    <dc:creator>Julien Gabel</dc:creator>
    
    <description>&lt;p&gt;To be able to get the SCSI LUN ID--whatever is the SAN storage provider, you
must know the appropriate sd devices which compose the multipath device
(PowerPath, GNU/Linux dm-multipath, etc.). Then, you can identify the LUN ID
using something like this:&lt;br /&gt;
# find /sys/devices -name &amp;quot;*block&amp;quot; -print | \&lt;br /&gt;
xargs \ls -l | awk -F\/ '$NF ~ /sdo$/ || $NF ~ /sdp$/ \&lt;br /&gt;
{print &amp;quot;HBA: &amp;quot;$7&amp;quot;\tscsi#:channel#:id#:lun#: &amp;quot;$9}'&lt;br /&gt;
HBA: host0 scsi#:channel#:id#:lun#: 0:0:0:9&lt;br /&gt;
HBA: host0 scsi#:channel#:id#:lun#: 0:0:1:9&lt;/p&gt;
&lt;p&gt;If you are looking for more information on SCSI devices, you can also use
the excellent EMC 'inq' little tool:&lt;br /&gt;
&lt;a href=&quot;http://blog.thilelli.net/post/2007/12/01/Nifty-Tool-For-Querying-Heterogeneous-SCSI-Devices&quot; title=&quot;http://blog.thilelli.net/post/2007/12/01/Nifty-Tool-For-Querying-Heterogeneous-SCSI-Devices&quot; rel=&quot;nofollow&quot;&gt;
http://blog.thilelli.net/post/2007/...&lt;/a&gt;&lt;/p&gt;</description>
  </item>
      
    
    <item>
    <title>Comparison: EMC PowerPath vs. GNU/Linux dm-multipath - Ash</title>
    <link>http://blog.thilelli.net/post/2009/02/09/Comparison%3A-EMC-PowerPath-vs-GNU/Linux-dm-multipath#c8140717</link>
    <guid isPermaLink="false">urn:md5:d0642328f5549c1564729934f8bc1d88</guid>
    <pubDate>Fri, 16 May 2008 21:04:04 +0200</pubDate>
    <dc:creator>Ash</dc:creator>
    
    <description>&lt;p&gt;Nice comparison, thank you.&lt;br /&gt;
Is there any way to get Clariion/Symmetrix LUN numbers when using
dm-multipath?&lt;/p&gt;</description>
  </item>
      
    
    <item>
    <title>RAID-1 Volume From the root File System Using SVM on x86 Platform - Julien Gabel</title>
    <link>http://blog.thilelli.net/post/2007/05/30/RAID-1-Volume-From-the-root-File-System-Using-SVM-on-x86-Platform#c8140683</link>
    <guid isPermaLink="false">urn:md5:95a070caea4e131b7f8fc9197959ee1b</guid>
    <pubDate>Thu, 24 Apr 2008 11:55:55 +0200</pubDate>
    <dc:creator>Julien Gabel</dc:creator>
    
    <description>&lt;p&gt;Although it may not be obvious, the VTOC layout on the first disk is assumed
to be in place since the installation time. So was created the slice c1d0s4, in
preparation of the later use of Solaris SVM--as a mandatory prerequisite.
Please refer to the online Sun documentation (&lt;a href=&quot;http://docs.sun.com/app/docs/doc/816-4520/6manpieid?a=view&quot; title=&quot;http://docs.sun.com/app/docs/doc/816-4520/6manpieid?a=view&quot; rel=&quot;nofollow&quot;&gt;http://docs.sun.com/app/docs/doc/81...&lt;/a&gt;)
for more information about the creation and the sizing of State Database
Replicas.&lt;/p&gt;</description>
  </item>
      
    
    <item>
    <title>RAID-1 Volume From the root File System Using SVM on x86 Platform - cgk</title>
    <link>http://blog.thilelli.net/post/2007/05/30/RAID-1-Volume-From-the-root-File-System-Using-SVM-on-x86-Platform#c8140682</link>
    <guid isPermaLink="false">urn:md5:e84571fc248a4b2df7b71eaf5f5df77c</guid>
    <pubDate>Wed, 23 Apr 2008 23:17:42 +0200</pubDate>
    <dc:creator>cgk</dc:creator>
    
    <description>&lt;p&gt;What did you do to come up with the slice 4 info in the initial metadb
initialization command? That's a bit opaque.&lt;/p&gt;</description>
  </item>
      
    
    <item>
    <title>Upcoming IBM AIX 6 features vs. Sun Solaris 10 and OpenSolaris - Abhay</title>
    <link>http://blog.thilelli.net/post/2007/05/22/Upcoming-IBM-AIX-6-features-vs-Sun-Solaris-10-and-OpenSolaris#c8140689</link>
    <guid isPermaLink="false">urn:md5:913bbc4c106905a250660670e9e4ecfc</guid>
    <pubDate>Sat, 19 Apr 2008 17:54:18 +0200</pubDate>
    <dc:creator>Abhay</dc:creator>
    
    <description>&lt;p&gt;POINT BLANK.......&lt;/p&gt;
&lt;p&gt;POWER 6 / AIX 6.1 has turned out to be a clear winner, over performance.
Hands down its value for what you pay for when you are considering a SMB
segment. One IBM Power Core has default 2 CPU's in one Dye, now talk about
Oracle / SAP licensing cost, you pay for one and get the performance of 2 which
invariabely not in the case of SUN Processors. SUN is totally dependent on
Fijitsu's R&amp;amp;D for all their upcoming processors on UNIX platform, IBM seems
to be self sufficient.&lt;/p&gt;</description>
  </item>
      
    
    <item>
    <title>Precompiled PHP RPMs and IBM IHS Web Server on AIX - strus</title>
    <link>http://blog.thilelli.net/post/2006/06/04/Precompiled-PHP-RPMs-and-IBM-IHS-Web-Server-on-AIX#c8140691</link>
    <guid isPermaLink="false">urn:md5:251db2095167d8872ec477a00a93317f</guid>
    <pubDate>Mon, 24 Mar 2008 22:22:21 +0100</pubDate>
    <dc:creator>strus</dc:creator>
    
    <description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;BULL provides for free tons of open source packages for AIX.&lt;br /&gt;
You can find the latest version of PHP, Apache ...&lt;/p&gt;</description>
  </item>
      
</channel>
</rss>