Language Selection

English French German Italian Portuguese Spanish

Linux distro spotlight: Fuduntu

Filed under
Linux

It's not unusual for Linux distributions to have somewhat offbeat names — Ubuntu (named after an Africa-originated philosophy), Red Hat (the creator of the original distro, Marc Ewing, had a red lacrosse hat given to him by his grandfather), and the wonderful CrunchBang Linux (named after the characters usually used at the start of a script — #!). In the case of Fuduntu, the origins of the name are quite simple: It's a combination of Unbuntu and Fedora, the Red Hat-sponsored Linux distribution.

Fuduntu started in 2010, with the first release of the distribution in November that year. It's a desktop distribution that was originally a repackaged edition of Fedora, but completely forked from the Red Hat distribution about a year ago.

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