It is a good question, I'd like to know, too. This isn't the same site it was back before there were accounts, of course, but it isn't the same site it was four years ago either. It's not just the lack of nerds, but there seem to be groups of shills pushing political agendas as well. I wonder if all the nerds here have been replaced by H1B's...
When you start running more than one screen process under the same user it can make it difficult to re-attach because you have to tell it which pty to attach to.
This is where the "-S sessionname" option is handy. I used to have multiple instances of long computations running, and each screen session would have multiple windows containing the code editing, compiling, and execution. Using the session name made it very easy to tell which was which.
Use the "screen -list" command to see all the different screen sessions you have started, along with their names.
The rovers on mars almost died when their flash memory filled up, because they did not intend to survive long enough to gather so much data, that the capacity of their flash was deemed more than enough.
That's not an accurate representation of what happened. I think you are confusing Bill Gates with the MER crew. JPL never designs a spacecraft with 'more memory than it will ever use' because that's just not possible (you can't launch the weight of that much memory). In fact, all missions have to be designed to delete data as the mission goes, but sometimes things go wrong.
If you want to read a description of the underlying issues and see how JPL responds to anomalies check MER Spirit Flash Memory Anomaly [PDF,NASA,JPL].
Just a pet peeve of mine. No scientists were involved in rescuing the rovers. Engineers did all the work, and deserve all the credit for the immense success and longer duration of this mission. Scientists deserve the credit for the science that we get from them. The success of the rovers depends entirely on Engineers.
Slashdot Mirror
Thank you, that was a nice trip down memory lane.
It is a good question, I'd like to know, too. This isn't the same site it was back before there were accounts, of course, but it isn't the same site it was four years ago either. It's not just the lack of nerds, but there seem to be groups of shills pushing political agendas as well. I wonder if all the nerds here have been replaced by H1B's...
This is where the "-S sessionname" option is handy. I used to have multiple instances of long computations running, and each screen session would have multiple windows containing the code editing, compiling, and execution. Using the session name made it very easy to tell which was which.
Use the "screen -list" command to see all the different screen sessions you have started, along with their names.
That's not an accurate representation of what happened. I think you are confusing Bill Gates with the MER crew. JPL never designs a spacecraft with 'more memory than it will ever use' because that's just not possible (you can't launch the weight of that much memory). In fact, all missions have to be designed to delete data as the mission goes, but sometimes things go wrong.
If you want to read a description of the underlying issues and see how JPL responds to anomalies check MER Spirit Flash Memory Anomaly [PDF,NASA,JPL].