Language Selection

English French German Italian Portuguese Spanish

Fedora 18 Spherical Cow review - Bad bad bad

Filed under
Linux

As you recall, a revolution happened last spring. Fedora 17, when blessed with the Cinnamon desktop, was superb. In fact, it earned a nice little place in the top charts for 2012. Encouraged by the very positive trend shown in the last release, I decided to see how well Fedora 18 would behave.

Live session - Buggy

The testing started on a left foot, after it was lost in a train accident. The thing is, Fedora would not auto-login. Spherical Cow only got to that login screen and waited. I tried using fedora, live, user, and several other generic account names, without success. Only root worked. Reading online, there's a bug noted, from September 2012, that this might happen in the live session. What you should do is select a certain user and proceed. The thing is, the bugzilla entry plus the explanation are written for Gnome, hence this does not work on KDE, hence this is bollocks, and I was tempted to quit at this stage. But I decided to try using the distro with the root account login.

On my first attempt, there were three warning and error messages coming up during the session.

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