Monthly Archives: November 2014
Dilbert comic strip for 11/24/2014 from the official Dilbert comic strips archive.
‘You left your lights on’ – Good samaritan goes above and beyond for neighbour
Ludovico Einaudi using two iPads to play I Giorni.
Hello Bank advert, the Czech National Symphony Orchestra play the Overture from Carmen using only mobile phones and tablets.
Docker.io Builds Page For 32-bit Architectures
I have started posting up my builds of Docker.io. They are unofficial, and unsupported by the community, pending official support and code release supporting 32-bit architectures.
I have setup my system to auto-build every week and post to this shared directory. There’s a readme in the shared folder.
Docker.io Build Script Update
Some changes to the Docker.io code has caused the build script to fail, this was down to the code now using btrfs to build a driver. It has taken me a while to figure out how to fix that error message, but the script now works. You have to add this chunk of code anywhere before the main docker build
git clone git://git.kernel.org/pub/scm/linux/kernel/git/kdave/btrfs-progs.git mv btrfs-progs btrfs #Needed to include into Docker code export PATH=$PATH:$(pwd) cd btrfs make || (echo "btrfs compile failed" && exit 1) export C_INCLUDE_PATH=$C_INCLUDE_PATH:$(pwd) #Might not be needed export CPLUS_INCLUDE_PATH=$CPLUS_INCLUDE_PATH:$(pwd) #Might not be needed echo PATH: $PATH cd ..
Map shows Britain’s rudest place names from Cockwood to Cum Lake
How Splitting A Computer Into Multiple Realities Can Protect You From Hackers
Virtualisation, Sandboxes, Containers. All terms and technologies used for various reasons. Security is not always the main reason, but considering the details in this article, it is a valid point. It is simple enough to setup a container in your machine. LXC/Linux Containers for example, don’t have as much overhead as a VirtualBox or VMWare virtual machine and can run almost, if not just as fast as a native installation (I’m using LXC for my Docker.io build script), but conceptually, if you use a container, and it is infected with malware, you can drop and rebuild the container, or roll back to a snapshot much more easily than reimaging your machine.
Right now I run three different containers — one is my main Ubuntu Studio, which is not a container, but my core OS. the second is my Docker.io build LXC, which I rebuild everytime I compile (and I now have that tied into Jenkins, so I might put up regular builds somehow), and the final one is a VirtualBox virtual machine that runs Windows 7 so I don’t have to dual boot.
How Splitting A Computer Into Multiple Realities Can Protect You From Hackers | WIRED.
You must be logged in to post a comment.