Cloud Native Computing Foundation Announces JFrog as Gold Member

  • DevOps Expert Joins CNCF to Further Best Practices for Cloud Native Operations

    SAN FRANCISCO – December 4, 2017 – The Cloud Native Computing Foundation (CNCF), which sustains and integrates open source technologies like Kubernetes and Prometheus, today announced that JFrog joined the Foundation as a Gold Member. A big proponent of open source and cloud native technologies, JFrog leverages technologies like Kubernetes to help its more than 4,000 customers build and release software in a fast, reliable, and secure manner.

    “CNCF is excited to have JFrog on board as a Gold Member, further embracing their commitment to open source and the cloud native community,” said Dan Kohn, Executive Director of the Cloud Native Computing Foundation. “JFrog has been a part of the open source community for some time and has implemented many cloud native technologies. We appreciate JFrog investing engineering time and financial resources into CNCF projects and initiatives.”

    Operated from California, Seattle, Israel, India, Spain and France, the company helps organizations of all sizes to improve software releases. Created by open source developers for the open source community, JFrog’s product and engineering teams are dedicated to OSS technologies and working on cloud native projects. JFrog is a significant contributor in the developer community with the offer of an open source version of Artifactory, the universal binary repository, and fully sponsored cloud infrastructure and commercial accounts for OSS projects with Bintray, the universal binary distribution platform. With over 2 billion downloads per month on Bintray and 60,000 OSS Artifactory servers, JFrog provides the community with the entire lifecycle for effective binary management.

    As the company joins CNCF it will introduce support for Helm repositories in Artifactory with the next version release scheduled for December. Consistent with the goal to provide the only Universal artifact support, JFrog Artifactory will now enable developers to build with Kubernetes open-source system. JFrog has been using Kubernetes for development of its products, as well as actively migrating hosted operations to Kubernetes; and the addition of Helm support is considered the next logical step for JFrog and for the community.

    “We know that ‘cloud native’ is more than a buzzword, it’s all about better software design and implementation,” said Kit Merker, JFrog VP of Business Development and supporter of Kubernetes open source project during his days as Google product manager for Kubernetes. “For us, joining CNCF is more than just supporting the open source community, it also signals that we are committed to bringing real engineering power to these important projects. Our goal is to contribute significantly to Kubernetes and related projects using our practical experience of creating rapid-delivery software systems.”

    As a CNCF member, JFrog plans to allocate resources to support documentation and maintenance of CNCF projects, as well as help promote best practices for cloud native operations.

    Additional Resources

    About Cloud Native Computing Foundation

    Cloud native computing uses an open source software stack to deploy applications as microservices, packaging each part into its own container, and dynamically orchestrating those containers to optimize resource utilization. The Cloud Native Computing Foundation (CNCF) hosts critical components of cloud native software stacks including Kubernetes, Fluentd, linkerd, Prometheus, OpenTracing, gRPC, CoreDNS, containerd, rkt, CNI, Envoy, Jaeger, Notary, and TUF. CNCF serves as the neutral home for collaboration and brings together the industry’s top developers, end users and vendors – including the six largest public cloud providers and many of the leading private cloud companies. CNCF is part of The Linux Foundation, a nonprofit organization. For more information about CNCF, please visit:

    About JFrog:

    With more than 4,000 customers and over 2 billion downloads per month on its binaries hub, JFrog is the leading universal solution for the management and distribution of software binaries. JFrog’s four products, JFrog Artifactory, the Universal Artifact Repository; JFrog Bintray, the Universal Distribution Platform; JFrog Mission Control, for Universal DevOps Flow Management; and JFrog Xray, Universal Component Analyzer, are used by Dev and DevOps engineers worldwide and are available as open-source, on-premise, and SaaS cloud solutions. Customers include some of the world’s top brands, such as Amazon, Google, Uber, Netflix, Twitter, Cisco, Oracle, Adobe, Salesforce, VMware, and Slack. The company is privately held and operated from California, Seattle, Israel, India, and France. More information can be found at

    “Cloud Native Computing Foundation”, “CNCF” and “Kubernetes” are registered trademarks of The Linux Foundation in the United States and other countries. “Certified Kubernetes” and the Certified Kubernetes design are trademarks of The Linux Foundation in the United States and other countries.

    Media Contact

    Natasha Woods

    The Linux Foundation

    (415) 312-5289

    The post Cloud Native Computing Foundation Announces JFrog as Gold Member appeared first on The Linux Foundation.

Tmux Commands

screen and tmux

A comparison of the features (or more-so just a table of notes for accessing some of those features) for GNU screen and BSD-licensed tmux.

The formatting here is simple enough to understand (I would hope). ^ means ctrl+, so ^x is ctrl+x. M- means meta (generally left-alt or escape)+, so M-x is left-alt+x

It should be noted that this is no where near a full feature-set of either group. This - being a cheat-sheet - is just to point out the most very basic features to get you on the road.

Trust the developers and manpage writers more than me. This document is originally from 2009 when tmux was still new - since then both of these programs have had many updates and features added (not all of which have been dutifully noted here).

Action tmux screen
start a new session tmux OR
tmux new OR
tmux new-session
re-attach a detached session tmux attach OR
tmux attach-session
re-attach an attached session (detaching it from elsewhere) tmux attach -d OR
tmux attach-session -d
screen -dr
re-attach an attached session (keeping it attached elsewhere) tmux attach OR
tmux attach-session
screen -x
detach from currently attached session ^b d OR
^b :detach
^a ^d OR
^a :detach
rename-window to newname ^b , <newname> OR
^b :rename-window <newn>
^a A <newname>
list windows ^b w ^a w
list windows in chooseable menu ^a "
go to window # ^b # ^a #
go to last-active window ^b l ^a ^a
go to next window ^b n ^a n
go to previous window ^b p ^a p
see keybindings ^b ? ^a ?
list sessions ^b s OR
tmux ls OR
tmux list-sessions
screen -ls
toggle visual bell ^a ^g
create another window ^b c ^a c
exit current shell/window ^d ^d
split window/pane horizontally ^b " ^a S
split window/pane vertically ^b % ^a |
switch to other pane ^b o ^a <tab>
kill the current pane ^b x OR (logout/^D)
collapse the current pane/split (but leave processes running) ^a X
cycle location of panes ^b ^o
swap current pane with previous ^b {
swap current pane with next ^b }
show time ^b t
show numeric values of panes ^b q
toggle zoom-state of current pane (maximize/return current pane) ^b z
break the current pane out of its window (to form new window) ^b !
re-arrange current panels within same window (different layouts) ^b [space]
Kill the current window (and all panes within) ^b killw [target-window]
  • Use the same script for updating/ upgrading

    Make sure to change the versions to the latest releases:

    #!/bin/bash set -e bpcver=4.2.1 bpcxsver=0.57 rsyncbpcver=

    Scroll through the script, know what you are doing.

    Uncomment the upgrade section(s) and comment out the install section(s)

    read more
  • Again running smartctl after all is said and done:

    smartctl --all /dev/sda

    ddrescue-smartctl-after-rescue.png ddrescue-smartctl-2.png

    Yet an old drive in itself, I run the wheels off of them, and monitor regularly as anyone should.

    read more