<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Linux on Calgary RHCE</title>
    <link>https://calgaryrhce.ca/tags/linux/</link>
    <description>Recent content in Linux on Calgary RHCE</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 19 Jul 2019 18:06:55 +0000</lastBuildDate>
    <atom:link href="https://calgaryrhce.ca/tags/linux/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Adding python virtual environments (venvs) to Ansible Tower</title>
      <link>https://calgaryrhce.ca/blog/2019/07/19/adding-python-virtual-environments-venvs-to-ansible-tower/</link>
      <pubDate>Fri, 19 Jul 2019 18:06:55 +0000</pubDate>
      <guid>https://calgaryrhce.ca/blog/2019/07/19/adding-python-virtual-environments-venvs-to-ansible-tower/</guid>
      <description>&lt;p&gt;As you’re developing playbooks you may find that you need to add additional python capability in order to use some modules. These are easy enough to install on a regular linux client with pip, but how does this work for Ansible Tower? Fortunately this is not too different for Ansible Tower, we’re just going to instruct Tower to add another source directory for our new venvs, and then assign these in Tower at an Organization, Project, or Job Template level. Let me show you how this works.&lt;/p&gt;</description>
    </item>
    <item>
      <title>32-bit application support in RHEL7</title>
      <link>https://calgaryrhce.ca/blog/2019/05/07/32-bit-application-support-in-rhel7/</link>
      <pubDate>Tue, 07 May 2019 16:17:02 +0000</pubDate>
      <guid>https://calgaryrhce.ca/blog/2019/05/07/32-bit-application-support-in-rhel7/</guid>
      <description>&lt;p&gt;I recently needed to check the supportability of 32-bit applications in Red Hat Enterprise Linux. RHEL can support 32-bit applications in a 64-bit environment in the following scenarios:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://access.redhat.com/solutions/509373&#34;&gt;https://access.redhat.com/solutions/509373&lt;/a&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Additionally, with the multilib toolchain, one can install the 32-bit packages by specifying the architecture in the yum install command:&lt;/p&gt;&#xA;&lt;pre&gt;&lt;code&gt;# yum install glibc.i686&#xA;&lt;/code&gt;&lt;/pre&gt;&#xA;&lt;p&gt; &lt;/p&gt;</description>
    </item>
    <item>
      <title>Testing the ODROID-HC2 with Open Media Vault</title>
      <link>https://calgaryrhce.ca/blog/2019/02/04/testing-the-odroid-hc2-with-open-media-vault/</link>
      <pubDate>Mon, 04 Feb 2019 22:59:18 +0000</pubDate>
      <guid>https://calgaryrhce.ca/blog/2019/02/04/testing-the-odroid-hc2-with-open-media-vault/</guid>
      <description>&lt;p&gt;I’ve recently been tinkering with a few small Raspberry Pi-like boards. I’m anxious to get my hands on hardkernel’s &lt;a href=&#34;https://www.hardkernel.com/shop/odroid-h2/&#34;&gt;ODROID-H2&lt;/a&gt; x86 board, I think they might have hit a sweet spot for a decently spec’d, low TDP board with a decent amount of RAM and NVMe storage options. I like the NUC platform, but the H2 might be a less expensive &amp;amp; more capable option. Until this product gets back in stock, I’ve been playing with the &lt;a href=&#34;https://www.hardkernel.com/shop/odroid-hc2-home-cloud-two/&#34;&gt;ODROID-HC2.&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Network teaming in RHEL7</title>
      <link>https://calgaryrhce.ca/blog/2016/11/24/network-teaming-in-rhel7/</link>
      <pubDate>Thu, 24 Nov 2016 22:32:26 +0000</pubDate>
      <guid>https://calgaryrhce.ca/blog/2016/11/24/network-teaming-in-rhel7/</guid>
      <description>&lt;p&gt;If you’ve adopted or are just starting to read up on the new features included in Red Hat Enterprise Linux 7, you may have come across the new networking feature called teaming. It essentially is a replacement for bonding that offers more modularity, increased link monitoring features, higher network performance, and easier management of interfaces.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Upgrading from Fedora 23 to Fedora 24</title>
      <link>https://calgaryrhce.ca/blog/2016/10/15/upgrading-from-fedora-23-to-fedora-24/</link>
      <pubDate>Sat, 15 Oct 2016 20:19:11 +0000</pubDate>
      <guid>https://calgaryrhce.ca/blog/2016/10/15/upgrading-from-fedora-23-to-fedora-24/</guid>
      <description>&lt;p&gt;For my main workstation, I’ve been running linux for about 8 or 9 years now and specifically Fedora for the past 3. I’ve tried to keep my workstation kernel around about the same version as the systems I maintain in the datacentre, typically just slightly ahead. This helps relate my workstation experience to the datacentre, and also keeps me slightly ahead of the learning curve getting experience with the new tools that come in, or figuring out workarounds prior to needing to do them in production. Running CentOS previously worked well, but upgrading was always a bit of a risk for me. I made sure my backup-fu was strong, and spent a fair bit of time reinstalling display drivers and dealing with other upgrade nuances. During the dawn of the &lt;a href=&#34;https://fedoraproject.org/wiki/Fedora.next&#34;&gt;Fedora.next&lt;/a&gt; initiative, I made the switch to Fedora. I was thrilled, and honestly a little surprised, to be getting similar stability and predictability while being able to take advantage of the new developments in a more modern kernel. Way to go Fedora team! I’ve had a flawless experience with this distro, I can say I’m quite happy with it.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Become a contributor!</title>
      <link>https://calgaryrhce.ca/blog/2014/05/04/become-a-contributor/</link>
      <pubDate>Sun, 04 May 2014 22:29:33 +0000</pubDate>
      <guid>https://calgaryrhce.ca/blog/2014/05/04/become-a-contributor/</guid>
      <description>&lt;div class=&#34;entry-content&#34;&gt;&#xA;  &lt;p&gt;&#xA;    As my career has evolved over the past 10 years, I’ve come to appreciate the value of collaborative ideas and solutions more than ever.  From my early days in software development and QA, into helpdesk, administrator, and architect roles, I’ve seen the best results in every field when we’ve worked closely together to solve problems.  Today, it’s become more apparent than ever that mass collaboration is going to be the innovation model that carries us into the future.  New challenges pop up faster than they ever have, and I’m increasingly relying on others to help me solve these challenges, as they are relying on me.  As a result, I’ve felt the need to become more and more involved with technology and relationships as these have proven key to fostering our joint success.&#xA;  &lt;/p&gt;</description>
    </item>
  </channel>
</rss>
