You are indirectly referring to the concept of executable management. The central idea here is to only allow trusted programs to run on the system. Under such a scheme the kernel would have a list of allowed programs (and libraries) complete with MD5 hashs etc. (to establish a chain of trust). When a program is executed the kernel would calculate it's MD5 sum (and sums for anything else that is loaded into memory) and the calculated sum isn't on the list then the program is not allowed to run. Under this scheme the users could "install" anything that they want on the system, but if it's not approved it doesn't run.
While a system like this would keep "bad" software from running on the system it is not a silver bullet (nothing ever will be), as someone will find ways around it. For example using an exploit in an allowed application that is already running.
There are also a couple of big limitations here, or with any system with the restrictions that you are asking about. First someone has to keep a list of the allowed applications, an update it regularly. This should be someone like the corporate IT department, it doesn't make sense to put the burdon on the OS vendor as you want the minimum set of applications on your systems and the OS vendor want the maximum set. Secondly this completely breaks software development, for obvious reasons.
I don't currently know of any operating system that implements these features.
The standard disclaimer about my not being a lawyer (or a citizen of the UK) applies here.
Read your service contract carefully, and if indeed it does say that the service provider may only update modems that they own, then they are in breach of contract, and you may be entitled to damages (depending on other clauses in the contract). This generally is easier to prove in court than the parent is suggesting.
Either way if you want to do something about it your best off to consult a lawyer
The base line machine is probably a high-end PC. As the article says, these applications take a large amount of RAM an disk space. The machine that the article is talking about is named Hammerhead and is a 108 processor alpha 833MHz Beowulf culster with 108GB of RAM distributed ove 27 nodes (so 4 prosessors and 4GB of RAM per node), with 2TB of disk. The other participationg unviersities are contributing similar resources. For more information on some of the resources being committed look at
The interesting question is how well will CISS actually work? The problem is being broken up and submitted in peices to each of the participating machines, however CISS does not have any higher priority than any other job (at least on SHARCNet) so how much time it will actually get is questionable, as these machines are fairly busy.
Same with Konqueror. this seems to be done in JavaScript So turning off Javascript fixes it, but it is still annoying
Re:What does NASA want?
on
Poor NASA
·
· Score: 2, Informative
Before we get too critical of NASA on the buget overruns, let's keep a few things in mind:
1. The source of many of the overruns is the two year delay in the launch of the service module (NASA had to keep its entire workforce for that whole time, which they didn't orignally buget for)
2. Many of the components of the space station are already bult and are sitting in a hanger in Florida waiting to be launched (maintaining them in this state costs a lot of money)
3. ISS since its inception has been the victim of the whims of many polititions.
While I'm not saying that NASA is a pisine organization with out inefficentcies, we should keep in mind that the buget overruns on ISS are not entirely NASA's fault.
I'm working on a super computing project up here in Canada, known as SHARC-Net. It is a group of Beowolf clusters (using Alpha's, with all the hardware supplied and serviced by Compaq) located at 3 different universities (as a side note 2 of the clusters run Linux and the other Tru-64). The project directors had a conference call with Compaq on Friday, for which they had to sign NDA's. When the Director for the University of Guelph came out of the conference call she was very unhappy with Compaq. She told us this:
1. Compaq will be announcing to the world what they discussed on Friday.
2. It won't effect us until 2004 (which agrees with the article).
3. Had they known about this earlier it could have effected their choice of supplier for the clusters.
This is very little to work with but it does agree with the article. Needless to say, may of Compaq's customers are very unhappy with them right now (including us as we are just now bringing these clusters online).
The Question here is, will BIND 9 be secure enough to be included in OpenBSD?
OpenBSD still uses BIND v4 due to the security issues with the later versions.
Actually the X-rays don't escape the black hole. the current theory is (since we have never actually "seen" a black hole) is that as particles fall in to the balck hole, they enter a sort of, spiraling, decaying orbit (called the accretion disk). It is the friction between all of these particles in the accretion disk, that generates the x-rays. If the x-ray is released in the right direction it can escape being sucked into the black hole, since the accretion disk exists outside of the black holes event horizon.
Slashdot Mirror
You are indirectly referring to the concept of executable management. The central idea here is to only allow trusted programs to run on the system. Under such a scheme the kernel would have a list of allowed programs (and libraries) complete with MD5 hashs etc. (to establish a chain of trust). When a program is executed the kernel would calculate it's MD5 sum (and sums for anything else that is loaded into memory) and the calculated sum isn't on the list then the program is not allowed to run. Under this scheme the users could "install" anything that they want on the system, but if it's not approved it doesn't run.
While a system like this would keep "bad" software from running on the system it is not a silver bullet (nothing ever will be), as someone will find ways around it. For example using an exploit in an allowed application that is already running.
There are also a couple of big limitations here, or with any system with the restrictions that you are asking about. First someone has to keep a list of the allowed applications, an update it regularly. This should be someone like the corporate IT department, it doesn't make sense to put the burdon on the OS vendor as you want the minimum set of applications on your systems and the OS vendor want the maximum set. Secondly this completely breaks software development, for obvious reasons.
I don't currently know of any operating system that implements these features.
Since when is WMA an open standard? The last time that I looked it was owned solely by Microsoft and jealously guarded by an army of lawyers.
The standard disclaimer about my not being a lawyer (or a citizen of the UK) applies here.
Read your service contract carefully, and if indeed it does say that the service provider may only update modems that they own, then they are in breach of contract, and you may be entitled to damages (depending on other clauses in the contract). This generally is easier to prove in court than the parent is suggesting.
Either way if you want to do something about it your best off to consult a lawyer
The base line machine is probably a high-end PC. As the article says, these applications take a large amount of RAM an disk space. The machine that the article is talking about is named Hammerhead and is a 108 processor alpha 833MHz Beowulf culster with 108GB of RAM distributed ove 27 nodes (so 4 prosessors and 4GB of RAM per node), with 2TB of disk. The other participationg unviersities are contributing similar resources. For more information on some of the resources being committed look at
p ://www.westgrid.ca
http://www.sharc-net.ca/Hardware/index.php
htt
The interesting question is how well will CISS actually work? The problem is being broken up and submitted in peices to each of the participating machines, however CISS does not have any higher priority than any other job (at least on SHARCNet) so how much time it will actually get is questionable, as these machines are fairly busy.
Same with Konqueror. this seems to be done in JavaScript
So turning off Javascript fixes it, but it is still annoying
Before we get too critical of NASA on the buget overruns, let's keep a few things in mind:
1. The source of many of the overruns is the two year delay in the launch of the service module (NASA had to keep its entire workforce for that whole time, which they didn't orignally buget for)
2. Many of the components of the space station are already bult and are sitting in a hanger in Florida waiting to be launched (maintaining them in this state costs a lot of money)
3. ISS since its inception has been the victim of the whims of many polititions.
While I'm not saying that NASA is a pisine organization with out inefficentcies, we should keep in mind that the buget overruns on ISS are not entirely NASA's fault.
in debian GNU/Linux the package is named msttcorefonts
I'm working on a super computing project up here in Canada, known as SHARC-Net. It is a group of Beowolf clusters (using Alpha's, with all the hardware supplied and serviced by Compaq) located at 3 different universities (as a side note 2 of the clusters run Linux and the other Tru-64). The project directors had a conference call with Compaq on Friday, for which they had to sign NDA's. When the Director for the University of Guelph came out of the conference call she was very unhappy with Compaq. She told us this:
1. Compaq will be announcing to the world what they discussed on Friday.
2. It won't effect us until 2004 (which agrees with the article).
3. Had they known about this earlier it could have effected their choice of supplier for the clusters.
This is very little to work with but it does agree with the article. Needless to say, may of Compaq's customers are very unhappy with them right now (including us as we are just now bringing these clusters online).
The Question here is, will BIND 9 be secure enough to be included in OpenBSD? OpenBSD still uses BIND v4 due to the security issues with the later versions.
Actually the X-rays don't escape the black hole. the current theory is (since we have never actually "seen" a black hole) is that as particles fall in to the balck hole, they enter a sort of, spiraling, decaying orbit (called the accretion disk). It is the friction between all of these particles in the accretion disk, that generates the x-rays. If the x-ray is released in the right direction it can escape being sucked into the black hole, since the accretion disk exists outside of the black holes event horizon.