Jan 192013
 

I used Fedora 17 on our home “server” (SSH, VNC, media and integrated with the sound system), and with Fedora 18 being out I figured it would be the best one to try to upgrade on.

Of course you’ll want to make backups before tryign this yourself if you haven’t already.

I’m normally quick to just format the / partition and do a clean install as I keep a separate /home partition, which keeps things pretty safe.

The new upgrade tool is called FedUp.

That was definitely a very smooth process for me. I ran:

su -c ‘yum update ; yum install fedup && fedup-cli –network 18 –debuglog fedupdebug.log’

After everything had downloaded, I was informed to reboot and the upgrade would begin. I restarted and it did. A progress bar came up to show me the status of the upgrade, and at some point (well it’s not like I said here watching the progress bar) my system was up and running as Fedora 18.

The only thing I had to do was set my custom SELinux and firewall rules again. So far so good.

Sep 192012
 

One of the most common questions I see around Linux communities with new users is: Which distribution should I choose?

Or one of the variations, all basically asking the same thing.

“Which Linux OS should I try?”
“I have an old computer which one should I use?”
etc.

People start to seem irritated with this question, and I understand that because it gets asked a lot. I think the problem for most new users is the overwhelming number of distributions available, and not knowing where to get started.

Continue reading »

Aug 242012
 

I posted some useful tidbits about yum on reddit semi-recently. The original post was in reply to somebody looking for yum understanding/help. I decided it would be worth copying over here, so I left a few tidbits out and modified it to be more useful here.


yum – Yellowdog Updater Modified

(Description copied from the man page) “DESCRIPTION yum is an interactive, rpm based, package manager. It can automatically perform system updates, including dependency analysis and obsolete processing based on “repository” metadata. It can also perform installation of new packages, removal of old packages and perform queries on the installed and/or available packages among many other commands/services (see below). yum is similar to other high level package managers like apt-get and smart.”

In Fedora (and many other Linux distros) there is a large source of programs, applications, etc. very similar to an “app store” (to simplify it). The package manager to handle those applications will vary between distros. We’re talking about Fedora, so, want to install a new program? It’s likely available with a quick command: yum.

Using yum requires root access for some actions, like installing new packages or removing (erasing) installed packages. In other actions (search, info, and other non-administrative actions) you can run it as a regular user.

yum search pidgin

Once you run that, it’ll search for packages available with the word “pidgin” in them.

Don’t see something you want or need? You can add third party repositories to your system to search for more programs. Of course you’ll want to be careful with that, but what fun is using Linux if you don’t break a few things?

If you want to get more comfortable with yum, try a few things out while you get comfortable.

yum list installed 

^ This will show you what you’ve installed.

yum search searchterms 

^ Replace searchterms with what you’re searching for. You can see what’s available to install.

yum info searchresults 

^ Want to know what that package you just found does? Find out by putting the name in the place of searchresults.

yum install searchresults -or- su -c 'yum install searchresults'

^ When you found something in the search, you can install it by replacing searchresults. Here’s where su comes in. You need to be root here, so you can run ‘su’ and completely change over to root, or you can run ‘su -c’ followed by the command (like in the example above) and you’re telling it that you want to run this one single command as the root user.

yum remove searchresults -or- yum erase searchresults 

^ That program didn’t suit your needs? That’s how you can remove it. (remove is an alias for erase). Needs root access.

yum update 

^ Want to see if you have any updates ready for your system? That’ll do it. Needs root access.

Of course these are just some examples of what you can do with yum. Open up terminal and run ‘man yum’ (no quotes needed) and read more!

Note that Fedora does have a “Software Center” – an app that is designed to give you a visual frontend for installing/removing/searching for new packages. What you see in there is basically a visual front-end for yum. It’s running the commands for you while you’re clicking around.

Jun 282012
 

At some point in the last few weeks I got hung up on wanting to play with Debian, but not Debian Stable. No, I want newer versions while still remaining pretty stable, so I went for Debian Testing. Noting that I was ditching Linux Mint 12 KDE (based on Ubuntu), not due to stability issues, but personal preferences and just getting in and getting my hands dirty.

Everything went pretty well, minus one major issue (and some odd audio issues): Debian Testing does not support fglrx, at least within the last few weeks. It looks like this has been an on again off again issue for Wheezy due to incompatibilities. The opensource driver was okay, except for the fact that games were miserable or wouldn’t run at all.

However, the stability was actually great. There are “stable” versions of distros available that are less stable than Debian Testing. I was running Debian Wheezy with KDE and really enjoying it.

Then I wanted to upgrade my video card and move over to 3 monitors. While Debian should support this, the fglrx driver was becoming more of an issue.

While skipping a lot of boring details, I ended up trying out Fedora 17 (KDE spin). Everything went well, and my experience with CentOS (mostly server experience) came into play. After adding the rpmfusion repository, I’m really enjoying it. Moving over to yum and RPM is a bit odd for me, but I can definitely say I’ve adjusted.

Also, gnash is a good opensource flash alternative, but it is limited. If you try Fedora, go for Adobe Flash unless you are completely against “non-free” (in which case, avoid my rpmfusion link above). Here is some useful information on that. Maybe one day we’ll get past Flash entirely…

Fedora’s installation process was different than most I’ve seen. It runs a basic install like most distros, asking for the root password, partitions, etc. — but it doesn’t come up and ask for the user profile information until after you restart, and a second part of the installation begins. The user I chose still existed on the system (separate /home partition anyone?) and Fedora’s installer offered to fix the permissions/ownership for me. Normally I have to fix the permissions/ownership manually after the installation, so that was pretty cool.

Fedora is the only distro I’ve tried on my desktop that did not include Chromium in the repositories. Apparently there are reasons for this, but it’s easily remedied (I opted to just install Chrome from Google – shame on me?).

Fedora has several spins. While you can just download Fedora and modify it the way you want it, the spins may give you an easy start. For example, I enjoyed the convenience of the KDE spin (the default installer is Gnome 3, however you may feel about that).

All in all, I’m happy with Fedora 17 on my main computer. We’ll see how long it lasts before I start messing around with something else (out of boredom or otherwise), but it looks like I’ll be sticking with this for a while. So far so good.

May 052012
 

It was recently pointed out to me that Linux Mint 12 with MATE does not have power management settings available.

I know that Mint 12 KDE has power settings, so I decided to check it out. I installed Mint 12 MATE on another device and it wasn’t there.

I could not locate screensaver options, power management settings, etc. — The person’s goal was to be able to shut down once the laptop lid was closed.

After doing some digging, I discovered that Linux Mint 12 MATE comes with version 1.0 of MATE, which did not include mate-power-settings or mate-screensaver. MATE 1.2 is the current stable edition, which does include the power management applications. I was led here and followed the directions on installing version 1.2.

I read and followed the directions for Mint as well as Ubuntu. If you install the packages recommended for Ubuntu it will end up upgrading most of the MATE packages while it adds and removes a few others.

Run sudo apt-get update && sudo apt-get upgrade to make sure everything else is up to date as well.

Go ahead and check to see if mate-screensaver and mate-power-settings are both installed. If so, log out and log back in so that all of the new additions can load (If not, install them). You should be able to manage the power settings now.

I really like MATE; It’s nice to see things the way they used to be on Gnome 2, and yet better with new improvements. R.I.P. Gnome 2, and hello there MATE.

Apr 252012
 

As much as I enjoyed using Sabayon, a couple of weeks ago I went distro-hunting again.

When you’re in the middle of working on a project and you have to stop to fix a few things on your computer it is annoying. When it happens multiple times… well, here I am.

Sabayon is a great distro, but being a rolling release that focuses on the newest software, most of which hasn’t hit a stable version yet, an unstable environment is going to be a possibility. I’d use Sabayon again, but probably not on my primary machine.

I spent a little time with Linux Mint Debian Edition (LMDE) and enjoyed having some of the Debian perks again (apt-get anyone?), but trying to keep with KDE, for some reason converting LMDE over to KDE on multiple computers resulted in terrible audio issues. Having seen how the Mint team handles things, I ended up deciding to go with Mint 12 KDE, even if there Ubuntu bloat behind it.

Mint 12 KDE has been stable and pretty up to date. I’m on KDE 4.7.4 rather than 4.8.1, but I haven’t noticed any differences other than the inability to use my old KDE profile. I could upgrade it, but right now I don’t see a reason to.

Was moving over the Mint lazy? Sure, I could be primarily using Gentoo or Arch (not that I have anything against them – they’re great distros) to try and show the size of my lower appendages online (read: e-penis), but right now that’s not going to work for me. I need to be able to focus on productivity, and a stable distro is how I’m going to accomplish it.

Mar 202012
 

I like to carry a flash drive around with a light version of Linux, such as Puppy Linux. This has come in handy a few times for computer recovery (for other people). I also wanted something more aesthetically pleasing alongside it.

I decided I would make a dual-boot flash drive. I had one a few years ago that I made with 3 – 4 different distros, but I’m pretty sure it got formatted somewhere along the way.

First you’ll want to open up UNetbootin and install Puppy on the flash drive. Once this is completed, exit unetbootin and copy all of the files to a safe location outside of the flash drive. I made a folder on my desktop named PuppyUSB and moved everything there (completely removed from the flash drive).

Open unetbootin again and install the second distro either from the downloadable list, or an ISO you have handy.

Once the installation is complete, copy the contents of your PuppyUSB folder into the flash drive, but do not overwrite any duplicate files.

You’ll then need to then open up the syslinux.cfg file on the flash drive, as well as the local copy from PuppyUSB. The one from PuppyUSB will look something like:

default puppy
display boot.msg
prompt 1
timeout 50

F1 boot.msg
F2 help.msg
F3 help2.msg

label puppy
kernel vmlinuz
append initrd=initrd.gz pmedia=cd

The second will look something like this (though it may vary depending on the distro):

default menu.c32
prompt 0
menu title UNetbootin
timeout 100

label unetbootindefault
menu label Default
kernel /ubnkern
append initrd=/ubninit boot=live config quiet

With this, you will need to add an entry for Puppy into the list, and modify the original entries a bit. Look for where the list begins with “label ubnentry0, ubnentry1…” right below “label unetbootindefault”. You will want to copy the menu information from Puppy over, adding a new ubnentry0 above the original (or ubnentry1), and re-ordering the rest of the menu to maintain the sequential order (ubnentry2, 3, 4, etc.)

I have two entries that I have modified under unetbootindefault:

label ubnentry0
menu label Crunchbang Live i386
kernel /live/vmlinuz1
append initrd=/live/initrd1.img boot=live config quiet

label ubnentry1
menu label Puppy
kernel vmlinuz
append initrd=initrd.gz pmedia=cd

After saving the file you should be able to properly boot from either distro from a compatible computer (note that not all computers will boot from USB, though most newer ones will).

With this information, it is also possible to add more than 2 distros to a flash drive, but this also increases the chances of botching something up in the config file.

Mar 182012
 

When first learning the command line (terminal), it can seem overwhelming for some people. There’s nothing wrong with that. Learn at your own pace, ask questions, and don’t forget to search online.

With that being said, I figured I’d drop this useful reference for those who may use it. Consider this a reference guide, or a cheat-sheet if you will. It isn’t an infinite source of every command you’ll use or need, but it should come in handy. Granted, this isn’t just for new users or those just starting out with terminal. This covers a lot of useful topics:

File Commands
SSH
Installation
Network
System Info
Searching
Process Management
File Permissions
Compression
Shortcuts
VIM (text editor)

 

Click the thumbnail for a readable size. Full size here.

If you know the original source for the image, let me know and I’ll give credit.

Mar 152012
 

While working on my CentOS 5 server, I decided to run a few basic tasks via a “for loop”.

Example:

for i in `find -name blah -type f` ; do stat $i ; done

The find command alone had no issues, running a command had no errors, but running it as a for loop:

stat: cannot stat `\033[Kblah’: No such file or directory
stat: cannot stat `\033[Kblah’: No such file or directory
stat: cannot stat `\033[Kblah’: No such file or directory
stat: cannot stat `\033[Kblah’: No such file or directory
stat: cannot stat `\033[Kblah’: No such file or directory
stat: cannot stat `\033[Kblah’: No such file or directory
stat: cannot stat `\033[Kblah’: No such file or directory
stat: cannot stat `\033[Kblah’: No such file or directory

With a bit of Google searching, it didn’t take long to see that “\033[K” is supposed to “erase to end of line”. Basically, when using it with the echo feature, you’ll get this result:

root@fsckinglinux # echo -en ‘test 123 123 \033[K’
test 123 123 root@fsckinglinux #

Okay, yes I see how this is relevant. What I couldn’t figure out is why suddenly it was printing the information at the beginning of every line.

After Googling it for a while, I finally found an old forum topic in a dark, dusty corner of the internet where somebody mentioned it. Using “ls –color=always” causes this issue to happen, and apparently I got lazy and set an alias for this a while back. Time to go back to ls –color=never, at least for for loops.

This may describe how I felt during the process of resolving the issue.

I feel like I should’ve known this, but it is time to move on. Fixed, learned, and passing the information on to you.