Dear Sir, The World Arsenic Association, holder of the Arsenic(tm) name and distinctive marks, believes your insinuations to be tortuously harmful to the value and good public image of the Arsenic(tm) brand.
We would ask that you cease and desist your activity, and would like to remind the reading public that Jonestown residents were consumers of "Cyanide" an inferior imitation product. John Doe III General Counsel
We don't even have fusion working yet, and He-3 isn't the easiest fuel to fuse, so it won't be burned by first-generation reactors. So stop talking about it as a primary reason to go to the moon, already! Let's get some kind of fusion working first.
That being said, getting some kind of a ship to Uranus that could collect it would be enough of a technological challenge that we would probably have fusion working by then.
It's being served by a different numbered IP address than it was the other day (was on a 178. address now on a 212. address), and I don't think this is MacDefender, but some other scareware trash that's just as stupid.
I ran across it this past weekend. I tried it just now and the ad is still being served via the oddsiti URL. (Not the actual content, that's on a numbered IP machine.)
I suggest you add "||oddsiti.com^" to your adblock preferences, as any ad provider that lets this kind of crap through deserves to be blocked, not to mention allowing ads to be served from numbered IP addresses.
For those of you who want to see it, here it is, but I'm adding spaces to keep the link dead without manual editing:
You should probably try to read at least one of my links, or even my actual post, before proving yourself to be an idiot as you have just done. I'm not talking about behavior supported by the filesystem, I'm talking about filenames in the kernel file tree that conflict when put on a case-insensitive filesystem.
Now take your wonderful loopback filesystem and try to store two different files named xt_mark.h and xt_MARK.h. What, you can't? Well the Linux source code requires it.
I don't think building under Cygwin or OSX is a high priority to the Linux kernel developers
Have you ever heard of a cross-compiler? Not all Linux kernels are compiled on the system they are intended to run on. Would you compile an ARM Linux kernel on an Android Phone?
Because not all Linux kernels are compiled on the system on which they are going to run. Apparently you have never worked with an embedded Linux system with a cross-compiler. GCC runs quite well on OS X, but you can't compile, say, an ARM Linux kernel on it without going out of your way to make a case-sensitive* volume. All because someone who worked on the Netfilter code was a retard and named multiple files the same with only case changed.
This requires that the kernel source be stored on a case insensitive file system, and will not work with Cygwin, nor with the default filesystem for OS X.
The lack of a standard "PC chipset platform" has already been a big problem for Windows. They're all x86 but each motherboard is different and requires different drivers, making booting a pre-installed Windows on another motherboard a complete nightmare. I have to say, I really expected Microsoft to force the PC chipset makers to standardise.
Oh wait, it hasn't been. The different ARM SoC platforms are the equivalent of motherboard chipsets in the x86 world, with a common CPU core (literally, with all using the same few CPU cores licensed directly from ARM). The only real difference is that certain important hardware units (such as IDE) are all based on legacy designs dating back to the '80s. As long as there is a common standard for loading the kernel and drivers (we could call it a "BIOS"), the OS kernel would then identify the chipset and load the appropriate drivers.
And the term "BSP" refers to more than just the kernel. I don't think each netbook requires a separate compilation of GNU utilities, busybox, etc.
That was the original intent. However, by the time the PS3 was released, yield was not a problem. So they kept it disabled (and forbade PS3 games from using it) to be consistent. (Also, one SPU was reserved for the hypervisor, leaving 6 for use by games and the original OtherOS.)
Slashdot Mirror
The best part was that cassette port sound could generally be heard with an AM radio due to all the RFI generated by the Model 1.
My favorite is still 'Istanbul Not Constantinople'.
...which was written in 1953.
Dear Sir, The World Arsenic Association, holder of the Arsenic(tm) name and distinctive marks, believes your insinuations to be tortuously harmful to the value and good public image of the Arsenic(tm) brand.
We would ask that you cease and desist your activity, and would like to remind the reading public that Jonestown residents were consumers of "Cyanide" an inferior imitation product. John Doe III General Counsel
Microsoft also owns a patent on throwing chairs around.
We don't even have fusion working yet, and He-3 isn't the easiest fuel to fuse, so it won't be burned by first-generation reactors. So stop talking about it as a primary reason to go to the moon, already! Let's get some kind of fusion working first.
That being said, getting some kind of a ship to Uranus that could collect it would be enough of a technological challenge that we would probably have fusion working by then.
I prefer to stamp them out with the sole of my shoe,
Nasty little nanodevices, always getting under the baseboards. Good riddance.
It's being served by a different numbered IP address than it was the other day (was on a 178. address now on a 212. address), and I don't think this is MacDefender, but some other scareware trash that's just as stupid.
I ran across it this past weekend. I tried it just now and the ad is still being served via the oddsiti URL. (Not the actual content, that's on a numbered IP machine.)
I suggest you add "||oddsiti.com^" to your adblock preferences, as any ad provider that lets this kind of crap through deserves to be blocked, not to mention allowing ads to be served from numbered IP addresses.
For those of you who want to see it, here it is, but I'm adding spaces to keep the link dead without manual editing:
http://oddsiti . com/?id = 541894
I'd have to say that The Pirate Bay is... Finnished.
(removes sunglasses)
YEAAAAAAAAAAAAAAAAAAAH!
Yep, I have one set up with keyword "g", and a location of "http://google.com/search?hl=en&q=%s".
The bonus is no stupid live search to distract me while typing. (Some of us don't look at our fingers while we type.)
You should probably try to read at least one of my links, or even my actual post, before proving yourself to be an idiot as you have just done. I'm not talking about behavior supported by the filesystem, I'm talking about filenames in the kernel file tree that conflict when put on a case-insensitive filesystem.
Now take your wonderful loopback filesystem and try to store two different files named xt_mark.h and xt_MARK.h. What, you can't? Well the Linux source code requires it.
I don't think building under Cygwin or OSX is a high priority to the Linux kernel developers
Have you ever heard of a cross-compiler? Not all Linux kernels are compiled on the system they are intended to run on. Would you compile an ARM Linux kernel on an Android Phone?
Because not all Linux kernels are compiled on the system on which they are going to run. Apparently you have never worked with an embedded Linux system with a cross-compiler. GCC runs quite well on OS X, but you can't compile, say, an ARM Linux kernel on it without going out of your way to make a case-sensitive* volume. All because someone who worked on the Netfilter code was a retard and named multiple files the same with only case changed.
*yes I got my terms confused in the last post
That's all ready there.
[citation needed]
I am specifically referring to names in the kernel source tree using conflicting cases such as:
include/linux/netfilter/xt_connmark.h
include/linux/netfilter/xt_CONNMARK.h
This requires that the kernel source be stored on a case insensitive file system, and will not work with Cygwin, nor with the default filesystem for OS X.
Examples:
Local uncommitted changes, not checked in to index with gitk
Kernel 2.6.20 File Names Case Sensitivity
The Linux kernel needs a case sensitive filesystem
Another LFS newb is stuck: Linux API headers won't install
etc.
Great. Now I can haz case insensitive filenames please?
The previous answer boiled down to "the appropriate time to make the change is a development kernel such as 2.7."
Because that's the only way you can get radioactive waste for a dirty bomb. That's comforting to know.
It depends on how many chairs you can attach to the equipment.
In Woz We Trust.
That's the Steve you were referring to, right?
Nope, that's just normal for Flash crapplet games. Most of the people who make those don't understand what a "busy wait" is or why it's bad.
The lack of a standard "PC chipset platform" has already been a big problem for Windows. They're all x86 but each motherboard is different and requires different drivers, making booting a pre-installed Windows on another motherboard a complete nightmare. I have to say, I really expected Microsoft to force the PC chipset makers to standardise.
Oh wait, it hasn't been. The different ARM SoC platforms are the equivalent of motherboard chipsets in the x86 world, with a common CPU core (literally, with all using the same few CPU cores licensed directly from ARM). The only real difference is that certain important hardware units (such as IDE) are all based on legacy designs dating back to the '80s. As long as there is a common standard for loading the kernel and drivers (we could call it a "BIOS"), the OS kernel would then identify the chipset and load the appropriate drivers.
And the term "BSP" refers to more than just the kernel. I don't think each netbook requires a separate compilation of GNU utilities, busybox, etc.
Calibrating the Sci-fi Ray Gun
It's all about getting the collimation and stuff right, I guess.
Isn't that the word that was traditionally used to refer to Apple?
143.5cm. There, all done! Now get cracking on moving all those rails 0.1mm closer.
That was the original intent. However, by the time the PS3 was released, yield was not a problem. So they kept it disabled (and forbade PS3 games from using it) to be consistent. (Also, one SPU was reserved for the hypervisor, leaving 6 for use by games and the original OtherOS.)
I heard you like singularities, so I put some black holes in your black holes so you can big bang while you big bang.