Find me on Google+


Fixing gvfs automount permissions problems

The fix is to get the drives off of gvfs and into fstab.  For me it was a luxury that wasn't meant to be.  A half dozen USB disks of varying sizes all hooked up and mounted nicely.

Well to fstab it needed to be.  Here's how to do it nicely

1)Run "gnome-disks" and rename them if need be.  In my case I had several 500G Seagate and 1TB WD entries.  Make life easier on yourself if you haven't already.

2)Open up 2 terminals.  In one, run 'sudo gedit /etc/fstab' and in the other just 'sudo su -'

3)Use the second terminal to get the block ID information by running (need to be root) 'blkid /dev/drive'

4)Make your fstab look something similar (add), presuming the mountpoints you have figured out andyou are using ext4:


5) Unmount the drives if need be and issue a 'mount -a' command



Not dead yet!

Been a year since last update, and no I am not dead ... yet.


From what I have posted last, some work has been done, but not all.  Its been a bit hectic, and forcing me in a bit more of a relax rather than do more work mode.  Got most of the server stuff complete, sans the email migration.  Just havent had the time to get all the SSL stuff working yet.

Also have been relaxing with Star Trek Online and Neverwinter with a increasingly litte amount of Minecraft.  Not that MC isnt a blast (it is), but just too many new updates from the former two to stay off for TOO long.


Have a bunch of RHEL6 vids awaiting post production work.  When I have cleaned them up and do a final once over for accuracy and sanity in the approach, I will post them here and on YouTube.


A few updates

I have been very busy as of late, mostly at work.  That said, I have been working on a few projects of note.


First, I am in process of getting everything migrated over to a new server.  Yes, I am dumping GoDaddy and Squarespace for a self run Linode.

Pertaining to the first point, I have been working on getting Teamspeak and Minecraft working on there first, then the others.  In my escapades here I have run into a few issues I had to overcome, and with that comes the third point.

Third, and lastly, I am going to be doing a video series on running, adminning, and tricks to RHEL (and its clones) servers.  I will eventually get to desktop orientated tasks (GNOME 3 has a bundle of hidden gems).  The idea is to use the RHEL docs as a guide, and step thru the commands with commentary.  GNOME3 (and Cinnamon for that matter) have screencasting software built in, so this will be rather easy. 

My first few videos will be getting RHEL6.2 installed and prepped.  There are steps to locking down your setup that should be obvious, but from what I have been seeing around -- rarely implemented.  Another will be on creating custom daemons.  Another is on Red Hat's new SPICE protocol for VMs.  This is going to be a good one :D  If you haven't tried SPICE, you are missing on alot of power there.  Think warp drive for thin client, or remote VM shares.  I was blown away a few months back when I first tried it out.

Any other ideas are welcome, but for starting out, the first dozen or so are pretty much in stone, so don't fret if your idea isn't done immediately.  My time lately has been short, so I am limited to a few videos a week tops once I get the Linode done (first priority, I a pissing alot of cash away by not using it).


Pulseaudio quirks -- possible fix.

If you run into an issue with PA where you reboot and no sound, there is a potentially easy fix.  Kill your ~/.pulse/ directory.  Thats all I had to do in the end (after pissing 2 hours away).  Alot of people had inadvertently misled me with bad updates, but the trouble shooting trick that you would need to do is figure out WHERE the problem really lies.

  • Kernel
  • Pulse
  • Pulse Plugin

I noted that the kernel could see all my devices, as lsusb and lspci showed them properly.

When I tried to load pulse, thats when the fireworks began.  A yum reinstall and downgrade proved not worthwhile.  After a bit more digging around, I noticed that one trick can kill a few birds with barely a pebble -- vaping the .pulse config folder.

Well that problem has been neutralized, and I figure that I see alot of nifty sound hacks that can easily run you down this path, and alot of people that say PA worked fine for a while, now its broke.  Perhaps this is/was the solution.


Atrix 4G Unlock Instructions

Sadly until I do some extensive research, I am unable to locate a viable solution using GNU/Linux as the host OS.  For the process I needed to use Windows.  The process works fine, but I would vastly prefer a solution on GNU/Linux or BSD, of which I located ones with tools that no longer existed at the mentioned/linked location.  Once I can do this on GNU/Linux, I will post the steps, and host the files so that dead filesharing hosts or changed links are a non-issue.

That said, here we go!



  1. Read over the following links, as they are handy and will have useful info for the remainder of this whole process -- General Atrix 4G Modding info    Unlock procedure that I followed
  2. Backup your data folder on the Atrix itself.  This will go bye-bye when you are unlocking.
  3. Download and install the Windows Motorola Drivers
  4. Download the unlock tool
  5. Unzip the archive.  Open the file that was enclosed called MAIN.BAT
  6. Follow the instructions.
  7. Note -- there may be a part in which you will error out with a missing/unbootable OS 'ERROR 0x1000' message.  Thats normal.  Get back into FASTBOOT mode as instructed earlier in the procedure.  You may continue along then just fine.  I did run into this, and had no issues.  There are some allusions to other errors that can crop up that can be alleviated by just continuing.

Some Notes to keep in mind:

  1. If you rooted your device, when complete, re-root.
  2. If you installed CWM recovery, you may need to reinstall to fix things.  CWM recovery requires an unlocked and rooted device to properly install and function.  The ROMManager utility did the trick for me, and did not need to go hunting for other recovery ROMs.  That said, I don't have nandroid support, which most others tout as a main feature.  So, perhaps I should :P
  3. And a forewarning, any use of CWM recovery to do backups or restores will require the unit to be plugged into a charger -- not a PC.