The Linux Foundation and the GDPR

  • As you may be aware, the European Union’s General Data Protection Regulation (GDPR) is leading to many changes in the regulatory framework for protecting personal data of EU individuals. You may find it useful to review our “Summary of GDPR Concepts for Free and Open Source Software Projects” white paper. The Linux Foundation will be compliant with the GDPR as of its effective date of May 25, 2018. The revised policies described below go into effect on this date.

    Like many other global organizations, The Linux Foundation has been working hard to review the ways that it collects and processes personal data, in preparation for the effectiveness of the GDPR on May 25, 2018. As part of this, we’ve updated our policies and have enhanced the ways that we protect the personal data of people who interact with The Linux Foundation and our projects and services. We wanted to explain a few of the updates and changes we’re making.

    We have updated our Privacy Policy to clarify and improve privacy protections and align with GDPR requirements. Briefly, the updated policy includes the following changes:

    • Clearer and more specific language. Our new Privacy Policy is easier to read and uses plain language where possible.
    • More details about our privacy practices. We provide more information about the types of personal data that we collect; the purposes for which we collect and process it; and the instances where data may be shared with third parties.
    • Information on your ability to control your personal data. We outline details about your legal rights under the GDPR regarding (1) how to get specific information about the processing of your personal data, and (2) how to control the ways that your personal data is processed.

    Please take a minute to read the Privacy Policy itself, as the above points are just a quick overview of a few of the main changes.

    We have also created a Cookies Policy to clarify how The Linux Foundation’s websites use cookies. The updated policy includes details about the specific types of cookies we use, a list of third-party cookies used on our sites, and information on how you can disable cookies if desired.

    We have taken other steps as well to ensure compliance with the GDPR. These include performing an analysis of how we collect, process and transfer personal data throughout our services; documenting our lawful bases for this processing; updating internal processes and policies relating to the handling of personal data; and entering into data protection agreements with key third parties.

    If you have any questions, please feel free to reach out to us at

    The post The Linux Foundation and the GDPR 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]
  • Make ISO from DVD

    In this case I had an OS install disk which was required to be on a virtual node with no optical drive, so I needed to transfer an image to the server to create a VM

    Find out which device the DVD is:



    NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 465.8G 0 disk ├─sda1 8:1 0 1G 0 part /boot └─sda2 8:2 0 464.8G 0 part ├─centos-root 253:0 0 50G 0 lvm / ├─centos-swap 253:1 0 11.8G 0 lvm [SWAP] └─centos-home 253:2 0 403G 0 lvm /home sdb 8:16 1 14.5G 0 disk /mnt sr0 11:0 1 4.1G 0 rom /run/media/rick/CCSA_X64FRE_EN-US_DV5

    Therefore /dev/sr0 is the location , or disk to be made into an ISO

    I prefer simplicity, and sometimes deal with the fallout after the fact, however Ive repeated this countless times with success.

    dd if=/dev/sr0 of=win10.iso

    Where if=Input file and of=output file

    I chill out and do something else while the image is being copied/created, and the final output:

    8555456+0 records in 8555456+0 records out 4380393472 bytes (4.4 GB) copied, 331.937 s, 13.2 MB/s


    read more
  • Recreate postrgresql database template encode to ASCII

    UPDATE pg_database SET datistemplate = FALSE WHERE datname = 'template1';

    Now we can drop it:

    DROP DATABASE template1;

    Create database from template0, with a new default encoding:

    CREATE DATABASE template1 WITH TEMPLATE = template0 ENCODING = 'UNICODE'; UPDATE pg_database SET datistemplate = TRUE WHERE datname = 'template1'; \c template1 VACUUM FREEZE;

    read more