Suramya's Blog : Welcome to my crazy life…

July 2, 2009

My Article just got Published in LinuxGazette #164

Filed under: Linux/Unix Related — Suramya @ 7:46 PM

My Latest article on ‘Sending and Receiving SMS from your Linux Computer just got published in the Linux Gazette #164 🙂

Check it out if you get the time.

– Suramya

June 13, 2009

My Upgrade to Debian 5 Testing & KDE 4

Filed under: Linux/Unix Related,My Life,My Thoughts — Suramya @ 11:40 PM

Yesterday night I decided to upgrade my system from Debian 5 Stable to Testing. As you might know Debian has three branches for every version that it releases:

Stable -> The most tested branch. Everything is as stable as possible and applications should not conflict with each other. The software versions available in this branch are slightly older
Testing -> This is slightly less stable branch but contains more recent versions of programs. For example I had to upgrade to Testing to get the correct libraries to run Firefox 3 in Debian Version 4
Unstable -> As the name says this repository contains programs that might have issues integrating with other programs in Debian. Doesn’t mean that the programs themselves are unstable, just means that they might not play well with others. Usually this contains the latest versions of software.

Anyways, usually I always run the Unstable branch but this time since v5 had just been released I stuck with the Stable branch to try it out. I really liked it.

Yesterday I decided to upgrade to Testing. So I pointed the repository to Testing and ran the following commands:

apt-get update
apt-get dist-upgrade

and went off to sleep. Today all the items were downloaded and I logged in to KDE4 (the latest version) and I am not pleased. It looks like Vista. All the menu’s are changed. The control panel looks and works like the Windows Control Panel. If I wanted a Vista experience I would have installed Vista on my system.

In the old KDE I could update the wallpaper for any of my 4 desktops from one location. I this one I don’t seem to be able to do so. Plus I can’t get the system to start showing the ‘Quick Launch’ bar. When I add that widget I get a 2mm – 5 mm wide blank area added to my taskbar. To top it all Plasma is using 80%-90% of my CPU even when I am not going anything other than typing this post.

I thought I should get a screenshot of my CPU usage and loaded up GIMP, but in KDE4 this loads up two separate windows, one with the toolbox and one with the menu items. What the hell? What was wrong with the old way where the menu items were listed on top of the toolbox. Now that place is empty and the menu’s are in another window.

Ok, now I am annoyed. Now the Acquire menu item has disappeared from GIMP. This could be a change in GIMP but I am pretty sure I was using the same version earlier. So I can’t seem to get a screenshot easily. I know I can do it other ways but am too lazy to do that. So no screenshots. In anycase too many images increases the load times of the blog homepage 🙂

So my verdict? I am switching back to Debian Stable. Unfortunately it will mean reinstalling the OS ’cause there is no way to downgrade from Testing to stable. thankfully all my data is kept separately so I just have to format one partition. But still its a pain.

I will keep with this version until Debian forces me to upgrade to KDE4. After that… lets see, I might try other desktop managers or hopefully by then KDE4 will have matured and cleared up these issues.

Ah well… Let me get my system back the way it was, then I can get some work done…

– Suramya

November 11, 2008

Fix Unresponsive or Frozen Linux Computers

Filed under: Knowledgebase,Linux/Unix Related — Suramya @ 4:43 PM

If you are ever stuck on a Linux system that is completely unresponsive try the following key combination to get access back:

Alt PrintScreen r s e i u b.

When you type the command the system executes the following commands:

* r – takes the control of the keyboard back from X.
* s – writes the data from the disc cache to the hard disk.
* e – sends SIGTERM to all processes except init.
* i – sends SIGKILL to all processes except init
* u – remounts all the filesystems readonly (basically a measure to help you reboot safely)
* b – reboots the system

Please keep in mind that this is a last ditch method, that is to be used only when everything else has failed to get you access to the system. Normally you should be able to switch to a virtual terminal (F1-F6) and kill the offending application.

Source: Fix Unresponsive or Frozen Linux Computers using Shortcuts | MakeUseOf.com

– Suramya

April 21, 2008

Getting my wireless card working in Debian

Filed under: Computer Tips,Knowledgebase,Linux/Unix Related,Tech Related — Suramya @ 2:03 AM

As promised here are the steps that I followed to get my wireless card working on my Comaq Presario V3000 in Debian:

1. Install ndiswrapper

In my case I allready had the ndis wrapper installed. If thats not the case with your system run the following command as root to install it:

apt-get install ndiswrapper-common ndiswrapper-utils ndisgtk

2. Disable the “bcm43xx” driver on your system

Run the following command at a command prompt as root :

echo 'blacklist bcm43xx' | sudo tee -a /etc/modprobe.d/blacklist

3. Download the Windows driver for your card

My system uses the Broadcom Corporation BCM4310 card and I had to download the Windows driver for it from the Dell site. For some reason the driver I found at the Compaq site refused to work. You can download it from here.

Save this in the /tmp directory cd into the /tmp directory, and unzip the Windows driver package:

cd /tmp
unzip R123456.EXE (or whatever the name of the download is)

4. Install the Windows driver with ndiswrapper

To load the driver you need to run the following command as root:

ndiswrapper -i /tmp/DRIVER/bcmwl5.inf

The you should verify that the driver has been successfully loaded

ndiswrapper -l

The output of this command should look like the following if it is loaded correctly

Installed ndis drivers:
{name of driver} driver present, hardware present

or

{name of driver} : driver installed
device ({Chipset ID}) present

5. Load the ndiswrapper module

You now need to load the ndiswrapper module. Run the following steps at a command prompt as root:

depmod -a
modprobe ndiswrapper

if the above commands don’t give any errors then the drivers have been successfully installed.

6. Configure the wireless card

I have found the ‘netcardconfig’ command the easiest to use when configuring a new card. Run it as root and answer the questions it asks and it will configure the card for you.

7. Set the ndiswrapper module to automatically load at boot

ndiswrapper is not started by default when the system starts up so you must configure your system to load the ndiswrapper module at system startup. To do this, edit /etc/modules file as root to add an entry for ndiswrapper at the end of the file.

vi /etc/modules

Add ‘ndiswrapper’ (without the quotes) to the end of the file in a new line. Save and exit.

Now the module will be loaded when the system next starts up.
—-

A special thanks to JamesGu from the UbuntuForums for figuring out the solution and posting it there.

Hope you find this useful. I certainly did. 😉

Will post about my sound card next.

– Suramya

December 17, 2007

Ping Tunnel – Send TCP traffic over ICMP

Filed under: Computer Software,Knowledgebase,Linux/Unix Related,Tech Related — Suramya @ 10:56 AM

This very interesting application allows you to tunnel TCP traffic over ICMP. Basically if you are behind a firewall that doesn’t allow any TCP data to pass through but allows you to ping systems on the net you can use this to create a tunnel over which you can send any data.

Check it out here: Ping Tunnel – Send TCP traffic over ICMP

Sounds very useful and is something to keep in the toolbox.

– Suramya

September 28, 2007

OpenDisc: Collection of open source software for download

All regular visitors of this Blog know that I like Open Source Software (OSS) and whenever I get the chance I like to spread the word about them. Today I found out about OpenDisc which is a high qualiy collection of open source software (OSS) for the Microsoft Windows operating system (Most of them are available on Linux also) that can be used instead of propitiatory software.

You don’t have to download the entire CD if you just want a few particular programs, This section of their site lists all the programs they have on the CD and links to sites where you can download them directly.

Check it out. The less pirated software you use, the less the chance of getting your computer infected with a virus/trojan. If you are paying for legal software then this will save you a lot of money. Most propitiatory software on my system has been replaced with OSS alternatives so I can vouch for most of the software.

– Suramya

August 18, 2007

’10 commandments for Linux users’ and some thoughts on them

Filed under: Linux/Unix Related,My Thoughts — Suramya @ 7:39 PM

I was browsing the web and I found this post called “The 10 Commandments for New Linux Users” with some simple rules for new linux users that the author thought might be useful for new users. Before I start with my comments, lets just read the ‘commandments’:

1. Thou shalt not log in as root.
    Use “sudo” or “su -” for administrative tasks.

2. Thou shalt use the package manager when possible.
    Sometimes installing from source code can’t be avoided, but when you use your distro’s package manager to install software, you can also use it to update and remove it. This is one of the main strengths of Linux.

3. Thou shalt be a part of the community.
    Freely give what you have received for free. Offer help and advice whenever you can.

4. Thou shalt read documentation and man pages.
    Always read the documentation. The people who wrote the software tried to anticipate your questions, and provided answers before you asked.

5. Thou shalt use the available support system.
    Switching to Linux can be tough. It can be frustrating, but there are a lot of people out there who want to help you. Let them.

6. Thou shalt search.
    In most cases, your question or problem has already been addressed. Try to find the answers that are already out there before asking someone to provide a new one.

7. Thou shalt explore.
    Linux opens a whole new world of options and possibilities. Try everything you can.

8. Thou shalt use the command line.
    Especially when it comes to configuration, use the GUI tools to get your system working, but get to know the command line versions as well. In many cases, the command line is the only way to use some of the more advanced features.

9. Thou shalt not try to recreate Windows.
    Linux is not meant to be a clone of Windows. It’s different. Embrace and appreciate the differences.

10. Thou shalt not give up.
    I tried several distributions before I found one I liked. I still try other distros from time to time. I also tried several different programs to serve one purpose before settling on what I use now (amarok, xmms, beep, exaile for music – azureus, ktorrent, deluge for bittorrents). If you don’t like the defaults, remember that you can change almost everything to suit you.

You won’t believe the responses he got to this post. They ranged from helpful additions to the list, some jokes and some rather rude personal comments on the author and the Linux community in general. This is one of the things I hate about the Fanboy and zealots that abound on the internet. They don’t have the knowledge to actually help someone and are retarded idiots whose sole purpose in life is to provoke a reaction from the other person. They don’t have the guts to standup to someone in real life so they hide behind their computer and make rude remarks about everyone else. I have found a couple of them on my site also and usually I either ignore them or make fun of them. What these idiots don’t realize that the person they are making fun of and calling a nerd/geek/looser is a person who probably earns 10 times more and probably has double their IQ.

Anyways, now that we have that out of the way lets talk about the Commandments themselves:

1. Thou shalt not log in as root.

This doesn’t mean that you shouldn’t log in to root at all. It means that you should login as your normal user for everyday tasks and only login to root when required. I have worked as root for hours when it was required (I was troubleshooting an install) but once I was done I logged out immediately. The issue is that if a root account is compromised or you make a mistake as root it can have a huge impact.

Lets take an example: lets say you are trying to delete all files in your home directory and you wanted to enter the following command: rm -rf ~/* but because you were tired you entered the following instead: rm -rf ~ /* (Notice the space between the ~ and the /). Now, if you are logged in as a normal user you will get a bunch of permission denied messages and you are fine. BUT if you are logged in as root it will delete every file in the / directory (Which is the top folder on the disk and hence contains all the files on your system). In one step you have made your system scrap. You will have to restore from backups or re-install which will take time.

Think that wont happen? It does. More times than you can imagine. Think that this just happens on Linux? Sorry, wrong again. I have personal experience with it on Windows (It was Windows 3.1) and at that time I was just learning how to use computers. I had installed a bunch of fonts on the computer thinking I was installing a fonts program. When I realized that the few 100 MB’s worth of stuff I installed on my system didn’t give me any new programs I was upset. So I decided to delete the fonts from my system. Unfortunately the command I entered was: “deltree c:\Windows”. This command deleted my entire windows directory and I spent a week reinstalling. This would not have happened if I was on Linux or if DOS/Windows had any concept of multiuser access controls. They have gotten a lot better at it and XP/Vista is a whole lot more secure than the older versions.

2. Thou shalt use the package manager when possible.

Usually a good idea unless you have a specific reason for not using it. Think of the package manager as the ‘Add/Remove’ programs equivalent in the Linux world. Only its a lot more powerful and versatile than it. Basically it makes managing the system/installing new software a lot easier. Basically all you have to do is select the program you want to install (using the gui frontend or the commandline) and it does the work for you. The same goes for removing programs. Adding a program manually (by compiling it) confuses the system as the package manager doesn’t know its there so if it needs it for some other program it will just download and install the latest version which might not be compatible with the version you installed.

Compiling programs and installing them is usually only required for users with specific needs or for software that doesn’t exist in the package manager repository. (Most popular programs do exist in the repositories)

3. Thou shalt be a part of the community.

An important part. This doesn’t mean that we expect you to start handing in code patches and fixes. It just means that you share your experiences and if someone asks a question that you can answer, you reply. You can be a part of the community by reporting bugs, creating documentation, help organize a meeting or create a new logo or layout thats more efficient. Proofreading the guides and reporting the issues you found while following it is also helpful. Feedback from a new user is an important step in software development and is appreciated.

4. Thou shalt read documentation and man pages.

Also important, but it doesn’t mean that if you have read it and still don’t understand it you can’t ask questions. It just means that if you want to know what the command is to delete files, you search on google for ‘how to delete files in linux’ before asking questions. Its an important rule because it saves both your time and ours. In the time it took you to ask someone and wait for a reply you could have found the answer if you looked first.

5. Thou shalt use the available support system.

Don’t really agree with this one because sometimes the hardest part is finding the support system. I face this problem when I try to fix issues on Windows systems. If I hit an issue I sometimes have a hard time because I don’t know the correct forums/news groups to ask questions in, while I do know what forums to look in when I have a linux question. So I guess new Linux users face the same issue also.

6. Thou shalt search.

See Point 4.

7. Thou shalt explore.

This is true on both Windows and Linux. Don’t be scared of your computer, its not an evil machine plotting to make your life miserable. Its a tool. When you buy a new car don’t you want to explore all the features in it? Same with a computer.

My cousin just bought a new computer for my nephew and the first thing I told him was “don’t be afraid to experiment whatever you break in the software can be fixed.” (so can the hardware. But that might cost money. 😉 ) I have learned more by breaking down the system and then trying to fix it than just playing with it.

If in doubt ask.

8. Thou shalt use the command line.

I would rephrase this as “Thou shalt learn to use the command line”. Because if you want to (and are interested in it) you can save a lot of time by entering a command to do something instead of clicking through 10 dialog boxes.

9. Thou shalt not try to recreate Windows.

Good one. Linux is a new system. Think of it like a new language. When you are learning Spanish, would you try to enforce English vocabulary rules in it? No right… So why do the same in Linux? You can recreate the layout, etc but don’t expect it to behave exactly like Windows.

10. Thou shalt not give up.

Very important rule. For everything in life as well as computers. If you give up you will never know what you are missing. You are more than welcome to try it and decide that it isn’t for you (Thats your choice) but don’t start installing and then quit the minute you hit the first obstruction.

Finally a new addition from my side:

11. Thou are more than welcome to use whatever OS that suites your needs

The main idea is to get the computer to work for you. If you are happy with Windows and if it works for you then you are more than welcome to continue using it. After all its all a matter of choice. I won’t force you to follow mine and I expect the same from you.

Enjoy the computing world. This is all for now. Will post more later.

– Suramya

August 8, 2007

Secure Websites Using SSL And Certificates

The following website has a good How-To on how you can Secure Websites Using SSL And Certificates on a system running Apache, Bind and OpenSSL.

– Suramya

April 1, 2007

Installing Debian without burning CD’s

Do you want to install Debian on a system thats running Windows but doesn’t have a working CD-ROM (Like my current laptop)? Earlier you had to try to install it using floppies and other methods that didn’t always work but now there’s an easier method:

You can now download a “Debian-Installer Loader” from their project site which is basically an exe file which you can run as a regular exe file. Once you run it, it will work for a few moments and then it’ll ask to reboot your PC, at which point you’ll be given the option to run Windows or Debian. Choose Debian and you will end up in a regular Debian installer interface.

Here are some Screenshots of how the installer looks like.

I haven’t tried it yet so I can’t personally verify how well it works but so far I have heard only good things about it. If you try it out let me know how it works out.

Thanks,
Suramya

March 16, 2007

SCO v IBM: SCO shows the copyrighted code

Filed under: Linux/Unix Related,News/Articles — Suramya @ 5:53 PM

On March 6, 2003, a company called the SCO Group which was doing very poorly financially decided to earn some revenue by filing a $1 billion lawsuit against IBM for allegedly adding copyrighted code from Unix (For which SCO is the copyright holder) to Linux. Over time this amount rose to $5 billion. SCO then sent letters to most fortune 500 companies using Linux and demanded licensing fees from them.

This case quickly became one of the most watched cases in computer law as it would determine the future of Linux and the ruling would set a precedent for other cases where open source projects are involved.

The lawsuit caused a huge outrage in the open source community and its members pointed out that it was highly unlikely that Linux contained code from Unix as it had been written from scratch by many programmers all over the world and its code was available for all to check. They demanded that SCO show the code that is supposed to be infringing so that they could verify the claim and remove it from the kernel if required. But SCO refused to show the code, it made many excuses and delayed it a lot.

On the 7th of March 2007 they finally showed the code that was included in Linux and it was a whooping 326 lines of code out of which 121 lines are #define headers. These headers basically allow the programmer to define easy to remember aliases for values/data. e.g. we can have the following statement: #define NAME Suramya Tomar in the code and now we can use NAME (which is easier to remember and type) instead of using “Suramya Tomar” in the code.

Now if we follow the pricing model that means each line of code is supposed to be worth $15,337,423.31. Howz that for quality code? I hope they paid the guy/girl who wrote it really well…

NEways now that the SCO case has been shown for the time waster it was, I suppose it will get thrown out of the court soon. They should be made to pay IBM and OSS community for all the grief they caused, but I guess since the company is almost bankrupt it will just file for Chapter 11 (Bankruptcy) and shutdown. Good riddance I say.

Read the transcript of the Hearing with detailed commentary/analysis : Groklaw – Transcript of Hearing in SCO v IBM

For more detailed info on the case check out: SCO vs IBM

Thanks to OpenDotDotDot for the link.

– Suramya

« Newer PostsOlder Posts »

Powered by WordPress