Dowload ConEmu:
https://conemu.github.io/

Download Git for Windows:

https://git-scm.com/download/win

Install Git using the default settings. You can change anything if you want, but dont need to this work.

Install ConEmu with the default settings too.

Now, let´s configure to the Git's Bash be the deafult in ConEmu.

Open the settings, press Win + Alt + P, or follow this:

1

Click on the tab Startup, and select {Bash::Git bash} on Specified named Task. Like this:

2

Click on Save settings and close ConEmu.

Open it again and it will start with the Git bash. There you can use SSH as your wish.

3

 

I bought a motherboard from MSI, Z270 Gaming M5. One of the features that make the choice, was the optical audio output.

I tryed to make it work, but was only working in Stereo mode. DTS and Dolby Digital that is the 5.1 modes, was hidden.

After some hours tying to resolve, I was thinking that was the driver that was wrong, but I found the solution.

Seems that my brand new and expensive motherboad dont have DTS or Dolby license, than the driver wouldnt show it to select.

But in a PC WORLD, where everything is possible, I found a workaround. Let's hack the driver. :)

Download this patcher and unzip it: realtek.hd.sound.driver-patch.exe

Download your driver installer and unzip it.

Run the patcher and when you click the 'patch' button, it will open a file browser. Browse through your setup to find each of the two DLLs RltkAPO64.dll and RltkAPO.dll. They are probably in a folder named 'WIN64'.

Screenshot_1 Screenshot_2

You need to make this two times. One for each file. Make one, close the patch and open again.

Run setup.exe and install as per normal. That means reboot when it says.

Now you can select 5.1 output on the SPDIF.

Screenshot_3

Enjoy your surround sound.

 

hdparm is a good place to start.

sudo hdparm -Tt /dev/sda

/dev/sda:
Timing cached reads:   12540 MB in  2.00 seconds = 6277.67 MB/sec
Timing buffered disk reads: 234 MB in  3.00 seconds =  77.98 MB/sec

sudo hdparm -v /dev/sda will give information as well.

dd will give you information on write speed. If the drive doesn't have a file system use of=/dev/sda. Otherwise, mount it on /tmp and write then delete the test output file.

sudo dd if=/dev/sdb1 of=/media/USBHDD1/output bs=80 k count=10k; rm -f /media/USBHDD1/output

10240+0 records in
10240+0 records out
83886080 bytes (84 MB) copied, 1.08009 s, 77.7 MB/s

hukl$ script/server -h
=> Booting Mongrel (use 'script/server webrick' to force WEBrick)
Usage: server [options]
    -p, --port=port                  Runs Rails on the specified port.
                                     Default: 3000
    -b, --binding=ip                 Binds Rails to the specified ip.
                                     Default: 0.0.0.0
    -d, --daemon                     Make server run as a Daemon.
    -e, --environment=name           Specifies the environment to run
                                     this server under
                                     (test/development/production).
                                     Default: development

    -h, --help                       Show this help message.

 

sudo rails server webrick -b 0.0.0.0 -p 3001 -d

How to turn off Xbox DVR through the Registry Editor

If you do not have an Xbox account and are not signed into the Xbox App you can disable Xbox DVR by using the Registry Editor.

Note: This process is more advanced and is not recommended for novice users.

  1. Open Registry Editor (Run > regedit)
  2. Navigate to HKEY_CURRENT_USER\System\GameConfigStore
  3. Set the value of DWORD "GameDVR_Enabled" to 0
  4. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\
  5. Create key "GameDVR".
  6. Create DWORD 32bit called "AllowGameDVR" and set to 0
  7. Restart your computer.

Or download this register file, execute and restart:

DisableGameDVR

Installing Ruby:

 

sudo apt-get install -y openssl libreadline6-dev git-core zlib1g libssl-dev libpq-dev 

sudo apt-get install -y libyaml-dev libsqlite3-dev sqlite3

sudo apt-get install -y libxml2-dev libxslt-dev

sudo apt-get install -y autoconf automake libtool bison

cd /usr/src/
sudo wget http://cache.ruby-lang.org/pub/ruby/2.4/ruby-2.4.0.tar.gz
sudo tar -xvzf ruby-2.4.0.tar.gz
cd ruby-2.4.0
sudo ./configure --enable-shared --with-openssl-dir=/usr/bin --disable-install-doc --disable-install-rdoc --disable-install-capi 
sudo make install

Before compile: Thu 19 Jan 05:11:11 BRST 2017

After compile: Thu 19 Jan 05:30:19 BRST 2017

It takes around 20 minutes to compile.

Installing Rails without the docs:

sudo gem install rails --no-ri --no-rdoc

you can make it default o not install rubygems documentation:

sudo echo "gem: --no-ri --no-rdoc" >> ~/.gemrc

 

Installing the PostgreSQL:
 

Step 1: Update and Install Packages

First, go ahead and update your Pi's packages:

sudo apt-get update

Once this is finished, you can run the following command to grab and install PostgreSQL:

sudo apt-get install postgresql-9.4

It may take a bit to complete, but once it's done, confirm the installation:

which psql

You should get a result like this:

pi@raspberrypi:~ $ which psql  
/usr/bin/psql

You should now have a fully functional PostgreSQL database server on your Pi! It's that easy!

In the next steps, we'll configure this server to allow access from external clients (i.e. other computers running a server manager, such as pgAdmin).

Step 2: Modify Configuration

By default, PostgreSQL is configured to only allow access to it's databases from the same machine. This is fine for testing, but our aim is to have a centralized, locally accessible database server. To open access for other machines, we'll need to modify a few configuration files.

First, let's modify the pg_hba.conf file. This controls client authentication and is, by default, configured to only allow local access. Before we make any edits, however, we'll want to create a backup of our default configuration:

sudo cp /etc/postgresql/9.4/main/pg_hba.conf /etc/postgresql/9.4/main/pg_hba.conf.bak

Then, enter the following to open the file for editing:

sudo nano /etc/postgresql/9.4/main/pg_hba.conf

At the end of this file, enter the following line:

host     all     all     192.168.0.0/24     md5  

This will allow access from users on our local network (i.e. any client with a 192.168.0.* IP address.

NOTE: You may need to change the first part (192.168) if your router assigns a different network address (like 129.144).

To save your changes to the pg_hba.conf file, enter Ctrl+Xy, and Enter.

Next, we'll need to modify the main postgresql.conf configuration file to allow access from IP addresses other than localhost. But first, make a backup of this file before proceeding:

sudo cp /etc/postgresql/9.4/main/postgresql.conf /etc/postgresql/9.4/main/postgresql.conf.bak

And then:

sudo nano /etc/postgresql/9.4/main/postgresql.conf

And change the following line:

listen_addresses = 'localhost'  

To:

listen_addresses = '*'  

/etc/init.d/postgresql restart

This will allow the PostgreSQL server to accept connections from any IP address. In combination with the changes we made to the pg_hba.conf file, this should allow any clients on the local network access to the server, while still protecting from outside requests. As explained on StackOverflow:

listen_addresses controls which IPs the server will answer on, not which IPs the server will permit connections to authenticate from. It's entirely reasonable and normal to use listen_addresses '*' so the server will accept incoming connections on any ip assigned to an interface on the postgresql server host, while using pg_hba.conf to control access at a finer grained level for which IPs the server will accept logins from for specific databases and users.