How to enable Intel hardware virtualization on an HP xw4600:
* Boot into the hardware BIOS setup
* Got to Security -> System Security
* Enable both types of virtualization (VTx and VTd)
* Save settings, and power-cycle the machine.
I’m running Linux, Fedora 9, and using KVM, so I run the following:
modprobe kvm-intel
Loading that module will fail if hardware virtualization isn’t enabled.
I’m not a Django programmer, but for those who are, this may be useful. YouTube has videos of the inagural DjangoCon conference: http://www.youtube.com/results?search_query=djangocon&search=tag
For over a year, I’ve endured a development machine that would lock up under heavy disk I/O. Yesterday, I apparently complained loudly enough that I was given a new machine to replace it. I didn’t want to reinstall Fedora 9, so I transferred my old hard drive to the new machine, as the primary drive. To get it to boot and function properly, here’s what I did:
* Booted with the Fedora 9 install CD into “rescue mode”
* Ran the following commands once I had a shell:
mount –bind /dev /mnt/sysimage/dev
mount –bind /sys /mnt/sysimage/sys
chroot /mnt/sysimage
mv /boot/initrd-2.6.25…i686.img /boot/initrd-2.6.25…i686.img.orig
mkinitrd /boot/initrd-2.6.25…i686.img 2.6.25…i686
* Then I ran ‘grub’, and typed the following:
root (hd0,0)
setup (hd0)
quit
* Ejected the install CD, and rebooted. Once booted, I noticed that my network cards weren’t set up quite right. My new network card was listed as “eth2″ in system-config-network, and I didn’t actually have cards for the listed “eth0″ and “eth1″ interfaces anymore. I didn’t know what file to change to get my new card listed as “eth0″, so I ran the following command to find out what files I might need to edit:
find /etc -type f -print0 | xargs -0 grep “eth[01]“
That command listed the following files, among others:
* /etc/udev/rules.d/70-persistent-net.rules
* /etc/vmware/locations
I edited /etc/udev/rules.d/70-persistent-net.rules and ripped out the assignments for my old NIC interfaces, and set the new one to be “eth0″, then rebooted and used `system-config-network` to set up my network.
When I ran my VMware guest, VMware Server gave me an error message about not being able to use bridged mode for the selected interface. With my old computer, VMware had used eth1 for bridged networking, and I didn’t have an “eth1″ interface anymore. I edited /etc/vmware/locations and changed “eth1″ to “eth0″, and restarted vmware. This time, bridged mode worked correctly.
Perhaps this is a bit old, but it’s the first time I’ve seen it, and I thought it was interesting enough to share.
http://www.webappsec.org/projects/statistics/
The Pragmatic Bookshelf is releasing a book on using Git for version control.
Steven Walter released a new command-line front-end for git called yap. It’s not only supposed to make it easier to work with git, but also with subversion repositories. It’s available from http://repo.or.cz/w/yap.git
I’ve often wondered why people seem to prefer either MySQL or PostgreSQL. For the most part, I think it comes down to the following:
Here are some resources that could be useful for learning the pros and cons of each database:
Have you ever wondered what forms of communication are the most and the least effective for software engineers? See Scott Ambler’s “Models of Communication” diagram in his essay. Face-to-face is most effective, and paper is the least effective, with email, telephone and video conferencing falling in-between the two ends of the spectrum.
Have you considered the merits and applicability of RESTful web apps? Here are a few notes I’ve made.
There was quite a discussion about RPC, REST, and message queuing — they are not the same thing. Each one is needed in a different scenario. All are used in building distributed systems.
Wikipedia’s explanation of REST is quite informative, especially their examples of RPC versus REST.
The poster “soabloke” says RPC “Promotes tightly coupled systems which are difficult to scale and maintain. Other abstractions have been more successful in building distributed systems. One such abstraction is message queueing where systems communicate with each other by passing messages through a distributed queue. REST is another completely different abstraction based around the concept of a ‘Resource’. Message queuing can be used to simulate RPC-type calls (request/reply) and REST might commonly use a request/reply protocol (HTTP) but they are fundamentally different from RPC as most people conceive it. “
The REST FAQ says, “Most applications that self-identify as using “RPC” do not conform to the REST. In particular, most use a single URL to represent the end-point (dispatch point) instead of using a multitude of URLs representing every interesting data object. Then they hide their data objects behind method calls and parameters, making them unavailable to applications built of the Web. REST-based services give addresses to every useful data object and use the resources themselves as the targets for method calls (typically using HTTP methods)… REST is incompatible with ‘end-point’ RPC. Either you address data objects (REST) or you don’t.”
RPC: Remote Procedure Call assumes that people agree on what kinds of procedures they would like to do. RPC is about algorithms, code, etc. that operate on data, rather than about the data itself. Usually fast. Usually binary encoded. Okay for software designed and consumed by a single vendor.
REST: All data is addressed using URLs, and is encoded using a standard MIME type. Data that is made up of other data would simply have URLs pointing to the other data. Assumes that people won’t agree on what they want to do with data, so they let people get the data, and act on it independently, without agreeing on procedures.
Google has made videos available for it’s two-day I/O conference for developers. They cover things such as Python, the Android platform, Google Apps, etc.