Technical books and notes: Difference between revisions
Jump to navigation
Jump to search
imported>Johayek |
imported>Johayek |
||
| Line 1: | Line 1: | ||
== Business/Publishing_and_Printing/Publishing/Books/Business/O'Reilly_and_Associates == | == Business/Publishing_and_Printing/Publishing/Books/Business/O'Reilly_and_Associates == | ||
=== Data Science at the Command Line === | === Data Science at the Command Line === | ||
I want to run the Vagrant VM on some physical machine somewhere within my LAN, | * I want to run the Vagrant VM on some physical machine somewhere within my LAN, | ||
let it have an interface (VirtualBox: ''Bridged Adapter'') and IP address on the LAN, | * let it have an interface (VirtualBox: ''Bridged Adapter'') and its own IP address on the LAN, | ||
it's called ''data-science-toolbox'', | * it's called ''data-science-toolbox'', | ||
and I access it from another machine on my LAN, | * and I access it from another machine on my LAN, not just from the machine, that hosts the VM: | ||
not just from the machine, that hosts the VM: | |||
<pre> | <pre> | ||
Revision as of 23:10, 11 April 2015
Business/Publishing_and_Printing/Publishing/Books/Business/O'Reilly_and_Associates
Data Science at the Command Line
- I want to run the Vagrant VM on some physical machine somewhere within my LAN,
- let it have an interface (VirtualBox: Bridged Adapter) and its own IP address on the LAN,
- it's called data-science-toolbox,
- and I access it from another machine on my LAN, not just from the machine, that hosts the VM:
$ ssh vagrant@data-science-toolbox
If I start the Vagrant VM through its ordinary interface, Vagrant complains about a NAT rule of this names already existing. But I am starting the VM from the Oracle VM VirtualBox Manager.