Accepting this then, the only truly safe way to compute today is to keep your boot/OS/application drive from being writable. Baring this, the next best step is to re-image your drive from non-writable media daily.
Yes, but how do you know that your drive or image hasn't already been infected?
Re:Microsoft and/or Windows have hit the wall?
on
WinFS Gets the Axe
·
· Score: 1
I get the feeling that they were planning on doing this with.NET (weren't they planning on making some important components in Vista use.NET), until they figured out that they don't want to rewrite their codebase, and that today's computers may be just a bit too slow for the operating system to be written in C#.
MP3's have ID3 tags, and JPEG's have EXIF data, while some other formats could have metadata extracted automatically from them. You're right, however, that in most cases getting good metadata will be a lot of work.
IE is the HTML rendering DLLs of Windows. AFAIK, it's just a thin wrapper around them. I suspect that most of the effort that goes into writing IE goes into writing those DLLs.
I agree, although the temperatures that they say that this process occurs at are almost twice the temperature you need to refine aluminum. That might explain why it was considered practical for aluminum, but not considered for titanium. They did say that they were having problems with heat.
Huh? If your equipment were to cut across the the wafer randomly, or mix chemicals slightly incorrectly, wouldn't that be a problem? What he's saying is that there may be too many failures on burn in. Also, wouldn't it be a problem if the tests were rejecting chips that were actually good, because they're too stringent?
At the moment, yes, but that's only because they don't expect you to use the internet too much from your phone. I suspect they might consider raising the price if lots of people play this game lots of the time.
Of course, part of the problem people have with classifying these messages is that the classifiers are not the recipients, so how would they know what the recipient wants?
When you distribute the kernel module, you must abide by the terms of the GPL, because
b) You must cause any work that you distribute or publish, that in
whole or in part contains or is derived from the Program or any
part thereof, to be licensed as a whole at no charge to all third
parties under the terms of this License.
and the kernel module is derivative of the shim is derivative of the kernel, which falls under the GPL. Therefore, you must:
a) Accompany it with the complete corresponding machine-readable
source code, which must be distributed under the terms of Sections
1 and 2 above on a medium customarily used for software interchange; or,
Notice the word *complete* in there? Complete means including the source code to the binary only portion. You must distribute the binary-only portion as
If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it.
The binary-only portion is distributed in the kernel module as part of a whole. It is one file, and there are function calls between the two parts. They are connected intimately. The binary-only portion itself is not source, as
The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable.
You would not prefer to modify the binary-only portion with a hex-editor, you would prefer to edit its source code with a text editor.
Imagine that Kororaa wanted to distribute this kernel module without needing to be under the terms of the GPL. They could not, as they otherwise have no permission to distribute a derivative work of the kernel - doing so would be a copyright violation. Therefore, they must fall under the terms of the GPL, one of which includes distributing the complete source code, including the source code of the binary-only portion. It does not matter that the binary-only portion is not a derivative of the kernel, as the complete kernel module is a derivative of the kernel, so the terms must be abided by for the *complete* kernel module, complete source code distribution included. Kororaa cannot do that, as they do not have source code to the binary-only distribution, so they cannot distribute the compiled kernel module.
If the last mile couldn't download the video, then there'd be no problem with choking the internet. No one would try to download it, so the internet could run smoothly. The problem is not the last mile, it's the rest of the internet.
Wrong. Did you even read what he was quoting, at all?
The NVIDIA kernel module consists of two pieces: a binary-only portion and a kernel interface layer (aka the "shim"). The binary-only portion is not Linux-specific (the same code is used on Windows, Solaris, etc), and does not include any Linux kernel header files when it is built.
The kernel module is not the same across all operating systems, the binary-only portion is. The kernel module is created by linking the kernel-derived shim with the binary-only portion. The shim is derived from the kernel. There is a different one for every operating system. The kernel module is derived from the shim, so the kernel module is derived from the kernel.
Your attempt to show that the kernel module is not based on the shim is obviously derived from a erroneous reading both of what I wrote, and of what nVidia wrote.
AFAIK, that would be great. It might even be possible for them to compile the binary shim on their own system, and just link the shim and binary blob together at boot time, every time, to form a kernel module. As long as the combination of GPLd shim and sourceless blob happens on the user's computer, so that combined thing wouldn't have to be redistributed, it would work fine.
As soon as you redistribute that and therefore need to redistribute the source to the binary blob, then you have a problem.
That's exactly what I said. Koraraa distributes the compiled combination of binary and shim - the kernel module - doesn't it?
After the shim is compiled, it is linked with the binary-only portion, to produce the final NVIDIA kernel module.
The shim is derived from the kernel, and the binary kernel module is derived from the shim, so the binary kernel module is derived from the kernel. The compiled binary module must therefore be distributed under the terms of the GPL, so when you distribute the binary module, you must distribute all of the source code, that of the binary-only portion.
Perhaps, but the binary module is compiled by linking against the kernel headers, and it includes shim code which may (or may not) be derived from the kernel. This would mean that the compiled binary module (which he is distributing) could therefore be derived from the kernel, and thus would need to be distributed under the terms of the GPL.
Why do you think that nvidia doesn't precompile their shim code too, when they distribute their kernel module. Of course, If copyright affected Kororaa, then it should affect any other distribution which distributes compiled binary kernel modules.
It's not just a matter of having fertile offspring when they do have have offspring, it's a matter of whether they have fertile offspring. If the two species don't interbreed very often at all (due to members of one species finding members of the other species unattractive, for instance), then they can still be considered seperate species, even if every child is fertile.
Slashdot Mirror
IANAL, but I suspect that the intent of giving that number was not malicious.
It was never really automatic. You always had to hack into the payroll system to do that - I guess these guys forgot that step.
Accepting this then, the only truly safe way to compute today is to keep your boot/OS/application drive from being writable. Baring this, the next best step is to re-image your drive from non-writable media daily.
Yes, but how do you know that your drive or image hasn't already been infected?
I get the feeling that they were planning on doing this with .NET (weren't they planning on making some important components in Vista use .NET), until they figured out that they don't want to rewrite their codebase, and that today's computers may be just a bit too slow for the operating system to be written in C#.
MP3's have ID3 tags, and JPEG's have EXIF data, while some other formats could have metadata extracted automatically from them. You're right, however, that in most cases getting good metadata will be a lot of work.
32 bits is generally more than enough.
8 registers, however, are not.
What are you complaining about? This is an extension. The firefox developers had nothing to do with it.
IE is the HTML rendering DLLs of Windows. AFAIK, it's just a thin wrapper around them. I suspect that most of the effort that goes into writing IE goes into writing those DLLs.
I agree, although the temperatures that they say that this process occurs at are almost twice the temperature you need to refine aluminum. That might explain why it was considered practical for aluminum, but not considered for titanium. They did say that they were having problems with heat.
D'Oh!
Huh? If your equipment were to cut across the the wafer randomly, or mix chemicals slightly incorrectly, wouldn't that be a problem? What he's saying is that there may be too many failures on burn in. Also, wouldn't it be a problem if the tests were rejecting chips that were actually good, because they're too stringent?
At the moment, yes, but that's only because they don't expect you to use the internet too much from your phone. I suspect they might consider raising the price if lots of people play this game lots of the time.
Of course, part of the problem people have with classifying these messages is that the classifiers are not the recipients, so how would they know what the recipient wants?
I was pretty surprised about this too, but Microsoft gives the URL of an example page that does this (if you're using IE5.5 for Windows).
Sure it has a monolithic kernel. It's just that it also has a microkernel, too.
and the kernel module is derivative of the shim is derivative of the kernel, which falls under the GPL.
Therefore, you must:
Notice the word *complete* in there? Complete means including the source code to the binary only portion. You must distribute the binary-only portion as
The binary-only portion is distributed in the kernel module as part of a whole. It is one file, and there are function calls between the two parts. They are connected intimately.
The binary-only portion itself is not source, as
You would not prefer to modify the binary-only portion with a hex-editor, you would prefer to edit its source code with a text editor.
Imagine that Kororaa wanted to distribute this kernel module without needing to be under the terms of the GPL. They could not, as they otherwise have no permission to distribute a derivative work of the kernel - doing so would be a copyright violation. Therefore, they must fall under the terms of the GPL, one of which includes distributing the complete source code, including the source code of the binary-only portion.
It does not matter that the binary-only portion is not a derivative of the kernel, as the complete kernel module is a derivative of the kernel, so the terms must be abided by for the *complete* kernel module, complete source code distribution included. Kororaa cannot do that, as they do not have source code to the binary-only distribution, so they cannot distribute the compiled kernel module.
*Free* login for all these books? You wish.
They use broadcast, so they don't have to on-demand retrieve the show that each person is watching from the internet.
If the last mile couldn't download the video, then there'd be no problem with choking the internet. No one would try to download it, so the internet could run smoothly. The problem is not the last mile, it's the rest of the internet.
Wrong. Did you even read what he was quoting, at all?
The NVIDIA kernel module consists of two pieces: a binary-only portion and a kernel interface layer (aka the "shim"). The binary-only portion is not Linux-specific (the same code is used on Windows, Solaris, etc), and does not include any Linux kernel header files when it is built.
The kernel module is not the same across all operating systems, the binary-only portion is. The kernel module is created by linking the kernel-derived shim with the binary-only portion. The shim is derived from the kernel. There is a different one for every operating system. The kernel module is derived from the shim, so the kernel module is derived from the kernel.
Your attempt to show that the kernel module is not based on the shim is obviously derived from a erroneous reading both of what I wrote, and of what nVidia wrote.
AFAIK, that would be great. It might even be possible for them to compile the binary shim on their own system, and just link the shim and binary blob together at boot time, every time, to form a kernel module. As long as the combination of GPLd shim and sourceless blob happens on the user's computer, so that combined thing wouldn't have to be redistributed, it would work fine.
As soon as you redistribute that and therefore need to redistribute the source to the binary blob, then you have a problem.
That's exactly what I said. Koraraa distributes the compiled combination of binary and shim - the kernel module - doesn't it?
After the shim is compiled, it is linked with the binary-only portion, to produce the final NVIDIA kernel module.
The shim is derived from the kernel, and the binary kernel module is derived from the shim, so the binary kernel module is derived from the kernel. The compiled binary module must therefore be distributed under the terms of the GPL, so when you distribute the binary module, you must distribute all of the source code, that of the binary-only portion.
Perhaps, but the binary module is compiled by linking against the kernel headers, and it includes shim code which may (or may not) be derived from the kernel. This would mean that the compiled binary module (which he is distributing) could therefore be derived from the kernel, and thus would need to be distributed under the terms of the GPL.
Why do you think that nvidia doesn't precompile their shim code too, when they distribute their kernel module. Of course, If copyright affected Kororaa, then it should affect any other distribution which distributes compiled binary kernel modules.
It's not just a matter of having fertile offspring when they do have have offspring, it's a matter of whether they have fertile offspring. If the two species don't interbreed very often at all (due to members of one species finding members of the other species unattractive, for instance), then they can still be considered seperate species, even if every child is fertile.
No, no, Rusty is the one with the monocle polish.