Well when you benchmark the compile time bfs is usally a bit faster.
Regarding reiser4. I used to use it. Very efficient and decent fs but since it's not developed anymore (?) and as far as I know it didn't approach the stage to be called stable, I don't think Linus would like to include that 'dead' project in the kernel.
Last edited by trapDoor; 12-18-2009 at 01:02 PM.
I seem to get 2.6.33-rc1 from ubuntu's mainline kernel failing to boot into gdm ...
Did they fix the eternal low responsiveness when doing IO already?
I'm getting so fed up with it, and there's no kernel maintainer who's addressing this bug.
Can someone with mainstream hardware (sata; dual-core, 2GB) perform a read test with tiobench 64MB and 32 threads, and still open iotop and use firefox in a usable manner?
What is the preferred distribution to use for testing new kernels?
Indeed, I compiled the kernel source as I always do and this time at reboot, I was requested a firmware or something.
I thought they were compiled in the kernel, weren't they?
Last edited by rvdboom; 12-18-2009 at 03:59 PM.
All new microcode is going into the /lib/firmware folder for distribution rather than being built directly into the kernel. I believe the latest microcode file (rlc) needs to go into the initrd so that drm can find it at boot.
It is still possible to build the firmware into the kernel yourself (ie on your own system) but I think the overall direction for the kernel is increased use of lib/firmware and initrd.
Last edited by bridgman; 12-18-2009 at 04:28 PM.