NLinker

Install the latest environment

Dec 24th, 2019
245
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
Rust 3.29 KB | None | 0 0
  1. https://sketchfab.com/3d-models/hydra-animated-4d05aa5290e448919bb6876b5da607b4
  2.  
  3. https://github.com/lopopolo/punchtop
  4. https://github.com/mvlabat/pirust
  5. https://github.com/braincow/digitransit-rt
  6. https://github.com/hyperium/hyper
  7. https://tokio.rs/docs/getting-started/hello-world/
  8. https://github.com/daogangtang/learn-tokio
  9. https://www.reddit.com/r/rust/comments/bgr7qe/stdfuturefuture_stabilized_in_136/
  10. https://github.com/Nemo157/embrio-rs
  11. https://github.com/tower-rs/tower-grpc/tree/ea4d6fd95563ae54d0ec900ed01ce0e44b46e404
  12.  
  13.  
  14. https://launchpad.net/~tiagohillebrandt/+archive/ubuntu/vagrant
  15.  
  16. sudo add-apt-repository ppa:tiagohillebrandt/vagrant
  17. sudo apt update
  18.  
  19. sudo apt install virtualbox-6.1
  20. suod apt install vagrant
  21.  
  22. ~/w/Vagrantfiles ❯❯❯ vagrant provision --provision-with=deploy-managed-hosts adm
  23. WARNING: Vagrant has detected the `vagrant-triggers` plugin. This plugin conflicts
  24. with the internal triggers implementation. Please uninstall the `vagrant-triggers`
  25. plugin and run the command again if you wish to use the core trigger feature. To
  26. uninstall the plugin, run the command shown below:
  27.  
  28.   vagrant plugin uninstall vagrant-triggers
  29.  
  30. Note that the community plugin `vagrant-triggers` and the core trigger feature
  31. in Vagrant do not have compatible syntax.
  32.  
  33. To disable this warning, set the environment variable `VAGRANT_USE_VAGRANT_TRIGGERS`.
  34. ==> adm: Running provisioner: deploy-managed-hosts (shell)...
  35.     adm: Running: /tmp/vagrant-shell20191224-22546-80febc.sh
  36.     adm: /tmp/vagrant-shell: line 3: iml: command not found
  37. The SSH command responded with a non-zero exit status. Vagrant
  38. assumes that this means the command failed. The output for this command
  39. should be in the log above. Please read the output to determine what
  40. went wrong.
  41. ~/w/Vagrantfiles ❯❯❯                                                                                                                                                          
  42.  
  43. ~/w/Vagrantfiles ❯❯❯ vagrant provision --provision-with=deploy-managed-hosts adm
  44. ==> adm: Running provisioner: deploy-managed-hosts (shell)...
  45.     adm: Running: /tmp/vagrant-shell20191224-23085-1wj4362.sh
  46.     adm: /tmp/vagrant-shell: line 3: iml: command not found
  47. The SSH command responded with a non-zero exit status. Vagrant
  48. assumes that this means the command failed. The output for this command
  49. should be in the log above. Please read the output to determine what
  50. went wrong.
  51. ~/w/Vagrantfiles ❯❯❯
  52.  
  53. ~/w/Vagrantfiles ❯❯❯ vagrant provision --provision-with=deploy-managed-hosts adm
  54. ==> adm: Running provisioner: deploy-managed-hosts (shell)...
  55.     adm: Running: /tmp/vagrant-shell20191224-13207-w8cmlt.sh
  56.     adm: ✗ error sending request for url (https://adm.local/api/test_host/): operation timed out
  57. The SSH command responded with a non-zero exit status. Vagrant
  58. assumes that this means the command failed. The output for this command
  59. should be in the log above. Please read the output to determine what
  60. went wrong.
  61. ~/w/Vagrantfiles ❯❯❯ vagrant ssh
  62. [vagrant@adm ~]$ ls
  63. blockdevice_zfs.log
  64. [vagrant@adm ~]$ logout
  65. Connection to 127.0.0.1 closed.
  66. ~/w/Vagrantfiles ❯❯❯
  67.  
  68. ~ ❯❯❯ mountpoint -q -- /media/nick/My\ CDROM
  69. ~ ❯❯❯ echo $?
  70. 1
  71. ~ ❯❯❯ mountpoint -q -- /media/nick/UBUNTU\ 19_1
  72. ~ ❯❯❯ echo $?
  73. 0
Add Comment
Please, Sign In to add comment