Name a long distance telco company (at least in the US) that *DOESN'T* provide internet access? Right, all the big long distance telco's already make extra money off of internet calls, especially since lots of them bill with obscene hourly rates. Also, how will they define 'ISP'? If my neighbor has a cable modem, or other high speed access system, and I agree to pay for part of his ISP bills if I can dial up my hypothetical 56K modem to his machine to get on the net, is the call between us now going to be billed long distance because he is providing me with internet access?
You don't have to use Disk Druid. Go right ahead and use fdisk! And just because redhat comes with one program that makes some potentially faulty assumptions, doesn't mean that the whole thing's buggy. It just means that disk druid is buggy. Also, if you bother to *read* the installation manual for redhat, you will notice that it *does* warn you that if you don't do the partitioning by hand, your existing partitions might get messed up.
my high school principal was Dennis Ritchie's brother... kinda kewl... He had one of those cool symbolic unix/c posters in his office... He was going to have Dennis come in and talk to our programming class, but it didn't happen before I graduated. Oh well.
I did an 'everything' install of RedHat 5.2 about a month before 2.2.0 came out. to upgrade to 2.2.0, all I had to do was go through the 'shopping list' and get the stuff I needed, all of which compiled and installed just fine. Then I downloaded the 2.2.0 source, extracted it, make xconfig, make dep && make clean && make bzImage && make modules && make modules_install, wait ~30 mins (2 pII300's run fast =]), then copy the new kernel, reconfigure lilo, run lilo, reboot. The only weirdness that I had to deal with was patching a couple utils like xosview to handle two cpus properly. RPMs are evil. TarBalls are good.
I have a feeling that a disproportionate number of people will end up downloading binaries for this one, even though they want to download source, since all us poor RedHat users have ecgs, and ecgs has a bug that the ecgs people have no interest in fixing that prevents Code Crusader from being working (it compiles, then segfaults all over the place when you try to use it). Let's put the slashdot effect to use and tell the ecgs people they need to be compliant with obscure c++ features, as well as commonly used ones! The Code Crusader home page has a good description of what the problem is, and what the ecgs people seem to think about it (our thunk optimization is more important than compliance with ANSI standards). Their attitude reminds me of our favorite locutus lookalike.
I saw an article in Scientific America about a year ago that was about a bunch of people working on a chip that could phyisically REWIRE itself on the fly in a very short amount of time (was it a few milliseconds, or a fraction of a second? I don't remember). So, you could have your general CPU for running most of the OS, but lets say you wanted to play a mad-assed-fast game of quake. The game uploads a specialized chip design to accelerate the game into oblivion by having specialized 'quake hardware.' Or, upload a chip design for an MP3 encoder and save lots of time. The possibilities are endless, both for scientific computing, and for consumer products. I can't say that I know what happened to this project, though...
About 5 years ago, I remember seeing something like this on tv, alebeit a bit more primitive. They had a rubber skull cap with bazillions of electrodes in it (I don't think you needed to shave your head...). It listened to brain waves, or whatever they are, and through a process of learning both by the human and the computer, after a couple hours, the person could fairly smoothly move a mouse-like cursor to any corner of the screen. I don't doubt that, with a little work, this could have been made into a full blown brain-mouse.
Slashdot Mirror
Name a long distance telco company (at least in the US) that *DOESN'T* provide internet access? Right, all the big long distance telco's already make extra money off of internet calls, especially since lots of them bill with obscene hourly rates. Also, how will they define 'ISP'? If my neighbor has a cable modem, or other high speed access system, and I agree to pay for part of his ISP bills if I can dial up my hypothetical 56K modem to his machine to get on the net, is the call between us now going to be billed long distance because he is providing me with internet access?
You don't have to use Disk Druid. Go right ahead and use fdisk! And just because redhat comes with one program that makes some potentially faulty assumptions, doesn't mean that the whole thing's buggy. It just means that disk druid is buggy. Also, if you bother to *read* the installation manual for redhat, you will notice that it *does* warn you that if you don't do the partitioning by hand, your existing partitions might get messed up.
my high school principal was Dennis Ritchie's brother... kinda kewl... He had one of those cool symbolic unix/c posters in his office... He was going to have Dennis come in and talk to our programming class, but it didn't happen before I graduated. Oh well.
I did an 'everything' install of RedHat 5.2 about a month before 2.2.0 came out. to upgrade to 2.2.0, all I had to do was go through the 'shopping list' and get the stuff I needed, all of which compiled and installed just fine. Then I downloaded the 2.2.0 source, extracted it, make xconfig, make dep && make clean && make bzImage && make modules && make modules_install, wait ~30 mins (2 pII300's run fast =]), then copy the new kernel, reconfigure lilo, run lilo, reboot. The only weirdness that I had to deal with was patching a couple utils like xosview to handle two cpus properly. RPMs are evil. TarBalls are good.
I have a feeling that a disproportionate number of people will end up downloading binaries for this one, even though they want to download source, since all us poor RedHat users have ecgs, and ecgs has a bug that the ecgs people have no interest in fixing that prevents Code Crusader from being working (it compiles, then segfaults all over the place when you try to use it). Let's put the slashdot effect to use and tell the ecgs people they need to be compliant with obscure c++ features, as well as commonly used ones! The Code Crusader home page has a good description of what the problem is, and what the ecgs people seem to think about it (our thunk optimization is more important than compliance with ANSI standards). Their attitude reminds me of our favorite locutus lookalike.
Can someone please explain what it the blazes a computer has to do with brewing beer? At least on a personal brewing scale?
I saw an article in Scientific America about a year ago that was about a bunch of people working on a chip that could phyisically REWIRE itself on the fly in a very short amount of time (was it a few milliseconds, or a fraction of a second? I don't remember). So, you could have your general CPU for running most of the OS, but lets say you wanted to play a mad-assed-fast game of quake. The game uploads a specialized chip design to accelerate the game into oblivion by having specialized 'quake hardware.' Or, upload a chip design for an MP3 encoder and save lots of time. The possibilities are endless, both for scientific computing, and for consumer products. I can't say that I know what happened to this project, though...
I have never legally owned a copy of linux, and now that I have 2.2.0 running smoothly (YAY Linus and everyone else!), I never will buy one!
About 5 years ago, I remember seeing something like this on tv, alebeit a bit more primitive. They had a rubber skull cap with bazillions of electrodes in it (I don't think you needed to shave your head...). It listened to brain waves, or whatever they are, and through a process of learning both by the human and the computer, after a couple hours, the person could fairly smoothly move a mouse-like cursor to any corner of the screen. I don't doubt that, with a little work, this could have been made into a full blown brain-mouse.