Luckily they kicked Dave out years before, but Cliff was the only real musician in the band after that.
They squandered a great resource in Jason. Trujillo is a master bassist. What next?
Thanks to Jason, I met the lady who'd become my wife.
Thanks to Cliff, I took up bass when I was 15.
Thanks to Dave I now play guitar.
Metallica albums 2, 3 and 4 are superb, along with S&M. The Black album is utter rubbish. Load and Reload are 60% contrived drivel. St Anger would have been good apart from the abysmal production.
It's a shame, because they're still OK live. Not a patch on Megadeth, Slayer, Budgie or Mastodon (or even Maiden), but still worth going to see.
Sun doesn't even test gcc on Solaris. Let alone actually try to fix bugs in native support.
Heh. Sun is quite arrogant in that regard.. however.. back in 2004 when it became apparent that Opteron was the way forward, they decided they needed an AMD64 port of Solaris 10. They went from 0 to up and running in 6 weeks flat but they had to use gcc to compile Solaris for AMD64 since their compiler only did 32-bit x86. They paid Code Sorcery to fix some bugs in gcc for them. That's the "gcc-3.4.3" that's _still_ in/usr/sfw/bin on Solaris 11. It's really gcc-3.4.2 with Sun/Code Sorcery fixes, not the real gcc-3.4.2.
They were not keen of having gcc with gcj enabled on Solaris.:-)
If I can get the downloads in one go, anybody can. Sounds like a problem with your computer, not Sun.
Which one? I've got 8 and my wife has a laptop with windows on it. The build 78 download was fine. It was 85 I had the trouble with. I'm in the UK where broadband is pretty ropey. I never have trouble downloading anything else, though. The last big thing I did was Slamd64. All OK.
If I could change one thing, I would love openSolaris to have a ports system like FreeBSD.
NetBSD pkgsrc runs fine on Solaris. A friend of mine was hired by Sun to work on it. He got a couple of thousand extra packages working with it while he was there.
There will be no official "ports" for Solaris. Sun PHBs can't handle it, and neither can the big egos.
The reason you have to log in to the download centre for Sun is export restrictions licensing and usage counters. The former could be solved by removing the offending code. The latter is just PHB nonsense.
How big and slow are C++ compilers? The language itself is enormous and unwieldy. Look at all the add-on libraries you had to use to achieve your example?
You'd have written assembler to do that yourself?
You truly are a god. I bow down and worship at your divine feet, unworthy that I am.
C is a systems language, and it's very good at it. Gone are the days of 8MHz desktop computers when we needed C for writing applications.
C has its place, and C++ isn't all it's cracked up to be.
I hope they are becoming proportionally less popular than other languages, because otherwise we aren't making progress.
I write C for a living, and enjoy it, but then I do systems level stuff. I would hate to write a modern application in C. It'd be crazy. Java or C# would be pushing it too, they're just not high-level enough.
Yes, it's a hog, and I say this as someone with a couple of dozen SUNW^H^H^H^HJAVA shares.
I have some old Sun boxen, one of which (Sun Blade 100, 512MB, 500MHz) I used to play at 64-bit big-endian RISCs running Solaris. All of my other boxes are Linux including an old Ultra 1 with splack.
Nevada build 85 only took about 2+ hours to install from DVD on my Sun Blade 100. The previous one I tried (78?) took 3.5. The GUI is unusably slow, and the disk thrashes like mad. I use it headless over my network normally, so I don't mind too much. There are suspicious java processes running all the time, too. I sometimes run SETI@Home on it and it gets just shy of 330MFLOPS, which isn't bad considering its age.
I remember when Sun started the Java desktop thing. It is a port of GNOME, but they insisted on writing a lot of replacement applets in Java for it. Why have XMMS for audio when you can write a lame mp3 player in Java, for example? *sigh*
On better days, I like to think that the people way up at the helm really "get it" and are just waiting for the rest of the ship to slowly (slowly!) turn. On not-so-good days, I start to wonder if maybe someone's trying to pull a fast one.
You're still waiting for the ship to turn after 3 years? Big egos eh?
I spent over a week trying to get Open Solaris build 85. Sun just doesn't get the free distribution thing. You have to register and log in to the Sun Download Centre, from where you can download the CD or DVD images. They try to persuade you to get the Sun Download Manager which is some Java app that gives you pause and resume buttons for the download.
I tried 5 or 6 times to download on different days with the download stalling at sometimes as much as 90%. On the 8th day, I got the whole image. So much for their download manager. You just have to overwrite the chunk you have and start again.
After all these years, they still haven't sorted out the auto-layout of the filesystems. There's not enough room partitioned to install their developer tools.
I went to build gcc-4.2.3. That took 5 days and about a day of CPU time. OK it's an ancient 500MHz USIIi that I got for nothing, but...
See, Solaris's/bin/sh is badly broken (archaic) and can't be used to build gcc. So you set CONFIG_SHELL to be ksh. Only the configure scripts in gcc are still broken from gcc-3.1.x days and two of the scripts it generates, bin/as and bin/collect-ld at each stage of the bootstrap are broken because they begin #!ksh instead of #!/usr/bin/ksh or whatever.
When I used to build gcc on Solaris, I just sed'd all the scripts to replace/bin/sh with/bin/bash or whatever.
So, for the casual SPARC/Solaris power-user/Linux developer myself, it's just too darn inconvenient.
And the stuff in/usr/sfw/bin, which is where the "Open Source migration" into Solaris proper was supposed to happen still looks like it did in 2005, 3 years ago.
Solaris has a brilliant kernel. Putting the DVD images on Bittorrent (officially) like OpenOffice.org, would be a great start. There are too many hurdles for the average user to go through who might have been interested in trying it out. I don't have to register to download Slackware, Ubuntu, KNOPPIX, NetBSD etc.
Sort out the default install so that the disk layout is sane and make it trivial to install the GNU toolchain.
But I've been through all this years ago, and it pains me to see that it still hasn't been fixed.
Slashdot Mirror
There is still the issue of consent.
Many would agree.
Luckily they kicked Dave out years before, but Cliff was the only real musician in the band after that.
They squandered a great resource in Jason. Trujillo is a master bassist. What next?
Thanks to Jason, I met the lady who'd become my wife.
Thanks to Cliff, I took up bass when I was 15.
Thanks to Dave I now play guitar.
Metallica albums 2, 3 and 4 are superb, along with S&M. The Black album is utter rubbish. Load and Reload are 60% contrived drivel. St Anger would have been good apart from the abysmal production.
It's a shame, because they're still OK live. Not a patch on Megadeth, Slayer, Budgie or Mastodon (or even Maiden), but still worth going to see.
It isn't? Let me give a little example of what you can do in C++.
There's this concept called, "Turing complete."
not the real gcc-3.4.2.
I meant "not the real gcc-3.4.3"
Sun doesn't even test gcc on Solaris. Let alone actually try to fix bugs in native support.
Heh. Sun is quite arrogant in that regard.. however.. back in 2004 when it became apparent that Opteron was the way forward, they decided they needed an AMD64 port of Solaris 10. They went from 0 to up and running in 6 weeks flat but they had to use gcc to compile Solaris for AMD64 since their compiler only did 32-bit x86. They paid Code Sorcery to fix some bugs in gcc for them. That's the "gcc-3.4.3" that's _still_ in /usr/sfw/bin on Solaris 11. It's really gcc-3.4.2 with Sun/Code Sorcery fixes, not the real gcc-3.4.2.
They were not keen of having gcc with gcj enabled on Solaris. :-)
Darn, that's just the live developer preview CD.
Cool, thanks. I'll get seeding :-)
Heh :-) Somewhere I've got a 486sx/20 with Slackware 7 on it and FVWM.
Was it a week or two weeks ago that intel's Larabee was going to replace nvidia and ati's raster graphics with ray tracing?
Thanks.
Ah yes, svc. You used to be able to do /etc/init.d/foo start|stop.
cacaoadm disable
Is this a thinly-veiled reference to Doom? :-)
The svc stuff came along just as I had no more "professional interest" (shall we say) in Solaris.
I'm sure it's nice when you know it, but it's yet another learning curve.
Sun typically priced its x86 and "x64" hardware cheaper than Dell's and HP's.
If I can get the downloads in one go, anybody can. Sounds like a problem with your computer, not Sun.
Which one? I've got 8 and my wife has a laptop with windows on it. The build 78 download was fine. It was 85 I had the trouble with. I'm in the UK where broadband is pretty ropey. I never have trouble downloading anything else, though. The last big thing I did was Slamd64. All OK.
If I could change one thing, I would love openSolaris to have a ports system like FreeBSD.
NetBSD pkgsrc runs fine on Solaris. A friend of mine was hired by Sun to work on it. He got a couple of thousand extra packages working with it while he was there.
There will be no official "ports" for Solaris. Sun PHBs can't handle it, and neither can the big egos.
The reason you have to log in to the download centre for Sun is export restrictions licensing and usage counters. The former could be solved by removing the offending code. The latter is just PHB nonsense.
There was an old joke of the form: C? Oh, you mean PDP-11 assembler.
Posts from this one keep getting modded troll and flamebait.
How big and slow are C++ compilers? The language itself is enormous and unwieldy. Look at all the add-on libraries you had to use to achieve your example?
You'd have written assembler to do that yourself?
You truly are a god. I bow down and worship at your divine feet, unworthy that I am.
C is a systems language, and it's very good at it. Gone are the days of 8MHz desktop computers when we needed C for writing applications.
C has its place, and C++ isn't all it's cracked up to be.
I hope they are becoming proportionally less popular than other languages, because otherwise we aren't making progress.
I write C for a living, and enjoy it, but then I do systems level stuff. I would hate to write a modern application in C. It'd be crazy. Java or C# would be pushing it too, they're just not high-level enough.
Yes, it's a hog, and I say this as someone with a couple of dozen SUNW^H^H^H^HJAVA shares.
I have some old Sun boxen, one of which (Sun Blade 100, 512MB, 500MHz) I used to play at 64-bit big-endian RISCs running Solaris. All of my other boxes are Linux including an old Ultra 1 with splack.
Nevada build 85 only took about 2+ hours to install from DVD on my Sun Blade 100. The previous one I tried (78?) took 3.5. The GUI is unusably slow, and the disk thrashes like mad. I use it headless over my network normally, so I don't mind too much. There are suspicious java processes running all the time, too. I sometimes run SETI@Home on it and it gets just shy of 330MFLOPS, which isn't bad considering its age.
I remember when Sun started the Java desktop thing. It is a port of GNOME, but they insisted on writing a lot of replacement applets in Java for it. Why have XMMS for audio when you can write a lame mp3 player in Java, for example? *sigh*
On better days, I like to think that the people way up at the helm really "get it" and are just waiting for the rest of the ship to slowly (slowly!) turn. On not-so-good days, I start to wonder if maybe someone's trying to pull a fast one.
You're still waiting for the ship to turn after 3 years? Big egos eh?
I spent over a week trying to get Open Solaris build 85. Sun just doesn't get the free distribution thing. You have to register and log in to the Sun Download Centre, from where you can download the CD or DVD images. They try to persuade you to get the Sun Download Manager which is some Java app that gives you pause and resume buttons for the download.
I tried 5 or 6 times to download on different days with the download stalling at sometimes as much as 90%. On the 8th day, I got the whole image. So much for their download manager. You just have to overwrite the chunk you have and start again.
After all these years, they still haven't sorted out the auto-layout of the filesystems. There's not enough room partitioned to install their developer tools.
I went to build gcc-4.2.3. That took 5 days and about a day of CPU time. OK it's an ancient 500MHz USIIi that I got for nothing, but...
See, Solaris's /bin/sh is badly broken (archaic) and can't be used to build gcc. So you set CONFIG_SHELL to be ksh. Only the configure scripts in gcc are still broken from gcc-3.1.x days and two of the scripts it generates, bin/as and bin/collect-ld at each stage of the bootstrap are broken because they begin #!ksh instead of #!/usr/bin/ksh or whatever.
When I used to build gcc on Solaris, I just sed'd all the scripts to replace /bin/sh with /bin/bash or whatever.
So, for the casual SPARC/Solaris power-user/Linux developer myself, it's just too darn inconvenient.
And the stuff in /usr/sfw/bin, which is where the "Open Source migration" into Solaris proper was supposed to happen still looks like it did in 2005, 3 years ago.
Solaris has a brilliant kernel. Putting the DVD images on Bittorrent (officially) like OpenOffice.org, would be a great start. There are too many hurdles for the average user to go through who might have been interested in trying it out. I don't have to register to download Slackware, Ubuntu, KNOPPIX, NetBSD etc.
Sort out the default install so that the disk layout is sane and make it trivial to install the GNU toolchain.
But I've been through all this years ago, and it pains me to see that it still hasn't been fixed.
What are the pros and cons of each when you have to interface with another language or platform?
How do you deal with code written in C++ and PERL, for example? And, for a couple of years, Ruby has been a buzzword.
Please explain what Java and Python have in common other than the fact that they are languages and one is also a platform?
People who want a CPU that's actually fast? If you're complaining about kludgy design, perhaps you shouldn't be using an x86 cpu in the first place.
I'm sorry, I don't buy IBM's marketing.
x86 CPUs aren't kludgy any more and haven't been for 10 years, They're all VLIW/RISC internally.
Blah blah blah, disturbance in the Force, blah blah like millions of slashbots (and IBM and Microsoft astroturfers) heads assplode.
3D!=D
So, D!=0?