Language Selection

English French German Italian Portuguese Spanish

Crunchbang #! 10 Statler

Filed under
Linux

My new buddy Crunchbang (abbreviated #!) and I have been spending quite some time lately. In fact, we spent enough time that he convinced me to install him as my main OS on my laptop. Unfortunately, that didn’t go too well (grub wouldn’t install, screwed up other distros on the laptop), but it ran nice and smooth in my virtual machine. This minimalistic distro consumes 57 MB (!) of RAM when it was up and running – yes, you read it right. A fully functioning operating system is running with fifty-seven megabytes of random access memory in use.

#! comes with either OpenBox or Xfce as default Window Manager/Desktop Environment. Both are pretty light weight, with OpenBox being lighter. Now OpenBox users will forgive me for saying this, but I do have to introduce the majority of people who have never used OpenBox – it is a lightweight window manager that is highly configurable. A cool feature is that everything is accessible from the main menu, which you can get by right clicking the desktop (and from there you can access EVERYTHING), or using the pre-defined/custom keyboard shortcut.

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