xfs 파일시스템 단편화 제거에 관한 질문과 답변내용입니다.
xfs파일시스템을 아주 좋아하는듯 보이는군요.. 저도 사용중이고 만족스럽네요.

출처 : http://bitubique.com/content/view/45/50/

I have been using XFS file-system for all my Linux box for quite some time now.
Why? Because I personally feels it a bit faster than either ext2, ext3, or ReiserFS.
On top of that, XFS have some fancy features such as live file-system defragmenting.
Let's cover how to do that.

First, make sure you have the xfsdump utilities install. For Ubuntu, simply issue this

sudo apt-get install xfsdump
Then, optionally you can check how fragmented your file-system is by this command:

sudo xfs_db -r /dev/hda1
xfs_db> frag
actual 300086, ideal 299315, fragmentation factor 0.26%
xfs_db> quit
In my case, my root is /dev/hda1. You need to reply with the device node containing your file-system you want to check.

How to defragment? Simple. Just invoke this command:

sudo xfs_fsr -v /dev/hda1
/ start inode=0
extents before:2 after:1 DONE ino=1278965
extents before:2 after:1 DONE ino=2114947
extents before:2 after:1 DONE ino=254717564

That's it. See...you should really be using XFS


xfs_fsr man page.


'System' 카테고리의 다른 글

CentOS 5.x Utter Ramblings Repo  (0) 2009.01.18
linux kernel 2.6.22 & geoip 패치  (2) 2007.07.22
Defragment XFS File-system  (0) 2006.11.28
커널 컴파일시 HIGHMEM옵션  (0) 2006.11.10
하드디스크 온도 모니터링  (3) 2006.08.04
what to expect (kernel 2.6에 관한 문서)  (0) 2004.10.01

이번에 서버에 메모리를 추가해주고 나서 알게된건데 커널옵션중 HIGHMEM옵션이
off로 되어있다면 메모리 용량이 896MB까지만 인식되고 사용가능하게 되더군요!
원인을 찾다가 커널로그 와 dmseg를 살펴보니 다음같은 메세지가 있었습니다.

kernel: Warning only 896MB will be used.
kernel: Use a HIGHMEM enabled kernel.
kernel: 896MB LOWMEM available.

두번째 라인에 해결책도 제시해 주고 있군요. emoticon

커널 컴파일시 HIGHMEM옵션이 off, 4GB, 64GB이렇게 있습니다만 1GB 미만에서 선택하는
옵션이 off더군요. 쉽게말해 0~1GB미만일때 옵션을 off로 하면 되겠습니다.
괜한 삽질로 인해 커널을 한번더 컴파일했군요 emoticon

정상적으로 정확한 옵션을 선택하고 커널을 컴파일했다면 다음과 같은 메세지를 남기게 됩니다.

시스템에 메모리가 1GB일때
kernel: 127MB HIGHMEM available.
kernel: 896MB LOWMEM available.

Kconfig에는 다음과 같이 설명되어 있습니다.

Linux can use up to 64 Gigabytes of physical memory on x86 systems. However,
the address space of 32-bit x86 processors is only 4 Gigabytes large. That means that,
if you have a large amount of physical memory, not all of it can be "permanently mapped"
by the kernel. The physical memory that's not permanently mapped is called "high memory".
If you are compiling a kernel which will never run on a machine with more than 1 Gigabyte
total physical RAM, answer "off" here (default choice and suitable for most users).
This will result in a "3GB/1GB" split: 3GB are mapped so that each process sees a 3GB
virtual memory space and the remaining part of the 4GB virtual memory space is used
by the kernel to permanently map as much physical memory as possible.

If the machine has between 1 and 4 Gigabytes physical RAM, then answer "4GB" here.
If more than 4 Gigabytes is used then answer "64GB" here. This selection turns Intel PAE (Physical Address Extension) mode on.
PAE implements 3-level paging on IA32 processors. PAE is fully supported by Linux,
PAE mode is implemented on all recent Intel processors (Pentium Pro and better).
NOTE: If you say "64GB" here, then the kernel will not boot on CPUs that don't support PAE!

커널 컴파일시 HIGHMEM 옵션없이 1GB이상의 메모리를 사용하려면 아래링크의 글을
참고하시기 바랍니다.

관련 링크: http://kerneltrap.org/node/6067

서버의 시스템 온도등의 모니터링을 위해 프로그램을 찾던중 hddtemp라는
프로그램을 받아서 설치해봤는데 깔끔하게 온도를 잘 보여주는군요.



hddtemp프로그램은 S.M.A.R.T (Self-Monitoring Analysis and Reporting Technology)
기능을 사용해 하드디스크의 온도를 알려주는 프로그램입니다.
최근에 나온 하드디스크는 온도센서가 달려나와 온도를 모니터링 할수 있습니다.
hddtemp에서 지원되는 하드디스크는 아래링크에서 확인할수 있습니다.



2. 다운로드

가장 최근버전은 0.3-beta15이고 아래링크에서 받을수 있습니다.


3. 설치

일반적인 프로그램설치와 마찬가지로 압축을 풀고
./configure && make &&make install 로 설치하시면 되겠고 하드디스크 리스트파일인 hddtemp.db파을을 받은뒤

/usr/share/misc에 카피하거나 혹은 configure시 위치를 지정해줄수 있습니다.

./configure --with-db-path=/etc/hddtemp.db

hddtemp.db파일은 수시로 갱신된다고 하니 현재 지원하지 않더라도 나중에 지원할수도 있을수 있겠습니다.

가끔씩 확인해보시는것도 좋겠네요.


4. 사용방법
기본적인 사용법은 도움말에 포함되어 있습니다.

#hddtemp --help
Usage: hddtemp [OPTIONS] [TYPE:]DISK1 [[TYPE:]DISK2]...

hddtemp displays the temperature of drives supplied in argument. Drives must support S.M.A.R.T.

TYPE could be SATA, PATA or SCSI. If omitted hddtemp will try to guess.

-b --drivebase : display database file content that allow hddtemp to recognize supported drives.
-D --debug : display various S.M.A.R.T. fields and their values.
Useful to find a value that seems to match the
temperature and/or to send me a report.(done for every drive supplied).
-d --daemon : run hddtemp in TCP/IP daemon mode (port 7634 by default.)
-f --file=FILE : specify database file to use.
-l --listen=addr : listen on a specific interface (in TCP/IP daemon mode).
-n --numeric : print only the temperature.
-p --port=# : port to listen to (in TCP/IP daemon mode).
-s --separator=C : separator to use between fields (in TCP/IP daemon mode).
-S --syslog=s : log temperature to syslog every s seconds.
-u --unit=[C|F] : force output temperature either in Celius or Fahrenheit.
-q --quiet : do not check if the drive is supported.
-v --version : display hddtemp version number.
-w --wake-up : wake-up the drive if need.
-4 : listen on IPv4 sockets only.
-6 : listen on IPv6 sockets only.


간단한 실행결과는 아래와 같습니다.

[root@free4u:~]#hddtemp /dev/hda
/dev/hda: ST380021A: 38 C


특이하게도 hddtemp프로그램을 데몬모드로 띄우고 원격에서 하드디스크의 온도를
모니터링 할수도 있다고 하는데 필요하신분은 -l -p옵션으로 데몬모드로 실행하시면 될듯합니다.

옵션이 꽤 많은데 아주 간단히 온도를 보고자 한다면 hddtemp /dev/hdx 명령으로 온도를 볼수있습니다.

% dev/hdx는 자신의 하드디스크명으로 대체됩니다.


관련 링크: http://www.guzu.net/linux/hddtemp.php

  1. Favicon of http://free4u.wo.tc/ BlogIcon EcusE 2009.02.27 17:17

    시스템에 하드디스크가 2개이상 있다면 hddtemp/contribs/hddtemp-all.sh 스크립트로 여러개의 하드디스크 온도를한번에 볼 수 있습니다.[root@free4u tmp]# hddtemp-all.sh/dev/sda: xxx: 31°C/dev/sdb: xxx: 34°C

  2. Favicon of http://hosting.digimoon.net BlogIcon 디지문 2009.06.20 10:01

    전 이미 MRTG로 그래프 그려가며 온도 모니터링 하고 있죠. ㅎㅎ

  3. Favicon of http://free4u.wo.tc/ BlogIcon EcusE 2009.06.20 14:04

    현재 시스템에서 모니터링 가능한 CPU 및 몇가지 센서를 시스템 통계에 넣을까하는데 귀찮아서 안하고 있네요;;; ^^;;

커널 2.6대에서 바뀐점들과 기존 커널에서 업그레이드시 필요한것들에
관한 문서입니다.기타 문제점들과 해결방법등도 있으니 한번쯤 읽어보시면 도움이 될듯합니다.

출처 : http://www.codemonkey.org.uk/post-halloween-2.5.txt

The post-halloween document. v0.50
(aka, 2.6 - what to expect)

Dave Jones <davej [at] codemonkey [dot] org [dot] uk>

(Updated as of 2.6.3)

This document explains some of the new functionality to be found in the 2.6
Linux kernel, some pitfalls you may encounter, and also points out some
new features which could really use testing.
Note, that "contact foo@bar.com" below also implies that you should also
cc: linux-kernel [at] vger [dot] kernel [dot] org.

Latest version of this document can always be found at

Thanks to many [far too many to list] people for valuable feedback.

Note, that this document is somewhat x86-centric, but most features
documented here affect all platforms anyway.

Spanish - http://www.terra.es/personal/diegocg/post-halloween-2.6.es.txt
German - http://www.kubieziel.de/computer/halloween-german.html
Polish - http://soltysiak.com/linux/post-halloween-2.6.pl.html
pt_BR - http://www.maluco.com.br/docs/post-halloween-2.6-pt_BR.txt

Applying patches.
- In 2.4 and previous kernels, the recommended way to apply patches was
to use a command line such as ...
gzip -cd patchXX.gz | patch -p0
In 2.6, Linus started adding an extra path element to the diffs,
so using -p1 in the untarred 'to be patched' directory is necessary.

Reporting bugs.
Most large subsystems of the kernel have their own mailing list.
Mailing these with bug reports is always good. If in doubt, send
them to linux-kernel [at] vger [dot] kernel [dot] org

ACPI - <acpi-devel [at] lists [dot] sourceforge [dot] net>
Bluetooth - <bluez-devel [at] lists [dot] sourceforge [dot] net>
DVB - <linux-dvd [at] linuxtv [dot] org>
Ext2 - <ext2-devel [at] lists [dot] sourceforge [dot] net>
Firewire - <linux1394-devel [at]  lists [dot] sourceforge [dot] net>
SCSI - <linux-scsi [at] vger [dot] kernel [dot] org>
USB - <linux-usb-users [at ] lists [dot] sourceforge [dot] net>
XFS - <linux-xfs [at] oss [dot] sgi [dot] com>

Known gotchas.
Certain known bugs are being reported over and over. Here are the
- Blank screen after decompressing kernel?
Make sure your .config has
A lot of people have discovered that taking their .config from 2.4 and
running make oldconfig to pick up new options leads to problems, notably
with CONFIG_VT not being set.
- An additional bug biting some people is that NICs fail to receive packets
(usually notable by a NIC not getting a DHCP lease for eg, despite being
sent one by the server). Booting with "noapic" "acpi=off" or a combination
of both fixes this for most people.
- (Possibly linked to above bug) VIA APIC routing is currently broken.
boot with 'noapic'.
- Can't load any modules? You need updated tools (See modules section below).
- depmod reports Unresolved symbols? depmod from modutils instead of
depmod from module-init-tools is first in $PATH (might be different
$PATHs as $USER and $ROOT)
- The boot command line argument mem= changed slightly in 2.6
Arguments such as mem=exactmap mem=640k@0 mem=200M@1M
should now use memmap= instead.

(Things not expected to work just yet)
- The hptraid/promise drivers for proprietary RAID formats are currently
non functional, and will probably be converted to use device-mapper.
- Some filesystems still need work (Intermezzo, UFS, HFS, HPFS..)
- UMSDOS fs is currently missing, pending rewrite.
- EFS (has a blocksize problem, depending on the device that the
filesystem is being mounted on)
- A number of drivers don't compile currently due to them needing various
work to convert them to the new APIs
- The format of /proc/stat changed, which could break some
applications that still depend on the old layout.
- Some people seem to have trouble running rpm, most notably Red Hat 9 users.
This is a known bug of rpm.
Workaround: run "export LD_ASSUME_KERNEL=2.2.5", before running rpm.
This is thought to be a bug related to db4 and O_DIRECT interaction.

Stuff needing forward porting from 2.4.
- HFSPlus
- SuperH 64

Removed features.
- khttpd is gone.
- Older Direct Rendering Manager (DRM) support (For XFree86 4.0)
has been removed. Upgrade to XFree86 4.1.0 or higher.
- LVM1 has been removed. See Device-mapper below.
- The system call table is no longer exported. Any module that relied
on this previously will no longer work.
- Soundmodem hamradio support has been removed. Its functionality
has been superceded by a userspace replacement.
- Direct booting from floppy is no longer supported.
You should now use a boot loader program such as syslinux instead.
"make bzdisk" continues to work (now using syslinux).
- Callout tty devices (/dev/cua) have been deprecated since 2.1.90pre2.
Support is now removed.

Deprecated/obsolete features.
- devfs will be obsoleted in favour of udev (http://www.kernel.org/pub/linux/utils/kernel/hotplug/)
- boot time root= parsing changed.
ramdisks are now ram<n> instead of rd<n> and cm206 is cm206cd (instead of
Additionally, cciss driver needs the numeric device ID passed instead of
the device name.
- usbdevfs will be going away in 2.7. The same filesystem can
be mounted as 'usbfs' in recent 2.4 kernels, and in 2.5.52
and above, which is what the filesystem will furthermore be
known as.
- elvtune is deprecated (as are the ioctl's it used).
Instead, the io scheduler tunables are exported in sysfs (see below)
in the /sys/block/<device>/queue/iosched directory.
Jens wrote a document explaining the tunables of the new scheduler at
- Using sysctls by numeric values is deprecated, and will go away
in the next development series.

- The in-kernel module loader was reimplemented.
- You need replacement module utilities from
- A backwards compatible set of module utilities is also available
from the same URL in RPM format.
- Debian sarge/sid or Conectiva snapshot users can just use
'apt-get install module-init-tools'
- Modules now free stuff marked with __init or __initdata.
- For Red Hat users, there's another pitfall in "/etc/rc.sysinit".
During startup, the script sets up the binary used to dynamically load
modules stored at "/proc/sys/kernel/modprobe". The initscript looks
for "/proc/ksyms", but since it doesn't exist in 2.6 kernels, the
binary used is "/sbin/true" instead.

This, eventually, will keep modules from working. Red Hat users will
have to patch the "/etc/rc.sysinit" script to set
"/proc/sys/kernel/modprobe" to "/sbin/modprobe", even
when "/proc/ksyms" doesn't exist.
- Modules now have a .ko suffix instead of .o
- Some (older) versions of 'mkinitrd' don't search for modules
that end with .ko, so update your mkinitrd if this is a problem.

Kernel build system.
- The build system is much improved compared to 2.4.
You should notice quicker builds, and less spontaneous rebuilds
of files on subsequent builds from already built trees.
- There are new graphical config tools.
"make xconfig" now requires the qt libraries.
"make gconfig" uses gtk libraries.
- Make menuconfig/oldconfig has no user-visible changes other than speed,
whilst numerous improvements have been made.
- Several new debug targets exist: 'allyesconfig' 'allnoconfig' 'allmodconfig'.
- Note: The new configuration system is not CML2 related.
- Also note: Whilst some ideas were taken from it, Keith Owens'
kbuild-2.5 project was not integrated.
- "make" is now the preferred command, without a target; it does <arch-zimage>
and modules.
- "make -jN" is now the preferred parallel-make execution.
Do not bother to provide "MAKE=xxx"
- The build is now much less verbose. If you want to see exactly what's
going on, try "make V=1" or set KBUILD_VERBOSE=1 in your environment.
- 'make kernel/mm.o' will build the named file, provided a
corresponding source exists. This also works for (non-composite)
modules. (FIXME: broken for modules right now?)
- 'make kernel/' will compile all files in a subdirectory and below.
- There is no need to run 'make dep' at any stage.
- 'make help' provides a list of typical targets, including debugging targets.
- You can now build in a separate tree from the source by doing
make O=builddir

IO subsystem.
- You should notice considerable throughput improvements over 2.4 due
to much reworking of the block and the memory management layers.
- Report any regressions in this area to Jens Axboe <axboe [at] suse [dot] de>
and Andrew Morton <akpm [at] osdl [dot] org>
- Two different IO elevators are available. The default is the
anticipatory IO scheduler. You can select the deadline scheduler by
booting with "elevator=deadline" on the kernel command line.
- For some workloads the anticipatory scheduler is around 10% slower
than deadline. Most notably, database workloads which seek all over the
disk performing reads and synchronous writes. Database folks will likely
want to boot with elevator=deadline to get that last bit of performance back.
- Assorted changes throughout the block layer meant various block
device drivers had a large scale cleanup whilst being updated to
newer APIs.
- The size and alignment of O_DIRECT file IO requests now matches that
of the device, not the filesystem. Typically this means that you
can perform O_DIRECT IO with 512-byte granularity rather than 4k.
But if you rely upon this, your application will not work on 2.4 kernels
and will not work on some devices.

block device size support.
- Thanks to work done by Peter Chubb, block devices can now access up to
16TB on 32-bit architectures, and up to 8EB on 64-bit architectures.
- To use the new BLKGETSZ64 ioctls, you'll need updated file-utils.
(Currently only jfsutils 1.0.20 has this change, patches for other
filesystems are still pending merging)
- The old 'struct statfs' is not able to describe large devices - the
statfs() system call will now return -EOVERFLOW for such devices.
A new system call called statfs64() with a new structure has been added
to support large devices. It it unknown at time of writing how many
userspace utilities have been converted to take advantage of this
syscall when available.

POSIX ACLs & Extended attributes.
- Userspace tools available at http://acl.bestbits.at

VM Changes.
- Version zero swap partitions are no longer supported (everything is
using v1 now anyway - rerun mkswap if in doubt).
Linux 2.0.x requires v0 swap space, Linux v2.1.117 and later
support v1. mkswap(8) can format swap space in either format.
- The actual 'reverse mappings' part of Rik van Riel's rmap vm was merged.
VM behaviour under certain loads should improve.
- VM misbehaviour should be reported to <linux-mm [at] kvack [dot] org>
- The VM explicitly checks for sparse swapfiles, and aborts if one is found.
- /proc/sys/vm/swappiness defines the kernel's preference for pagecache over
mapped memory. Setting it to 100 (percent) makes it treat both types of
memory equally. Setting it to zero makes the kernel very much prefer to
reclaim plain pagecache rather than mapped-into-pagetables memory.
- The bdflush() syscall is now officially deprecated. The syscall
does nothing, and prints a stern warning to users. The functionality
is replaced by the pdflush daemons.
- Due to various changes, swap files should be just as fast as swap partitions.
- In 2.4, up to 64 swap files were possible. In 2.6, this number is reduced
to 32. Like 2.4, these files can be up to 64GB in size, though you will
need a recent util-linux to have a mkswap utility that supports >2GB

Kernel preemption.
- The much talked about preemption patches made it into 2.6.
With this included you should notice much lower latencies especially
in demanding multimedia applications.
- Note, there are still cases where preemption must be temporarily disabled
where we do not. These areas occur in places where per-CPU data is used.
- If you get "xxx exited with preempt count=n" messages in syslog,
don't panic, these are non fatal, but are somewhat unclean.
(Something is taking a lock, and exiting without unlocking)
- If you DO notice high latency with kernel preemption enabled in
a specific code path, please report that to Andrew Morton <akpm [at] osdl [dot] org>
and Robert Love <rml [at] tech9 [dot] net>
The report should be something like "the latency in my xyz application
hits xxx ms when I do foo but is normally yyy" where foo is an action
like "unlink a huge directory tree".

Process scheduler improvements.
- Another much talked about feature. Ingo Molnar reworked the process
scheduler to use an O(1) algorithm. In operation, you should notice
no changes with low loads, and increased scalability with large numbers
of processes, especially on large SMP systems.
- Scheduler is now Hyperthreading SMP aware and will disperse processes
over physically different CPUs, instead of just over logical CPUs.
- Robert Love wrote various utilities for changing behaviour of the
scheduler (binding processes to CPUs etc). You can find these tools at
- The behavior of sched_yield() changed a lot. A task that uses
this system call should now expect to sleep for possibly a very
long time. Tasks that do not really desire to give up the
processor for a while should probably not make heavy use of this
function. Unfortunately, some GUI programs (like Open Office)
do make excessive use of this call and under load their
performance is poor. It seems this new 2.6 behavior is optimal
but some user-space applications may need fixing.
- The above applies to use of yield() in the kernel, too.
- 2.6 adds system calls for manipulating a task's processor
affinity: sched_getaffinity() and sched_setaffinity()
- Regressions to <mingo [at] redhat [dot] com> and <rml [at] tech9 [dot] net>
- Debian users who encounter effects such as skips in mp3
playback, jerky mouse movement may want to stop the
X server from renicing itself to -10
You can alter this permanently with 'dpkg-reconfigure xserver-common';
if you elect not to have /etc/X11/Xwrapper.config managed by debconf,
simply edit it directly.
- Balancing of IRQs between multiple CPUs should be handled using the
irqbalance (http://people.redhat.com/arjanv/irqbalance/) program.
- David Mosberger maintains a webpage containing some current 'known gotchas'
of the O(1) scheduler at http://www.hpl.hp.com/research/linux/kernel/o1.php

- PCI domain support has been added. For most people, this just means that
all PCI slot names are extended with "0000:" on the front, but for people
with bigger servers it means they're able to access all their PCI devices.
- More hotplug drivers have been added, including a fake PCI hotplug driver
so people without specialised hardware can test hotplug features.

- /dev/hwrandom got support for some new hardware (now also backported to 2.4)
such as the HW RNG on newer VIA Cyrix CPUs.
- rng-tools can be found at http://sourceforge.net/projects/gkernel

Fast userspace mutexes (Futexes).
- Rusty Russell added functionality that allows userspace to have
fast mutexes that only use syscalls when there is contention. Used by
- Additional information on futexes can be found in Ulrich Dreppers
paper on the subject at http://people.redhat.com/drepper/futex.pdf
- Bert Hubert has written some documentation on this functionality
at http://ds9a.nl/futex-manpages

Davide Libenzi wrote an event based poll replacement that got
included in 2.6. More info available at

Threading improvements.
- Ingo Molnar put a lot of work into threading improvements for 2.6.
Some of the features of this work are:
- Generic pid allocator (arbitrary number of PIDs with no slowdown,
unified pidhash).
- Thread Local Storage syscalls
- POSIX thread signals stuff (atomic signals, shared signals, etc.)
- Threaded coredumping support
- sys_exit() speedups (O(1) exit)
- Generic, improved futexes, vcache
- New, threading related ptrace features
- exit/fork task cache
- /proc updates for threading
- API changes for threading.
- Users should notice a significant speedup in basic thread operations.
This is true to a lesser extent even for old-threading userspace libraries
such as LinuxThreads.
- Regressions should go to Ingo Molnar <mingo [at] redhat [dot] com> and
<phili-list [at] redhat [dot] com>. Regressions could happen in the area of signal
handling and related threading semantics, plus coredumping.
- Native Posix Threading Library (NPTL).
Ulrich Drepper worked closely with Ingo on the threading enhancements, and
developed a 1:1 model threading library. You can find out more about NPTL at

Enhanced coredumping.
- 2.6 offers you the ability to configure the way core files are
named through a /proc/sys/kernel/core_pattern file.
You can use various format identifiers in this name to affect
how the core dump is named.

%p - insert pid into filename
%u - insert current uid into filename
%g - insert current gid into filename
%s - insert signal that caused the coredump into the filename
%t - insert UNIX time that the coredump occurred into filename
%h - insert hostname where the coredump happened into filename
%e - insert coredumping executable name into filename

You should ensure that the string does not exceed 64 bytes.
- Multithreaded processes can now dump core

Input layer.
- Possibly the most visible change to the end user. If misconfigured,
you'll find that your keyboard/mouse/other input device will no longer work.
2.6 offers a much more flexible interface to devices such as keyboards.
- The downside is more confusing options.
In the "Input device support" menu, be sure to enable at least the following.

--- Input I/O drivers
< > Serial i/o support
< > i8042 PC Keyboard controller
[ ] Keyboards
[ ] Mice

(Also choose the relevant keyboard/mouse from the list)

- If you find your keyboard/mouse still don't work, edit the file
drivers/input/serio/i8042.c, and replace the #undef DEBUG
with a #define DEBUG, recompile and reinstall.

When you boot, you should now see a lot more debugging information.
Forward this information to Vojtech Pavlik  <vojtech [at] suse [dot] cz>

- If you use a KVM switcher, and experience problems, booting with the boot
time argument 'psmouse_noext' should fix your problems.
- Users of multimedia keys without X will see changes in how the kernel
handles those keys. People who customize keymaps or keycodes in 2.4
may need to make some changes in 2.6
- Users wanting support for the PC speaker need to enable CONFIG_INPUT_PCSPKR,
or you won't get a single beep.
- Synaptics touchpad users may be interested to check out
- In 2.4 users of Japanese keyboards were able to type '|' or
'' characters without loading any custom keymap on the
console. With the keymap in 2.6, this is not possible
anymore. People with these keyboards have to load a keymap
with loadkeys rebuilt from the source, since loadkeys in some
vendor distributions cannot load keycodes larger than 127.
There is a patch to fix this, but it has not been integrated
- A FAQ on common problems with the new input layer is available
at http://lwn.net/Articles/69107/

PnP layer.
- Support for plug and play devices such as early ISAPnP cards has improved a
lot in the 2.6 kernel. The new code behaves more closely to the code
handling PCI devices (probe, remove etc callbacks), and also merges
PnP BIOS access code.
- Report any regressions in plug & play functionality to
Adam Belay <ambx1 [at] neo [dot] rr [dot] com>

- The advanced linux sound architecture was merged into 2.6.
This offers considerably improved functionality over the older OSS drivers,
but requires new userspace tools.
- Several distros have shipped ALSA for some time, so you may already have the
necessary tools. If not, you can find them at http://www.alsa-project.org/
- ALSA can emulate OSS interface using the snd_pcm_oss/snd_pcm_mixer
modules, if your card produces nothing but silence, you may need to run
alsamixer to unmute channels wich /dev/mixer doesn't see
- Note that the OSS drivers are also still functional, and still present.
Many features/fixes that went into 2.4 are still not applied to these
drivers, and it's still unclear if they will remain when 2.6 ships.
The long term goal is to get everyone moved over to (the superior) ALSA.

- The agpgart driver got a long overdue cleanup which involved
splitting it into an agpgart core, and per-chipset drivers.
You may need to adjust your modules configuration to autoload
the chipset drivers on loading the agpgart module.
- Generic AGP 3.0 support is now included.

- Direct rendering in 2.6 hasn't had much (if any?) testing on
older versions of XFree86. Feedback on whether 4.1 works would
be useful.

Faster system calls.
- Systems that support the SYSENTER extension (Basically Intel Pentium-II
and above, and AMD Athlons) now have a faster method of making the
transition from userspace to kernelspace when a syscall is performed.
- Pentium Pro also has SYSENTER, but due to errata, is unusable.
- Without an updated glibc, this will not be noticable.
- VMWare 4 users may get crashes due to this.
Zwane Mwaikambo wrote a patch for a "nosysenter" option which is worth
googling for if there isn't a vmware update available.
- Regressions to <torvalds [at] osdl [dot] org> and <libc-alpha [at] sources [dot] redhat [dot] com> 

- The 2.6 /proc filesystems changed some statistics, which confuse older
versions of procps. Rik van Riel and Robert Love have been maintaining a
version of procps during the development of 2.6 which tracks changes to
/proc which you can find at http://tech9.net/rml/procps/
- Alternatively, the procps by Albert Cahalan now supports the altered formats
since v3.0.5 -- http://procps.sf.net/
- The /proc/meminfo format changed slightly which also broke gtop in strange
ways. Likely this also broke some of the KDE/GNOME panel applets.

Framebuffer layer.
- James Simmons has reworked the framebuffer/console layer considerably for
2.6. Support for some cards is still lagging a little, but it should be
functionally no different than previous incarnations.
- boot time arguments may have changed depending on your driver.
an example of the change is..
append = "video=radeon:1024x768-24@100"
needs to become..
append = "video=radeonfb:1024x768-24@100"
- Current userspace tools (fbset for eg) are not yet updated,
and won't function as expected.
- The VESA framebuffer now enables MTRRs for the framebuffer memory range during
initialisation (Note: PCI cards only).
If you notice screen corruption, please report this, along with an lspci output,
so your card can be blacklisted.
- Any problems should go to <jsimmons [at] infradead [dot] org>

- The IDE code rewrite was subject to much criticism in early 2.5.x, which
put off a lot of people from testing. This work was then subsequently
dropped, and reverted back to a 2.4.18 IDE status.
Since then additional work has occurred, but not to the extent
of the first cleanup attempts.
- Known problems with the current IDE code.
o Simplex IDE devices (eg Ali15x3) are missing DMA sometimes
o Most PCMCIA devices have unload races and may oops on eject
o Modular IDE does not yet work, modular IDE PCI modules sometimes
oops on loading
o ide-scsi is completely broken in 2.6 currently. Known problem.
If you need it either use 2.4 or fix it 8)
- IDE disk geometry translators like OnTrack, EZ Partition, Disk Manager
are no longer autodetected. The only way forward is to remove the translator
from the drive, and start over, or use boot parameters depending on the
type of remapper used :-
hdx=remap63 - add 63 to each sector (For OnTrack DM)
hdx=remap - remap 0->1 (For EZDrive)
- See also the CD Recording section for some important changes
related to IDE CD writers.

- Tagged command queueing for IDE devices has been included.
- Not all combinations of controllers & devices may like this,
so handle with care.
READ AS: ** Don't use IDE TCQ on any data you value.
It's likely bad combinations will be blacklisted as and when discovered.

- If you didn't choose the "TCQ on by default" option, you can enable
it by using the command

echo "using_tcq:32" > /proc/ide/hdX/settings

(replacing 32 with 0 disables TCQ again).

- Report success/failure stories to Jens Axboe <axboe [at] suse [dot] de> with
inclusion of hdparm -i /dev/hdX, and lspci output.

- Various SCSI drivers still need work, and don't even compile.
- Various drivers currently lack error handling.
These drivers will cause warnings during compilation due to
missing abort: & reset: functions.
- Note, that some drivers have had these members removed, but still
lack error handling. Those noticed so far are ncr53c8xxx, sym53c8xx
- large dev_t support allowing thousands of disks to be
supported (was 128 or 256 in the 2.4 series)
- major code cleanup, initially to support the block layer (bio)
improvements have led to:
- better throughput (?) [less double handling of data]
- per HBA locks (there was a single io_request_lock in
the 2.4 series)
- more flexible interface to HBA drivers
- better hotplug support, especially for USB mass storage
and ieee1394 sbp2 devices [well it's work_in_progress]
- improved error processing and scanning code (support for
large, sparse lun spaces)
- lots of scsi driver internals available via sysfs

- The video4linux API finally got its long awaited cleanup.
- xawtv, bttv and most other existing v4l tools are also compatible
with the new v4l2 layer. You should notice no loss in functionality.
- See http://bytesex.org/v4l/ for more information.

Quota reworking.
The new quota system needs new tools. Supports 32 bit uids.

CD Recording.
- Jens Axboe added the ability to use DMA for writing CDs on
ATAPI devices. Writing CDs should be much faster than it
was in 2.4, and also less prone to buffer underruns and the like.
- With a recent cdrecord, you also no longer need ide-scsi in order to use
an IDE CD writer.
- Ripping audio tracks off of CDs now also uses DMA and should be
notably faster. You can also find an updated cdda2wav at:
- Send good/bad reports of audio extraction with cdda2wav and burning with
the cdrecord to Jens Axboe <axboe [at] suse [dot] de>
- Currently only 'open by device name' works in cdrecord.
cdrecord -dev=/dev/hdX -inq
- More info at http://lwn.net/Articles/13538/ & http://lwn.net/Articles/13160/

- USB host controller drivers were renamed in 2.6. They are now
uhci-hcd for UHCI controllers.
ohci-hcd for OHCI controllers.
ehci-hcd for EHCI (USB 2.0) controllers.
- Very little user visible changes, the only noticable 'major' change
is that there is now only one UHCI driver. As noted elsewhere, usbdevfs
was renamed to usbfs.
- USB-storage has changed behaviour. A device which is disconnected and
then reconnected is not reassociated with the old /dev node.
- USB storage also got several performance enhancements.

- USB 'gadget' support.
There's a new "USB Gadget" API supporting USB devices that
run Linux inside. Examples include PDAs, cable modems,
and some printers. That API is how the driver for the
USB Device Controller (UDC) hardware talks with portable
"gadget drivers". A gadget driver is what makes that
hardware act like a "network link" or a "printer".

When you don't want to write a gadget driver in the kernel,
then "gadgetfs" lets you do it in user mode programs.
Each endpoint appears as a single file, so it's a lot
simpler than "usbfs". Currently it's purely synchronous,
but it should be natural for someone to add AIO support.

See http://www.linux-usb.org/gadget for more information
about this API framework, including a pthreaded example
"gadgetfs" program. See the 2.6 kerneldoc for API info.

Nanosecond stat:
The stat64() syscall was changed to return jiffies granularity.
This allows make(1) to make better decisions on whether or not it
needs to recompile a file. Not all filesystems may support such precision.

A number of additional filesystems have made their way into 2.6.
Currently it supports: ext2, ext3, reiserfs, jfs, xfs, minix, romfs,
iso9660, udf, msdos, vfat, ntfs (ro), adfs, amiga ffs, apple macintosh hfs,
BeOS befs (ro), bfs, efs (ro), cramfs, free vxfs, os/2 hpfs, qnx4fs,
sysvfs, ufs.
Whilst these have had testing out of tree, the level of testing
after merging is unparalleled. Be wary of trusting data to immature
filesystems. A number of new features and improvements have also
been made to the existing filesystems from 2.4.

Reports of stress testing with the various tools available would
be beneficial.

Generic VFS changes.
- Since Linux 2.5.1 it is possible to atomically move a subtree to
another place. The usage is...
mount --move olddir newdir
- Since 2.5.43, dmask=value sets the umask applied to directories only.
The default is the umask of the current process.
The fmask=value sets the umask applied to regular files only.
Again, the default is the umask of the current process.
- Directories can now be marked as synchronous using chattr +S,
so that all changes will be immediately written to disk.
Note, this does not guarantee atomicity, at least not for all filesystems
and for all operations. You *can* be guaranteed that system calls will
not return until the changes are on disk; note though that this does have
has some significant performance impacts.

- devfs was somewhat stripped down and a lot of duplicate functionality
was removed. You now need to enable CONFIG_DEVPTS_FS=y and mount
the devpts filesystem in the same manner you would if you were not
using devfs.

- 2.5.49 included an extension to ext2 which will cause it to not attach
buffer_head structures to file or directory pagecache at all, ever.
This is for the big highmem machines. It is enabled via the `-o nobh'
mount option.
- The ext2 filesystem is now using finer-grained locking which yields reduced
context switch rates and higher throughput on large SMP machines.

- The ext3 filesystem has gained indexed directory support, which offers
considerable performance gains when used on filesystems with directories
containing large numbers of files.
- In order to use the htree feature, you need at least version 1.32 of
- Existing filesystems can be converted using the command

tune2fs -O dir_index /dev/hdXXX

- The latest e2fsprogs can be found at
- The ext2 and ext3 filesystems have new file allocations policies (the "Orlov
allocator") which will place subdirectories closer together on-disk. This
tends to mean that operations which touch many files in a directory tree are
much faster if that tree was created under a 2.6 kernel.

- Reiserfs now supports inode attributes such as immutable.
(Also included in 2.4.17, so not really 'new').
- Relocated/non-standard size journal support (also backported
to 2.4.22pre3)
- Support for writes larger than 4KB in size, which means speedups
on large file writes, esp in append mode, should also be more
SMP friendly.
- Variable blocksize support. (Ie, you can choose any blocksize
in the range of 1024 .. PAGE_CACHE_SIZE, must be power of 2).
- A bug in kmail was triggered by some optimisations in reiserfs in 2.6
Upgrading kmail should fix this, or mounting the reiserfs partition
with 'nolargeio=1'

- Basic support has been added for NFSv4 (server and client)
- Additionally, kNFSD now supports transport over TCP.
This experimental feature is also backported to 2.4.20
- Interoperability reports with other OS's would be useful.
- v1.0.3 of nfs-utils supports the newer 2.6 kernels change
of kdev_t type. You can grab it at http://nfs.sourceforge.net
- Problems to <nfs [at] lists [dot] sourceforge [dot] net>

- A new, rewritten NTFS driver was merged for 2.6. It has the
following main benefits over the old driver:
- SMP and reentrant safe
- support bigger than 4 kB cluster sizes
- full support for sparse files on W2K/XP/W2K3
- mmap() support
- More stable, and much faster than the previous NTFS driver.
- Still read-only, but with safe file overwrite support without changes
to the file size
- More information is available at http://linux-ntfs.sf.net

In simple terms, the sysfs filesystem is a saner way for
drivers to export their innards than /proc.
This filesystem is always compiled in, and can be mounted
just like another virtual filesystem. No userspace tools
beyond cat(1) and echo(1) are needed. tree(1) is also good for
viewing its overall structure.

mount -t sysfs none /sys

See Documentation/filesystems/sysfs.txt for more info.

IBM's JFS was merged for 2.6. (And backported to 2.4.20, but
it was still a new feature here first. You can read more about JFS at

The SGI XFS filesystem has been merged, and has a number of userspace
features. Users are encouraged to read http://oss.sgi.com/projects/xfs
for more information.
The various utilities for creating and manipulating XFS volumes can
be found on SGI's ftp server:

Support utilities and documentation for the common internet file system (CIFS)
can be found at http://us1.samba.org/samba/Linux_CIFS_client.html

CVF (Compressed VFAT) support has been removed. This means you
will no longer be able to access DriveSpace partitions.

Files in this filesystem are backed by large pages if the CPU
supports them. See Documentation/vm/hugetlbpage.txt for more details.

Internal filesystems.
/proc/filesystems will contain several filesystems that are not
mountable in userspace, but are used internally by the kernel
to keep track of things. Amongst these filesystems are futexfs
and eventpollfs.

Kernel Asynchronous I/O (AIO) Support
Support for kernel AIO has been included in 2.6.

AIO enables even a single application thread to overlap I/O
operations with other processing, by providing an interface
for submitting one or more i/o requests in one system call
(io_submit) without waiting for completion, and a separate
interface (io_getevents) to reap completed i/o operations
associated with a given completion group.

The following is a quick summary of what works today as
- AIO read and write on raw (and O_DIRECT on blockdev)
- AIO read and write on files opened with O_DIRECT on
ext2, ext3, jfs, xfs

And what doesn't work as expected or is not currently
- AIO read and write on files opened without O_DIRECT
(i.e. normal buffered filesystem AIO). On ext2, ext3,
jfs, xfs and nfs, these do not return an explicit
error, but quietly default to synchronous or rather
non-AIO behaviour (i.e io_submit waits for i/o to complete
in these cases). For most other filesystems, -EINVAL is
- AIO fsync (not supported for any filesystem)
- AIO read and write on sockets (doesn't return an
explicit error, but quietly defaults to synchronous
or rather non-AIO behaviour)

You need to install libaio-0.3.92 (available at
if you are writing AIO applications which use the native
AIO interfaces.

More info is available at http://lse.sf.net/io/aio.html

- A system wide performance profiler (Oprofile) has been included in 2.6.
With this option compiled in, you'll get an oprofilefs filesystem
which you can mount, that the userspace utilities talk to.
You can find out more at http://oprofile.sf.net/
- You need a fixed readprofile utility for 2.6.
Present in util-linux as of 2.11z

Improved BIOS table support.
- Linux now supports various new BIOS extensions.

Simple boot flag support.
The SBF specification is an x86 BIOS extension that allows improved
system boot speeds. It does this by marking a CMOS field to say
"I booted okay, skip extensive POST next reboot".
Userspace tool is at http://www.codemonkey.org.uk/projects/sbf/sbf.c
More info on SBF is at http://www.microsoft.com/hwdev/resources/specs/simp_bios.asp

EDD Support.
- Support for BIOS Enhanced Disk Drive Services (EDD) was added,
which exports information on what the BIOS thinks is the boot
drive and other useful info to /sys/firmware/edd
- Matt Domsch is interested in hearing success/fails on this code
with some simple tests decribed at http://linux.dell.com/edd/results.html

Improved system monitoring.
- lm_sensors.
- Shipped in vendors kernels for years, lm_sensors is now part of mainline.
It does however have a different interface. (/sysfs instead of /proc
- http://www.xs4all.nl/~thospel/ASIS/bin/psensors is a handy script
for parsing the new sysfs fields.
- IPMI. (Intelligent Platform Management Interface)
- IPMI is a standard for monitoring the hardware in a system.
- Project home page: http://openipmi.sourceforge.net
- Specification: http://www.intel.com/design/servers/ipmi/spec.htm

x86 CPU detection.
- The CPU detection code got a pretty hefty shake up. To be certain your
CPU has all relevant workarounds applied, be sure to check that it was
detected correctly. cat /proc/cpuinfo will tell what the kernel thinks it is.
- Likewise, the x86 MTRR driver got a considerable makeover.
Check that XFree86 sets up MTRRs in the same way it did in 2.4
(Failures will get logged in /var/log/XFree86.log)
- Early PII Xeon processors and possibly other early PII processors
require microcode updates either from the BIOS or the microcode driver
to work around CPU bugs the O(1) scheduler exposes.
You can find the relevant microcode tools at
- Any regressions in both should go to <mochel [at] sodl [dot] org>Cc: <davej [at] codemonkey [dot] org [dot] uk> 

Extra tainting.
Running certain AMD processors in SMP boxes is out of spec, and will taint
the kernel with the 'S' flag. Running 2 Athlon XPs for example may seem to
work fine, but may also introduce difficult to pin down bugs.
In time it's likely this tainting will be extended to cover other out of
spec cases.

Additionally, the new modules interface will taint the kernel if you try
to 'force' a module to load with insmod -f.

Power management.
- 2.6 contains a more up to date snapshot of the ACPI driver. Should
you experience any problems booting, try booting with the argument
"acpi=off" to rule out any ACPI interaction. ACPI has a much more involved
role in bringing the system up in 2.6 than it did in 2.4
- The old "acpismp=force" boot option is now obsolete, and will be ignored
due to the old "mini ACPI" parser being removed.
- software suspend is still in development, and in need of more work.
Use with SMP and/or PREEMPT not advised.
- The ACPI code will do basic sanity checks on the DMI structure in the BIOS
to determine the date it was written. BIOSes older than year 2000 are
assumed to be broken. In some circumstances, this assumption is wrong.
If you see a message saying ACPI is disabled for this reason, try booting
with acpi=force. If things work fine, send the output of dmidecode
(http://www.nongnu.org/dmidecode/) to <acpi-devel [at] lists [dot] sf [dot] net>
with an explanation of why your BIOS shouldn't be blacklisted.

CPU frequency scaling.
Certain processors have the facility to scale their voltage/clockspeed.
2.6 introduces an interface to this feature, see Documentation/cpufreq
for more information. This functionality also covers features like
Intel's speedstep, and the Powernow! feature present in mobile AMD Athlons.
In addition to x86 variants, this framework also supports various ARM CPUs.
You can find a userspace daemon that monitors battery life and
adjusts accordingly at: http://sourceforge.net/projects/cpufreqd

Background polling of MCE.
The machine check handler has been extended so that it regularly polls
for any problems on AMD Athlon, and Intel Pentium 4 systems.
This may result in machine check exceptions occuring more frequently
than they did in 2.4 on out of spec systems (Overclocking/inadequate
cooling/underated PSU etc..).

LVM2 - DeviceMapper.
The LVM1 code was removed wholesale, and replaced with a much better
designed 'device mapper'.
- This is backwards compatible with the LVM1 disk format.
- Device mapper does require new tools to manage volumes however.
You can get these from ftp://ftp.sistina.com/pub/LVM2/tools/

Debugging options.
During the stabilising period, it's likely that the debugging options
in the kernel hacking menu will trigger quite a few problems.
Please report any of these problems to <linux-kernel [at] vger [dot] kernel [dot] org>
rather than just disabling the relevant CONFIG_ options.

Merging of kksymoops means that the kernel will now spit out
automatically decoded oopses (no more feeding them to ksymoops).
For this reason, you should always enable the option in the
kernel hacking menu labelled "Load all symbols for debugging/kksymoops".

Testing with CONFIG_PREEMPT will also increase the amount of debug
code that gets enabled in the kernel. Kernel preemption gives us
the ability to do a whole slew of debugging checks like sleeping
with locks held, scheduling while atomic, exiting with locks held, etc.

Compiler issues.
- The recommended compiler (for x86) is still 2.95.3.
- When compiled with a modern gcc (Ie gcc 3.x), 2.6 will use additional
optimisations that 2.4 didn't. This may shake out compiler bugs that
2.4 didn't expose.
- Do not use gcc 3.0.x on x86 due to a stack pointer handling bug.
- gcc 2.96 is not supported with CONFIG_FRAME_POINTER=y due to a stack
pointer handling bug.

Security concerns.
Several security issues solved in 2.4 may not yet be forward ported
to 2.6. For this reason 2.6.x kernels should not be tested on
untrusted systems. Testing known 2.4 exploits and reporting results
is useful.

NSA Security-Enhanced Linux (SELinux) was merged in 2.6.
SELinux defaults to not being config'd in. If you
config it in it defaults to enabled. If you also config the bootparam
you can use that param to disable it, otherwise selinux=1 is redundant
as that's the default.

You can obtain SELinux tools and an example policy configuration from

- ebtables
The bridging firewall code was merged. To manage these you'll
need the ebtables tool available from
More on bridge-nf can be found at http://bridge.sourceforge.net
- Bridged packets can now be 'seen' by iptables.
- IPSec
Linux finally has IPSec support in mainline. Use the KAME tools port on
For more info see http://www.lib.uaa.alaska.edu/linux-kernel/archive/2002-Week-44/1127.htm...
Also Bert Hubert has a howto at http://lartc.org/howto/lartc.ipsec.html
Additionally, ipsec-utils is at http://sourceforge.net/projects/ipsec-tools
Herbert Xu also has patches against FreeSWAN 2.00 to allow its userspace
to use the 2.6 IPSec functionality. They can be downloaded from
An additional HOWTO is at http://www.ipsec-howto.org
- Some applications may trigger the kernel to spit out warnings about
'process xxx using obsolete setsockopt SO_BSDCOMPAT' .
- Bind 9.2.2 checks for #ifdef SO_BSDCOMPAT in <asm/socket.h> correctly,
so a recompile is all that is needed.
- bind9-host from debian testing triggers, though the 'host' package doesn't.
- process `snmpd' is using obsolete setsockopt SO_BSDCOMPAT
- process `snmptrapd' is using obsolete setsockopt SO_BSDCOMPAT
- ntop uses obsolete (PF_INET,SOCK_PACKET)
- Users of boxes with >1 NIC may find that for eg, eth0 and eth1 refer to
the opposites of what they did in 2.4. This is a bug that will be fixed
before 2.6.0. One option (or management workaround) for this is to use
'nameif' to name Ethernet interfaces. There is a HOWTO for doing this at
- Support for various new RFCs.
- RFC3173 (IP Payload Compression).
- RFC3041 (IPv6 Privacy Extensions).
- RFC2473 (IPv6 in IPv6 tunnels).
- RFC2960 (SCTP - see below).
- Linux reaches congestion collapse when subjected to heavy network load.
NAPI fixes this amongst other things and therefore improving network
More info at http://www.cyberus.ca/~hadi/usenix-paper.tgz and
- IPVS (IP Virtual Server)
- RFC 2960 - SCTP (Stream Control Transmission Protocol)
SCTP is an IP based, message oriented reliable transport protocol with
congestion control, support for transparent multi-homing and multiple
ordered streams of messages. RFC2960 defines the core protocol.
More information about the protocol can be found at
and about the Linux kernel implementation at
- ANSI/IEEE 802.2 LLC type 2 Support
Full implementation of LLC 1 and 2 stack, used by Appletalk, IPX and Token
Ring, also needed for the out of the tree, not yet functional NetBEUI
stack and for the for Linux SNA.

This is based on the stack released under the GPL by Procom Inc. for the
2.0.30 Linux kernel.

- A generic crypto API has been merged, offering support for various
algorithms (HMAC,MD4,MD5,SHA-1,SHA256,SHA384,SHA512,DES,Triple DES EDE,
Blowfish, Twofish, Serpent, AES, CAST5, CAST6)

- This functionality is used by IPSec and the crypto-loop. It's possible
that it will later also be available for use in userspace through a crypto
device, possibly compatible with the OpenBSD crypto userspace.

- The in-kernel loopback device can now do crypto using the CryptoAPI.
May need new userspace tools.

- A 2.4->2.6 cryptoloop migration guide is at http://clemens.endorphin.org/Cryptoloop_Migration_Guide.html

- 2.6 features support for several new architectures.
- x86-64 (AMD Hammer)
- ppc64
- UML (User mode Linux)
See http://user-mode-linux.sf.net for more information.
- uCLinux: m68k(w/o MMU), h8300 and v850. sh also added a uCLinux option.
- The 64 bit s390x port was collapsed into a single port, appearing
as a config option in the base s390 arch.
- In the opposite direction, arm26 was split out from arm.
- x86 architecture also got 'subarch' support to support 'strange' x86
boxes (usually big boy toys). Currently supported subarchs include
- ES7000
- PC9800 (incomplete merge)
- VISWS (Was in 2.4, but now maintained again)
- Voyager. (http://www.hansenpartnership.com/voyager/)

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Revision history:
0.50 - mem= arguments moved to memmap=
0.49 - additional pt_BR translation URL.
Note about cciss & root= device ID
Mention kmail/reiserfs bug
Add pointer to input layer FAQ.
Update EDD URL.
Update polish translation.
Update brazil translation url.
0.48 - gadgetfs
cryptoloop howto URL.
Mailing list pointers.
0.47 - Add futex paper URL.
Correct libc-alpha mailing list.
Jeff Garzik shouldn't get IRQ routing problems
Clarify syslinux necessity for boot disks.
Add depmod to common gotchas
Add EFS regression
Add mkinitrd note to modules section.
Various grammar cleanups
Mention tree(1) in sysfs section
SELinux corrections.
Duh, numerical sysctls are deprecated not syscalls.
Document seperate build dir feature.
/proc/stat changes broke more than just DOTS.
Add Japanese keyboard issue to input section.
0.46 - Update akpm's email address.
Mention LLC in the networking section.
Added link to 2.6 migration guide.
0.45 - DEVFS is obsolete.
Add pt_BR translation.
0.44 - lm_sensors.
x86 subarch support.
Add link to Joseph Pranevich's 2.6 doc.
Mention chattr +S
Update dmidecode URL
Fix sbf.c URL
Fix typos (s/proprietory/proprietary/)
add URL to patched cdda2wav.
Mention which filesystems does 2.6 actually supports.
Add a small note about SELinux
Add a few more RFCs which we now support in the Networking section
Change IPVS to IPVS (IP Virtual Server)
Mention additional encryption algorithms that crypto api supports
Add a few things to TODO section
Add URL to AIO.
Polish translation URL added.
Fix up a stray <davej [at] suse [dot] de> that I missed.
Update spanish translation URL.
0.43 - oprofile URL changed.
Update Linus' email
Drop report of buggy Red Hat 3.2.2-5 gcc.
Remove reference to Jens' hacked cdrecord, standard version is now ok.
PC Speaker note added.
Mention elevator=deadline for database folks.
Merge two deprecated sections.
Update URL to xfsprogs.
Mention Conectiva module-init-tools
Mention acpi=force, and DMI blacklist.
DRI CFT on X4.1
Pentium Pro SYSENTER is broken.
Update Alans list of IDE bugs
Add geometry translator workarounds.
Mention swapfile limitations.
Update Reiserfs new features.
Move some features marked as 'deprecated' to 'removed'.
Add 'needs forward porting' section.
Pointer to synaptics touchpad driver webpage.
Update ipsec utils URL.
Mention usb-storage changes.
Modules are now .ko instead of .o
Mention how to change elevator on command line.
Document statfs64()
ext3 data=journal mode should now be fixed.
Fix iosched pathname.
Document USB changes.
Add SCTP to Networking.
s/2.5/2.6/ in most of the doc.
Mention AIO.
Add additional IPSEC howto URL.
Deprecate numeric sysctls
0.42 - CONFIG_LOG_BUF_SHIFT is now sanity checked by Kconfig
Hyperthreading scheduler improvements.
ALSA OSS emulation.
32bit uids in new quota.
Not all filesystems support nanosecond stat.
Note that NTFS still isn't R/W
Mention CryptoLoop.
0.41 - V=0 is now default. Document V=1
s/Redhat/Red Hat/ everywhere.
Added vmware sysenter note.
MTRR for vesafb
Various grammar fixes.
Selectable elevators.
PCI domains
0.40 - Callout tty devices are removed.
Added note about modules in Red Hat 9
0.39 - irqbalance note added.
Added ntop, snmp tools obsolete messages.
Added link to David Mosberger's O(1) page.
Mention Herbert Xu's FreeSWAN patches.
Add CONFIG_VGA_CONSOLE to the list of gotchas.
Add note about 2.4 .config's to gotchas.
Reword devpts note.
0.38 - Fixed URL to nameif
0.37 - devfs users now need to mount devpts.
mention h8300 port.
mentioned NTFS rewrite.
0.36 - Include Doug Gilberts 'positive SCSI spin'.
Mention NAPI.
Reword the CPU bug workaround that the O(1) scheduler exposes.
Added 'Known Gotchas' section
0.35 - Note about KDE panel applets.
mount --move, dmask, fmask
Removed note about oprofile utilities being underdeveloped.
Mention ext2 locking, and ext2/ext3 orlov allocator.
0.34 - Remove people.redhat.com NPTL URLs on Ulrich Dreppers request.
Added note about s390x going away.
Various kbuild updates.
Note about swap files.
Added note about -p1 vs -p0
Lots of typo fixes from Randy Dunlap.
RPM from RH9 seems to have problems.
0.33 - Networking RFCs section added.
0.32 - Added Soundmodem userspace replacement URL.
0.31 - ext3 data=journal breakage noted.
0.30 - Athlon powernow is now supported.
0.29 - Mention NIC renumbering and ACPI/APIC NIC bugs.
0.28 - SO_BSDCOMPAT obsolete messages, nfsutils.
0.27 - radeon -> radeonfb
0.26 - Added info about readprofile.
0.25 - Added cdrecord example. Added URL to Spanish translation.
0.1->0.24 - Unrecorded history

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Other Links.

TODO: (Please mail me a few lines about these if you are
the owner of these).

PCI IDs (new_id, agpgart try_unsupported)
kdev_t changes?
ISDN rewrite?
Hangcheck timer
initramfs ?

관련 링크: http://www.codemonkey.org.uk/post-halloween-2.5.txt

커널 2.4대에서 2.6대로 이전시에는 많은 프로그램들의 업그레이드가 필요합니다.
이서버 역시 베이스는 레드햇 7.1인지라 (새로 설치된 프로그램도 많고 레드햇 7.1의 흔적은 glibc정도에서
찾아볼수 있긴합니다만 ^^) 꽤나 많은 프로그램들을 업데이트 했습니다. 자세한 사항은 아래링크를 참고하시고..
정상적으로 커널을 컴파일한뒤 새로운 커널로 부팅후에 message등의 로그에 kernel로그로 모듈관련 메세지나
"kernel: Fix your initscripts?"등의 로그가 보인다면  /etc/rc.d/rc.sysinit 파일을 열고 /proc/ksyms 부분을
/proc/kallsyms로 고쳐주면 됩니다. /proc/ksyms ==> /proc/kallsyms
그리고 net-snmp 사용시 syslog에 "process `snmpd' is using obsolete setsockopt  SO_BSDCOMPAT" 등의 메세지가
보인다면 net-snmp를 5.1.x대 이상버전으로 새로 설치하시면 해결됩니다.

또한 시스템이 오래된 bdflush를 사용하고 있다면 "update used the obsolete bdflush"등의 메세지를 보일수 있습니다.
해결방법은 /etc/inittab파일을 열고 아래부분을 주석처리하면 다음부팅후엔 위와같은 메세지는 뜨지 않을겁니다.

# Things to run in every runlevel.

기타프로그램을 사용시 비슷한 "used the obsolete~" 메세지가 남을수 있는데 사용프로그램의 최근버전을
사용하면 해결될것으로 보입니다.

관련 링크: http://thomer.com/linux/migrate-to-2.6.html
  1. Favicon of http://free4u.dnip.net BlogIcon first4you 2004.07.21 13:11

    "kernel: No module symbols loaded - kernel modules not enabled." 메세지에 관한 글을
    Linux-Kernel Archive에서 퍼왔습니다.


    &gt; Basic problem - my kernel modules wont load on boot.

    This doesn't seem to be a kernel issue.

    &gt; Dec 21 18:33:54 noc kernel: Symbols match kernel version 2.6.0.
    &gt; Dec 21 18:33:54 noc kernel: No module symbols loaded - kernel modules not enabled.

    This is output from klogd. Since you have CONFIG_KALLSYMS enabled, you shouldn't need this anyway.


    출처 : http://www.uwsg.iu.edu/hypermail/linux/kernel/0312.2/1312.html

+ Recent posts