X File Explorer – Today’s Featured Application

A week or so ago, I was upgrading my Slackware systems to Current and noticed an unwanted “feature” had been added to my Xfce 4.10 Thunar file manager.

Thunar now shows all unmounted partitions on my systems by default. Years ago, I had this issue in Debian and had to create custom 10ignore-disks.fdi configuration files in /usr/share/hal/preprobe/95userpolicy to eliminate the display of unwanted volumes in Gnome/Nautilus. Unfortunately, that’s not a viable solution in my current situation. My Slack is not utilizing HAL anymore in its current version. I was at a loss on how to resolve this issue. With numerous partitions across three drives on my main system, it really made for a cluttered up Thunar left pane. See Fig 1 below:

Fig 1: Thunar showing unmounted volumes in left pane


I’m sure there is a resolution for this annoyance, but I haven’t found it as of yet. However, I did find a fabulous “work-around”, as mentioned in my previous article here about my adventures upgrading from Slack 13.37 to Current. I found a neat little file manager called X File Manager or Xfe. The more I use this little app, the more I really like it. See a shot in Fig 2 below:

Fig 2: Xfe showing standard Linux file system in left pane


As you can see in the above screenie of Xfe, I have just my standard Linux file system tree in the left pane. That’s how I want it. That’s how Thunar used to be before the recent upgrades to Xfce 4.10. Coincidentally, I had this same issue in Arch Linux when they first introduced Xfce 4.10 to their repos. I had other issues there also, namely failed auto-mounting, which I also experienced in Slack with this new upgrade. X File Manager solves it all.

This is a feature-rich and lightweight file manager. My only complaint is that it doesn’t use my already installed Xfce4 icon themes. That’s no big deal, though. The interface is fully customizable in regards to colors, fonts, highlighting, etc. I’m using the standard issue Tango theme that came with it. I can easily create (or modify an Xfce4 theme) a custom icon theme for it should I really want to some time in the future, but for now I’m just happy to be rid of the unmounted volumes and have my auto-mount back. It’s actually one-click mounting in Xfe. Still, faster than CLI mounting/dismounting… depending on your typing speed. ;)

So, if you’re tired of Nautilus, Dolphin, Konqueror (my old fav) or Thunar, give X File Manager a shot. You might find that it grows on you.

Xfe Homepage

From the above Xfe Homepage:

What is it ?

X File Explorer (Xfe) is an MS-Explorer or Commander like file manager for X. It is based on the popular, but discontinued, X Win Commander, originally developed by Maxim Baranov.
Xfe is developed since 2002 by Roland Baudin, a French Linux enthusiast.

Xfe aims to be the file manager of choice for all light thinking Unix addicts!

Have fun!



Running Pure systemd In Arch Linux

A recent upgrade in Arch Linux caused my Thunar file manager to lose its auto-mounting capabilities.

Now granted, auto-mounting of removable media (floppy, ZIP, CD/DVD, USB, etc.) on my system is purely a convenience. It’s not a necessity. I have no fear of the command line, so mounting manually can always be achieved. It’s the principle of the thing, dammit. What used to work should continue to work. Unfortunately, as we all know, thanks to updates of one sort or another (in any operating system), this doesn’t always hold true.

After doing some reading and research into the causes of Thunar’s apparent crippling, I became aggravated with Arch because recent updates have been plaguing me with breakage. Now, let’s be honest here… it’s not really Arch’s fault. Arch is a rolling-release distribution. Things change rapidly. The developers keep the base system closer to the bleeding edge that most periodic-release distributions. Anyone who uses Arch knows these things.

I run Slackware as my primary operating system on all my machines (except for an old Dell Latitude 610 running Bodhi Linux). Arch is my secondary (backup) operating system on my main system. I used to use Debian for this purpose, but as much as I love Debian, it is just too sluggish about getting current versions of apps in its repos. Now don’t all you Debian folks start throwing rubber chickens at me. I understand that Debian’s legendary stability is due to the fact that its stable repos contain only tried and truly long-term tested versions of applications. That is how it should be with Debian (I run Sid as a tester on my system, by the way).

So, back the Arch situation…

In the process of trying to find out what I needed to do to fix the auto-mounting issue, I ran across some information here and there about systemd. What is systemd, you might ask.

systemd is a system and service manager for Linux, compatible with SysV and LSB init scripts. systemd provides aggressive parallelization capabilities, uses socket and D-Bus activation for starting services, offers on-demand starting of daemons, keeps track of processes using Linux control groups, supports snapshotting and restoring of the system state, maintains mount and automount points and implements an elaborate transactional dependency-based service control logic. It can work as a drop-in replacement for sysvinit.

*from http://www.freedesktop.org/wiki/Software/systemd

I noticed that Arch’s core repo shifted udev from its stand-alone status to a sub-app of the systemd-tools application.

News: systemd-tools replaces udev

2012-06-01 – Dave Reisner

systemd and udev have been merged upstream. We will still ship them in separate packages. However, in order to keep things simple, udev will now be part of a package called systemd-tools. This package contains several other standalone tools which can be used without systemd. The astute reader will note that this also means the entirety of systemd is available in the core repository.

Please replace udev with systemd-tools when prompted. If you upgrade the linux package at the same time, you may see an error during initramfs creation that the udev hook is not found. After the upgrade completes, please rerun ‘mkinitcpio -p linux’ to ensure that a bootable image is created for the newly installed kernel.

Seeing this made me wonder if Arch was going to transition to systemd over initscripts sometime soon. To be honest, as some of the folks at Scot’s Newsletter Forums/Bruno’s All Things Linux can attest to,  I actually became a bit peeved… pissed off, you might even say. ;) All’s well, though. Ignorance is a great stimulant for fear and loathing. Knowledge paves the way for understanding and acceptance.

A little research was in order, so I spent the next few days after this initial rant about systemd learning what I could about it. Eventually, I decided to convert my Arch to systemd 100%, eschewing initscripts entirely. How did that go? Relatively well, actually. Read more about how I did it and how things turned out HERE, if you’re interested. I even managed to solve my auto-mount issues along the way.

systemd is available in many distributions already. I do believe that it has a good chance of replacing the standard initscripts method of services in GNU/Linux in the near future. If you’re a tinkerer, go give it a try on some test partition on one of your systems. I wouldn’t recommend converting 100% to systemd on your main operating system, though; not unless you really know what you’re doing. It wouldn’t hurt to learn the fundamentals of systemd. I believe it’ll be around for a while.

Have fun!


Further reading:





*Sorry for the raw links. I’m being lazy today. :(

A Short Trip Down Memory Lane

Back in 2006, I was a fresh-faced new GNU/Linux adventurer.

About a year after my first install of Ubuntu, I posted THIS at Scot’s Newsletter Forums, a site which has since become my second home. Some of my opinions have changed since then. For instance, I don’t use KDE anymore (not since 3.5). I also don’t care for Google too much these days, not since they’ve started showing their greedy fangs… “Do no evil” Pffffft! Yeah, right. Anywho…

Relatively quickly I settled on Slackware as my primary operating system. My GNU/Linux mentor, Bruno Knaapen, once predicted that I would end up with Slackware because I definitely had the Slacker attitude. Miss you, Bruno, old friend. He called that one right. I run Slackware as my primary and Arch Linux as my secondary (backup) OS on my main system. I also run Slack on my laptop and my shop systems.

Back in the beginning of my GNU/Linux adventures, I ran Slack as primary and Debian as secondary. Arch beat Debian out for that position quite a while back, though. Don’t take this the wrong way. I still have a deep and undying love for Debian. I believe it is one of the finest distributions of GNU/Linux ever. About the only complaint one can have with Debian is that its software is a bit dated.

No, Debian is not a risk taker’s distro. It’s staid and stable as a ROCK. Part of this is because of all that older and well-tested software in its huge repository. If you want a distribution that is just going to work… and work… and work without a glitch or burp, Debian is for you.

Earlier today, we were discussing Debian at Scot’s Newsletter Forums – Bruno’s All Things Linux. I realized that I had not had a copy of Deb on any of my machines for a year or so. That’s not like me. I always keep an up-to-date Deb somewhere on my systems… just in case. I decided to download and install it. I have numerous “tester” slots open on my main machine, so space is not an issue.

The install went off without a hitch. I had to make some minor edits to Arch’s menu.lst (the MBR controlling boot-loader on my system) and to Debian’s fstab (switch from UUIDs to /dev/… nomenclature). My only issue now is that I need to install the proprietary Nvidia drivers. I usually do this manually, but this time around, I think I’ll do it the “Debian Way“. Knowing Debian, this shouldn’t even cause me to break a sweat.

If you have moderate GNU/Linux experience, and have never tried Debian before, I strongly recommend that you give it a looksee. Next to Slackware, Debian is the oldest still maintained GNU/Linux distribution. Slack only has it beat by a few months, actually. Try Debian. You’ll learn a lot about GNU/Linux with this distribution. You’ll also get the unique experience of using one of the absolute best package managers in existence… apt.

Until next time…


Mate – an Alternative Desktop Environment

So, you’re not too thrilled with Gnome 3, Unity, or KDE 4. Well, here’s another option…

MATE is a Gnome 2 fork started by Arch Linux Forum member Perberos. I like the description: MATE Desktop Environment, a non-intuitive and unattractive desktopHeh! Can’t get much more honest than that.

Christopher Tozzi at varguy.com wrote a nice article about MATE. Here’s a snippet or two:

Right or wrong, plenty of Linux users — such as this guy — have been less than happy with the interface changes wrought by the advent of Unity and GNOME 3. Lucky for these people, there’s hope in the form of MATE, a fork of GNOME 2…

To be perfectly upfront with my readers here, I have never tried Gnome 3 or Unity on any of my systems. I do have some experience with KDE 4, as many of you know; none of it was pleasant. My main desktop environment is Xfce. I’ve been using Xfce primarily in my main (Slackware) and secondary (Arch) installations for quite some time now; ever since KDE 4 first came on the scene, actually. I was a big KDE fan up till then. Oh well… the world moves on.

Tozzi continues…

GNOME 2 may not have been ideal for touchscreens or tablets, and it wasn’t the most visually dazzling interface out there. But it got the job done without giving me a headache or turning every mouse click into a surprise by eliciting totally unpredictable behavior.

A surprise with every mouse click. Hmm… that sounds a lot like my KDE 4 experience. ;)

Seriously, folks… as I always say, whatever works best for you is what’s best for you. If you would like to go back to the older, more stable, less visually orgasmic Gnome 2 days, give Mate a shot.

Have fun!


Today’s Featured Distribution – Arch Linux (Revisited)

Today’s Featured Distribution – Arch Linux

Posted by V. T. Eric Layton on Apr 8, 2010

Let’s do things the “Arch Way” for a bit, OK?

As you can probably tell from this recent article, I do maintain a good sized distro farm. Sometimes, I’ll plow up one field and plant a new distro. Other times, I leave a field planted with a certain distro for long periods of time. This is the case with Arch Linux. It’s one Linux distro crop that I probably will continue to plant regularly.

You will always find two distributions on any system I have up and running for my own use; Slackware, my primary operating system and Debian, my backup operating system. Both are what you might call stable to the point of ennui. That’s why they are my operating systems of choice. I’m an old geek. Old geeks don’t like surprises. We like everything steady and familiar.

If someone were to ask me, “Hey Eric, what would you do if you couldn’t run Slackware or Debian?” I’d have to admit that Arch Linux would probably be my next choice as a primary operating system. I’ve always considered Arch to be like a secret love child of Slackware, even though they have no direct relation in the Linux Tree. I think of Arch in this light because it shares two goals with Slackware; namely, beautiful simplicity and a lightness of being.

It’s almost Zen-like, huh? Ahhhhmm! Ahhhhhmm!

Oops! Wrong kind of yogi. I meant… er, never mind.

Anyway, where was I? Oh yeah…

So, about Arch Linux… Oh, did I mention that Arch has an exceptional support community, excellent documentation, and a fabulous wiki? Well, it does. Visit the Arch Linux main page. Do a little reading, follow some links. There is a wealth of information at that site. The Arch Wiki has been helpful to me many times in resolving issues that were not even specific to Arch. There is a lot of compiled Linux knowledge there. When you’re visiting the wiki, be sure to check out the Beginner’s Guide… absolutely outstanding!

And lastly, if you would like to give Arch a looksee, I highly recommend securitybreach’s excellent installation tutorial available for you at Scot’s Newsletter Forums – Bruno’s All Things Linux – Bruno’s Classroom –> Installing and setting up Archlinux.

Have FUN with it!

Until next time…


Update – 8 August, 2011: Since first publishing this article, Arch has been promoted to my secondary operating system on my main system. I still love Debian, but was having issues with Squeeze, so…


This article was originally published on my Nocturnal Slacker | Lockergnome blog. To read the it there and see the accompanying comments, click HERE.

Sometimes, You Just Have to Revert

For a couple weeks now, I’ve been having issues with Thunderbird 5 in my Arch Linux installation.

I have a few much-used extensions installed in my Thunderbird, and 5.x broke four of them when it updated in Arch from 3.1.11. I tried a few work-arounds. I tried to live without the extensions. This morning I decided that I just wasn’t going to deal with this any longer. I reverted. How’d I do that, you might be asking? Well, with Arch (in most instances), it’s pretty simple.Photobucket

First item of importance is that I had a backup of my Thunderbird 3.1.11 .thunderbird directory backed up on separate media (DVD). Second item is that I had not run pacman -Scc in a while. This command clears the cache of installed items in Arch. So, with those items being satisfied, I was able to revert using the magical pacman -U command.

#pacman -U thunderbird-3.1.11*

The asterisk denotes auto-completion at the command line. BASH will automatically add the remaining characters to the command.


And with that simple series of commands, my world is back to being wonderful once again. Oh, and to make sure that I don’t accidentally upgrade T-bird on my next pacman update session, I’ve added it to the ignore list in my pacman.conf file.

#vim /etc/pacman.conf

# Pacman won’t upgrade packages listed in IgnorePkg and members of IgnoreGroup
 IgnorePkg   =  thunderbird

There you have it. The wonderful simplicity of Arch package management.

Have fun… and learn something while you’re at it. :)


They’re Like Lay’s Potato Chips…

…you can’t have just one. With that thought in mind, here’s a freshly minted GNU/Linux distribution for you diehard experimenters to check out.

LDR – Linux Done Right

LDR is another wonderful choice (ain’t GNU/Linux great!?) in your further Linux adventures. It was recently transformed from idea to actual distribution by friend Thomas Medhurst. It’s based on Arch Linux and uses the Gnome Desktop Environment.

Keep in mind, this one is fresh off the assembly line. It might need some polishing and tweaking here and there. Get in on the ground floor on another new GNU/Linux, folks. Thomas is also very interested in hearing any and all feedback and suggestions. You can contact him at the LDR webpage or his own personal webpage.

Give it a go… might be fun!



A Little Help Here, Please…

I know that a lot of very knowledgeable gurus read this site, and I’d like to ask a favor of some assistance with an unusual issue that I’m currently having. Any help would be appreciated.

This article was originally posted as a forum submission at two different forums. You can read those threads here and here for some more info and progress.

Here’s a little background for everyone…

I am running Slackware as my primary operating system and Arch as my secondary (backup) operating system on my main computer (ericsbane05). I also have installations of MS Windows XP, CentOS, and Debian on a separate hard drive.

SATA looks like this on my system:

SATA0 channel = /dev/sda, /dev/sdb
SATA1 channel = /dev/sdc, /dev/sr1
SATA2 channel = vacant, vacant

Originally, these drives were in ericsbane03 and 04 with one exception. I only had two SATA drives and one EIDE drive then. The EIDE drive was removed when building this new system and replaced with the drive /dev/sdc that you see above on the SATA1 channel (/dev/sr1 is a DVD R/W, by the way).

Arch Linux’s GRUB controls /dev/sda’s MBR and is the main bootloader for all operating systems on this system. Here’s what my menu.lst looks like:

<snip># IMPORTANT –> Arch GRUB sees /dev/sda as hd0, but /dev/sdb as hd2 (should be hd1).
# (1) Slackware64-13.37
title  Slackware Primary
root   (hd0,0)
kernel /boot/vmlinuz root=/dev/sda1 ro
initrd /boot/initrd.gz
# (2) Arch64
title  Arch Linux Secondary
root   (hd0,4)
kernel /boot/vmlinuz26 root=/dev/sda5 ro
initrd /boot/kernel26.img

# (3) MS Windows XP/SP3
title MS WIN XP Pro
root (hd2,0)
map (hd0) (hd2)
map (hd2) (hd0)
chainloader +1

# (4) CentOS64 5.6
title    CentOS Tester01
root    (hd2,5)
kernel    /boot/vmlinuz-2.6.18-238.9.1.el5 root=/dev/sdb6 ro
initrd    /boot/initrd-2.6.18-238.9.1.el5.img<snip>

You can see that Arch’s GRUB thinks that /dev/sdb is (hd2), when in fact, it should be (hd1). This was like this originally because of the hybrid EIDE/SATA setup that I had on previous systems. Now that I’m running pure SATA, I’d like to get this fixed. Here’s what I’ve done so far:

1) I manually edited /boot/grub/device.map to look like this:

(fd0)    /dev/fd0
(hd0)    /dev/sda
(hd1)    /dev/sdb
(hd2)    /dev/sdc

It was originally incorrect, but this didn’t fix the issue. GRUB was still seeing the drives incorrectly.

2) I then deleted all files from the /boot/grub directory and used pacman to uninstall GRUB completely.

3) I then reinstalled GRUB and created a new menu.lst with the correct /dev to (hd) conversions. It looks like this now:

# (1) Slackware64-13.37
title  Slackware Primary
root   (hd0,0)
kernel /boot/vmlinuz root=/dev/sda1 ro
initrd /boot/initrd.gz
# (2) Arch64
title  Arch Linux Secondary
root   (hd0,4)
kernel /boot/vmlinuz26 root=/dev/sda5 ro
initrd /boot/kernel26.img

# (3) MS Windows XP/SP3
title MS WIN XP Pro
root (hd1,0)
map (hd0) (hd1)
map (hd1) (hd0)
chainloader +1

# (4) CentOS64 5.6
title    CentOS Tester01
root    (hd1,5)
kernel    /boot/vmlinuz-2.6.18-238.9.1.el5 root=/dev/sdb6 ro
initrd    /boot/initrd-2.6.18-238.9.1.el5.img<snip>

The entries for Windows and CentOS reflect the new (and correct) device.map in /boot/grub.

4) After all this, I reinstalled GRUB to the MBR like this:

# grub-install /dev/sda

Unfortunately, GRUB is still seeing /dev/sdb as (hd2). I can get all my operating systems to boot just fine by using the wrong (hd) strings in menu.lst, but I’d really like to get GRUB to work the way it’s supposed to. I’m sure there is something simple here that I’m missing. Any help would be appreciated.



Addenda: Here’s a copy of my fdisk -l output along with notations. It might be helpful:

Disk /dev/sdb: 250.0 GB, 250000000000 bytes
255 heads, 63 sectors/track, 30394 cylinders, total 488281250 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0009e140

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1    *      16384    51216383    25600000    7  HPFS/NTFS/exFAT <– MS Windows XP C partition
/dev/sdb2        51232768   102432767    25600000    7  HPFS/NTFS/exFAT
/dev/sdb3       102453181   488270159   192908489+   5  Extended <– swap
/dev/sdb5       102453183   106550639     2048728+  82  Linux swap
/dev/sdb6       106565823   137289599    15361888+  83  Linux <– CentOS /
/dev/sdb7       137304783   188501039    25598128+  83  Linux
/dev/sdb8       188516223   219239999    15361888+  83  Linux <– Debian /
/dev/sdb9       219255183   270451439    25598128+  83  Linux
/dev/sdb10      270466623   301190399    15361888+  83  Linux <– tester /
/dev/sdb11      301205583   352401839    25598128+  83  Linux
/dev/sdb12      352417023   383140799    15361888+  83  Linux <– tester /
/dev/sdb13      383155983   434352239    25598128+  83  Linux
/dev/sdb14      434367423   488270159    26951368+  83  Linux <– storage

Disk /dev/sdc: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0002cd1d

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1           16065   102414374    51199155   83  Linux <– Slackware backups
/dev/sdc2       102430440   204828749    51199155   83  Linux <– Arch backups
/dev/sdc3       204844815   488392064   141773625    5  Extended
/dev/sdc5       204860880   307259189    51199155    b  W95 FAT32 <– MS Windows backups
/dev/sdc6       307275318   409673564    51199123+  83  Linux <– tester backups
/dev/sdc7       409689693   488392064    39351186    b  W95 FAT32 <– common storage

Disk /dev/sda: 250.1 GB, 250058268160 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488395055 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0×24812481

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *       16065    51215219    25599577+  83  Linux <– Slackware primary operating system /
/dev/sda2        51247350   153645659    51199155   83  Linux
/dev/sda3       153661725   488392064   167365170    5  Extended
/dev/sda5       153661788   204860879    25599546   83  Linux <– Arch secondary operating system /
/dev/sda6       204877008   307275254    51199123+  83  Linux
/dev/sda7       307307448   311403959     2048256   82  Linux swap <– swap
/dev/sda8       311420088   488392064    88485988+  83  Linux <– archives

Thanks again. :)

Ericsbane05 LIVES!

What is ericsbane? Well, that’s what I name some of my computers. I also have ericslaptop01 and ericsshop01 and 02.

What a strange name this ericsbane thing. Where’d that come from? you might be wondering. The definition of bane is a person or thing that ruins or destroys or the name of a deadly poison. HA! Both are accurate sometimes when it comes to my computering hobby. Computers can be my bane, but I love ‘em, anyway.

As some of you may know from reading here and here, I have been having some hardware issues with my main system. And as a sidebar to this, I’ve also been trying to put together a system for my shop. Well, it’s finally all come together. What a nightmare it’s been. Of course, if I had money to burn, this wouldn’t have been an issue at all. Unfortunately, money is very tight right now. We won’t even go into that.

So, what happened this weekend? I woke up Saturday morning jonesing to play one of my vid games on my system. S.T.A.L.K.E.R., Far Cry, Deus Ex, anything. I just wanted to frag stuff. Know what I mean? I haven’t been able to play any games on my main system due to issues with a bad PCIe socket, which has forced me to use crappy onboard graphics. Hmm… can’t play many games these days with a 2900fps framerate.

I made the mistake of going to the local CompUSA (Tiger Direct) store after seeing a really decent mobo/micro bundle advertised online. Hmm… I had spent a few bucks recently on a replacement mobo from them, but it didn’t work out, so I was given a refund. I figured that money was already spent. I had it set aside for a rainy day. Well, that day was Saturday. I went to the CompUSA and got myself a mobo/micro combo.

I came home and, after much travail and gnashing of teeth, I managed to cobble together ericsbane05. Here are the specs:

Cooler Master Chassis Mid Tower Elite 334 Nvidia Edition ATX Casing
Cooler Master Extreme Power Plus – 650watt power supply
785GTM-E45 socket AM2+ motherboard
AMD Phenom 9750 Quad-Core Processor
AMD chipset
4Gig Centon DDR2 800 PC-6400 RAM DDR 800 (slots 1 & 2)
EVGA Nvdia GeForce 450 GTS
IDE 0 Master: Master: DVD Writer 840
IDE 0 Slave: ZIP 100
SATA 0: Western Digital 250Gig
SATA 1: Western Digital 250Gig
SATA 2: Western Digital 250Gig
Standard 3.5″ floppy
Seven (7) cooling fans
HP Deskjet 842C printer
HP Scanjet 3400 flatbed scanner
HP W1907 LCD monitor
Altec Lansing (front) + Harman Kardon (rear) speakers
Dell USB keyboard
Logitech Trackball mouse

So, there ya’ have it. Here’s what the framerate on this baby looks like now:


So much gooder! I can play games again! I can shoot and frag away my frustrations. It’s better than religion, I’m telling you. Woo-hoo!

Oh, and as a by-product of this adventure, I also was able to salvage ericsbane04. I slapped the guts of that system into another box and changed its name to ericsshop02. It’s loaded with Slackware current and is sitting on the bench outside in my shop. I put ericsshop01 on the shelf as a backup system. We are just on a roll here, huh?

I have 99.9% of the kinks worked out of the new ericsbane05. There are always issues when you install pre-existing operating systems onto new hardware. There are issues with drivers, disk nomenclature, sensor daemons, GRUB, etc. I’ve got them all squared away but one, I think. I’m having a minor issue with Arch’s GRUB, the bootloader for my entire system (numerous operating systems installed). It has incorrectly mapped the hard drives. I’m working on it, though.

That, friends, is how I spent the last three days of my life. Bane, indeed. See what I mean?

We’ll have some new lessons coming along shortly. Stay tuned…

Until next time…

~Eric, the happy 19000fps framerate, fraggin’ Slacker!


Get every new post delivered to your Inbox.

Join 37 other followers