<?xml version="1.0"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:bgn="http://blogreen.org" xmlns:res="http://blogreen.org/TR/Resources" bgn:template-name="rss" version="2.0"><channel><title>Romain Tartière's Blog's Comments</title><link>http://romain.blogreen.org/blog/</link><description>All comments to mostly technical blog posts from Romain Tartière's Blog.</description><link xmlns="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://romain.blogreen.org/blog/comments-rss.xml"/><item><title>Romain Tartière commented Updating a ZFS Mirror</title><description><![CDATA[
	  <p xmlns="http://www.w3.org/1999/xhtml">You are right: there is no <em>need</em> to <tt>zpool replace</tt>
	      in this case.  In fact, the man page indicates that this command
	      does what you say in a single step (the only difference is the
	      order of operations, and it's not critical):</p>
	  <blockquote xmlns="http://www.w3.org/1999/xhtml" class="man">    <strong>zpool</strong> <strong>replace</strong> [<strong>-f</strong>] <em>pool</em> <em>old_device</em> [<em>new_device</em>]

        Replaces <em>old_device</em> with <em>new_device</em>. This is equivalent to  attach-
        ing  <em>new_device</em>,  waiting  for  it  to resilver, and then detaching
        <em>old_device</em>.</blockquote>
        <p xmlns="http://www.w3.org/1999/xhtml">Let's face it: I am a lazy sysadmin ;-)</p>
      ]]></description><link>http://romain.blogreen.org/blog/2012/01/updating-a-zfs-mirror/#comment-2</link><guid isPermaLink="true">http://romain.blogreen.org/blog/2012/01/updating-a-zfs-mirror/#comment-2</guid><pubDate>Thu, 05 Jan 2012 11:38:24 +0100</pubDate></item><item><title>Freddie Cash commented Updating a ZFS Mirror</title><description><![CDATA[
	  <p xmlns="http://www.w3.org/1999/xhtml">Just a note: you don't need to use <tt>zpool replace</tt> on
	      mirror vdevs.  Instead, just <tt>zpool detach</tt> the degraded
	      disk from the vdev (thus turning it into a single disk vdev).
	      And <tt>zpool attach</tt> the new disk to the remaining disk
	      (thus turning it back into a mirror vdev).</p>

	  <p xmlns="http://www.w3.org/1999/xhtml"><tt>zpool replace</tt> is only needed for raidz vdevs.</p>
      ]]></description><link>http://romain.blogreen.org/blog/2012/01/updating-a-zfs-mirror/#comment-1</link><guid isPermaLink="true">http://romain.blogreen.org/blog/2012/01/updating-a-zfs-mirror/#comment-1</guid><pubDate>Wed, 04 Jan 2012 15:51:49 -0800</pubDate></item><item><title>Romain Tartière commented Thomson ST2030 Feature Key Sheet Template</title><description><![CDATA[
	  <p xmlns="http://www.w3.org/1999/xhtml">Hi JM!</p>
	  <p xmlns="http://www.w3.org/1999/xhtml">
	      Well, I though about writing a script for automagically
	      filling-in the <acronym title="Scalable Vector Graphics">SVG</acronym> document but I saw
	      a few issues in my case and I don't think it worth the time (can
	      be an amusing exam subject for students anyway):
	  </p>
	  <ol xmlns="http://www.w3.org/1999/xhtml">
	      <li>
		  As you mentioned, there are some numbers I don't want to have as
		  <em>fast call keys</em> (e.g. <tt>*1</tt>, <tt>123</tt>);
	      </li>
	      <li>
		  Another point is that the log only has the numbers, not the
		  caller-id (i.e. real name) and in my
		  <acronym title="Lightweight Directory Access Protocol">LDAP</acronym> directory, a single telephone-number
		  can belong to multiple persons (I am considering to register
		  <em>places</em> in addition to <em>people</em> to circumvent
		  this limitation but I am not sure that this would really help
		  making my life easier anyway).  In such a situation, I can't
		  rely on the directory information to retrieve the label
		  corresponding to the number, and I have to pick a custom name
		  myself;
	      </li>
	      <li>
		  Some names in the <acronym title="Lightweight Directory Access Protocol">LDAP</acronym> directory
		  are a bit too long and required to be shortened to fit in;
	      </li>
	      <li>
		  A last point is grouping: I didn't want to order the numbers by
		  how often I use them, but rather by the category they belong to (e.g.
		  family, friends).
	      </li>
	  </ol>
	  <p xmlns="http://www.w3.org/1999/xhtml">
	      Taking all these rules into account would have required some
	      non-trivial development, and as I don't plan to change these
	      numbers every once a while, I stuck to filling-in the sheet
	      myself.
	  </p>
	  <p xmlns="http://www.w3.org/1999/xhtml">
	      However, in a company context, auto-filling-in the template
	      definitively makes sense.  In this case, using the same source
	      to generate both the filled-in template (using
	      <acronym title="eXtensible Stylesheet Language Transformations">XSLT</acronym>) and the provisioning
	      configuration files would make the <em>fast call keys</em>
	      update for internal calls as easy as changing the sheet and
	      rebooting the telephone!
	  </p>
	  <p xmlns="http://www.w3.org/1999/xhtml">Happy end of year season!</p>

      ]]></description><link>http://romain.blogreen.org/blog/2011/12/thomson-st2030-feature-key-sheet-template/#comment-2</link><guid isPermaLink="true">http://romain.blogreen.org/blog/2011/12/thomson-st2030-feature-key-sheet-template/#comment-2</guid><pubDate>Fri, 30 Dec 2011 13:29:06 +0100</pubDate></item><item><title>Jean-Marie Favreau commented Thomson ST2030 Feature Key Sheet Template</title><description><![CDATA[
	  <p xmlns="http://www.w3.org/1999/xhtml">
	      Since <acronym title="Scalable Vector Graphics">SVG</acronym> is a text-based format (an
	      <acronym title="eXtensible Markup Language">XML</acronym> language), you may create a script
	      that inserts into an <acronym title="Scalable Vector Graphics">SVG</acronym> template your
	      top-20 numbers (you can have a black-list file to remove the
	      unwanted numbers, the ones you don't want to flaunt on your
	      desk).<br/> The next step is to add a line in your crontab, that
	      checks if your numbers has been modified, and print the new
	      <acronym title="Portable Document Format">PDF</acronym>
	      in case of modification. :)
	  </p>
	  <p xmlns="http://www.w3.org/1999/xhtml">Merry Christmas!</p>
      ]]></description><link>http://romain.blogreen.org/blog/2011/12/thomson-st2030-feature-key-sheet-template/#comment-1</link><guid isPermaLink="true">http://romain.blogreen.org/blog/2011/12/thomson-st2030-feature-key-sheet-template/#comment-1</guid><pubDate>Fri, 30 Dec 2011 12:41:22 +0100</pubDate></item><item><title>Romain Tartière commented TeXLive 2011 on FreeBSD</title><description><![CDATA[
	  <p xmlns="http://www.w3.org/1999/xhtml">Hi Antonio!</p>
	  <blockquote xmlns="http://www.w3.org/1999/xhtml" class="cite">Can you clarify the statement <q>As of August 1st 2011,
		  the freebsd-texlive projects distributes ports for using
		  TeXLive 2011 from the FreeBSD ports tree</q></blockquote>
	  <p xmlns="http://www.w3.org/1999/xhtml">The FreeBSD-TeXLive project aims at providing TeXLive as ports
	      for the FreeBSD operating system.  This effort was started in
	      late 2008 (<tt>texlive-2008</tt>) and is regularly updated to
	      track the project upstream (currently <tt>texlive-2011</tt>).
	      When a new TeXLive version is available, I try to post a note
	      about the FreeBSD-TeXLive ports being updated to advertise a
	      bit this project.</p>
	  <p xmlns="http://www.w3.org/1999/xhtml">While I am a FreeBSD ports committer, TeXLive is not available
	      through the FreeBSD ports collection: when the project was
	      started, some other efforts where already engaged, but not yet
	      public.  Since I had basically no news since that, I am considering
	      sharpening the FreeBSD-TeXLive ports to eventually bring them to
	      the official tree: the teTeX maintainer has <a href="http://www.tug.org/tetex/">stopped the project more
		  than 5 years ago</a>, I think we have to switch!</p>
	  <p xmlns="http://www.w3.org/1999/xhtml">This will require extensive work to update <a href="http://www.freshports.org/search.php?stype=depends_all&amp;method=match&amp;query=print/teTeX">existing
		  ports in the tree which depend on teTeX</a> to make them use
	      TeXLive instead (~150 ports).</p>
	  <p xmlns="http://www.w3.org/1999/xhtml">In the meantime, <a href="http://code.google.com/p/freebsd-texlive/wiki/Installing">you
		  have to use <tt>portshaker(8)</tt> to merge the
		  FreeBSD-TeXLive ports into the FreeBSD tree</a>, and any port
	      that depend on teTeX on your system will require a closer look to
	      avoid installing conflicting packages.</p>
	  <p xmlns="http://www.w3.org/1999/xhtml">Regards,<br/>
	  Romain</p>
      ]]></description><link>http://romain.blogreen.org/blog/2011/08/texlive-2011-on-freebsd/#comment-2</link><guid isPermaLink="true">http://romain.blogreen.org/blog/2011/08/texlive-2011-on-freebsd/#comment-2</guid><pubDate>Fri, 16 Sep 2011 11:10:38 +0200</pubDate></item><item><title>Antonio Olivares commented TeXLive 2011 on FreeBSD</title><description><![CDATA[
	  <p xmlns="http://www.w3.org/1999/xhtml">Dear Romain,</p>
	  <p xmlns="http://www.w3.org/1999/xhtml">I have successfully installed 9.0-BETA 2 and have looked in
	      <tt>/usr/ports/print/texlive-*</tt>, but it does not exist in
	      native FreeBSD ports.  Can you clarify the statement <q>As of
		  August 1st 2011, the freebsd-texlive projects distributes
		  ports for using TeXLive 2011 from the FreeBSD ports tree</q>
	      on page <a href="http://code.google.com/p/freebsd-texlive/">http://code.google.com/p/freebsd-texlive/</a>?</p>
	  <p xmlns="http://www.w3.org/1999/xhtml">Due to many packages on FreeBSD depending on TeX mainly teTeX, I
	      successfully removed the TeXLive 2010 install from my FreeBSD 8.2
	      amd64 box.  I am using native teTeX on 2 of my 3 FreeBSD boxes.  I
	      don't see any TeXLive packages in native FreeBSD ports.  I have also
	      tried to install TeXLive through your advice in page using portshaker,
	      but have not succeeded.</p>
	  <p xmlns="http://www.w3.org/1999/xhtml">If I install TeXLive from TeXLive DVD 2011, I get working tex, but
	      xdvi complain(s)(ed) about missing a <em>file****.so</em> and did not work
	      correctly.  I would like a tighter integration and would prefer if
	      possible to get the full scheme installed and configure the ports that
	      use teTeX to use TeXLive that you have made, but I have not
	      succeeded.</p>
	  <p xmlns="http://www.w3.org/1999/xhtml">Thank you for any pointers on this and if TeXLive is not in FreeBSD
	      ports, despite your enormous contributions and dedications; there is
	      sadly not much that we can do.  Many users complain that TeXLive is a
	      monster and that they prefer teTeX, but for me a full scheme is
	      preferred as it has the majority of style files that one needs.</p>
	  <p xmlns="http://www.w3.org/1999/xhtml">Regards,<br/>
	      Antonio</p>

      ]]></description><link>http://romain.blogreen.org/blog/2011/08/texlive-2011-on-freebsd/#comment-1</link><guid isPermaLink="true">http://romain.blogreen.org/blog/2011/08/texlive-2011-on-freebsd/#comment-1</guid><pubDate>Thu, 15 Sep 2011 21:01:53 GMT</pubDate></item><item><title>Romain Tartière commented TeXLive for FreeBSD updated</title><description><![CDATA[<p xmlns="http://www.w3.org/1999/xhtml">Hi Antonio!</p>

	  <p xmlns="http://www.w3.org/1999/xhtml">Unfortunately, there is no plan to merge the freebsd-texlive ports into the FreeBSD ports tree.  I am considering pushing portshaker in the ports however to make it easier for people who want to use these ports, BSD# Ports, etc</p>

	  <p xmlns="http://www.w3.org/1999/xhtml">BTW, the TeXLive and teTeX are not compatible.  And no port for kile is available for using with TeXLive.  Any contribution is welcome however :-)</p>

	  <p xmlns="http://www.w3.org/1999/xhtml">Thanks!<br/>
	      Romain</p>]]></description><link>http://romain.blogreen.org/blog/2009/05/texlive-for-freebsd-updated/#comment-2</link><guid isPermaLink="true">http://romain.blogreen.org/blog/2009/05/texlive-for-freebsd-updated/#comment-2</guid><pubDate>Sun, 11 Apr 2010 16:23:22 +0100</pubDate></item><item><title>Antonio commented TeXLive for FreeBSD updated</title><description><![CDATA[<p xmlns="http://www.w3.org/1999/xhtml">Dear Romain,</p>

	  <p xmlns="http://www.w3.org/1999/xhtml">I have recently installed FreeBSD 8.0.  I had used FreeBSD 6 back a while and liked it but my disk died and I did not install it again.  Now I installed on an AMD machine and installed kile and it pulled in tetex.  teTeX is old and unmaintained, I applied your solution in google code, but the tex is still the old tex, how can I make sure that I have TeXLive installed?</p>

	  <p xmlns="http://www.w3.org/1999/xhtml">I did not know many more things like cvsup/csup and I am learning a little bit more and currently updating to newer.</p>

	  <p xmlns="http://www.w3.org/1999/xhtml">Thanks for your TeXLive work. When will it become part of FreeBSD?  NetBSD has a port already?  Is it like going to happen soon?</p>

	  <p xmlns="http://www.w3.org/1999/xhtml">Regards,</p>

	  <p xmlns="http://www.w3.org/1999/xhtml">Antonio</p>]]></description><link>http://romain.blogreen.org/blog/2009/05/texlive-for-freebsd-updated/#comment-1</link><guid isPermaLink="true">http://romain.blogreen.org/blog/2009/05/texlive-for-freebsd-updated/#comment-1</guid><pubDate>Fri, 09 Apr 2010 00:20:19 GMT</pubDate></item><item><title>Romain Tartière commented Deploying OpenLDAP under FreeBSD 7.0</title><description><![CDATA[<p xmlns="http://www.w3.org/1999/xhtml">Hey!</p>

	  <p xmlns="http://www.w3.org/1999/xhtml">Maybe a base-dn error.  Difficult to say without seeing the slapd.conf file. /var/log/debug.log may also contain useful details ;-)</p>]]></description><link>http://romain.blogreen.org/blog/2008/03/deploying-openldap-under-freebsd-70/#comment-3</link><guid isPermaLink="true">http://romain.blogreen.org/blog/2008/03/deploying-openldap-under-freebsd-70/#comment-3</guid><pubDate>Mon, 05 Apr 2010 16:10:42 +0100</pubDate></item><item><title>Joost commented Deploying OpenLDAP under FreeBSD 7.0</title><description><![CDATA[<p xmlns="http://www.w3.org/1999/xhtml">Hi</p>

	  <p xmlns="http://www.w3.org/1999/xhtml">I get this error doing the above</p>

<code xmlns="http://www.w3.org/1999/xhtml">/usr/local/etc/openldap/slapd.conf: line 15: suffix &lt;dc=uwaterloo,dc=ca&gt; not allowed in frontend database. slapadd: bad configuration file!</code>

<p xmlns="http://www.w3.org/1999/xhtml">Do you know what it means and how this can be solved? Thanks in advance.</p>
]]></description><link>http://romain.blogreen.org/blog/2008/03/deploying-openldap-under-freebsd-70/#comment-2</link><guid isPermaLink="true">http://romain.blogreen.org/blog/2008/03/deploying-openldap-under-freebsd-70/#comment-2</guid><pubDate>Mon, 05 Apr 2010 15:20:49 GMT</pubDate></item></channel></rss>

