# Sdkenv.sh scripts check for system-shell not beeing \`dash\`

**URL:** <https://forums.windriver.com/t/sdkenv-sh-scripts-check-for-system-shell-not-beeing-dash/1207>\
**Category:** VxWorks SDK\
**Created:** [December 27, 2025, 1:38pm UTC](https://forums.windriver.com/t/sdkenv-sh-scripts-check-for-system-shell-not-beeing-dash/1207 "2025-12-27T13:38:47Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![infohoschie](https://avatars.discourse-cdn.com/v4/letter/i/ecc23a/32.png) [@infohoschie](https://forums.windriver.com/u/infohoschie)\
**Post date:** [December 27, 2025, 1:38pm UTC](https://forums.windriver.com/t/sdkenv-sh-scripts-check-for-system-shell-not-beeing-dash/1207/1 "2025-12-27T13:38:47Z")

</div>

Why does the script **`sdkenv.sh`** expect the system shell not to be **`dash`**?  
The shell of the user who is using the SDK is explicitly set to **`bash`**.  
Why should the VxWorks SDK rely on this system-wide setting?  
Current versions of Debian and Ubuntu do not allow the “system shell” to be modified manually without changing the symlink. This, in turn, can negatively affect overall system behavior.

---

<div class="post-metadata">

**Author:** ![dan.milea](https://avatars.discourse-cdn.com/v4/letter/d/4bbf92/32.png) [@dan.milea](https://forums.windriver.com/u/dan.milea)\
**Post date:** [December 27, 2025, 7:51pm UTC](https://forums.windriver.com/t/sdkenv-sh-scripts-check-for-system-shell-not-beeing-dash/1207/2 "2025-12-27T19:51:17Z")

</div>

The VxWorks host tools for Linux are using bash, and the SDK inherits the same configuration. This doesn’t mean dash will not work in any circumstances, it may just mean that the tools have not been validated using dash as the default shell.

---

<div class="post-metadata">

**Author:** ![infohoschie](https://avatars.discourse-cdn.com/v4/letter/i/ecc23a/32.png) [@infohoschie](https://forums.windriver.com/u/infohoschie)\
**Post date:** [December 28, 2025, 3:50pm UTC](https://forums.windriver.com/t/sdkenv-sh-scripts-check-for-system-shell-not-beeing-dash/1207/3 "2025-12-28T15:50:53Z")

</div>

But why depending on the system-setting nad not the default setting?

Furthermore the script exits early with return 1.  
Maybe a printing a warning and continuing would be sufficient.

If any Wind River Shell-Script strictly depends on bash it should place `#!/bin/bash`instead of `/bin/sh`

Regards Thomas

---

<div class="post-metadata">

**Author:** ![dan.milea](https://avatars.discourse-cdn.com/v4/letter/d/4bbf92/32.png) [@dan.milea](https://forums.windriver.com/u/dan.milea)\
**Post date:** [December 29, 2025, 8:14am UTC](https://forums.windriver.com/t/sdkenv-sh-scripts-check-for-system-shell-not-beeing-dash/1207/4 "2025-12-29T08:14:29Z")

</div>

Thank you for your suggestions. Feel free to comment or update the shell validation check in sdkenv.sh. If you encounter any issues, please document them and share them on this forum.

Thanks!  
Dan
