A FAMILY FULL OF EYE CANDY
on 01/02/2011 at 02:41 PM
Looks like Diane did a bit of cropping herself there.The miracle of the lady shick I suspect.
"Does that happen with the op. system in a MAC as well?”
- Ah, short answer? No…
Never had a Mac or Linux box hang completely or be unable to kill a hung process unless the hardware was faulty, but I have witnessed such behavior on Windows.
To kill a process, is much the same as in Linux. Lookup the process id number and issue a kill command:
kill -9 3909That would kill process 3909, the -9 flag means to kill with extreme prejudice!
There is a GUI Activity Monitor much like Task Manager in Windows, but when you quit a process in Activity Monitor it stays quit. Except for special items that are configured to restart when killed by the launchd system. i.e. you could setup a webserver that auto restarts when it crashes, etc. - http://en.wikipedia.org/wiki/Launchd
Apple Mac’s are now really Unix machines. Under the hood, they are running a Mach kernel, many of the BSD family of command line utilities, etc. You get a full development environment for free and anything that runs in Linux or FreeBSD will run on a Mac. It has commercial software such as Microsoft Office, Adobe Photoshop, etc.
You can run VMWare Fusion or Parallels to setup a Windows virtual machine that runs in a window inside the Mac OS. You just need enough RAM to run both operating systems effectively. Win7 needs about 2GB’s in VM to run quickly. Since Mac’s are Intel PC’s you can also dual boot Win7 and MacOS and Apple supplies a utility called Boot Camp to make it easy to setup.
I never would have bought a Mac prior to Mac OS X being released. Mac OS 9 was a toy. Mac OS X is a complete redesign based on NeXTStep/OpenStep which is based on commercial UNIX. Pop open the Terminal application located under Applications, Utilities and you are sitting at a full Unix shell prompt!
Posted by MJS
01/02/2011 at 09:45 PM
Is that the same Diane Kruger who played Bridget VonHammersmark in Inglorious Basterds?
Nice little tits on the hair dresser. Probably gay though.
You have probably gotten your box fixed by now, but, if not, it sounds like you may have a services or registry issue.
The quickest and easiest treatment is a system restore. Pick a date a couple of weeks ago and have at it!
I have found that a nice cleanup with CCleaner (free) and its registry gadget can help.
Best wishes in the New Year!
Posted by heldmyw
01/03/2011 at 11:44 AM
kill -9 pID is straight up old school Unix. And it will kill just about any process you have running, as long as it isn’t too hungry: poorly written code that is allocating more and more memory within an infinite loop will leave just about no resources for any other process. So the smart move is to already have a second session open ahead of time, just in case.
It’s usually better to just kill pID. Sometimes you need the shell the runaway is running in. OTOH, sometimes you need to kill -KILL a proc, and sometimes you need to face the music and call the sysadmin to have it done for you.
unix geeks, use “man kill” to learn more.
On the last hand, Windows XP has it’s own version of kill, called taskkill. It works pretty well if you learn how to use it, and it will shut down stuff that Task Manager won’t.
