I think you're very wrong on your last comment. You look at the computers currently nailing the top500 and it's Blue Gene. #1, #2 are both Blue Gene based machines. If you've seen the architecture of those machines, they're anything but generic 64bit x86. The density of these things is amazing, just look it up. You're looking at thousands of processors per rack.
Also, you can get some pretty cool (ahem) machines running Itanium (SGI Altix for example) running 512 processors and 128Tb RAM in a single image. Combine that with an interconnect that provides well under 1 microsecond latency (up to 6.4Gb bandwidth) and you've got quite a fun machine.
But you're right, if you don't need anything exotic, don't buy it.
Look at the goals of Fedora. One is to not be so patch happy like the other distros and stay as close to upstream as possible. That means some stuff will be slower in. As for your 'insight' swsusp2 is already part of FC5 test I believe, so it's not a great leap of faith to expect it to be in FC5.
English beer has absolutely no problem dealing with strong numbers and still rating them as ales and not wine. IPA (India Pale Ale) for example, was traditionally brewed at about 10% and used to be quite a sweet mellow beverage. It was extra-hopped and sugared to protect it on the long journey to india, and by the time it arrived, it was quite a delicate tasty number.
I don't get why they didn't put all the connectors on, and at least provide the option of running non-SLI with 8 monitors driven with decent 3D. That's actually really appeals to me, if it wasn't for the fairly non-blade like power density this will end up with (once you stick it in a dual-proc box).
If you've got a reasonable amount of bandwidth, and not too much packet loss, it's great. Even better if you're multicast capable. It's also open source.
Unless you feel like making some similar hardware device in which case you can reuse their code. Which is very much in keeping with the GPL. So you are, unsurprisingly, quite wrong.
If the software is GPL it doesn't give you immediate rights to the hardware. More to the point, it doesn't require them to produce hardware that's easy to change the software on.
They've moved towards on die cache, and that makes it expensive. A typical CPU uses a hell of a lot of chip area for cache already. Why do you think P4 EE costs so much?
I agree with your point, but at the same time it can be hard to fully cost something like that. You do actually learn something by setting things up (which has value) so it's not necessarily as bad as saying 2 days pay == cost of PBX. Also you could find it is somewhat enjoyable. If it's your own business, and you get a kick out of setting up something for free that you otherwise would have had to pay for, feel free.
Fedora: Plug in soundcard. Run system-config-soundcard. Job done. The nice thing with USB soundcards is that they all use the same usb-audio.ko module.
In what way does klik resolve dependenciess differently? That article claims it just overlays ontop of a.deb repository.
I was also under the impression that the main reason there isn't.deb hell is simply that people make an effort to be compatible with 'core' debian, and there has traditionally been more in debian (and contrib and friends) than redhat. rpms suffered when ximian, redhat, suse, mandrake et al packaged things differently.
Sorry, an incomplete reply on my part. Fly-by-wire is I agree in a critical position, but it's a different challenge. It's not really making decisions, it's just processing the input (from the stick and from wind speed sensors etc.) to determine what to do.
I know you could consider that's all any autonomous system has to do, but it really isn't that complex.
No, I don't remember a crash with recent versions that's not down to a fault with the mplayer plugin.
That URL looks fine using 1.0.7 linux, apart from the presumably flash menu looking a little odd. I've just tested it on 1.0.6 win2k and it was fine, and the menu looked fine.
That's certainly not my experience. I use 1.5 beta 1 at home, and 1.0.7 in the office, and I haven't really noticed much difference. I sometimes run the same copy of firefox for days and don't suffer crashes.
I'm sure there's some small print on the case. I'm just guessing here, but surely if you run with reduced priviliges then you're not vulnerable to this software?
Grid is a horrible term that means relatively little even with the grid computing field. Grid is all about virtualisation, and complex authorization/authentication, something that google really doesn't have to worry about that much.
I think you're very wrong on your last comment. You look at the computers currently nailing the top500 and it's Blue Gene. #1, #2 are both Blue Gene based machines. If you've seen the architecture of those machines, they're anything but generic 64bit x86. The density of these things is amazing, just look it up. You're looking at thousands of processors per rack.
Also, you can get some pretty cool (ahem) machines running Itanium (SGI Altix for example) running 512 processors and 128Tb RAM in a single image. Combine that with an interconnect that provides well under 1 microsecond latency (up to 6.4Gb bandwidth) and you've got quite a fun machine.
But you're right, if you don't need anything exotic, don't buy it.
Look at the goals of Fedora. One is to not be so patch happy like the other distros and stay as close to upstream as possible. That means some stuff will be slower in. As for your 'insight' swsusp2 is already part of FC5 test I believe, so it's not a great leap of faith to expect it to be in FC5.
English beer has absolutely no problem dealing with strong numbers and still rating them as ales and not wine. IPA (India Pale Ale) for example, was traditionally brewed at about 10% and used to be quite a sweet mellow beverage. It was extra-hopped and sugared to protect it on the long journey to india, and by the time it arrived, it was quite a delicate tasty number.
I don't get why they didn't put all the connectors on, and at least provide the option of running non-SLI with 8 monitors driven with decent 3D. That's actually really appeals to me, if it wasn't for the fairly non-blade like power density this will end up with (once you stick it in a dual-proc box).
Not at all. This looks to be the same as the feature of .dvi files (hence the -R flag of dvips).
If you've got a reasonable amount of bandwidth, and not too much packet loss, it's great. Even better if you're multicast capable. It's also open source.
Unless you feel like making some similar hardware device in which case you can reuse their code. Which is very much in keeping with the GPL. So you are, unsurprisingly, quite wrong.
If the software is GPL it doesn't give you immediate rights to the hardware. More to the point, it doesn't require them to produce hardware that's easy to change the software on.
They've moved towards on die cache, and that makes it expensive. A typical CPU uses a hell of a lot of chip area for cache already. Why do you think P4 EE costs so much?
I agree with your point, but at the same time it can be hard to fully cost something like that. You do actually learn something by setting things up (which has value) so it's not necessarily as bad as saying 2 days pay == cost of PBX. Also you could find it is somewhat enjoyable. If it's your own business, and you get a kick out of setting up something for free that you otherwise would have had to pay for, feel free.
Fedora: Plug in soundcard. Run system-config-soundcard. Job done. The nice thing with USB soundcards is that they all use the same usb-audio.ko module.
That used to be true, but my recent experience of Xbox and PS2 is that frame rate hit is now allowable on consoles...
Play more gigs.
"that same inertia will probably carry you forward." Can I hang that on my wall?
Two things.
You'd be surprised how high birds fly, reportedly up to around 20,000 feet. You'll be using Autopilot *way* below that.
Fully automated landings are hardly something new.
In what way does klik resolve dependenciess differently? That article claims it just overlays ontop of a .deb repository.
.deb hell is simply that people make an effort to be compatible with 'core' debian, and there has traditionally been more in debian (and contrib and friends) than redhat. rpms suffered when ximian, redhat, suse, mandrake et al packaged things differently.
I was also under the impression that the main reason there isn't
Sorry, an incomplete reply on my part. Fly-by-wire is I agree in a critical position, but it's a different challenge. It's not really making decisions, it's just processing the input (from the stick and from wind speed sensors etc.) to determine what to do.
I know you could consider that's all any autonomous system has to do, but it really isn't that complex.
Aircraft on autopilot aren't exactly good at avoiding flocks of birds and the like though are they?
The skies are a blissful place compared to the M25 on a friday night. The navigation side is easy, avoiding next doors dog is hard.
No, I don't remember a crash with recent versions that's not down to a fault with the mplayer plugin.
That URL looks fine using 1.0.7 linux, apart from the presumably flash menu looking a little odd. I've just tested it on 1.0.6 win2k and it was fine, and the menu looked fine.
Almost. I think 'si' in that context means 'so', and you can safely drop the leading 'The'. I would be a little less word-for-word and translate it as
"Common sense isn't so common."
That's certainly not my experience. I use 1.5 beta 1 at home, and 1.0.7 in the office, and I haven't really noticed much difference. I sometimes run the same copy of firefox for days and don't suffer crashes.
"Le sens commun n'est pas si commun." so said Voltaire
You're not wrong there AC. I received a text sent from Sydney on new year's and it arrived in the UK on the 7th...
I'm sure there's some small print on the case. I'm just guessing here, but surely if you run with reduced priviliges then you're not vulnerable to this software?
Grid is a horrible term that means relatively little even with the grid computing field. Grid is all about virtualisation, and complex authorization/authentication, something that google really doesn't have to worry about that much.
So just fix the last part no?
find . -name "*.o" | xargs -n 50 rm -f --