Technical books and notes: Difference between revisions

Revision as of 14:05, 15 April 2015

I want to run the Vagrant VM on some physical machine attached to my LAN,
I want the VM to have an interface (VirtualBox: Bridged Adapter) and its own IP address on the LAN;
the VM's OS is ubuntu;
its hostname is data-science-toolbox;
I want to access the OS 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 – that way it works.

Appendix A lists the command-line tools together with their home pages.

@@ Line 1: / Line 1: @@
 == Business/Publishing_and_Printing/Publishing/Books/Business/O'Reilly_and_Associates ==
 === Data Science at the Command Line ===
+==== running the Vagrant VM not just locally on some physical machine but … ====
 * I want to run the Vagrant VM on some physical machine attached to my LAN,
 * I want the VM to have an interface (VirtualBox: ''Bridged Adapter'') and its own IP address on the LAN;
@@ Line 12: / Line 13: @@
 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''.
+But I am starting the VM from the ''Oracle VM VirtualBox Manager'' – that way it works.
+==== installing the tools elsewhere ====
+Appendix A lists the command-line tools together with their home pages.