...as far as possible from the dangers of firing engines and falling debris, which were responsible for the accidents that destroyed the shuttle Challenger in 1986 and the Columbia in 2003.
Now, If I recall correctly, it was a faulty o-ring that caused a fuel leak, which was blamed on a managerial decision to go ahead with a launch in temperatures colder than all previous launches. The cold air caused the o-ring to be brittle and not seal properly. This is a pretty major fact screw up for the NYT!
A reference with correct info:
I think the argument "it's free, you can't expect much" just doesn't count nowadays. The Debian concept shouldn't be "it's inferior, but at least it's free".
Uhh? Hello? It _is_ free. If you want to provide free security support past the 1 year mark, you go right ahead. Since you feel that somebody should be offering it for free, put _your_ money (well really, time) where your mouth is.
Stoplights are in a pre-determined order, so that extremely colorblind people can still know what the light is signalling (red on top, green on bottom, or red on left, green on right iirc). Of corse you would be right about the single blinking yellow or red lights (for yield & stop)
So what you are saying is, in an emergency situation when your radio goes out, you have a 1 in 4 chance of actually recognizing the colors and not putting other people at risk? Good thing you went for a fourth opinion!
Hrm... When I use the CAN'bus, I do get paranoid, but I've never had the volume of music change, allthough, music generally sounds better when I'm on it.
I like how the first result for a simple search of 'linux' returns a (probably biased) comparison between Linux and Windows, hosted by www.microsoft.com.
'q' meaning quit is non obvious, but things like F1 meaning help are? You do have to make some assumptions about your target audience when writing technical documentation. I thing the general idea of 'q' meaning quit _is_ obvious.
And, next time you are in a manpage, you can try 'h' for help, but i guess that makes no sense either.
Yes It could have taken me many more commands to get there, and i can use more than 3 clicks in windows to do even very simple things. IIRC the article i was refrencing didnt mean "If a user cant find it in 3 clicks, it sucks" it was "everything should be reachable by 3 clicks." So, 3 commands. deal.
Can't post that blog article here? I don't blame you the/. trolls would flame you to death in about 2 seconds.
IMO The people that need to grow up are the people that dont put any effort into finding something out for themselves, and get all pissy when someone explains to the how to get information for themselves, and yes, RTFM, STFW and etc are not valid pieces of advice.
There have been plenty of times that my questions were ignored, or answered back with snyde remarks. It is just par for the course. Go on the msdn forums sometimes, you'll find plenty of tools there too.;)
If you think it is common practice to give your grandma a computer with linux installed, that boots to a CLI, you sir are the one kidding.
And, as a couple posts down, You think that if it was Windows on that strange shiny new thing you gave to grandma, she'd be up and running as soon as she hits the power button? Any thing new requires a at least minimum effort to be able to use it.
I had to hold my fathers hand to do the most simple of tasks in Windows the first couple of times (Read E-Mail, search the web, make the text bold in Word.) Are you going to tell me that Windows is not ready for the desktop because he wasn't able to do whatever he wanted with nil in the way of training, or of seeking help?
What, the attitude of "please, someone hold my hand?" come on dude, these are basic concepts, that exist in DOS as well as linux. $command/? in DOS dosen't work? If you are unwilling to look at the help screen/manpage of a command, then I am unwilling to do it for you.
Yes, things like mounting are not the most intuitive, if you are used to the way that Windows does it. But, IME all of the common things that are not intuitive that people want to do are covered in the distributions getting started docs. Or at least they were when i was starting out.
maybe you should check out the apropos command
caffeine blef # apropos floppy
fd (4) - floppy disk device
fdformat (8) - Low-level formats a floppy disk
setfdprm (8) - sets user-provided floppy disk parameters
hrm fd looks interesting...
caffeine blef # man fd
FD(4) Linux Programmer's Manual FD(4)
NAME
fd - floppy disk device
*snip*
SEE ALSO
floppycontrol(1), mknod(1), chown(1), getfdprm(1), superformat(1), mount(8), setfdprm(8)
So, with this route, I am 3 commands away from what I want. I seem to recall some design essay about everything being at most 3 clicks. Looks good to me.
Slashdot Mirror
Avast! Ye be one pirate talking scallywag!
http://talklikeapirate.com/piratehome.html
Now, If I recall correctly, it was a faulty o-ring that caused a fuel leak, which was blamed on a managerial decision to go ahead with a launch in temperatures colder than all previous launches. The cold air caused the o-ring to be brittle and not seal properly. This is a pretty major fact screw up for the NYT! A reference with correct info:
http://www.engineering.com/content/ContentDisplay
FWIW, go fuck yourself.
FWIW, HIV is the virus, AIDS is a descryption of a condition when your white blood cells drop below a certain level.
support@imblaze.com
Uhh? Hello? It _is_ free. If you want to provide free security support past the 1 year mark, you go right ahead. Since you feel that somebody should be offering it for free, put _your_ money (well really, time) where your mouth is.
Stoplights are in a pre-determined order, so that extremely colorblind people can still know what the light is signalling (red on top, green on bottom, or red on left, green on right iirc). Of corse you would be right about the single blinking yellow or red lights (for yield & stop)
So what you are saying is, in an emergency situation when your radio goes out, you have a 1 in 4 chance of actually recognizing the colors and not putting other people at risk? Good thing you went for a fourth opinion!
welcome home.
Hrm... When I use the CAN'bus, I do get paranoid, but I've never had the volume of music change, allthough, music generally sounds better when I'm on it.
uhhh 0? Well I guess 1 since I can count you now.
Me Too!
I like how the first result for a simple search of 'linux' returns a (probably biased) comparison between Linux and Windows, hosted by www.microsoft.com.
o l= mc&qt=linux&accoona+submit=Accoona+Search
OH, and the link is broken to boot!
I think I'll keep using google, thanks.
http://accoona.com/search?charset=utf-8&la=en&c
http://www.suse.de/~aj/linux_lfs.html
;)
Been in the stable kernel... for a while IIRC.
The boat left a while ago
An amazing 30 minutes of battery life.
'q' meaning quit is non obvious, but things like F1 meaning help are? You do have to make some assumptions about your target audience when writing technical documentation. I thing the general idea of 'q' meaning quit _is_ obvious.
And, next time you are in a manpage, you can try 'h' for help, but i guess that makes no sense either.
I figgure it by apropos->man fd->man mount.
Yes It could have taken me many more commands to get there, and i can use more than 3 clicks in windows to do even very simple things. IIRC the article i was refrencing didnt mean "If a user cant find it in 3 clicks, it sucks" it was "everything should be reachable by 3 clicks." So, 3 commands. deal.
Can't post that blog article here? I don't blame you the /. trolls would flame you to death in about 2 seconds.
;)
IMO The people that need to grow up are the people that dont put any effort into finding something out for themselves, and get all pissy when someone explains to the how to get information for themselves, and yes, RTFM, STFW and etc are not valid pieces of advice.
There have been plenty of times that my questions were ignored, or answered back with snyde remarks. It is just par for the course. Go on the msdn forums sometimes, you'll find plenty of tools there too.
If you think it is common practice to give your grandma a computer with linux installed, that boots to a CLI, you sir are the one kidding.
And, as a couple posts down, You think that if it was Windows on that strange shiny new thing you gave to grandma, she'd be up and running as soon as she hits the power button? Any thing new requires a at least minimum effort to be able to use it.
I had to hold my fathers hand to do the most simple of tasks in Windows the first couple of times (Read E-Mail, search the web, make the text bold in Word.) Are you going to tell me that Windows is not ready for the desktop because he wasn't able to do whatever he wanted with nil in the way of training, or of seeking help?
What, the attitude of "please, someone hold my hand?" come on dude, these are basic concepts, that exist in DOS as well as linux. $command /? in DOS dosen't work? If you are unwilling to look at the help screen/manpage of a command, then I am unwilling to do it for you.
Done:
http://www.tldp.o rg/
maybe you should check out the apropos command
hrm fd looks interesting...
So, with this route, I am 3 commands away from what I want. I seem to recall some design essay about everything being at most 3 clicks. Looks good to me.
$command -h
$command --help
man $command
info $command
http://www.google.com/search?q=$command
use brain;
I'm not even supposed to be here today!