Skip to main content

Life with Linux

I have been using Ubuntu Linux at home for the last month (courtesy of those folks over at Wubi). Overall I think it is great. So much faster than MS Vista and it helps inject life back into old machines.

However I have spent a fair amount of time configuring and re-configuring things (partly my own fault, and also partly because of the learning curve involved with any new OS). I even had to do one re-install (more on that later). Mostly though it worked out of the box.

So here are a few good ground rules for newbies...

1) Make sure you have more than one Internet enabled computer in the house before you do anything. If for some reason you have a hardware conflict (as I did with the wireless card on my wife's laptop) you will need to look up how to fix it.

2) Most of what you need is available through Synaptic Package Manager or Applications > Add/Remove. If you need a program or driver search there first before the Internet. The only notable exceptions I can think of are Skype and Adobe Flash. Basically Ubuntu has a number of great free programs available which you don't need to install externally.

3) Don't mess around with settings and config files unless you really know what they do. It was this that led me to my re-install, partly because of the next category...

4) When going online for info on configuring your computer, don't automatically use the first solution you read (especially if it asks you to update your settings and config files). Manually updating settings and config files with your text editor should be a LAST resort. More often than not the GUI tools are safer. You wouldn't normally update your Window's registry by hand would you? There are sometimes exceptions, but if an article tells you to go to your terminal and do anything with sudo, vi, pico, rm or gedit think twice. The only exception is sudo apt-get install (which is pretty safe because you are just using the command line version of Synaptic Package Manager). Also be wary of shell scripts (.sh files).

Apart from that I found Ubuntu much faster and easier to install than any Window's distribution (way faster). Provided you have the disk or the files on hand I would say it takes twice as long to install as Vista takes to boot up on an old machine.

Comments

Unknown said…
It is not that the GUI tools are any "safer", but it's probably more likely for the new linux user to understand what they are changing.

Overall good suggestions for the new to linux crowd. It's practically exactly what I tell my friends when I try to get them on the linux bandwagon.
Anonymous said…
>1) Make sure you have more than one >Internet enabled computer in the house >before you do anything.

I find that to be good advice no matter what the OS.

Popular posts from this blog

Freezing Gems

What is a gem and why would you want to freeze it?

In Ruby, there are times when you want to access pieces of functionality that other people of written (3rd party libraries) and you normally have 2 options. You can install a plug in or install a gem. Normally the method you use is determined by which ever is made available by the author.

Gems are installed on the host machine and are pretty handy when you want to run things in the command line or else across lots of projects, but their downside is that if you use a gem in a Rails project there is no automatic publishing mechanism when you deploy your site. You will need to log onto the remote host machine and install the gem manually.

Plugins are specific to Rails and are similar to gems in that they are also 3rd party libraries. However they are associated with your Rails project as opposed to your machine so they will get posted to the server on a regular deploy.

Freezing a gem is the process of transforming a gem into a plug in. Essen…

Comparing Rails' Active Record Pattern with Phoenix/Elixir/Ecto

Rails has a very well established Active Record pattern for dealing with the database. You have an Active Record model which maps to the database table, the schema of the model comes directly from the database schema and you place your model specific methods on the Active Record model. This file is also where you set your model relationships (e.g. has_many, has_one, belongs_to). Your instance of the model has all the methods built in.

In Ecto/Phoenix it's a little different. First of all, the database schema doesn't automatically map to the "model". In fact we don't really have models (as Elixir is a functional paradigm). What happens in one file in Rails, happens in essentially two (or more). You have a schema file (where you have to list out all the attributes and relationships). Using the schema file, your "instance" is essentially a data structure (with no methods on it). If you want to transform the data on your struct, you would use a context modu…

Unit/Functional Testing RubyAMF

One of my current projects is using RubyAMF to communicate with Flash (http://rubyforge.org/projects/rubyamf/). On the whole this is really nice because it allows you to transfer Ruby objects directly to ActionScript ones (as opposed to translating the object into XML, sending the XML and then recreating the object in ActionScript).
However, Rails does not provide a built in transport mechanism for AMF, so we cannot run functional testing directly on the data call (as we could for an XML or HTML transport layer). This is a show stopper for a lot of people (Rails w/o Unit testing = a big mess of trouble when something goes wrong).
We can though serve both the HTML and the AMF formats depending on the request format. This means that we can test the object instantiation logic and make sure there are no errors in the controllers (though we cannot check the actual format of the data being served). In the controller, instead of rendering AMF alone, do the following respond_to do |format|