So, when is it important to write portable scripts?

 

what types of scripts should be as portable as possible?

When you're using them for your working environment, and you work (or could in the future) on different machines - AND, you don't want to have to rewrite your tools prior to getting down to work.

eg: a trash script / rm replacement

Mark Stewart:

...for my troubleshooting toolkit I assume I will only have vi and Korn shell. And I try to use commands that work on most flavors of Unix.

So, when is it important to write portable scripts?

what types of scripts should be as portable as possible?

When you're using them for your working environment, and you work (or could in the future) on different machines - AND, you don't want to have to rewrite your tools prior to getting down to work.

eg: a trash script / rm replacement

Mark Stewart:

...for my troubleshooting toolkit I assume I will only have vi and Korn shell. And I try to use commands that work on most flavors of Unix.

So, when is it important to write portable scripts?

what types of scripts should be as portable as possible?

When you're using them for your working environment, and you work (or could in the future) on different machines - AND, you don't want to have to rewrite your tools prior to getting down to work.

eg: a trash script / rm replacement

So, when is it important to write portable scripts?

what types of scripts should be as portable as possible?

When you're using them for your working environment, and you work (or could in the future) on different machines - AND, you don't want to have to rewrite your tools prior to getting down to work.

eg: a trash script / rm replacement

Mark Stewart:

...for my troubleshooting toolkit I assume I will only have vi and Korn shell. And I try to use commands that work on most flavors of Unix.