Posted by jpluimers on 2017/06/13
For my research list:
–jeroen
Posted in Development, Internet, MikroTik, Power User, RouterOS, routers, Scripting, Software Development | Leave a Comment »
Posted by jpluimers on 2017/06/08
curl Statistics Made Simple: httpstat is a single file Python script that has no dependency and is compatible with Python 3.
Source: curl Statistics Made Simple: httpstat [WayBack]
via: Using curl to get the HTTP header, and httpstat script to add connection stats (timings) to it. – Jean-Luc Aufranc – Google+ [WayBack]
Source: Using curl to get the HTTP header, and httpstat script to add connection stats…
Posted in *nix, cURL, Development, Power User, Python, Scripting, Software Development | Leave a Comment »
Posted by jpluimers on 2017/06/08
The RouterOS scripting language you can use on Mikrotik device immediately shows it’s origin: the console.
As promised some links to questions I asked:
:global convert ({});/system script entries to the file system, but due to a stupid 4096 length string export issue (causing the dreaded “failure: new contents too long” error), scripts longer than 4096 bytes will not even be written truncated. Since LUA got ditched and never re-introduced, LUA is not a workaround either and splitting into multiple files is impractical./system script` entries::foreach scriptId in [/system script find] do={ :local scriptSource [/system script get $scriptId source]; :local scriptSourceLength [:len $scriptSource]; :local scriptName [/system script get $scriptId name]; :put "$scriptSourceLength bytes: '$scriptName'" }Some questions by others that were also extremely useful:
:if ([:len [:find "abcd" "x"]] > 0) do={:put "Found";} else={:put "Not Found";};:return from a function when inside a loop, but that’s not the same (for instance compare C# break versus return or Delphi break versus exit).And a few observations:
:local myFunc do={:put "hello from function"}
$myFunc
# output:
# hello from function
–jeroen
Posted in Development, Internet, MikroTik, Power User, RouterOS, routers, Scripting, Software Development | 1 Comment »
Posted by jpluimers on 2017/06/07
When switching my DHCP to a Mikrotik CCR1009, both the AP7920 and AP7921 failed to get IP addresses. The APC7921 would look bounce between waiting and offered states like this:
The cause is the need of DHCP Option 43 (Vendor Class Identifier) specified in RFC2132 – based on [WayBack] RFC 2131 – Dynamic Host Configuration Protocol and [WayBack] RFC 1533 – DHCP Options and BOOTP Vendor Extensions – which I found first via these links:
Posted in Development, Internet, MikroTik, Power User, RouterOS, routers, Scripting, Software Development | 3 Comments »
Posted by jpluimers on 2017/06/01
The picture tricked me into thinking it was a Makefile for Tic-Tac-Toe, but it is in fact a 174 kilobyte makefile for Conways’ game of life which proofs that make macros are Turing complete.
Source: Makefile Assignments are Turing-Complete « null program
While running on my Mac, the recursivity will make it fail on lack of resources though.
If seen both these:
and
make[119]: /bin/sh: Resource temporarily unavailable
make[119]: *** wait: No child processes. Stop.
make[119]: *** Waiting for unfinished jobs....
make[119]: *** wait: No child processes. Stop.
–jeroen
Posted in Development, Makefile, Scripting, Software Development | Leave a Comment »
Posted by jpluimers on 2017/04/26
Printing Markdown with GitPrint
Simply view any Markdown file on GitHub, then in your URL bar replace the github.com part of the URL with gitprint.com — your markdown file will be rendered to a beautiful, printable PDF.
Try an example https://gitprint.com/jquery/jquery/blob/master/README.md
Every once in a while I feel like I’ve been living under a stone for years. Today is such a day as gitprint has been around since 2014 and I only noticed it until now.
It’s cool as it prints any github page (including Markdown, RestructuredText, etc) as a PDF file.
Notes:
Posted in Bookmarklet, Development, DVCS - Distributed Version Control, git, GitHub, jQuery, Software Development, Source Code Management, Web Browsers | Leave a Comment »
Posted by jpluimers on 2017/04/20
Note this works only when the VMs have VMware Tools installed (more on that below):
VMWare provides, not surprisingly, a built in tool for this, vmrun. It’s under
/Applications/VMware Fusion.app/Contents/Library/vmrunalthough it has moved around in other Fusion releases a bit.
🍺 vmrun list Total running VMs: 1 .docker/machine/machines/myvm.vmx
🍺 vmrun getGuestIPAddress ~/.docker/machine/machines/myvm.vmx 172.16.213.128
via: How do I find the IP address of a virtual machine using VMware Fusion? – Super User [WayBack]
vmrun [WayBack] is barely documented and most of is in PDF of which this is the most recent I could find: www.vmware.com/pdf/vix180_vmrun_command.pdf [WayBack]
Based on the above path, I added this to my ~/.bash_profile file:
alias vmrun='/Applications/VMware\ Fusion.app/Contents/Library/vmrun'
alias vmrun-list-running-VMs='vmrun list | grep vmx'
vmrun-list-ipv4-of-running-VMs()
{
vmrun-list-running-VMs | while read line ; do echo $line && vmrun getGuestIPAddress $line; done
}
Now I can do this:
$ vmrun-list-ipv4-of-running-VMs
/Users/jeroenp/VM/W81Entx64DelphiRegression.vmwarevm/W81Entx64.vmx
172.16.172.135
/Users/jeroenp/VM/diaspore-opensuse-Tumbleweed-x64.vmwarevm/diaspore-opensuse-Tumbleweed-x64.vmx
Error: The VMware Tools are not running in the virtual machine: /Users/jeroenp/VM/diaspore-opensuse-Tumbleweed-x64.vmwarevm/diaspore-opensuse-Tumbleweed-x64.vmx
$ vmrun-list-ipv4-of-running-VMs
/Users/jeroenp/VM/diaspore.opensuse-Tumbleweed-x64/diaspore.opensuse-Tumbleweed-x64.vmx
Error: Unable to get the IP address
/Users/jeroenp/VM/W81Entx64DelphiRegression.vmwarevm/W81Entx64.vmx
172.16.172.135
$ vmrun-list-ipv4-of-running-VMs
/Users/jeroenp/VM/diaspore.opensuse-Tumbleweed-x64/diaspore.opensuse-Tumbleweed-x64.vmx
Error: Unable to get the IP address
/Users/jeroenp/VM/W81Entx64DelphiRegression.vmwarevm/W81Entx64.vmx
172.16.172.135
$ vmrun-list-ipv4-of-running-VMs
/Users/jeroenp/VM/diaspore.opensuse-Tumbleweed-x64/diaspore.opensuse-Tumbleweed-x64.vmx
172.16.172.134
/Users/jeroenp/VM/W81Entx64DelphiRegression.vmwarevm/W81Entx64.vmx
172.16.172.135
$ vmrun-list-ipv4-of-running-VMs
/Users/jeroenp/VM/diaspore.opensuse-Tumbleweed-x64/diaspore.opensuse-Tumbleweed-x64.vmx
172.16.172.134
/Users/jeroenp/VM/W81Entx64DelphiRegression.vmwarevm/W81Entx64.vmx
172.16.172.142
These are the messages I observed:
Error: The VMware Tools are not running in the virtual machine: /Users/jeroenp/VM/diaspore-opensuse-Tumbleweed-x64.vmwarevm/diaspore-opensuse-Tumbleweed-x64.vmx
Error: Unable to get the IP address
172.16.172.135
The first one means a machine is running but has no VMware Tools installed. For an OpenSuSE machine you can install it with zypper install open-vm-tools, for other Linux systems read VMware Tools auf Ubuntu, Mint, CentOS oder openSUSE installieren | ITrig [WayBack]
Some more examples of vmrun for VMware Fusion are at Control VMware Fusion from the Command Line | James Reuben Knowles [WayBack]
–jeroen
Posted in *nix, bash, Development, Fusion, openSuSE, Power User, Scripting, Software Development, SuSE Linux, Tumbleweed, Virtualization, VMware | Leave a Comment »
Posted by jpluimers on 2017/04/18
Glueing together APIs requires working with JSON: parsing it, extracting it, transforming it. JQ is a fast, lightweight, flexible, CLI JSON processor, that does the job well. Learn how to use it by getting your hands dirty with a JSON blob that represents the open issues in the public Docker GitHub repository.
via: http://blog.librato.com/posts/jq-json – Joe C. Hecht – Google+
–jeroen
Source: http://blog.librato.com/posts/jq-json
Posted in bash, Development, JavaScript/ECMAScript, jq, JSON, Scripting, Software Development | Leave a Comment »
Posted by jpluimers on 2017/04/13
Cool: .bashrc generator: create your .bashrc PS1 with a drag and drop interface
–jeroen
http://bashrcgenerator.com/ – Joe C. Hecht – Google+
Posted in bash, Development, Scripting, Software Development | Leave a Comment »
Posted by jpluimers on 2017/04/13
How bad is the Windows command line really?
The Windows command line is bad. Very bad.
But it took until recently for old Windows versions – that out of the box had either no or poor PowerShell versions – to have slowly died.
So only now PowerShell finally has become an option that really works across all Windows versions I use. Go PowerShell!
–jeroen
Posted in Batch-Files, Development, PowerShell, Scripting, Software Development | Leave a Comment »
The Wiert Corner - irregular stream of stuff 