I actually like Solaris 10 as a desktop. I played with it on a test box for a few months. It's horribly slow unless it has a lot of RAM (I had 512MB on a Blade 100 and it was still slow), but it seems good. I changed the colors, background, etc. using the supplied tools (remember, it's basically Gnome) and it worked well. I still greatly prefer Solaris as a server OS, but it's acceptable as a desktop. Firefox, Gaim, Thunderbird, and most anything you want to compile just work.
I'm curious, what about the paths and default executables do you find difficult in Solaris? I'll agree that/usr/ccs/bin appears goofy for the compiler (to me, at least), but I don't see what's odd about everything else. Then again, I'm used to running Solaris, AIX, Tru64, etc. and Linux seems weird to me. I expect most of my optional software to be self-contained, say in/opt, and not scattered about various other dirs. But, that's just my opinion.
I don't know, taking "screenshots" of my boot sequences are pretty easy, they're logged by the terminal server. Then again, I see no reason to run a GUI on my Solaris servers.
Really? For a long time, Sun's first response was "Patch your systems and apply new firmware. After that, we'll help you troublshoot." They've gotten a lot better about that, but I've had _much_ more luck getting help from IBM (AIX), Red Hat (AS 2.1), and HP/Compaq (Tru64 4.0F-5.1A), that Sun (Solaris 2.6, 7, 8, and 9).
So, your Solaris servers haven't been patched in at least two years? Long service/application uptimes is great, via HA clusters, load-balancing, etc. IMHO, long server uptimes means that the admin hasn't done his duty to keep the machines updated. My servers (Solaris and Linux) get quarterly patches, so that they're relatively up-to-date on security fixes, bug fixes, enhancements, etc.
"Veritas SAN?" Do you mean "The the Suns use Veritas and are connected to a SAN?" Veritas doesn't make SAN hardware. Their software is normally used with storage from EMC, HP, Sun, Hitachi, etc.
Firefox went from 1.0 to 1.0.1 and required replacing the entire app. How is that not a "minor update?" On Windows it also required that the installation not be done in a directory where Firefox already existed, i.e., it couldn't be installed over itself. To me, that's just a bad way to do things. If the intended audience is the average user and not geeks, then this is a terrible way to do things.
My favorite one was built into the machine. Back in "the day", in this case the early-to-mid 90s, I had access to a NeXT Dimension. I don't remember the specs, but it was awesome watching TV on it back in 1994.
A cold office? I'm jealous. My cube is always hot. In winter the heat is blasting and in summer no one cranks up the A/C. I'd _really_ dig an office that's cold.
Lousy if you want to have remote access? I use SSH and don't have any issues, but I don't try to use the entire desktop. Shoot, most of my time when sitting at the machine is spent working in a command prompt.
Kind of like one bad virus experience makes you want to move away from Microsoft products? Don't get me wrong, I prefer *nix over MS products most any day. I'm just playing devil's advocate with your logic flow.
Why not? People paid to see it three times, why would anyone expect them not to pay to see it four times?
It's funny, everyone I knew went to see Episode I because it was Star Wars. Then, they went to see Episode II while saying, "There's no way it can be a lame as Episode I." Now, they're planning to see Episode III while saying, "The prequels _have_ to get better or at least show some tie-in with Episode IV."
Personally, I'll go see it just to see how far Lucas will stretch this out just to make a buck. IMHO, he should've simply stopped with Jedi....
Using that same logic, is it Chevy's fault if I don't change my oil and the engine destroys itself? As some point, the owner/user has to take responsibility for their equipment. If they don't know how to maintain it, then they need to check with someone who does. I don't feel 100% comfortable changing the serpentine belt on my vehicle, so I pay a professional to do it. Why should a computer be any different?
I'm merely trying to comment on any failure rate in the user recognition system. Every well-maintained firearm that I've ever used with good ammunition has an almost nil failure rate. My concern is that, due to grip changes, change-of-hands, injury, etc., any recognition system is likely to have a much higher rate of failure (i.e. user lockout/rejection) as compared to the misfire rate of the "dumb" weapon alone.
It was poor phrasing. I wasn't trying to state that Huygens is an "impactor," more that the similar utilization of a "mothership" and "probe" will be used.
This makes for an interesting question. Would you depend on a condom that worked 80% of the time? If not, why would you trust something to protect your life if it has the same failure rate?
Would it also realize that I changed hands? If I normally shoot with my dominant hand holding the weapon and my non-dominant hand wrapped around it in a two-hand grip, what happens if my dominany hand is unusable? Say my pinky finger is broken in a scuffle, will the system still allow me to fire with only three fingers and a thumb? In my opinion, this introduces too many variables for a possible life-or-death situation.
If this is a good idea for the civilian population, then it should apply to law enforcement as well. However, if a system is not usuable by those who are highly-trained and/or -skilled professionals, then it should not be forced on those who also need to protect themselves.
Slashdot Mirror
Actually, Windows 2003 Datacenter scales to 32 processors. Still much less than Solaris. Still Windows.
Excellent, I didn't realize that the GA was more efficient. I have it running on a home server, but I've not attempted it as a desktop.
I actually like Solaris 10 as a desktop. I played with it on a test box for a few months. It's horribly slow unless it has a lot of RAM (I had 512MB on a Blade 100 and it was still slow), but it seems good. I changed the colors, background, etc. using the supplied tools (remember, it's basically Gnome) and it worked well. I still greatly prefer Solaris as a server OS, but it's acceptable as a desktop. Firefox, Gaim, Thunderbird, and most anything you want to compile just work.
I'm curious, what about the paths and default executables do you find difficult in Solaris? I'll agree that /usr/ccs/bin appears goofy for the compiler (to me, at least), but I don't see what's odd about everything else. Then again, I'm used to running Solaris, AIX, Tru64, etc. and Linux seems weird to me. I expect most of my optional software to be self-contained, say in /opt, and not scattered about various other dirs. But, that's just my opinion.
I don't know, taking "screenshots" of my boot sequences are pretty easy, they're logged by the terminal server. Then again, I see no reason to run a GUI on my Solaris servers.
vi /etc/ethers /etc/hosts
vi
add_install_client
boot net - install
There you are, the installation walkthrough for jumpstarting Solaris. Tune in for our next episode, when we cover logging onto the console.
True, but not every *nix-based OS puts things in the same place. Look for /etc/exports on Solaris or /etc/sysconfig/network on AIX....
Really? For a long time, Sun's first response was "Patch your systems and apply new firmware. After that, we'll help you troublshoot." They've gotten a lot better about that, but I've had _much_ more luck getting help from IBM (AIX), Red Hat (AS 2.1), and HP/Compaq (Tru64 4.0F-5.1A), that Sun (Solaris 2.6, 7, 8, and 9).
So, your Solaris servers haven't been patched in at least two years? Long service/application uptimes is great, via HA clusters, load-balancing, etc. IMHO, long server uptimes means that the admin hasn't done his duty to keep the machines updated. My servers (Solaris and Linux) get quarterly patches, so that they're relatively up-to-date on security fixes, bug fixes, enhancements, etc.
"Veritas SAN?" Do you mean "The the Suns use Veritas and are connected to a SAN?" Veritas doesn't make SAN hardware. Their software is normally used with storage from EMC, HP, Sun, Hitachi, etc.
Firefox went from 1.0 to 1.0.1 and required replacing the entire app. How is that not a "minor update?" On Windows it also required that the installation not be done in a directory where Firefox already existed, i.e., it couldn't be installed over itself. To me, that's just a bad way to do things. If the intended audience is the average user and not geeks, then this is a terrible way to do things.
My favorite one was built into the machine. Back in "the day", in this case the early-to-mid 90s, I had access to a NeXT Dimension. I don't remember the specs, but it was awesome watching TV on it back in 1994.
A cold office? I'm jealous. My cube is always hot. In winter the heat is blasting and in summer no one cranks up the A/C. I'd _really_ dig an office that's cold.
Lousy if you want to have remote access? I use SSH and don't have any issues, but I don't try to use the entire desktop. Shoot, most of my time when sitting at the machine is spent working in a command prompt.
Kind of like one bad virus experience makes you want to move away from Microsoft products? Don't get me wrong, I prefer *nix over MS products most any day. I'm just playing devil's advocate with your logic flow.
Watch IV, then V, then VI. Unless you're _really_ bored and/or inebriated, skip I and II. We'll see about III, but I'm not holding my breath....
Why not? People paid to see it three times, why would anyone expect them not to pay to see it four times?
It's funny, everyone I knew went to see Episode I because it was Star Wars. Then, they went to see Episode II while saying, "There's no way it can be a lame as Episode I." Now, they're planning to see Episode III while saying, "The prequels _have_ to get better or at least show some tie-in with Episode IV."
Personally, I'll go see it just to see how far Lucas will stretch this out just to make a buck. IMHO, he should've simply stopped with Jedi....
I'd bet that the VMS/OpenVMS boys would also disagree....
Using that same logic, is it Chevy's fault if I don't change my oil and the engine destroys itself? As some point, the owner/user has to take responsibility for their equipment. If they don't know how to maintain it, then they need to check with someone who does. I don't feel 100% comfortable changing the serpentine belt on my vehicle, so I pay a professional to do it. Why should a computer be any different?
I'm merely trying to comment on any failure rate in the user recognition system. Every well-maintained firearm that I've ever used with good ammunition has an almost nil failure rate. My concern is that, due to grip changes, change-of-hands, injury, etc., any recognition system is likely to have a much higher rate of failure (i.e. user lockout/rejection) as compared to the misfire rate of the "dumb" weapon alone.
It was poor phrasing. I wasn't trying to state that Huygens is an "impactor," more that the similar utilization of a "mothership" and "probe" will be used.
This makes for an interesting question. Would you depend on a condom that worked 80% of the time? If not, why would you trust something to protect your life if it has the same failure rate?
Would it also realize that I changed hands? If I normally shoot with my dominant hand holding the weapon and my non-dominant hand wrapped around it in a two-hand grip, what happens if my dominany hand is unusable? Say my pinky finger is broken in a scuffle, will the system still allow me to fire with only three fingers and a thumb? In my opinion, this introduces too many variables for a possible life-or-death situation.
If this is a good idea for the civilian population, then it should apply to law enforcement as well. However, if a system is not usuable by those who are highly-trained and/or -skilled professionals, then it should not be forced on those who also need to protect themselves.
Assuming all of their calculations were done using the same units of measurement.....
It's similar to the idea behind Cassini and Huygens. The main craft "drops off" an impactor and records the results, then sends them back to Earth.