Thursday, November 11, 2010

Wolvix-The Linux for home users

 Wolvix is a desktop oriented GNU/Linux distribution based on Slackware. It features the Xfce desktop environment and a comprehensive selection of development, graphics, multimedia, network and office applications. It's mainly targeted at home users and strives to provide a balance between everyday computing tasks, creativity, work and enjoyment.
Using Wolvix does not require more than basic computer skills, but installing and administering the system might require more knowledge than some of the other GNU/Linux distributions. Much like Slackware, Wolvix sometimes requires you to roll up your sleves and get your hands dirty. So if the thought of using the command line and reading documentation scares you, you might be better off using another distribution.
By default Wolvix only includes GTK+ applications, this is not because the developers hate Qt programs, it's mainly an aesthetic choice. The Qt widget looks out-of-place under Xfce, which use GTK+ and there are pleny of great GTK+ applications to choose from.
Wolvix does not strictly follow the 'one-application-per-task' mantra that some other distributions do. In Wolvix you will sometimes find that there are two, or perhaps even three applications that basically does the same thing. One reason for this is that some application fill each other out in functionality. Another reason is choice; we all have different preferences, my preferred text editor is not necessarily the one you prefer. There is of course a balance to this, the goal is not to create a bloated distribution, but some times one application is simply not enough.
Though Wolvix is fast and has a low memory footprint, it's not specifically developed for old computers, as it features modern software; which has modern hardware requirements. But it should perform well on systems which are not the latest and greatest. You should get acceptable performance from Wolvix and most of it's applications on a computer with a 700Mhz CPU and 256MB RAM.

An index of BASH command for Linux

adduser  Add a user to the system
  addgroup Add a group to the system
  alias    Create an alias •
  apropos  Search Help manual pages (man -k)
  apt-get  Search for and install software packages (Debian/Ubuntu)
  aptitude Search for and install software packages (Debian/Ubuntu)
  aspell   Spell Checker
  awk      Find and Replace text, database sort/validate/index
b
  basename Strip directory and suffix from filenames
  bash     GNU Bourne-Again SHell 
  bc       Arbitrary precision calculator language 
  bg       Send to background
  break    Exit from a loop •
  builtin  Run a shell builtin
  bzip2    Compress or decompress named file(s)
c
  cal      Display a calendar
  case     Conditionally perform a command
  cat      Display the contents of a file
  cd       Change Directory
  cfdisk   Partition table manipulator for Linux
  chgrp    Change group ownership
  chmod    Change access permissions
  chown    Change file owner and group
  chroot   Run a command with a different root directory
  chkconfig System services (runlevel)
  cksum    Print CRC checksum and byte counts
  clear    Clear terminal screen
  cmp      Compare two files
  comm     Compare two sorted files line by line
  command  Run a command - ignoring shell functions •
  continue Resume the next iteration of a loop •
  cp       Copy one or more files to another location
  cron     Daemon to execute scheduled commands
  crontab  Schedule a command to run at a later time
  csplit   Split a file into context-determined pieces
  cut      Divide a file into several parts 

Wednesday, November 4, 2009

Building a LAMP Server

This document will walk you through the installation of what is known as a "LAMP" system: Linux, Apache, MySQL and PHP. Depending on who you talk to, the P also stands for Perl or Python, but in general, it is assumed to be PHP. I run CentOS on my servers; these directions were written for CentOS/Red Hat/Fedora. I have had requests for SuSE (another RPM-based distribution) as well as Debian-based systems, so I will work on variants of these directions for those distributions in the future (donations might help speed that process up!). The main difference between the distributions is in the paths to the startup scripts.