![[info]](http://l-stat.livejournal.com/img/userinfo.gif?v=92.2){kind=small}
bouncy One more for today.
So yesterday I had to get a new license plate. What the hell, I figured: I asked about personalized tags, or "prestige" tags as they're apparently called in my county. The deal seemed fair, so I bit. HERMES was my first choice, but it was taken. My second choice, however, was available. In 4-6 weeks I should be driving around with SIGSEGV on my tag, marking me officially as a Unix geek.
w00t.
(LJ Spellchecker Genius of the Day: SIGSEGV -> SIXGUN)
September 1 2005, 03:02:12 UTC 6 years ago
*blink blink*
*blink blink*
*covers eyes with hand and sighs*
*shakes head*
Although that spell checker thing is sad. It's like a comedian was saying once that the saddest thing was he would spell words so bad that spell checker didn't even have a suggestion. Although I still don't understand only matching three of seven letters, but... :P
September 1 2005, 04:25:16 UTC 6 years ago
before I left LA we were fighting over "UID 0"
hehe
September 1 2005, 13:31:01 UTC 6 years ago
September 1 2005, 10:41:21 UTC 6 years ago
Explain the meaning of your tag?
And I looooooove prestige plates. I'm bummed 'cause I don't have one right now...
September 1 2005, 13:36:10 UTC 6 years ago
September 2 2005, 00:52:31 UTC 6 years ago
September 1 2005, 13:44:39 UTC 6 years ago
OK, most modern computers have the concept of memory access permissions. Your programs can access only certain sections ("segments") of memory. Other segments of memory are owned by other people's programs or by the computer's internals. Some of the most common bugs in Unix programs cause those programs to inadvertently access segments of memory that they're not allowed to. When the computer sees this happen, it signals a "segmentation fault" or "segmentation violation".
The computer tells the program this happened with a special thing called a signal. There are a handful of different types of signals that the computer can send to a program. There's one to say "Somebody's asking you to stop running." That one's called SIGTERM. There's one to say "A timer that you set just went off." That one's called SIGALRM. There are anywhere from 16 to 64 or even more of these. The one that says "You just caused a segmentation violation" -- that common memory access error I was talking about above -- is called SIGSEGV.
If you've ever programmed in Unix using the C programming language or one of its derivatives, you've almost certainly seen a lot of SIGSEGVs. If you haven't, well, you're probably scratching your head looking for an explanation.
In other words, it's a handy shibboleth. :-)
September 1 2005, 15:52:08 UTC 6 years ago
I like rainbows.
Rice is fun!
Anonymous
September 2 2005, 00:52:57 UTC 6 years ago
September 2 2005, 00:53:35 UTC 6 years ago