<?xml version="1.0" encoding="UTF-8"?> 
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>Steven Rosenberg</title>
        <link>https://stevenrosenberg.nfshost.com/blog/networking/ipv6/</link>
        <description>frugal technology, simple living and guerrilla large-appliance repair</description>
        <language>en</language>
        <docs>http://blogs.law.harvard.edu/tech/rss</docs>
        <generator><!-- name="generator" content="ode/1.2.1" --></generator>
        <managingEditor>steven@stevenrosenberg.net (Steven Rosenberg)</managingEditor>
        <webMaster>steven@stevenrosenberg.net (Steven Rosenberg)</webMaster>
        <atom:link href="https://stevenrosenberg.nfshost.com/blog/index.rss2" rel="self" type="application/rss+xml" />


        <item>
            <title>I upgraded from Debian Squeeze to Wheezy today</title>
            <link>https://stevenrosenberg.nfshost.com/blog/linux/debian/2012_0629_upgrade_squeeze_to_wheezy</link>
            <description><![CDATA[ <p>Though my track record with in-place upgrades of Linux/Unix systems is far from positive, I decided to do just that with my long-running (since late 2010) Debian Squeeze laptop today.</p>

<p>It went surprisingly well -- and by that I mean I'm using a fully upgraded Debian Wheezy laptop to create this post in Nautilus via sftp.
<p><a href="https://stevenrosenberg.nfshost.com/blog/linux/debian/2012_0629_upgrade_squeeze_to_wheezy?include_jump_separator=y#2012_0629_upgrade_squeeze_to_wheezy">Read the rest of this post</a></p> ]]></description>
            <pubDate>Fri, 29 Jun 2012 17:29:31 UTC</pubDate>
            <guid>https://stevenrosenberg.nfshost.com/blog/2012/06/29/17/29/31/</guid>
       </item>


        <item>
            <title>Reducing swappiness in Linux for better desktop performance</title>
            <link>https://stevenrosenberg.nfshost.com/blog/linux/debian/2012_0620_swappiness_in_debian</link>
            <description><![CDATA[ <p>My Debian Squeeze system has been swapping a lot lately. I think web browsers -- mostly Google Chrome -- are to blame. I'm not sure switching entirely to Firefox will solve the problem. Web browsers eat resources.</p>

<p>To speed things up, I decided to reduce my "swappiness" to see how that affects system performance.</p>

<p>It's been a very long time since I've done it, so I Googled "swappiness in Debian," and came across <a href="http://www.insidesocal.com/click/2010/04/ubuntu-1004-swap-update-its-no.html">my own entry</a> from 2010 when I was running Ubuntu 10.04. I got my information from the Ubuntu community Swap FAQ, and <a href="https://help.ubuntu.com/community/SwapFaq#What_is_swappiness_and_how_do_I_change_it.3F">you can too</a>.</p>

<p>I followed the recipe on my Debian Squeeze system, changing swappiness from the default of 60 to 10 so the system will use swap less often.</p>

<p>So far, so good.</p>

<p><strong>The next day:</strong> This is totally working. After six or so hours of my usual workload, I'm only using 1.2 MB of swap. Nice!</p>

<p><strong>The next week:</strong> After a full day of computing, with lots of Google Chrome windows and tabs open all day (I barely used Firefox/Iceweasel today), doing some photo edits but no video editing, I'm using 1.4 GB of RAM and 24.8 MB of swap. I'd say the experiment in changing swappiness is a success.</p>
 ]]></description>
            <pubDate>Wed, 20 Jun 2012 19:14:42 UTC</pubDate>
            <guid>https://stevenrosenberg.nfshost.com/blog/2012/06/20/19/14/42/</guid>
       </item>


        <item>
            <title>Debian project leader Stefano Zacchiroli and the controversy over Debian Multimedia</title>
            <link>https://stevenrosenberg.nfshost.com/blog/linux/debian/2012_0613_debian_project_leader_and_debian_multimedia</link>
            <description><![CDATA[ <p>I came across Debian project leader Stefano Zacchiroli's Bits from the DPL on <a href="http://planet.debian.org/">Planet Debian</a> -- the most recent bits also living <a href="http://upsilon.cc/~zack/blog/posts/2012/06/bits_from_the_DPL_for_May_2012/">on Stefano's blog</a> and <a href="https://lists.debian.org/debian-devel-announce/2012/06/msg00005.html">on a Debian mailing list</a>.</p>

<p>The more interesting bits this month include <a href="http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/2012-May/026678.html">a controversy</a> over duplication between the Debian Multimedia archive and Debian proper.</p>

<p>Stefano suggests that what package belongs where be worked out, or that Debian Multimedia shed its Debian name and move on.
<p><a href="https://stevenrosenberg.nfshost.com/blog/linux/debian/2012_0613_debian_project_leader_and_debian_multimedia?include_jump_separator=y#2012_0613_debian_project_leader_and_debian_multimedia">Read the rest of this post</a></p> ]]></description>
            <pubDate>Wed, 13 Jun 2012 10:25:47 UTC</pubDate>
            <guid>https://stevenrosenberg.nfshost.com/blog/2012/06/13/10/25/47/</guid>
       </item>


        <item>
            <title>I just installed Iceweasel 13 in Debian Squeeze</title>
            <link>https://stevenrosenberg.nfshost.com/blog/applications/browsers/firefox/2012_0612_iceweasel_13</link>
            <description><![CDATA[ <p>I finally got Iceweasel 13 installed out of the Mozilla Debian APT archive on my Debian Squeeze system. For at least a week I've been stuck on Iceweasel/Firefox 12 due to dependency issues. dWhile a Debian Forums article didn't provide the exact solution to my problem, it did give me a clue:</p>

<p>Reinstall Iceweasel.</p>

<p>I did that, and I got the new Iceweasel/Firefox as well as the needed dependencies, and thus far nothing appears to be broken.
<p><a href="https://stevenrosenberg.nfshost.com/blog/applications/browsers/firefox/2012_0612_iceweasel_13?include_jump_separator=y#2012_0612_iceweasel_13">Read the rest of this post</a></p> ]]></description>
            <pubDate>Wed, 13 Jun 2012 10:00:55 UTC</pubDate>
            <guid>https://stevenrosenberg.nfshost.com/blog/2012/06/13/10/00/55/</guid>
       </item>


        <item>
            <title>WordPress: What am I doing wrong?</title>
            <link>https://stevenrosenberg.nfshost.com/blog/blogging_systems/wordpress/2012_0612_wordpress_custom_output</link>
            <description><![CDATA[ <p>OK, here's the deal. In <a href="http://ode-is-simple.com">Ode</a> I can get any kind of output I want through the project's infinitely flexible theming. In <a href="http://movabletype.org">Movable Type</a> I can create any number of custom Javascript output files that draw on the blogging system's database.</p>

<p>So how do I do this in WordPress? I'm looking into child themes (I confess that I've -- <em>horror of horrors</em> -- modified the main theme in a WordPress blog), but I need EXTRA theming. What I need is the ability to tap the blog database for custom HTML output that includes only the elements I want with accompanying HTML so I can display that output on other sites.</p>

<p>It's so easy to do this in Ode and Movable Type. Why is it so hard (or seemingly so) in WordPress?
<p><a href="https://stevenrosenberg.nfshost.com/blog/blogging_systems/wordpress/2012_0612_wordpress_custom_output?include_jump_separator=y#2012_0612_wordpress_custom_output">Read the rest of this post</a></p> ]]></description>
            <pubDate>Tue, 12 Jun 2012 20:01:56 UTC</pubDate>
            <guid>https://stevenrosenberg.nfshost.com/blog/2012/06/12/20/01/56/</guid>
       </item>


        <item>
            <title>How do you feel about social-networking posts originating as blog-post titles?</title>
            <link>https://stevenrosenberg.nfshost.com/blog/social/2012_0611-blog-post-titles</link>
            <description><![CDATA[ 
 ]]></description>
            <pubDate>Mon, 11 Jun 2012 02:50:42 UTC</pubDate>
            <guid>https://stevenrosenberg.nfshost.com/blog/2012/06/11/02/50/42/</guid>
       </item>


        <item>
            <title>Allowing the use of multiple themes simultaneously would solve many #WordPress problems for me.</title>
            <link>https://stevenrosenberg.nfshost.com/blog/blogging_systems/wordpress/2012_0611_wordpress_theme_problem</link>
            <description><![CDATA[ 
 ]]></description>
            <pubDate>Mon, 11 Jun 2012 02:43:59 UTC</pubDate>
            <guid>https://stevenrosenberg.nfshost.com/blog/2012/06/11/02/43/59/</guid>
       </item>


        <item>
            <title>Social networking -- the giving and the taking</title>
            <link>https://stevenrosenberg.nfshost.com/blog/social/2012_0609_social_network_temptation</link>
            <description><![CDATA[ <p>I know it's easy. You pick up your smartphone. You click the Twitter icon (or Facebook, if that's your poison).</p>

<p>Then you lay it out in 140- (or 500-odd) character bursts. Or you talk about the sandwich you're eating.</p>

<p>There's nothing wrong with that. Except that your words now live on some social network. Not on your own hard drive or server. Not even on a WordPress.com blog from which you can extract every post to archive and reuse as you please. 
<p><a href="https://stevenrosenberg.nfshost.com/blog/social/2012_0609_social_network_temptation?include_jump_separator=y#2012_0609_social_network_temptation">Read the rest of this post</a></p> ]]></description>
            <pubDate>Mon, 11 Jun 2012 02:37:52 UTC</pubDate>
            <guid>https://stevenrosenberg.nfshost.com/blog/2012/06/11/02/37/52/</guid>
       </item>


        <item>
            <title>I will not be posting on Twitter, Facebook, Google Plus, Diaspora or Identi.ca</title>
            <link>https://stevenrosenberg.nfshost.com/blog/social/2012_0608_no_direct_posts</link>
            <description><![CDATA[ <p>These are the social networks on which I have accounts.</p>

<p>But I won't be posting directly on any of them.
<p><a href="https://stevenrosenberg.nfshost.com/blog/social/2012_0608_no_direct_posts?include_jump_separator=y#2012_0608_no_direct_posts">Read the rest of this post</a></p> ]]></description>
            <pubDate>Fri, 08 Jun 2012 19:37:24 UTC</pubDate>
            <guid>https://stevenrosenberg.nfshost.com/blog/2012/06/08/19/37/24/</guid>
       </item>


        <item>
            <title>DSL Extreme: No plans -- or need -- to go IPv6 at this time; so what are web sites and ISPs going to do?</title>
            <link>https://stevenrosenberg.nfshost.com/blog/networking/ipv6/2012_0607_dsl_extreme_and_ipv6</link>
            <description><![CDATA[ <p>With <a href="http://www.google.com/intl/en/ipv6/">all the talk of IPv6</a> and how the Internet is running out of IP addresses and how we have to move from IPv4 to avoid catastrophe, I wondered what my ISP, <a href="http://dslextreme.com">DSL Extreme</a>, is doing about it.
<p><a href="https://stevenrosenberg.nfshost.com/blog/networking/ipv6/2012_0607_dsl_extreme_and_ipv6?include_jump_separator=y#2012_0607_dsl_extreme_and_ipv6">Read the rest of this post</a></p> ]]></description>
            <pubDate>Thu, 07 Jun 2012 12:33:06 UTC</pubDate>
            <guid>https://stevenrosenberg.nfshost.com/blog/2012/06/07/12/33/06/</guid>
       </item>


    </channel>
</rss>
