well then... XD1 to you! We got one at my place of employment a few weeks ago. It is a nice machine. We've been following it since it was an OctigaBay 12k system at SC03. It's basically the same system as it was then I guess, but with the Cray name as far as I can tell. Only a few complaints so far is they could give you a little longer power cord. The thing that comes with it is like 12". Also the case is a bitch to get into... it's like 12 screws, thumb screws would be a plus, something like the IBM p630s with a slide on cover or something would be a lot better. Otherwise the interconnect performance is great!
I work for a USDOE research lab, and I spent the better part of last year shoehorning 64bit ppc into ppc32 debian. This includes time spent porting over scientific applications and testing everything to make sure it would work well in a production environment. The end result was a switch of 64 nodes of various hardware(dual Power3s to 8way power4+s) from AIX to Linux. While debian is not an officially supported distribution, I've been able to alien most anything IBM releases for Deadrat or SuSE with great success. If you're going to be running on ppc64 hardware, I recommend grabbing the redhat releases though, as the SuSE libc linked files are generally non-working with latest toolchains. I imagine similar success with alien on other architectures.
The way the opteron numbering system works is the first number is the amount of CPUs you can run SMP. The 150 is the fastest single CPU you can buy right now, the 850 is running at same clock rate as the 150 but can run in an 8way opteron system (if the boards ever become available). Right now you'd mainly find the 850s in a 4way system. The 850 would definitely be the most expensive opteron, but as a single chip would perform the same as the 150.
2. the RPM has nothing to do with being closed source. It has a binary "IP" library that gets linked in when you compile it... if you want to install on a non-rpm system use alien or some other method of unrpming it, then compile and install. Yes, it's still closed source, but rpm the reason for this.
What I'm upset about is that they have all the hooks for 64bit amd support in the wrapper code, but the binary IP driver is not released for x86_64.
I can verify 1.5Mbit/768k... I'd verify faster but I'm at about 15000ft from the CO.... my coworker that lives closer to the CO gets 1.5mbit/1mbit... so there's 2 verifications... (both from modem training and dslreports speedtests)
What happened to Qwest? They're actually offering good services and more options lately... Was there some change of management?
I'm actually happy with Qwest for once... in the past 3 months: they have lowered my DSL costs by 3 bucks, cut my long distance to 5 cents/minute with a cap of $20/mnth and no monthly fee, raised my DSL speed from 640k/256k to 1.5mbit/1mbit for no additional cost, and now give me the option to cancel phone service altogether.
At one time I REALLY wanted this option because I was so fed up with them. However, with the current changes they've been making lately, I think I'll be keeping my voice line for now!
One note about win64 before you install it. There are no current drivers for the integrated wireless card. Just thought I'd warn you. If you're using an external card with it, enjoy.
Also, with the install, there was a tendency for the installer to sort of "freeze" near the later steps of the install, a quick wiggle of the touchpad seemed to clear that up.
There were a few other components that lacked drivers but I can't recall which exactly.
This is odd. I too have this laptop and it's not hot at all, much cooler than my tibook even! It also lasts 2.5-3hours on battery. Maybe the powernow! drivers were not installed on the laptop you looked at. They are what allows it to clock down. Overall I like this notebook, and you can't beat the price.
Did you read the article? It's not an actual inflating airbag that explodes, it's merely a comparison to an airbag. All the happens is the drive heads are stabilized to prevent a head crash.
But where's their AMD64 drivers... I see a press release from april, but I have yet to find any release of 64bit drivers. Personally, I've never had any problem with nvidia's linux drivers.
Many have mentioned VisualAge C++, but also XL Fortran is available, and saved me a hell of a lot of time porting some AIX code to ppc64-linux. They definitely have the compilers... and also a Java SDK/JRE... the only problem with all of these is that you have to run glibc 2.2.5. This rules out Redhat, which means that your only options for distributions are then limited to SuSE SLES 8.0, or roll your own. I'm hoping to put up a page with debian packages or at least some tarballs to help out with that soon. Maybe within the week. I'm currently running debian on our ppc64 machines and it works very well... apt-get old 32bit stuff, or compile your own 64bit.
Actually, The market does exist. There are already IBM compilers ported to Linux (xlf 8.1 and VisualAge C++ 6.0) and they both work quite well and are a big help in porting code from AIX. There are other people interested in switching from AIX as well.
I would also like to mention that the PPC64 toolchain and kernel is heavily developed. If you're interested in information relating to the ppc64linux development I suggest visiting penguinppc64.
And on a personal note....I would love a cheap ppc64 linux machine such as this. Over the past month or so I've been building a 64bit debian distribution for our IBM pSeries clusters(both power3 and some power4 machines). Preliminary results have some of our programs running a bit faster under linux than in AIX. Hopefully we'll have some more results soon.:-)
Hrmm... not entirely insane... maybe
on
LOTR The Musical!
·
· Score: 3, Interesting
Well... the first intro that I had to the world of hobbits was from a musical version of The Hobbit that I saw as a kid at a local community theatre that my friend was involved in. This sparked both my interest in theatre, and also my interest in the world of Tolkein. Following this performance, I went on to read all of the books, etc... Anyway, My biggest concern of this new musical is how the hell do you shrink it into a length that people will sit though. I fear this will be a mighty big challenge and that the results might not be so pretty... Time will tell I guess!
Sadly though, this is also in windows2000 sp3. So, you'd have to move back to NT 4.0 to be completely safe.
While you may be correct in their intentions, the EULA doesn't specifically state this. Going by just the wording of the EULA, they can do whatever they want, if you have auto-update enabled or not. This is where the problem is. If they specified a clause that would state something to the effect of "unless the user turns off auto-update" or have this EULA addendum pop up when they user enables auto-update with a yes/no box, it would be much, much better. This wording of the EULA in current form of not mentioning any change based on auto-updates being enabled is what is keeping SP3 off of our rdesktop Terminal Server.
Another interesting note is that the EULA for SP3 with the bad text is only there when you install the update, the original Win2k eula.txt is still left unchanged on your hard drive. Makes it kind of confusing, if you ever want to review what you actually agreed to at a later date.
It's not as difficult as you might think. It would be quite easy for a script kiddy to type "ifconfig eth0 hw ether 11:22:33:44:55:66" and many windows ethernet drivers include the option to change it in the device properties. All one has to do is open up the device settings and change the "Network Address", or Media Address, or whatever the people writing the driver want to call it. Not to mention most script kiddy would be able to google for all the above information to get around the ban. Granted this is highly dependent on your NIC and I'm sure not all of them would have one that makes it this easy, but I doubt they will give up that easily either. I don't think this would stop anyone. Well, maybe once 281,474,976,710,656 MAC addresses are banned.
Slashdot Mirror
well then... XD1 to you! We got one at my place of employment a few weeks ago. It is a nice machine. We've been following it since it was an OctigaBay 12k system at SC03. It's basically the same system as it was then I guess, but with the Cray name as far as I can tell. Only a few complaints so far is they could give you a little longer power cord. The thing that comes with it is like 12". Also the case is a bitch to get into... it's like 12 screws, thumb screws would be a plus, something like the IBM p630s with a slide on cover or something would be a lot better. Otherwise the interconnect performance is great!
I work for a USDOE research lab, and I spent the better part of last year shoehorning 64bit ppc into ppc32 debian. This includes time spent porting over scientific applications and testing everything to make sure it would work well in a production environment. The end result was a switch of 64 nodes of various hardware(dual Power3s to 8way power4+s) from AIX to Linux. While debian is not an officially supported distribution, I've been able to alien most anything IBM releases for Deadrat or SuSE with great success. If you're going to be running on ppc64 hardware, I recommend grabbing the redhat releases though, as the SuSE libc linked files are generally non-working with latest toolchains. I imagine similar success with alien on other architectures.
The way the opteron numbering system works is the first number is the amount of CPUs you can run SMP. The 150 is the fastest single CPU you can buy right now, the 850 is running at same clock rate as the 150 but can run in an 8way opteron system (if the boards ever become available). Right now you'd mainly find the 850s in a 4way system. The 850 would definitely be the most expensive opteron, but as a single chip would perform the same as the 150.
Minor correction to your correction: Bryan Mack attended Iowa State University(from the article), which is much different than University of Iowa.
1. ATI has offered drivers since last year.
2. the RPM has nothing to do with being closed source. It has a binary "IP" library that gets linked in when you compile it... if you want to install on a non-rpm system use alien or some other method of unrpming it, then compile and install. Yes, it's still closed source, but rpm the reason for this.
What I'm upset about is that they have all the hooks for 64bit amd support in the wrapper code, but the binary IP driver is not released for x86_64.
I can verify 1.5Mbit/768k... I'd verify faster but I'm at about 15000ft from the CO.... my coworker that lives closer to the CO gets 1.5mbit/1mbit... so there's 2 verifications... (both from modem training and dslreports speedtests)
What happened to Qwest? They're actually offering good services and more options lately... Was there some change of management?
I'm actually happy with Qwest for once... in the past 3 months: they have lowered my DSL costs by 3 bucks, cut my long distance to 5 cents/minute with a cap of $20/mnth and no monthly fee, raised my DSL speed from 640k/256k to 1.5mbit/1mbit for no additional cost, and now give me the option to cancel phone service altogether.
At one time I REALLY wanted this option because I was so fed up with them. However, with the current changes they've been making lately, I think I'll be keeping my voice line for now!
One note about win64 before you install it. There are no current drivers for the integrated wireless card. Just thought I'd warn you. If you're using an external card with it, enjoy.
Also, with the install, there was a tendency for the installer to sort of "freeze" near the later steps of the install, a quick wiggle of the touchpad seemed to clear that up.
There were a few other components that lacked drivers but I can't recall which exactly.
Other than those issues, good luck!
This is odd. I too have this laptop and it's not hot at all, much cooler than my tibook even! It also lasts 2.5-3hours on battery. Maybe the powernow! drivers were not installed on the laptop you looked at. They are what allows it to clock down. Overall I like this notebook, and you can't beat the price.
Did you read the article? It's not an actual inflating airbag that explodes, it's merely a comparison to an airbag. All the happens is the drive heads are stabilized to prevent a head crash.
But where's their AMD64 drivers... I see a press release from april, but I have yet to find any release of 64bit drivers. Personally, I've never had any problem with nvidia's linux drivers.
Who's crotch? The Penguin's or Darl's? Sounds messy either way.
Many have mentioned VisualAge C++, but also XL Fortran is available, and saved me a hell of a lot of time porting some AIX code to ppc64-linux. They definitely have the compilers... and also a Java SDK/JRE... the only problem with all of these is that you have to run glibc 2.2.5. This rules out Redhat, which means that your only options for distributions are then limited to SuSE SLES 8.0, or roll your own. I'm hoping to put up a page with debian packages or at least some tarballs to help out with that soon. Maybe within the week. I'm currently running debian on our ppc64 machines and it works very well... apt-get old 32bit stuff, or compile your own 64bit.
Actually, The market does exist. There are already IBM compilers ported to Linux (xlf 8.1 and VisualAge C++ 6.0) and they both work quite well and are a big help in porting code from AIX. There are other people interested in switching from AIX as well.
:-)
I would also like to mention that the PPC64 toolchain and kernel is heavily developed. If you're interested in information relating to the ppc64linux development I suggest visiting penguinppc64.
And on a personal note....I would love a cheap ppc64 linux machine such as this. Over the past month or so I've been building a 64bit debian distribution for our IBM pSeries clusters(both power3 and some power4 machines). Preliminary results have some of our programs running a bit faster under linux than in AIX. Hopefully we'll have some more results soon.
Obviously they're compensating for something...
the actual size of the units
Well... the first intro that I had to the world of hobbits was from a musical version of The Hobbit that I saw as a kid at a local community theatre that my friend was involved in. This sparked both my interest in theatre, and also my interest in the world of Tolkein. Following this performance, I went on to read all of the books, etc... Anyway, My biggest concern of this new musical is how the hell do you shrink it into a length that people will sit though. I fear this will be a mighty big challenge and that the results might not be so pretty... Time will tell I guess!
obviously you've never heard of this... I mean... I haven't either... uhh... look a pigeon!
Sadly though, this is also in windows2000 sp3. So, you'd have to move back to NT 4.0 to be completely safe.
While you may be correct in their intentions, the EULA doesn't specifically state this. Going by just the wording of the EULA, they can do whatever they want, if you have auto-update enabled or not. This is where the problem is. If they specified a clause that would state something to the effect of "unless the user turns off auto-update" or have this EULA addendum pop up when they user enables auto-update with a yes/no box, it would be much, much better. This wording of the EULA in current form of not mentioning any change based on auto-updates being enabled is what is keeping SP3 off of our rdesktop Terminal Server.
Another interesting note is that the EULA for SP3 with the bad text is only there when you install the update, the original Win2k eula.txt is still left unchanged on your hard drive. Makes it kind of confusing, if you ever want to review what you actually agreed to at a later date.
It's not as difficult as you might think. It would be quite easy for a script kiddy to type "ifconfig eth0 hw ether 11:22:33:44:55:66" and many windows ethernet drivers include the option to change it in the device properties. All one has to do is open up the device settings and change the "Network Address", or Media Address, or whatever the people writing the driver want to call it. Not to mention most script kiddy would be able to google for all the above information to get around the ban. Granted this is highly dependent on your NIC and I'm sure not all of them would have one that makes it this easy, but I doubt they will give up that easily either. I don't think this would stop anyone. Well, maybe once 281,474,976,710,656 MAC addresses are banned.