Blog Archives

Install Linux From Pen-drive With Universal USB Installer


One of the joys for me  in using Linux  is the amount of variety I  have. There are so many distro’s some of which are designed for a very specific use.I like to try many Linux distro’s . One problem in trying out different distro’s the amount of CD’s required to burn the iso images of course I can use a re-writable CD but the process of burning CD image takes some time and after sometime CD’s become un-usable. Recently I found a software that makes pendrive bootable  with distro of my choice.

Universal USB Installer is a Live Linux USB Creator that allows you to choose from a selection of Linux Distributions to put on your USB Flash Drive. The Universal USB Installer is easy to use. Simply choose a Live Linux Distribution, the ISO file, your Flash Drive and, Click Install. Other features include; Persistence (if available), and the ability to fat32 format the flash drive (recommended) to ensure a clean install. Upon completion, you should have a ready to run bootable USB Flash Drive with your select Linux version installed.

Why We Use Linux (The Real Reason)


We tell people we use Linux because it’s secure. Or because it’s free, because it’s customizable, because it’s free (the other meaning), because it has excellent community support. But all of that is just marketing crap. We tell that to non-Linuxers because they wouldn’t understand the real reason. And when we say those false reasons enough, we might even start to believe them ourselves.

But deep underneath, the real reason remains.

Tux, as originally drawn by Larry Ewing

Image via Wikipedia

We use Linux because it’s fun!

It’s fun to tinker with your system. It’s fun to change all the settings, break the system, then have to go to recovery mode to repair it. It’s fun to have over a hundred distros to choose from. It’s fun to use the command line.Let me say that again.

 It’s fun to use the command line.

No wonder non-Linuxers wouldn’t understand.

The point with us Linux fans is – we use Linux for its own sake. Sure, we like to get work done. Sure, we like to be secure from viruses. Sure, we like to save money. But those are only the side-effects. What we really like is playing with the system, poking around, and discovering completely pointless yet fascinating facts about the OS.

And that’s the reason we use Linux because

Linux is Fun

Happy Birth Day Linux


I’m doing a (free) operating system (just a hobby, won’t be big and professional like gnu) for 386(486) AT clones.  This has been brewing since april, and is starting to get ready.

Linus Torvalds, 25 August 1991 on comp.os.minix (original message)

20 YearsOf Linux

The first version of Linux Kernel Was released on September 17 1991 and uploaded to an FTP server by Linus Torvalds in Helsinki.  That early iteration consisted of a mere 10,239 lines of code.

Fast-forward to the present day, where the Linux kernel 2.6.35 contains more than 13.5 million lines of code, and controls gadgets, devices and instruments you might never have expected.

 

 

 

 

 

Autoten An Easy Way To Install Software In Fedora


The official symbol of the Linux distribution ...

Image via Wikipedia

One of the main reasons I use Linux is availability of Software Repositories. Having all the software you need in one place saves you having to trawl the web to find the program you’re missing. It also means the software has been independently checked and digitally signed by the distro’s developers, making it almost impossible to pick up a root-kitted version.

But Unfortunately Fedora‘s package manager Package-kit was not that much user friendly or efficient as the package managers available in Ubuntu or Linux Mint. I found it very difficult to find the software required especially proprietary ones like the multimedia codecs etc. Then I found a nice little tool called autoten.

Autoten is a nifty application which makes installing proprietary codecs & other proprietary stuff a piece of cake on your Fedora system. It does the same things which Easy Life does in a way which is similar to Easy Life. Autoten should ideally be run after your first install so that your system is ready for multimedia playback including mp3, mp4, mkv etc. Autoten is available for 32bit & 64 bit Fedora and Omega Linux.

Once installed it will provide you with whole bunch of options to choose from. In Fedora 14 you will get a screen shot like this.

Autoten for Fedora 32bit and 64bit

As you can see there are lot of software to choose from. By using the same tool one can uninstall the softwares installed using autoten.

To install auto ten just type follow these steps:

  1. Type su in the terminal and press enter.  It will ask for the root password. Provide the root password.
  2. rpm -Uvh http://dnmouse.org/autoten-5.2-2.fc14.noarch.rpm.

Enter the above command and the rest will be taken care by the Operating system itself. After installing Autoten icon can be found on the desktop or alternatively you can find it in System Tools —–> Autoten.

 

Grep Command in Linux Demystified


The grep command is a hugely powerful way to search through files. Like many command line utilities, once you’re comfortable using it, you will discover that it is surprisingly fast and accurate.

However, many Linux users only bother to learn one or two grep options and then use them as a kind of one-size-fits-all approach to searching. A little time spent learning what grep can do will pay dividends – and there’s nothing more satisfying than knowing exactly how to use a command to find something in a jiffy.

We’ll start out with the basics and build up a repertoire of ways to use grep, before finishing with some things to check out if you’re still hungry for more.

The examples that follow use the OpenBSD calendar files. These are already installed by default on Ubuntu, Mint, and even the Mac, along with many other distros.

However if you are a Fedora user, and you want to follow along, you can add them manually by selecting the

System > Administration > Add/Remove Software option from your desktop. Search for calendar, check the box next to Reminder Utility and click Apply. Or, just run yum install calendar on the command line. Now for the important stuff.

Basic searches

The grep command looks for the following things:

1. Any options you might use to tailor your search.
2. The string (or pattern) you are looking for.
3. A location in which to search – either a file or a directory.

As a quick example, try:

grep first /usr/share/calendar/calendar.history

Let’s examine exactly what’s happening here. We’ve asked grep to find all instances of the string ‘first’ in the file calendar.history.

Bear in mind that grep is case sensitive – compare the different set of results you get if you run:

grep First /usr/share/calendar/calendar.history

If you want your search to return everything, regardless of capitalisation, use the -i option to ignore case.

grep -i first /usr/share/calendar/calendar.history

All good so far.

Now, what if you want to search in more than one file? There are many calendar files we might want to look in, so change the file path to a directory and then use the -r option so that grep searches recursively through all the files and subdirectories it finds under the specified directory:

grep -ir first /usr/share/calendar

Each line of output is now prefixed with the name of the file. Note that the order in which you add options after the ‘‘ character does not matter.

Sometimes the examples above are exactly what you need; if you’re looking for a letter you wrote to someone called Don Jenkins, and you know that it’s somewhere in your home directory, you can probably find your file with:

grep -r Jenkins /home/faye

However, what if you run your grep command, but you don’t get the results you expect, or you get so many matches that you can’t tell one line from another?

Customise your output

Let’s make it a bit easier to see what we’re doing by turning on grep’s highlighting option. This time we’ll search for ‘war’.

grep -ri –color=auto war /usr/share/calendar/

That’s better, now you can see the actual string you are searching for (if you are running Linux Mint, highlighting is turned on by default).

grep highlighting

BRIGHTEN YOUR SEARCH:

Highlighting your grep output brightens your terminal and allows you to see the wood for the trees

Next, let’s make sure we aren’t picking up any substrings, since grep will list all matches even if they are part of another word. For example, our search for war is also picking up a line about Rod Stewart.

You can prevent this by requesting whole word matches only, with the -w option. This reduces the number of matches by two thirds. We know this because you can use grep to tally up instances, rather than report them directly, by adding the -c option:

grep -riwc war /usr/share/calendar

You can see that grep outputs the number of matches for each file it searches. If you were searching a single file, it would simply return a single number.

One last thing before we move on: if you want to search for more than one word, you need to use single quotes to retain the whitespace:

grep -ri ‘civil war’ /usr/share/calendar

That’s all well and good, but when I search for something like "$20", it all goes horribly wrong. What’s happening? OK, there’s something else about grep that you need to know, and that’s the fact that it’s designed to match patterns with regular expressions.

grep regular expression

SEARCH EXPRESSIONS: The $ sign is being interpreted here as part of a regular expression. One small adjustment and I can easily find the transactions we’re looking for

This is a huge topic all of its own, but here’s a heads-up. Characters like $*.?+ have their own special meaning, and enable you to search for complex and precise patterns in files. If you are searching for something that contains one of these special characters, you need to ‘escape’ it using a backslash directly before the character:

grep -ri \$20 /home/faye/statement.txt

If you don’t do this, grep will interpret the character as more than just a literal, and the output you get may, or may not, return the results you were hoping for.

Finally, if you want to save a search, you can redirect your grep output into a file as follows:

grep -riw first /usr/share/calendar > /home/faye/search.txt

Beware that if you are saving the file in the same directory, or subdirectory, as the one in which you are recursively searching, you can end up stuck in a loop with grep returning output from the file it is creating. If you do this by accident, just Ctrl+C out of the loop, and make sure that you delete the output file, as it will be massive.

You’ll find grep indispensable as you become a seasoned Linux user, but if you really want to master this command there are a couple of further steps you need to take.

Firstly, make use of the man page (press Q to exit once you’ve finished reading):

man grep

This will give you a detailed reference to all grep’s options. You should also try using the help command:

grep –help

which is perfect for a quick reminder.

They can tell you how to show line numbers (brilliant for source files), display filenames only, print contextual lines above and below matches, and even return everything that doesn’t match what you’re searching for.

Second, if you can invest some time learning how to use regular expressions, you will reap the benefits tenfold – and then the grep world really will be your oyster.

%d bloggers like this: