Unfortunately, you can't even try the Personal version of SuSE 9.1 without forking the $90 because the Personal edition does not ship with a x86-64 kernel.
So let the more savvy Linux users recompile their kernel...I don't see why Anandtech couldn't have tried that.
Unless other 64-bit binaries were needed that weren't included.
There's more to the competition than just out-performing your competitor for this cycle.
You have to have your next product ready for your anounced (or even widely rumored) release date. It's a lot easier to resell the same overperforming device at lower performance levels than to keep producing new overperforming devices at the same rate.
Basically, you take bigger, slower steps, but you only report a frequently increasing fraction of each completed step in order to keep a comparable product out there competing with your competitors'.
Also, having a single product for a longer period of time allows you to tune the hell of that product while R&D is working on pumping out the next generation. So by the end of your cycle, you'll have a reputation for a stable product.
Finally, having a single design with a long lifespan gives you insurance in case there are delays in the R&D while they're trying to produce the next generation. You don't want your competitor to come out with two or three iterations of their product while you've only got a single relatively lackluster device on the market. (This has happened to Intel in the past...look at some of the old benchmarks on Ars Technica.)
What the poster meant was that the introduction of the O(1) scheduler, and the benefits to user experience it provided, caused a lot of "ordinary users" to take notice. That doesn't necessarily mean most "ordinary users" know, or even care.
However, for those that do, you'll Soon be able to drop in the latest IO, CPU or 'whatever' scheduler, now being developed independantly from the kernel.
A shotgun vaccine might have to include large quantites of protein injected into your blood to work, more than your body could tolorate.
You'd have to test everything you put in for toxicity. And randomly generating proteins (by shredding viruses or whatever) sounds like the fastest way to produce something operating the same way Mad Cow disease does...
I've clipped every fingernail on my body. Not many other people have had such a grand oppertunity. In fact, I think the only other person would have been my mother, but that would have been when I was a little tike.
Wouldn't that same clause prohibit Congress from creating an organisation with more powers than Congress itself has? In the computing world, that's called priviledge escalation, and can be dangerous.
The counterexample to "The Stand" would be "The Andromeda Strain"...
In The Stand, destruction of the facility required a specific individual to sacrifice himself and initiate the destruction of the facility. In The Andromeda Strain, the arming of the system was automatic, and only a specific individual could abort it.
I'm not sure either is relevant to present-day bio-hazard facilities, though.
That reminds of a software application I'd heard of a while back. Basically, you chose the options you wanted, and this application would create a computer virus out of pre-written parts to fit the bill.
Antivirus software was particularly effective, though, as a whole new family of viruses had common components you could detect.
I bet the body's immune system will respond in the same way. If you re-use the same formula for the virus shell, the same antibodies will react to a variety of viruses.
Well, you could use things like SSH tunnels and VNC. But that only prevents network-level interception. You'd still be susceptible to keyloggers, video cameras, and the oddball looking over your shoulder.
I tried that with Thunderbird after running the release tarballs for a long time. The Debian Thunderbird setup didn't recognize my old data. Suggestions?
I'd be very surprised if the FCC had the power to implement retroactive law. Under Article 1, Section 9, Clause 3 of the US Constitution, no ex post facto law may be passed.
Very few networks should have the abilitiy to broadcast to 200 million people. Unless you're talking about satellite TV, a single station certainly couldn't.
IIRC, the Microsoft patent is more involved in using the human body for data transmission. It didn't have anything to do with power transmission or generation.
I'm picturing the solar-powered van from an old favorite of my childhood. Of course, Szalinski probably didn't think to charge up batteries for cloudy days.
Slashdot Mirror
What steps did you take to make the transition from self-funded to funded by donations?
Once the Linux binaries came out, you could have used the kernel's x87 emulation. :)
I remember being shocked when a friend told me they ran a qtest server on a 386.
I don't see why Anandtech couldn't have tried that.
Darn it...let me reword that. "I don't see why Anandtech couldn't have mentioned that as an option."
QTA:
Unfortunately, you can't even try the Personal version of SuSE 9.1 without forking the $90 because the Personal edition does not ship with a x86-64 kernel.
So let the more savvy Linux users recompile their kernel...I don't see why Anandtech couldn't have tried that.
Unless other 64-bit binaries were needed that weren't included.
Try using apt. I know it works well for Debian, but I haven't really given it a shot on RPM-based distros.
You'd give up automated dependancy checking and downloading in order to run someone's build script?
Besides, the five-step build process isn't universal. Try compiling Nethack+(any GUI for it)...I find configuring my kernel easier.
On the other hand, I've had to install apps that just came with C files, and no list of dependencies.
(snaps fingers) Ah! That was it.
:(
I was in elementary school at the time, so my memory's a little foggy.
Now that OpenBSD is implementing SMP support, I wonder if (more?) high-end servers will start running it.
There's more to the competition than just out-performing your competitor for this cycle.
You have to have your next product ready for your anounced (or even widely rumored) release date. It's a lot easier to resell the same overperforming device at lower performance levels than to keep producing new overperforming devices at the same rate.
Basically, you take bigger, slower steps, but you only report a frequently increasing fraction of each completed step in order to keep a comparable product out there competing with your competitors'.
Also, having a single product for a longer period of time allows you to tune the hell of that product while R&D is working on pumping out the next generation. So by the end of your cycle, you'll have a reputation for a stable product.
Finally, having a single design with a long lifespan gives you insurance in case there are delays in the R&D while they're trying to produce the next generation. You don't want your competitor to come out with two or three iterations of their product while you've only got a single relatively lackluster device on the market. (This has happened to Intel in the past...look at some of the old benchmarks on Ars Technica.)
What the poster meant was that the introduction of the O(1) scheduler, and the benefits to user experience it provided, caused a lot of "ordinary users" to take notice. That doesn't necessarily mean most "ordinary users" know, or even care.
However, for those that do, you'll Soon be able to drop in the latest IO, CPU or 'whatever' scheduler, now being developed independantly from the kernel.
How many of those 10,000 students were actively using that machine any given semester?
Uh, Win95 didn't come out until 1996, IIRC.
A shotgun vaccine might have to include large quantites of protein injected into your blood to work, more than your body could tolorate.
You'd have to test everything you put in for toxicity. And randomly generating proteins (by shredding viruses or whatever) sounds like the fastest way to produce something operating the same way Mad Cow disease does...
I've clipped every fingernail on my body. Not many other people have had such a grand oppertunity. In fact, I think the only other person would have been my mother, but that would have been when I was a little tike.
Wouldn't that same clause prohibit Congress from creating an organisation with more powers than Congress itself has? In the computing world, that's called priviledge escalation, and can be dangerous.
The counterexample to "The Stand" would be "The Andromeda Strain" ...
In The Stand, destruction of the facility required a specific individual to sacrifice himself and initiate the destruction of the facility. In The Andromeda Strain, the arming of the system was automatic, and only a specific individual could abort it.
I'm not sure either is relevant to present-day bio-hazard facilities, though.
That reminds of a software application I'd heard of a while back. Basically, you chose the options you wanted, and this application would create a computer virus out of pre-written parts to fit the bill.
Antivirus software was particularly effective, though, as a whole new family of viruses had common components you could detect.
I bet the body's immune system will respond in the same way. If you re-use the same formula for the virus shell, the same antibodies will react to a variety of viruses.
...what they have airtight labs and testing procedures for?
Well, you could use things like SSH tunnels and VNC. But that only prevents network-level interception. You'd still be susceptible to keyloggers, video cameras, and the oddball looking over your shoulder.
I tried that with Thunderbird after running the release tarballs for a long time. The Debian Thunderbird setup didn't recognize my old data. Suggestions?
and when you're (retroactively!) guilty?
I'd be very surprised if the FCC had the power to implement retroactive law. Under Article 1, Section 9, Clause 3 of the US Constitution, no ex post facto law may be passed.
Very few networks should have the abilitiy to broadcast to 200 million people. Unless you're talking about satellite TV, a single station certainly couldn't.
IIRC, the Microsoft patent is more involved in using the human body for data transmission. It didn't have anything to do with power transmission or generation.
I'm picturing the solar-powered van from an old favorite of my childhood. Of course, Szalinski probably didn't think to charge up batteries for cloudy days.
Maybe it would be nice if someone used the system against itself once in a while, eh?
Do you perchance mean "Use a system against its abusers." instead?