The deadline for installing Windows 10 as a free upgrade is July 29. You may have heard Microsoft made it free because Microsoft sees it as a tool to gather information about you so they may sell it for profit. So it remains, nothing is rarely ever free and there always seems to be a catch. When upgrading, follow these steps to minimize Microsoft’s snooping into your life.
When upgrading, you will first be given the option to customize your installation settings. If you go too fast, you’ll miss it. The customize settings is in small text at the bottom left. Choose that.
Next you will be presented with these screens. Make the choices shown below.
You don’t want Cortana.
Be sure to choose your default apps yourself.
After upgrading, download, install, and run ShutUp10 choosing the recommended settings:
Some time ago Adobe open sourced their Flex programming language over to Apache. I have some old Adobe Flex based programs that I wanted to move over to using the new Apache Flex. After downloading the new SDK, I tried to compile the Flex source code, and I was presented the following error message:
Error: unable to open '{playerglobalHome}/11.1/playerglobal.swc
The fix for this error is to go into the Apache Flex SDK installation directory and do the following.
Finally, edit the env.properties file and find the env.PLAYERGLOBAL_HOME setting. Change it to the path that contains the :
123456789101112131415
#
# PLAYERGLOBAL_HOME is a directory which contains one or more subdirectories.
# The name of each subdirectory corresponds to a supported target player version and
# in each of the subdirectories is the playerglobal.swc that corresponds to that target
# player. The default
#
# For this sample directory structure, set PLAYERGLOBAL_HOME to the full path of the
# player directory.
#
# - player (dir)
# - 11.1 (dir)
# playerglobal.swc (file)
#
#env.PLAYERGLOBAL_HOME=
env.PLAYERGLOBAL_HOME=/home/john/apache-flex-sdk-4.15.0-bin/frameworks/libs/player/
You’re done. To test this you can compile the sample program below.
Use the following command to compile:
mxmlc -compiler.optimize -compiler.as3 FlashVersion.mxml
You can use the linux scheduler cron to automate backups of your postgres database. First as root, you’ll want to log in as the postgres user since we’ll be doing a number of things in that account:
su - postgres
Assuming you have a database named “mydb”, lets set up a small script in the postgres account. On Ubuntu & Linux Mint the account is in /var/lib/postgresql, and on Red Hat & CentOS you’ll find it in /var/lib/pgsql. For now, lets assume Ubuntu. Here is the script:
Make sure you give your script execute permissions:
chmod 755 db_backup.sh
You also want to create the backups directory where your sql dump will be archived:
mkdir backups
Next you’ll need to set up our postgres credentials in a .pgpass file:
/var/lib/postgresql/.pgpass
1
localhost:5432:mydb:postgres:dbPa$$w0Rd
You will need to set the parmissions for .pgpass to 600.
chmod 600 .pgpass
Also, since cron will run as root, you’ll need to copy the .pgpass file over to root’s home directory:
sudo cp .pgpass ~root
Finally, you’ll want to run “crontab -e” as root to schedule when your new backup script will run. This entry will have the system run the script at 00:00:00 every day:
You can create a self signed server certificate and a server key for Tomcat without having to go through a certificate authority. First, create the certificate and key:
<!-- Define a SSL Coyote HTTP/1.1 Connector on port 8443 --><Connectorprotocol="org.apache.coyote.http11.Http11Protocol"port="8443"maxThreads="200"scheme="https"secure="true"SSLEnabled="true"keystoreType="PKCS12"keystoreFile="/var/lib/tomcat7/conf/my_cert.p12"keystorePass="djEwuDysjSIdc88w3"clientAuth="false"sslProtocol="TLS"/>
Finally, edit Tomcat’s web.xml, at the bottom add a security restraint to force all connections to use HTTP/s: