Showing posts with label beginner. Show all posts
Showing posts with label beginner. Show all posts

How-To: Install Finch 2.6.5 in Debian Lenny

    Finch is a powerful text user interface instant messaging client based on libpurple, and it comes included in the Pidgin source, the popular GNOME IM client. Finch supports various protocols, including AIM, ICQ, MSN, Yahoo and IRC.

    The version which ships in Debian Lenny is rather old (2.4.3), so in order to install the latest release of Finch in Debian Lenny (which, at the time of writing is 2.6.5), just follow the next steps:

    Make sure the sources repositories are enabled, so that the needed development libraries are available. That is, a line like the following should be available in the /etc/apt/sources.list file:

    deb-src http://ftp.fi.debian.org/debian/ lenny main contrib non-free

    As root, update the packages list:

    apt-get update

    And install the development libraries:

    apt-get build-dep finch

    Next, download the Pidgin source code (which also includes Finch source) from the official website (direct link here), uncompress it:

    tar -xjf pidgin-2.6.5.tar.bz2

    Change the current working directory to pidgin-2.6.5 and compile and install it using:

    ./configure --disable-gtkui --disable-vv --disable-nm

    The --disable-gtkui switch will not build the GTK interface, and the other two will disable voice/video support and NetworkManager support.

    Now issue the usual:

    make
    make install

    The last one as root. Alternately, you can install Finch as a local user, by specifying an install prefix:

    ./configure --prefix=/home/USER/usr --disable-gtkui --disable-vv --disable-nm
    make
    make install

    In this case, make install should be run as normal user. Replace USER with your username and make sure /home/USER/usr/bin is included in your $PATH variable. Run Finch by typing finch at the command-line.

    Pidgin 2.6.5 running in a terminal
    Source URL: http://ashesgarrett.blogspot.com/search/label/beginner
    Visit ashes garrett for Daily Updated Hairstyles Collection

How-To: Change GRUB Splash Image (For GRUB Legacy)

    Although GRUB 2 replaced the older GRUB 0.9x (currently known as 'GRUB Legacy'), the latter still is the default boot loader on some distributions, like Debian 5.0 for example.

    The splash screen for GRUB Legacy is an XPM image which appears as a background when you select which OS to boot. For those who are tired of the default splash screen, here is a short tutorial on how to change it.

    First, download some splash screens from here (or Google some). Each splash screen comes as an XPM image archived as a Gzip file. Once you downloaded the desired splash images, copy them inside the /boot/ directory, or create symbolic links in this directory which will point to the actual location of the files. For example, if you downloaded the file tenerife.xpm.gz inside your home directory, you can type as root (and replace USER with the actual username):

    cp /home/USER/tenerife.xpm.gz /boot/

    Or, to create a symbolic link to it:

    ln -s /home/USER/tenerife.xpm.gz /boot/grub/tenerife.xpm.gz

    In Ubuntu (pre-Karmic releases, since Karmic uses GRUB 2 by default), use one of those, with the user password:

    sudo cp ~/tenerife.xpm.gz /boot/grub/

    Or:

    sudo ln -s ~/tenerife.xpm.gz /boot/grub/tenerife.xpm.gz

    The next step is to edit the /boot/grub/menu.lst file, and tell it to use the newly downloaded splash image. For this, add a line which looks like this inside the file mentioned earlier (don't forget to edit it with root privileges):

    splashimage (hd0,0)/boot/tenerife.xpm.gz

    This will tell GRUB to search for the file tenerife.xpm.gz on the first partition of the first hard drive. Save the file and restart the computer.
    Source URL: http://ashesgarrett.blogspot.com/search/label/beginner
    Visit ashes garrett for Daily Updated Hairstyles Collection

How-To: Install KDE 4.3 in Ubuntu/Kubuntu 9.04 Jaunty Jackalope

    KDE 4.3 was released just yesterday, and it comes with a lot of great new features and improvements, like the the new Plasma theme called Air, new Plasma widgets, several improvements to Dolphin, the default KDE4 file manager, improvements to the KDE games, and these are just a tiny part of all the improvements KDE4 introduced. The full announcement including reader's changelog can be found on the official KDE4 website, here.

    Kubuntu comes with an older release of KDE4, but there is a PPA (Personal Package Archives) available which includes the newest packages for Jaunty, so in order to install it just follow the steps below.

    First, open up a terminal like Konsole or GNOME Terminal and edit the sources.list file using your favourite text editor, e.g.:

    sudo nano /etc/apt/sources.list

    Or, for Kate:

    sudo kdesu /etc/apt/sources.list

    If you are installing KDE from Ubuntu, you can use Gedit:

    sudo gedit /etc/apt/sources.list

    Enter your user password and add the following repository line:

    deb http://ppa.launchpad.net/kubuntu-ppa/backports/ubuntu jaunty main

    Next, make sure to save the file (Ctrl+O followed by Ctrl+X in Nano) and update the package lists:

    sudo apt-get update

    All you have to do now is to install the new KDE 4.3 environment by issuing:

    sudo apt-get dist-upgrade

    Should take a while. This will fetch and install all the newer packages from the freshly added repository. To see the new KDE 4.3 installation log out and log back in KDE, or open up Konsole and type:

    sudo /etc/init.d/kdm restart
    Source URL: http://ashesgarrett.blogspot.com/search/label/beginner
    Visit ashes garrett for Daily Updated Hairstyles Collection

How-To: Install Miro 2.5.1 in Ubuntu 9.04 Jaunty Jackalope

    Miro is a great application for watching videos and high-definition TV podcasts in Linux. The latest release is 2.5.1, a bug fix release for the 2.5 series, which has a faster start-up time, a new, revamped library interface, new keyboard shortcuts, a refined interface and lots of bug fixes. Miro is an awesome multimedia application, especially if you like watching videos at high quality.

    Miro 2.5.1 in Ubuntu 9.04

    By default, Ubuntu Jaunty comes with Miro 2.0, but the Miro project offers their own repositories for Ubuntu with the latest Miro packages, so you can easily fetch and install the latest release using the instructions below.

    1. Edit the sources.list file
    Edit the /etc/apt/sources.list file using your favourite text editor (e.g. sudo nano /etc/apt/sources.list or gksudo gedit /etc/apt/sources.list) and add the following line:

    deb http://ftp.osuosl.org/pub/pculture.org/miro/linux/repositories/ubuntu jaunty/

    2. Update the package lists
    Type in a shell like GNOME Terminal:

    sudo apt-get update

    3. Remove your existing Miro
    If you have an older version of Miro installed on your Ubuntu system, first remove it:

    sudo apt-get remove --purge miro
    sudo apt-get autoremove --purge

    4. Install Miro 2.5.1
    Type:

    sudo apt-get install miro

    This should do it. Miro 2.5.1 should be now properly installed and you can run it by typing Alt+F2 and writing miro in the run box that appears.

    Alternately, here are instruction to install it the graphical way (applies for Ubuntu with GNOME):

    Open System -> Administration -> Synaptic Package Manager. You will be asked for your user password upon opening Synaptic.

    Next, in Synaptic go to the Settings -> Repositories menu, then click on the Third-Party Software tab in the window that pops up. Click the Add button and copy/paste the line below (it's the same line you would have added in the /etc/apt/sources.list file by hand):

    deb http://ftp.osuosl.org/pub/pculture.org/miro/linux/repositories/ubuntu jaunty/


    Click the Add Source button, close the window and then click the Reload button in the main Synaptic window.

    Next, just search for Miro in the packages list in Synaptic, mark it for installation including its dependencies and you're ready to go.

    Source URL: http://ashesgarrett.blogspot.com/search/label/beginner
    Visit ashes garrett for Daily Updated Hairstyles Collection

5 Simple APT Tips for Debian and Ubuntu, Part II

    Several months ago I created an article with 5 APT (Advanced Packaging Tool) tips for both Debian and Ubuntu available here. APT is the package manager in Debian and Debian-based distributions, like Ubuntu. Here's part two of that article, with 5 more tips and tricks for APT.

    Notice: I specified which commands need root privileges. In Debian, type su, followed by your root password, while in Ubuntu just precede each command which needs root privileges with sudo. Notice that by default there is no feedback when entering the password, so you won't be able to see it, but it goes in. Just press Enter when you're done.

    Add repositories from a CD or DVD
    If you need an offline repository for packages, you can download all the ISO images for your distribution, eventually burn them on CDs/DVDs and add them manually to the /etc/apt/sources.list file using apt-cdrom (as root):

    apt-cdrom add

    Enter the CD/DVD in the drive and let APT scan for packages.

    Another great solution is to not even burn the ISO images to CD, just mount them and add them to your sources.list this way. Here's what you have to do:

    First, type:

    apt-cdrom -d=/cdrom add

    Or replace /cdrom with some empty directory of your choice, that's where the ISO images will be mounted. I use here /mnt/iso0, /mnt/iso1 etc. Just make sure the directory is empty. The output of the above command looks something like this:

    # apt-cdrom -d=/cdrom add
    Using CD-ROM mount point /cdrom/

    Unmounting CD-ROM

    Waiting for disc...

    Please insert a Disc in the drive and press enter


    Now don't press Enter, instead open another terminal session and mount the image in that directory (as root):

    mount -o loop /path/to/iso/file.iso /cdrom

    Then return to the shell where you started apt-cdrom and press Enter. It should scan the directory where the ISO image was mounted. I'm not very sure this is the only method, but this worked very well for me. If you mount the ISO the first time and then execute apt-cdrom, it first umounts it and then it fails with the message E: Failed to mount the cdrom.

    Use dpkg -S to search for a specific file
    dpkg -S filename will search for filename in all the packages available and return all the packages which have a file (or the path to that file) with the same name. Notice that the name can also be included in the found files. For example, typing dpkg -S bash will return all the packages which contain the name 'bash' in their files, including mybashburn, bash and several other packages. On the other hand, searching for dpkg -S /bin/bash will only return package bash, since dpkg will match the whole path to the bash binary. See the screenshots below for examples:


    Use apt-file to search for files in packages
    This is a tool which creates a cache with info about all the packages available in the repositories, and it allows to search for specific files in a package and show what files a package will install (including packages which are not already installed). To get it, type as root:

    sudo apt-get install apt-file

    Next, update its cache:

    sudo apt-file update

    Use it like this:

    apt-file search filename

    Or:

    apt-file search file_path

    This will also return paths which include the name file_path. To show what files a package will install, use:

    apt-file show package_name

    Here's a more comprehensive tutorial I wrote a while ago about apt-file.

    Remove unnecessary packages
    This was a feature which existed for while in aptitude, but not in apt. Once you remove an application, it may be possible that some libraries on which that application depended to remain installed in the system. In order to get rid of those too, use:

    apt-get autoremove --purge

    Notice that this command will only remove packages which are not needed any more by some other application or that are not marked as 'installed manually'. This means packages which you did not specifically installed yourself.

    List files in a package
    Just use dpkg -L package_name for this one. Example:

    dpkg -L amarok
    dpkg -L bash
    ...

    This will list all the packages installed by the respective package. Notice that it won't list anything if the specified package is not installed.

    Hope this will be useful. Have some more, or maybe something wrong in the article? Please share other APT-related tips and tricks in the comments below.
    Source URL: http://ashesgarrett.blogspot.com/search/label/beginner
    Visit ashes garrett for Daily Updated Hairstyles Collection

How-To: Install VLC 1.0 from the Ubuntu PPA Repository


    Since most of the users found the compilation method to have either too many steps or too complicated, here's a tutorial on how to install VLC 1.0.0 using the Ubuntu VLC PPA repository. Just follow the steps below:

    First, download and install the trusted key:

    sudo apt-key adv --recv-keys --keyserver keyserver.ubuntu.com 7613768D

    This commands tells apt-key to download key 7613768D from keyserver.ubuntu.com and add it to your trusted repository keys.

    Next, we need to edit the /etc/apt/sources.list file with root privileges (sudo nano /etc/apt/sources.list or gksudo gedit /etc/apt/sources.list) and add the following two repository lines:

    deb http://ppa.launchpad.net/c-korn/vlc/ubuntu jaunty main
    deb-src http://ppa.launchpad.net/c-korn/vlc/ubuntu jaunty main

    Make sure to save the file when you're done. Alternately, this can be done as:

    sudo bash -c "echo 'deb http://ppa.launchpad.net/c-korn/vlc/ubuntu jaunty main' >> /etc/apt/sources.list"

    sudo bash -c "echo 'deb-src http://ppa.launchpad.net/c-korn/vlc/ubuntu jaunty main' >> /etc/apt/sources.list"

    These two commands will append the two lines mentioned earlier to /etc/apt/sources.list.

    Next, update the package lists:

    sudo apt-get update

    Then, just install VLC the usual way:

    sudo apt-get install vlc

    Or you can use Synaptic (System -> Administration -> Synaptic Package Manager), search for package vlc and install it from there.
    Source URL: http://ashesgarrett.blogspot.com/search/label/beginner
    Visit ashes garrett for Daily Updated Hairstyles Collection

How-To: Compile and Install VLC 1.0 in Ubuntu 9.04 Jaunty Jackalope


    Ubuntu 9.04 (and Kubuntu) comes with VLC 0.9.9 included in the repositories. However, VLC 1.0.0 was released today and it ships with several new features and many improvements. For readers who don't know what VLC means, it is a powerful, cross-platform and open-source video player, built using Qt 4 toolkit. It supports many video formats and comes with advanced video features and functions.

    To install the latest release of VLC (currently 1.0.0) in either Ubuntu/Kubuntu/Xubuntu distributions, just follow the steps below:

    1. Install the needed dependencies
    First, use build-dep to get all the dependencies VLC needs. This will also install compilation tools, including the build-essential meta package:

    sudo apt-get build-dep vlc

    You will need your user password. Notice that on a fresh system this will install a lot of development packages. After the installation is completed proceed to the next step.

    Notice: If the buil-dep command fails with a message which goes like E: Build-dependencies for vlc could not be satisfied. then try to install all the packages manually. The following are two separate commands:

    sudo apt-get install build-essential libmad0-dev libavutil49 libavcodec-dev libavformat-dev libavutil-dev libswscale-dev libpostproc-dev liba52-0.7.4-dev

    sudo apt-get install debhelper dh-buildinfo gettext quilt nasm yasm libass-dev libxul-dev liba52-0.7.4-dev libaa1-dev libasound2-dev libcaca-dev libcdio-dev libdca-dev libdvbpsi4-dev libaudiofile-dev libavahi-client-dev libavcodec-dev libdvdnav-dev libdvdread-dev libesd0-dev libfaad-dev libflac-dev libfreetype6-dev libfribidi-dev libggi2-dev libgl1-mesa-dev libglib2.0-0 libgnutls-dev libhal-dev libid3tag0-dev libidl0 libimlib2-dev libjack-dev liblircclient-dev liblivemedia-dev liblua5.1-0-dev libmad0-dev libmatroska-dev libmodplug-dev libmpcdec-dev libmpeg2-4-dev libncursesw5-dev libnotify-dev libogg-dev libpng12-dev libpostproc-dev libpulse-dev libqt4-dev libschroedinger-dev libsdl-image1.2-dev libsdl1.2-dev libv4l-dev libvcdinfo-dev libvorbis-dev libx11-dev libx264-dev libxext-dev libxml2-dev libxpm-dev libxt-dev libxv-dev pkg-config qt4-dev-tools zlib1g-dev

    This may take a while.

    2. Download the source tarball
    Get the source code from the official website (direct link), then make sure the currently working directory is the one where you saved it and uncompress it:

    tar -xjf vlc-1.0.0.tar.bz2

    3. Compile and install VLC
    To compile and install, just issue the usual commands inside the vlc-1.0.0 directory:

    ./configure
    make
    sudo make install

    Finally, don't forget to run sudo ldconfig with your user password.

    You can choose an alternate location for the installation, so you can install as normal user. E.g.:

    ./configure --prefix=/home/user/usr/
    make
    make install

    VLC 1.0.0 running in Kubuntu 9.04

    Source URL: http://ashesgarrett.blogspot.com/search/label/beginner
    Visit ashes garrett for Daily Updated Hairstyles Collection

5 Bash Tips, Part II

    This article is a continuation to my other Bash-related post, 6 Bash Productivity Tips. Since that article gathered many useful comments and I bumped into several more over the net, here are 5 more tips and tricks. Although these may not be necessarily productivity-related, they will surely ease working in a Bash terminal and it may be worth knowing them. If you're not familiar with the terminal, command-line interface and Bash you can go ahead and read my introduction to Linux CLI.

    Using Ctrl+R (reversed search)
    Ctrl+R performs a reversed search in the history. For example, typing the command df -h | grep /dev/sda1, then pressing Ctrl+R and typing only df, the most recent command will be auto-completed and performed upon pressing Enter. Ctrl+R searches for occurences of what you type and returns the last command in which it finds it:

    $ df -h | grep /dev/sda1
    /dev/sda1 83G 65G 14G 83% /
    (reverse-i-search)`df': df -h | grep /dev/sda1

    Using !COMMAND
    Where COMMAND is any command executed in the past or the beginning of a command. This calls the most recent command starting with COMMAND. For example:

    $ for i in *.ogg; do vorbiscomment -l $i; done
    ...
    $ ls
    ...
    $ !for
    for i in *.ogg; do vorbiscomment -l $i; done

    In the above example, using !for followed by Enter executed the last occurence in the history which started with for.

    Exit status: echo "$?"
    This will return the exit status of the last executed command. It can prove useful in scripts. A command returns 0 if it ended successfully and a non-zero value otherwise:

    $ cat /etc/motd | head -1
    Linux debian 2.6.26-2-686 #1 SMP Sun Jun 21 04:57:38 UTC 2009 i686
    $ echo "$?"
    0
    $ cat /etc/mots
    cat: /etc/mots: No such file or directory
    $ echo "$?"
    1

    Using !! with sudo
    Here's a useful example of !! from one of the comments in the older post. !! will replace the last command, so using sudo !! will execute the last command preceding it with sudo. Very useful when performing commands which need root privileges and forgetting to precede them with sudo. Example:

    $ apt-get update
    E: Could not open lock file /var/lib/apt/lists/lock - open (13 Permission denied)
    E: Unable to lock the list directory
    $ sudo !!
    sudo apt-get update

    Run a specified command in history with !NUMBER
    This will run command numbered NUMBER from history. Examples: !250, !1, etc. To view the history and the corresponding numbers, type history:

    $ history | tail -3
    534 for i in *.ogg; do vorbiscomment -l $i; done
    535 history
    536 history | tail -3
    $ !534
    for i in *.ogg; do vorbiscomment -l $i; done
    Error opening input file '*.ogg'.

    In the above example, command number 534 was executed when typing !534.

    For other suggestions or corrections to these tips, please use the comments below.
    Source URL: http://ashesgarrett.blogspot.com/search/label/beginner
    Visit ashes garrett for Daily Updated Hairstyles Collection

How-To: Compile and Install SMPlayer from Source in Debian Lenny

    SMPlayer uses the mplayer engine for displaying videos and it's one of the most powerful and popular video players out there. Built using the Qt 4 toolkit, SMPlayer offers great features and it's highly customisable.

    The latest version is 0.6.7, which brings experimental support for DVD menus and several other improvements and bug fixes over the previous release, 0.6.6. Here are several steps to follow in order to build SMPlayer from source in Debian Lenny:

    1. Enable the sources repositories
    Edit the /etc/apt/sources.list file as root with your favourite text editor (e.g. nano /etc/apt/sources.list or kdesu /etc/apt/sources.list) and make sure you have a line which starts with deb-src, as in the example below:

    deb-src ftp://ftp.ro.debian.org/debian/ lenny main contrib non-free

    You can replace the TLD with the one of your country (e.g. instead of ro use fi for Finland, de for Germany etc.) Next, update the packages list as root:

    apt-get update

    2. Install the needed dependencies
    As root, type:

    apt-get build-dep smplayer
    apt-get install devscripts

    This will install the tools needed to build SMPlayer and also the development libraries on which it depends.

    3. Download the source tarball and uncompress it
    Get the latest source for SMPlayer (which is 0.6.7 at the time of writing) from the official website (the file is called smplayer-0.6.7.tar.bz2). To uncompress it, make sure the current working directory is the one where you saved the source and type:

    tar -xjf smplayer-0.6.7.tar.bz2

    4. Compile and install SMPlayer
    Change the working directory to smplayer-0.6.7 and issue the commands:

    make QMAKE=/usr/share/qt4/bin/qmake

    And to install it type as root:

    make install

    This should be all. SMPlayer should be inside /usr/local/bin/smplayer.

    Source URL: http://ashesgarrett.blogspot.com/search/label/beginner
    Visit ashes garrett for Daily Updated Hairstyles Collection

How-To: Configure Bash to Show Some Info and Greet the User When Invoked

    In this tutorial I'll show how to add some message (or run whatever application, echo whatever text you wish) when you start Bash in a terminal application like GNOME Terminal or Konsole.

    When Bash is started in interactive way it will execute the commands found in ~/.bashrc, where ~ is you home directory. This file usually contains the PS1 variable (which holds the way the prompt looks like (by default this is user@host in most distribution), aliases, instructions to execute the /etc/bash_completion and ~/.bash_aliases files if found etc.

    In order to show some message when Bash starts we will add the commands we want executed at the end of this file, so edit it with your favourite text editor, e.g. nano ~/.bashrc and add something like this:

    fortune

    This command will echo some random quote from a database which has over 15.000 quotes. Notice that you will have to install the fortunes package, in example on a Debian system type as root:

    apt-get install fortunes

    You can add any command you want executed to ~/.bashrc, for example I have those:

    echo -ne "Hello, $USER! Today is $(date).\n\n"
    cal
    echo -ne "System Info: $(uptime)\n\n"
    echo -ne "Fortune of the Day:\n"
    /usr/games/fortune

    Here's a screenshot of the output for those commands:


    As you can see, first it echoes a message to the currently logged in user, it shows the date, invokes the cal application which will display a calendar, it shows the system uptime and then echoes a quote using the fortune game.
    Source URL: http://ashesgarrett.blogspot.com/search/label/beginner
    Visit ashes garrett for Daily Updated Hairstyles Collection

How-To: Compile and Install digiKam 0.10 in Debian Sid

    digiKam is a popular photo management application for both KDE3 and KDE4. Starting with version 0.10, digiKam offers a KDE4 port too. Here are instructions on how to compile from source and install the latest release in Debian Sid.

    1. Install the needed dependencies
    First of all, install the tools needed for the compilation. Type as root:

    apt-get install build-essential cmake

    Get the KDE4 development libraries too:

    apt-get install kdelibs5-dev

    Now, install the development libraries needed to compile digiKam (that's only one line):

    apt-get install libgphoto2-2-dev libkipi6-dev libexiv2-dev libkdcraw7-dev liblcms1-dev libtiff4-dev libpng12-dev libjpeg62-dev libjasper-dev

    These should do it.

    2. Download the source code
    Next, download the tarball from the official website and uncompress it:

    tar -xjf digikam-0.10.0.tar.bz2

    3. Compile and install digiKam
    Change the current working directory to digikam-0.10.0, then compile and install it using these commands:

    cmake .
    make
    make install

    The last one as root. This worked for me (I hope I didn't miss any dependencies, if so, please let me know.) DigiKam 0.10 should be now installed.
    Source URL: http://ashesgarrett.blogspot.com/search/label/beginner
    Visit ashes garrett for Daily Updated Hairstyles Collection

5 Popular Tricks to Customise Nano Editor


    Nano is a popular and user-friendly text editor for console which is mostly used for editing quickly configuration files, sources or various other text files. It does not compete with advanced development environments like Vim or Emacs, but it's fast and easy on resources.

    Here are five (popular, I hope) tips for customising Nano and changing its default behaviour.

    1. Enable auto-indentation
    When Nano starts, it reads a system wide configuration file which is usually located inside /etc/nanorc and executes the commands located inside it, then it searches for the user configuration file, located in ~/.nanorc, where ~ is the user's home directory. To configure Nano for your user, you only need to edit the ~/.nanorc file. Notice that since this is a hidden file, you may have to turn on hidden file view in your file manager, or use ls -a in a terminal.

    Edit the ~/.nanorc configuration file (create it if it doesn't exist; ~ is your home directory) and add the following line:

    set autoindent

    This will turn on auto-indentation for a new line to the same level of the previous line. Alternately, you can run Nano with the -i switch:

    nano -i

    Or just type Alt+I inside Nano when it's running.

    2. Enable syntax highlighting
    Edit the ~/.nanorc configuration file and add lines which go like this:

    include "/usr/share/nano/c.nanorc"
    include "/usr/share/nano/perl.nanorc"

    Default Perl syntax highlighting in Nano

    Several other default highlighting rules are found inside the /usr/share/nano/ directory. I wrote a full tutorial about enabling syntax highlighting in Nano here.

    3. Turn off the creation of backup files
    By default, Nano creates backup files with names like filename~ after editing a file. To turn this behaviour off, edit the ~/.nanorc file and add the line:

    unset backup

    To turn backup files on again, use set backup in the configuration file.

    4. Don't add newlines at end of files
    By default, Nano will add a newline character at the end of a saved text file. If you want this disabled, add the following option inside ~/.nanorc:

    set nonewlines

    5. Change tab size
    Nano uses by default 8 columns for the tab size. In order to change it to another value, say 4, use:

    set tabsize 4

    Or some other value depending on your needs.

    These are several settings I think are among the most popular. For a complete manual, use man nano, man nanorc and the official online manual.Source URL: http://ashesgarrett.blogspot.com/search/label/beginner
    Visit ashes garrett for Daily Updated Hairstyles Collection

How-To: Enable Syntax Highlighting in Nano

    Nano is a popular, user-friendly text editor which can be ran in a shell, without the need of an X Server. It can be very useful especially for editing text files (like configuration files or scripts) in a fast manner, being faster than more advanced, graphical text editors.

    Nano has syntax highlighting support for programming languages, which is disabled by default. However, Nano provides default rules for several languages like Perl, Python, or C, to name a few. These highlighting definitions are kept inside the /usr/share/nano/ directory, and for each language there is available a file with rules.

    For example, ls /usr/share/nano will output the following on my system, which has Nano 2.0.7 installed:

    $ ls /usr/share/nano/
    asm.nanorc groff.nanorc java.nanorc mutt.nanorc nanorc.nanorc perl.nanorc python.nanorc sh.nanorc
    c.nanorc html.nanorc man.nanorc nano-menu.xpm patch.nanorc pov.nanorc ruby.nanorc tex.nanorc

    These are default syntax highlighting rules for several languages, like Java, Perl, Python, Bash, C, HTML or Ruby.

    In order to enable syntax highlighting in Nano based on one of these files, edit the ~/.nanorc file, where ~ is your home directory. Notice that you will have to create this file if it doesn't already exist. Then add lines to it in this fashion:

    include "/usr/share/nano/c.nanorc"
    include "/usr/share/nano/perl.nanorc"
    include "/usr/share/nano/sh.nanorc"
    include "/usr/share/nano/html.nanorc"

    And so on for each language you want to have syntax highlighting enabled. Those four lines will include the files c.nanorc, perl.nanorc, sh.nanorc and html.nanorc, which will define highlighting rules for C, Perl, Bash and HTML respectively. This can also be accomplished by copying the contents of one of those files directly into ~/.nanorc. For example:

    cat /usr/share/nano/c.nanorc >> ~/.nanorc

    The above command will append the contents of /usr/share/nano/c.nanorc at the end of ~/.nanorc, enabling syntax highlighting for C. You can also search on Google for other rules, if the default colours don't fit well.

    Syntax highlighting for C in Nano

    Notice: This tutorial is a later, revised version of the tutorial which I initially published here.Source URL: http://ashesgarrett.blogspot.com/search/label/beginner
    Visit ashes garrett for Daily Updated Hairstyles Collection

Tutorial: An Introduction to Linux CLI

    The shell
    A shell is a command interpreter which allows the user to interact with the computer. The way things work is simple: the user types in commands, the shell interprets them and performs the tasks it was asked to do, and finally it sends the result to the standard output (which is usually the screen). For example, the output of the ls command can be something like:

    $ ls
    bin dev home lost+found opt sbin sys var
    boot etc initrd.img media proc selinux tmp vmlinuz
    cdrom floyd lib mnt root srv usr

    This is a list of files inside the root directory. The root directory is the first location in the filesystem hierarchy, and it is represented by a slash sign: /.

    Some of the most popular shells are:
    bash Bourne-Again Shell, the default shell on most Linux systems
    sh Bourne Shell, an older shell which is not so widely used anymore and it has been replaced by Bash
    csh C Shell, with a syntax that resembles the C programming language syntax
    tcsh an improved version of the C Shell
    ksh Korn Shell
    dash Debian Almquist Shell

    To access a shell-like application you can use, for example, GNOME Terminal (the GNOME terminal application) or Konsole (the KDE terminal application). To open either of those, press Alt+F2, and type either gnome-terminal or konsole in the Run dialogue that appears. You can also press Alt+Ctrl+F1 to get a shell login prompt, and you can return to the graphical interface with Alt+Ctrl+F7. Some other terminal applications include Yakuake, xterm or rxvt, but I recommend to stay with the default one which comes with your distribution for now. Here is a full article about those.

    Konsole, default KDE terminal application

    Bash, the default shell in most Linux distributions, including Debian and Ubuntu, is a modern implementation of the older Bourne Shell (sh). Bash was developed by the GNU Project, which is also responsible for most of the important command-line tools widely used on a Linux system. In fact, a more appropriate name for Linux is GNU/Linux, since any Linux-based distribution includes the Linux kernel (the core of the operating system) and the GNU tools and utilities. On a Debian system, the default shell used by the system is specified in the /etc/passwd file.

    Basic commands
    Commands in Linux are executable files which can be ran to perform tasks, like listing the files in a directory or creating and renaming files for example. Examples of frequently used commands are ls, pwd, date, cat, less, top and so on. The general form of Linux commands is:

    command option(s) filename(s)

    A command may or may not have arguments. An argument (also called a parameter) can be an option or a filename. Here is a list of basic, most used commands, with the exact description specified in the manual pages:

    ls list directory contents
    pwd print name of current/working directory
    date print or set the system date and time
    mkdir make directories
    rm remove files or directories
    mv move (rename) files
    who show who is logged on
    whoami print effective userid
    cat concatenate files and print on the standard output
    more file perusal filter for crt viewing
    less opposite of more

    Standard GNU tools usually have two ways of specifying an option, the short and the long syntax, so ls -a and ls --all will do the same thing, list files including the ones that start with a dot (.).

    Options specified between the [ and ] brackets are optionally, for example the synopsis ls [OPTION]... [FILE]... tells that neither OPTION or FILE needs to be necessarily specified.

    The cat command can be used to read text files, and it is especially useful for small ones. cat will display on the screen the last page of the text file(s) passed as arguments, without the ability to scroll it in order to see the rest of the file. For larger files which are longer than one page, use the less and more commands, or a text editor like nano. For example, to read the /etc/motd (message of the day) file, one can use:

    $ less /etc/motd

    Omit the dollar sign ($), which is the prompt in this case. A file with some text message in it should be now displayed on the screen. To navigate in a text file using less, use the following keyboard shortcuts:

    ^N to go forward one line (same effect as J)
    ^P to go backward one line (same effect as K)
    ^V to go forward one page (same effect as SPACE)
    Alt+V to go backward one page

    To quit and return to the prompt, type Q. In the examples above, the ^ character stands for the CONTROL character (labeled Ctrl), so ^N means 'press Ctrl+N'. The above shortcuts are widely used on a Linux-based OS by applications like Emacs (an advanced text editor and IDE - integrated development environment), the man command and many others. The arrow keys can also be used, by the above method is the preferred one due to the fact that it is faster, and the user doesn't have to move the fingers to the arrows then back to the typing position.

    The man command
    man is used to see detailed help about a command. You can use the keyboard shortcuts mentioned above to navigate through a manual page.

    Type Q to quit the manual page and return to the shell prompt. The Q character is usually used to quit most Linux command-line applications, like more, less, man and many others. If you type H while reading a manual page, a help about the command less will be provided (man uses the less tool in order to format the manual pages). Those are the commands that apply in the manual page.

    The cd and pwd commands
    The commands cd, which is used to change the current directory, and pwd, used to print the current working directory, are both shell built-ins. This means that they are included in the Bash program rather than a standalone command (file), like ls or date. Some examples of shell built-ins are cd, echo, read, exit, logout, alias, fg or bg.

    You can see what cd does by changing the current working directory to a new one and see the new path using the pwd command:

    $ pwd
    /home/embryo
    $ cd /usr/share
    $ pwd
    /usr/share

    You can now type ls to see the available files in /usr/share. As a note, cd without any arguments changes the current directory to the home directory of the current user, located by default in /home/username:

    $ pwd
    /usr/share
    $ cd
    $ pwd
    /home/embryo

    Control characters
    A shell uses certain key combinations to perform certain tasks. These key combinations are called control characters. Here are examples of control characters:

    ^A - go to the start of line
    ^E - go to the end of line
    ^H - erase one character to the left (same effect as Backspace)
    ^D - erase one character to the right; it also ends the session if there is nothing to delete
    ^U - erase entire line
    ^K - erase everything to the right until the end of line
    ^P - bring the previous command in history
    ^N - bring the next command in history
    ^C - interrupt character: this usually terminates programs

    Those are very important because they make working with the shell faster and easier. Although a little tough to learn for a beginner, they prove fast once they are learned.

    Regarding ^N and ^P: for example if you type ls, then date and pwd, and after that ^P, the pwd command will be brought back and you only have to type Enter to issue it again. If you type ^P again, the date command is brought and so on.

    Regarding ^D, also called the EOF (end-of-file) character: this key combination can also be used to tell a program that the input has ended and it can return its output. For example, you can type wc -l, which is the command to count the lines in a text file, without providing the text file. Now you can start filling in lines and typing Enter after each line. When you're done, just type Ctrl+D and the wc tool will return the total number of lines you entered:

    $ wc -l
    There is a house in New Orleans
    They call the rising sun
    And it's been the ruin of many a poor boy
    And god I know I'm one
    4

    As you can see, there were 4 lines typed in.

    The ls command
    The ls command is used to list directory contents. With no arguments, it returns a list of files and directories in the current directory. It also offers many arguments, so you can list more information about the existing files. For example:

    ls -l use a long listing format
    ls -X sort alphabetically by extension
    ls -h display sizes in human readable format (transforms in KB, MB or GB when necessary); use this with the -l switch to see the effect
    ls -a list all files; this includes files starting with a dot character

    You can nest arguments to obtain the desired result:

    $ ls -lhX
    total 96K
    drwxr-xr-x 2 root root 4.0K 2009-03-12 16:58 bin
    drwxr-xr-x 3 root root 4.0K 2009-03-20 23:08 boot
    lrwxrwxrwx 1 root root 11 2009-02-18 18:22 cdrom -> media/cdrom
    drwxr-xr-x 13 root root 4.2K 2009-04-07 06:25 dev
    drwxr-xr-x 120 root root 12K 2009-04-07 02:18 etc
    ...

    Notice that this way ls will return the current directory contents, however you can use it to list files located in some other directory:

    $ ls -lh /bin
    total 4.3M
    -rwxr-xr-x 1 root root 685K 2008-05-12 22:02 bash
    -rwxr-xr-x 1 root root 121K 2007-07-14 00:52 bsd-csh
    -rwxr-xr-x 3 root root 26K 2008-08-05 14:19 bunzip2
    -rwxr-xr-x 1 root root 368K 2008-09-08 02:29 busybox
    -rwxr-xr-x 3 root root 26K 2008-08-05 14:19 bzcat
    ...

    The . and .. files
    When using ls -a, you will notice two special files, . (one dot) and .. (two dots). These are virtual files. The single dot stands for the current working directory, while the double dot represents the parent directory of the current directory. For example if your current directory is /home/chris/ and you want to change it to its parent /home, you can either use cd /home (which is the absolute path) or cd .. (which is the relative path). Or if you want to copy, say, the file /etc/motd in the current directory, you can use:

    $ cp /etc/motd .

    Instead of:

    $ cp /etc/motd /home/chris

    The rm, mkdir and touch commands
    To remove a file, use the rm command:

    $ rm file

    To remove a directory, use:

    $ rm -r directory

    The mkdir command is used to create directories:

    $ mkdir mydir

    touch is a tool used to change file timestamps. That means it updates the date a file was last accessed and/or modified. Example:

    $ ls -lh ubuntupocketguide-v1-1.pdf
    -rw-r--r-- 1 embryo embryo 2.2M 2009-01-20 21:51 ubuntupocketguide-v1-1.pdf

    The file was last modified on January 20, 2009, at 21:51. To update its modification time, type:

    $ touch ubuntupocketguide-v1-1.pdf
    $ ls -lh ubuntupocketguide-v1-1.pdf
    -rw-r--r-- 1 embryo embryo 2.2M 2009-04-07 16:41 ubuntupocketguide-v1-1.pdf

    Now, the date the file was last modified was changed to April 7, 2009, at 16:41. If the file specified as argument for touch does not exist, an empty file is created:

    $ ls myfile.txt
    ls: cannot access myfile.txt: No such file or directory
    $ touch myfile.txt
    $ file myfile.txt
    myfile.txt: empty

    We used the file command to see what what kind of file myfile.txt is.

    Getting help
    One of the most powerful ways to get help is to read the manual pages, usually available for any GNU utility and application via the man command. These tools also have two standard arguments, --version (or -v) and --help (or -h). They return the version of the program and a brief help on how to use the respective command. You can also use info command.

    On a usual Linux system, the manual pages are located in the directory /usr/share/man, in directory names like man1, man2, man3 and so on.

    $ bash --version
    GNU bash, version 3.2.39(1)-release (i486-pc-linux-gnu)
    Copyright (C) 2007 Free Software Foundation, Inc.

    Shell built-ins
    Shell built-ins are commands included in the Bash program. To see the available built-ins in your Bash application, you can type help in any shell. Some examples of built-ins include:

    . (or source) - read and execute commands from a filename
    alias - define aliases (read here how to create aliases)
    bg - place each job specified as argument in the background
    fg - place the job specified as argument in the foreground and make it the current task
    read - read one line from the standard input
    if - execute commands if the condition specified is true
    while - execute commands as long as a condition is true
    help - display helpful information about built-in commands

    You can use the help command to see a complete list of shell built-ins, and help to see detailed help about each command. In order to see if a command is a standalone program or a shell built-in, you can use the type command:

    $ type cd
    cd is a shell builtin
    $ type bash
    bash is hashed (/bin/bash)

    If the specified command is an alias, the output will be something like:

    $ type ls
    ls is aliased to `ls --color=auto'

    Linux directory structure
    Usually, the standard Linux directory structure is as follows:

    /bin contains essential programs for booting and maintaining the system; examples: bash, chmod, chown, cp, grep, kill, ps, rm, tar
    /boot contains the Linux kernel image used to boot the system, and also the /boot/grub/menu.lst file, for configuring the GRUB boot menu
    /dev special files pointing to system devices
    /etc configuration files for various applications
    /home contains directories for all the users a system has; examplse: /home/embryo, /home/pink
    /lib contains shared libraries available for all programs throughout the system
    /media mount points for devices like hard disks or optical drives
    /mnt used for mount points like external filesystems
    /opt additional applications go here
    /proc virtual files which provide information about the system; try cat /proc/cpuinfo for example
    /root home for the super user (root)
    /tmp temporary files are stored here
    /sbin programs for system administration, generally used by root
    /usr contains almost all the programs which are not located in /bin or /sbin, documentation, manual pages, icons etc
    /var files like logs, emails

    Using tar, gzip and bzip2
    tar is a tool which creates archives known as tarfiles, while gzip is a compressing tool which uses an advanced compression algorithm. bzip2 is an advanced compression tool which takes more time to compress/uncompress files but offers a better compression rate, which results in smaller files. bzip2 is used especially to save disk space and bandwidth.

    To uncompress a .tar.gz file you would issue a command like:

    tar -xzf archive.tar.gz

    x stands for extract
    z specifies that the compressed file is a gzip file
    f stands for the filename

    To uncompress a .tar.bz2 file you can use:

    tar -xjf archive.tar.bz2

    To create a .tar.gz file from a directory, you can use:

    tar -czf my_archive.tar.gz directory_name

    This will create the compressed file my_archive.tar.gz from the contents of directory_name, which will be the root directory.

    More Linux commands

    who
    The command who is used to show who is logged on, the number of the tty (teletype terminal) or display they are using, and the date and time they logged in:

    $ who
    embryo tty1 2009-04-07 17:08
    embryo :0 2009-04-06 23:30

    uptime
    uptime will show how long the system has been running:

    $ uptime
    17:09:03 up 17:39, 2 users, load average: 0.14, 0.17, 0.11

    uname
    This command is used to print system information:

    $ uname -a
    Linux debian 2.6.26-1-686 #1 SMP Fri Mar 13 18:08:45 UTC 2009 i686 GNU/Linux

    echo
    This built-in will display a line of text to the screen:

    $ echo 'Hello, world!'
    Hello, world!

    $ echo $PATH
    /home/embryo/bin:/usr/local/bin:/usr/bin:/bin:/usr/games

    Search for commands
    In order to see the path in which a command is located, you can use the whereis command, which will search in all the standard locations:

    $ whereis bash
    bash: /bin/bash /etc/bash.bashrc /usr/share/man/man1/bash.1.gz

    Notice that whereis will not look into non-standard paths (e.g. /home/user/bin), instead, you can use the which command for that:

    $ which q3ut4.bash
    /home/embryo/bin/q3ut4.bash

    When you type in a command like uptime or uname, Bash searches for it in the directories in your $PATH variable (see echo $PATH), and it executes the first one it finds in that order. Aliases have priority.

    Additional resources
    There is a huge number of tutorials for Linux CLI, but I'd like to recommend two particular ones, specially created for beginners:

    TuxFiles.org - Tutorials for Linux newbies
    LinuxCommand.org - An introduction to Linux command-line and basic scripting for beginners

    Do you have any suggestions or corrections for this tutorial? Please feel free to discuss in the comments section below.

    This is a later, revised version of the tutorial which I initially published here.

    Updated: April 9, 2009
    Source URL: http://ashesgarrett.blogspot.com/search/label/beginner
    Visit ashes garrett for Daily Updated Hairstyles Collection

How-To: Compile and Install XMMS in Ubuntu 9.04 Jaunty Jackalope

    XMMS (X Multimedia System) was a very popular audio player for many years, but it was dumped from Debian Lenny and Ubuntu since it uses older GTK+ libraries and it is not maintained any more. It was replaced with the newer Audacious player on both distributions, which you can install by typing sudo apt-get install audacious in a terminal.


    However, if you want to compile it from source in Ubuntu 9.04 and 8.10, you can follow the steps below:

    1. Install the tools needed for compilation and XMMS dependencies
    Open up a terminal and type:

    sudo apt-get install build-essential

    build-essential is a meta package which depends on tools needed for compilation, like gcc (GNU Compiler Collection). Next, install the development libraries:

    sudo apt-get install libgtk1.2-dev libglib1.2-dev

    It's recommended to also install libvorbis-dev, for the Ogg Vorbis plugin:

    sudo apt-get install libvorbis-dev

    2. Download the XMMS source
    Get the source from the official website, here, and save it to a location of your choice. Next, make sure the current working directory is the one where you saved the source, then uncompress it using one of the following commands (depending on which file you downloaded, the .tar.gz or the .tar.bz2):

    tar -xzf xmms-1.2.11.tar.gz

    Or:

    tar -xjf xmms-1.2.11.tar.bz2

    3. Compile and install XMMS
    Change the working directory to xmms-1.2.11 and issue the following commands to configure, compile and install it:

    ./configure
    make
    sudo make install

    Next, run ldconfig as root:

    sudo ldconfig

    This should be all. Run XMMS by typing ALT+F2 and entering xmms in the Run dialogue that appears. Notice that XMMS will not be able to play sound if there is another audio or video player running.

    To uninstall it, issue the command sudo make uninstall in the same directory from which you installed it.

    An alternate way of installing XMMS in Intrepid Ibex, without compiling it, is to follow this short guide. Basically, you will have to add the following two lines to your /etc/apt/sources.list file:

    deb http://www.pvv.ntnu.no/~knuta/xmms/intrepid ./
    deb-src http://www.pvv.ntnu.no/~knuta/xmms/intrepid ./

    Update the package lists and install XMMS using:

    sudo apt-get update
    sudo apt-get install xmms
    Source URL: http://ashesgarrett.blogspot.com/search/label/beginner
    Visit ashes garrett for Daily Updated Hairstyles Collection

How-To: Debian Lenny Minimal Installation

    Debian Lenny comes with KDE 3.5.10 and GNOME 2.22, and will install by default the entire GNOME desktop environment and the X Window System. This means many applications which you may never use will also be installed, so here is a solution in order to get only a basic system and then install only the packages you need.

    This tutorial will briefly show what you have to do in order to have a basic and minimum Debian installation on your PC.

    First, when the installer reaches the window where it asks what software you want to install (like Desktop Environment, Web Server, Basic System etc.), just de-select the Desktop Environment option using the SPACE key, and also make sure the Basic System option remains selected.

    After the installation is over, Debian will ask to reboot the computer, then it will boot to a shell login. Login as root, then type the following commands in order to only get the core packages for the X Window System and your desktop environment of choice:

    If you want GNOME, type:

    apt-get update
    apt-get install xserver-xorg-core gdm gnome-core

    If you want KDE, type:

    apt-get update
    apt-get install xserver-xorg-core kdm kde-core

    Either of those commands will only install a minimum needed for running Debian graphically, so you will be able after that to install only the applications which you actually need.

    gdm and kdm stand for GNOME Display Manager and, respectively, K Display Manager and they are, as the name suggests, the login applications for GNOME and KDE. gnome-core and kde-core will only fetch and install the basic libraries and applications needed to run GNOME and, respectively, KDE. This means that in KDE, for example, only applications like KControl, Kate or Konqueror (but not applications like noatun or kdegames) will be installed. You then get to choose which image viewer, music and video players will install.

    Next, to start the X Server, use one of the commands as root:

    If you installed GNOME and GDM:

    /etc/init.d/gdm start

    If you installed KDE and KDM:

    /etc/init.d/kdm start

    If the X server fails to start, try, as root:

    dpkg-reconfigure xserver-xorg

    And specify the driver vesa in section Device inside the /etc/X11/xorg.conf file. You may need to install the specific video driver for your video card.

    Notice that you can also install any other (read: lighter) desktop environments, like Xfce or even Enlightenment for example.

    Notice: This is a later, revised version of the tutorial I initially posted here.Source URL: http://ashesgarrett.blogspot.com/search/label/beginner
    Visit ashes garrett for Daily Updated Hairstyles Collection

4 Ways to Create CD/DVD ISO Images in Ubuntu

    In this guide I will show how to create CD/DVD ISO images in Ubuntu using four easy methods.

    1. Create ISO Images With K3b
    K3b is the KDE default CD/DVD burner and also one of the most popular (if not the most popular) burning application for Linux. The current version comes installed by default in Kubuntu 8.10 and 9.04, but if you are using Ubuntu and want to get install it issue the following command:

    sudo apt-get install k3b

    A port for KDE4 is in the works too, but until now there is no stable release. (Update: This applies for K3b 2.0+ too)

    To create an ISO image just fire up K3b and follow the steps below:

    Go to File -> New Project -> New Data CD Project (or New Data DVD Project, depending on what size the image you want to create will have):


    Next, drag and drop the files and folders from the file browser to the bottom area:


    Now, click the Burn button and, in the window that appears, tick the Only create image option under the Settings widget. The image will be created by default as the /tmp/kde-YOUR_USERNAME/image_name.iso, but you can change this location in the Image tab.



    Next, click on Start and wait for the image to be created. This should be all.


    Here's what the file /var/kde-embryo/my_iso_image.iso shows:

    embryo@kubu:~$ file /tmp/kde-embryo/my_iso_image.iso
    /tmp/kde-embryo/my_iso_image.iso: ISO 9660 CD-ROM filesystem data 'my_iso_image '

    2. Create ISO images with Brasero
    Brasero is the default CD/DVD burning application in Ubuntu. The way Brasero creates images is similar with K3b's. If you don't have Brasero installed for some reason, type:

    sudo apt-get install brasero

    Start Brasero (or fire it up, as you wish to call it) and click on the Data project button (or go to Project -> New Project -> New Data Project).


    Change the name of the disc at the bottom to whatever you like and then click on the green plus sign in the upper left corner in the toolbar to start adding files and directories to your image:


    After you finished adding files click on Burn and make sure no empty CD/DVD is in your optical drives:


    This should be all. The image will be located in the home directory.

    3. Create ISO images using AcetoneISO
    AcetoneISO is a GUI (graphical user interface) application built in Qt4 for mounting and unmounting CD/DVD ISO (NRG, MDF and BIN too) images, but it can also be used to create ISO images.

    To install AcetoneISO in Ubuntu you can follow the guide I put up a while ago, here. I will use version 2.0.2 for this example. In newer Ubuntu versions, just type in a terminal:

    sudo apt-get install acetoneiso

    First, put all the files and folders you want included in the image into a new, empty directory. Next, in the menu go to Conversion -> Generate ISO from folder, select the desired folder and enter the name of the image:


    That's it.

    4. Create ISO images using command-line
    What, you thought I was going to leave CLI behind? Here's (probably) the easiest way to create ISO images using command-line interface.

    First, install the tool called genisoimage (if you already have Brasero or K3b installed, this package is probably already installed):

    sudo apt-get install genisoimage

    Use it like this:

    genisoimage -o my_image.iso my_directory

    Or:

    genisoimage -o my_image.iso file01 file02 file03

    The first command will create an ISO image from the contents of folder my_directory (and it will include it as the root directory), while the second one will create an image containing file01, file02, file03 (and no root directory).

    For Rock Ridge extensions (which provide permissions and ownership support), use:

    genisoimage -o my_image.iso -R my_directory

    So, these are the four methods I find most accessible for creating CD/DVD images in Ubuntu. Please share other ways of accomplishing this in the comments below.

    Updated: September 19, 2010Source URL: http://ashesgarrett.blogspot.com/search/label/beginner
    Visit ashes garrett for Daily Updated Hairstyles Collection

Blog Archive