certainly not everything is the same, some nsh versions of commands behave differently from native versions (sed for example). I think it would be much simpler to answer your question if you had specific tasks in mind... those tasks can be tested for direct comparison.
The client does not have a complete list of tasks or commands that are used in the environment. This is why they have requested any information on what others may have come across as issues or potential issues utilizing NSH.
1 of 1 people found this helpful
since it's possible to nexec into a shell on the target, there's not much of a limitation there if you are going to use nsh as the access mechanism instead of ssh. also, one man's limitation is another's security feature
i would get a list of use cases from the customer and determine how nsh matches up. if they can't define their use cases it's going to be hard to determine what to evaluate about nsh.