This is exactly the sort of thing that Manditory Access Controls is supposed to take care of. All of the work that has gone into SELinux by the NSA and others is just starting to pay off. I won't be so bold as to say Linux will have complete immunity from these types of attacks and rootkits, but it is a long way ahead of Windows.
If you want to know more about detecting kernel rootkits and cryptograhpically signed kernel modules, check out this
paper by Dino Dai Zovi.
Take a look at Fog Creek Software'sFogBugz. Its usage paradigm is a little different than bugzilla, but a lot of people swear by it. It's well supported and designed to work on Windows, so it shouldn't be too much of a headache to get running.
Just grab a computer and stick 3 video cards in it. Configure X to run multihead and then use mplayer or xine or totem to send the videos to your 3 monitors. If you want to be really cool, you could use gstreamer to build a custom app pretty quickly that sent 3 separate video streams to 3 different monitors and kept everything synchronized with a single point of control.
1800 spams in almost 2 months?! Man, you are a lightweight. I've received over 15,000 spams in that time. You might as well forget the filter cause, brother, you barely need it.
(And just for the record, I've had 13 false negatives and zero false positives in that same interval using dspam)
Probably no one remembers this, but there was a project called Medusa in development 4 or 5 years ago by Rebecca Schulman and the other happy hackers over at Eazel. It had some awsome indexing technology but a lot of people eyed it suspiciously because it was somethnig of a resource hog, espceially for its day. Probably, these days no one would flinch at dropping that kind of RAM on something like this. Unfortunately, after Eazel crashed and burned, Medusa was heaped on the pile dead carcases of so many other free software projects that line the road to software Nirvana. It's good that this functionality will finally be come to fruition with projects like Storage and DBFS, but I always thought that had Medusa been saved, we might already have a mature document indexing system by now.
WordPerfect 8 wasn't the first version released for linux. I have a version of WP 6.0 thats dated April 3, 1996. I guess that makes tomorrow the 8 year anniversary of WP on Linux. It was distributed on the Caldera Internet Office Suite along with the NExS spreadsheet and ZMail. The CIOS was the companion CD to The Caldera Network Desktop v 1.0, the first linux distro that bright eyed Linux start-up Caldera (now SCO) put forth.
But all that is ancient history now. How things have changed in the last 8 years.
I have seen locks based on this routing idea before, although using electrical connections rather than optical ones. The one saw had 16 paths, which is much more secure, as the number of unique keys is the number of paths factorial. 6! is only 720 keys, which you could imagine having a sack of and trying each one in a matter of minutes. 16 paths gives you 20 Trillion unique keys, which is going to be one freaking heavy sack. Also, optical fibers are very fragile in real world environments, where as electrical connections can jingle jangle in your pocket all day long and still be functional. I'd give this high marks for "cool" but not for "useful."
I find Card's description of the old copyright system troubling. He says that the old system was bad because it only granted a monopoly for 52 years before the the work fell into the public domain and whines that he or his descendants might not die before that happened. This is ridiculous. The section of the Constitution (Article I, Section 8) that gives congress permission to create copyright law says that the purpose is to encourage "progress in science and the useful arts." Nowhere does is say anything about providing a welfare system for authors who get lazy and squander their earnings and their nidhoggic progeny.
If your dad was a plumber, would you expect that a leaky pipe he fixed 50 years ago would buy you a new house today? Why should copyright holders and their descendants be any different. If authors plan on maintaining a lifestyle after they get older, they should get a 401k like everyone else.
The framers decided that 14 years, extensible to 28 was long enough to encourage authors to keep science and the arts progressing, while still keeping the public domain well stocked with good material so that other authors could do their bit to advance science and the useful arts. The system enacted by Congress in 1978, and more recently with the Sonny Bono Copyright term extension act is so unbalanced that not only is it unconstitutional, its stagnating the intellectual development of our society.
You can't save it till you need it
on
Qt On DirectFB
·
· Score: 2, Interesting
The idea of saving the network abstraction layer of X "till you NEED it" is flawed. If we design all of our applications without it, then when the occasion comes up (for some it may be rare, but I use it every day) it will be too much trouble to retrofit those applications to have X support. But if you assume X all the time, then you can gaurantee it'll be there when you need it.
If you are worried about interface responsiveness, there are plenty of things that are being done to address that without giving up the X paradigm, such as the X DRI extensions, and X server hardware support (its difficult enough to get NVIDIA and ATI's support for X, do you think they'll want to bother with 2 totally different unix graphic drivers?), and my personal favorite, the preemptable kernel (woohoo, Linux 2.6! (3.0?)).
Of Course CS Ph.D.s are just the opposite
on
Computing's Lost Allure
·
· Score: 5, Interesting
The other side of the coin that Computer Science graduate admissions are inundated with applicants this year. Hordes of people, after getting a bachelor's degree a few years ago, went off to industry to get rich instead of persuing advanced degrees. Now that the market has cooled off, many of them are returning to graduate school. It sucks to be a recent graduate trying to get into CS grad school, because you have to compete with many more applicants for the same few slots.
I'm a physicist who specailizes in Quantum Information, so I've read just about every quantum book out there. I would have to agree that it is the all around top cookie in the arena of intro into quantum mechanics books. However, for exactly the reasons that physicists like myself like it, people just getting into quantum mechanics may not.
Quantum Mechanics is a Taoist precept in a way, where only understanding brings understanding.
I think that Griffiths is at its best when you already have some understanding to work with. To bootstrap your self into that place, I would recomend "Quantum Physics" by Stephen Gasiorowicz. Its more compact than Griffiths and so it may be easier to get a big picture view of what Quantum Physics is all about.
I would like to thank Chairman Powell, who discented to the majority opinion with rather strong language. If you read the opinions from all five commissioners it becomes obvious that Powell is the only one with a seat on the clue train. Commissioner Adelstein spends most of the brief talking about how late they all stayed up, and how this was his first decision as a new Commissioner, rather than the merits of the Mojority Opinion.
Powell suggests that the Majority Opinion is in dire legal peril since it is almost exactly like the previous telco rulemaking proposal which was swatted down by the supreme court. For them to pass the same, obviously flawed, argument all over again is idiotic.
Powell must be saying to himself: "I am surrounded by fools and peasants."
Several posters have stated that the position of the center of gravity doesn't matter. I respectfully must disagree. Since the car begins on an incline and ends horizontal, the higher your center of gravity at the begining, the more potential energy you have to work with, and the faster your car goes. You make the CG higher by putting the weight in the back of the car.
I not only know this because I am a career physicist, but because when I was in the scounts many years ago, I built my own test track with an integrated electronic timing system in my back yard and built an array of cars to empirically determine the best design, and I have several pack and state derby championship trophies to show for it. The sweet spot is to have the CG between the rear axle and about 1cm forward from that place. If the CG gets behind the rear axle the car becomes unstable and you'll waste energy on friction between the insides of the wheels and the guide strip that the cars run on.
The best way, as opposed to drilling holes and filling them with lead shot, is to sand cast the rear portion of the car out of molten lead. Use of an oxy-acetylene torch to melt lead and make precision casts may be beyond the reach of most cub scouts. I was fortunate enough to have a dad who thought welding was a very important skill to have and taught me at a very early age.
It kind of makes you wonder what would have happened if DEC had accepted Apple's offer to base PowerMacs on the alpha. Back when Apple was getting ready to leave the venerable M68040 series of chips, it approached DEC and said it wanted to make a deal with them to produce alphas for Macs. The CEO of DEC said no, because he wanted to focus the companies efforts on extending the life of VAX/VMS for one more generation, and getting involved with Apple would be a distraction. Of course, he was fired shortly there after for being a knucklehead, but by then it was too late. Apple had teamed up with Motorola and IBM to develop the PowerPC architecture. Still, you gotta wonder what would have happened if he had had a clue and played with Apple.
There is another reason why this might work that people seem to be overlooking. Although the lava is very hot, pumice has an etremely low heat conductivity, which means it can't transfer heat very quickly. Even though the bird is in contact with it, the rock can't dump heat into it fast enough to cook it quickly.
NASA builds space shuttles and covers them with ceramic tiles to prevent them from burning up on reentry. The tiles that they use are physically almost identical to the pumice found in a volcanoe.
If its works for the space shuttle, its going to work for you hen as well.
You can use gnome-terminal with the --use-factory option. It makes one process for all your terms, so if you have a lot of windows open, it doesn't use that much memory.
Here is a full course that I found on the web, coincidently earlier this morning, while I was searching for something completely different. It is designed with an eye towards scheme, because scheme has the simplest syntax there is, although its contents can be applied to any language. It has lessons and an on-line text, examples and problems. It has the multi-platform scheme interpreter DrScheme which can be used to run all the examples and problem sets.
I'm not sure how all of this stacks up to SICP since I just found this one this morning. I can't say enough good things about SICP (It is how I really learned to think about software), but neither can a lot of other posters, so I figure I don't have to. This program is directed at a conceptual level and it looks like this course might be a worthwhile comparison.
I am very worried about the fax component of this. If you sign a document and then fax it somewhere, the person recieving the fax can't validate the signature. Digital signatures gaurantee that the document is bit-perfect, and the process of encoding an image into a fax transmission is substantially less than bit-perfect. So if the recipient can't verify the signatures becasue you are transmitting them in a lossy way, it doesn't seem like there is much point in signing them in the first place.
Etch-A-Sketch Animator
on
PDAs For Kids
·
· Score: 2, Informative
Etch-A-Sketch made something just like this back in the 80's. It was called the Etch-A-Sketch Animator and as I recall, it sucked. Maybe they've got something better here, but I feel that for my money, you can't beat a tablet of paper and a 64 pack of Crayolas.
The argument that MS is making here is essentially "our right to innovate must be protected at the expense of everyone else's." Since Microsoft is always trumpeting the 'right to innovate' unencumbered, then logically they should recognize that if another company innovates something better than a start button, for instance, then that company should have the right to implement it with out Microsoft interfering. If a third party introduces a modification that users find confusing, then people won't buy it. People don't need Microsoft to tell them what they find confusing. Let free market forces determine what innovative features be included, no matter where they come form.
But logic and consistency seem to be beyond these hypocrites. They are only interested in protecting the 'freedom to innovate' and allowing a free market when the deck is stacked in their favor. Everyone else's freedom to innovate be damned.
I think that this problem would be better solved not by a new filesystem, which means implementing a new kernel module for what is essentially a file symantics problem, but by a module to Nautilus, or whatever your favorite filebrowser is, that looks for ID3 tags and displays those.
If you do it at the FS level, you would also have to rewrite things like ls and change the way the stat ioctl works, which would break the posix compliance OS. In short, you'd have to modify a ton of stuff just to get id3 tags to display, not to mention that once you got it all working, you'd have to track the development of all the newest FS features like journaling because people are going to want all that stuff to store their mp3s too.
It would be much easier just to have your filebrowser do it for you, and let the filesystem do its job: store files.
Different labs at MIT find their inspiration from different sources. I should know, I've worked for 3 different research groups at MIT, one of which was the intelligent graphics group at the Media Lab. Places like the AI lab are mostly driven by the professors who have built their careers there. But the Media Lab is of a different sort. It is totally driven by the students. With few exceptions (Neil Gershenfeld's Physics and Media group being one) most research groups in the Media Lab are propelled by students. Undergrads cook up all the crasy projects, they hack together all the pieces, they write all the code. The reason is that most of the staffers who work there are not engineers, they are artist types who like to reflect on the social ramifications of how great their projects are, but never really get much done. They hire genius undergrad engineers to come and bulid everything, and produce much of the fantastic gadgets that the Media Lab is famous for.
I find it amusing that they use the phrase "reserve the right" to ask people to remove links to their site in their policy. You can't reserve a right that you never had in the first place. What they really should say is:
We made up the right to ask people to take away links to our site.
Slashdot Mirror
If you want to know more about detecting kernel rootkits and cryptograhpically signed kernel modules, check out this paper by Dino Dai Zovi.
Take a look at Fog Creek Software's FogBugz. Its usage paradigm is a little different than bugzilla, but a lot of people swear by it. It's well supported and designed to work on Windows, so it shouldn't be too much of a headache to get running.
Just grab a computer and stick 3 video cards in it. Configure X to run multihead and then use mplayer or xine or totem to send the videos to your 3 monitors. If you want to be really cool, you could use gstreamer to build a custom app pretty quickly that sent 3 separate video streams to 3 different monitors and kept everything synchronized with a single point of control.
(And just for the record, I've had 13 false negatives and zero false positives in that same interval using dspam)
Probably no one remembers this, but there was a project called Medusa in development 4 or 5 years ago by Rebecca Schulman and the other happy hackers over at Eazel. It had some awsome indexing technology but a lot of people eyed it suspiciously because it was somethnig of a resource hog, espceially for its day. Probably, these days no one would flinch at dropping that kind of RAM on something like this. Unfortunately, after Eazel crashed and burned, Medusa was heaped on the pile dead carcases of so many other free software projects that line the road to software Nirvana. It's good that this functionality will finally be come to fruition with projects like Storage and DBFS, but I always thought that had Medusa been saved, we might already have a mature document indexing system by now.
Alas, alack.
WordPerfect 8 wasn't the first version released for linux. I have a version of WP 6.0 thats dated April 3, 1996. I guess that makes tomorrow the 8 year anniversary of WP on Linux. It was distributed on the Caldera Internet Office Suite along with the NExS spreadsheet and ZMail. The CIOS was the companion CD to The Caldera Network Desktop v 1.0, the first linux distro that bright eyed Linux start-up Caldera (now SCO) put forth.
But all that is ancient history now. How things have changed in the last 8 years.
I have seen locks based on this routing idea before, although using electrical connections rather than optical ones. The one saw had 16 paths, which is much more secure, as the number of unique keys is the number of paths factorial. 6! is only 720 keys, which you could imagine having a sack of and trying each one in a matter of minutes. 16 paths gives you 20 Trillion unique keys, which is going to be one freaking heavy sack. Also, optical fibers are very fragile in real world environments, where as electrical connections can jingle jangle in your pocket all day long and still be functional. I'd give this high marks for "cool" but not for "useful."
Take the 6 nuggets and throw 2 of them away. I'm jus t wanting the 4 nugget thing.
I'm trying to watch my calorie intake.
I find Card's description of the old copyright system troubling. He says that the old system was bad because it only granted a monopoly for 52 years before the the work fell into the public domain and whines that he or his descendants might not die before that happened. This is ridiculous. The section of the Constitution (Article I, Section 8) that gives congress permission to create copyright law says that the purpose is to encourage "progress in science and the useful arts." Nowhere does is say anything about providing a welfare system for authors who get lazy and squander their earnings and their nidhoggic progeny.
If your dad was a plumber, would you expect that a leaky pipe he fixed 50 years ago would buy you a new house today? Why should copyright holders and their descendants be any different. If authors plan on maintaining a lifestyle after they get older, they should get a 401k like everyone else.
The framers decided that 14 years, extensible to 28 was long enough to encourage authors to keep science and the arts progressing, while still keeping the public domain well stocked with good material so that other authors could do their bit to advance science and the useful arts. The system enacted by Congress in 1978, and more recently with the Sonny Bono Copyright term extension act is so unbalanced that not only is it unconstitutional, its stagnating the intellectual development of our society.
The idea of saving the network abstraction layer of X "till you NEED it" is flawed. If we design all of our applications without it, then when the occasion comes up (for some it may be rare, but I use it every day) it will be too much trouble to retrofit those applications to have X support. But if you assume X all the time, then you can gaurantee it'll be there when you need it.
If you are worried about interface responsiveness, there are plenty of things that are being done to address that without giving up the X paradigm, such as the X DRI extensions, and X server hardware support (its difficult enough to get NVIDIA and ATI's support for X, do you think they'll want to bother with 2 totally different unix graphic drivers?), and my personal favorite, the preemptable kernel (woohoo, Linux 2.6! (3.0?)).
The other side of the coin that Computer Science graduate admissions are inundated with applicants this year. Hordes of people, after getting a bachelor's degree a few years ago, went off to industry to get rich instead of persuing advanced degrees. Now that the market has cooled off, many of them are returning to graduate school. It sucks to be a recent graduate trying to get into CS grad school, because you have to compete with many more applicants for the same few slots.
I'm a physicist who specailizes in Quantum Information, so I've read just about every quantum book out there. I would have to agree that it is the all around top cookie in the arena of intro into quantum mechanics books. However, for exactly the reasons that physicists like myself like it, people just getting into quantum mechanics may not.
Quantum Mechanics is a Taoist precept in a way, where only understanding brings understanding.
I think that Griffiths is at its best when you already have some understanding to work with. To bootstrap your self into that place, I would recomend "Quantum Physics" by Stephen Gasiorowicz. Its more compact than Griffiths and so it may be easier to get a big picture view of what Quantum Physics is all about.
I would like to thank Chairman Powell, who discented to the majority opinion with rather strong language. If you read the opinions from all five commissioners it becomes obvious that Powell is the only one with a seat on the clue train. Commissioner Adelstein spends most of the brief talking about how late they all stayed up, and how this was his first decision as a new Commissioner, rather than the merits of the Mojority Opinion.
Powell suggests that the Majority Opinion is in dire legal peril since it is almost exactly like the previous telco rulemaking proposal which was swatted down by the supreme court. For them to pass the same, obviously flawed, argument all over again is idiotic.
Powell must be saying to himself: "I am surrounded by fools and peasants."
Several posters have stated that the position of the center of gravity doesn't matter. I respectfully must disagree. Since the car begins on an incline and ends horizontal, the higher your center of gravity at the begining, the more potential energy you have to work with, and the faster your car goes. You make the CG higher by putting the weight in the back of the car.
I not only know this because I am a career physicist, but because when I was in the scounts many years ago, I built my own test track with an integrated electronic timing system in my back yard and built an array of cars to empirically determine the best design, and I have several pack and state derby championship trophies to show for it. The sweet spot is to have the CG between the rear axle and about 1cm forward from that place. If the CG gets behind the rear axle the car becomes unstable and you'll waste energy on friction between the insides of the wheels and the guide strip that the cars run on.
The best way, as opposed to drilling holes and filling them with lead shot, is to sand cast the rear portion of the car out of molten lead. Use of an oxy-acetylene torch to melt lead and make precision casts may be beyond the reach of most cub scouts. I was fortunate enough to have a dad who thought welding was a very important skill to have and taught me at a very early age.
Anyway, best of luck to you.
How about a sign that says:
SETEC ASTRONOMY
It kind of makes you wonder what would have happened if DEC had accepted Apple's offer to base PowerMacs on the alpha. Back when Apple was getting ready to leave the venerable M68040 series of chips, it approached DEC and said it wanted to make a deal with them to produce alphas for Macs. The CEO of DEC said no, because he wanted to focus the companies efforts on extending the life of VAX/VMS for one more generation, and getting involved with Apple would be a distraction. Of course, he was fired shortly there after for being a knucklehead, but by then it was too late. Apple had teamed up with Motorola and IBM to develop the PowerPC architecture. Still, you gotta wonder what would have happened if he had had a clue and played with Apple.
There is another reason why this might work that people seem to be overlooking. Although the lava is very hot, pumice has an etremely low heat conductivity, which means it can't transfer heat very quickly. Even though the bird is in contact with it, the rock can't dump heat into it fast enough to cook it quickly.
NASA builds space shuttles and covers them with ceramic tiles to prevent them from burning up on reentry. The tiles that they use are physically almost identical to the pumice found in a volcanoe.
If its works for the space shuttle, its going to work for you hen as well.
You can use gnome-terminal with the --use-factory option. It makes one process for all your terms, so if you have a lot of windows open, it doesn't use that much memory.
I'm not sure how all of this stacks up to SICP since I just found this one this morning. I can't say enough good things about SICP (It is how I really learned to think about software), but neither can a lot of other posters, so I figure I don't have to. This program is directed at a conceptual level and it looks like this course might be a worthwhile comparison.
The link is here
I am very worried about the fax component of this. If you sign a document and then fax it somewhere, the person recieving the fax can't validate the signature. Digital signatures gaurantee that the document is bit-perfect, and the process of encoding an image into a fax transmission is substantially less than bit-perfect. So if the recipient can't verify the signatures becasue you are transmitting them in a lossy way, it doesn't seem like there is much point in signing them in the first place.
Etch-A-Sketch made something just like this back in the 80's. It was called the Etch-A-Sketch Animator and as I recall, it sucked. Maybe they've got something better here, but I feel that for my money, you can't beat a tablet of paper and a 64 pack of Crayolas.
The argument that MS is making here is essentially "our right to innovate must be protected at the expense of everyone else's." Since Microsoft is always trumpeting the 'right to innovate' unencumbered, then logically they should recognize that if another company innovates something better than a start button, for instance, then that company should have the right to implement it with out Microsoft interfering. If a third party introduces a modification that users find confusing, then people won't buy it. People don't need Microsoft to tell them what they find confusing. Let free market forces determine what innovative features be included, no matter where they come form.
But logic and consistency seem to be beyond these hypocrites. They are only interested in protecting the 'freedom to innovate' and allowing a free market when the deck is stacked in their favor. Everyone else's freedom to innovate be damned.
I think that this problem would be better solved not by a new filesystem, which means implementing a new kernel module for what is essentially a file symantics problem, but by a module to Nautilus, or whatever your favorite filebrowser is, that looks for ID3 tags and displays those.
If you do it at the FS level, you would also have to rewrite things like ls and change the way the stat ioctl works, which would break the posix compliance OS. In short, you'd have to modify a ton of stuff just to get id3 tags to display, not to mention that once you got it all working, you'd have to track the development of all the newest FS features like journaling because people are going to want all that stuff to store their mp3s too.
It would be much easier just to have your filebrowser do it for you, and let the filesystem do its job: store files.
Different labs at MIT find their inspiration from different sources. I should know, I've worked for 3 different research groups at MIT, one of which was the intelligent graphics group at the Media Lab. Places like the AI lab are mostly driven by the professors who have built their careers there. But the Media Lab is of a different sort. It is totally driven by the students. With few exceptions (Neil Gershenfeld's Physics and Media group being one) most research groups in the Media Lab are propelled by students. Undergrads cook up all the crasy projects, they hack together all the pieces, they write all the code. The reason is that most of the staffers who work there are not engineers, they are artist types who like to reflect on the social ramifications of how great their projects are, but never really get much done. They hire genius undergrad engineers to come and bulid everything, and produce much of the fantastic gadgets that the Media Lab is famous for.
We made up the right to ask people to take away links to our site.