Language Selection

English French German Italian Portuguese Spanish

Fedora Day Two: Customisation

Filed under
Linux

So now I’ve got my Fedora 18 machine all up and running from Day One, and I’m now ready to get some work done, and oh what a busy day it’s been. As I mentioned yesterday, the default look of Fedora leaves a lot to be desired, so I’ve been busy working away to get my OS looking and running how I like it.

Installing software

I used a number of sources to get my software loaded up on Fedora. I did of course use the package manager that’s bundled in, simply called “Software” which does an ok job. But I found the search feature to be poor, the whole thing a little dated and generally rubbish to be honest. I personally prefer to install applications by CLI (Command Line Interface) anyway, so this wasn’t a deal breaker for me.

rest here




More in Tux Machines

Android Leftovers

Leftovers: OSS

Ubuntu 16.04 Review: What’s New for Desktop Users

Ubuntu is a tricky distribution. As much as I love it on my home server, my desktop is a different ballgame. In my experience, releases between LTS versions have many new technologies that may or may not survive in the next LTS. There were many technologies or features that Canonical thought were ambitious -- HUD, experimenting with menus, online dash search, Ubuntu Software Center, etc. -- but they were abandoned. So, if I were to use Ubuntu on my desktop, I would still choose LTS. Read more

Workflow and efficiency geek talks Drush and Drupal

I started using Drupal because I needed an open source content management system (CMS) to use in several community projects. One of the projects I was involved with was just getting started and had narrowed its CMS selection down to either Drupal or Joomla. At the time I was using a different framework, but I had considered Drupal in the past and knew that I liked it a lot better than Joomla. I convinced them to go with the new Drupal 6 release and converted all of my other projects for consistency. I started working with Drush because I wanted a unified mechanism to work with local and remote sites. My first major contribution to Drush was site aliases and sql-sync in Drush 3. Read more