....::::::WELCOME TO TECH-HUT::::::......

www.TechHut.co.cc

Welcome to Tech-Hut:Your Daily Dose Of Technology!
This Place is all about Computers!

It doesn't matter if you came here looking for something specific, Or just browsing through... Just look around and you are bound to find something of your interest here, and most importantly OF USE!

If you find anything that interests you you can use "ADD THIS" social bookmarking button (Which is ever hanging at the end of every post) to bookmark that post on ALMOST ANY bookmarking service that you might prefer to use. So that you can reach that article easily whenever you need to consult it.
Even The Search Engines (One above the Post, and one at the bottom) are pretty friendly(Google At Work!). They can help you get what you are looking For.

You can even link back from your blog to that specific article, or The Tech-Hut.

Don't Forget To bookmark Tech-Hut, so that you can reach here easily. PRESS CTRL+D to Bookmark this site in your Browser.

..... and yeah! one last thing :) Please do comment on the articles... They Keep us going and tells How We Are Doing

Are we asking TOO MUCH??? Well... All We guys need is SOME ENCOURAGEMENT!


Enjoy Your Stay At Tech-Hut
...... And Come Back Again!


Regards,
Tech-Hut Team



FEEDBACK PLEASE
ABOUT US





~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
BE AN AUTHOR AT TECH-HUT
If You have any good Technology related article and would like to showcase it to the world, we will be happy to publish here on Tech-Hut for world to see, with credits to your Name.
However there are certain quality guidelines that you need to follow

1. Article should Be unique and informative.
2. It should NOT be a copy of someone else's work of from another website.
3. Language should be ENGLISH, EASY TO UNDERSTAND, AND DECENT

Please send in your articles by clicking this Contact Us link. Contact US
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
SOME RIGHTS RESERVED
You can use any of the articles published on this blog to publish somewhere else or even to e-mail your friends. We believe in contribution towards the society. All We ask for is the credit to the original author and a link to the original article on this blog.

Please notify us if you publish them anywhere us, which you are free to do!
Contact Us


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Question:
(HP laptop Problem "Plugged in , not charging")
I have a HP laptop problem (DV5), Recently i am facing this problem. When i plug the charger i shows plugged icon in battery, but it would stop charging after some time. "Clicking on the battery icon shows plugged in , Not Charging" why is that? No matter how long i keep it plugged in laptop is not charging. It runs good on AC power. Is the problem with my hp charger ? or my battery ? should i replace my battery ? it is new !!

ADDITIONAL INFO:
HP battery check shows my battery is broken and i should get it replaced!!! But i bought it monts ago !!



Answer:
" HP laptops Not Charging " Is one thing i hear most these days and clearly most common HP laptop problem. Here is a trick you can try . Hopefully it will sort your problem.

#Its possible that Laptop not charging due to dust at the contact points of laptop battery, or adapter plug. First thing is to make sure all the contact points are clean and properly connected, take your battery out , clean the metal contact points well with dry clean cloths (Don't use cleaning solvents) . Same thing goes with the charger plug. Make sure none of the contacts are loose including the AC cable going into the Adapter.

# Now don't plug in the AC power and continue to use your laptop till the battery is completely discharged. After that plug in the AC and let it charge for whatever time it takes to get fully charged

This should Sort your problem.
If not please reply back

Being bored and having nothing to do, i thought of writing this...
Hey, we might aswell give this thread space for that great man. If you have anything to share about him, Please leave Comments!
Linus Torvalds writes the Linux kernel, he also likes a good mailing list flamewar, not least because he has a very sarcasatic wit. Here he is, writing about various topics.

On fair use:

>When you start thinking that you have absolute control over the content or
programs you produce, and that the rest of the worlds opinions doesn't matter,
you're just _wrong_.

>Me, personally, I think the RIAA and the MPAA is a shithouse. They are
immoral.

On virtualization:

>I think what you're seeing is virtualization proponents being absolutely
_desperate_ for any reason to use virtualization.

On userspace binary drivers:

>No user-space ass-hattery here.

On turning off interrupt requests:

You cannot have a generic kernel driver that doesn't know about the low-
level hardware (not with current hardware - you could make the "shut the
f*ck up" a generic thing if you designed hardware properly, but that simply
does not exist in general right now).

On those arguing for userpace interrupt request handlers:

You may be a bit simple. But I think it's more polite to call you "special". Or
maybe just not very used to how hardware works.

On C++ :
>In fact, in Linux we did try C++ once already, back in 1992. It sucks. Trust
me...

>C++ is a horrible language. It's made more horrible by the fact that a lot of
substandard programmers use it, to the point where it's much much easier to
generate total and utter crap with it. Quite frankly, even if the choice of
C
were to do nothing but keep the C++ programmers out, that in itself would
be a
huge reason to use C.

>So I'm sorry, but for something like git, where efficiency was a primary
objective, the "advantages" of C++ is just a huge mistake. The fact that we also
piss off people who cannot see that is just a big additional advantage.

On Linux Kernel version 2.6.19:

> It's one of those rare "perfect" kernels. So if it doesn't happen to
compile with your config, you can rest easy knowing that it's all your own d*mn
fault, and you should just fix your evil ways.

On Intel's inventions:
> The fact that ACPI was designed by a group of monkeys high on LSD, and is
some of the worst designs in the industry obviously makes running it at _any_
point pretty damn ugly. And the fact that MB vendors don't test it with anything
else than Windows (and sometimes you wonder whether they do even that) doesn't
help.

> EFI is this other Intel brain-damage (the first one being ACPI). It's
totally different from a normal BIOS, and was brought on by ia64, which never
had a BIOS, of course. Sadly, Apple bought into the whole "BIOS bad, EFI good"
hype, so we now have x86 machines with EFI as the native boot protocol.

On Apple OS X:

> OS X in some ways is actually worse than Windows to program for. Their file
system is complete and utter crap, which is scary.

AND IF YOU THINK THIS IS NOT ENOUGH, HERE IS A MAILING LIST FLAMEWAR BETWEEN Linus AND Andy Tanenbaum .

While a few commands, such as 'cd' are built directly into bash; many of the most important commands come from coreutils, a GNU package containing over a hundred commands.
Some are the well known commands such as 'ls', 'mv' and 'cat'. While there are some more obscure ones that are not always discovered because there are also more modern programs that can do similar jobs.

These less well known commands often reflect the history of computing where once upon a time you would do everything possible in the Bourne or Bash shell, rather than waiting a long time for program such as emacs or vi to start, which at the time were considered to be memory intensive but now seem lightning fast (now you can even run them from a mobile phone).
Here we will look at ten useful commands that might come in handy one day.


1. tac
One of the key commands is 'cat', short for concatenate, which you can use to add the contents of one file to another, or just to print a file or set of files out to the screen.
cat 1.txt 2.txt > 3.txt # Adds 1 and 2 together as a new file 3.
cat 3.txt # Prints file 3 out to the screen.
However, tac is cat backwards, it lets you concatenate and print files in reverse. It could come in very handy for some uses, for example if you want to reverse a list or a log file.
tac 1.txt > 2.txt # 2 is a reversed copy of 1

2. tee
Often you will pipe the output of one program as the input of another:
ps -e grep apache
This command will feed to grep the output of ps, thus showing what apache processes are currently running.
Or you may redirect the output of a command to a file:
ps -e grep apache > apache-processes.txt
However, what if you want to see the results and write the file or files? This is where the tee command is useful:
ps -e grep bash tee bash-processes.txt # Print the results to the screen but also to a file.
You can enter more than one filename if you want multiple copies.

3. pr
Most printers these days will attempt to print out anything that you throw at them. However, you still may want to format a file in a certain way before sending it to the printer. For example, you may regularly discuss a log or some records at a meeting and want them to look the same every week.
The pr command gets a text file ready for the printer. For example you may want a set page or column format.
pr +10 -h"Apache Errors" -l25 error_log lpr -# 5
Reading the pr command from left to right, the options are to start from page 10, then add a header to each page, make each page 25 lines long and lastly the filename. The result is then piped to lpr which will submit the file to the printer with a request for 5 copies.

4. stat
Using 'ls -l' will give a lot of information about a file, enough for me at least. If you are a glutten for punishment, you can use the 'stat' command to get more information:
$ stat statFile: `stat'Size: 34684 Blocks: 72 IO Block: 4096 regular fileDevice: 302h/770d Inode: 7586763 Links: 1Access: (0755/-rwxr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root)Access: 2007-01-06 00:35:15.000000000 +0000Modify: 2006-09-18 09:50:24.000000000 +0100Change: 2007-01-04 14:51:47.000000000 +00005. yes
'yes' is one of those strange legacy commands, the most comic featured here. 'yes' prints a string and a newline and then repeats until interrupted.
As dumb as it sounds, it does have a couple of uses. Firstly, if you want to turn an interactive command into a non-interactive one.
There are some command line programs which you run and then it asks something like "Are you sure?". For example:
yes 5 command
This will run command then send the string 5 and a newline (i.e. as if you had pressed return).
It almost goes without saying that you can also use yes to turn your processor up to 100% usage, for example if you are testing some fans or cooling system or if you otherwise want to punish your machine.

6. expand
So you wrote lots of nice Python files, indenting them with tabs. But shock horror, you found out that the current fashion is to use four spaces not tabs!
No problem, the expand command converts tabs to spaces, here we have chosen to use 4 spaces:
expand -4 uncoolscript.py > coolerscript.py
To go from spaces to tabs, you can use 'unexpand' command.


7. split
'split' takes a file and splits it into chunks for you. For example:
split -l 20 access_log part
This command will split the file access_log into chunks of 20 lines each, the name of each file will begin with part.

8. uniq
Sometimes you will have a file that is a long list of items and you want to remove all the repeated lines, or possibly you want to group the items into sets with a number of occurrences.
So to remove all repeated lines:
uniq file.txt
You can also use the output of another command:
cat file.txt uniq
To include the occurrence count:
uniq -c file.txt

9. wc (i know u already know this, but still)
wc allows you to count words, lines and bytes. The default is to show all three:
wc ulyss12.txt
32758 267235 1561677 ulyss12.txt
[lines] [words] [bytes]
Using -l just gives you lines:
wc -l ulyss12.txt32758 ulyss12.txtUsing -w just gives you words:
wc -w ulyss12.txt267235 ulyss12.txt


10. shred
'rm', the remove command, unlinks a file so the space can be reused. However, files deleted can sometimes be recovered with a bit of persistence and luck.
Our final command is shred. 'shred' overwrites a file repeatedly, making it much harder to recover. This can be useful for personal financial information such as your credit card details.
shred -u mastercard.txt
You can even use shred on a device such as a partition. If you want to completely clear your home partition which happens to be stored on /dev/sda6. Then you would use:
shred /dev/sda6
Alert readers will note that I used -u in the first example but not the second. This because you want to unlink (i.e. rm) a file but not a device - you will want empty the /dev/sda6 to exist.
Now there are some complications to this. Firstly, a complex RAID setup might interpret this as hardware failure and replace the data. Likewise some corporate setups will sync the files with a server. Shred will not remove these copies.
Lastly, some fancy modern journaled filesystems such as reiserfs will have a backup in the journal, you will need to mount the partition in a non- journaled mode for shred to work completely.
There we go, ten commands that you may not have heard of, I hope you can find at least one that is useful in your computing activities.

Who says unix is not fun???
These are some command line fun!

(Some of them won't apply to linux)

try them and post if you find something new and fun

% cat "food in cans"

cat: can't open food in cans



% nice man woman

No manual entry for woman.



% rm God

rm: God nonexistent



% ar t God

ar: God does not exist



% ar r God

ar: creating God



% "How would you rate Quayle's incompetence?

Unmatched ".



% [Where is Jimmy Hoffa?

Missing ].


% If I had a ( for every $ the Congress spent, what would I have?

Too many ('s.

% got a light?

No match.



% man: why did you get a divorce? man::

Too many arguments.



% !:say, what is saccharine?

Bad substitute.


--------------------------------------------------------------------------------





/* not csh but sh */

$ PATH=pretending!/usr/ucb/which sense no

sense in pretending!



$ drink bottle: cannot open

opener: not found







--------------------------------------------------------------------------------





Christmas song in UNIX

A Christmas song, in everyone's favourite language:



Sing



better !pout !cry

better watchout

telnet why

santa claus <> town



cat/etc/passwd > list

ncheck list

ncheck list

cat list grep naughty > no_gift_list

cat list grep nice > gift_list

santa claus <> town



who grep sleeping

who awake

who egrep 'badgood'

for ( goodness sake) {





be good

}