# Chsh command not avaiable

**URL:** <https://universal-blue.discourse.group/t/chsh-command-not-avaiable/4382>\
**Category:** Bluefin\
**Created:** [October 4, 2024, 3:01pm UTC](https://universal-blue.discourse.group/t/chsh-command-not-avaiable/4382 "2024-10-04T15:01:58Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![kylegospo](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/kylegospo/32/375_2.png) [@kylegospo](https://universal-blue.discourse.group/u/kylegospo)\
**Post date:** [October 5, 2024, 6:23pm UTC](https://universal-blue.discourse.group/t/chsh-command-not-avaiable/4382/11 "2024-10-05T18:23:51Z")

</div>

> [@reisaraujo-miguel](#):
>
> It seems chsh was removed on purpose.

That’s correct, chsh is dangerous on atomic because you could install a new shell, chsh to it, and then roll back to a previous image without that shell. We pulled it partly because Fedora was thinking of doing the same, and partly to cut down on support requests from users doing just that. Ptyxis has a way to change the shell, as does bluefin/bazzite-cli. Glad you found a work around!

---

_[View the full topic](https://universal-blue.discourse.group/t/chsh-command-not-avaiable/4382)._
