I just ported my own OS kernel (davros) to the MSP430. Mostly quick & easy - a couple of quirks in the I/O area, but that's normal on nearly all microcontrollers.
I expect to upload the source to my homepage in the next few days:
home.graffiti.net/pogue/downloads/davros/
(but don't bother looking just yet, unless you want x86 and/or tricore)
The main problem is not stopping your code from being overwritten, but stopping your data from being executed. Many (most? all?) buffer overrun expliots use the fact that arbitrary data can be written to the stack. So you overwrite the return address to make it return to somewhere in the stack, which you've also overwritten to contain a short stub program that lets the main exploit in.
Of course, real processors (powerpc, sparc etc.) have had this feature for years.
Europeans who cherish their freedoms should be boycotting Nokia, since it appears that their lobbying activities are primarily responsible for the European Commission's current attempts to override Parliament on the software patents directive.
... there's a slightly dented unmanned probe with a small LCD screen displaying the message "Do you really want to deploy the airbags? [Yes] [No]".
Theyr'e sending someone up to click one of the buttons.
Many natural languages have case-sensitivity too - German, for example: fliegen (verb) and Fliegen (noun) are different words.
But why a big list of reasons FOR case-insensitivity?
IMHO the question should be turned around to "Why should anyone want case-insensitivity in a language?" (since, as you say, it has to be put there and requires more work in the part of the compiler and/or the compiler writer).
Then it is up to those who want case-insensitivity to argue their case against the simplest implementation.
As a fully paid-up member of the Pirates, Buccaneers and Allied Trades union, I object you labelling these P2P users as Pirates. Demarcation, that is. You're not allowed to be called a Pirate until you've served a full 5-year apprenticeship as a cabin-boy, learned to say "Yo ho ho and a bottle of rum" without falling over, and are able to find the stolen treasure thet you buried after consuming said rum, using only a very crude map that you don't even remember drawing.
Pesky blighters have probably never even *seen* a
rottle of bum... bobble of tum... blubble blumblo..... [distant crash]
The bugs might be cheaper to fix, but they cost a lot more to find.
At any stage, you can only find bugs that are introduced at or before that stage. So while fixing a requirements bug in the coding phase might be more expensive than fixing it during the requirements phase, fixing a coding bug during the requirements phase is a tricky operation that I'll leave as an exercise for the reader:-)
Of course, if you omit some of these phases completely, you won't introduce any bugs during them. That's why the JFDI(*) methodoloy is so popular.
Also, last time I checked (like: just now), you were able to download a copy of the supposedly offending kernel from SCO's own ftp server and use and/or distribute it under the GPL.
Close, but not quite. Without the equalisation curve, the sound would contain a lot of noise caused by the naturally slightly rough surface of the vinyl. To overcome this, the higher frequencies are boosted on the recording and then attenuated again on playback. By attenuating the higher frequencies the level of noise is reduced to an acceptable level.
The RIAA set the standard back in the 50s or somewhen for its members to follow when making the recordings. As far as I can tell, it is the last good thing they did.
Dolby-B and DBX do similar tricks to improve the s/n ratio of audio tape.
I could add that the reason that most successful hacks are of systems running Linux is because the hackers' ham-fisted attempts to crack application interfaces on a W*dows box will usually take down the OS.
But I won't;-)
Slashdot Mirror
I expect to upload the source to my homepage in the next few days:
home.graffiti.net/pogue/downloads/davros/
(but don't bother looking just yet, unless you want x86 and/or tricore)
Of course, real processors (powerpc, sparc etc.) have had this feature for years.
Europeans who cherish their freedoms should be boycotting Nokia, since it appears that their lobbying activities are primarily responsible for the European Commission's current attempts to override Parliament on the software patents directive.
Litter bug. It should be neatly crumpled up and dropped into the nearest convenient litter bin.
I can count up to 1023 on my fingers :-)
Spirit grinds Adirondack, looks for iron
It's right there in the middle, between Ad and dack. Silly of it not to spot that right away ;-)
In my experience, servers go up & down all the time.
... there's a slightly dented unmanned probe with a small LCD screen displaying the message "Do you really want to deploy the airbags? [Yes] [No]". Theyr'e sending someone up to click one of the buttons.
The memory bus of the 8088 was also 8-bit. But internally it was the same as the 8086.
But why a big list of reasons FOR case-insensitivity?
IMHO the question should be turned around to "Why should anyone want case-insensitivity in a language?" (since, as you say, it has to be put there and requires more work in the part of the compiler and/or the compiler writer).
Then it is up to those who want case-insensitivity to argue their case against the simplest implementation.
I've been religiously circumventing copy protection devices for quite a while now.
So, you reckon you can identify HM the Q from that silhouette on the stamps?
I'll bet HM the Q (or K perhaps by then) won't be carrying an id card.
It wouldn't be named after Gene Amdahl now, would it?
Try to export it to other countries?
Pesky blighters have probably never even *seen* a rottle of bum ... bobble of tum ... blubble blumblo ..... [distant crash]
"Thou shalt not download"
I think those must have been on the tablet that Moses dropped ... can't seem to find them in the Good Bok anywhere. ;-)
s/Thigs/Things/
s/methodoloy/methodology/
Oh, and I saw JFDI originally in an article in Computer Weekly, I think. It's also here
At any stage, you can only find bugs that are introduced at or before that stage. So while fixing a requirements bug in the coding phase might be more expensive than fixing it during the requirements phase, fixing a coding bug during the requirements phase is a tricky operation that I'll leave as an exercise for the reader :-)
Of course, if you omit some of these phases completely, you won't introduce any bugs during them. That's why the JFDI(*) methodoloy is so popular.
(*)Just F*cking Do It
"Hot" being the operative word, presumably. If it wasn't before, it will be afterwards ;-)
Simple. The internet stations in question don't play *that* kind of music.
The RIAA set the standard back in the 50s or somewhen for its members to follow when making the recordings. As far as I can tell, it is the last good thing they did.
Dolby-B and DBX do similar tricks to improve the s/n ratio of audio tape.
(Fake Yorkshire accent)
Right.
When I were a lad, our firewall were a shoebox in t' middle o' t' information superhighway.
And you tell t' young people o' today that, an' they won't believe you.
I could add that the reason that most successful hacks are of systems running Linux is because the hackers' ham-fisted attempts to crack application interfaces on a W*dows box will usually take down the OS. But I won't ;-)