This could get ugly, but mainly I want to know what hardware you actually run on (primarily), not which company you like better or which processor you would buy if you had the money.
I run on AMD. I like them b/c they are very inexpensive right now.
CRC123 wrote:
> This could get ugly, but mainly I want to know what hardware you
> actually run on (primarily), not which company you like better or which
> processor you would buy if you had the money.
>
> I run on AMD. I like them b/c they are very inexpensive right now.
>
> Play Nice>:)
>
>
Desktop systems - AMD.
Laptops - Intel since that is what is in the thinkpad. Motorola also
since I have a Powerbook.
Sigh…I wanted a Core 2 Duo system, but I couldn’t get the socket 775 cpu installed without bending all those tiny little pins on the newly-designed 775 motherboard. I built a socket 775 system, but it died after a few days. I took the cpu out, and discovered that every single pin was bent. I installed it wrong, I guess. So then I sold the cpu and just bought an AMD board and cpu. Much easier to install.
Dare I suggest that $£ may be an issue in some cases. Lets be realistic - when you build your box $£ does come in to the equation. My CPU’s hardly ever break into a trot - even with VBox running XP. I get more thrashing from the _64 Flash browser plug-in.
I may be wrong, but I suspect AMD may be has more users in Linux. I always consider Intel to the domain of Speed freaks and gamers. No offence intended KV!
But of course there is no reason why you should or shouldn’t use either. And if I’m honest, I probably would have chosen Intel if they had been cheaper at the time I built my box a year ago.
Wow! I am suprised Intel hasn’t received more of a following here! I have had Intels on almost all of my computers, and been extremely pleased with them. I personally prefer Intel’s Dual-Core approach to AMD’s 64-bit approach for several reasons. On Linux in particular I find that the difference is huge, as there are far more i386-i686 packages than AMD64 packages. For this reason alone I prefer using Intel processors.
could somebody help me to get a tutorial of open suse 10.3 for dummies i am quite interested in using a suse rather than windows now. its just that i dont know how to start… using GUI and console,i want it both…please! start from scratch…:?
We have 4 PCs in the house:
a. athlon-2800 (my main PC)
b. athlon-1100 (my backup/test PC)
c. sempron-2600 (my wife’s PC)
d. intel celeron 1.5 GHz (family laptop).
So thats 3 x amd and 1 x intel.
My wife and I are planning to purchase two new PCs in December. A new family laptop and and a new desktop PC for me. I suspect the new family laptop will also use an Intel PC, and it is quite possible that my next desktop PC will use an Intel. IMHO AMD has been struggling as of late.
irrdev wrote:
> Wow! I am suprised Intel hasn’t received more of a following here! I
> have had Intels on almost all of my computers, and been extremely
> pleased with them. I personally prefer Intel’s Dual-Core approach to
> AMD’s 64-bit approach for several reasons. On Linux in particular I
> find that the difference is huge, as there are far more i386-i686
> packages than AMD64 packages. For this reason alone I prefer using
> Intel processors.
>
>
Huh??? You can run i386 on AMD 64 cpu’s. You can also run x86_64 on
Intel’s Core Duo 2’s and some of the Core Duo’s. i386/x86_64 has nothing
to do with the makers of the CPU.
Most i386-i686 packages can be compiled into AMD64 packages using source/src. For those where the 64-bit proprietary code has not been released, there are __wrappers (fill in the blank) that allow them to function.
Plus, as openSUSE x86-64 has both /lib 32-bit and /lib64 64-bit libraries any package will work on an openSUSE x86-64 install (for me, since about SuSE 9.0 x86-64).
Yeah, there are a lot of Windows users at my college who are obsessed with how fast their computer is, and how much they can overclock their processor and graphics card. Yet, they’re running a Windows operating system. No point in overclocking if you’re going to use a memory hogging OS. I remember my roommate would spend entire afternoons trying to overclock video cards and processors. In that time, he could have gotten a C programming book out at the library, and learned how to program, or do something productive.