| 1 |
Hi, |
| 2 |
I want to add my codes to the kernel source( I use gentoo-source ) and |
| 3 |
compile it as modules. |
| 4 |
All my codes are under the directory /usr/src/linu/fs/dnfs/. |
| 5 |
The problem is why everytime after I changed my codes and re-complied |
| 6 |
the kernel, I got a different strange kernel image. |
| 7 |
|
| 8 |
Here is the details: |
| 9 |
linux # make && make modules_install |
| 10 |
CHK include/linux/version.h |
| 11 |
[...] |
| 12 |
LD kernel/built-in.o |
| 13 |
CC [M] fs/dnfs/dnfs.o |
| 14 |
################ my codes |
| 15 |
fs/dnfs/dnfs.c: In function 'init_once': |
| 16 |
fs/dnfs/dnfs.c:22: warning: ISO C90 forbids mixed declarations and code |
| 17 |
fs/dnfs/dnfs.c: In function 'init_dnfs_fs': |
| 18 |
fs/dnfs/dnfs.c:51: warning: ISO C90 forbids mixed declarations and code |
| 19 |
GEN .version |
| 20 |
CHK include/linux/compile.h |
| 21 |
UPD include/linux/compile.h |
| 22 |
CC init/version.o |
| 23 |
LD init/built-in.o |
| 24 |
LD .tmp_vmlinux1 |
| 25 |
KSYM .tmp_kallsyms1.S |
| 26 |
AS .tmp_kallsyms1.o |
| 27 |
LD .tmp_vmlinux2 |
| 28 |
KSYM .tmp_kallsyms2.S |
| 29 |
AS .tmp_kallsyms2.o |
| 30 |
LD vmlinux.o |
| 31 |
MODPOST vmlinux.o |
| 32 |
LD vmlinux |
| 33 |
SYSMAP System.map |
| 34 |
SYSMAP .tmp_System.map |
| 35 |
AS arch/x86/boot/header.o |
| 36 |
CC arch/x86/boot/version.o |
| 37 |
LD arch/x86/boot/setup.elf |
| 38 |
OBJCOPY arch/x86/boot/setup.bin |
| 39 |
OBJCOPY arch/x86/boot/compressed/vmlinux.bin |
| 40 |
GZIP arch/x86/boot/compressed/vmlinux.bin.gz |
| 41 |
LD arch/x86/boot/compressed/piggy.o |
| 42 |
LD arch/x86/boot/compressed/vmlinux |
| 43 |
OBJCOPY arch/x86/boot/vmlinux.bin |
| 44 |
BUILD arch/x86/boot/bzImage |
| 45 |
Root device is (8, 38) |
| 46 |
Setup is 10904 bytes (padded to 11264 bytes). |
| 47 |
System is 2763 kB |
| 48 |
Kernel: arch/x86/boot/bzImage is ready (#22) |
| 49 |
Building modules, stage 2. |
| 50 |
MODPOST 12 modules |
| 51 |
[...] |
| 52 |
CC fs/dnfs/dnfs.mod.o ######### build modules |
| 53 |
LD [M] fs/dnfs/dnfs.ko |
| 54 |
[...] |
| 55 |
INSTALL fs/dnfs/dnfs.ko ######### install modules |
| 56 |
[...] |
| 57 |
DEPMOD 2.6.24-gentoo-r4-gb921d0de-dirty ############### a |
| 58 |
different strange kernel image name |
| 59 |
|
| 60 |
then, the kernel image I am using now is: |
| 61 |
# uname -r |
| 62 |
2.6.24-gentoo-r4-g506ab20b-dirty |
| 63 |
|
| 64 |
From the above, I get two questions: |
| 65 |
1, Why I got a new kernel image(2.6.24-gentoo-r4-gb921d0de-dirty) |
| 66 |
instead of using the old one (2.6.24-gentoo-r4-g506ab20b-dirty) ? As I |
| 67 |
know if I add/change something as modules, all I need to do is "make |
| 68 |
&& make modules_install", and I don't need to install the kernel image |
| 69 |
again and reboot my OS because all the changes are in modules and the |
| 70 |
kernel image is all the same - fixed me please if I'm wrong. |
| 71 |
2, Why the kernel image including my codes have a very strange name |
| 72 |
- 2.6.24-gentoo-r4-g506ab20b-dirty. |
| 73 |
|
| 74 |
Any help will be appreciated! |
| 75 |
-- |
| 76 |
wcw |
| 77 |
-- |
| 78 |
gentoo-user@l.g.o mailing list |
Archives