Useful man pages in your browser

2017/12/21

A new useful *nix tool popped up in my Twitter timeline a while back.

http://tldr.sh/

Lede says Simplified and community-driven man pages and it does what it says on the tin.

If you’re a *nix admin you know the drill of looking up man pages for *nix tools. You’re solving some problem and need to grok an *nix command options and/or refer to a sample of how the tool is used. man {toolname} is the way to do it.

Frequently though the result is usually page and pages of esoteric information about the tool most of which you will never learn and will take you a lot of time to wrap your brain around. Sometimes there will be examples, waaay at the bottom of the page and often those usage examples are pretty light on information.

This is where http://tldr.sh/ comes in. Put your *nix tool name into the sample at https://tldr.ostera.io/ and it will display useful help. Example: https://tldr.ostera.io/tar

But it doesn’t end there. The page also has many community contributed clients. Scroll down the page at http://tldr.sh/ for the full list.

My favourite use of it is to add the https://tldr.ostera.io/ as a search provider in your browser. Chrome in my case. Open your Chrome settings and add a search engine with the config as below.

Screen Shot 2017-12-21 at 11.36.16

Now, in any search bar in Chrome you can type tldr {toolname} eg tldr tar and it will display the results right there for you. A convenient way to get useful information about *nix tools.

Advertisements

“Shockwave Flash has crashed” workaround for vSphere Web (Flash) Client | virtuallyGhetto

2017/10/17

Im using the vSphere Web Client everyday at the moment and will also preference the HTML5 version over the Flash (phtoowe) version.

Chrome 61.0.3163.100 breaks Flash though due to a patch for an undisclosed zero-day which was in use in the wild. Impacts Chrome on Mac and Windows.

See the post below from William Lam over at VMW.

On Saturday, I started to notice that logins to the vSphere Web (Flex) Client stopped working with Google Chrome. Upon a successful logon, it would immediately crash with “Shockwave Flash has…

Source: “Shockwave Flash has crashed” workaround for vSphere Web (Flash) Client | virtuallyGhetto


Adding your vCenter Web Client as a search provider in Chrome

2017/09/13

Most browsers these days offer a function that allows you to add other search engines to them. This function allows you to quickly search for stuff directly from your web browsers search field instead of having to open up the site directly, type in what you want and press enter.

In this article I’m going to show describe how to add your vCenter 6.5U1 HTML5 client as a custom search engine in Google Chrome.

This will allow you to search for vCenter objects directly from Chrome without first opening the HTML5 Web Client.

What you need

  • Access to an HTML5 vCenter Web Client (vCenter 6.5U1 on the VCSA was used to write this.)
  • Google Chrome (Chrome 60 was used at the time this was written)

Find your vCenter Web Client Search URL

  • Browse to your HTML5 vCenter Web Client and sign in. Its usually something like ​https://{FQDN}/ui` where {FQDN} is the URL for your vCenter Web Client.
  • From the banner at the top of the page, click on `Menu` and select `Search`.
  • Enter the name of a VM you want to search for and press `Search`.
  • Copy the URL from the address bar in Chrome. In this example we have something like this. I’ve replaced https://{FQDN}/ui/#?extensionId=vsphere.core.search.domainView&query={SEARCHTERM}&searchType=simple

Add a custom search provider to Chrome

Testing

  • Open a new Chrome tab or Window, enter your keyword and the object name you want to search for.
  • Chrome will return the vCenter Web Client search page with the term you entered.
  • $profit.

Finding which proxy is used by MacOS when autoconfiguration is used.

2016/11/15

Problem: I wanted to know what proxy my Mac was using for Internet access.

The advanced settings in the Network cdev had Proxies set to “Auto Proxy Discovery” however I could not find a way to make my Mac tell me what proxy servers it had discovered and was using.

Solution: Chrome has a nifty command that will cause it to output its proxy configuration. Enter the following into the address bar.

chrome://net-internals/#proxy