After running nuke my terminal is unnaccessible
Closed this issue · 1 comments
elsom25 commented
Ran nuke --all --force
, and now receive:
Last login: Wed Oct 7 21:04:54 on ttys001
login: /opt/boxen/homebrew/bin/bash: No such file or directory
[Process completed]
I've renamed my .profile
to .profile.bak
to ensure it's not being loaded and am not sure what else I can do, particularly without access to a terminal.
and for completeness,
[1:8687]-$ l. ~
./ .bash_ps1@ .docker/ .guard_history .profile.bak@ .v8flags.4.5.103.30.jesse.json
../ .boot2docker/ .dropbox/ .heroku/ .pry_history .vagrant.d/
.DS_Store .boot2dockerscripts@ .exercism.json .netrc .pryrc@ .vim/
.Trash/ .cache/ .gem/ .node-gyp/ .rnd .viminfo
.bash_aliases@ .config/ .gitconfig@ .npm/ .ssh/
.bash_history .cups/ .gitignore_global@ .pow@ .subversion/
As a temporary workaround, I can access a shell via bash --noprofile
, though the problem of shell being broken after a boxen nuke is still not so great...
elsom25 commented
And in the off chance anyone from google comes here:
chsh -s /bin/bash
I had changed my default shell to /opt/boxen/homebrew/bin/bash
Alas.