1. In the Smithsonian institution, there is a lovely display of the dresses worn on inauguaration day. The fancy inaugeration dress is a major part of tradition here in the USA. (might as well be in the Constitution) I'm dying to see Bill in a dress.
2. Inquiring minds want to know: will the interns be male? What services will they perform?
As far as activity software is concerned, the resolution is always 1200x900. It's always 16-bit color. (5 red, 6 green, 5 blue)
In color mode, the display is purposely blurred to avoid color fringes. One could say that the result is roughly as good as 600x450 to 800x600. You get better effective resolution in a lower-left to upper-right direction than you do in an upper-left to lower-right direction.
In greyscale mode, a weighted average of the color values is done to make grey pixels. The framebuffer is still 16-bit color, but you can't see the color.
Black gets unevenly hot in the sun. It's really a stupid color. Pure white makes sense, but...
What we really need is pink. Lots of women adore the little laptop. It fits in a purse. Unfortunately, it's not pink. Seriously. It matters for many women.
Lavender and purple are also nice. One could have several shades of pink.
It has always been that you must work your ass off to climb out of poverty. Few poor people bother. They find time-wasting entertainment to consume their time, addictive substances to rot their often feeble minds, stupid toys to waste their money on, etc.
There are places in the world where you can't climb out of poverty. In the past, there were many more.
When there isn't much difference from one person to the next, any kid can easily grow up to have any job. The well-paid people aren't all that different from the low-paid people. Wealth-enhancing abilities like intelligence may be inheritable, but this barely matters because people are pretty much the same.
If people are really different from each other, then those differences will matter. Since people tend to marry others who are similar, and since wealth-enhancing abilities are inheritable, you get persistant classes of people.
Only draconian control over families could change this. We'd have to purposely breed the stupid people with the bright people.
Glass platters look just like aluminum ones. It's hard to tell the difference until they break. When they do break, zillions of ultra-sharp slivers of glass go flying everywhere. It's way worse than breaking typical glass.
Now, don't get me wrong. I think that's a really cool hack. I admire the effort.
Seriously though, WTF? That's a rootkit technique. Changes of this nature should be made to source code, not binaries. It's way more maintainable and sustainable that way.
For example, we could prohibit airlines from screwing with sleep patterns. If a guy sleeps from 8 AM to 4 PM, you don't suddenly switch him over to sleeping from 4 PM to midnight. Well, you don't do that unless you are an airline or a hospital!
You could scrape the top of the arm with a file. Scrape very near the pole, but not right above the little brace. Go deep enough to get through any galvanization or other rust-resistant coating. Optionally, wrap some salty gauze around it, or apply a gel that collects water. Such gel can be found in feminine napkins and disposable diapers.
HERF stuff need not be a gun. Walk right by, hold up a coil, and discharge away.
A cattle prod should do nicely.
Get a buddy. Put on reflective vests. Go out during working hours with a dremmel tool and just take the thing down! For bonus points, place cones on the road.
A tow chain might do nicely. Just don't get the thing yanked up into the air and landing in your rear window.
Here in the USA of course we haven't been disarmed. A regular old shotgun or hunting rifle would do nicely. Rifled slugs are fun.
That could be a big problem, commonly a denial-of-service.
Suppose the app takes a lock (or similar) which requires privilege. This succeeds. The app then does something else which requires privilage, and fails.
If the app dies at this point, things are stuck. Hopefully a reboot can clear the problem. Depending on the nature of the app, you may well have database corruption.
BTW, maybe I shouldn't have referred to the first case as sloppy programming. It's perfectly legit on a traditional system that lacks the fancy new features. The resulting security problem has actually happened, with sendmail on Linux.
Channels can be split about 4 ways, giving multiple low-quality signals. Thus, instead of 500 lame channels, we may see 2000 lame channels. Already I'm seeing "digital cable" that looks way worse than analog, including many over-the-air NTSC transmissions. Note that this means there was no good reason to increase the resolution. Going to 480p, with the option for alternate frame rates, would have been sensible however.
Analog shutdown is a myth. Congress will stop it every time. Nothing makes people riot like the loss of their TV.
We could have switched over if we'd simply permitted digital on the analog channels, then slowly reduced the hours of analog service permitted per day. Pretty soon the stations would transmit digital instead of going off the air for a few hours during the night, people would see the need to get digital without being immediatly 100% pissed off, and before long we'd be done.
This stuff is MPEG2. Eeeew. After 50 years, more if you count non-color TV, waiting an extra decade wouldn't have killed us. Wavelet-based compression would be nice. Heck, even just MPEG4 would be nice.
Oh, I know all that. I'm not giving up my curly braces. You can pry them from my cold dead hands.
To a large degree, humans are visual pattern matching engines. When I look at normal code, each different language construct has a different sort of feel to it. Usually a variable declaration looks nothing like a loop, etc.
LISP breaks all that. It doesn't let me take advantage of my human abilities. It forces me to deal with raw naked trees. That's a brutal productivity hit.
BTW, there are other things I hate about LISP, but those are shared with everything from python to perl. I don't wish for my programs to drag along a whole damn compiler or interpreter as needed for "eval" functionality, I like being able to make system calls without having to beg a language vendor to support them, I like my inline assembly language, and I can damn well take out my own garbage.
Lots of programs try to limit themselves when run as setuid root. For example, they refuse some kind of user input. If they see that they are NOT running setuid root, then they assume that they have no privilage and that thus there is no need to limit themselves.
Other programs assume that if ONE privileged operation succeeds, then some OTHER privileged operation will also succeed. (because root can traditionally do everything) When that other operation fails unexpectedly, you may get some sort of inconsistant state. Inconsistant state is the playground of an attacker.
With this new feature, both sorts of sloppy programming become security holes.
Years ago, we swiped the idea from SGI's Irix. They seem to have swiped it from Data General's DG-UX.
We implemented everything but the filesystem support. Filesystem support is complicated. It's actually SE Linux that has driven our ability to put arbitrary security markings on files, along with non-security desires for various extended attribute and multi-fork things.
Unfortunately the set of bits was nearly copied from SGI's Irix, where it was botched. The bit choice is inflexible, redundant, and rather small. See, there's this "admin" bit that controls nearly everything...
SGI also botched the math. Well, to excuse them a bit, the POSIX draft (never ratified) went through dramatic changes to the equations a few times.
Really we ought to rip out the trash and clone what Sun has, but that is terribly hard for compatibility. Some programs already deal with the capabilitites. For example, I think sendmail drops capability bits.
Slashdot Mirror
1. In the Smithsonian institution, there is a lovely display of the dresses worn on inauguaration day. The fancy inaugeration dress is a major part of tradition here in the USA. (might as well be in the Constitution) I'm dying to see Bill in a dress.
2. Inquiring minds want to know: will the interns be male? What services will they perform?
States aren't rejecting this for privacy. It's the money to change crufty old non-relational database code. Go COBOL!!!
Sure. Your "shoulder" or "arm". Riiiigh...
<0)
( \
X
8====D
Not that there's anything wrong with owning a p3n15 b1rd.
http://smoke.rotten.com/bird/ouch.jpg
If she leaves blood at the scene, prove innocence with a cheek swab.
If she leaves anything else, prove innocence with a blood test.
As far as activity software is concerned, the resolution is always 1200x900. It's always 16-bit color. (5 red, 6 green, 5 blue)
In color mode, the display is purposely blurred to avoid color fringes. One could say that the result is roughly as good as 600x450 to 800x600. You get better effective resolution in a lower-left to upper-right direction than you do in an upper-left to lower-right direction.
In greyscale mode, a weighted average of the color values is done to make grey pixels. The framebuffer is still 16-bit color, but you can't see the color.
Black gets unevenly hot in the sun. It's really a stupid color. Pure white makes sense, but...
What we really need is pink. Lots of women adore the little laptop. It fits in a purse. Unfortunately, it's not pink. Seriously. It matters for many women.
Lavender and purple are also nice. One could have several shades of pink.
It has always been that you must work your ass off to climb out of poverty. Few poor people bother. They find time-wasting entertainment to consume their time, addictive substances to rot their often feeble minds, stupid toys to waste their money on, etc.
There are places in the world where you can't climb out of poverty. In the past, there were many more.
When there isn't much difference from one person to the next, any kid can easily grow up to have any job. The well-paid people aren't all that different from the low-paid people. Wealth-enhancing abilities like intelligence may be inheritable, but this barely matters because people are pretty much the same.
If people are really different from each other, then those differences will matter. Since people tend to marry others who are similar, and since wealth-enhancing abilities are inheritable, you get persistant classes of people.
Only draconian control over families could change this. We'd have to purposely breed the stupid people with the bright people.
Glass platters look just like aluminum ones. It's hard to tell the difference until they break. When they do break, zillions of ultra-sharp slivers of glass go flying everywhere. It's way worse than breaking typical glass.
The IBM Deathstar platters, I suppose rebranded to Hitachi now, are glass.
They don't have to care. They're the phone company.
Woah...
Now, don't get me wrong. I think that's a really cool hack. I admire the effort.
Seriously though, WTF? That's a rootkit technique. Changes of this nature should be made to source code, not binaries. It's way more maintainable and sustainable that way.
There was a guy in France who ate a whole bicycle. He powdered it and mixed it into his food for a year.
The laptop is RoHS-compliant, so you don't have to worry about toxic stuff like mercury and lead.
Just Eat It.
The FPU is terrible.
Maybe a PowerPC G4 would be tolerable.
There is a lot to be said for x86. It isn't pretty, but it has good code density and people have put a lot of effort into making good CPUs for it.
Proper CPU choice can avoid the infection. You'll want:
* huge virtually indexed virtually tagged caches with contexts
* big-endian
* 64-bit, with very slow 16-bit operations and very fast 64-bit operations
* unaligned memory accesses silently corrupt the destination (ignore low bits and/or use stale data on the bus)
* the MMU's dirty and accessed bits should be zSeries-style: physical rather than virtual, and accessed only via special instructions
* have DMA not be cache-coherent
* have an IOMMU. Give the PCI DMA a very limited window into memory, perhaps 64 MB, so that the IOMMU must be used.
For example, we could prohibit airlines from screwing with sleep patterns. If a guy sleeps from 8 AM to 4 PM, you don't suddenly switch him over to sleeping from 4 PM to midnight. Well, you don't do that unless you are an airline or a hospital!
sandpaper the lens
Use an automotive jack. Place it on the arm to lift off the box.
Paint is obvious. Tar may be better.
You could scrape the top of the arm with a file. Scrape very near the pole, but not right above the little brace. Go deep enough to get through any galvanization or other rust-resistant coating. Optionally, wrap some salty gauze around it, or apply a gel that collects water. Such gel can be found in feminine napkins and disposable diapers.
HERF stuff need not be a gun. Walk right by, hold up a coil, and discharge away.
A cattle prod should do nicely.
Get a buddy. Put on reflective vests. Go out during working hours with a dremmel tool and just take the thing down! For bonus points, place cones on the road.
A tow chain might do nicely. Just don't get the thing yanked up into the air and landing in your rear window.
Here in the USA of course we haven't been disarmed. A regular old shotgun or hunting rifle would do nicely. Rifled slugs are fun.
That could be a big problem, commonly a denial-of-service.
Suppose the app takes a lock (or similar) which requires privilege. This succeeds. The app then does something else which requires privilage, and fails.
If the app dies at this point, things are stuck. Hopefully a reboot can clear the problem. Depending on the nature of the app, you may well have database corruption.
BTW, maybe I shouldn't have referred to the first case as sloppy programming. It's perfectly legit on a traditional system that lacks the fancy new features. The resulting security problem has actually happened, with sendmail on Linux.
Channels can be split about 4 ways, giving multiple low-quality signals. Thus, instead of 500 lame channels, we may see 2000 lame channels. Already I'm seeing "digital cable" that looks way worse than analog, including many over-the-air NTSC transmissions. Note that this means there was no good reason to increase the resolution. Going to 480p, with the option for alternate frame rates, would have been sensible however.
Analog shutdown is a myth. Congress will stop it every time. Nothing makes people riot like the loss of their TV.
We could have switched over if we'd simply permitted digital on the analog channels, then slowly reduced the hours of analog service permitted per day. Pretty soon the stations would transmit digital instead of going off the air for a few hours during the night, people would see the need to get digital without being immediatly 100% pissed off, and before long we'd be done.
This stuff is MPEG2. Eeeew. After 50 years, more if you count non-color TV, waiting an extra decade wouldn't have killed us. Wavelet-based compression would be nice. Heck, even just MPEG4 would be nice.
Oh, I know all that. I'm not giving up my curly braces. You can pry them from my cold dead hands.
To a large degree, humans are visual pattern matching engines. When I look at normal code, each different language construct has a different sort of feel to it. Usually a variable declaration looks nothing like a loop, etc.
LISP breaks all that. It doesn't let me take advantage of my human abilities. It forces me to deal with raw naked trees. That's a brutal productivity hit.
BTW, there are other things I hate about LISP, but those are shared with everything from python to perl. I don't wish for my programs to drag along a whole damn compiler or interpreter as needed for "eval" functionality, I like being able to make system calls without having to beg a language vendor to support them, I like my inline assembly language, and I can damn well take out my own garbage.
Lots of programs try to limit themselves when run as setuid root. For example, they refuse some kind of user input. If they see that they are NOT running setuid root, then they assume that they have no privilage and that thus there is no need to limit themselves.
Other programs assume that if ONE privileged operation succeeds, then some OTHER privileged operation will also succeed. (because root can traditionally do everything) When that other operation fails unexpectedly, you may get some sort of inconsistant state. Inconsistant state is the playground of an attacker.
With this new feature, both sorts of sloppy programming become security holes.
Years ago, we swiped the idea from SGI's Irix. They seem to have swiped it from Data General's DG-UX.
We implemented everything but the filesystem support. Filesystem support is complicated. It's actually SE Linux that has driven our ability to put arbitrary security markings on files, along with non-security desires for various extended attribute and multi-fork things.
Unfortunately the set of bits was nearly copied from SGI's Irix, where it was botched. The bit choice is inflexible, redundant, and rather small. See, there's this "admin" bit that controls nearly everything...
SGI also botched the math. Well, to excuse them a bit, the POSIX draft (never ratified) went through dramatic changes to the equations a few times.
Really we ought to rip out the trash and clone what Sun has, but that is terribly hard for compatibility. Some programs already deal with the capabilitites. For example, I think sendmail drops capability bits.
I need some example code. Uh, for my research.