Skip to main content

So are we looking for a AMD buyout?

I guess its Saturday and imaginations are flying. This L'Inq reporter thinks AMD can still save the ship. I didn't know that the ship was sinkin'!

Option 1 AMD continues as it is, comes out of the doldrums, creates internal $$$ to repay the mounting debt, and Hector Ruiz becomes the new Steve Jobs-like IT hero figure.

Option 2 IBM decides it is the time, and buys AMD as it is, lock stock and barrel. Benefits? It gains control of its own competitive X86 platform, with potential future socket compatibility with POWER7 for cross-platform shared infrastructure, sets up truly serious competition against Intel. Headaches? Well, what to do with the current management, and why should IBM bother repaying all those debts.

Option 3 Samsung comes in, figuring out it should continue where it stopped in 2001 after the Alphacide. Samsung did try to get into the worldwide 64 bit CPU market then with Alpha, and could do it now again with AMD. Will it happen? Hardly, in my mind - Uncle Sam might not look favourably to ceding the control of this technology to a Far Eastern company, and even if that hurdle is jumped, I could imagine a management revamp chaos worse than in the IBM case - the corporate cultures of these two are so different, and yes I know them both for years.


So, intel has done some work and spent billions of dollars onR&D and marketing, and kept pushing the press to get its opinion across the table. AMD was touted as the hero just a year back and now we're speculating a buyout. What has the world come to?

Y'know something, I need a beer and a swim ;)

If you're hooked on your PC, then you can muse with Nebojsa Novakovic.
Labels:

Comments

Post a Comment

Popular posts from this blog

Security: VMware Workstation 6 vulnerability

vulnerable software: VMware Workstation 6.0 for Windows, possible some other VMware products as well type of vulnerability: DoS, potential privilege escalation I found a vulnerability in VMware Workstation 6.0 which allows an unprivileged user in the host OS to crash the system and potentially run arbitrary code with kernel privileges. The issue is in the vmstor-60 driver, which is supposed to mount VMware images within the host OS. When sending the IOCTL code FsSetVoleInformation with subcode FsSetFileInformation with a large buffer and underreporting its size to at max 1024 bytes, it will underrun and potentially execute arbitrary code. Security focus
Post a Comment
Read more

Splunk that!

Saw this advert on Slashdot and went on to look for it and found the tour pretty neat to look at. Check out the demo too! So why would I need it? WHY NOT? I'd say. As an organization grows , new services, new data comes by, new logs start accumulating on the servers and it becomes increasingly difficult to look at all those logs, leave alone that you'd have time to read them and who cares about analysis as the time to look for those log files already makes your day, isn't it? Well a solution like this is a cool option to have your sysadmins/operators look at ONE PLACE and thus you don't have your administrators lurking around in your physical servers and *accidentally* messing up things there. Go ahead and give it a shot by downloading it and testing it. I'll give it a shot myself! Ok so I went ahead and installed it. Do this... [root@tarrydev Software]# ./splunk-Server-1.0.1-linux-installer.bin to install and this (if you screw up) [root@tarrydev Software]# /op
Post a Comment
Read more