Fedora

After upgrading my Fedora 20 Xen hypervisor to virt-manager 1.

In my previous post about installing Fedora via PXE, I forgot to mention a big time saver for the installation.

This post has been a bit delayed, but I want to follow up on the post I wrote last month about moving from OS X to Linux at work.

If you run bwm-ng and you’ve run a yum upgrade lately on Fedora 19, you have probably seen this:

The thought of using Linux as a manager in a highly Windows- and Mac-centric corporate environment isn’t something to be taken lightly.

The X1 Carbon’s touchpad has been my nemesis in Linux for quite some time because of its high sensitivity.

Outside of the RHCA exams, I haven’t configured a PXE system for my personal needs.

I was shocked to see Robyn Bergeron’s email today about Seth Vidal’s passing.

Pairing virt-manager with KVM makes booting new VM’s pretty darned easy.

The confined user support in SELinux is handy for ensuring that users aren’t able to do something that they shouldn’t.

Most of my websites run on a pair of Supermicro servers that I purchased from Silicon Mechanics (and I can’t say enough good things about them and their servers).

It’s been a little while since I last posted about installing Xen on Fedora, so I figured that Fedora 19’s beta release was as good a time as any to write a new post.

I’ve converted one of my KVM hypervisors from CentOS 6 to Fedora 18 and now comes the task of migrating my virtual machines off of my single remaining CentOS 6 hypervisor.

This post is a quick one but I wanted to share it since I taught it to someone new today.

Changing my ssh port from the default port (22) has been one of my standard processes for quite some time when I build new servers or virtual machines.

A coworker heard me grumbling about Linux system administration standards and recommended that I review the CIS Security Benchmarks.

The wheel group exists for a critical purpose and Wikipedia has a concise definition:

This article appeared in SC Magazine and I’ve posted it here as well.

After many discussions with fellow Linux users, I’ve come to realize that most seem to disable SELinux rather than understand why it’s denying access.

I’m in the process of moving back to a postfix/dovecot setup for hosting my own mail and I wanted a way to remove the more sensitive email headers that are normally generated when I send mail.

The latest versions of virt-manager don’t release the mouse pointer when you’re doing X forwarding to a machine running OS X.

I dragged out an old Aopen MP57-D tonight that was just sitting in the closet and decided to load up kvm on Fedora 18.

Although the X1 Carbon has a much better looking display than the T430s, it still looked a bit washed out when I compared it to other monitors right next to it.

UPDATE: I’ve found a better configuration via another X1 Carbon user and there’s a new post with all the details.

I’m still quite pleased with my Samsung Galaxy SIII but there are some finicky Bluetooth issues with my car that I simply can’t figure out.

Although GRUB 2 does give us some nice benefits, changing its configuration can be a bit of a challenge if you’re used to working with the original GRUB for many, many years.

LVM snapshots can be really handy when you’re trying to take a backup of a running virtual machine.

This problem came up in conversation earlier this week and I realized that I’d never written a post about it.

If you try to run Xen without libvirt on Fedora 17 with SELinux in enforcing mode, you’ll be butting heads with SELinux in no time.

Anyone who has been a system administrator for even a short length of time has probably used traceroute at least once.

I originally wrote this post for the Rackspace Blog but I decided to post it here in case some of my readers might have missed it.

A fellow Racker showed me httpry about five years ago and I’ve had in my toolbox as a handy way to watch HTTP traffic.

I originally wrote this post for the Rackspace Blog but I’ve posted it here just in case anyone following my blog’s feed finds it useful.

The grades came back last Friday and I’ve passed the last exam in the requirements to become a Red Hat Certified Architect (RHCA).

Getting Fedora 16 working in XenServer isn’t the easiest thing to do, but I’ve put together a repository on GitHub that should help.

As promised in my earlier post entitled Kerberos for haters, I’ve assembled the simplest possible guide to get Kerberos up an running on two CentOS 5 servers.

Scientific Linux installations have a package called yum-autoupdate by default and the package contains two files:

I’ll be the first one to admit that Kerberos drives me a little insane.

I used to be one of those folks who would install Fedora, CentOS, Scientific Linux, or Red Hat and disable SELinux during the installation.

If you want to forward e-mail from root to another user, you can usually place a .

Before we get started, I really ought to drop this here:

Fedora 15 was released with some updates to allow for consistent network device names.

SELinux isn’t a technology that’s easy to tackle for newcomers.

I’m using SELinux more often now on my Fedora 15 installations and I came up against a peculiar issue today on a new server.

If you haven’t noticed already, full Xen dom0 support was added in the Linux 3.

Some might call me paranoid, but I get nervous when my package manager automatically removes a kernel.

It’s no secret that I’m a big fan of the RouterBoard network devices paired with Mikrotik’s RouterOS.

As promised in one of my previous posts about dual-primary DRBD and OCFS2, I’ve compiled a step-by-step guide for Fedora.

FUDCon 2011 in Tempe hasn’t even fully started yet, but it’s been well worth the trip already.

It’s not easy remembering which RPM packages contain certain files.