Howto | Connect KAddressBook to ActiveDirectory
21 Mar 2009In Kmail, under Contacts, in the lower half of the screen press button to [Add]. Select LDAP.
In Kmail, under Contacts, in the lower half of the screen press button to [Add]. Select LDAP.
KNetworkManager does not like inheriting a pre-existing /etc/network/interfaces file.
Comment out all but the following from your /etc/network/interfaces:
auto lo
iface lo inet loopback
Iceweasel and Firefox do not use the KDE Print system, but instead print directly to CUPs. This works fine, but can be confusing, as it looks different and doesn’t offer all the same functions, like PDF etc.
Trying to resolve this issue, I came across this posting:
Firstly comment out the CDROM installation from /etc/apt/sources.list. This seems to be done automatically from Lenny.
Next change any references to “stable” are replaced with the name of the current stable release, currently “Lenny”. If we don’t do this, then when the next release “Squeeze” goes “stable”, suddenly your system will be upgraded next time you do an apt-get upgrade.
In my opinion, protecting your Windows PC is much harder than it should be, and for that reason I recommend Linux.
If you are determined to run Windows, then read on!
I have been repeatedly astonished by the number of people who have no idea that any alternative to Microsoft Windows actually exists. Here is a list of just a few with Links to their respective Wikipedia pages:
Download Open Source Edition (OSE) from VirtualBox:
The VirtualBox Open Source Edition is now in the Debian and Ubuntu repositories, so these instructions are largely redundant.
The full product is not open source, only free for personal and evaluation use. They do offer an open source version, but this requires compiling from source and does not include headless VRDP or automated set-up, nor USB support.
Most instructions on the web are suggesting setting up bridging and setting the interface to work in promiscuous mode; which I understand has security implications. I came across this website which seemed to promise a simple alternative, by which instead of bridging the networks we just advertise the presence of the guest interface. It seems to work well as far as I can tell.
# egrep '^flags.*(vmx|svm)' /proc/cpuinfo
If nothing is displayed, then you do not have a CPU that supports KVM. If lines are output that include the text “vmx” then you have an Intel CPU that supports KVM, if “svm” then an AMD CPU that supports KVM.