1 / 4

Files to change in Redhat Linux

Files to change in Redhat Linux. The following list is a starting point for adding a simple kernel service. Possible files to change in Redhat Linux. / usr / src / redhat /BUILD/kernel-2.6.18/linux-2.6.18.s390x/arch/ s390 /mm/ fault.c

yuki
Download Presentation

Files to change in Redhat Linux

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Files to change in Redhat Linux The following list is a starting point for adding a simple kernel service.

  2. Possible files to change in Redhat Linux • /usr/src/redhat/BUILD/kernel-2.6.18/linux-2.6.18.s390x/arch/s390/mm/fault.c • /usr/src/redhat/BUILD/kernel-2.6.18/linux-2.6.18.s390x/arch/s390/kernel/syscalls.S • /usr/src/kernels/2.6.18-92.el5-s390x/include/asm-s390/unistd.h • /usr/src/redhat/BUILD/kernel-2.6.18/linux-2.6.18.s390x/include/asm-s390/unistd.h • /usr/include/asm/unistd.h --------- The following file is for PCs only ---------- /usr/src/redhat/BUILD/kernel-2.6.18/linux-2.6.18.s390x/arch/i386/kernel/syscall_table.S

  3. Contents, by number on previous slide • “mm/fault.c”: Your code for the service call • “syscalls.S”: Builds the syscall table • “../kernels../unistd.h”: Defines the name & number of the call • “../redhat/BUILD/../unistd.h”: Same as above • “/usr/include/asm/unistd.h”: Contains the include values for the kernel itself to determine what facilities are available at compile time---------------------------------------------- • “syscall_table.S”: Defines the name as a “long”

  4. Names I used (for my own solution) • …/fault.c: sys_DJ_fault_tracker 311 • …/BUILD…/unistd.h “ • /usr/include/asm/unistd.h“(allows TESTING pgmto use a name instead of 311) • …/kernels…/asm-s390/unistd.h __NR_DJ_fault_tracker 311 (note that this one is different, but it doesn’t hurt because it isn’t referenced by fault.c) • …/syscalls.S (sys_DJ_fault_tracker, sys_DJ_fault_tracker, sys_DJ_fault_tracker) • The whole point of using a NAME instead of the number is that, users do not have to use raw numbers. Raw numbers lead to errors. Names are better (for humans anyway). • Of course, you should have your own names!!!!

More Related