I am getting two of those mails everyday to my alternate ID.
Someone's trying to break into my ID. Now, anyway we can stop this / find out who it is?
Ten Minute Yoga
8 years ago
Saturday, October 31, 2009
Monday, October 26, 2009
Windows XP on dual core - Powers off! :(
I have a system with two operating systems installed. Windows XP SP2 and Ubuntu Jaunty Jackalope.
My Laptop has a dual core capability of 2.16GHz each. Let me get straight to the point.
My Windows, which I am almost forced to use at work, because all the tools I need to use are tested well there (irony) and some of them don't exist in Ubuntu, POWERS OFF by itself randomly. By powering off, it's like pulling the power chord from your old PCs. It's running now, and ta da, heck you imagined that.
Just imagine you working on a code with a knowledge it's gonna turn off any instant. Saving your files for every damn line of code or comment. Sure pissed me off!
Searched the net and found numerous numerous queries on the same topic.
a) Many lesser techies with an almost religious belief in MS pooh pooh it as a power problem.
b) Found one hit about worms that do this, but I have an official version of Symantec with regular updates that is good enough to find any virus this powerful. Rule that out.
c) Found this issue on a Windows help central site which claims this is an issue due to a leaky capacitor in your motherboard. They ask you to replace that so that this would work. You'd say you can't argue with that.
Yes you can.
What I have that those question-posters didn't have, is Ubuntu. :)
Ubuntu ran flawlessly under this situation.
That told me options (a) and (c) can go spank themselves.
While the issue seemed to happen very rarely before, it powered off on loading windows today. Again, again and again.
Ubuntu, on the other hand, ran like Forrest Gump. Nothing could stop it.
...and hey, did I tell you? I seem to have found a workaround. I tried various options to see if it had any effect. (I have to use Windows to get to a few things I need to work :( ) Among those attempts, I switched dual core to single core in BIOS.
I was able to log in to Windows. It seems to be running fine for over an hour now. What's funny is that "My Computer" still believes two cores are running at full speed.
If you have any ideas on this issue, let me know. Thanks. I would sure want to use both the cores because I have them! Why should I not use one for the sake of an OS? :( I have a feeling this will happen once your laptop is two years old or something. It was a rare thing and started showing up more frequently, one step at a time. One more GUESS is that this is not related to dual core at all. After all, it is not like it's been showing up since day 1. Setting to single core might have changed some other config by default, or something like that. I don't know.
Again, please let me know if have faced this issue and found the issue / solution for good. Badly need it, man. You never know when the single core system will go down too! F1!
PS: By the way, there's no free game in Windows that'd get anywhere near the Battle of Wesnoth! Wicked addictive.
My Laptop has a dual core capability of 2.16GHz each. Let me get straight to the point.
My Windows, which I am almost forced to use at work, because all the tools I need to use are tested well there (irony) and some of them don't exist in Ubuntu, POWERS OFF by itself randomly. By powering off, it's like pulling the power chord from your old PCs. It's running now, and ta da, heck you imagined that.
Just imagine you working on a code with a knowledge it's gonna turn off any instant. Saving your files for every damn line of code or comment. Sure pissed me off!
Searched the net and found numerous numerous queries on the same topic.
a) Many lesser techies with an almost religious belief in MS pooh pooh it as a power problem.
b) Found one hit about worms that do this, but I have an official version of Symantec with regular updates that is good enough to find any virus this powerful. Rule that out.
c) Found this issue on a Windows help central site which claims this is an issue due to a leaky capacitor in your motherboard. They ask you to replace that so that this would work. You'd say you can't argue with that.
Yes you can.
What I have that those question-posters didn't have, is Ubuntu. :)
Ubuntu ran flawlessly under this situation.
That told me options (a) and (c) can go spank themselves.
While the issue seemed to happen very rarely before, it powered off on loading windows today. Again, again and again.
Ubuntu, on the other hand, ran like Forrest Gump. Nothing could stop it.
...and hey, did I tell you? I seem to have found a workaround. I tried various options to see if it had any effect. (I have to use Windows to get to a few things I need to work :( ) Among those attempts, I switched dual core to single core in BIOS.
I was able to log in to Windows. It seems to be running fine for over an hour now. What's funny is that "My Computer" still believes two cores are running at full speed.
If you have any ideas on this issue, let me know. Thanks. I would sure want to use both the cores because I have them! Why should I not use one for the sake of an OS? :( I have a feeling this will happen once your laptop is two years old or something. It was a rare thing and started showing up more frequently, one step at a time. One more GUESS is that this is not related to dual core at all. After all, it is not like it's been showing up since day 1. Setting to single core might have changed some other config by default, or something like that. I don't know.
Again, please let me know if have faced this issue and found the issue / solution for good. Badly need it, man. You never know when the single core system will go down too! F1!
PS: By the way, there's no free game in Windows that'd get anywhere near the Battle of Wesnoth! Wicked addictive.
Sunday, October 11, 2009
Subnet, Subnet mask and find out the machines in the same sub network
Awrite. Here's the next deal.
What's this subnet that people talk about?
A subnet or subnetwork is like virtualizing a network. Though we have one network, we use masks to make it behave like more than one. Like physical processors and logical processors.
So, here was a guy who asked me how in the world I could claim that the two IP addresses 9.134.60.30 and 9.134.60.200 do not belong to the same subnet.
He thought I'd gone crazy. Two months ago, I'd have said the same.
How do we determine if the given IPs belong to the same subnet? This is where the subnet mask comes into the picture.
Let's take 255.255.255.192 as the subnet mask for the second IP.
Let me take it further in steps.
Step 1: Take one IP and the subnet mask.
Step 2: Do a bitwise AND of the two addresses.
For those of you with the thought, "Oh right, but er.. how?", each of the four numbers in the IP should be converted to an eight digit binary.
eg. 9 would be 00001001. (Use the windows calculator to convert big numbers if you don't want to sit and think about it). Some of you may have a hex address (in system logs etc). eg. "9a ff cc aa". It is simpler in this case. each of them would transform to a four digit binary and you don't need any calculators here. '9 a' would be '1001 1010'.
For our example,
IP address : 00001001 10000110 00111100 11001000
subnet mask: 11111111 11111111 11111111 11000000
Bitwise AND: 00001001 10000110 00111100 11000000
(1 only if both
inputs are 1)
Step 3: Ta da. The result of the bit wise AND is your network address.
Here, it is 9.134.60.192
Step 4:
How many IPs can be in this subnet?
Count the number of zeroes from the right end. Six.
Maximum possible number of machines would be: 2 to the power of 6, which is 64.
Every subnet has a network address (one we found there) and a gateway IP. leaving those two, sixty two other IPs can be accommodated.
Including those two IPs, the range is usually 9.134.60.192 to 9.134.60.255
...and there you go, 9.134.60.30 is nowhere close to being in this subnet.
Peace.
What's this subnet that people talk about?
A subnet or subnetwork is like virtualizing a network. Though we have one network, we use masks to make it behave like more than one. Like physical processors and logical processors.
So, here was a guy who asked me how in the world I could claim that the two IP addresses 9.134.60.30 and 9.134.60.200 do not belong to the same subnet.
He thought I'd gone crazy. Two months ago, I'd have said the same.
How do we determine if the given IPs belong to the same subnet? This is where the subnet mask comes into the picture.
Let's take 255.255.255.192 as the subnet mask for the second IP.
Let me take it further in steps.
Step 1: Take one IP and the subnet mask.
Step 2: Do a bitwise AND of the two addresses.
For those of you with the thought, "Oh right, but er.. how?", each of the four numbers in the IP should be converted to an eight digit binary.
eg. 9 would be 00001001. (Use the windows calculator to convert big numbers if you don't want to sit and think about it). Some of you may have a hex address (in system logs etc). eg. "9a ff cc aa". It is simpler in this case. each of them would transform to a four digit binary and you don't need any calculators here. '9 a' would be '1001 1010'.
For our example,
IP address : 00001001 10000110 00111100 11001000
subnet mask: 11111111 11111111 11111111 11000000
Bitwise AND: 00001001 10000110 00111100 11000000
(1 only if both
inputs are 1)
Step 3: Ta da. The result of the bit wise AND is your network address.
Here, it is 9.134.60.192
Step 4:
How many IPs can be in this subnet?
Count the number of zeroes from the right end. Six.
Maximum possible number of machines would be: 2 to the power of 6, which is 64.
Every subnet has a network address (one we found there) and a gateway IP. leaving those two, sixty two other IPs can be accommodated.
Including those two IPs, the range is usually 9.134.60.192 to 9.134.60.255
...and there you go, 9.134.60.30 is nowhere close to being in this subnet.
Peace.
Monday, September 14, 2009
Drugs to erase Memory imprints in Humans?
http://www.timesonline.co.uk/tol/life_and_style/health/article6832339.ece
This is about erasing sections of Human memory! Those moments which you want to forget, those past moments that traumatize you, they will be more than just things of the past. They will be erased!
This is an interesting idea actually and movies have been based on this (like 'paycheck' and 'Eternal sunshine of the Spotless mind'). While making this technology possible is just great, I believe it has more negative factors associated with it than the positive factors.
I agree, this helps a great deal for people who want to forget what happened when they suffered a great deal, as in cases of World war concentration camps, rapes and cases where you have lost a loved one and you just cannot deal with it.
Is forgetting your lost one really the best way of tribute? What about the side effects?
In other cases too, after you have forgotten stuff, it is human curiosity to go back and find what happened. In this case, you will not remember what happened or the seriousness or intensity of it. You'll go back to the newspapers or anything and try to find out what happened. Also, This will be a gross Human failure, if commercialized.
I can only think of two cases where this will really be useful.
1. Secret service:
People will essentially be forced to forget what happened during their tenure in CIA or RAW. This will mean they do not know any more secrets. They will even think they might have accomplished something great even if they hadn't :)
2. Saving Criminals from death:
Death penalty can be avoided by just erasing out a person's memory and allowing him to live. Many criminals are daring and brilliant. They can even be trained for the army / intelligence for all I know.
Also, other serious crimes can be handled in a similar manner. Funny I used this technique in an old story of mine at http://letmekillyou.blogspot.com/2008/07/fictional-reality.html
If commercialized, there is no way this technology can be restricted from falling into the wrong hands, like Terrorist organizations, who can brainwash people more literally to use them. Research folks should be more careful with this.
Have you ever looked back on a old bad memory and laughed? You'd want to forget a person now, but a few years down the lane, you'd be happy you didn't forget him.
Want to close out with, "Memories remain the same, but the way we look at them changes from time to time."
This is about erasing sections of Human memory! Those moments which you want to forget, those past moments that traumatize you, they will be more than just things of the past. They will be erased!
This is an interesting idea actually and movies have been based on this (like 'paycheck' and 'Eternal sunshine of the Spotless mind'). While making this technology possible is just great, I believe it has more negative factors associated with it than the positive factors.
I agree, this helps a great deal for people who want to forget what happened when they suffered a great deal, as in cases of World war concentration camps, rapes and cases where you have lost a loved one and you just cannot deal with it.
Is forgetting your lost one really the best way of tribute? What about the side effects?
In other cases too, after you have forgotten stuff, it is human curiosity to go back and find what happened. In this case, you will not remember what happened or the seriousness or intensity of it. You'll go back to the newspapers or anything and try to find out what happened. Also, This will be a gross Human failure, if commercialized.
I can only think of two cases where this will really be useful.
1. Secret service:
People will essentially be forced to forget what happened during their tenure in CIA or RAW. This will mean they do not know any more secrets. They will even think they might have accomplished something great even if they hadn't :)
2. Saving Criminals from death:
Death penalty can be avoided by just erasing out a person's memory and allowing him to live. Many criminals are daring and brilliant. They can even be trained for the army / intelligence for all I know.
Also, other serious crimes can be handled in a similar manner. Funny I used this technique in an old story of mine at http://letmekillyou.blogspot.com/2008/07/fictional-reality.html
If commercialized, there is no way this technology can be restricted from falling into the wrong hands, like Terrorist organizations, who can brainwash people more literally to use them. Research folks should be more careful with this.
Have you ever looked back on a old bad memory and laughed? You'd want to forget a person now, but a few years down the lane, you'd be happy you didn't forget him.
Want to close out with, "Memories remain the same, but the way we look at them changes from time to time."
Saturday, September 5, 2009
The AIX OS
IBM has its own brand of Unix. The AIX.
Most users of UNIX that I've met think AIX is some sort of OS used by higher-humans, and Solaris is for humans. Like, there's this dude I know, working in retail services for an MNC. "I work on C and UNIX. Sun's unix, you know. Also, hey, there's this OS... AIX. Gawd, it's so complex. I've even worked on that, you know."
I've not used or seen how Solaris works till this date, but I can assure you, AIX is not being designed solely for secret Nasa operations (or at least nothing I know about!). A 15 year old can work on it just like he works on DOS. Fact is, AIX has so many distinct features compared to its competitors that when you first look at it, you're lost. It takes time to grow into it, and it's worthwhile for UNIX system admins and organisations to read up on AIX and the advantages it offers over its rivals. There's so much!
AIX is mostly used on P-Series systems, and it is designed on top of them, unlike any other style of UNIX; so, I say you get max returns (performance and stability) on your investment on Pseries with AIX, compared to Solaris, UX or linux.
If you're here reading this, it means that you already know about the AIX basics and its history. For all I know, you might even be an ardent DevWorks dude. So, I stop here.
Most users of UNIX that I've met think AIX is some sort of OS used by higher-humans, and Solaris is for humans. Like, there's this dude I know, working in retail services for an MNC. "I work on C and UNIX. Sun's unix, you know. Also, hey, there's this OS... AIX. Gawd, it's so complex. I've even worked on that, you know."
I've not used or seen how Solaris works till this date, but I can assure you, AIX is not being designed solely for secret Nasa operations (or at least nothing I know about!). A 15 year old can work on it just like he works on DOS. Fact is, AIX has so many distinct features compared to its competitors that when you first look at it, you're lost. It takes time to grow into it, and it's worthwhile for UNIX system admins and organisations to read up on AIX and the advantages it offers over its rivals. There's so much!
AIX is mostly used on P-Series systems, and it is designed on top of them, unlike any other style of UNIX; so, I say you get max returns (performance and stability) on your investment on Pseries with AIX, compared to Solaris, UX or linux.
If you're here reading this, it means that you already know about the AIX basics and its history. For all I know, you might even be an ardent DevWorks dude. So, I stop here.
Thursday, August 20, 2009
Intro to me
If you ask me, even God must have had a beginning.
The intro is that I work on AIX, and this is where I mention the usual disclaimers.
* This blog includes just my personal opinions. It does not reflect the views of the AIX organisation or IBM.
* The blog will focus more on performance and related tools and less on AIX in general (as I personally am not the strongest admin around here. I will learn the admin stuff as I write here)
* I don't promise any regular updates and I don't expect regular visits from you. If you visit more and get involved, I'll be tempted to write more.
Introduction to the AIX Operating system will follow. If you have any performance related queries, let me know. I'll at least ask someone who knows about it and get back to you :)
The intro is that I work on AIX, and this is where I mention the usual disclaimers.
* This blog includes just my personal opinions. It does not reflect the views of the AIX organisation or IBM.
* The blog will focus more on performance and related tools and less on AIX in general (as I personally am not the strongest admin around here. I will learn the admin stuff as I write here)
* I don't promise any regular updates and I don't expect regular visits from you. If you visit more and get involved, I'll be tempted to write more.
Introduction to the AIX Operating system will follow. If you have any performance related queries, let me know. I'll at least ask someone who knows about it and get back to you :)
Subscribe to:
Posts (Atom)