Archive for the 'Tools' Category

My new Eeep C

This little machine is pretty nice. I’m getting used to the interface right now as the keyboard is a bit smaller than my normal T60p. A few keys are in a different spot, but overall, this little machine rocks!!

Probably my biggest headache right now is the right Shift key is further over than I regularly expect it to be. Have a look at the specs:


# cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 13
model name : Intel(R) Celeron(R) M processor 900MHz
stepping : 6
cpu MHz : 630.081
cache size : 512 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr mce cx8 apic mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss tm pbe up bts
bogomips : 1261.18
clflush size : 64

# cat /etc/*release
Fedora release 8 (Werewolf)
Fedora release 8 (Werewolf)
Fedora release 8 (Werewolf)

I’m hoping to take this over to FUDCon later today and help get it more solid for F9.

Pictures to come.

Cheers,

Herlo

Dig this!

Hi all,

While at work today, setting up test environments for Ubuntu Gutsy (7.10), I needed to check something with the ubuntu.com DNS entries. So I ran the following:

# dig -t ns ubuntu.com

And got something very interesting and entertaining. Can you see what it was? Yes, the mythic-beasts are definitely alive and well within Ubuntu! Now that you are having fun, try these commands immediately afterward:

# dig -t ns mythic-beasts.com

And

# whois mythic-beasts.com

Note the other nameservers. Quite an entertaining 5-10 minutes of your life.

Enjoy,

Herlo

Distro Comparison: openSUSE 10.3 - Day 3

Wow, I’m excited by the response, and while I still believe that openSUSE is not the distro for me, it definitely has grown on me. I believe on my last review, I might have been a bit hasty in stating that just about everything was useless. And while I do have a few more complaints about this distribution, getting settled in might have been all it takes to shake of the pure hatred I recently expressed.

Much of my response has been in fact aimed at my personal opinions of certain features, and while a few of the failures I noted were indeed things that bugged me, they were personal preference and thus, I will be revising my scoring system a little. In fact, how I will award points will not so much be based upon personal preference unless its completely unbearable to me. And to that end, I’ll make a new PREFERENCES section, which will not receive scores, but will have things I personally like or dislike.

In addition, I so appreciate all of the comments I’ve received, many were very helpful in pointing out errors in my representation of openSUSE. Others were part of the reason I decided to change the scoring a bit. And even others I’d like to take the time to reply:

First, to my friend Heartsbane, thanks for the smartass reply. I should’ve known it was coming!

Sontek pointed out that there were bugs in the iwlwifi driver when 10.3 was released. While I agree with not releasing something before its ready, I find it interesting that 2 months after its release openSUSE doesn’t have iwlwifi drivers available in their updates. Why is this? Did I miss them somewhere? My problems with the ipw3945 are more to the fact that it never seems to work with the WPA PSK setup I have at home/work. The iwlwifi driver has less issues with this specific problem.

apokryphos had several comments, and I will address a few of them.

  1. The 1-click-install feature is to help reduce much of the repo setup and installation that used to be a long drawn out process has been reduced to 1 click. While I agree that this is a major improvement, it is such a misnomer to call it a 1-click-install when it clearly isn’t. I only suggest we rename the process as someone coming from another world to Linux who find openSUSE may be disappointed when a 1-click-install indeed requires more like 7 clicks.
  2. zypper shows what will be installed was another response I received contrary to what I saw. He asked me for an example, and in return I would suggest that indeed it does tell you what will be installed, but only after you agree to install the extra dependencies. Please provide me a command/option that shows me the dependencies prior to my agreement to install the package(s).
  3. The root prompt was another failure on my end, however. Mostly, I have it ingrained in my head to look for the “root” part in the prompt. The entire prompt indeed turns red as suggested, this is something I just have to get used to, or change to my preference I guess. I do still think the prompt is ugly, but its growing on me. Others mentioned this as well, thanks for pointing out this to me.

Another, which I received from Ani and lejocelyn (as well as apokryphos), was in regard to my complaint about the Windows-like look and feel. First off, its not a cop-out and secondly, it does look like Windows. Where is the multiple-workspaces? Isn’t that a big plus, I had to add them and enable the panel object. What about this “control center”, feels a lot like Windows “control panel” to me. There is much more I think, and it also might be somewhat because I’m a GNOME user. But like I said, if I wanted it to look like Windows, I would just run Windows.

Ani also pointed out that some of my complaints about the lack of horizontal bars were because of the wasted space, especially with the new widescreen displays coming out. In retrospect, I agree that its useful to only have one bar on widescreen displays or because it takes up so much space. The “one glance” aspect I get from my status bars sure helps me, however, so I’ll define this as just a preference.

benji.weber@gmail.com pointed out his installation time was much shorter than mine. I’m not sure how he got this, but I installed from DVD offline so maybe its a bit related. He also mentioned that there are many more users testing KDE over GNOME. I suppose this might be the case for openSUSE, but overall, I think that number is pretty evenly split between the two major desktops.

Thank you all for your wonderful comments, I really appreciate the contrasting views and look forward to the next round of comments.

As I didn’t use openSUSE as much yesterday and today, so I have a little less to report:

GOOD

  • YaST is growing on me, but I’m still adjusting to living in this world. Its still not my favorite tool (0)
  • Suspend works like a charm. Although this also works in Fedora. (+1)

Positive Score: +1

BAD

  • The YaST printer tool does not deliver reliable results when setting up printers. YaST discovered my printer, but failed to deliver the correct IP address (-1)
  • My bluetooth mouse is still not working, even after following several good tutorials I found online. As per this tutorial from Andrew Jorgensen, I already have the bluez-gnome and bluez-utils from the GNOME Community repository installed. Not sure why, but it looks this one will have to wait for an update, whenever that occurs. (0)
  • Enabling the fingerprint reader only asks me for files. I thought that was odd, clicking on the help indicates that providing files from another installation that uses the fingerprint reader will set it up. I didn’t see a way to set this up from scratch with openSUSE in YaST, however. (-1)

Negative Score: -2

Total Score for the last two days: -1 (not bad for day two, you never know, I might actually give a positive score by the end…)

Overall score: -6

PREFERENCES

  • I still prefer the system-config-* tools from Fedora over YaST. I don’t like its interface and it still seems to be unfriendly. I do think that its much improved over the original YaST I used back in SUSE 10.0

A New Series: Distro Comparisons, with Flair!

Its been a little couple weeks since I posted anything useful in my Program of the Week (POW) series. And while I still plan to keep that up in the near future, I am going to be doing a new series, Distro Comparisons, with Flare!

My plan is to install the other two major distros of Linux (OpenSUSE and Ubuntu) and compare them with Fedora, my favorite distribution. I’ll be comparing them on installation, features, tools and any other thing that I regularly use in my day-to-day life. Once the distros are all installed (in a triple-boot, no less), I’ll be keeping each one for a week at a time over the next few months.

Over each week, I’ll write down things that are awesome, good, bearable, or just plain bug me, and each will get a score. To be fair, I’ll make sure to rank them with a maximum of +5 and a minimum of -5. Its possible that a negative score can happen, but I expect that this will not be the case for any of the distros.

Anyway, wish me luck on my triple-boot installs and my future blogging with these comparisons. I also hope this will enlighten others about the options available in each of the distros and encourage the developers to continue to improve the usability and functionality of their particular distribution.

Tonight, I’ll be installing and setting up OpenSUSE 10.3 and running it for the next week. During the holidays, I’ll be taking a bit of a break, so blogging might be a bit slower. In early January, I’ll install Ubuntu Gutsy (7.10) as well. See you all on the flip side.

Cheers,

Herlo

LugBin: Improving the Local User Group experience

The charter of the Utah Open Source Foundation is to help Open Source grow in Utah. As part of this charter, we focus on the local community and especially the User Groups.

Because of this goal, we’ve been working hard to come up with some simple, yet effective ideas to help the User Groups overall. Just recently, myself and Will Smith (undertakingyou) were discussing the LugBin. The idea is simply just a big plastic bin with good stuff that User Groups might need or want. In fact, we think it might be a good idea to get others involved so we’re asking for help.

If you would take a few minutes after you read this to visit our wiki page for the LugBin and give suggestions for what would be useful inside. Keep in mind that User Groups may be about operating systems, programming languages, business organizations, or anybody that just wants to get together and talk about any Free/Libre Open Source (F/LOSS) software.

Thank you for your input. We really appreciate every comment/suggestion.

Cheers,

Herlo

Thunderbird! You’re Annoying us all!

Let me get this out first, I’m a avid fan of all things Mozilla. Even with the limitations they cause, the problems I’ve heard about Firefox and Thunderbird and all that Jazz, I’m still a big fan, current and future consumer of these wonderful applications.

BUT!

Why is it that a bug that has been logged for some time can go so long without being fixed. It sure seems like a very simple fix, but no, its still broken.

What, you ask, am I talking about? Well, its this bug on mozilla’s bugzilla that’s bugging me. While its not a major bug, its annoying and causes me heartache every time I look into my /tmp directory.

The problem is that as Thunderbird creates and moves data around when using a filter rule. It creates temporary files which is all fine and good, but the problem is the code is broken that removes the temporary files. My /tmp directory just fills and fills with these useless little files. It’s driving me insane. Every time I go into the directory to look at something, I’m bombarded with files that are named tmprules-##.dat , where the ## is a number.

Have a look into the directory:

$ ls /tmp/tmprules*.dat | wc -l
492

Why do we need to have 492 files in there? I don’t even have 492 messages I read each day. Come on Mozilla Foundation, take a few minutes and fix this annoying little bug that’s been hanging around since this March!

Cheers,

Herlo

POW: Agave

An interesting tool I came across in the last week or so is this week’s Program of the Week: Agave, from the GNOME Community. Recently, we’ve been working on a new logo for the Utah Open Source Foundation, and needed to come up with some simple color schemes that would work well with our logo. In doing so, I came across Agave and started playing with possible combinations of colors we could use.

This tutorial will cover some of the simple, but effective features Agave provides to help provide a good contrast in designing logos, websites and more.

To install Agave, I simply did the following:

# yum -y install agave
.. snip ..
Installed: agave.i386 0:0.4.2-5.fc8
Dependency Installed: gconfmm26.i386 0:2.20.0-1.fc8
Complete!

Once Agave is installed, it is immediately available from the main Applications -> Graphics menu in GNOME. If you use a different desktop, its possible to type agave at the command line. Agave starts up similar to this screenshot:

agave-start.png

As is shown above, its simple to see that the three colors here would go nicely together, maybe a bit bright for a website, but not too bad for a logo maybe. In our logo, however, we didn’t want such bright colors, plus we wanted to base it on a color that already existed in our already established brand logo seen below:

utos_bc.gif

This logo is well known in our community, and thus we wanted to make sure to keep the look and feel as our org morphs into its true form. Out game GIMP and with the color picker tool, I obtained the bluish color needed for contrast. Agave only needs the value to give several different options through its several available views. The first view shown is the triads view, in other words, a scheme with three colors that fit well together:

agave4.png yields the triad agave3.png

But the real power of Agave is in this section of the application:

agave-power.png

The color picker provides for easy to choose colors on the left.

On the right hand side, is the color scheme chooser which allows 6 different choices; Complements, Split-Complements, Triads (3 colors), Tetrads (4 colors), Analagous and Monochromatic. In addition, on the toolbar near the top, is another feature that allows random color schemes to be chosen.

When we’ve finished our site and logo, I’ll update this article with the results.

Try out Agave today and maybe even paint your house using its recommendations!

Cheers,

Herlo

POW: apg, Automated Password Generator

This week’s program may seem like a bit of a cop out, but it really isn’t. I’ve regularly found myself in need of some quick passwords to hand out to users that are both semi-secure and easy to remember. With apg, this can become a reality.

First, install apg:

# yum install apg
.. snip ..
Install      1 Package(s)
.. snip ..
Total download size: 101 k
Is this ok [y/N]: y
.. snip ..
Installed: apg.i386 0:2.3.0b-5.fc8
Complete!

apg does provide several switches which help to provide an easy way to distribute passwords. Recently, I generated random, yet pronounceable passwords for about 30 users of an application I was using. it was quite nice to let the users login and feel safe with my choices of passwords.

To start with apg is quite easy to generate a set of passwords:

$ apg
NatnawmIx
GhisImAv*
Bahiwaihet
adMuhevep
Ombachat
cier]bipt

These passwords are the default set from apg, providing six pronounceable, 8-10 digit, In my opinion, its better to lose a bit of security to make a password easy to remember, than to have a user have to write the password down, more or less defeating the purpose of the password in the first place.

Because of my opinion, (and no, I’m not a security expert by any means, just using common sense), its probably a good idea to have a look at some of the switches provided by apg:

-a : 0 (default) will make the passwords semi-pronounceable, 1 on the other hand, will be pseudo-random

-n : tell apg how many passwords to display

-m/-x : the minimum/maximum length of the generated passwords

Here’s an example of these options in use:

$ apg -a 1 -n 2 -m 7 -x 10

apg has more to give us though. We can use some standard Linux password checking utilities to help us:

-r : checks the generated passwords against a particular dictionary file.  /usr/share/dict/words, for example.

Adding this to our previous example (and removing the -a option) will verify the password doesn’t have any dictionary words:

$ apg -r /usr/share/dict/words -n 2 -m 7 -x 10

The last component is -M mode, which can request/require that a password has a particular set of attributes. Its a bit more complex than the others above. The mode consists of eight letters, S, N, C and L, in both upper and lower case.

S :  must use special symbol set for every generated password.
s :  should use special symbol set for password generation.

N : must use numeral symbol set for every generated password.
n : should use numeral symbol set for password generation.

C : must use capital symbol set for every generated password.
c : should use capital symbol set for password generation.

L : must use small letters symbol set for every generated password (always present if pronounceable  password generation algorithm is used).
l  : should use small letters symbol set for password generation.

As you might be able to tell, the list above is almost directly from the man page for apg. This is on purpose as it is very well explained (and recommended to read each and every man page for any tool used). Many a good trick has come directly from the man pages.

Let’s see these options in use:

$ apg -n 2 -m 7 -x 10 -M SCnL
Hej=Nio
nefMit/

What is noted right away during several iterations of these modes is the fact that rarely, if ever, is a number included. It seems the lowercase modes are not strong suggestions except in the case of “lower case letters”. However, using the uppercase mode values works every time as expected.

apg is a simple, yet effective tool for generating passwords. My hope is that you decide to use more secure passwords in the future with tools like apg.

Cheers,

Herlo

Locate vs Find

Tonight at the Ubuntu Utah User Group I presented about Locate vs Find.

The slides are here and written in S5.

Kevin Kubasik also presented on Desktop Search in Gnome. It was pretty cool as well.

The presentations went very well and was streamed and recorded by Utah Open Source Foundation.

POW: Bluetooth Improvements in Fedora 8

The POW is going to be the improvements made in the Bluetooth functionality in Fedora 8. I’m actually quite impressed with it as its been a bit of a challenge to keep my little mouse connected in the past.

Fedora 8 provides a new extended technology with its bluez-gnome package. In fact, the simplicity of it is that I only have to be able to click and approve a new device.

When I first turn on my bluetooth mouse and start to move it around, it doesn’t work, but up in the top right hand corner of my GNOME desktop is the bluetooth manager. It has a message for me:

bluetooth-authorize.png

The message indicates a click to authorize the device, namely the bluetooth mouse. (One note here, I was originally unable to use my touchpad, so I had to resort to other tactics [not pretty] to enable my mouse. Probably ought to have some other options available instead of clicking.)

Clicking on the notification window above brings me to an authorization window.

bluetooth3.png

At this point, authorization is quite simple. Click yes for a one time authorization of the mouse (Note the Bluetooth Travel Mouse indicated in the description), and to authorize it more permanently, choose Always Grant Access.

That’s it. My Bluetooth mouse is now enabled and working. I’d say this is much friendlier than what I used to have to do, including running hidd –connect <bluetooth id> after pressing the little connect button on the bottom of the mouse. This is sure nice now!

Its possible, that at some point, disconnecting the device might be necessary. To do this, right-click on the nice little Bluetooth logo at the top right of your screen.

bluetooth5.png

Choose Preferences. Up pops the Bluetooth Preferences window. From this window, three tabs are available. In the first (and also selected) tab, there is a section at the bottom of the window which lists the devices that are currently bonded and/or trusted. Choose the device from the list and then the appropriate action. The choices are Disconnect, Trust or Delete.

bluetooth4.png

In addition to just configuring your devices, it appears it might be possible to do things like Bluetooth DUN with a Treo, or enable data synchronization between laptops. One thing I’ve always wanted to try is to get my bluetooth headset working so I could do Skype or Asterisk phone calls through my headset, to my computer and out through the service.

Cheers,

Herlo

« Previous PageNext Page »