Technical books and notes: Difference between revisions
Jump to navigation
Jump to search
imported>Johayek |
imported>Johayek mNo edit summary |
||
Line 1: | Line 1: | ||
== Business/Publishing_and_Printing/Publishing/Books/Business/Manning == | |||
=== Minimal Perl === | |||
* http://www.manning.com/maher/ | |||
* … | |||
== 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 === |
Revision as of 04:02, 4 May 2015
Business/Publishing_and_Printing/Publishing/Books/Business/Manning
Minimal Perl
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 a strong 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 without complaint.
With a entry in $HOME/.ssh/config :
# from $HOME/.ssh/config : Host data-science-toolbox User vagrant
… the ssh command line is even shorter:
$ ssh data-science-toolbox
installing the tools elsewhere
Appendix A lists the command-line tools together with their home pages.