And yes, this handles file names with spaces and other weird characters…ohh the joys of double quotes.
ls *.zip | while read i; do IFS="\n" echo "Starting on $i"; unzip -d "$i-extracted" "$i"; echo -en "Finished $i..\n"; done
This was fairly easy to do:
Edit the sources.list or necessary file in sources.list.d to use the new version “qiana” and also utilize “trusty” ubuntu packages: 2.
` apt-get update apt-get dist-upgrade apt-get upgrade
???
Profit!
Thanks tecmint!
This new site, Cipherli.st, allows you to get configurations for the major web server and proxy software suites to ensure they are using the most secure ssl/tls cipher settings for serving out sensitive content, or anything on port 443.
The configs are copy/pastable into your web server configuration. Be sure to check there for the latest, most secure confs.
Example for nginx:
ssl_ciphers "AES256+EECDH:AES256+EDH"; ssl_protocols TLSv1 TLSv1.1 TLSv1.2; ssl_prefer_server_ciphers on; ssl_session_cache shared:SSL:10m; add_header Strict-Transport-Security "max-age=63072000; includeSubDomains"; add_header X-Frame-Options DENY; ssl_stapling on; # Requires nginx >= 1.
Booting into the livecd, its pretty basic:
Setup networking with “ip addr add” etc.. commands: # ip addr add <address>/<masklen> dev eth0 # ip link set dev eth0 up # ip route add default via <default gw> Set root user password and log in via ssh
Do something similar to below, basically create a cloud-config, and call the coreos-install command. ?[~]> sh root@cartman root@cartman's password: root@cartman's password: CoreOS (stable) Update Strategy: No Reboots root@localhost ~ # export http_proxy=http://proxy.
This isn’t as easy as you think…a normal du -h doesn’t work on /var/lib/docker. This is because of the aufs filesystem docker uses that du by default skips. The proper way to figure out how much space is actually being used involves a few more arguments:
docker -shx /var/lib/docker
So besides how great it is to be able to just pull down a docker image, theres actually a bit more advanced things you can do in terms of manipulating an image. The following points will give you a better understanding of how to work with, create, and modify images for your own projects:)
The two ways to get an image…
A registry. A docker registry (i.e. registry.hub.docker.com) allows you to easily pull an entire image locally for utilizing to create other images or just start a container.
Fortunately, could only get server via the eval program….btw, I strongly dislike rhel.
Via RedHat:
yum groupinstall "X Window System" Desktop Edit /etc/inittab for runlevel 5 (change the 3 to a 5)
/etc/sysconfig/desktop needs to contain: DISPLAYMANAGER=GNOME DESKTOP=GNOME Install vmware-tools (can do this via cli), mainly ./vmware*.pl (read the INSTALL)
Enjoy?
A quick overview of architecture names for x86 systems:
i386: The 80386 CPU has historically been the bare minimum for running Linux on a PC-compatible system. Consequently, a package for “i386? is designed for maximum compatibility and can run on any x86-like system; a system that describes itself as “i386? is either ancient or exotic, and can only be counted on to run i386 packages.
i485, i586: Rarely-seen, these refer to the 80486 and Pentium (80586) CPUs.
So I don’t usually use a RHEL based machine, but recently was tasked with deploying one on our network.
After the normal install process, which I decided to do text based via adding the following to the boot statement for the default installer option (push “e” when it appears):
linux text
I decided to setup networking later, after the machine was fully installed. On ubuntu/debian based systems, /etc/network/interfaces defines the configuration for interfaces on the system.