vagrant ssh
sudo
$ find /c/HashiCorp/Vagrant/embedded/gems/ -name 'vagrant'
/c/HashiCorp/Vagrant/embedded/gems/bin/vagrant
/c/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.2/bin/vagrant
/c/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.2/keys/vagrant
/c/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant
/c/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.2/test/unit/vagrant
vi
/c/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.2/bin/vagrant
# added comment только что
exit e.status_code if e.respond_to?(:status_code)
exit 255 # An error occurred with no status code defined
end
"/c/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.2/bin/vagrant" E212: Can't
open file for writing
Press ENTER or type command to continue
grep 'added comm' /c/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.2/bin/vagrant
# added comment ?????? ??? <-- не может браузер клипборд получить....
BTW
Could not find a suitable provider for rvm_system_ruby · Issue #2830 ...
https://github.com/puphpet/puphpet/issues/2830
Dec 13, 2018 - Could not find a suitable provider for rvm_system_ruby #2830. Open .... RVM GPG error on vagrant up with default settings #2831 · @Axel29
dowgrade to 2.0.2 это кочено очень далеко но там ЕмниП все тихр даано ?
With Ruby and friends *sometimes* old beats new