>It's for scripting commands that insist on prompting the user. e.g.
>
>yes | rm -iR ~/ 2>&1 /dev/null
>
>!!

Umm, why would you use iR with yes, when you can just use R?

Similarly, with the fsck thing...first you're using the command & forcing
it to ask...but then you're going on to force it to not wait for an answer.
Seems oxymoronic to me :)

So if it's piped through another command, will it automatically shut up
when that command's through asking? In using yes with no pipes, it just
scrolled the hell outta my telnet session.
Bikers don't *DO* taglines.