Allinthemiddle

Control network routes for specific processes on Linux

2024-05-07T04:25:00.000-07:00

Intro

I wanted to control the flow of packets for specific processes on my Linux (Ubuntu 22.04) such that they won't go through a tunnel device which is setup for VPN connectivity. The VPN software is provided as is and I do not administer its configuration.

Please note that this post assumes you have understanding of network routing and are equiped to troubleshoot problems. If not you should first learn how networks work first. Each network setup has its own specifics. Appliance vendors come up with defaults and automation for the most common scenarios. Custom configuration can conflict with that and might isolate you from network access. All responsibilities remain those of the reader.

What worked

Summary of the solution

Use the network classifier cgroup (src: docs.kernel.org) to tag network packets with a class identifier (classid) for a process and its subprocesses (src: unix.stackexchange.com). Subsequently use iptables to mark packets which you can use from a custom routing table using policy-based routing (serverfault.com).

Step by step for an example scenario

Imagine that for certain tasks you need to use a VPN that is provided and configured by another team. The VPN software setups up a tunnel interface on your computer and configures a default route for this tunnel device. You still want to use a public service that provides a dedicated client but for which you don't want traffic to go over the VPN (e.g. an audio streaming service like Spotify).

Step 1 : Create a novpn network class

sudo mkdir /sys/fs/cgroup/net_cls
sudo mount -t cgroup -onet_cls net_cls /sys/fs/cgroup/net_cls
sudo mkdir /sys/fs/cgroup/net_cls/novpn
echo 0x100001 | sudo tee /sys/fs/cgroup/net_cls/novpn/net_cls.classid

You can see the upstream documentation on https://docs.kernel.org/admin-guide/cgroup-v1/net_cls.html . Important is the structure of the classid. You can freely chose it as long as it is unique for your system but if you chose another id make sure to check the id doing a cat on the file as it will be needed later:

cat /sys/fs/cgroup/net_cls/novnp/net_cls.classid
1048577

Step 2 : Create custom routing table

In order to create the custom routing table the easiest way is to just 'clone' the default route from your setup when the VPN is not up. You can easily get this using ip:

ip route | grep default
default via 192.168.0.1 dev wlp0s20f3 proto dhcp metric 600

With that it is best to pick a route table number that is not in use such that there is a dedicated routing table. As per serverfault.com this can be done using

ip route show table all | grep -Po 'table \K[^\s]+' | sort -u
local

The example output above would just mean there is no tables besides the reserved routing tables. In our case we want a dedicated route table for traffic that should not go through VPN so lets register it officially with a number not taken. I chose 3 and I can register it as follows:

echo "3\tnovpn" | sudo tee -a /etc/iproute2/rt_tables
3 novpn

For me this file looks now like:

cat /etc/iproute2/rt_tables
#
# reserved values
#
255   local
254   main
253   default
0   unspec
#
# local
#
#1   inr.ruhep
3   novpn

So it shows the reserved values as well as the table id we chose and its logical name 'novpn'. We should also pick a firewall mark to mark the packets. We can check all the iptables tables for marks:

for table in raw security mangle nat filter; do echo "===$table===";sudo /sbin/iptables -L -n --line-numbers --table $table -v; done | grep -o "MARK set [0-9x]*"

On my setup there were no firewall marks yet. I will therefore use mark 2 in this example. Now we have all the inputs to setup our route table

ip rule add fwmark 2 table 3
ip route add default via 192.168.0.1 dev wlp0s20f3 proto dhcp metric 1 table 3
ip route flush cache

With the first command we make sure the routing table is selected for packets with firewall mark 2. With the second command we add the default route to our routing table. And finally we clear cache to make sure new config is used.

Step 3 : Configure the marking using iptables

Since we already decided upon the mark and we have setup the cgroup and know its class id we have everything to configure iptables to mark pakkets as desired:

sudo iptables -t mangle -A OUTPUT -m cgroup --cgroup 1048577 -j MARK --set-mark 2

Step 4: Start our process such that it has the cgroup class id

It is important our processes get the cgroup class id. This can be done by registering their process ID in /sys/fs/cgroup/net_cls/novpn/tasks . This could become quite tedious since a lot of programs spawn a lot of children. Luckily Linux keeps track of the parent child hierarchy and if we register a process all its children will also be added. So if you spawn a terminal window and register its pid and subsequently spawn the process than the process and all of its children will get associated with this novpn cgroup class.

echo $$ | sudo tee /sys/fs/cgroup/net_cls/novpn/tasks
spotify

Now this Spotify process will have all its packets adhere to routing table 3 which doesn't have a route for the VPN but rather goes as if there wasn't a VPN setup.

Final notes

I do not represent Spotify I just use their services and it felt to be a useful example (their client application spawns multiple processes and needs to be able to communicate with other OS entities which makes other solutions like using netns more tricky).
When using the terminal approach, one should take care not to use the terminal for actions that require VPN connectivity as per-design those wouldn't work in that terminal.
This is a rather static solution if you move your computer and end up on a new network then likely you need a different network configuration (other default route in the custom table)
Verify the marking of packets of a cgroup is working. An easy trick to verify the tagging is working is by changing the iptables rule to drop the packages rather than to mark them. Then you can easily verify that Spotify works when launched outside the "novpn" terminal but that it cannot connect to any network when launched inside the "novpn" terminal.

Podman pitfalls

2023-11-25T07:12:00.000-08:00

Fedora docs are your friend

https://docs.fedoraproject.org/en-US/fedora-coreos/

SELinux might be on

If you are having permission denied errors watch out for SELinux. Check your podman VM and verify /etc/selinux/config . You can consider switching to permissive mode + reboot

Certificate errors

MITM

Some company like to or must inspect their users traffic. Generally this is done by having a transparent proxy which terminates SSL/TLS and uses a self-signed certificate that is owned by the company and can be considered trusted. The default podman VM won´t trust this certificate. You can try the following:

COPY the PEM file to /etc/pki/ca-trust/source/anchors/ and then update the trust:

update-ca-trust force-enable && update-ca-trust extract

Time drift

If the podman VM has time drift this can also break SSL/TLS certificate verification. Just update the time of your VM.

Allow docker in podman

sudo rpm-ostree install podman-docker

Kubernetes cheat sheet

2023-11-25T07:00:00.000-08:00

Just some commands that had value at some time or another.

Debugging

Sometimes debugging is hard because you are using an optimized images without troubleshooting tools or even a shell. Ephemeral containers come to the rescue there with some useful kubectl debug commands but if you need to see the attached volumes these tools fall short and while it is possible to do it manually it is tedious. Make sure you are aware of kubectl-superdebug :

https://medium.com/datamindedbe/debugging-running-pods-on-kubernetes-2ba160c47ef5

Resources

All resources in a namespace

Just iterate over the resource type and look for them:

for i in `kubectl api-resources --verbs list --namespaced -o name`; do kubectl get --sho-kind --ignore-not-found $i; done

Which pods still have persistent volume claim

kubectl get pods --all-namespaces -o=json | jq -c '.items[] | {name: .metadata.name, namespace: .metadata.namespace, claimName:.spec.volumes[] | select (has ("persistentVolumeClaim") ).persistentVolumeClaim.claimName }'

Networking

Jump portals

In order to do this you'd need to be able to exec into pods and make sure socat is available on the pod. When that is possible it is possible to tunnel via the pod towards a target.

On the pod setup a tunnel to remote endpoint:

socat tcp-l:<local-port>,fork,reuseaddr tcp:<target-host>:<target-port>

kubectl port-forward pod/<jump-pod> <local-port>:<target-port>

resources:

- socat commad list: https://exploit-notes.hdks.org/exploit/network/port-forwarding/port-forwarding-with-socat/

- k8s port-forward docs: https://kubernetes.io/docs/tasks/access-application-cluster/port-forward-access-application-cluster/

OAuth 2.0 notes

2022-09-01T12:24:00.001-07:00

This post is by no means meant to be original just some notes to persist info acquired while digesting oauth2.0/openid connect articles. Use at your own risk. An attempt was made at keeping pointers to the sources.

rfc6749

source: https://www.rfc-editor.org/rfc/rfc6749

The authorization code grant type is used to obtain both access
   tokens and refresh tokens and is optimized for confidential clients.
   Since this is a redirection-based flow, the client must be capable of
   interacting with the resource owner's user-agent (typically a web
   browser) and capable of receiving incoming requests (via redirection)
   from the authorization server.

     +----------+
     | Resource |
     |   Owner  |
     |          |
     +----------+
          ^
          |
         (B)
     +----|-----+          Client Identifier      +---------------+
     |         -+----(A)-- & Redirection URI ---->|               |
     |  User-   |                                 | Authorization |
     |  Agent  -+----(B)-- User authenticates --->|     Server    |
     |          |                                 |               |
     |         -+----(C)-- Authorization Code ---<|               |
     +-|----|---+                                 +---------------+
       |    |                                         ^      v
      (A)  (C)                                        |      |
       |    |                                         |      |
       ^    v                                         |      |
     +---------+                                      |      |
     |         |>---(D)-- Authorization Code ---------'      |
     |  Client |          & Redirection URI                  |
     |         |                                             |
     |         |<---(E)----- Access Token -------------------'
     +---------+       (w/ Optional Refresh Token)

https://www.rfc-editor.org/rfc/rfc6749#section-4.1

AWS Cognito's authorization code grant:

https://aws.amazon.com/blogs/mobile/understanding-amazon-cognito-user-pool-oauth-2-0-grants/

Cognito comes by default with an auth app which gets hosted on an URI with a chosen domain name:

https://<domain-name>.auth.<region>.amazoncognito.com

In there you have the different endpoints for your authn/authz flows which are documented on

https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-userpools-server-contract-reference.html

Verification of JWT tokens from Cognito

The key information for verification depends on the user pool and can be retrieved from:

https://cognito-idp.Region.amazonaws.com/your_user_pool_ID/.well-known/jwks.json . For details

see the knowledge-center article https://aws.amazon.com/premiumsupport/knowledge-center/decode-verify-cognito-json-token/

ALB authn/authz

https://docs.aws.amazon.com/elasticloadbalancing/latest/application/listener-authenticate-users.html

The loadbalancer sets the following headers:

x-amzn-oidc-accesstoken

The access token from the token endpoint, in plain text.

x-amzn-oidc-identity

The subject field (sub) from the user info endpoint, in plain text.

x-amzn-oidc-data

The user claims, in JSON web tokens (JWT) format.

Miscellaneous notes

- redirect_uri's have to match
- state is also used to avoid cross-side request forgery attacks

Authentication via Belgian eID card with Mozilla Firefox on Linux

2022-01-23T08:17:00.003-08:00

Since 2003 the Belgian government issues electronic identity cards called "eID" cards. These cards have cryptographic keys on them that allow digital signatures. This enables you to authenticate to government e-services using a smart card reader, your eID and pin (which you have to set when you receive your eID card). While setting up the software on Windows is straight forward I found the process for Linux less trivial hence I like to documented it.

So if you want to use your eID card to login to Belgian governmental services on Linux you can use this as a guide. My setup is a Linux Mind 20.3 "Una" which was not considered a support OS at time of writing (20.2 "Uma" was) so these instructions should not be limited to supported OS-es.

The well documented part

In order to be able to authenticate using an eID you need some middleware on your computer. This middleware provides the interface between your browser plugin and your eID in the smartcard reader. This section describes the installation of this middleware.

This piece of software is available via https://eid.belgium.be and at time of writing the Linux version can be found at https://eid.belgium.be/en/linux-eid-software-installatie . I do appreciate that they have tried to support a variety popular Linux distributions but what I respect most is their decision to have it available as opensource. In my case I used a newer release of Mint and therefore I downloaded the tarbal from the link under "Downloads for unsupported distributions". Surprisingly they don't mention their github repo which has a better README.md. So I'd advise to start there: https://github.com/Fedict/eid-mw or either just check out the instructions and use it to install the code packaged in the tarbal.

The github page details the pre-requisites. For my distribution I was able to install them using:

sudo apt-get install libtool autoconf automake libassuan-dev autoconf-archive libpcsclite-dev libgtk-3-dev libcurl4-openssl-dev libproxy-dev libxml2 libp11-kit-dev openssl

Once you have the pre-requisites installed you can just use the commands from the github README.md to install the middleware:

autoreconf -i

./configure

make

sudo make install

After this the middleware is installed. It comes with a binary application which you can run via the command `eid-viewer` and use to verify it is working correctly.

No card reader found

At this stage the application opened but the status bar at the bottom stated "No cardreader found" even when my cardreader was connected. Generally when a card reader is connected but no eID is inserted it should read "Ready to read identity card" but when testing just make sure to insert an eID card because the card reader might require this. In my case however I was stuck at "no cardreader found".

The most likely explanation was that Linux didn't know how to communicate with my card reader and that it requires a device driver. Since it is a card reader that has many years I didn't have the documentation that came with it and the device itself only has a label "Digipass by vasco" which is too little to get a specific driver.

Fortunately Linux can help here. Since my smart cardreader is a USB device I can list all the USB devices and get there VendorId and ProductId using lsusb:

lsusb

...

Bus 003 Device 006: ID 1a44:0001 VASCO Data Security International Digipass

...

When you Google this you arrive at the useful linux-hardware.org website (specifically https://linux-hardware.org/?id=usb:1a44-0001). There they link to https://salsa.debian.org/rousseau/CCID which is a driver that works with quite a lot of models. This time I found the instructions on the website more useful: (i.e. https://ccid.apdu.fr/ ). It also seems that you can do a `sudo apt-get install libccid` but I only saw this package afterwards. In my case I have compiled from source.

If at this stage you still aren't able to check your card via `eid-viewer` then make sure to install `pcscd` which is a daemon that allows access to a smart card. You'll need it anyway at a later point. After installing you can also start the corresponding service:

sudo apt-get install pcscd

sudo service pcscd start

Hopefully at this stage you can open `eid-viewer` and see your card details.

Now make it work on firefox

There is an official extension for firefox to make it work with firefox which is available at https://addons.mozilla.org/nl/firefox/addon/belgium-eid/ .

However for me it always would notify me at startup with "A recent enough version of the Belgian electronic identity card software could not be found. Is the eID software installed and up-to-date?".

I know the software is up-to-date since I have installed the latest version. This part required a bit more research so I'll split up in 2 sections; the explanation and the solution so you can skip to the solution if you are only interesting in getting yours working. If the solution doesn't work for you the explanation can give insights in how it works to aid troubleshooting on your end.

The explanation

Whenever you get stuck you need to troubleshoot. One tool for troubleshooting is debugging. Recent versions of Firefox allows to debug extensions out of the box. If you browse to "about:debugging" then you get a debugging screen for Firefox, when you select "This Firefox"then you can see all the extensions that are currently installed. When you click the "inspect" button for the "eID Belgium" plugin you'll get a screen (if you've used developer tools from Firefox or Chrome this looks very familiar). There is a debugger tab in which you can find the main thread which runs "background-script.js". This allows you to see what the plugin actually does. In this particular case it tries to install a pkcs11 security module. When that fails it shows the notification we saw earlier.

Since automatic installation doesn't work I thought let's do it manually and I followed instruction from https://developer.mozilla.org/en-US/docs/Mozilla/Projects/NSS/PKCS11/Module_Installation and after I added the module I could see in security devices that Firefox can even see the attached card reader. Full of optimism I try a test login via https://iamapps.belgium.be/tma/?lang=en leading to a disappointing failed login.

The Firefox window to manage security devices gives very little configuration options but the issue at hand here is that the Firefox extension "eID Belgium" is not allowed to use the pkcs11 module that I imported manually. If you've tried creating this security module manually you'd want to delete it again because although it shows the cardreader it won't be usable and it will give rise to name conflict as you can only have one module named "beidpkcs11".

The proper way to go about it is via a native manifest: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Native_manifests#manifest_location . This manifest was actually built but it was put on /usr/local/lib/mozilla/pkcs11-modules/beidpkcs11.json which seems not checked by Firefox (perhaps in the past it was . There is also an alternate version that acts as a fallback /usr/local/lib/mozilla/pkcs11-modules/beidpkcs11_alt.json . This fallback uses p11-kit but in my case the first version works perfectly.

The solution

Put the generated manifest on the location where Firefox expects it:

sudo mkdir -p /usr/lib/mozilla/pkcs11-modules/

 sudo ln -s /usr/local/lib/mozilla/pkcs11-modules/beidpkcs11.json /usr/lib/mozilla/pkcs11-modules/beidpkcs11.json

Restart firefox and you should no longer see the notification pop-up and ideally the lights of your card reader are even blinking.

Note according to the docs the following 3 locations should be valid:

/usr/lib/mozilla/pkcs11-modules/beidpkcs11.json
/usr/lib64/mozilla/pkcs11-modules/beidpkcs11.json
~/.mozilla/pkcs11-modules/beidpkcs11.json

For me option 2 didn't work even though I'm on Firefox 96.0.1 (64-bit). Option 1 & 3 both worked. So use 1 if you want it to be system-wide or option 3 if you only want it to be available for a specific user.

The final test

Now go to https://iamapps.belgium.be/tma/?lang=en and you should be able to authenticate successfully!

Finally you can start the fun part; the filing of your taxes! Or whatever you wanted to do.

Edit: I wanted to create a PR to add the native manifest but it seems somebody has beaten me to it (with this change). So likely the next version will be easier to install.

Serialization Anomily when using MVCC (The good, the bad & the ugly)

2021-12-03T16:04:00.001-08:00

Intro

When working in-depth with databases sooner or later you will encounter transaction isolation levels. If you are new to transaction isolation check out the Postgress transaction isolation documentation because that documentation team did an amazing job! In this post I'd like to go into more depth on one issue mentioned on that page the serialization anomaly.

Real life example

A picture says more than a thousands words so let's try to create a mental picture by talking about a real-life scenario. For this assume we are creating an application that has to manage financial accounts.

Let's take as a starting point 3 accounts with the following balances:

Account A: €20
Account B: €30
Account C: €40

Now consider 2 transaction:

tx1: transfers money (€10) from account A to a account B
tx2: transfers money (€10) from account A to C

In order to perform these transactions against our database engine it is required to read the balance of the sender from the balances table , subtract the amount sent and write the new balance. Subsequently it needs to read the balance of the receiver, add the amount and write the receiver's new balance.

When these transactions happen in a non-overlapping mode performing these changes to your data is almost trivial. We can detail the steps as follows: Transaction 1 is in bold and transaction 2 in italics. Then the statements look like:

Begin - RA - WA - RB - WB - end - begin - RA - WA - RC - WC - end

So in detail:

begin: begins the first transaction
RA: reads balance for account A 20 euro
WA: write the new balance of 10 Euro for account A
RB: reads balance for account B 30 euro
WB: write new balance of 40 euro for account B
end: ends the first transaction
begin: begins the second transaction
RA: reads balance for account A 10 euro (since previous change is committed)
WA: writes the new balance of 0 euro for account A
RC: reads balance for account C 40 euro
WC: writes the new balance of 50 euro for account C
end: ends the second transaction

These steps should be intuitive and feel familiar as it is the behavior we expect when performing financial transactions in real life.

The reason why this is easy is because concurrency in this example always 1, a single transaction is in the system, so no overlap is taking place.

The interesting world of concurrency

Just like a puzzle becomes more interesting when getting to more than 1 piece concurrency becomes interesting when having multiple concurrent actors.

A modern database however will have a few tricks up its sleeves to manage concurrency. Locking is probably the best-known mechanism to deal with concurrency. It can for example avoid data corruption due to multiple processes writing the same record at the same time. Locking is very powerful but is generally not the first choice to deal with concurrency because it causes contention which lowers the throughput of your database system. Which brings us to another database trick; Multiversion Concurrency Control, MVCC in short.

MVCC is an implementation where each transaction will get a snapshot of the database state at transaction start. This allows the DB engine to be able to read data without risking a dirty read. So it avoids reading of uncommitted data even when that data is changed by another concurrent process. It also enables repeatable reads. It can however cause Serialization anomalies which would make scenario's possible that don't make sense in real life. In order to understand why this is a problem let's revisit our 2 example transactions. Let's start with our system initialized again on the starting point detailed earlier but this time let's have the transactions executed concurrently such that the different statements within them are interleaved.

Assume the order:

Begin - RA - begin - RA - WA - RB - WB - end - WA - RC - WC - end

So in detail:

begin: begins the first transaction
RA: reads balance for account A 20 euro
begin: begins the second transaction
RA: reads balance for account A 20 euro (since previous change is not committed and when transaction started the snapshot of the database had still the original balance of 20 euro for account A)
WA: write the new balance of 10 Euro for account A
RB: reads balance for account B 30 euro
WB: write new balance of 40 euro for account B
end: ends the first transaction
WA: writes the new balance of 10 euro for account A (since this transaction also read the 20 euro starting balance due to MVCC and subtracted 10 from it)
RC: reads balance for account C 40 euro
WC: writes the new balance of 50 euro for account C
end: ends the second transaction

This is a serialization anomaly and this example hopefully illustrated why this is a problem. If it is unclear imagine you are a bank managing these accounts. Your system has just generated money for your customer who could withdraw or use that money! The above scenario is well possible if you picture an account with multiple users. Two different users could easily wire money to different accounts concurrently around the same time. So for these type of workloads it is important to avoid serialization anomalies.

Serializable isolation to the Rescue

It is possible to avoid serialization anomalies in database engines that allow running with the strictest transaction isolation level; serializable isolation.

Serializable isolation states that in order for a concurrent execution of transactions to be valid a serial ordering of transactions has to exist such that each statement execution has the same results as in the concurrent execution.

So if we start from our concurrent execution in our example. Since there are 2 transactions we have 2 possible orderings:

Tx1 followed by Tx2
Tx2 followed by Tx1

Or in our per statement illustration:

begin - RA - WA - RB - WB - end - begin - RA - WA - RC - WC - end
begin - RA - WA - RC - WC - end - begin - RA - WA - RB - WB - end

I leave it to the reader to detail the outcomes of the second ordering. You should arrive to the conclusion that account A will always have a balance of 0 after both transactions finish no matter how you order these 2 transactions (serially). Therefore if you have a database engine running in transaction level serializable isolation and you try to do the concurrent execution then that engine will give an error. This does not mean there is an issue in the Database engine but rather that there is a problem with your workload. If it occurs rarely it's possible to just have your application catch these exceptions and retry. Because when this error is thrown generally the database engine will rollback 1 of the transactions, often the transaction that submitted the statement that would give rise to the anomaly.

How can the DB know?

There is no such thing as magic (not even in the database world) so the engine must have some clever way of detecting that a statement would cause a serialization anomaly. Working backwards from the behavior of serially ordered transactions you could come op with 2 rules:

If data is read in a transaction TX that was written by another transaction TC which was committed before the start of Tx then in a sequential ordering Tx must follow TC (order: TC -> TX)
If data is read in a transaction TY that is written by another transaction that overlaps but wasn't committed when TY started then Ty must precede TU (order TY -> TU)

Note that

Data read and written within the same transaction doesn't impose ordering
2 Reads from different transactions also don't impose an ordering
Since more than 2 transactions can overlap a read-only transaction could still give rise to a serialization anomaly!

In concurrent executions that are a serialization anomaly you will get ordering rules that will be in conflict. For our example:

Begin - RA - begin - RA - WA - RB - WB - end - WA - RC - WC - end

begin: begins the first transaction
RA: reads balance for account A
begin: begins the second transaction
RA: reads balance for account A

2 reads don't impose ordering between each other

WA: write the new balance of account A

At this point the DB knows that T2 reads data written to by an overlapping transaction T1 which is uncommitted so T2 must precede T1 (T2 -> T1 )

RB: reads balance for account B
WB: write new balance for account B
end: ends the first transaction
WA: writes the new balance for account A

Now the DB knows that T1 reads data written by T2 which was not committed at starttime of T1 so T1 has to precede T2 (T1 -> T2)

At this stage the DB engine can throw an exception as no matter what happens further with T2 (except for a transaction rollback) it will yield a serialization anomaly. Therefore it is best to rollback the transaction immediately and don't allow further statements as their results shouldn't be relied upon anyway.

The advantage of the arrow notation is that you can chain them together and as soon as you encounter a transaction for a second time you know there is a violation. So if we chain them in the order we found them:

(T2 -> T1 ) || (T1 -> T2) => (T2 -> T1 -> T2)

A directed graph would be a useful way of tracking these orderings discovered by applying the rules. Cycles would in this case indicate a serialization anomaly so we can use a directed acyclic graph (DAG).

In summary

Transactions should see the database as if they were running alone on the system, not being impacted by other running transactions. This is important because we don't know what will happen to these transactions, they could be aborted and in that case relying on the data written by them would cause an anomaly in itself. Ironically it is the measures we put in place to protect against these anomalies that could give rise to a serialization anomaly where results from statements of overlapping transactions wouldn't be retrievable if the transactions had happened serially. This post showcases that for MVCC and aims at providing intuition into why these serialization anomalies are problematic and give basic insights in what a database can do to protect you from it. That is if you chose to run with a transaction level of serializable isolation.

Final Notes:

I haven't gone into much detail about locking. Locking can be used to avoid serializable isolation anomalies but it requires aggressive locks (e.g. exclusive locks) that would enforce serial access to the underlying resource. The example is chosen in such a way that the concurrent execution would be possible even with table level locking. For example where during normal database execution writes would block other writes. This is because locks follow the lifetime of a transaction and T1 ended before a write in T2 could give rise to contention on a lock.

I have tried to give a simple explanation for the tracking mechanism above. Note that my example covered only rule 2. Rule 2 is easiest to track as you only need to take into account open transactions. Rule 1 on the other hand uses committed transactions which is troublesome to track since their amount grows with the uptime of your database. You can stop keeping track of committed transactions from the moment they no longer have (direct or indirect) overlap with open transactions. This overlap could disappear because transactions can close (by commit or rollback). But a lot of database instances have a continuous workload which could block this type of cleanup since there always remains overlap with open transactions. The good news is that research exists which investigates use of heuristics to efficiently avoid serialization anomalies. A nice and freely available paper on such a heuristic is "Efficiently making (almost) any concurrency control mechanism serializable".

Setting up Pyhon 3.7 with SSL support

2018-12-23T02:58:00.000-08:00

Intro

If you are lucky enough to have Python 3.7 in your OS repositories then you can skip this post if not you might find a hard time setting up Python 3.7 with SSL support. Python 3.7 requires a recent version of openssl but even when that one has been installed in my case it would not find it so I'm documenting the steps on how I got it to work.

1) Get a recent openssl installation

In my case I went for 1.1.1a as that one should be working with Python 3.7.

cd /usr/src/
sudo wget https://github.com/openssl/openssl/archive/OpenSSL_1_1_1a.tar.gz
sudo tar -xvzf OpenSSL_1_1_1a.tar.gz
cd openssl-OpenSSL_1_1_1a/
export CFLAGS=-fPIC  # Make sure we build shared libraries
./config shared --prefix /usr/local/openssl111a --openssldir=/usr/local/ssl  # Make sure we build shared libraries
sudo make
sudo make install

2) Get and install Python

It is possible to follow instuctions of https://tecadmin.net/install-python-3-7-on-ubuntu-linuxmint/ with the following changes:

Before doing any configure make symbolic links to the openssl libraries. I tried adding the openssl lib folder to LD_LIBRARY_PATH but for some reason I would still always error out with
```
*** WARNING: renaming "_ssl" since importing it failed: libssl.so.1.1: cannot open shared object file: No such file or directory'
```
Creating symbolic links in a default library path did strangely enough work:
```
cd /usr/lib
sudo ln -s /opt/openssl/lib/libcrypto.so.1.1
sudo ln -s /opt/openssl/lib/libssl.so.1.1
```

When doing the configure specify additional details

sudo LDFLAGS="-L/opt/openssl/lib" ./configure --enable-optimizations --with-openssl=/opt/openssl > /tmp/configure_output

When doing the make if you redirect stdout you will only see the warnings if they don't show:

*** WARNING: renaming "_ssl" since importing it failed: libssl.so.1.1: cannot open shared object file: No such file or directory

*** WARNING: renaming "_hashlib" since importing it failed: libssl.so.1.1: cannot open shared object file: No such file or directory

then you are good to go.

You can validate by importing the python ssl lib:

$ /usr/local/bin/python3.7
Python 3.7.0 (default, Dec 23 2018, 10:35:52) 
[GCC 6.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import ssl
>>>

No error means you should be good to go.

My attempt to the AWS Solution Architect professional exam sample questions.

2016-08-30T13:25:00.000-07:00

For this practice exam the correct answers are given on the Japanese version of the practice exam which can be found here. The English practice exam is available from here. And in this post I like to provide my reasoning in why the given answers are the correct ones. I have done similarly for the DevOps professional exam here.

Question 1: Best RTO for on-premise Content Management System

- Answer A will and is the best of the provided options because storage gateway is already used and it's volumes can be converted to EBS volumes. RMAN backups in S3 also allow restoration into EC2
- Answer B is not acceptable since Glacier storage takes recovery times >= 3 hours
- Answer C: There is no need to attach a AWS Storage gateway to the EC2 instance, better to use an EBS volume
- Answer D: AWS Storage Gateway-VTL is for tapes so no need here as you had a storage gateway volume

Question 2: ERP application in multiple AZs

- Answer C is valid and allows to restore data up until 5 minutes from the issue (so RPO of 15 minutes is met). Since you have hourly backups as well in S3 you can quickly restore these and you only need to replay transaction logs for max 1 hour. Furthermore S3 provides excellent data retention.
- Answer A is not acceptable since Glacier recoveries take too much time > 3 hours
- Answer B is not good for this scenario as it is unknown how the data corruption occurred. Probably data corruption is introduced by a logical error rather than issues on storage level. Since synchronous replication only makes sure you write the changes on a 2nd system as part of your transactions it doesn't allow to recover to earlier time to protect for these corruption errors.
- Answer D is unacceptable because even though instance store volumes might allow to take quicker backups they are volatile and should not be relied upon for database backups (they are also only accessible from 1 instance and therefore data is only in 1 AZ)

Question 3: Random acts of kindness

- Answer B is good as it is a cheap way that allows you to operate without maintaining infrastructure
- Answer A is not good as IAM users should be internal users of your organizations. You should not use these identities for 'web' users. One reason would be because the amount of users would be limited. Even if you would map them to a single 'application' user it would not be a good practice to do so.
- Answer C is not good again because of IAM user usage as well as introducing additional unnecessary infrastructure (incurring costs)
- Answer D introduces unneeded infrastructure incurring unneeded costs.

Question 4: Protecting SSL

- Answer D is the best. CloudHSM is hardened to make sure SSL certificates cannot leave the device. Furthermore its design and external certification certify that Amazon employees won't have access to them either. Since Amazon employees also don't have access inside your EC2 instance it is good to store your logs on an ephemeral volume using a randomly generated AES key. This means that you will lose your logs upon stop/start or when you experience a hardware failure but there were no retention requirements mentioned for the log files. Since the volumes use this random key when mounting you grant your users access by granting them access to the instance. The encryption makes sure that data is encrypted at rest and that physical access does not compromise your data.
- Answer A is generally a good solution but since in this case security is the main concern it is not the best solution. By offloading SSL at your Load balancing tier you have the traffic flowing in plain text from ELB to web servers.
- Answer B is not good as there is no way of protecting your private key in the Amazon S3 bucket. Since your instances need access to the S3 bucket to retrieve the key, employees could do the same and therefore compromise the key.
- Answer C is good but it does not really protect your logs as you cannot write them straight into S3. S3 is an object store and cannot be used reliably as a block device.

Question 5: Fat client application

- Answer D is the best. Using the SSL VPN client the users can securely connect to the VPC and have access to the private subnets. The fat client can then connect over the VPN tunnel to the application servers which are safely in the private subnet.
- Answer A does not make sense, AWS Direct Connect is to allow a 'private' line from your data center into AWS and therefore does not come into play for this scenario
- Answer B is not valid as you don't want to publish the application on the internet therefore an ELB by itself won't help
- Answer C is not valid as you still place your application servers in the public subnet. Having the IPsec VPN connection is meant to avoid this need.

Question 6: Legacy engineering application migration

- Answer B is indeed the way to go an initial sync followed by incremental syncs to make sure you get all the data in the latest state within the time frame. If needed you could perform multiple incremental syncs (note that these would incur additional cost as you would be consuming more bandwidth)
- Answer A is not valid as it does not provide a solution to time needed to transfer the 900 GB of data
- Answer C is not valid as AWS Import/Export is not to migrate data within 48 hours
- Answer D is not valid because it says to copy the data on Friday which again does not provide enough time to transfer all the data.

My attempt to the AWS DevOps Engineer professional exam sample questions.

2016-08-30T13:16:00.001-07:00

This is just a blogpost to try out the sample questions of the AWS Devops Engineer professional exam. So keep in mind that these are by no means official answers they are just my attempt to solving the example questions. I did a similar attempt for the Solutions Architect professional exam.

Question 1 automated data backup solution:

- Answer C: ec2-create-snapshot API results in a snapshot from your EBS volume which is stored in S3 (=distributed data store without single point of failure). Use the tags to manage metadata and be able to cleanup old snapshots to limit costs.
- Answer A is not valid because ec2-create-volume creates an empty volume or one initiated from a snapshot. Even if copy backup data means to this volume than it would be sub optimal as you will have worse retention compared to answer C and you will have higher costs (every volume you create will take up full space whereas S3 snapshot will be incremental)
- Answer B is not valid because recovering your data from Glacier won't be possible within 1 hour
- Answer D is not valid because ec2-copy-snapshot can only operate on snapshots not on EBS volumes

Question 2: Going from M3 instances to C3 instances when using CloudFormation and AutoScaling Groups

- Answer D is correct:
- Answer A is not sufficient as the Auto Scaling group won't automatically replace your existing instances.
- Answer B & C are not valid since you cannot update a launch configuration. As stated in the documentation.

Question 3: CloudFormation for complex systems

- Answer B is my preferred answer as multiple separate templates are easier to maintain and allow re-use.
- Answer A is not good because maintaining a single template does not scale (it won't allow re-use)
- Answer C is not good as orchestrating the process from an EC2 instance introduces a single point of failure. It is also not cost efficient as it will require additional work to implement and a running instance.
- Answer D is not good because you wanted to version-control your infrastructure which encompasses networking and thus VPC

Question 4: Automated deployment - reduce launch time

- Answer B is correct as it fulfills the requirements
- Answer A is incorrect because of the timing requirements it would take more than 3 minutes given the timings of the operations
- Answer C is incorrect because of timing (artifacts 4 min + deploy app code 1 min) > 3 min
- Answer D is incorrect because you still need to perform all the steps and thus require > 3 minutes, also the polling is not needed as User Data can be used to initialize the EC2

Question 5: I/O load performance test

- Answer B is correct. This operation is needed to avoid the first touch penalty and to make sure you check the performance of a warm Volume (at least if the volume is restored from snapshot, nowadays you don't need to prewarm new empty volumes).
- Answer A is incorrect because you would use the block size which is applicable for your application and won't change it upon deployment
- Answer C is incorrect as you just use the volumes to test so no need to back them up, having a backup also does not influence performance
- Answer D is incorrect as encrypted volumes won't boost performance
- Answer E is incorrect as creating a snapshot does not read every block in the volume but only touches the blocks that have data (or changed data if the volume itself was created from a snapshot)

Question 6: social media marketing application

- Answer B is a possible way to do this. DynamoDB is a persistent store that stores data in multiple AZs.
- Answer A is not correct because Kinesis is for streaming data, it won't allow you to keep historical data as it only can keep data records for 1-7 days.
- Answer C is not correct because Glacier is for archiving data that you rarely want to retrieve. Also if you want to publish your data into Redshift using DataPipeline you need to have your data in a source that can be used by Redshift (e.g regular S3 (not Glacier!), DynamoDB, EC2 (via SSH), EMR (via SSH) )
- Answer D is not correct because Amazon CloudWatch is not for analytics. Also Cloudwatch only retains data for 14 days.

Question 7: bill increase

- Answer C is correct: wording is a bit weird as it looks sub optimal to send an SNS to your application which would then query DynamoDB. It is good to have the data in Dynamo DB to have it there persistently but it would be more efficient to have a lambda function putting the data into Dynamo DB and that this lambda function also updates the cache with the new entry such that at this time DynamoDB does not need to be queried.
- Answer A is incorrect because S3 bucket life cycles are to change storage type of an object it does not allow you to push a list of objects to another bucket
- Answer B would be feasible but only if you have a very controlled process over the uploads that can be done in your bucket it is not as practical as C.
- Answer D is incorrect because there is no such thing as SQS lifecycles that move objects into S3
- Answer E is incorrect because ElastiCache is a key-value cache service which does not allow you to push files into Amazon S3

Question 8: AWS Elastic Beanstalk + continuous deployment (zero downtime)

- Answer B is correct because the swap of DNS name allows you to rollback almost immediately (ignoring clients that don't implement DNS and TTLs correctly)
- Answer A is incorrect because depending on the deploy time rollback won't be almost immediately
- Answer C is incorrect doesn't have a rollback scenario
- Answer D is incorrect because I don't think you can configure a beanstalk environment to send HTTP 301 response codes. Also because 301 HTTP response code is a permanent redirect and therefore will cause clients to cache this redirect so rollback will still keep impacted clients on the new environment

Question 9: Log analysis application

- Answer A seems possible as CoudWatch Logs can filter your logs and keep track of login actions
- Answer B is incorrect as it won't be real time
- Answer C is incorrect because it has no auto-scaling
- Answer D is incorrect as it won't be real time
- Answer E is incorrect as you cannot use map reduce job on data that is in your RDS MySQL. You would need to export the data which won't be real time either

Question 10: orders processing

- Answer B is correct because it will automatically replace an instance if it is stopped/terminated or fails (HW failure).
- Answer E is correct because it allows to detect that the application is no longer running correctly and will stop the instance automatically.
- Answer A is incorrect as a 2nd watchdog instance costs money
- Answer C is incorrect as no need for scaling was expressed and having a minimum of 2 already makes it more expensive
- Answer D is incorrect as you need to pay for the ELB so it is not the most cost-effective way

Setup Linux Mint 17.2 on Dell XPS 15 (2015 edition)

2015-08-27T13:05:00.001-07:00

This blog post will describe a possible setup for Linux Mint 17.2 on a Dell XPS 15 (built year 2015 with 4K Ultra-HD touch screen). It will focus on the pre-installation steps (how to boot your Linux Live USB) and post-installation steps (fixing driver issues). It is expected that the reader already knows how to perform a Linux install.

Installation of Linux on a Dell XPS 15

Download Linux Mint 17.2 Cinnamon and create a bootable USB.

Disable fast boot from Windows

Boot into Windows and disable fast boot (Instructions at http://www.eightforums.com/tutorials/6320-fast-startup-turn-off-windows-8-a.html)

Disable Secure boot and change boot order

Go into the Bios (Reboot notebook and press F2 on splash screen (bios keys are mentioned in bottom right corner). After this your BIOS screens should look like:

Boot from the USB into Linux. Once there use gparted (if needed install using `sudo apt-get install gparted` to resize the Windows partitions and to free up space for your Linux installation. Next perform the Linux installation to your preference (for me that means a separate partition for /home).

Driver issues + fixes

Wi-Fi

This is one is available in the restricted drivers area of Mint. Before launching it however it is best to get your repository data up-to-date and to install all updates:

sudo apt-get update && sudo apt-get upgrade

Next go to the restricted drivers wizard using the menu:

In this window only consider the area on the wireless drivers (broadcom drivers):

Select bcmwl-kernel-source and click apply changes, this should do all the necessary configuration to get Wi-Fi working. Next you can connect to a wireless network using network manager.

How to get internet-access on this notebook without Wi-Fi?

I have bought the 4-in-1 connector for the PC that will go from USB3.0 to USB2.0, ethernet, VGA & HDMI ports. For the USB and the ethernet ports this adapter is plug&play. So handy when you need to install updates when your wireless is not yet working.

Nvidia

Bumblebee Installation instructions

Using instructions from https://wiki.ubuntu.com/Bumblebee

sudo apt-get update
sudo apt-get upgrade
sudo add-apt-repository ppa:bumblebee/stable
sudo apt-get install bumblebee bumblebee-nvidia primus linux-headers-generic

Which gives the following output:

Dellx log # sudo apt-get install bumblebee bumblebee-nvidia primus linux-headers-generic
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following extra packages will be installed:
  bbswitch-dkms lib32gcc1 libc6-i386 linux-headers-3.13.0-62
  linux-headers-3.13.0-62-generic nvidia-304 nvidia-current primus-libs socat
Recommended packages:
  nvidia-settings libcuda1-304 nvidia-opencl-icd-304 primus-libs-ia32
The following packages will be REMOVED:
  linux-kernel-generic
The following NEW packages will be installed:
  bbswitch-dkms bumblebee bumblebee-nvidia lib32gcc1 libc6-i386
  linux-headers-3.13.0-62 linux-headers-3.13.0-62-generic
  linux-headers-generic nvidia-304 nvidia-current primus primus-libs socat
0 upgraded, 13 newly installed, 1 to remove and 0 not upgraded.
Need to get 47,8 MB of archives.
After this operation, 260 MB of additional disk space will be used.
Do you want to continue? [Y/n]

Install newest nvidia drivers

These are present in the driver manager.

Select the latest driver

Click apply and afterwards it should show that an additional proprietary driver is in use.

Configure Bumblebee to use these new drivers

Changes the following four lines using your favorite editor in /etc/bumblebee/bumblebee.conf (using sudo, e.g. sudo gedit /etc/bumblebee/bumblebee.conf):

Driver=nvidia
KernelDriver=nvidia
# colon-separated path to the nvidia libraries
LibraryPath=/usr/lib/nvidia-346-updates:/usr/lib32/nvidia-346-updates
# comma-separated path of the directory containing nvidia_drv.so and the
# default Xorg modules path
XorgModulePath=/usr/lib/nvidia-346-updates/xorg,/usr/lib/xorg/modules

Note that paths are once colon-separated and once comma-separated.

After a reboot the bumblebee daemon should be running.

peter@Dellx ~ $ /etc/init.d/bumblebeed status
 * bumblebeed is running

Why would I install these proprietary drivers?

You don't need to install them but they can boost performance our lower your power consumption:

Performance

3D Performance before setup

peter@Dellx ~ $ glxgears 
Xlib:  extension "NV-GLX" missing on display ":0".
Running synchronized to the vertical refresh.  The framerate should be
approximately the same as the monitor refresh rate.
348 frames in 5.3 seconds = 65.786 FPS
300 frames in 5.0 seconds = 59.997 FPS
300 frames in 5.0 seconds = 59.995 FPS
300 frames in 5.0 seconds = 59.996 FPS

3D performance after setup

peter@Dellx ~ $ glxgears 
30157 frames in 5.0 seconds = 6031.306 FPS
31302 frames in 5.0 seconds = 6260.384 FPS
32086 frames in 5.0 seconds = 6415.288 FPS
30959 frames in 5.0 seconds = 6191.375 FPS

Battery saving mode

This performance gain comes however with a penalty for the autonomy of your notebook (higher battery drain). In your panel with status and notification icons an Icon should be present that either holds the nvidia logo or the intel logo:

When you click the logo you will get the Nvidia configuration screen that allows you to switch between the modes.

When selecting a mode you'll need to provide a password because privileges are required (only possible if your user is allowed to perform privileged actions (sudo rights)).

In order to activate the changes you need to re-login.

After a re-login you'll see the intel logo.

To investigate

How to get the 4-in-1 adapter working for external displays. Low priority as I currently don't have a secondary display.
Quite frequently text gets pasted while typing or mouse jumps. This is likely caused by the touchpad which is quite broad and easily touched by accident. Currently I don't have an external mouse but will likely look into buying one in the near future and will then check howto best disable the touchpad when mouse is connected and re-activate it when mouse is disconnected. (e.g. using udev)
In syslog CPU stacktraces show up from time to time
Touchscreen: This seems to be a weak point for Linux. The 'chromium-browser' however seems to do support gestures like pinching and two-finger scrolling. Can be handy for Google Maps although I dislike greasy fingers on my screen.

"to modify zones, delete program in service" on polar watch

2014-08-02T10:09:00.002-07:00

In this post I'll explain how to setup your heart rate zones manually on a polar watch when you get the message "to modify zones, delete program in service". I have the polar rcx3 but probably for other polar watches the same logic will apply.

Personal introduction (can be skipped without a problem)

A few months ago I started running and to track my progress I want to monitor my heart rate. For this I bought the Polar RCX3 run watch which comes with heart rate monitor and stride sensor s3+. I wanted to configure my heart rate zones manually as I had a physical examination from a physician who determined my training zones. Since he also provided a training program based on my heart rate zones it seems most appropriate to use the zones that are mentioned in his program. The zones that were proposed by the watch are not completely different but there are some differences. When I wanted to change the heart rate I received the vague error message: "to modify zones, delete program in service". As it took a while to find the problem I'll put it here for other people their convenience.

Setting heart rate zones manually on polar rcx3

This can be done easily by going to.

 Settings -> Heart rate settings -> Sport zones

There you can select any of the 5 zones and select its limits. In some cases however you can have an error. I have seen the following errors:

'To modify zones, first set ZoneOptimizer off'

This is a clear error message and can be easily solved. Just disable the Heart rate Zone optimizer of your polar watch. This can be done in the following menu entry:

 Settings -> Heart rate settings -> ZoneOptimizer

Set it to 'OFF' and retry setting your heart rate zones manually.

'To modify zones, delete program in service'

This however is a rather cryptic error message imho. Google is your friend but this time I only found the advise to reset the watch by pressing all the buttons simultaneously for 2 seconds. Don't do this as it will just reset your watch settings but won't fix the problem! This error is shown because you cannot change your heart rate zones as long as you have training programs from www.polarpersonaltrainer.com on your watch. As I already uploaded some training plans to my watch my heart rate zones were blocked. I guess the training program calculates heartrate zones based on your maximal heart rate and than locks the heart rate zones so that changing them doesn't modify the training program completely.

Unfortunately this means that the only solution I know is to go to www.polarpersonaltrainer.com, delete your trainingsprogram and then sync with your watch. Then you can again try to set your heart rate zones manually.

Personal Conclusion/remark

It is not to hard to set your manual heart rate zones as long as you know to remove training programs but it is a pitty that they need to be removed. I guess it is necessary due to to the implementation of heart rate zone programs but it is a pity. Since I only wanted to start the program from polarpersonaltrainer in a few months I'll first continue with my tailored training programs and then I might switch back to the calculated heart rate zones.

Setting up a vagrant basebox for Oracle Linux by using veewee

2014-01-05T23:08:00.001-08:00

Introduction

Note: Due to my professional life I use Oracle Linux a lot (Which is a distro that tracks Red Hat so it is very similar to RH and CentOS) therefore I will use Oracle Linux for the VM's in this blogpost as well. Don't worry about a possible price tag; Oracle Linux is free and you can get free updates from their Oracle public yum servers. I am no Oracle employee, so if you want their vision: https://linux.oracle.com.

Another reason why I use Oracle linux is because vagrant boxes were not easy to find for this distro. At least not for usage with libvirt. This makes it more interesting topic for a blog post.

For home usage I really like mint. So the building of the basebox is done on my home PC which runs mint (which is Ubuntu based and thus a Debian derivative).

Overview

In order to build a vagrant basebox we will need to go through the following steps

Install Ruby version manager (rvm)
Install bundler gem
Install veewee as a gemset in rvm
Installing kvm support for your system.
Installing ruby-libvirt gem
Create a storage pool
Create a basebox
Install a compatible Vagrant with libvirt
Create a vagrant config and test.

The remaining of this blogpost will have sections corresponding with these steps. The reader can skip steps that are of no interest to him/her.

Installing rvm

RVM is a command-line tool which allows you to easily install, manage, and work with multiple ruby environments from interpreters to sets of gems. For this blogpost we use its feature to manage sets of gems. I only use it to avoid corrupting your default ruby environment but it is not perse necessary for building a vagrant basebox.

Install the pre-requisites

sudo apt-get install libxslt1-dev libxml2-dev zlib1g-dev curl

Install rvm

\curl -sSL https://get.rvm.io | bash

Ruby works by sourcing a script. By sourcing this script rvm gets 'activated'.

source /home/$USER/.rvm/scripts/rvm

Once rvm is ready for setup we will install ruby 1.9.2 in it since this is the version we will use to run veewee

rvm install 1.9.2

Additional remark regarding rvm: rvm will be a function but in order for this to be initialized correclty you need to use a loginshell (if this is chinese to you and you wish to translate do a 'man bash' and start reading the 'INVOCATION' section). Since I was using guake (a dropdown terminal) this was not done automatically when opening a new terminal. Luckily there is a checkbox 'Run command as a login shell' in the guake preferences, after selecting this box rvm was loaded automaticlly in every new guake shell.

Install veewee as a gemset

Now that rvm is installed and a ruby 1.9.2 is available we can install veewee. We will get the latest version by cloning the github repository of the original creator.

$USER@$HOST ~ $ cd
$USER@$HOST ~ $ git clone https://github.com/jedi4ever/veewee.git
Cloning into 'veewee'...
remote: Reusing existing pack: 13273, done.
remote: Total 13273 (delta 0), reused 0 (delta 0)
Receiving objects: 100% (13273/13273), 4.13 MiB | 1.86 MiB/s, done.
Resolving deltas: 100% (8370/8370), done.
Checking connectivity... done
$USER@$HOST ~ $ cd veewee/
You are using '.rvmrc', it requires trusting, it is slower and it is not compatible with other ruby managers,
you can switch to '.ruby-version' using 'rvm rvmrc to [.]ruby-version'
or ignore this warning with 'rvm rvmrc warning ignore /home/$USER/veewee/.rvmrc',
'.rvmrc' will continue to be the default project file in RVM 1 and RVM 2,
to ignore the warning for all files run 'rvm rvmrc warning ignore all.rvmrcs'.

********************************************************************************************************************
* NOTICE                                                                                                           *
********************************************************************************************************************
* RVM has encountered a new or modified .rvmrc file in the current directory, this is a shell script and           *
* therefore may contain any shell commands.                                                                        *
*                                                                                                                  *
* Examine the contents of this file carefully to be sure the contents are safe before trusting it!                 *
* Do you wish to trust '/home/$USER/veewee/.rvmrc'?                                                                *
* Choose v[iew] below to view the contents                                                                         *
********************************************************************************************************************
y[es], n[o], v[iew], c[ancel]> v
********************************************************************************************************************
* The contents of the .rvmrc file will now be displayed.                                                           *
* After reading the file, you will be prompted again for 'yes or no' to set the trust level for this particular    *
* version of the file.                                                                                             *
*                                                                                                                  *
* Note: You will be re-prompted each time the .rvmrc file's contents change                                        *
* changes, and may change the trust setting manually at any time.                                                  *
********************************************************************************************************************
(( press a key to review the .rvmrc file ))
rvm use ruby-1.9.2@veewee --create
#rvm use ruby-1.8.7@veewee --create

alias veewee="bundle exec veewee"
alias irb="bundle exec irb"
#alias vagrant="bundle exec vagrant"
********************************************************************************************************************
* Viewing of /home/$USER/veewee/.rvmrc complete.                                                                   *
********************************************************************************************************************
* Trusting an .rvmrc file means that whenever you cd into this directory, RVM will run this .rvmrc shell script.   *
* Note that if the contents of the file change, you will be re-prompted to review the file and adjust its trust    *
* settings. You may also change the trust settings manually at any time with the 'rvm rvmrc' command.              *
********************************************************************************************************************
y[es], n[o], v[iew], c[ancel]> y
gemset veewee is not existing, creating.
ruby-1.9.2-p320 - #gemset created /home/$USER/.rvm/gems/ruby-1.9.2-p320@veewee
ruby-1.9.2-p320 - #generating veewee wrappers.
Using /home/$USER/.rvm/gems/ruby-1.9.2-p320 with gemset veewee

A lot has happened in the previous code block.

We descended into the home folder of the current user (you can install veewee somewhere else if you want).
There we cloned the github repository.
Next we descended into the cloned directory. This activated rvm since it contained a .rvmrc file. Which is a project configuration file for rvm. More info on this can be found here.

By looking at the .rvmrc file we see that this script creates an environment ruby-1.9.2@veewee. This means a named gemset called veewee for ruby-1.9.2. It also sets up an alias which allows the linux users to just call veewee.

Install bundler gem

For this make sure that rvm is in the correct environment. You can check the current environment with:

$USER@$HOST ~ $ rvm current
ruby-1.9.2-p320

To change to the veewee environment you can execute:

$USER@$HOST ~ $ rvm use ruby-1.9.2-p320@veewee
Using /home/$USER/.rvm/gems/ruby-1.9.2-p320 with gemset veewee

A safety check doesn't hurt

$USER@$HOST ~ $ rvm current
ruby-1.9.2-p320@veewee

Now we can install the gem

gem install bundler

Finally install veewee

We have got the veewee source code in $HOME/veewee thanks to the clone of the github repository. We will descend into this directory and install veewee as a gem by executing bundle install. (As in previous section it is important that the ruby-1.9.2-p320@veewee environment is active).

$USER@$HOST ~/veewee $ bundle install
Fetching https://github.com/hh/em-winrm.git
remote: Counting objects: 144, done.
remote: Compressing objects: 100% (76/76), done.
remote: Total 144 (delta 67), reused 144 (delta 67)
Receiving objects: 100% (144/144), 24.26 KiB | 0 bytes/s, done.
Resolving deltas: 100% (67/67), done.
Fetching gem metadata from http://rubygems.org/........
Fetching gem metadata from http://rubygems.org/..
Resolving dependencies...
Installing rake (10.1.1) 
Installing libxml-ruby (2.7.0) 
Installing CFPropertyList (2.0.17) 
Installing Platform (0.4.0) 
Installing builder (3.2.2) 
Installing gyoku (1.1.0) 
Installing mini_portile (0.5.2) 
Installing nokogiri (1.6.1) 
Installing akami (1.2.0) 
Installing ansi (1.3.0) 
Using bundler (1.3.5) 
Installing ffi (1.9.3) 
Installing childprocess (0.3.9) 
Installing diff-lcs (1.2.5) 
Installing eventmachine (1.0.0.beta.3) 
Installing mixlib-log (1.6.0) 
Installing uuidtools (2.1.4) 
Installing gssapi (1.0.3) 
Installing httpclient (2.3.4.1) 
Installing little-plugger (1.1.3) 
Installing multi_json (1.8.2) 
Installing logging (1.8.1) 
Installing rubyntlm (0.1.1) 
Installing rack (1.5.2) 
Installing httpi (0.9.7) 
Installing nori (1.1.5) 
Installing wasabi (1.0.0) 
Installing savon (0.9.5) 
Installing winrm (1.1.3) 
Using em-winrm (0.5.4.rc.1) from https://github.com/hh/em-winrm.git (at 3174560) 
Installing excon (0.31.0) 
Installing fission (0.4.0) 
Installing formatador (0.2.4) 
Installing mime-types (1.25.1) 
Installing net-ssh (2.7.0) 
Installing net-scp (1.1.2) 
Installing ruby-hmac (0.4.0) 
Installing fog (1.19.0) 
Installing posix-spawn (0.3.8) 
Installing grit (2.5.0) 
Installing highline (1.6.20) 
Installing i18n (0.6.9) 
Installing json (1.8.1) 
Installing log4r (1.1.10) 
Installing open4 (1.3.0) 
Installing os (0.9.6) 
Installing popen4 (0.1.2) 
Installing progressbar (0.21.0) 
Installing rspec-core (2.14.7) 
Installing rspec-expectations (2.14.4) 
Installing rspec-mocks (2.14.4) 
Installing rspec (2.14.1) 
Installing ruby-vnc (1.0.1) 
Installing thor (0.18.1) 
Using veewee (0.3.12) from source at /home/$USER/veewee 
Your bundle is complete!
Gems in the group kvm were not installed.
Use `bundle show [gemname]` to see where a bundled gem is installed.

Installing kvm support

This is based on the serverguide from ubuntu: https://help.ubuntu.com/lts/serverguide/libvirt.html

Install the packages

sudo apt-get install kvm libvirt-bin libvirt-dev cpu-checker

Add the current user to the libvirtd group

With current user I mean the user which will be administrating the VM's

sudo adduser $USER libvirtd

To activate this change it is best to logout and login again. In order to avoid strang problems in the future, it is best to do the logout now :-).

Check whether kvm is an option for your processor

USRE@HOST ~ $ kvm-ok 
INFO: /dev/kvm exists
KVM acceleration can be used

Installing the ruby-libvirt gem

As before make sure we are in the correct rvm environment

$USER@$HOST ~ $ rvm current
ruby-1.9.2-p320@veewee

Install the gem

$USER@$HOST ~/veewee $ gem install ruby-libvirt
Building native extensions.  This could take a while...
Successfully installed ruby-libvirt-0.5.1
Installing ri documentation for ruby-libvirt-0.5.1
Done installing documentation for ruby-libvirt after 0 seconds
1 gem installed

Make sure the new gem is in the context of your bundle

bundle install --without restrictions

Logout and login before building kvms (otherwise you might get a permission denied like:)

 
There was a problem opening a connection to libvirt: Error making a connection to libvirt URI qemu:///system:
Call to virConnectOpen failed: Failed to connect socket to '/var/run/libvirt/libvirt-sock': Permission denied

This error is a permission error. Possibly because the user executing the command is not in the libvirtd group.

Create a libvirt storage pool

The following ruby script can be used to create a storage pool. A storage pool is necessary as there the disks will be placed. For libvirt one of the possiblities is to set a directory as a repository. Since this is an easy solution we go for these approach. The following script is borrowed from http://libvirt.org/ruby/examples/storage.rb. It is just adapted in order to only create the storage pool and no volumes. Make sure you change the path (it has the dummy value USER in it).

# http://libvirt.org/ruby/examples/storage.rb
# this program demonstrates the use of the libvirt storage APIs.  In particular
# it demonstrates directory pool creation, volume creation, and teardown.
# libvirt supports many other kinds of storage pools, including iSCSI, NFS,
# etc.  See http://libvirt.org/formatstorage.html for more details

require 'libvirt'

# a directory storage pool.  
storage_pool_xml = <
  libvirt-pool
  
    /home/$USER/libvirt-pool
  

EOF

# open up the connection to libvirt
conn = Libvirt::open('qemu:///system')

# print out how many storage pools are currently active
puts "Number of storage pools: #{conn.num_of_storage_pools}"

# create our new storage pool
pool = conn.define_storage_pool_xml(storage_pool_xml)

# build the storage pool.  The operation that this performs is pool-specific;
# in the case of a directory pool, it does the equivalent of mkdir to create
# the directory
pool.build

# start up the pool
pool.create

# print out how many active storage pools are now there; this should be one
# more than before
puts "Number of storage pools: #{conn.num_of_storage_pools}"

# print out some information about the pool.  Note that allocation can be
# much less than capacity; see the discussion for the storage volume XML for
# more details
puts "Storage Pool:"
puts " Name: #{pool.name}"
puts " UUID: #{pool.uuid}"
puts " Autostart?: #{pool.autostart?}"


conn.close

Run this in your rvm environment (ruby-1.9.2-p320@veewee) and with ruby

 
$USER@$HOST ~/libvirt $ ruby storage.rb 
Number of storage pools: 0
Number of storage pools: 1
Storage Pool:
 Name: libvirt-pool
 UUID: fdaada6f-7d0d-484f-9434-fc43e25bd43e
 Autostart?: false

Create a basebox using veewee

Now we are ready to create our basebox. We will create a basebox for Oracle Linux 6.5. Veewee make use of template directories describing VMs out of which it builds the baseboxes. In the version that I cloned from github there was no template for Oracle Linux 6.5 yet. Since the differences between Oracle Linux 6.4 and 6.5 do not impose big changes on the installation procedure we can create a new template directory based on the template of Oracle Linux 6.

cd ~/veewee
cp -R templates/OracleLinux-6.4-x86_64-DVD templates/OracleLinux-6.4-x86_65-DVD

In the definition.rb the VM is defined. Here it explains how the VM will be build. We need to use a different iso but other than that we will keep the same definition. Change the iso details:

$USER@$HOST ~/veewee $ diff templates/OracleLinux-6.5-x86_64-DVD/definition.rb templates/OracleLinux-6.4-x86_64-DVD/definition.rb 
8,10c8,10
<   :iso_file => "OracleLinux-R6-U5-Server-x86_64-dvd.iso",
<   :iso_src => "http://mirrors.dotsrc.org/oracle-linux/OL6/U5/x86_64/OracleLinux-R6-U5-Server-x86_64-dvd.iso",
<   :iso_md5 => "774fb999e4ed43341dcdf5ebc0d48f42",
---
>   :iso_file => "OracleLinux-R6-U4-Server-x86_64-dvd.iso",
>   :iso_src => "http://mirrors.dotsrc.org/oracle-linux/OL6/U4/x86_64/OracleLinux-R6-U4-Server-x86_64-dvd.iso",
>   :iso_md5 => "744fc1663519b4d54da1345669fcee52",

Next we can create a definition for a kvm VM out of the template, we call it oel65_kvm. A definition is like a working copy of a template. It alows you to create definitions for servers with different software installed on them. For this first example we keep the definition the same as the template:

$USER@$HOST ~/veewee $ veewee kvm define 'oel65_kvm' 'OracleLinux-6.5-x86_64-DVD' --workdir=/home/$USER/veewee
The basebox 'oel65_kvm' has been successfully created from the template 'OracleLinux-6.5-x86_64-DVD'
You can now edit the definition files stored in /home/$USER/veewee/definitions/oel65_kvm or build the box with:
veewee kvm build 'oel65_kvm' --workdir=/home/$USER/veewee

Since we won't change this definition we will directly build the box:

$USER@$HOST ~/veewee $ veewee kvm build 'oel65_kvm' --workdir=/home/$USER/veewee
Building Box oel65_kvm with Definition oel65_kvm:
- debug : false
- cwd : /home/$USER/veewee
- force : false
- nogui : false
- auto : false
- checksum : false
- postinstall_include : []
- postinstall_exclude : []
- use_emulation : false
- network_name : default

The isofile OracleLinux-R6-U5-Server-x86_64-dvd.iso already exists.
Waiting 10 seconds for the machine to boot
Finding unused TCP port in range: 7122 - 7199
Selected TCP port 7122
Sending keystrokes to VNC port :0 - TCP port: 5900
Starting a webserver :7122
Typing:[1]:  text ks=http://192.168.75.18:7122/ks.cfg
Done typing.

Serving file /home/$USER/veewee/definitions/oel65_kvm/ks.cfg
Shutting down for /home/$USER/veewee/definitions/oel65_kvm/ks.cfg
Waiting for ssh login on 192.168.122.162 with user veewee to sshd on port => 22 to work, timeout=10000 sec
.........................................................................
Transferring /tmp/.veewee_version20131228-7059-18zzcu6 to .veewee_version 
..
Waiting for ssh login on 192.168.122.162 with user veewee to sshd on port => 22 to work, timeout=10000 sec
.
Transferring /tmp/.veewee_params20131228-7059-e1ql2d to .veewee_params 
..
Waiting for ssh login on 192.168.122.162 with user veewee to sshd on port => 22 to work, timeout=10000 sec
.
Transferring /home/$USER/veewee/definitions/oel65_kvm/proxy.sh to proxy.sh 
..
Waiting for ssh login on 192.168.122.162 with user veewee to sshd on port => 22 to work, timeout=10000 sec
.
Executing command: chmod +x "proxy.sh"
Waiting for ssh login on 192.168.122.162 with user veewee to sshd on port => 22 to work, timeout=10000 sec
.
Transferring /home/$USER/veewee/definitions/oel65_kvm/base.sh to base.sh 
..
Waiting for ssh login on 192.168.122.162 with user veewee to sshd on port => 22 to work, timeout=10000 sec
.
Executing command: chmod +x "base.sh"
Waiting for ssh login on 192.168.122.162 with user veewee to sshd on port => 22 to work, timeout=10000 sec
.
Transferring /home/$USER/veewee/definitions/oel65_kvm/chef.sh to chef.sh 
..
Waiting for ssh login on 192.168.122.162 with user veewee to sshd on port => 22 to work, timeout=10000 sec
.
Executing command: chmod +x "chef.sh"
Waiting for ssh login on 192.168.122.162 with user veewee to sshd on port => 22 to work, timeout=10000 sec
.
Transferring /home/$USER/veewee/definitions/oel65_kvm/puppet.sh to puppet.sh 
..
Waiting for ssh login on 192.168.122.162 with user veewee to sshd on port => 22 to work, timeout=10000 sec
.
Executing command: chmod +x "puppet.sh"
Waiting for ssh login on 192.168.122.162 with user veewee to sshd on port => 22 to work, timeout=10000 sec
.
Transferring /home/$USER/veewee/definitions/oel65_kvm/vagrant.sh to vagrant.sh 
..
Waiting for ssh login on 192.168.122.162 with user veewee to sshd on port => 22 to work, timeout=10000 sec
.
Executing command: chmod +x "vagrant.sh"
Waiting for ssh login on 192.168.122.162 with user veewee to sshd on port => 22 to work, timeout=10000 sec
.
Transferring /home/$USER/veewee/definitions/oel65_kvm/virtualbox.sh to virtualbox.sh 
..
Waiting for ssh login on 192.168.122.162 with user veewee to sshd on port => 22 to work, timeout=10000 sec
.
Executing command: chmod +x "virtualbox.sh"
Waiting for ssh login on 192.168.122.162 with user veewee to sshd on port => 22 to work, timeout=10000 sec
.
Transferring /home/$USER/veewee/definitions/oel65_kvm/cleanup.sh to cleanup.sh 
..
Waiting for ssh login on 192.168.122.162 with user veewee to sshd on port => 22 to work, timeout=10000 sec
.
Executing command: chmod +x "cleanup.sh"
Waiting for ssh login on 192.168.122.162 with user veewee to sshd on port => 22 to work, timeout=10000 sec
.
Transferring /home/$USER/veewee/definitions/oel65_kvm/zerodisk.sh to zerodisk.sh 
..
Waiting for ssh login on 192.168.122.162 with user veewee to sshd on port => 22 to work, timeout=10000 sec
.
Executing command: chmod +x "zerodisk.sh"
Waiting for ssh login on 192.168.122.162 with user veewee to sshd on port => 22 to work, timeout=10000 sec
.
Executing command: echo 'veewee'|sudo -S sh './proxy.sh'
Waiting for ssh login on 192.168.122.162 with user veewee to sshd on port => 22 to work, timeout=10000 sec
.
Executing command: echo 'veewee'|sudo -S sh './base.sh'
--2013-12-28 10:56:33--  https://public-yum.oracle.com/public-yum-ol6.repo
Resolving public-yum.oracle.com... 2.22.55.98, 2.22.55.123
Connecting to public-yum.oracle.com|2.22.55.98|:443... connected.
ERROR: certificate common name “a248.e.akamai.net” doesn’t match requested host name “public-yum.oracle.com”.
To connect to public-yum.oracle.com insecurely, use ‘--no-check-certificate’.
Loaded plugins: security
public_ol6_UEKR3_latest                                  | 1.2 kB     00:00     
public_ol6_UEKR3_latest/primary                          | 2.3 MB     00:00     
public_ol6_UEKR3_latest                                                   77/77
public_ol6_latest                                        | 1.4 kB     00:00     
public_ol6_latest/primary                                |  35 MB     00:16     
public_ol6_latest                                                   24509/24509
Setting up Update Process
Resolving Dependencies
--> Running transaction check
---> Package ca-certificates.noarch 0:2013.1.94-65.0.el6 will be updated
---> Package ca-certificates.noarch 0:2013.1.95-65.1.el6_5 will be an update
---> Package dmidecode.x86_64 1:2.11-2.el6 will be updated
---> Package dmidecode.x86_64 1:2.11-2.el6_1 will be an update
---> Package dracut.noarch 0:004-335.0.1.el6 will be updated
---> Package dracut.noarch 0:004-336.0.1.el6_5.2 will be an update
---> Package dracut-kernel.noarch 0:004-335.0.1.el6 will be updated
---> Package dracut-kernel.noarch 0:004-336.0.1.el6_5.2 will be an update
---> Package kernel.x86_64 0:2.6.32-431.1.2.el6 will be installed
---> Package kernel-firmware.noarch 0:2.6.32-431.el6 will be updated
---> Package kernel-firmware.noarch 0:2.6.32-431.1.2.el6 will be an update
---> Package kernel-uek.x86_64 0:3.8.13-16.3.1.el6uek will be installed
---> Package kernel-uek-firmware.noarch 0:3.8.13-16.3.1.el6uek will be installed
---> Package libjpeg-turbo.x86_64 0:1.2.1-1.el6 will be updated
---> Package libjpeg-turbo.x86_64 0:1.2.1-3.el6_5 will be an update
---> Package nspr.x86_64 0:4.10.0-1.el6 will be updated
---> Package nspr.x86_64 0:4.10.2-1.el6_5 will be an update
---> Package nss.x86_64 0:3.15.1-15.0.1.el6 will be updated
---> Package nss.x86_64 0:3.15.3-3.0.1.el6_5 will be an update
---> Package nss-sysinit.x86_64 0:3.15.1-15.0.1.el6 will be updated
---> Package nss-sysinit.x86_64 0:3.15.3-3.0.1.el6_5 will be an update
---> Package nss-tools.x86_64 0:3.15.1-15.0.1.el6 will be updated
---> Package nss-tools.x86_64 0:3.15.3-3.0.1.el6_5 will be an update
---> Package nss-util.x86_64 0:3.15.1-3.el6 will be updated
---> Package nss-util.x86_64 0:3.15.3-1.el6_5 will be an update
---> Package openssl.x86_64 0:1.0.1e-15.el6 will be updated
---> Package openssl.x86_64 0:1.0.1e-16.el6_5.1 will be an update
---> Package pixman.x86_64 0:0.26.2-5.el6_4 will be updated
---> Package pixman.x86_64 0:0.26.2-5.1.el6_5 will be an update
---> Package system-config-network-tui.noarch 0:1.6.0.el6.2-1.0.3.el6 will be updated
---> Package system-config-network-tui.noarch 0:1.6.0.el6.3-1.0.1.el6 will be an update
---> Package systemtap-runtime.x86_64 0:2.3-3.0.1.el6 will be updated
---> Package systemtap-runtime.x86_64 0:2.3-4.0.1.el6_5 will be an update
---> Package tzdata.noarch 0:2013g-1.el6 will be updated
---> Package tzdata.noarch 0:2013i-1.el6 will be an update
---> Package yum.noarch 0:3.2.29-40.0.1.el6 will be updated
---> Package yum.noarch 0:3.2.29-43.0.1.el6_5 will be an update
--> Finished Dependency Resolution

Dependencies Resolved

================================================================================
 Package             Arch   Version               Repository               Size
================================================================================
Installing:
 kernel              x86_64 2.6.32-431.1.2.el6    public_ol6_latest        28 M
 kernel-uek          x86_64 3.8.13-16.3.1.el6uek  public_ol6_UEKR3_latest  41 M
 kernel-uek-firmware noarch 3.8.13-16.3.1.el6uek  public_ol6_UEKR3_latest 1.6 M
Updating:
 ca-certificates     noarch 2013.1.95-65.1.el6_5  public_ol6_latest       1.1 M
 dmidecode           x86_64 1:2.11-2.el6_1        public_ol6_latest        71 k
 dracut              noarch 004-336.0.1.el6_5.2   public_ol6_latest       122 k
 dracut-kernel       noarch 004-336.0.1.el6_5.2   public_ol6_latest        24 k
 kernel-firmware     noarch 2.6.32-431.1.2.el6    public_ol6_latest        13 M
 libjpeg-turbo       x86_64 1.2.1-3.el6_5         public_ol6_latest       174 k
 nspr                x86_64 4.10.2-1.el6_5        public_ol6_latest       112 k
 nss                 x86_64 3.15.3-3.0.1.el6_5    public_ol6_latest       821 k
 nss-sysinit         x86_64 3.15.3-3.0.1.el6_5    public_ol6_latest        39 k
 nss-tools           x86_64 3.15.3-3.0.1.el6_5    public_ol6_latest       358 k
 nss-util            x86_64 3.15.3-1.el6_5        public_ol6_latest        64 k
 openssl             x86_64 1.0.1e-16.el6_5.1     public_ol6_latest       1.5 M
 pixman              x86_64 0.26.2-5.1.el6_5      public_ol6_latest       200 k
 system-config-network-tui
                     noarch 1.6.0.el6.3-1.0.1.el6 public_ol6_latest       818 k
 systemtap-runtime   x86_64 2.3-4.0.1.el6_5       public_ol6_latest       188 k
 tzdata              noarch 2013i-1.el6           public_ol6_latest       447 k
 yum                 noarch 3.2.29-43.0.1.el6_5   public_ol6_latest       996 k

Transaction Summary
================================================================================
Install       3 Package(s)
Upgrade      17 Package(s)

Total download size: 91 M
Downloading Packages:
(1/20): ca-certificates-2013.1.95-65.1.el6_5.noarch.rpm  | 1.1 MB     00:00     
(2/20): dmidecode-2.11-2.el6_1.x86_64.rpm                |  71 kB     00:00     
(3/20): dracut-004-336.0.1.el6_5.2.noarch.rpm            | 122 kB     00:00     
(4/20): dracut-kernel-004-336.0.1.el6_5.2.noarch.rpm     |  24 kB     00:00     
(5/20): kernel-2.6.32-431.1.2.el6.x86_64.rpm             |  28 MB     00:08     
(6/20): kernel-firmware-2.6.32-431.1.2.el6.noarch.rpm    |  13 MB     00:03     
(7/20): kernel-uek-3.8.13-16.3.1.el6uek.x86_64.rpm       |  41 MB     00:12     
(8/20): kernel-uek-firmware-3.8.13-16.3.1.el6uek.noarch. | 1.6 MB     00:00     
(9/20): libjpeg-turbo-1.2.1-3.el6_5.x86_64.rpm           | 174 kB     00:00     
(10/20): nspr-4.10.2-1.el6_5.x86_64.rpm                  | 112 kB     00:00     
(11/20): nss-3.15.3-3.0.1.el6_5.x86_64.rpm               | 821 kB     00:00     
(12/20): nss-sysinit-3.15.3-3.0.1.el6_5.x86_64.rpm       |  39 kB     00:00     
(13/20): nss-tools-3.15.3-3.0.1.el6_5.x86_64.rpm         | 358 kB     00:00     
(14/20): nss-util-3.15.3-1.el6_5.x86_64.rpm              |  64 kB     00:00     
(15/20): openssl-1.0.1e-16.el6_5.1.x86_64.rpm            | 1.5 MB     00:00     
(16/20): pixman-0.26.2-5.1.el6_5.x86_64.rpm              | 200 kB     00:00     
(17/20): system-config-network-tui-1.6.0.el6.3-1.0.1.el6 | 818 kB     00:00     
(18/20): systemtap-runtime-2.3-4.0.1.el6_5.x86_64.rpm    | 188 kB     00:00     
(19/20): tzdata-2013i-1.el6.noarch.rpm                   | 447 kB     00:00     
(20/20): yum-3.2.29-43.0.1.el6_5.noarch.rpm              | 996 kB     00:00     
--------------------------------------------------------------------------------
Total                                           3.2 MB/s |  91 MB     00:28     
warning: rpmts_HdrFromFdno: Header V3 RSA/SHA256 Signature, key ID ec551f03: NOKEY
Retrieving key from http://public-yum.oracle.com/RPM-GPG-KEY-oracle-ol6
Importing GPG key 0xEC551F03:
 Userid: "Oracle OSS group (Open Source Software group) "
 From  : http://public-yum.oracle.com/RPM-GPG-KEY-oracle-ol6
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
  Updating   : nspr-4.10.2-1.el6_5.x86_64                                  1/37 
  Updating   : nss-util-3.15.3-1.el6_5.x86_64                              2/37 
  Updating   : nss-3.15.3-3.0.1.el6_5.x86_64                               3/37 
  Updating   : nss-sysinit-3.15.3-3.0.1.el6_5.x86_64                       4/37 
  Installing : kernel-uek-firmware-3.8.13-16.3.1.el6uek.noarch             5/37 
  Updating   : dracut-004-336.0.1.el6_5.2.noarch                           6/37 
  Updating   : dracut-kernel-004-336.0.1.el6_5.2.noarch                    7/37 
  Updating   : ca-certificates-2013.1.95-65.1.el6_5.noarch                 8/37 
  Updating   : kernel-firmware-2.6.32-431.1.2.el6.noarch                   9/37 
  Installing : kernel-2.6.32-431.1.2.el6.x86_64                           10/37 
  Updating   : systemtap-runtime-2.3-4.0.1.el6_5.x86_64                   11/37 
  Updating   : openssl-1.0.1e-16.el6_5.1.x86_64                           12/37 
  Installing : kernel-uek-3.8.13-16.3.1.el6uek.x86_64                     13/37 
  Updating   : nss-tools-3.15.3-3.0.1.el6_5.x86_64                        14/37 
  Updating   : yum-3.2.29-43.0.1.el6_5.noarch                             15/37 
  Updating   : 1:dmidecode-2.11-2.el6_1.x86_64                            16/37 
  Updating   : libjpeg-turbo-1.2.1-3.el6_5.x86_64                         17/37 
  Updating   : system-config-network-tui-1.6.0.el6.3-1.0.1.el6.noarch     18/37 
  Updating   : tzdata-2013i-1.el6.noarch                                  19/37 
  Updating   : pixman-0.26.2-5.1.el6_5.x86_64                             20/37 
  Cleanup    : dracut-kernel-004-335.0.1.el6.noarch                       21/37 
  Cleanup    : dracut-004-335.0.1.el6.noarch                              22/37 
  Cleanup    : yum-3.2.29-40.0.1.el6.noarch                               23/37 
  Cleanup    : kernel-firmware-2.6.32-431.el6.noarch                      24/37 
  Cleanup    : system-config-network-tui-1.6.0.el6.2-1.0.3.el6.noarch     25/37 
  Cleanup    : tzdata-2013g-1.el6.noarch                                  26/37 
  Cleanup    : systemtap-runtime-2.3-3.0.1.el6.x86_64                     27/37 
  Cleanup    : nss-tools-3.15.1-15.0.1.el6.x86_64                         28/37 
  Cleanup    : nss-3.15.1-15.0.1.el6.x86_64                               29/37 
  Cleanup    : nss-sysinit-3.15.1-15.0.1.el6.x86_64                       30/37 
  Cleanup    : nss-util-3.15.1-3.el6.x86_64                               31/37 
  Cleanup    : openssl-1.0.1e-15.el6.x86_64                               32/37 
  Cleanup    : ca-certificates-2013.1.94-65.0.el6.noarch                  33/37 
  Cleanup    : nspr-4.10.0-1.el6.x86_64                                   34/37 
  Cleanup    : 1:dmidecode-2.11-2.el6.x86_64                              35/37 
  Cleanup    : libjpeg-turbo-1.2.1-1.el6.x86_64                           36/37 
  Cleanup    : pixman-0.26.2-5.el6_4.x86_64                               37/37 
  Verifying  : pixman-0.26.2-5.1.el6_5.x86_64                              1/37 
  Verifying  : kernel-2.6.32-431.1.2.el6.x86_64                            2/37 
  Verifying  : tzdata-2013i-1.el6.noarch                                   3/37 
  Verifying  : openssl-1.0.1e-16.el6_5.1.x86_64                            4/37 
  Verifying  : kernel-uek-3.8.13-16.3.1.el6uek.x86_64                      5/37 
  Verifying  : system-config-network-tui-1.6.0.el6.3-1.0.1.el6.noarch      6/37 
  Verifying  : dracut-kernel-004-336.0.1.el6_5.2.noarch                    7/37 
  Verifying  : nss-sysinit-3.15.3-3.0.1.el6_5.x86_64                       8/37 
  Verifying  : nspr-4.10.2-1.el6_5.x86_64                                  9/37 
  Verifying  : kernel-firmware-2.6.32-431.1.2.el6.noarch                  10/37 
  Verifying  : ca-certificates-2013.1.95-65.1.el6_5.noarch                11/37 
  Verifying  : libjpeg-turbo-1.2.1-3.el6_5.x86_64                         12/37 
  Verifying  : 1:dmidecode-2.11-2.el6_1.x86_64                            13/37 
  Verifying  : nss-tools-3.15.3-3.0.1.el6_5.x86_64                        14/37 
  Verifying  : dracut-004-336.0.1.el6_5.2.noarch                          15/37 
  Verifying  : nss-3.15.3-3.0.1.el6_5.x86_64                              16/37 
  Verifying  : systemtap-runtime-2.3-4.0.1.el6_5.x86_64                   17/37 
  Verifying  : yum-3.2.29-43.0.1.el6_5.noarch                             18/37 
  Verifying  : kernel-uek-firmware-3.8.13-16.3.1.el6uek.noarch            19/37 
  Verifying  : nss-util-3.15.3-1.el6_5.x86_64                             20/37 
  Verifying  : libjpeg-turbo-1.2.1-1.el6.x86_64                           21/37 
  Verifying  : openssl-1.0.1e-15.el6.x86_64                               22/37 
  Verifying  : kernel-firmware-2.6.32-431.el6.noarch                      23/37 
  Verifying  : nss-3.15.1-15.0.1.el6.x86_64                               24/37 
  Verifying  : tzdata-2013g-1.el6.noarch                                  25/37 
  Verifying  : nss-tools-3.15.1-15.0.1.el6.x86_64                         26/37 
  Verifying  : dracut-kernel-004-335.0.1.el6.noarch                       27/37 
  Verifying  : ca-certificates-2013.1.94-65.0.el6.noarch                  28/37 
  Verifying  : nspr-4.10.0-1.el6.x86_64                                   29/37 
  Verifying  : yum-3.2.29-40.0.1.el6.noarch                               30/37 
  Verifying  : system-config-network-tui-1.6.0.el6.2-1.0.3.el6.noarch     31/37 
  Verifying  : nss-sysinit-3.15.1-15.0.1.el6.x86_64                       32/37 
  Verifying  : dracut-004-335.0.1.el6.noarch                              33/37 
  Verifying  : nss-util-3.15.1-3.el6.x86_64                               34/37 
  Verifying  : pixman-0.26.2-5.el6_4.x86_64                               35/37 
  Verifying  : 1:dmidecode-2.11-2.el6.x86_64                              36/37 
  Verifying  : systemtap-runtime-2.3-3.0.1.el6.x86_64                     37/37 

Installed:
  kernel.x86_64 0:2.6.32-431.1.2.el6                                            
  kernel-uek.x86_64 0:3.8.13-16.3.1.el6uek                                      
  kernel-uek-firmware.noarch 0:3.8.13-16.3.1.el6uek                             

Updated:
  ca-certificates.noarch 0:2013.1.95-65.1.el6_5                                 
  dmidecode.x86_64 1:2.11-2.el6_1                                               
  dracut.noarch 0:004-336.0.1.el6_5.2                                           
  dracut-kernel.noarch 0:004-336.0.1.el6_5.2                                    
  kernel-firmware.noarch 0:2.6.32-431.1.2.el6                                   
  libjpeg-turbo.x86_64 0:1.2.1-3.el6_5                                          
  nspr.x86_64 0:4.10.2-1.el6_5                                                  
  nss.x86_64 0:3.15.3-3.0.1.el6_5                                               
  nss-sysinit.x86_64 0:3.15.3-3.0.1.el6_5                                       
  nss-tools.x86_64 0:3.15.3-3.0.1.el6_5                                         
  nss-util.x86_64 0:3.15.3-1.el6_5                                              
  openssl.x86_64 0:1.0.1e-16.el6_5.1                                            
  pixman.x86_64 0:0.26.2-5.1.el6_5                                              
  system-config-network-tui.noarch 0:1.6.0.el6.3-1.0.1.el6                      
  systemtap-runtime.x86_64 0:2.3-4.0.1.el6_5                                    
  tzdata.noarch 0:2013i-1.el6                                                   
  yum.noarch 0:3.2.29-43.0.1.el6_5                                              

Complete!
--2013-12-28 10:59:55--  http://download.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm
Resolving download.fedoraproject.org... 209.132.181.16, 80.239.156.215, 85.236.55.6, ...
Connecting to download.fedoraproject.org|209.132.181.16|:80... connected.
HTTP request sent, awaiting response... 302 FOUND
Location: http://fedora.cu.be/epel/6/x86_64/epel-release-6-8.noarch.rpm [following]
--2013-12-28 10:59:56--  http://fedora.cu.be/epel/6/x86_64/epel-release-6-8.noarch.rpm
Resolving fedora.cu.be... 194.50.97.11, 2001:67c:314::feed:cafe
Connecting to fedora.cu.be|194.50.97.11|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 14540 (14K) [application/octet-stream]
Saving to: “epel-release-6-8.noarch.rpm”

100%[======================================>] 14,540      --.-K/s   in 0.03s   

2013-12-28 10:59:56 (447 KB/s) - “epel-release-6-8.noarch.rpm” saved [14540/14540]

warning: epel-release-6-8.noarch.rpm: Header V3 RSA/SHA256 Signature, key ID 0608b895: NOKEY
Preparing...                ########################################### [100%]
   1:epel-release           ########################################### [100%]
Loaded plugins: security
epel/metalink                                            |  23 kB     00:00     
epel                                                     | 4.2 kB     00:00     
epel/primary_db                                          | 5.8 MB     00:07     
Setting up Install Process
Package 1:make-3.81-20.el6.x86_64 already installed and latest version
No package kernel-devel-3.8.13-16.2.1.el6uek.x86_64 available.
Package 4:perl-5.10.1-136.el6.x86_64 already installed and latest version
Package wget-1.12-1.8.el6.x86_64 already installed and latest version
Package curl-7.19.7-37.el6_4.x86_64 already installed and latest version
Package bzip2-1.0.5-7.el6_0.x86_64 already installed and latest version
Resolving Dependencies
--> Running transaction check
---> Package dkms.noarch 0:2.2.0.3-20.el6 will be installed
--> Processing Dependency: kernel-devel for package: dkms-2.2.0.3-20.el6.noarch
---> Package gcc.x86_64 0:4.4.7-4.el6 will be installed
--> Processing Dependency: libgomp = 4.4.7-4.el6 for package: gcc-4.4.7-4.el6.x86_64
--> Processing Dependency: cpp = 4.4.7-4.el6 for package: gcc-4.4.7-4.el6.x86_64
--> Processing Dependency: cloog-ppl >= 0.15 for package: gcc-4.4.7-4.el6.x86_64
--> Processing Dependency: glibc-devel >= 2.2.90-12 for package: gcc-4.4.7-4.el6.x86_64
--> Processing Dependency: libgomp.so.1()(64bit) for package: gcc-4.4.7-4.el6.x86_64
---> Package gcc-c++.x86_64 0:4.4.7-4.el6 will be installed
--> Processing Dependency: libstdc++-devel = 4.4.7-4.el6 for package: gcc-c++-4.4.7-4.el6.x86_64
--> Processing Dependency: libmpfr.so.1()(64bit) for package: gcc-c++-4.4.7-4.el6.x86_64
---> Package kernel-uek-devel.x86_64 0:3.8.13-16.2.1.el6uek will be installed
--> Processing Dependency: libdtrace-ctf for package: kernel-uek-devel-3.8.13-16.2.1.el6uek.x86_64
---> Package openssl-devel.x86_64 0:1.0.1e-16.el6_5.1 will be installed
--> Processing Dependency: krb5-devel for package: openssl-devel-1.0.1e-16.el6_5.1.x86_64
---> Package readline-devel.x86_64 0:6.0-4.el6 will be installed
--> Processing Dependency: ncurses-devel for package: readline-devel-6.0-4.el6.x86_64
---> Package sqlite-devel.x86_64 0:3.6.20-1.el6 will be installed
---> Package zlib-devel.x86_64 0:1.2.3-29.el6 will be installed
--> Running transaction check
---> Package cloog-ppl.x86_64 0:0.15.7-1.2.el6 will be installed
--> Processing Dependency: libppl_c.so.2()(64bit) for package: cloog-ppl-0.15.7-1.2.el6.x86_64
--> Processing Dependency: libppl.so.7()(64bit) for package: cloog-ppl-0.15.7-1.2.el6.x86_64
---> Package cpp.x86_64 0:4.4.7-4.el6 will be installed
---> Package glibc-devel.x86_64 0:2.12-1.132.el6 will be installed
--> Processing Dependency: glibc-headers = 2.12-1.132.el6 for package: glibc-devel-2.12-1.132.el6.x86_64
--> Processing Dependency: glibc-headers for package: glibc-devel-2.12-1.132.el6.x86_64
---> Package kernel-devel.x86_64 0:2.6.32-431.1.2.el6 will be installed
---> Package krb5-devel.x86_64 0:1.10.3-10.el6_4.6 will be installed
--> Processing Dependency: libselinux-devel for package: krb5-devel-1.10.3-10.el6_4.6.x86_64
--> Processing Dependency: libcom_err-devel for package: krb5-devel-1.10.3-10.el6_4.6.x86_64
--> Processing Dependency: keyutils-libs-devel for package: krb5-devel-1.10.3-10.el6_4.6.x86_64
---> Package libdtrace-ctf.x86_64 0:0.4.0-1 will be installed
---> Package libgomp.x86_64 0:4.4.7-4.el6 will be installed
---> Package libstdc++-devel.x86_64 0:4.4.7-4.el6 will be installed
---> Package mpfr.x86_64 0:2.4.1-6.el6 will be installed
---> Package ncurses-devel.x86_64 0:5.7-3.20090208.el6 will be installed
--> Running transaction check
---> Package glibc-headers.x86_64 0:2.12-1.132.el6 will be installed
--> Processing Dependency: kernel-headers >= 2.2.1 for package: glibc-headers-2.12-1.132.el6.x86_64
--> Processing Dependency: kernel-headers for package: glibc-headers-2.12-1.132.el6.x86_64
---> Package keyutils-libs-devel.x86_64 0:1.4-4.el6 will be installed
---> Package libcom_err-devel.x86_64 0:1.42.8-1.0.1.el6 will be installed
---> Package libselinux-devel.x86_64 0:2.0.94-5.3.el6_4.1 will be installed
--> Processing Dependency: libsepol-devel >= 2.0.32-1 for package: libselinux-devel-2.0.94-5.3.el6_4.1.x86_64
--> Processing Dependency: pkgconfig(libsepol) for package: libselinux-devel-2.0.94-5.3.el6_4.1.x86_64
---> Package ppl.x86_64 0:0.10.2-11.el6 will be installed
--> Running transaction check
---> Package kernel-uek-headers.x86_64 0:3.8.13-16.3.1.el6uek will be installed
---> Package libsepol-devel.x86_64 0:2.0.41-4.el6 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

================================================================================
 Package             Arch   Version               Repository               Size
================================================================================
Installing:
 dkms                noarch 2.2.0.3-20.el6        epel                     75 k
 gcc                 x86_64 4.4.7-4.el6           public_ol6_latest        10 M
 gcc-c++             x86_64 4.4.7-4.el6           public_ol6_latest       4.7 M
 kernel-uek-devel    x86_64 3.8.13-16.2.1.el6uek  public_ol6_UEKR3_latest 8.8 M
 openssl-devel       x86_64 1.0.1e-16.el6_5.1     public_ol6_latest       1.2 M
 readline-devel      x86_64 6.0-4.el6             public_ol6_latest       134 k
 sqlite-devel        x86_64 3.6.20-1.el6          public_ol6_latest        80 k
 zlib-devel          x86_64 1.2.3-29.el6          public_ol6_latest        43 k
Installing for dependencies:
 cloog-ppl           x86_64 0.15.7-1.2.el6        public_ol6_latest        93 k
 cpp                 x86_64 4.4.7-4.el6           public_ol6_latest       3.7 M
 glibc-devel         x86_64 2.12-1.132.el6        public_ol6_latest       977 k
 glibc-headers       x86_64 2.12-1.132.el6        public_ol6_latest       608 k
 kernel-devel        x86_64 2.6.32-431.1.2.el6    public_ol6_latest       8.8 M
 kernel-uek-headers  x86_64 3.8.13-16.3.1.el6uek  public_ol6_UEKR3_latest 912 k
 keyutils-libs-devel x86_64 1.4-4.el6             public_ol6_latest        28 k
 krb5-devel          x86_64 1.10.3-10.el6_4.6     public_ol6_latest       494 k
 libcom_err-devel    x86_64 1.42.8-1.0.1.el6      public_ol6_latest        32 k
 libdtrace-ctf       x86_64 0.4.0-1               public_ol6_UEKR3_latest  27 k
 libgomp             x86_64 4.4.7-4.el6           public_ol6_latest       118 k
 libselinux-devel    x86_64 2.0.94-5.3.el6_4.1    public_ol6_latest       135 k
 libsepol-devel      x86_64 2.0.41-4.el6          public_ol6_latest        63 k
 libstdc++-devel     x86_64 4.4.7-4.el6           public_ol6_latest       1.6 M
 mpfr                x86_64 2.4.1-6.el6           public_ol6_latest       156 k
 ncurses-devel       x86_64 5.7-3.20090208.el6    public_ol6_latest       643 k
 ppl                 x86_64 0.10.2-11.el6         public_ol6_latest       1.3 M

Transaction Summary
================================================================================
Install      25 Package(s)

Total download size: 45 M
Installed size: 122 M
Downloading Packages:
(1/25): cloog-ppl-0.15.7-1.2.el6.x86_64.rpm              |  93 kB     00:00     
(2/25): cpp-4.4.7-4.el6.x86_64.rpm                       | 3.7 MB     00:01     
(3/25): dkms-2.2.0.3-20.el6.noarch.rpm                   |  75 kB     00:00     
(4/25): gcc-4.4.7-4.el6.x86_64.rpm                       |  10 MB     00:03     
(5/25): gcc-c++-4.4.7-4.el6.x86_64.rpm                   | 4.7 MB     00:01     
(6/25): glibc-devel-2.12-1.132.el6.x86_64.rpm            | 977 kB     00:00     
(7/25): glibc-headers-2.12-1.132.el6.x86_64.rpm          | 608 kB     00:00     
(8/25): kernel-devel-2.6.32-431.1.2.el6.x86_64.rpm       | 8.8 MB     00:03     
(9/25): kernel-uek-devel-3.8.13-16.2.1.el6uek.x86_64.rpm | 8.8 MB     00:09     
(10/25): kernel-uek-headers-3.8.13-16.3.1.el6uek.x86_64. | 912 kB     00:00     
(11/25): keyutils-libs-devel-1.4-4.el6.x86_64.rpm        |  28 kB     00:00     
(12/25): krb5-devel-1.10.3-10.el6_4.6.x86_64.rpm         | 494 kB     00:00     
(13/25): libcom_err-devel-1.42.8-1.0.1.el6.x86_64.rpm    |  32 kB     00:00     
(14/25): libdtrace-ctf-0.4.0-1.x86_64.rpm                |  27 kB     00:00     
(15/25): libgomp-4.4.7-4.el6.x86_64.rpm                  | 118 kB     00:00     
(16/25): libselinux-devel-2.0.94-5.3.el6_4.1.x86_64.rpm  | 135 kB     00:00     
(17/25): libsepol-devel-2.0.41-4.el6.x86_64.rpm          |  63 kB     00:00     
(18/25): libstdc++-devel-4.4.7-4.el6.x86_64.rpm          | 1.6 MB     00:00     
(19/25): mpfr-2.4.1-6.el6.x86_64.rpm                     | 156 kB     00:00     
(20/25): ncurses-devel-5.7-3.20090208.el6.x86_64.rpm     | 643 kB     00:00     
(21/25): openssl-devel-1.0.1e-16.el6_5.1.x86_64.rpm      | 1.2 MB     00:00     
(22/25): ppl-0.10.2-11.el6.x86_64.rpm                    | 1.3 MB     00:01     
(23/25): readline-devel-6.0-4.el6.x86_64.rpm             | 134 kB     00:00     
(24/25): sqlite-devel-3.6.20-1.el6.x86_64.rpm            |  80 kB     00:00     
(25/25): zlib-devel-1.2.3-29.el6.x86_64.rpm              |  43 kB     00:00     
--------------------------------------------------------------------------------
Total                                           1.6 MB/s |  45 MB     00:27     
warning: rpmts_HdrFromFdno: Header V3 RSA/SHA256 Signature, key ID 0608b895: NOKEY
Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-6
Importing GPG key 0x0608B895:
 Userid : EPEL (6) 
 Package: epel-release-6-8.noarch (installed)
 From   : /etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-6
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
Warning: RPMDB altered outside of yum.
  Installing : mpfr-2.4.1-6.el6.x86_64                                     1/25 
  Installing : cpp-4.4.7-4.el6.x86_64                                      2/25 
  Installing : libsepol-devel-2.0.41-4.el6.x86_64                          3/25 
  Installing : libselinux-devel-2.0.94-5.3.el6_4.1.x86_64                  4/25 
  Installing : ppl-0.10.2-11.el6.x86_64                                    5/25 
  Installing : cloog-ppl-0.15.7-1.2.el6.x86_64                             6/25 
  Installing : libgomp-4.4.7-4.el6.x86_64                                  7/25 
  Installing : libcom_err-devel-1.42.8-1.0.1.el6.x86_64                    8/25 
  Installing : kernel-uek-headers-3.8.13-16.3.1.el6uek.x86_64              9/25 
  Installing : glibc-headers-2.12-1.132.el6.x86_64                        10/25 
  Installing : glibc-devel-2.12-1.132.el6.x86_64                          11/25 
  Installing : gcc-4.4.7-4.el6.x86_64                                     12/25 
  Installing : libdtrace-ctf-0.4.0-1.x86_64                               13/25 
  Installing : zlib-devel-1.2.3-29.el6.x86_64                             14/25 
  Installing : ncurses-devel-5.7-3.20090208.el6.x86_64                    15/25 
  Installing : keyutils-libs-devel-1.4-4.el6.x86_64                       16/25 
  Installing : krb5-devel-1.10.3-10.el6_4.6.x86_64                        17/25 
  Installing : libstdc++-devel-4.4.7-4.el6.x86_64                         18/25 
  Installing : kernel-devel-2.6.32-431.1.2.el6.x86_64                     19/25 
  Installing : dkms-2.2.0.3-20.el6.noarch                                 20/25 
  Installing : gcc-c++-4.4.7-4.el6.x86_64                                 21/25 
  Installing : openssl-devel-1.0.1e-16.el6_5.1.x86_64                     22/25 
  Installing : readline-devel-6.0-4.el6.x86_64                            23/25 
  Installing : kernel-uek-devel-3.8.13-16.2.1.el6uek.x86_64               24/25 
  Installing : sqlite-devel-3.6.20-1.el6.x86_64                           25/25 
  Verifying  : readline-devel-6.0-4.el6.x86_64                             1/25 
  Verifying  : glibc-devel-2.12-1.132.el6.x86_64                           2/25 
  Verifying  : libselinux-devel-2.0.94-5.3.el6_4.1.x86_64                  3/25 
  Verifying  : openssl-devel-1.0.1e-16.el6_5.1.x86_64                      4/25 
  Verifying  : glibc-headers-2.12-1.132.el6.x86_64                         5/25 
  Verifying  : kernel-devel-2.6.32-431.1.2.el6.x86_64                      6/25 
  Verifying  : libstdc++-devel-4.4.7-4.el6.x86_64                          7/25 
  Verifying  : keyutils-libs-devel-1.4-4.el6.x86_64                        8/25 
  Verifying  : cpp-4.4.7-4.el6.x86_64                                      9/25 
  Verifying  : ncurses-devel-5.7-3.20090208.el6.x86_64                    10/25 
  Verifying  : libdtrace-ctf-0.4.0-1.x86_64                               11/25 
  Verifying  : mpfr-2.4.1-6.el6.x86_64                                    12/25 
  Verifying  : kernel-uek-devel-3.8.13-16.2.1.el6uek.x86_64               13/25 
  Verifying  : zlib-devel-1.2.3-29.el6.x86_64                             14/25 
  Verifying  : gcc-c++-4.4.7-4.el6.x86_64                                 15/25 
  Verifying  : cloog-ppl-0.15.7-1.2.el6.x86_64                            16/25 
  Verifying  : kernel-uek-headers-3.8.13-16.3.1.el6uek.x86_64             17/25 
  Verifying  : libcom_err-devel-1.42.8-1.0.1.el6.x86_64                   18/25 
  Verifying  : libgomp-4.4.7-4.el6.x86_64                                 19/25 
  Verifying  : gcc-4.4.7-4.el6.x86_64                                     20/25 
  Verifying  : dkms-2.2.0.3-20.el6.noarch                                 21/25 
  Verifying  : ppl-0.10.2-11.el6.x86_64                                   22/25 
  Verifying  : libsepol-devel-2.0.41-4.el6.x86_64                         23/25 
  Verifying  : sqlite-devel-3.6.20-1.el6.x86_64                           24/25 
  Verifying  : krb5-devel-1.10.3-10.el6_4.6.x86_64                        25/25 

Installed:
  dkms.noarch 0:2.2.0.3-20.el6                                                  
  gcc.x86_64 0:4.4.7-4.el6                                                      
  gcc-c++.x86_64 0:4.4.7-4.el6                                                  
  kernel-uek-devel.x86_64 0:3.8.13-16.2.1.el6uek                                
  openssl-devel.x86_64 0:1.0.1e-16.el6_5.1                                      
  readline-devel.x86_64 0:6.0-4.el6                                             
  sqlite-devel.x86_64 0:3.6.20-1.el6                                            
  zlib-devel.x86_64 0:1.2.3-29.el6                                              

Dependency Installed:
  cloog-ppl.x86_64 0:0.15.7-1.2.el6                                             
  cpp.x86_64 0:4.4.7-4.el6                                                      
  glibc-devel.x86_64 0:2.12-1.132.el6                                           
  glibc-headers.x86_64 0:2.12-1.132.el6                                         
  kernel-devel.x86_64 0:2.6.32-431.1.2.el6                                      
  kernel-uek-headers.x86_64 0:3.8.13-16.3.1.el6uek                              
  keyutils-libs-devel.x86_64 0:1.4-4.el6                                        
  krb5-devel.x86_64 0:1.10.3-10.el6_4.6                                         
  libcom_err-devel.x86_64 0:1.42.8-1.0.1.el6                                    
  libdtrace-ctf.x86_64 0:0.4.0-1                                                
  libgomp.x86_64 0:4.4.7-4.el6                                                  
  libselinux-devel.x86_64 0:2.0.94-5.3.el6_4.1                                  
  libsepol-devel.x86_64 0:2.0.41-4.el6                                          
  libstdc++-devel.x86_64 0:4.4.7-4.el6                                          
  mpfr.x86_64 0:2.4.1-6.el6                                                     
  ncurses-devel.x86_64 0:5.7-3.20090208.el6                                     
  ppl.x86_64 0:0.10.2-11.el6                                                    

Complete!
Waiting for ssh login on 192.168.122.162 with user veewee to sshd on port => 22 to work, timeout=10000 sec
.
Executing command: echo 'veewee'|sudo -S sh './chef.sh'
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 14101  100 14101    0     0  13933      0  0:00:01  0:00:01 --:--:-- 48126
Downloading Chef  for el...
downloading https://www.opscode.com/chef/metadata?v=&prerelease=false&p=el&pv=6&m=x86_64
  to file /tmp/install.sh.21115/metadata.txt
trying wget...
url	https://opscode-omnibus-packages.s3.amazonaws.com/el/6/x86_64/chef-11.8.2-1.el6.x86_64.rpm
md5	10f3d0da82efa973fe91cc24a6a74549
sha256	044558f38d25bbf75dbd5790ccce892a38e5e9f2a091ed55367ab914fbd1cfed
downloaded metadata file looks valid...
downloading https://opscode-omnibus-packages.s3.amazonaws.com/el/6/x86_64/chef-11.8.2-1.el6.x86_64.rpm
  to file /tmp/install.sh.21115/chef-.x86_64.rpm
trying wget...
Checksum compare with sha256sum succeeded.
Installing Chef 
installing with rpm...
warning: /tmp/install.sh.21115/chef-.x86_64.rpm: Header V4 DSA/SHA1 Signature, key ID 83ef826a: NOKEY
Preparing...                ########################################### [100%]
   1:chef                   ########################################### [100%]
Thank you for installing Chef!
Waiting for ssh login on 192.168.122.162 with user veewee to sshd on port => 22 to work, timeout=10000 sec
.
Executing command: echo 'veewee'|sudo -S sh './puppet.sh'
--2013-12-28 11:01:24--  https://yum.puppetlabs.com/el/6/products/x86_64/puppetlabs-release-6-7.noarch.rpm
Resolving yum.puppetlabs.com... 198.58.114.168, 2600:3c00::f03c:91ff:fe69:6bf0
Connecting to yum.puppetlabs.com|198.58.114.168|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 5712 (5.6K) [application/x-redhat-package-manager]
Saving to: “puppetlabs-release-6-7.noarch.rpm”

100%[======================================>] 5,712       --.-K/s   in 0s      

2013-12-28 11:01:25 (55.8 MB/s) - “puppetlabs-release-6-7.noarch.rpm” saved [5712/5712]

warning: puppetlabs-release-6-7.noarch.rpm: Header V4 RSA/SHA1 Signature, key ID 4bd6ec30: NOKEY
Preparing...                ########################################### [100%]
   1:puppetlabs-release     ########################################### [100%]
Loaded plugins: security
puppetlabs-deps                                          | 1.9 kB     00:00     
puppetlabs-deps/primary_db                               |  21 kB     00:00     
puppetlabs-products                                      | 1.9 kB     00:00     
puppetlabs-products/primary_db                           | 101 kB     00:00     
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package facter.x86_64 1:1.7.4-1.el6 will be installed
--> Processing Dependency: ruby >= 1.8.5 for package: 1:facter-1.7.4-1.el6.x86_64
--> Processing Dependency: /usr/bin/ruby for package: 1:facter-1.7.4-1.el6.x86_64
---> Package puppet.noarch 0:3.4.1-1.el6 will be installed
--> Processing Dependency: ruby-rgen >= 0.6.5 for package: puppet-3.4.1-1.el6.noarch
--> Processing Dependency: hiera >= 1.0.0 for package: puppet-3.4.1-1.el6.noarch
--> Processing Dependency: ruby-augeas for package: puppet-3.4.1-1.el6.noarch
--> Processing Dependency: ruby-shadow for package: puppet-3.4.1-1.el6.noarch
--> Processing Dependency: ruby(selinux) for package: puppet-3.4.1-1.el6.noarch
--> Running transaction check
---> Package hiera.noarch 0:1.3.0-1.el6 will be installed
--> Processing Dependency: rubygem-json for package: hiera-1.3.0-1.el6.noarch
---> Package libselinux-ruby.x86_64 0:2.0.94-5.3.el6_4.1 will be installed
---> Package ruby.x86_64 0:1.8.7.352-13.el6 will be installed
--> Processing Dependency: ruby-libs = 1.8.7.352-13.el6 for package: ruby-1.8.7.352-13.el6.x86_64
--> Processing Dependency: libruby.so.1.8()(64bit) for package: ruby-1.8.7.352-13.el6.x86_64
---> Package ruby-augeas.x86_64 0:0.4.1-1.el6 will be installed
--> Processing Dependency: augeas-libs >= 0.8.0 for package: ruby-augeas-0.4.1-1.el6.x86_64
--> Processing Dependency: libaugeas.so.0(AUGEAS_0.8.0)(64bit) for package: ruby-augeas-0.4.1-1.el6.x86_64
--> Processing Dependency: libaugeas.so.0(AUGEAS_0.12.0)(64bit) for package: ruby-augeas-0.4.1-1.el6.x86_64
--> Processing Dependency: libaugeas.so.0(AUGEAS_0.11.0)(64bit) for package: ruby-augeas-0.4.1-1.el6.x86_64
--> Processing Dependency: libaugeas.so.0(AUGEAS_0.10.0)(64bit) for package: ruby-augeas-0.4.1-1.el6.x86_64
--> Processing Dependency: libaugeas.so.0(AUGEAS_0.1.0)(64bit) for package: ruby-augeas-0.4.1-1.el6.x86_64
--> Processing Dependency: libaugeas.so.0()(64bit) for package: ruby-augeas-0.4.1-1.el6.x86_64
---> Package ruby-rgen.noarch 0:0.6.5-1.el6 will be installed
---> Package ruby-shadow.x86_64 0:1.4.1-13.el6 will be installed
--> Running transaction check
---> Package augeas-libs.x86_64 0:1.0.0-5.el6 will be installed
---> Package ruby-libs.x86_64 0:1.8.7.352-13.el6 will be installed
--> Processing Dependency: libreadline.so.5()(64bit) for package: ruby-libs-1.8.7.352-13.el6.x86_64
---> Package rubygem-json.x86_64 0:1.5.5-1.el6 will be installed
--> Processing Dependency: rubygems for package: rubygem-json-1.5.5-1.el6.x86_64
--> Running transaction check
---> Package compat-readline5.x86_64 0:5.2-17.1.el6 will be installed
---> Package rubygems.noarch 0:1.3.7-5.el6 will be installed
--> Processing Dependency: ruby-rdoc for package: rubygems-1.3.7-5.el6.noarch
--> Running transaction check
---> Package ruby-rdoc.x86_64 0:1.8.7.352-13.el6 will be installed
--> Processing Dependency: ruby-irb = 1.8.7.352-13.el6 for package: ruby-rdoc-1.8.7.352-13.el6.x86_64
--> Running transaction check
---> Package ruby-irb.x86_64 0:1.8.7.352-13.el6 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

================================================================================
 Package            Arch     Version                Repository             Size
================================================================================
Installing:
 facter             x86_64   1:1.7.4-1.el6          puppetlabs-products    87 k
 puppet             noarch   3.4.1-1.el6            puppetlabs-products   1.1 M
Installing for dependencies:
 augeas-libs        x86_64   1.0.0-5.el6            public_ol6_latest     308 k
 compat-readline5   x86_64   5.2-17.1.el6           public_ol6_latest     129 k
 hiera              noarch   1.3.0-1.el6            puppetlabs-products    23 k
 libselinux-ruby    x86_64   2.0.94-5.3.el6_4.1     public_ol6_latest      98 k
 ruby               x86_64   1.8.7.352-13.el6       public_ol6_latest     534 k
 ruby-augeas        x86_64   0.4.1-1.el6            epel                   21 k
 ruby-irb           x86_64   1.8.7.352-13.el6       public_ol6_latest     313 k
 ruby-libs          x86_64   1.8.7.352-13.el6       public_ol6_latest     1.6 M
 ruby-rdoc          x86_64   1.8.7.352-13.el6       public_ol6_latest     376 k
 ruby-rgen          noarch   0.6.5-1.el6            puppetlabs-deps        87 k
 ruby-shadow        x86_64   1.4.1-13.el6           epel                   11 k
 rubygem-json       x86_64   1.5.5-1.el6            puppetlabs-deps       763 k
 rubygems           noarch   1.3.7-5.el6            public_ol6_latest     206 k

Transaction Summary
================================================================================
Install      15 Package(s)

Total download size: 5.7 M
Installed size: 17 M
Downloading Packages:
(1/15): augeas-libs-1.0.0-5.el6.x86_64.rpm               | 308 kB     00:00     
(2/15): compat-readline5-5.2-17.1.el6.x86_64.rpm         | 129 kB     00:00     
(3/15): facter-1.7.4-1.el6.x86_64.rpm                    |  87 kB     00:00     
(4/15): hiera-1.3.0-1.el6.noarch.rpm                     |  23 kB     00:00     
(5/15): libselinux-ruby-2.0.94-5.3.el6_4.1.x86_64.rpm    |  98 kB     00:00     
(6/15): puppet-3.4.1-1.el6.noarch.rpm                    | 1.1 MB     00:01     
(7/15): ruby-1.8.7.352-13.el6.x86_64.rpm                 | 534 kB     00:00     
(8/15): ruby-augeas-0.4.1-1.el6.x86_64.rpm               |  21 kB     00:00     
(9/15): ruby-irb-1.8.7.352-13.el6.x86_64.rpm             | 313 kB     00:00     
(10/15): ruby-libs-1.8.7.352-13.el6.x86_64.rpm           | 1.6 MB     00:00     
(11/15): ruby-rdoc-1.8.7.352-13.el6.x86_64.rpm           | 376 kB     00:00     
(12/15): ruby-rgen-0.6.5-1.el6.noarch.rpm                |  87 kB     00:00     
(13/15): ruby-shadow-1.4.1-13.el6.x86_64.rpm             |  11 kB     00:00     
(14/15): rubygem-json-1.5.5-1.el6.x86_64.rpm             | 763 kB     00:01     
(15/15): rubygems-1.3.7-5.el6.noarch.rpm                 | 206 kB     00:00     
--------------------------------------------------------------------------------
Total                                           753 kB/s | 5.7 MB     00:07     
warning: rpmts_HdrFromFdno: Header V4 RSA/SHA512 Signature, key ID 4bd6ec30: NOKEY
Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-puppetlabs
Importing GPG key 0x4BD6EC30:
 Userid : Puppet Labs Release Key (Puppet Labs Release Key) 
 Package: puppetlabs-release-6-7.noarch (installed)
 From   : /etc/pki/rpm-gpg/RPM-GPG-KEY-puppetlabs
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
Warning: RPMDB altered outside of yum.
  Installing : augeas-libs-1.0.0-5.el6.x86_64                              1/15 
  Installing : compat-readline5-5.2-17.1.el6.x86_64                        2/15 
  Installing : ruby-libs-1.8.7.352-13.el6.x86_64                           3/15 
  Installing : ruby-1.8.7.352-13.el6.x86_64                                4/15 
  Installing : ruby-rgen-0.6.5-1.el6.noarch                                5/15 
  Installing : ruby-irb-1.8.7.352-13.el6.x86_64                            6/15 
  Installing : ruby-rdoc-1.8.7.352-13.el6.x86_64                           7/15 
  Installing : rubygems-1.3.7-5.el6.noarch                                 8/15 
  Installing : rubygem-json-1.5.5-1.el6.x86_64                             9/15 
  Installing : hiera-1.3.0-1.el6.noarch                                   10/15 
  Installing : 1:facter-1.7.4-1.el6.x86_64                                11/15 
  Installing : ruby-augeas-0.4.1-1.el6.x86_64                             12/15 
  Installing : ruby-shadow-1.4.1-13.el6.x86_64                            13/15 
  Installing : libselinux-ruby-2.0.94-5.3.el6_4.1.x86_64                  14/15 
  Installing : puppet-3.4.1-1.el6.noarch                                  15/15 
  Verifying  : hiera-1.3.0-1.el6.noarch                                    1/15 
  Verifying  : libselinux-ruby-2.0.94-5.3.el6_4.1.x86_64                   2/15 
  Verifying  : ruby-augeas-0.4.1-1.el6.x86_64                              3/15 
  Verifying  : ruby-1.8.7.352-13.el6.x86_64                                4/15 
  Verifying  : compat-readline5-5.2-17.1.el6.x86_64                        5/15 
  Verifying  : ruby-rgen-0.6.5-1.el6.noarch                                6/15 
  Verifying  : ruby-rdoc-1.8.7.352-13.el6.x86_64                           7/15 
  Verifying  : puppet-3.4.1-1.el6.noarch                                   8/15 
  Verifying  : ruby-irb-1.8.7.352-13.el6.x86_64                            9/15 
  Verifying  : 1:facter-1.7.4-1.el6.x86_64                                10/15 
  Verifying  : rubygems-1.3.7-5.el6.noarch                                11/15 
  Verifying  : ruby-libs-1.8.7.352-13.el6.x86_64                          12/15 
  Verifying  : rubygem-json-1.5.5-1.el6.x86_64                            13/15 
  Verifying  : augeas-libs-1.0.0-5.el6.x86_64                             14/15 
  Verifying  : ruby-shadow-1.4.1-13.el6.x86_64                            15/15 

Installed:
  facter.x86_64 1:1.7.4-1.el6            puppet.noarch 0:3.4.1-1.el6           

Dependency Installed:
  augeas-libs.x86_64 0:1.0.0-5.el6                                              
  compat-readline5.x86_64 0:5.2-17.1.el6                                        
  hiera.noarch 0:1.3.0-1.el6                                                    
  libselinux-ruby.x86_64 0:2.0.94-5.3.el6_4.1                                   
  ruby.x86_64 0:1.8.7.352-13.el6                                                
  ruby-augeas.x86_64 0:0.4.1-1.el6                                              
  ruby-irb.x86_64 0:1.8.7.352-13.el6                                            
  ruby-libs.x86_64 0:1.8.7.352-13.el6                                           
  ruby-rdoc.x86_64 0:1.8.7.352-13.el6                                           
  ruby-rgen.noarch 0:0.6.5-1.el6                                                
  ruby-shadow.x86_64 0:1.4.1-13.el6                                             
  rubygem-json.x86_64 0:1.5.5-1.el6                                             
  rubygems.noarch 0:1.3.7-5.el6                                                 

Complete!

Waiting for ssh login on 192.168.122.162 with user veewee to sshd on port => 22 to work, timeout=10000 sec
.
Executing command: echo 'veewee'|sudo -S sh './vagrant.sh'
Changing password for user vagrant.
passwd: all authentication tokens updated successfully.
--2013-12-28 11:01:50--  https://raw.github.com/mitchellh/vagrant/master/keys/vagrant.pub
Resolving raw.github.com... 185.31.16.133
Connecting to raw.github.com|185.31.16.133|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 409 [text/plain]
Saving to: “/home/vagrant/.ssh/authorized_keys”

100%[======================================>] 409         --.-K/s   in 0s      

2013-12-28 11:01:50 (3.05 MB/s) - “/home/vagrant/.ssh/authorized_keys” saved [409/409]

Waiting for ssh login on 192.168.122.162 with user veewee to sshd on port => 22 to work, timeout=10000 sec
.
Executing command: echo 'veewee'|sudo -S sh './virtualbox.sh'
cat: /home/veewee/.vbox_version: No such file or directory
/home/veewee/VBoxGuestAdditions_.iso: No such file or directory
sh: /mnt/VBoxLinuxAdditions.run: No such file or directory
umount: /mnt: not mounted
Waiting for ssh login on 192.168.122.162 with user veewee to sshd on port => 22 to work, timeout=10000 sec
.
Executing command: echo 'veewee'|sudo -S sh './cleanup.sh'
Loaded plugins: security
Setting up Remove Process
No Match for argument: avahi
Package(s) avahi available, but not installed.
No Match for argument: bitstream-vera-fonts
Resolving Dependencies
--> Running transaction check
---> Package freetype.x86_64 0:2.3.11-14.el6_3.1 will be erased
--> Processing Dependency: libfreetype.so.6()(64bit) for package: libXft-2.3.1-2.el6.x86_64
--> Processing Dependency: libfreetype.so.6()(64bit) for package: cairo-1.8.8-3.1.el6.x86_64
--> Processing Dependency: libfreetype.so.6()(64bit) for package: pango-1.28.1-7.0.1.el6_3.x86_64
--> Processing Dependency: libfreetype.so.6()(64bit) for package: fontconfig-2.8.0-3.el6.x86_64
--> Processing Dependency: freetype >= 2.1.3-3 for package: pango-1.28.1-7.0.1.el6_3.x86_64
--> Processing Dependency: freetype >= 2.1.3-3 for package: pango-1.28.1-7.0.1.el6_3.x86_64
--> Processing Dependency: freetype >= 2.1.4 for package: fontconfig-2.8.0-3.el6.x86_64
---> Package gtk2.x86_64 0:2.20.1-4.el6 will be erased
--> Processing Dependency: libgdk_pixbuf-2.0.so.0()(64bit) for package: libfprint-0.1.0-19.pre2.el6.x86_64
---> Package hicolor-icon-theme.noarch 0:0.11-1.1.el6 will be erased
---> Package libX11.x86_64 0:1.5.0-4.el6 will be erased
--> Processing Dependency: libX11.so.6()(64bit) for package: libXi-1.6.1-3.el6.x86_64
--> Processing Dependency: libX11.so.6()(64bit) for package: libXrender-0.9.7-2.el6.x86_64
--> Processing Dependency: libX11.so.6()(64bit) for package: libXcomposite-0.4.3-4.el6.x86_64
--> Processing Dependency: libX11.so.6()(64bit) for package: libXfixes-5.0-3.el6.x86_64
--> Processing Dependency: libX11.so.6()(64bit) for package: libXcursor-1.1.13-6.20130524git8f677eaea.el6.x86_64
--> Processing Dependency: libX11.so.6()(64bit) for package: libXdamage-1.1.3-4.el6.x86_64
--> Processing Dependency: libX11.so.6()(64bit) for package: libXinerama-1.1.2-2.el6.x86_64
--> Processing Dependency: libX11.so.6()(64bit) for package: libXext-1.3.1-2.el6.x86_64
--> Processing Dependency: libX11.so.6()(64bit) for package: libXrandr-1.4.0-1.el6.x86_64
--> Processing Dependency: libX11 >= 1.4.99.1 for package: libXi-1.6.1-3.el6.x86_64
--> Running transaction check
---> Package cairo.x86_64 0:1.8.8-3.1.el6 will be erased
---> Package fontconfig.x86_64 0:2.8.0-3.el6 will be erased
---> Package libXcomposite.x86_64 0:0.4.3-4.el6 will be erased
---> Package libXcursor.x86_64 0:1.1.13-6.20130524git8f677eaea.el6 will be erased
---> Package libXdamage.x86_64 0:1.1.3-4.el6 will be erased
---> Package libXext.x86_64 0:1.3.1-2.el6 will be erased
---> Package libXfixes.x86_64 0:5.0-3.el6 will be erased
---> Package libXft.x86_64 0:2.3.1-2.el6 will be erased
---> Package libXi.x86_64 0:1.6.1-3.el6 will be erased
---> Package libXinerama.x86_64 0:1.1.2-2.el6 will be erased
---> Package libXrandr.x86_64 0:1.4.0-1.el6 will be erased
---> Package libXrender.x86_64 0:0.9.7-2.el6 will be erased
---> Package libfprint.x86_64 0:0.1.0-19.pre2.el6 will be erased
--> Processing Dependency: libfprint.so.0()(64bit) for package: fprintd-0.1-21.git04fd09cfa.el6.x86_64
---> Package pango.x86_64 0:1.28.1-7.0.1.el6_3 will be erased
--> Running transaction check
---> Package fprintd.x86_64 0:0.1-21.git04fd09cfa.el6 will be erased
--> Processing Dependency: fprintd = 0.1-21.git04fd09cfa.el6 for package: fprintd-pam-0.1-21.git04fd09cfa.el6.x86_64
--> Running transaction check
---> Package fprintd-pam.x86_64 0:0.1-21.git04fd09cfa.el6 will be erased
--> Finished Dependency Resolution

Dependencies Resolved

================================================================================
 Package     Arch   Version
                      Repository                                           Size
================================================================================
Removing:
 freetype    x86_64 2.3.11-14.el6_3.1
                      @anaconda-OracleLinuxServer-201311252058.x86_64/6.5 816 k
 gtk2        x86_64 2.20.1-4.el6
                      @anaconda-OracleLinuxServer-201311252058.x86_64/6.5  13 M
 hicolor-icon-theme
             noarch 0.11-1.1.el6
                      @anaconda-OracleLinuxServer-201311252058.x86_64/6.5  44 k
 libX11      x86_64 1.5.0-4.el6
                      @anaconda-OracleLinuxServer-201311252058.x86_64/6.5 1.2 M
Removing for dependencies:
 cairo       x86_64 1.8.8-3.1.el6
                      @anaconda-OracleLinuxServer-201311252058.x86_64/6.5 779 k
 fontconfig  x86_64 2.8.0-3.el6
                      @anaconda-OracleLinuxServer-201311252058.x86_64/6.5 440 k
 fprintd     x86_64 0.1-21.git04fd09cfa.el6
                      @anaconda-OracleLinuxServer-201311252058.x86_64/6.5 106 k
 fprintd-pam x86_64 0.1-21.git04fd09cfa.el6
                      @anaconda-OracleLinuxServer-201311252058.x86_64/6.5  17 k
 libXcomposite
             x86_64 0.4.3-4.el6
                      @anaconda-OracleLinuxServer-201311252058.x86_64/6.5  31 k
 libXcursor  x86_64 1.1.13-6.20130524git8f677eaea.el6
                      @anaconda-OracleLinuxServer-201311252058.x86_64/6.5  41 k
 libXdamage  x86_64 1.1.3-4.el6
                      @anaconda-OracleLinuxServer-201311252058.x86_64/6.5  24 k
 libXext     x86_64 1.3.1-2.el6
                      @anaconda-OracleLinuxServer-201311252058.x86_64/6.5  80 k
 libXfixes   x86_64 5.0-3.el6
                      @anaconda-OracleLinuxServer-201311252058.x86_64/6.5  40 k
 libXft      x86_64 2.3.1-2.el6
                      @anaconda-OracleLinuxServer-201311252058.x86_64/6.5 116 k
 libXi       x86_64 1.6.1-3.el6
                      @anaconda-OracleLinuxServer-201311252058.x86_64/6.5  63 k
 libXinerama x86_64 1.1.2-2.el6
                      @anaconda-OracleLinuxServer-201311252058.x86_64/6.5  32 k
 libXrandr   x86_64 1.4.0-1.el6
                      @anaconda-OracleLinuxServer-201311252058.x86_64/6.5  79 k
 libXrender  x86_64 0.9.7-2.el6
                      @anaconda-OracleLinuxServer-201311252058.x86_64/6.5  56 k
 libfprint   x86_64 0.1.0-19.pre2.el6
                      @anaconda-OracleLinuxServer-201311252058.x86_64/6.5 261 k
 pango       x86_64 1.28.1-7.0.1.el6_3
                      @anaconda-OracleLinuxServer-201311252058.x86_64/6.5 1.0 M

Transaction Summary
================================================================================
Remove       20 Package(s)

Installed size: 18 M
Downloading Packages:
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
  Erasing    : fprintd-pam-0.1-21.git04fd09cfa.el6.x86_64                  1/20 
  Erasing    : fprintd-0.1-21.git04fd09cfa.el6.x86_64                      2/20 
  Erasing    : libfprint-0.1.0-19.pre2.el6.x86_64                          3/20 
  Erasing    : gtk2-2.20.1-4.el6.x86_64                                    4/20 
  Erasing    : pango-1.28.1-7.0.1.el6_3.x86_64                             5/20 
  Erasing    : libXft-2.3.1-2.el6.x86_64                                   6/20 
  Erasing    : cairo-1.8.8-3.1.el6.x86_64                                  7/20 
  Erasing    : libXcursor-1.1.13-6.20130524git8f677eaea.el6.x86_64         8/20 
  Erasing    : libXrandr-1.4.0-1.el6.x86_64                                9/20 
  Erasing    : libXdamage-1.1.3-4.el6.x86_64                              10/20 
  Erasing    : libXi-1.6.1-3.el6.x86_64                                   11/20 
  Erasing    : libXinerama-1.1.2-2.el6.x86_64                             12/20 
  Erasing    : libXext-1.3.1-2.el6.x86_64                                 13/20 
  Erasing    : libXfixes-5.0-3.el6.x86_64                                 14/20 
  Erasing    : libXrender-0.9.7-2.el6.x86_64                              15/20 
  Erasing    : fontconfig-2.8.0-3.el6.x86_64                              16/20 
  Erasing    : libXcomposite-0.4.3-4.el6.x86_64                           17/20 
  Erasing    : hicolor-icon-theme-0.11-1.1.el6.noarch                     18/20 
  Erasing    : libX11-1.5.0-4.el6.x86_64                                  19/20 
  Erasing    : freetype-2.3.11-14.el6_3.1.x86_64                          20/20 
  Verifying  : libXinerama-1.1.2-2.el6.x86_64                              1/20 
  Verifying  : libXrandr-1.4.0-1.el6.x86_64                                2/20 
  Verifying  : libXfixes-5.0-3.el6.x86_64                                  3/20 
  Verifying  : libXrender-0.9.7-2.el6.x86_64                               4/20 
  Verifying  : pango-1.28.1-7.0.1.el6_3.x86_64                             5/20 
  Verifying  : hicolor-icon-theme-0.11-1.1.el6.noarch                      6/20 
  Verifying  : cairo-1.8.8-3.1.el6.x86_64                                  7/20 
  Verifying  : fprintd-0.1-21.git04fd09cfa.el6.x86_64                      8/20 
  Verifying  : libXext-1.3.1-2.el6.x86_64                                  9/20 
  Verifying  : freetype-2.3.11-14.el6_3.1.x86_64                          10/20 
  Verifying  : libfprint-0.1.0-19.pre2.el6.x86_64                         11/20 
  Verifying  : libXi-1.6.1-3.el6.x86_64                                   12/20 
  Verifying  : libXcursor-1.1.13-6.20130524git8f677eaea.el6.x86_64        13/20 
  Verifying  : fprintd-pam-0.1-21.git04fd09cfa.el6.x86_64                 14/20 
  Verifying  : libX11-1.5.0-4.el6.x86_64                                  15/20 
  Verifying  : libXcomposite-0.4.3-4.el6.x86_64                           16/20 
  Verifying  : fontconfig-2.8.0-3.el6.x86_64                              17/20 
  Verifying  : libXdamage-1.1.3-4.el6.x86_64                              18/20 
  Verifying  : gtk2-2.20.1-4.el6.x86_64                                   19/20 
  Verifying  : libXft-2.3.1-2.el6.x86_64                                  20/20 

Removed:
  freetype.x86_64 0:2.3.11-14.el6_3.1           gtk2.x86_64 0:2.20.1-4.el6      
  hicolor-icon-theme.noarch 0:0.11-1.1.el6      libX11.x86_64 0:1.5.0-4.el6     

Dependency Removed:
  cairo.x86_64 0:1.8.8-3.1.el6                                                  
  fontconfig.x86_64 0:2.8.0-3.el6                                               
  fprintd.x86_64 0:0.1-21.git04fd09cfa.el6                                      
  fprintd-pam.x86_64 0:0.1-21.git04fd09cfa.el6                                  
  libXcomposite.x86_64 0:0.4.3-4.el6                                            
  libXcursor.x86_64 0:1.1.13-6.20130524git8f677eaea.el6                         
  libXdamage.x86_64 0:1.1.3-4.el6                                               
  libXext.x86_64 0:1.3.1-2.el6                                                  
  libXfixes.x86_64 0:5.0-3.el6                                                  
  libXft.x86_64 0:2.3.1-2.el6                                                   
  libXi.x86_64 0:1.6.1-3.el6                                                    
  libXinerama.x86_64 0:1.1.2-2.el6                                              
  libXrandr.x86_64 0:1.4.0-1.el6                                                
  libXrender.x86_64 0:0.9.7-2.el6                                               
  libfprint.x86_64 0:0.1.0-19.pre2.el6                                          
  pango.x86_64 0:1.28.1-7.0.1.el6_3                                             

Complete!
Loaded plugins: security
Cleaning repos: epel public_ol6_UEKR3_latest public_ol6_latest puppetlabs-deps
              : puppetlabs-products
Cleaning up Everything
Waiting for ssh login on 192.168.122.162 with user veewee to sshd on port => 22 to work, timeout=10000 sec
.
Executing command: echo 'veewee'|sudo -S sh './zerodisk.sh'
dd: writing `/EMPTY': No space left on device
6808+0 records in
6807+0 records out
7138480128 bytes (7.1 GB) copied, 84.4773 s, 84.5 MB/s
The box oel65_kvm was built successfully!
You can now login to the box with:
ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -p 22 -l veewee 192.168.122.162

Now your box is ready. You can login (username and password are both veewee) to it over ssh to do some checkups but I trust the build and I will just shut down the VM.

$USER@$HOST ~/veewee $ ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -p 22 -l veewee 192.168.122.162
Warning: Permanently added '192.168.122.162' (RSA) to the list of known hosts.
veewee@192.168.122.162's password: 
Last login: Sat Dec 28 11:05:36 2013 from 192.168.122.1
Welcome to Veewee built Vagrant Base Box.
[veewee@localhost ~]$ sudo /sbin/shutdown -h now

Broadcast message from veewee@localhost.localdomain
	(/dev/pts/0) at 11:07 ...

The system is going down for halt NOW!
[veewee@localhost ~]$ Connection to 192.168.122.162 closed by remote host.
Connection to 192.168.122.162 closed.

Export to Vagrant format

$USER@$HOST ~/veewee $ veewee kvm export oel65_kvm Creating a temporary directory for export Adding additional files Creating Vagrantfile Copying the box volume Packaging the box Cleaning up temporary directory To import it into vagrant type: vagrant box add 'oel65_kvm' '/home/$USER/veewee/oel65_kvm.box' To use it: vagrant init 'oel65_kvm' vagrant up --provider=libvirt vagrant ssh

Installing a compatible vagrant

At the time I was testing this there was no libvirt provider for vagrant 1.4. Therefore I installed an older version (1.3.5) which was already compatible with the provider.

Install vagrant 1.3.5

Download vagrant from the official web site (here) and install the package

sudo dpkg -i vagrant_1.3.5_x86_64.deb

Install vagrant-libvirt

vagrant plugin install vagrant-libvirt

My first try looked like:

$USER@$HOST ~ $ vagrant plugin install vagrant-libvirt
Installing the 'vagrant-libvirt' plugin. This can take a few minutes...
/usr/lib/ruby/1.9.1/rubygems/installer.rb:556:in `rescue in block in build_extensions': ERROR: Failed to build gem native extension. (Gem::Installer::ExtensionBuildError)

        /usr/bin/ruby1.9.1 extconf.rb
/usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- mkmf (LoadError)
	from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
	from extconf.rb:5:in `'


Gem files will remain installed in /home/$USER/.vagrant.d/gems/gems/nokogiri-1.5.10 for inspection.
Results logged to /home/$USER/.vagrant.d/gems/gems/nokogiri-1.5.10/ext/nokogiri/gem_make.out
	from /usr/lib/ruby/1.9.1/rubygems/installer.rb:534:in `block in build_extensions'
	from /usr/lib/ruby/1.9.1/rubygems/installer.rb:509:in `each'
	from /usr/lib/ruby/1.9.1/rubygems/installer.rb:509:in `build_extensions'
	from /usr/lib/ruby/1.9.1/rubygems/installer.rb:180:in `install'
	from /usr/lib/ruby/1.9.1/rubygems/dependency_installer.rb:297:in `block in install'
	from /usr/lib/ruby/1.9.1/rubygems/dependency_installer.rb:270:in `each'
	from /usr/lib/ruby/1.9.1/rubygems/dependency_installer.rb:270:in `each_with_index'
	from /usr/lib/ruby/1.9.1/rubygems/dependency_installer.rb:270:in `install'
	from /usr/share/vagrant/plugins/commands/plugin/action/install_gem.rb:38:in `block in call'
	from /usr/share/vagrant/plugins/commands/plugin/gem_helper.rb:42:in `block in with_environment'
	from /usr/lib/ruby/1.9.1/rubygems/user_interaction.rb:40:in `use_ui'
	from /usr/share/vagrant/plugins/commands/plugin/gem_helper.rb:41:in `with_environment'
	from /usr/share/vagrant/plugins/commands/plugin/action/install_gem.rb:28:in `call'
	from /usr/lib/ruby/vendor_ruby/vagrant/action/warden.rb:34:in `call'
	from /usr/share/vagrant/plugins/commands/plugin/action/bundler_check.rb:20:in `call'
	from /usr/lib/ruby/vendor_ruby/vagrant/action/warden.rb:34:in `call'
	from /usr/lib/ruby/vendor_ruby/vagrant/action/builder.rb:116:in `call'
	from /usr/lib/ruby/vendor_ruby/vagrant/action/runner.rb:61:in `block in run'
	from /usr/lib/ruby/vendor_ruby/vagrant/util/busy.rb:19:in `busy'
	from /usr/lib/ruby/vendor_ruby/vagrant/action/runner.rb:61:in `run'
	from /usr/share/vagrant/plugins/commands/plugin/command/base.rb:17:in `action'
	from /usr/share/vagrant/plugins/commands/plugin/command/install.rb:44:in `execute'
	from /usr/share/vagrant/plugins/commands/plugin/command/root.rb:47:in `execute'
	from /usr/lib/ruby/vendor_ruby/vagrant/cli.rb:46:in `execute'
	from /usr/lib/ruby/vendor_ruby/vagrant/environment.rb:467:in `cli'
	from /usr/bin/vagrant:84:in `'

Apparently ruby-devel is needed and as we don't run vagrant in rvm we can install it using the OS package manager.

sudo apt-get install ruby-dev

Retry the plugin installation:

$USER@$HOST ~ $ vagrant plugin install vagrant-libvirt
Installing the 'vagrant-libvirt' plugin. This can take a few minutes...
Installed the plugin 'vagrant-libvirt (0.0.13)'!

Testing the box using vagrant

We create a directory for the vagrant file and there we init a vagrant box based on box 'oel65_kvm'.

cd
mkdir oel65_kvm_vagrantbox
cd oel65_kvm_vagrantbox
vagrant init 'oel65_kvm'
vagrant up --provider=libvirt

At this time something goes wrong, vagrant seems to initialize just fine until:

$USER@$HOST ~/oel65_kvm_vagrantbox $ vagrant up --provider=libvirt
Bringing machine 'default' up with 'libvirt' provider...
[default] Creating image (snapshot of base box volume).
[default] Creating domain with the following settings...
[default]  -- Name:          oel65_kvm_vagrantbox_default
[default]  -- Domain type:   kvm
[default]  -- Cpus:          1
[default]  -- Memory:        512M
[default]  -- Base box:      oel65_kvm
[default]  -- Storage pool:  default
[default]  -- Image:         /var/lib/libvirt/images/oel65_kvm_vagrantbox_default.img
[default]  -- Volume Cache:  default
[default] Creating shared folders metadata...
[default] Starting domain.
[default] Waiting for domain to get an IP address...

But then it seems to be hanging. If you wait long enough the following will be added:

[default] Removing domain...
An error occurred while executing multiple actions in parallel.
Any errors that occurred are shown below.

An unexpected error ocurred when executing the action on the
'default' machine. Please report this as a bug:

The specified wait_for timeout (2 seconds) was exceeded

/home/$USER/.vagrant.d/gems/gems/fog-1.15.0/lib/fog/core/wait_for.rb:10:in `wait_for'
/home/$USER/.vagrant.d/gems/gems/fog-1.15.0/lib/fog/core/model.rb:64:in `wait_for'
/home/$USER/.vagrant.d/gems/gems/vagrant-libvirt-0.0.13/lib/vagrant-libvirt/action/wait_till_up.rb:38:in `block (2 levels) in call'
/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/util/retryable.rb:17:in `retryable'
/home/$USER/.vagrant.d/gems/gems/vagrant-libvirt-0.0.13/lib/vagrant-libvirt/action/wait_till_up.rb:33:in `block in call'
/home/$USER/.vagrant.d/gems/gems/vagrant-libvirt-0.0.13/lib/vagrant-libvirt/util/timer.rb:9:in `time'
/home/$USER/.vagrant.d/gems/gems/vagrant-libvirt-0.0.13/lib/vagrant-libvirt/action/wait_till_up.rb:31:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call'
/home/$USER/.vagrant.d/gems/gems/vagrant-libvirt-0.0.13/lib/vagrant-libvirt/action/start_domain.rb:26:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/builtin/set_hostname.rb:16:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call'
/home/$USER/.vagrant.d/gems/gems/vagrant-libvirt-0.0.13/lib/vagrant-libvirt/action/share_folders.rb:20:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call'
/home/$USER/.vagrant.d/gems/gems/vagrant-libvirt-0.0.13/lib/vagrant-libvirt/action/prepare_nfs_settings.rb:12:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/builtin/nfs.rb:30:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call'
/home/$USER/.vagrant.d/gems/gems/vagrant-libvirt-0.0.13/lib/vagrant-libvirt/action/create_network_interfaces.rb:96:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call'
/home/$USER/.vagrant.d/gems/gems/vagrant-libvirt-0.0.13/lib/vagrant-libvirt/action/create_networks.rb:83:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/builtin/provision.rb:54:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call'
/home/$USER/.vagrant.d/gems/gems/vagrant-libvirt-0.0.13/lib/vagrant-libvirt/action/create_domain.rb:62:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call'
/home/$USER/.vagrant.d/gems/gems/vagrant-libvirt-0.0.13/lib/vagrant-libvirt/action/create_domain_volume.rb:51:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call'
/home/$USER/.vagrant.d/gems/gems/vagrant-libvirt-0.0.13/lib/vagrant-libvirt/action/handle_box_image.rb:38:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/builtin/handle_box_url.rb:24:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call'
/home/$USER/.vagrant.d/gems/gems/vagrant-libvirt-0.0.13/lib/vagrant-libvirt/action/handle_storage_pool.rb:42:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call'
/home/$USER/.vagrant.d/gems/gems/vagrant-libvirt-0.0.13/lib/vagrant-libvirt/action/set_name_of_domain.rb:26:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/runner.rb:61:in `block in run'
/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/util/busy.rb:19:in `busy'
/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/runner.rb:61:in `run'
/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/builtin/call.rb:51:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call'
/home/$USER/.vagrant.d/gems/gems/vagrant-libvirt-0.0.13/lib/vagrant-libvirt/action/connect_libvirt.rb:88:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/builder.rb:116:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/runner.rb:61:in `block in run'
/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/util/busy.rb:19:in `busy'
/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/runner.rb:61:in `run'
/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/machine.rb:147:in `action'
/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/batch_action.rb:63:in `block (2 levels) in run'

So it seems that the VM doesn't get a valid IP. Or at least Vagrant doesn't receive it. Since the VM is a kvm we can have a look to it using the vnc protocol. For this we will use virsh.

We need the domain to be running so if it was stopped already execute vagrant up again:

vagrant up --provider=libvirt

Open a new shell and using virsh look if a kvm is available:

$USER@$HOST ~ $ virsh list
 Id    Name                           State
----------------------------------------------------
 4     oel65_kvm_vagrantbox_default   running

A new kvm is available and it has the name we expected. It has Id 4 and is in state running. Now we need to have the vnc details to connect to it:

$USER@$HOST ~ $ virsh domdisplay 4
vnc://127.0.0.1:0

Here 4 is the Id of the domain we want to connect to. When you now launch vncviewer on this adres you will be connected to the VM:

$USER@$HOST ~ $ vncviewer 127.0.0.1:0

VNC Viewer Free Edition 4.1.1 for X - built Jan 14 2013 22:25:00
Copyright (C) 2002-2005 RealVNC Ltd.
See http://www.realvnc.com for information on VNC.

Sat Dec 28 13:17:46 2013
 CConn:       connected to host 127.0.0.1 port 5900
 CConnection: Server supports RFB protocol version 3.8
 CConnection: Using RFB protocol version 3.8
 TXImage:     Using default colormap and visual, TrueColor, depth 24.
 CConn:       Using pixel format depth 6 (8bpp) rgb222
 CConn:       Using ZRLE encoding

A console windows will show and you can login (veewee/veewee). Once logged in you can look at /etc/udev/rules.d/70-persistent-net.rules. It will look like:

So udev finds an e1000 interface which is bound to eth0 but the interface is not available. So it will never come up. There is as well a interface which gets number eth1. But for eth1 there is no valid configuration present (/etc/sysconfig/network-scripts/ifcfg-eth1).

Change the file so only the entry for virtio-pci is still present. For that entry change NAME eth0 to eth1

# PCI device 0x1af4:0x1000 (virtio-pci)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="52:54:00:9b:86:96", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

The mac address here should correspond to the mac address mentioned in the kvm config when you execute:

virsh dumpxml 4

If you perform these steps the vagrant up command will continue and the total output will look like:

Bringing machine 'default' up with 'libvirt' provider...
[default] Creating image (snapshot of base box volume).
[default] Creating domain with the following settings...
[default]  -- Name:          oel65_kvm_vagrantbox_default
[default]  -- Domain type:   kvm
[default]  -- Cpus:          1
[default]  -- Memory:        512M
[default]  -- Base box:      oel65_kvm
[default]  -- Storage pool:  default
[default]  -- Image:         /var/lib/libvirt/images/oel65_kvm_vagrantbox_default.img
[default]  -- Volume Cache:  default
[default] Creating shared folders metadata...
[default] Starting domain.
[default] Waiting for domain to get an IP address...
[default] Waiting for SSH to become available...
[default] Rsyncing folder: /home/$USER/oel65_kvm_vagrantbox/ => /vagrant
[default] Configuring and enabling network interfaces...

Now you should be able to easily connect to the box using:

vagrant ssh

Troubleshooting & Solving Linux disk space problems

2013-08-24T09:56:00.001-07:00

In this blogpost I want to explain how you can troubleshoot diskspace problems.

Find out which files are using all the disk space.

Graphical desktop

When you have a graphical desktop at hand you should really consider installing Baobab (also known as disk usage analyzer for Ubuntu users). This application is rather straightforward.

You can click on 'Scan home' to verify the disk usage in your home directory. You can also click the button with the Harddisk symbol to start the analysis at your root directory. The graph on the right shows the usage per folder, this is handy to quickly identify greedy disk space consumers.

Command line

When you don't have a graphical desktop at hand, you must help yourself with the df and du commands.

df

The df tool will show you a table that reports the file system disk space usage. It takes a -h flag to write the output in human readable format. A table (constructed by df -h) looks like the following:

Filesystem	Size	Used	Avail	Use%	Mounted
/dev/sda5	28G	12G	16G	43%	/
udev	3.9G	4.0K	3.9G	1%	/dev
tmpfs	1.6G	1.1M	1.6G	1%	/run
none	5.0M	0	5.0M	0%	/run/lock
none	3.9G	520K	3.9G	1%	/run/shm
/dev/sda7	193G	135G	48G	74%	/home
/dev/sda8	121G	120G	1G	99%	/tmp

As you can see it is a handy tool to quickly see the state of your filesystems. A good first indication to see if problems are at hand.

The du tool will estimate the disk space usage. It takes 2 very handy flags which I cannot live without anymore.

-h -> Human readable
--max-depth=N -> Make a summary of directories up till the Nth level

The human readable flag will convert the numerical output from bytes (B) to more readable units like KB, MB, GB. This is the same behavior as with the df command.

Let's illustrated the du command with an example::

ow@D ~/Desktop $ du -h --max-depth=1 /tmp
du: cannot read directory `/tmp/vmware-root': Permission denied
4.0K /tmp/vmware-root
8.0K /tmp/pulse-O0P9w3N0W4t6
120G /tmp/img
8.0K /tmp/mintUpdate
du: cannot read directory `/tmp/cvcd': Permission denied
4.0K /tmp/cvcd
4.0K /tmp/ssh-fyPBrSQD2054
4.0K /tmp/orbit-peter
8.0K /tmp/sni-qt_skype_2251-QXMSXq
4.0K /tmp/.ICE-unix
4.0K /tmp/VMwareDnD
8.0K /tmp/matecorba-peter
4.0K /tmp/.X11-unix
4.0K /tmp/.com.google.Chrome.XybSSu
4.0K /tmp/hsperfdata_peter
4.0K /tmp/jna
4.0K /tmp/keyring-GJe9xq
du: cannot read directory `/tmp/pulse-PKdhtXMmr18n': Permission denied
4.0K /tmp/pulse-PKdhtXMmr18n
164K /tmp

This example shows some typical output lines.

Each line represents a directory and the first column shows the size of the content of the directory.

The last line is a summary line and shows the total size of the content of /tmp (or at least an estimate of it taking into account the files/directories that the user can read).

The lines ending with permission denied illustrated that the du tool couldn't descend in these directories. This is because the user that launched the du command didn't have the rights to descend into that directory.

This usage can be used to track down the big disk space consumers. I prefer to start examining the disk usage with max-depth=1 from the root directory and go down the directories to find the files that consume too much disk space. E.g. Using df I notice that my filesystem mounted at /tmp is reaching it's limit (it has only 121GB of disk space and it consumes more then 120GB). Therefore I launch the du command from above and I get the output from the example above. Then I know that the disk space is used inside /tmp/img so I could launch du --max-depth=1 -h /tmp/img to drill down further. These steps can be repeated until you find the consuming files.

Mismatch between du & df.

There can be a mismatch between the outputs of du and df. This is because df really shows the diskspace that is free and du calculates the disk usage based on the file attributes. It can however be that a file you have deleted isn't really gone yet and thus takes up space. Eventhough it isn't completely gone, it doesn't show up in the directory listing and thus du won't take it into account.

An example of a situation where such a mismatch might occur is when you have an application that logs to a file. When you delete the file it can be that the application still had a handle to the file. The file won't show up in the directory listing anymore but the filespace is not freed up until the file handle is released. If this was a log file from an application that has high availability restrictions, this can be problematic since you cannot shut it down whenever you want. It is possible to force Linux to give away the space but it involves actions with /proc. This is something I might post about on a later time.

Use Oracle Database Gateway for ODBC to query MSSQL Server from an Oracle Database.

2013-02-08T12:51:00.001-08:00

Introduction

In this blogpost I will explain how you can setup Oracle Database Gateway for ODBC (=DG4ODBC) on a linux host to connect from an Oracle Database to a Microsoft SQL Server. To achieve this we will setup the unixODBC driver manager and use the freetds driver.

Overview of the solution.

The solution

Pre-requisites

Working databases

It is not the purpose of this blogpost to tell you how to install an Oracle or MS SQL Database. We will therefore only explain the setup of the DG4ODBC.

A (virtual) machine on which you can install DG4ODBC.

A (virtual) machine with a linux OS and a 64 bit architecture is required. I used an Oracle Linux 6.3 (64-bit) OS but any Red Hat (derivative) should suffice. The installation of the OS is rather basic. On the hard disk I only created 1 EXT4 partition and 1 swap partion. I chose 1 CPU with 2 cores and 2GiB of RAM.

Installed packages

I just did a server installation (no desktop environment). After the installation I installed the oracle-rdbms-server-11gR2-preinstall package (see https://blogs.oracle.com/linux/entry/oracle_rdbms_server_11gr2_pre for more information). This package is installed because I use this VM as a template to create test machines. It is not a requirement for the setup.

Actually if you want to install the package you can execute the yum statement below. Besides installing the packages the package also sets OS parameter to tune the OS for running a database.

yum install cloog-ppl compat-libcap1 compat-libstdc++-33 cpp gcc gcc-c++ glibc-devel glibc-headers
 kernel-uek-headers ksh libXmu libXxf86dga libXxf86misc libaio-devel libdmx libstdc++-devel mpfr ppl
 xorg-x11-utils xorg-x11-xauth glibc glibc-common

disable selinux

Just to be sure that selinux doesn't spoil the fun. I will disable it:

[root@gwexample ~]# cat /etc/sysconfig/selinux 
# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
#     enforcing - SELinux security policy is enforced.
#     permissive - SELinux prints warnings instead of enforcing.
#     disabled - No SELinux policy is loaded.
SELINUX=disabled
# SELINUXTYPE= can take one of these two values:
#     targeted - Targeted processes are protected,
#     mls - Multi Level Security protection.
SELINUXTYPE=targeted

Step 1: Make it possible to connect to MS SQL server from Linux

Install the unixODBC Driver manager.

As unixODBC is provided in the public-yum repositories of Oracle we can make our life easy and install the software from the repo.

yum install unixODBC unixODBC-devel

Do not forget the devel package, it contains files like sql.h which are necessary to compile freetds with support for unixODBC!

Installation of freetds

Download freetds

Download the latest version of freetds. I downloaded the freetds-stable.tgz. We will copy this to /tmp/freetds-stable.tgz. Execute the following to extract it and move it to /home/oracle.

#As user oracle
cd /tmp
gunzip -c freetds-stable.tgz | tar -xvf -
mv freetds-0.91/ /home/oracle/

Configure and build freetds

Now we need to configure it:

#As user oracle
cd /home/oracle/freetds-0.91
./configure --prefix=/usr/local/freetds --with-tdsver=8.0 --with-unixodbc=/usr

If you get an error about missing sql.h. It is most likely because unixODBC is installed on a different location. Do a search for the file (either `locate sql.h` or if locate is not available `find / -name "sql.h"`). If the location is /aa/bbb/c/include/sql.h the configure argument should be --with-unixodbc=/aa/bbb/c . So for my setup it was /usr/include/sql.h

Next build the source

#as user oracle
make

And finally install it

#as root
make install

Configuring unixODBC driver manager

Setup the content of /etc/odbc.ini

[ODBC Data Sources]
#I do not think this line is really necessary but it does no harm :-)
MSSQLVM=FreeTDS
 
#The name between square brackets should correspond to the DB name of your SQL server.
#From now on it will be referred to as DSN !!
[MSSQLVM]
Driver = /usr/local/freetds/lib/libtdsodbc.so
#Do not use Driver = /usr/lib64/libodbc.so
#Location of the MS SQL Server (ip or hostname)
Server = 172.16.58.130
#Port where MS SQL Server is listening
Port = 1433
TDS_Version = 8.0
TraceFile = /tmp/odbc.trace
DEBUG = 1
Trace = Yes
dump file = /tmp/freetds.log

The following should be checked:

You should check if the file /usr/local/freetds/lib/libtdsodbc.so exists, because without it it won't work!
If you use a hostname to locate the server, make sure it is resolvable. Try to do `ping ` and see if you can reach the server. (If not try `ping ip` , if that doesn't work ICMP might be disabled). As I use a simple setup with VMs and no DNS server I use /etc/hosts file of linux to use the hostname.

Verify if freetds can be used via odbc

isql  -v   
+---------------------------------------+
| Connected!                            |
|                                       |
| sql-statement                         |
| help [tablename]                      |
| quit                                  |
|                                       |
+---------------------------------------+
SQL>

For example isql -v MSSQLVM test Welcome1

Setup Oracle DB gateway for ODBC

Download software

The Oracle DB gateway for ODBC can be downloaded separately if you have got an Oracle Support Account. Instructions are available at https://updates.oracle.com/Orion/Services/download?type=readme&aru=14125322#CHDIHDIB . (you need to get Oracle Gateways)

Install software

Unzip the downloaded zip. And run the installer gateways/runInstaller

In splash screen click next.

We leave the default values for location and name.

No incompatibilities were found -> Next.

Select Oracle Database Gateway for ODBC 11.2.0.3.0 -> Next

Click the Install button to install the software.

Execute the 1 or 2 scripts mentioned in the dialog screen AS ROOT.

select Perform typical configuration and click Next.

An error might popup. Just click OK

The error has been noted. Click retry to try again.

If we do exactly the same will it work now?

Apparently yes :-).

Verify if the software works

#as user oracle
 export ORACLE_HOME=/home/oracle/product/11.2.0/tg_1
./dg4odbc

Oracle Corporation --- WEDNESDAY FEB 06 2013 21:02:11.918
Heterogeneous Agent Release 11.2.0.3.0 - 64bit Production Built with
Oracle Database Gateway for ODBC

Everytime you start dg4odbc make sure ORACLE_HOME is set!

Configure the listener

This must be done on the host ware DG4ODBC is installed. Because this listener will be your entry point to the MS SQL SERVER. Listener config file is situated at $ORACLE_HOME/network/admin/listener.ora

SID_LIST_LISTENER=
   (SID_LIST=
      (SID_DESC =
         (SID_NAME = MSSQLVM)
         (ORACLE_HOME = /home/oracle/product/11.2.0/tg_1)
         (ENVS="LD_LIBRARY_PATH=/usr/lib64:/usr/local/freetds/lib:/home/oracle/product/11.2.0/tg_1/lib")
         (PROGRAM = dg4odbc)
       )
 
   )
LISTENER =
  (DESCRIPTION_LIST =
    (DESCRIPTION =
       (ADDRESS_LIST =
          (ADDRESS = (PROTOCOL = TCP)(HOST = gwexample)(PORT = 1511)) 
       )
    )
  )
ADR_BASE_LISTENER = /home/oracle/product/11.2.0/tg_1

Important notes with listener config:

ENVS is not a typo, it should be ENVS
SID_NAME should correspond to DSN from /etc/odbc.ini
Each occurence of '/home/oracle/product/11.2.0/tg_1' should be replaced by the oracle home of dg4odbc but you cannot use the variable $ORACLE_HOME
HOST should be set to hostname or IP of the machine that hosts the dg4odbc. (if hostname is used it is best to have it in /etc/hosts of this machine)
PORT should be set to any free port
Firewall should be configured to allow connections to the PORT selected above -> do this now because you will forget about it!
ADR_BASE_LISTENER might not be necessary but I set it to the oracle home of dg4odbc and that does work

Configure tnsnames.ora

This file should be available at each machine that has an Oracle Database that wants to connect to the MS SQL server using the DG4ODBC. It is used to resolve the listener!

tnsnames config file is situated at $ORACLE_HOME/network/admin/tnsnames.ora

MSSQLVM =
  (DESCRIPTION=
    (ADDRESS=(PROTOCOL=tcp)(HOST=gwexample)(PORT=1511))
    (CONNECT_DATA=(SID=MSSQLVM))
    (HS=OK)
  )

Important notes with tnsnames.ora config

The name at the start is chosen to be the same as the DSN for convenience
The value for HOST does not have to be the ip/hostname of the DB server but must be the ip/hostname of the machine where dg4odbc is installed (this can be the same as the DB server)
The value after the SID must be the DSN
The line (HS=OK) must be present!

Configure dg4odbc

Configuration of this is done in $ORACLE_HOME/hs/admin/init.ora

# This is a sample agent init file that contains the HS parameters that are
# needed for the Database Gateway for ODBC
#
# HS init parameters
#
HS_FDS_CONNECT_INFO = MSSQLVM
HS_FDS_TRACE_LEVEL = 255
HS_FDS_SHAREABLE_NAME = /usr/lib64/libodbc.so
HS_FDS_SUPPORT_STATISTICS = FALSE
HS_LANGUAGE=american_america.we8iso8859P1

#
# ODBC specific environment variables
#
set ODBCINI=/etc/odbc.ini

#
# Environment variables required for the non-Oracle system
#
#set =

Important notes with dg4odbc config

HS_FDS_CONNECT_INFO must be set equal to the DSN
HS_FDS_TRACE_LEVEL must be set to 0 after setup is working! It should only be set to 255 to do troubleshooting at the beginning.
HS_FDS_SHAREABLE_NAME should point to the ODBC library (i.e. the one of the ODBC driver manager)
HS_LANGUAGE should be set to american_america.we8iso8859P1

Reload the listener

This should be done for each change of listener.ora (on dg4odbc machine) and tnsnames.ora (on DB machine)

#as user oracle
#Make sure if ORACLE_HOME is set correctly and if DB SID
lsnrctl reload

Test if dg4odbc can be reached from the DB server

#as user oracle
#if not set, set oracle environment using . oraenv
[oracle@dbserver ~]$ tnsping MSSQLVM
TNS Ping Utility for Linux: Version 11.2.0.3.0 - Production on 05-FEB-2013 10:09:48
Copyright (c) 1997, 2011, Oracle.  All rights reserved.
Used parameter files:

Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=gwexample)(PORT=1511)) (CONNECT_DATA=(SID=MSSQLVM)) (HS=OK))
OK (0 msec)

Creat DB link

#in the Oracle DB execute:
create database link db_link connect to "test" identified by "Welcome1" using 'MSSQLVM';
SELECT * FROM dbo.table@db_link;

Important notes:

db_link is the name of the database link. It can be used after an @-sign
In the create database link statement BOTH the username and password should be surrounded by double quotes.
After using comes the DSN, surrounded by single quotes.

Troubleshooting

Handy files

/tmp/sql.log
$ORACLE_HOME/hs/log directory contains traces

Error messages + solution

Strange output -> language issue (we only speak americano)

sqlplus output

ORA-28500: connection from ORACLE to a non-Oracle system returned this message:
[

ORA-02063: preceding 2 lines from link_name

Sqldeveloper ouput

For Sqldeveloper is the output a bit clearer:

ORA-28500: connection from ORACLE to a non-Oracle system returned this message:
[ u n i x O D B C ) ( D r i v e r M a n a g e r ] D a t a s o u r c e n a m e ...

Strange output comes due to incorrect language settings. Please verify that HS_LANGUAGE=american_america.we8iso8859P1 is set in init.ora !!

Corrupt link

This time no error message is displayed at all.

ORA-28500: connection from ORACLE to a non-Oracle system returned this message:
ORA-02063: preceding 2 lines from link_name
 (and ORA-28500) are caused by invalid

If the listener is restarted with a new config your link in the database might have become invalid. Drop it and recreate it:

DROP DATABASE LINK db_link;
create database link db_link connect to "test" identified by "Welcome1" using 'MSSQLVM';

Nonexistent table or view

ORA-00942: table or view does not exist
[FreeTDS][SQL Server]Invalid object name 'your.table' . {42S02,NativeErr = 208}[FreeTDS][SQL Server]Statement(s) could not be 
ORA-02063: preceding 2 lines from link_name
00942. 00000 - "table or view does not exist"

This can happen if there are quotes surrounding the table name -> Remove surrounding quotes!

References

Some of the contents is based on http://gotodba.weebly.com/install-and-configure-db-link-to-sql-server-database-in-linux.html.

De freetds website http://freetds.schemamania.org/

https://forums.oracle.com/forums/thread.jspa?messageID=4351081 . Thank you kgronau for the answer on setting HS_LANGUAGE!

Downgrade VMDK from HW version 8 to HW version 7 (Workstation 8 to ESXi 4.1 )

2012-12-28T15:55:00.001-08:00

Introduction

When you create a VM using VMWare workstation, which you want to deploy on a ESXi server at a later moment, you should plan in advance which Version you will use for your Virtual machine (and thus your vmx config file). If you don't, your ESXi-server can complain about a unsupported version. But don't panic just yet, it might be fixable.

Which version to use?

When you still need to create a new VM in workstation you should think before choosing a version. The wizard to create a VM provides you with all the necessary information you need. But to choose the correct version it is easier to have a table with an overview. For this reason I present it to you:

Workstation version	Compatible products	Limitations
Workstation 8.0	ESX 5.0 Fusion 4.0 Workstation 8.0	64GB memory limit 8 processor limit 10 network adapter limit 2 TB disk size limit No HD Audio
Workstation 6.5-7.x	ACE 2.5 - 2.7 ESX 4.x ESX 5.0 Fusion 2.x Fusion 3.x Fusion 4.0 Server 2.x Workstation 6.5 Workstation 7.x Workstation 8.0	32GB memory limit 8 processor limit 10 network adapter limit 2 TB disk size limit
Workstation 6.0	ACE 2.0 ACE 2.5 up to 2.7 ESX 4.x ESX 5.0 Fusion 1.1 Fusion 2.x Fusion 3.x Fusion 4.0 Server 2.x Workstation 6.x Workstation 6.5 Workstation 7.x Workstation 8.0	8 GB memory limit 2 processor limit 10 network adapter limit 950 GB disk size limit No HD Audio No CPU hot plug No device hot plug No memory hot plug No LSI Logic SAS SCSI controller No printer support
Workstation 5.x	ACE 2.0 ACE 2.5 up to 2.7 ESX 4.x ESX 5.0 Fusion 1.1 Fusion 2.x Fusion 3.x Fusion 4.0 Server 2.x Workstation 5.x Workstation 6.0 Workstation 6.5 Workstation 7.x Workstation 8.0	3.5 GB memory limit 2 processor limit 4 network adapter limit 950 GB disk size limit No HD Audio No USB 2.0 No multiple monitor display No battery status No CPU hot plug No device hot plug No memory hot plug No LSI Logic SAS SCSI controller No VMCI support No printer support
Workstation 4.x	ACE 1.0 ACE 2.0 ACE 2.5 up to 2.7 ESX 4.x ESX 5.0 Fusion 1.1 Fusion 2.x Fusion 3.x Fusion 4.0 GSX Server 3.x Server 1.x Server 2.x Workstation 4.x Workstation 5.x Workstation 6.0 Workstation 6.5 Workstation 7.x Workstation 8.0	3.5 GB memory limit 1 processor limit 4 network adapter limit 128 GB IDE disk size limit 256 GB SCSI disk size limit No HD Audio No USB 2.0 No multiple monitor display No battery status No 64-bit guests No 3D graphics acceleration No CPU hot plug No device hot plug No memory hot plug No LSI Logic SAS SCSI controller No VMCI support No printer support No clone support

So prior to selecting a version you should determine which features you need (think long-term for this!). Next you need to find a version for which your product (e.g. ESXi server) is in the compatibility list. If it has limitations that conflict with your features, you will need to upgrade.

How to downgrade a version?

Suppose you have a version 8 how do you downgrade to a version 7. I didn't find an official way but as long as you don't have features that are not supported by the version you wish to go to. Then you can just change the version numbers in the vmx file. For example if you want to go from version "8" to version "7" you can open it in your favorite editor and search for "8" and replace it with "7". (For your search replace, make sure you use the double quotes!)

Does it work?

I cannot give any promises if it works for you but I tried it on a VM with an Application server and an Oracle DB and it worked! After you change the file you can just create an OVF of it and deploy it on an ESXi 4.1 server. Which is not possible if you would create it from the original VM.

How to set GPIO on Raspberry PI in assembly

2012-09-23T11:15:00.001-07:00

How to set GPIO on Raspberry PI in assembly.

While reading the nice free courses 'Baking Pi: Operating Systems Development by Alex Chadwick' that explain how to write your own OS for your raspberry Pi, I couldn't figure out how the setup of the GPIO pins was done. I was able to copy the code from the lesson and thus to make it work on my raspberry PI but I wanted to understand what I was doing. For the people who also want a better understanding of how you can use the GPIO pins on the raspberry PI I'll share my findings.

As explained in the OK1 course the GPIO pins our grouped by 10 and there are 3 bits per GPIO pin to select its function. On page 90 of the Soc_pheripherals manual you can see what these 3 bits do:

000 = GPIO Pin 9 is an input 
001 = GPIO Pin 9 is an output 
100 = GPIO Pin 9 takes alternate function 0 
101 = GPIO Pin 9 takes alternate function 1 
110 = GPIO Pin 9 takes alternate function 2 
111 = GPIO Pin 9 takes alternate function 3 
011 = GPIO Pin 9 takes alternate function 4 
010 = GPIO Pin 9 takes alternate function 5

(This is a small extract of the BCM2835 ARM Peripherals manual.  Copyright is property of Broadcom corporation).

In the course we want to set the 16th pin to an output pin so we need to write 001 to the 3 bits corresponding with the 16th pin.

When we make a drawing of the bits (starting from the GPIO address, so our bit 0 is address 0x20200000 in the tutorial). We get the following layout:

The upper row denotes the bit numbers. The second row will number the bytes and in the 3th row we mark the pin that corresponds with the bits. As explained in the course lesson, there corresponds 10 pins with 4 bytes.

The 4th row illustrates what happens if we write value one to 0x20200000.

ldr r0,=0x20200000
mov r1,#1
str r1,[r0]

The 5th row illustrates what happens if we write the shifted register to 0x20200000

ldr r0,=0x20200000
mov r1,#1
lsl r1,#18
str r1,[r0]

The 6th row shows the bits that are written when we write to [r0+4]. Because ARM uses a byte aligned layout the word will be written to bytes 4-7. So the full code part from the course lesson will give the result shown in row 7. The code fragment from the lesson was:

ldr r0,=0x20200000
mov r1,#1
lsl r1,#18
str r1,[r0,#4]

Next we need to now how to set the pin on (LED OFF) and how to set it off (LED ON).

The pin is cleared by writing a 1 to the relevant bit This is done using address 0x 7E20 0028 [GPCLR0] ( see Soc-Peripherals page 90). This word will be used for setting pins 0-31 , the next word will be for pins 32-54.

As denoted in the course we need to set the pin to 0 to set voltage high (led ON). We write a 1<<16 to the address 0x7E200028. But 0x28 = 40 so this gives the following to activate the LED:

mov r1,#1
lsl r1,#16
str r1,[r0,#40]

GPIO Pin Output set Register to set the pin on (LED OFF). This is done using address 0x 7E20 001C [GPSET0] ( see Soc-Peripherals page 90). This word will be used for setting pins 0-31 , the next word will be for pins 32-54.

Now we will set the 16th bit for the address with offset 0x1C = 28. This results in the code

mov r1,#1
lsl r1,#16
str r1,[r0,#28]

So now that you know this, you should head back to http://www.cl.cam.ac.uk/freshers/raspberrypi/tutorials/os and continue the courses. I think they are very good and it is good that the authors are so generous to share them for free with the rest of the world!

Shutdown an internal server using php (apache) in a more efficient matter.

2012-06-15T10:34:00.000-07:00

In a previous post I explained a possible way to shutdown a server with a php page. (here)

Now I will provide a more efficient way using a cgi-script.

Pre-requisites for apache

In order for the code to work you'll have to make sure that the correct modules are loaded. We need the following to modules:

 LoadModule cgi_module /usr/lib/apache2/modules/mod_cgi.so
 LoadModule alias_module /usr/lib/apache2/modules/mod_alias.so
 LoadModule suexec_module /usr/lib/apache2/modules/mod_suexec.so

When that is done we need to add a directory where we want to place our shutdown-script. e.g. /var/www/bin

 ScriptAlias /bin/ /var/www/bin/

We also need to define a user with whom we want to execute the script. This must not be a system user (i.e. it must be possible to login as the user account and uid must be greater then 500.)

 SuexecUserGroup username groupname

This will be all for the Apache configuration.

The script

First we create the directory and we make sure that the directory is owned by the same user as whom is going to execute the script.

 sudo mkdir /var/www/bin
 sudo chown username.groupname /var/www/bin

Within the script we just call the shutdown command. So create a script /var/www/bin/shutdown.cgi with contents:

 #!/bin/bash
 echo -e "Content-type: text/html\n" 
 # ^ Necessary HTTP header, needs to be finished with an empty line
 sudo /sbin/shutdown -h now

Give the script execute permissions:

 chmod +x /var/www/bin/shutdown.cgi

Sudo without a password

If you were paying attention when reading the previous script you have noticed that we used sudo. The first time you use sudo you will be prompted for a password. But our command is executed in a script and we don't have a shell to enter the password! Luckily it is possible to setup sudo so no password is needed. Launch visudo to edit the configuration of sudo (If you have a favorite command-line editor you can set it temporary by executing 'export EDITOR=' before you start visudo. (You have to use -E argument for sudo to make sure you preserve the environmental variables) e.g.:

 export EDITOR=vi
 sudo -E /usr/sbin/visudo

Now add the following config rule to the configuration file:

 username   ALL=(ALL:ALL) NOPASSWD: /sbin/shutdown

This rule let you execute the /sbin/shutdown command on ALL hosts which are OWNED by ALL (=anyone) and part of group ALL (any group) and this without a password.

Test it

Make sure you restart apache and then test it!

 /etc/init.d/httpd restart
or
 /etc/init.d/apache2 restart

if you get an warning 'Warning: SuexecUserGroup directive requires SUEXEC wrapper.' then install the extra package for suexec 'sudo apt-get install apache2-suexec' and try to restart apache again.

When the server is restarted you an browse to http:///bin/shutdown.cgi and your system will shutdown immediatly. (No need for a cronjob anymore :-P).

Complete configuration file for apache:

Place it in a .conf file in the folder /etc/apache2/conf.d/ or /etc/httpd/conf.d/ (depending on your installation). For example shutdown.conf:

 
 LoadModule cgi_module /usr/lib/apache2/modules/mod_cgi.so
 
 
 LoadModule alias_module /usr/lib/apache2/modules/mod_alias.so
 

 
 LoadModule suexec_module /usr/lib/apache2/modules/mod_suexec.so
 
 ScriptAlias /bin/ /var/www/bin/
 SuexecUserGroup username groupname

References

Shutdown an internal server with a php page.

2012-04-08T13:43:00.002-07:00

A more efficient way is posted on my more recent post .

For some reason, don't ask me why, it was very useful to me to shutdown a server using a http-request. This way I didn't have to go to the server to shut him down which is handy if it is locked away. Only for boot up I have to access the machine.

Pre-requisite is off course that a webserver is running on the machine, as there are plenty of tutorials to setup an Apache server I am not going to address that here.

Concept of the solution

In my solution I will be running a simple script every minute to check if a file exists. I the file exists, the script will remove the file and will shutdown the server, if not the script will do nothing. The reason I chose this solution is because it doesn't require much work :-).

The script

The content of the script is:


#!/bin/bash
if [ -f /tmp/shutdown ]
then
 echo "HttpServerShutdown script called" >> /var/log/syslog
 /bin/rm /tmp/shutdown
 /sbin/shutdown -h now
fi

This script is saved as /var/remoteShutdown.sh. It is important to use the full path to the commands. If you use just the command it is probably not part of the path and it will not execute properly.

Trigger the script every minute.

We want to execute the script every minute. Luckily Linux has something like cronjobs. Because we use the shutdown command which should be executed with appropriate privileges, we will set cronjobs with sudo. To do this execute:

 sudo crontab -e

If you have never added a cronjob, you can chose an editor to use. As I am a vi fan I use vi but if you don't know via chose another one :-). Nano is rather straightforward. Using the text editor append a line with the following content:

 * * * * * /var/remoteShutdown.sh

Make sure you save the crontab file.

PHP-page

As I have a default installation of Apache, my PHP pages are kept in /var/www. Create a file called shutdown.php with the following contents:


<?
echo "shutdown";
$file=fopen("/tmp/shutdown",'w');
fwrite($file,"pretty please");
fclose($file);
?>

That's it. Now you can browse to http://<serverIP>/shutdown.php and your server will shutdown.

Drupal development, a more pleasant way.

2011-11-19T05:03:00.000-08:00

Why this post

In my spare time I am making a website for a youth movement using Drupal. Drupal is a very nice CMS that is quite powerful. You can use a lot of code (modules) that are provided by the Drupal community but if it goes wrong it might be hard to find out why. In the beginning I was just making my changes in the Drupal files and when I wanted to test them I uploaded the files to my hosting provider. It seems that it is hard to find a worse way of Drupal development :-). This week I noticed one of the major disadvantages of my approach. After uploading some code my site reported a 500 error message (server error). Since I don't have access to the server itself I couldn't check if it was indeed the server that was erroneous or that it was something I have done. The next day I still got the same error so it was likely that my code was at fault. Finding the fault was quite hard because the only hint I got was (500 server error). Then I realised that it was my own fault. If you want to do some development you should always invest some time in setting up a proper development environment. I knew this when I started the website project but I was too lazy to do it. Now I found out that is was plain stupid since it is very easy to setup a nice Drupal development!

How to quickly setup a good Drupal development environment.

Thanks to some Drupal enthousiasts setting up a Drupal development is easier than ever. There is a Drupal Quickstart project that provides a virtual machine that contains an Ubuntu OS that is configured for some serious Drupal development. You can find the project at http://drupal.org/project/quickstart. Just follow the steps explained on that website to set up the environment.

The Ubuntu OS contains a Drupal 6 and a Drupal 7 example and also has some nice scripts to setup new Drupal installations. Unfortunately I already had started development and I didn't want to lose my previous work.

Importing an existing Drupal project in you development environment

I had my Drupal files on a USB stick so I could easily import them into the Virtual Machine. I also had a backup of the Drupal tables from my database that I made using phpmyadmin (It is wise to use a prefix like 'Drupal_' or a separate database when performing a Drupal installation).

Setting up the database

In the Virtual Machine (Quickstart) you launch firefox. In the toolbar there will be a link to PHPMyAdmin. You browse to PHPMyAdmin and login using the root as username and quickstart as password. Without selecting a database you click on SQL on the left pane.

This will give you a window where you can enter MySQL statements. Make a user that has the same name as you used when making your Drupal installation and give him the same password.

CREATE USER 'YOUR_USERNAME'@'localhost' IDENTIFIED BY 'YOUR_PASSWORD_IN_PLAIN_TEXT';

After typing this statement you click 'Go'. Next you'll have to make the table that you used when making your Drupal installation.

CREATE TABLE TABLE_NAME_FROM_YOUR_DRUPAL_INSTALL;

Now you'll have to make sure that your user has the appropriate rights on your table. Because this is a development environment it won't hurt to grant him all rights.

GRANT ALL PRIVILEGES ON TABLE_NAME_FROM_YOUR_DRUPAL_INSTALL.* TO 'YOUR_USERNAME'@'localhost';

Logout of PHPMyAdmin and log back in using YOUR_USERNAME and YOUR_PASSWORD_IN_PLAIN_TEXT. Now select the table of your Drupal Install which is still empty. Now you can click on import tab on the right pane. There you can select your SQL backup file (click browse) and confirm it (click go). Now your Drupal tables will be imported. I had my files gzipped and I got a strange error. Trying the unzipped SQL-file worked for me. Congratulations your database is setup!

Placing the Drupal files.

For consistency I thought it would be best to place the Drupal files in the websites folder which is located in the home folder of the Quickstart user. Just make a new dir that identifies your drupal installation (e.g. drupal_42) and place the files of your Drupal project there. See to it that you also copy the .htacces file. Files starting with a dot are hidden in Linux. You can make them visible in nautilus by pressing ctrl+h or by using the menu: View-> Show hidden files.

Making it work

All the contents of your Drupal project are in place but how can you view your website? For this you need to do some additional setup. Notice that in the websites folder (/home/quickstart/websites) there is a config folder. This folder contains (links to) all the necessary configuration files that you'll need. Will split the changes per file.

hosts

Here you can set aliases that point to IP-addresses. As your localhost (your Virtual machine) will generate your site you will need to setup the name (URL) of your website to point to your localhost. This can be done by adding a rule at the end of the file. You can see that there are already URLs pointing to the localhost, these are the example Drupal installations that are pre-installed. Just add a rule with a URL you like.

Then save your file and close it.

Apache

Next you'll have to configure Apache. Apache is the server which will generate the HTML using the PHP files. Your site needs to be registered to Apache so it knows that is should process the necessary files. The configuration files of Apache can be found by following apache-sites-available link in /home/quickstart/websites/config. There you see the config files of the other pre-installed Drupal sites. As I wanted to get my installation working without too much trouble, I made a copy of example.dev named drupal42.dev. Then I changed the content to reflect my project. It is rather straightforward. Just change example.dev into drupal42.dev. And where you see a path pointing to the example.dev folder, you change it to the folder where you copied your Drupal project files. Save your changes and all the configuration is done. It might be necessary to restart Apache to notice the configurationfiles.

sudo /etc/init.d/apache2 restart

The result

To view the result open up firefox and browse to your URL (e.g. http://drupal42.dev/). And you should see your website. If you get a permission denied error you should check the permissions of your files from your drupal installation. The owner should be quickstart and the group should be www-data. (browse to root folder using a command shell and execute sudo chown -R quickstart:www-data . , including the dot!). If it still doesn't work make sure group permissions are set correctly (they should be able to read and execute files). sudo chmod -R 755 *

It works, now what?

Now you have got a server which you can configure yourself. The default is actually good already for development. Warnings and errors are shown in the browser so you can get more debug information than on a production server. There are also IDEs installed on the Virtual machine. Eclipse and Netbeans. I have setup Netbeans but you can use Eclipse also.

Netbeans

Launch netbeans from your desktop or from the upper gnome panel. Click File->New Project... Then in the new window select PHP project with existing sources. Click Next. Then you can select your source folder using the browse button and give the project an appropriate name. You can also select a PHP version that you want to use. Click next again and look at the run configuration. Make sure that the project URL is correct. This is the URL where you browse to see your website in your development environment. The default is http://localhost/drupal42.dev/ so you probably have to change this to http://drupal42.dev/. When you click finish your project will be imported into the IDE.

Why should you use an IDE for development? There are multiple reasons actually. You have good syntax highlighting. You have tools for Version control that are integrated into the IDE. You can do real debugging (Setting breakpoints, stepping through code, examining content of variables,...). If you don't know Netbeans or Eclipse it might be interesting to learn how to work with one of them. They are both pretty nice. There are sometimes plugins which configure the IDE for you for Drupal development. I think Eclipse can generate code for Drupal hooks. (Yes it does http://drupal.org/node/75242#templates and for netbeans http://drupal.org/project/nb_templates). Don't you love open source community software :-).

And what was the error?

I had a typo in the code for my own custom module. After my function there was one } too much. Again, plain stupid.

Android Recover Mail password

2011-11-04T09:20:00.000-07:00

It's probably necessary that your device is rooted in order to be able to do this. I'm not sure though. This blog post is for people willing to recover there OWN password, do not misuse this information.

Prerequisites

Before you can start, it is necessary that the tools of the Android SDK are installed and ready to be used. How to install these tools is explained here

The story

We want to recover the password of our e-mail account. Because android needs this password to download your e-mail, it will store the password on your phone. The data of applications is stored in /data/data. At that location there are directories for the different applications. The directory for mail is com.android.email. There we have to find the password. The password is located in 1 of the databases that is in the com.android.email folder. The databases are SQLite databases, so the easiest way to recover the password is by browsing the databases using an appropriate tool.

The recovery steps

First you need to get the contents of com.android.email. (You don't need it all but this way you can inspect the other contents also.) This is done by executing the following command in the shell of your ubuntu installation:

adb pull /data/data/com.android.email ~/email_of_phone

This will place the contents in a folder named "email_of_phone" in your home directory.

Next you'll need to install a tool to explore the databasefiles. I have used SQLitebrowser which is in the repositories. Just install it by using the command:

sudo apt-get install sqlitebrowser

When this is done you'll have to launch the SQLitebrowser. Just use shell:

sqlitebrowser

The people who are no shell-enthousiasts can be happy, from now on everything is by GUI. The GUI is very straightforward. Click the Folder icon (with the arrow). This opens up a dialog window where you can select your database. The database will be 1 of the databases in ~/email_of_phone/databases. For me it was the EmailProvider.db so you should try that one first :-).

When the databases is opened you can see that there is a table called HostAuth. This might be interesting to find out our authentication credentials. So we click the + sign to the left of it.

Then we can see that it has indeed a password field!

But we are not interested in the table layout. We want the content of the table. So click the "Browse Data" tab.

The last step is changing the table that is shown to HostAuth.

Finally you can read the content of the table. In the Password field, you can read the password in plaintext.

Quiet down a Noisy Fan (Sony VAIO VPCEB1S1E model PCG-71211M) (OS independent)

2011-03-12T03:40:00.000-08:00

This post will tell you how to solve a noisy fan problem. My notebook ran hot very quickly resulting in a fan that is going crazy. (This post won't be about ubuntu nor android but the solution worked so well that I thought I should share it anyway.)

First it is interesting to think about any possible reasons your PC is running hot. If you are doing very intensive tasks it might be normal that it's hot. But if your notebook or PC runs hot when doing normal stuff (e.g. searching in a large PDF document) then there might be a problem with the heath conduction within your notebook.

My Notebook worked fine before so I knew it wasn't a design flaw of my notebook itself. One very likely possibility is that there is dust in your computer which prevents a good internal air (and thus heat) flow. Since my warranty expired 2 weeks before being fed up with the noise there was only 1 budget friendly solution, so I searched for my screwdrivers.

Before opening up a notebook it can be wise to search for a service/repair manual of your notebook which describes how to open up your notebook. As I couldn't find any on my model (PCG-71211M) I decided to work without a map. Be warned that notebooks can be quite a pain to put together again (ordinary PC's are like 4 piece jigsaw puzzles compared to notebooks!). Luckily my Vaio didn't need a lot of disassembling for my goal.

Now I will describe how I opened up my notebook with some accompanying pictures (you can click on them to enlarge them). If you try this yourself, know that it is on your own responsibility! Lets start with a picture:

This is the backside of your notebook, you might already familiar with it. You can notice that there are quite a lot of screws. Since they may vary in size it is important to work neatly. HINT: It can be useful to work on a large table and put the screw upside down on the table in the same layout you took them out of your notebook. (This sounds lame but if you've got more than 20 screws you won't remember which one went where.)

Ok, first remove the battery. Slide the lock and pull the release button away and you can roll out the battery. Your notebook should look now like the picture below. As you can see there already 19 screws visible (don't worry we only need to remove 21 screws in total).

When you remove screws 16 and 17 you can remove the cover protecting your hard disk. You can raise the cover at the side that is nearest to you (nearest to the bottom of the picture). Then you can see screws 21 and 22. Apparently I forgot number 20 when photo shopping the pictures and I am to lazy to redo them :-).

Now that all the screws are located remove them all! And I mean all of them. Otherwise you can force the body at the places where it is still screwed together! When all screws are gone you can first remove your Hard Disk. When screws 16,17,21 & 22 are removed you can slide your Hard Drive as depicted below. You want to treat this hard disk with care since it contains all your precious data.

After removing your Hard disk you can remove your CD/DVD drive. When screws 6 and 9 are removed, you can just slide it out.

You can also remove the cover that is fixed by screw number 10. Behind this is your RAM memory. I removed the RAM memory also but I don't think it is necessary. (The cover must be removed however!)

Now you should be ready to open up the body! Maybe to be sure you can do a last check to see if all screws are removed. Then you can start lifting the side that is nearest to you and open up the body like it was a treasure chest (full of dust). Be careful however, there are little plastic hooks that hold the body together. So you might have to apply some light pressure at some points using a screw driver. Be gently however since you don't want to break of any of the hooks. It is not hard but the first time you might have to get used to it. When your notebook is opened up it should look like this:

At this moment you might be a bit disappointed as you might have thought that there would be much more dust. But don't worry! The picture above was taken before the cleanup of my notebook so it didn't look too bad either! But the cleaning helped a lot! Before you start cleaning: REMOVE THE POWER SUPPLY OF THE FAN!. This is circled in blue on the picture above.

Now the cleaning can begin. I cleaned it using a vacuum cleaner which can blow air. If you don't have a vacuum cleaner which can blow you might want to search for cans containing pressurized air (so called air dusters). I've heard that sucking air isn't a good idea (don't know if this is true but I'd rather play safe). The metal on the upper part (see picture) I have cleaned using a cloth (that was a bit wet). Then I dried the cloth and cleaned it again. Make sure everything is dry when you put your notebook back together! The other parts I have blown out using the vacuum cleaner. When cleaning the ventilator you should hold it still using one of your hands. Be sure to send a strong air flow through the ventilator shaft. (The metal block that goes to the side of your notebook on the right.) Since this is a place were dust can easily get trapped. (Again hold the ventilator).

When the cleaning is done you can put your notebook back together by performing the steps above in reverse order. THE FIRST STEP IS TO RECONNECT YOUR FAN. If you don't reconnect your fan you are blessed with a notebook that will be very silent (but silence can (and will) kill!). The re-closing of the body is the hardest part. First make sure the back sides (sides furthest away from you) fit together and than close the body. Then gently press the body together at the sides. You might hear little clicking sounds.

Next insert the hard drive and CD/DVD drive again. Just gently slide them back in. Remember that screws 16 and 17 are there to keep the cap fixed to the body so they should be screwed after placing the cover over the hard disk.

If everything is back at its place then you should boot up your notebook and enjoy the silence.

Ubuntu and EasySMS (for android)

2011-02-24T14:11:00.000-08:00

Introduction

When you are on your computer almost all the time it might be interesting to send sms messages using your computer. There is an application for Android that lets you do this. It is called EasySMS and is available in the Android market.

But it only gets useful if it's configured well. So I want to share my configuration. Important to note is that my configuration is for USB connections. As I prefer a USB connection to a WiFi connection.

Configuration on the phone

After installing the application from the market you can launch the application (you can choose free or paid version. The paid version obviously has some advantages and I bought it).
When the application is launched you see a screen were you can set configuration options. Check the box before "Auto" underneath "Control of services Wifi/USB". Secondly you should set a port for Wifi/USB (mine is set to 2511 but you can choose any number higher than 1023). I have got the HTC Hero and my phone needs the checkbox before "Alt. send" to be checked. Normally you only have to check this if you notice that your messages don't get send.
You can set other configurations as you wish.

Configuration of Ubuntu

This part will tell you how to make it possible to send SMS messages by just clicking one button. A requirement for your system is that you have the Android SDK somewhere on it. You can find the SDK on http://developer.android.com/sdk/index.html

First make an simple script "startUSBSMS.sh" with the following contents:
#!/bin/sh
$PATH_TO_ANDROID_SDK/tools/adb forward tcp:1977 tcp:2511
google-chrome http://localhost:1977/

Of course you can use another browser by changing google-chrome to firefox or any other browser launching command. $PATH_TO_ANDROID_SDK must be changed to the android SDK folder containing the tools folder. It is important that the bold port numbers match and that the number in italics is the same as the port number that was chosen during the configuration of the phone. Finally you should make the script executable (chmod +x startUSBSMS.sh or using the properties window of the file)

Normally you can add a custom application launcher to one of your gnome panels. When creating this launcher you can select an icon and a command. The command is just the path to your script.

This might work for you but I had to do a little bit of extra work. Since my phone wasn't always connected with the right permissions I had to create some udev rules to make sure my phone was accessible. The udev rules should only be executed when you're phone is connected. One way to do this is to find out the VendorId corresponding with your phone. This can be done by executing lsusb WHEN YOUR PHONE IS CONNECTED VIA USB! it will give output of the different USB devices. Find the line corresponding to your phone. Normally every line has a description. Ee.g. I have a htc (=High Tech Corporation) Hero phone and output is:

Bus 002 Device 003: ID 0bb4:0c99 High Tech Computer Corp.

The number after ID and before the following colon will be the vendorid. Now we have got all the information to make the udev rules. Make a file /etc/udev/rules.d/50-android.rules with the following content:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", RUN+="$PATH_TO_ANDROID_SDK/tools/adb start-server"

Finally execute sudo restart udev to make sure the rules are activated. After reconnecting your phone you should be able to use your SMS button!

EasySMS link

http://www.fireblade.org/EasySMS/

Easiest fix for sound Sony VAIO VPCEB1S1E

2010-05-22T13:35:00.000-07:00

Easiest fix for sound Sony Vaio VPCEB1S1E

In my previous post I allready explained some fixes. But now it's even more easier, just follow these little steps

1)Download the following zip file on your pc

vaio_soundfix.zip

   2)Go to the folder where you downloaded the file and extract it

   3)This will create a folder called "vaio_soundfix"
Because we will need root privileges we will continue in terminal:
   4)Open up a terminal

   5)Change the current directory to the vaio_soundfix you just created*

   6)type in the following command (caution: capital I) and confirm with enter

sudo ./Install.sh

This will output something like:

username@computername:DirectoryWhereYouExtractedFiles/vaio_soundfix$ sudo ./Install.sh
Now in directory /opt/vaio/vaio_soundfix
update-rc.d: warning: /etc/init.d/soundvaio missing LSB information
update-rc.d: see
Adding system startup for /etc/init.d/soundvaio ...
/etc/rc0.d/K20soundvaio -> ../init.d/soundvaio
/etc/rc1.d/K20soundvaio -> ../init.d/soundvaio
/etc/rc6.d/K20soundvaio -> ../init.d/soundvaio
/etc/rc2.d/S20soundvaio -> ../init.d/soundvaio
/etc/rc3.d/S20soundvaio -> ../init.d/soundvaio
/etc/rc4.d/S20soundvaio -> ../init.d/soundvaio
/etc/rc5.d/S20soundvaio -> ../init.d/soundvaio
All done, press enter to quit…

So the warning is normal.

7)Reboot & enjoy the bootsound!

*Some more information on how to go to the right directory. If you have for example downloaded vaio_soundfix.zip to 'Downloads'. You just type the following command in the terminal:

cd ~/Downloads

'~' Must be a 'tilde' for some reason it won't show correctly...
cd is the change directory command and is followed by the directory to which you want to change. ~ is a wildcard that gets replaced by the home directory of the userdirectory. So this command will move your current directory to the Downloads-folder in your own home-folder.

For the people interested: You can also just open the Install.sh script with gedit if you want to see what it does. I've commented it a little bit.

Fixing sound issue on Sony vaio VPCEB1S1E

2010-05-04T13:34:00.000-07:00

edit:The easiest solution (which is also persistent!) is explained in a newer post which can be found here!!!

This blogpost will explain how to make sound work on a Sony Vaio VPCEB1S1E. The solution is based on bug report 445889. Where Arwin Tugade posted a solution. In this post I'll try to provide a more detailed explanation.

There are 2 solutions: an easy one and a hard one. The easy one is however not persistent. So after each reboot you'll have to redo all the steps to enable your sound. The hard one on the other hand is persistent. I will explain both.

Easy (non persistent) solution

For the easy solution a python script has to be downloaded. This script is called HDA Analyzer and provides a GUI which will help us to enable the intern speaker of our notebook. (HDA Analyzers wiki can be found on:http://www.alsa-project.org/main/index.php/HDA_Analyzer)
First you'll have to download the script. This can be don by starting up a terminal and execute the following command:

wget -O run.py http://www.alsa-project.org/hda-analyzer.py

Next will have to run this script with super user privileges. This can be done by executing the next command in the terminal:

sudo python run.py

You will be prompted to enter your password. After entering your password a GUI will start up. In the GUI click on "Node[0x19] PIN" in the list on the left-side. Then in the right part you'll have to change the value of the dropdownlist next to VREF to HIZ. See picture:

Now the sound of your notebook should work!

When you close the application a popup will ask "HDA-Analyzer: Would you like to revert settings for all HDA codecs?". Answer No.

Hard (persistent) solution

Warning: The following instructions are to be used on Lucid only. If the process isn't performed right, it might break your system. And thus you will need to re-install your computer. I hereby clearly state that I won't take any responsibility for broken systems.

Before trying this you might first check out the solution above because if that won't work, this also won't work. For a persistent solution we wil create a custom kernel. This means we need to recompile the kernel. Therefore we first need to be sure the have some packages. This by entering the 2 following commands:

sudo apt-get install fakeroot kernel-wedge build-essential makedumpfile kernel-package

and

sudo apt-get build-dep linux

Then we need to download the kernel source, do this by entering the following commands:

sudo apt-get build-dep --no-install-recommends linux-image-$(uname -r)

apt-get source linux-image-$(uname -r)

Note: The source will be placed in your current working directory. You can use the pwd command to print this directory out. As I myself am new to building kernels I have just put it in my home folder. But there might be a better practice.

Note2:The `uname -r` command makes sure that you download the source of the kernel you are currently using

Go into the directory with the kernel source:
It's name will start with linux and contain the first part of the kernel release number.
For example when the `uname -r` command returns "2.6.32-21-generic". The kernel source will be in a map with a name like `linux-2.6.32`. In that case you want to go into that directory by executing the following command:

cd linux-2.6.32

Now we are going to change the source. Therefore we need to open the file that needs to be changed in a text-editor. You can open it with gedit by executing the following command:

gedit sound/pci/hda/patch_realtek.c

Then find “static struct hda_verb alc269_init_verbs[] = {“. In my file it was around line number 13272 but it may be different because you might have got another version of the file, depending on your current kernel. In this struct definition (thus the code between curly brackets) you must find the line stating:
{0x19, AC_VERB_SET_PIN_WIDGET_CONTROL, PIN_VREF80},

and you will have to change this line into:

{0x19, AC_VERB_SET_PIN_WIDGET_CONTROL, PIN_IN},

Than save and quit the file.

Now that the source is changed we need to recompile the kernel.
This is done by executing the following 2 commands:

fakeroot debian/rules clean

And

AUTOBUILD=1 fakeroot debian/rules binary-debs-FLAVOUR

Where FLAVOUR must be changed to the flavour you wish. If you type `uname -r` in your terminal you will get the release of your kernel and normally this contains the flavour you need. For example:
if `uname -r` results in the following answer:
2.6.32-21-generic

Then your flavour is generic and the second command should have been:

AUTOBUILD=1 fakeroot debian/rules binary-debs-generic

I haven't test this because I had executed

AUTOBUILD=1 fakeroot debian/rules binary-debs

by mistake and this command builds kernels for every possible flavour. You can do this also, but I don't recommend this since building may take a while...

After the building of the kernel you will have 2 deb files. You can install them by executing the command:

sudo dpkg -i name_of_file.deb

I have first installed the header file and then the image, but I don't know if the order is important.

URLs of the webpages that helped me a lot:

The bug report that showed me the solution. (THANK YOU Arwin Tugade)
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/445889

The necessary information on Kernel compiling
https://help.ubuntu.com/community/Kernel/Compile

udev rules needed for your android device

2009-12-21T05:58:00.000-08:00

This blogpost will contain the udev-rules needed for making adb work.

This information is partly copied from here. I've posted it here because that source wasn't available anymore, and it was for htc-devices only.

To add the rules file you must do the following steps:

1. Login as root and create this file: /etc/udev/rules.d/50-android.rules.
   For Gusty/Hardy/Intrepid/Jaunty/Karmic, edit the file to read:
     SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
   For Dapper and earlier, edit the file to read:
     SUBSYSTEM=="usb_device", SYSFS{idVendor}=="0bb4", MODE="0666"
2. Now execute:
   chmod a+rx /etc/udev/rules.d/50-android.rules
3. And make the rule active by restarting udev:
   sudo /etc/init.d/udev restart

It is important to note that this only works for HTC-devices. However you can make it work for any device. You'll just have to change the value of SYSFS{idVendor} into another value (read further).

You can obtain the value of SYSFS{idVendor} by connecting your device via usb and launching the command lsusb:
an example output:

Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 0bb4:0c02 High Tech Computer Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

As you can see this is for a HTC (High Tech Computer Corp.) Device. And you can read the id of the vendor after ID and before the colon. So if you have another device, just use the id printed out. This by putting it in the quotes, instead of 0bb4 in /etc/udev/rules.d/50-android.rules.