Preemption
The server kernel has kernel preemption turned off (CONFIG_PREEMPT_NONE=y), while the desktop kernel has it enabled (CONFIG_PREEMPT_BKL=y, CONFIG_PREEMPT_VOLUNTARY=y). Preemption works along with scheduling to fine-tune performance, efficiency and responsiveness. In non-preemptive kernels, kernel code runs until completion; the scheduler can't touch it until it's finished. But the Linux kernel allows tasks to be interrupted at nearly any point (but not when it is unsafe, which is a whole huge fascinating topic all by itself), so that tasks of lesser-priority can jump to the head of the line.
This is appropriate for desktop systems because users typically have several things going at once: writing documents, playing music, Web surfing, downloading and so on. Users don't care how responsive background applications are; they care only about the ones they're actively using. So if loading a Web page takes a little longer while the user is writing an e-mail, it's an acceptable trade-off. Overall efficiency and performance are actually reduced but not in a way that annoys the user.
On servers you want to minimize any and all performance hits, so turning off preemption is usually the best practice.
yc c on 30 Jan 10netboot.me is a service that allows you to boot nearly any operating system or utility on any computer with a wired internet connection - without having to know ahead of time what you'll want to boot. Once you can netboot.me, you never need to update your boot disk again! In order for your computer to know where to find the netboot servers, you need to change your DHCP settings to return some extra information. The two relevant pieces of information: next-server, which should be "tftp.netboot.me", and "filename", which should be "netbootme.kpxe". How to set these settings depends on your DHCP server. For dhcpd, simply add the following to the relevant 'subnet' section of your configuration: next-server "tftp.netboot.me" filename "netbootme.kpxe" For dnsmasq, the following line in /etc/dnsmasq.conf will achieve the same effect: dhcp-boot=netbootme.kpxe,tftp.netboot.me netboot.me works through the magic of netbooting. There are a number of ways to boot a computer with netboot.me. The simplest is to download a bootable image and burn it to a CD, USB memory stick, or floppy disk. Boot off it on any networked computer, and it will automatically fetch the latest boot options from netboot.me and let you choose from dozens of installation, recovery, testing, portable desktop and other tools. You can also start netboot.me from any computer running gPXE, or from any netbootable computer with some simple tweaks to your DHCP server.
