Linked by Thom Holwerda on Thu 21st Oct 2010 22:14 UTC, submitted by diegocg
Linux Linux 2.6.34 has been released. This version includes support for the Tilera architecture, a new filesystem notification interface called fanotify, a redesign of workqueues optimized for concurrency, CIFS local caching, support for Intel Intelligent Power Sharing in i3/5 systems, integration of the kernel debugger and KMS, inclusion of the AppArmor security system and several new drivers and small improvements. You can read the full changelog as well.
Thread beginning with comment 446603
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Speed
by sorpigal on Fri 22nd Oct 2010 16:52 UTC in reply to "Speed"
Member since:

If you want to test raw boot speed try changing init to /bin/sh and see what you get.

This isn't 100% reliable of course but it will give you a pretty good idea of what kind of raw boot speed you have.

Reply Parent Score: 2

RE[2]: Speed
by earksiinni on Sat 23rd Oct 2010 01:07 in reply to "RE: Speed"
earksiinni Member since:

Just to add on, it's more complicated than that if you wanted to make that a permanent setup, because init sends out TTY hooks so that the kernel knows to start virtual terminals. So, yes, changing to /bin/sh would get you raw boot speed, but you wouldn't be able to get to shell. You'd be surprised how hard it is to turn Linux into a genuinely single user system (not just selecting single user mode at boot and running as root).

But I understood your comment, which was just talking about the benchmark usage. Point taken.

Reply Parent Score: 1

RE[3]: Speed
by sorpigal on Sat 23rd Oct 2010 12:40 in reply to "RE[2]: Speed"
sorpigal Member since:

It's even worse than that since udev came along. This will only give you an idea of how fast Linux initializes hardware and will not give you a system you can really use. Combined with a benchmark of your real boot it will give you an idea which parts are due to Linux and which are your init system and services (just subtract).

Another useful technique: install a minimal system, such as debian-netinst, and uninstall all daemons that are not actually essential. This still involves some benchmarking of init and so forth but will give you a usable system (albeit with nothing much running).

Reply Parent Score: 2