It should be in/Library/Logs/panic.log (unless it's/var/log/panic.log, can't remember). It'll only get written if the panic didn't mess up the filesystem code in the kernel.
Alright, I remember my password now:)
To clarify: I am both on the Fink and the KDE-Darwin project. I can't get to KDE-Darwin CVS right now because my SSH keys are messed up at OpenDarwin.
Errr, I thought pico was a text editor... (with a nasty habit of hard wrapping things when you don't want it to).
I'm a complete Unix newbie (longtime Mac user, discovered Fink, and read lots of man pages), and pico is a LOT easier to use than emacs or vi.
It only deletes hard drives with spaces in their names:)
For all the rest, it just wipes the privileges so that only root can see them.
A simple
cd/Volumes/whatever;sudo du;
will tell you what happened.
You can use it as a furnace. The other ones were just good as space heaters :)
(Shouldn't they be making "the fastest chip in the world" on an architecture that isn't horribly crappy?)
True... I'm 14, and am significantly better at OS X coding/porting than most of the people who come to #fink on irc.freenode.net for tech support :)
MS just pulled that ad, and it's not in the Google cache.
Anyone got a copy they can upload somewhere (or email it to me, i'll handle it)?
Right, that was his point.
I once wrote a kernel extension that crashed your computer so you could see the image, but I lost it.
Sometimes you can trigger a panic with a 'sudo kill -SEGV 2', but that may just fux it enough to not let you reboot and not do a full panic.
It should be in /Library/Logs/panic.log (unless it's /var/log/panic.log, can't remember).
It'll only get written if the panic didn't mess up the filesystem code in the kernel.
* Addresses various potential kernel panic situations.
Now all the users won't get to see the nifty "You need to reboot your computer" image....
Hmmm... maybe we should add that to the FAQ.
Alright, I remember my password now :)
To clarify: I am both on the Fink and the KDE-Darwin project. I can't get to KDE-Darwin CVS right now because my SSH keys are messed up at OpenDarwin.
On #5:
I've heard several people use the phrase "Reality Distortion Field" in conjunction with Steve Jobs. He's too charismatic. It's annoying.
Errr, I thought pico was a text editor... (with a nasty habit of hard wrapping things when you don't want it to). I'm a complete Unix newbie (longtime Mac user, discovered Fink, and read lots of man pages), and pico is a LOT easier to use than emacs or vi.
http://sourceforge.net/projects/gtkquartz/
Yes, I know it's asleep.
Right, I'm going to sic the Webmaster on you.
As a developer for Aleph One (and a mapmaker for M1A1) , I think I'll add some stuff...
1. The Mac OS X version doesn't work very well; however, the stuff in CVS works great.
2. M1A1 is now available for the SDL version of Aleph, too.
Take2 Interactive owns Myth, yes, but Bungie still owns the metaserver.
And that's the meaning I usually use. It's just a matter of semantics.
Yes, it runs on Linux (Mandrake 8.1, I believe).5 1
See http://slashdot.org/article.pl?sid=00/09/21/15492
Marius.net is already hosting a Myth: TFL and Myth 2 server, not based on this code.
I should have added "...or any OS with a Berkeley sockets implementation".
It's HipCrime!
I should think of something useful to post.
So, an OS running Linux and Windows programs reminds you of a BSD4.4/Mach1.4/Darwin OS that runs BSD,MacOS(Carbon),and OpenStep(Cocoa)?
Sort of, but the MacOS X people had access to the code for NeXT and Classic MacOS. Lindows doesn't have Windows code.
Bungie is fairly independent from Microsoft. Halo for PC and Mac WILL be released when they say it will.
Don't make me get Matt Soell on your case.
It only deletes hard drives with spaces in their names :)
/Volumes/whatever;sudo du;
For all the rest, it just wipes the privileges so that only root can see them.
A simple
cd
will tell you what happened.
It's definitly more of one than the article below it..
An M1A1?