[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: little patch for kallsyms (kernel2.6) (package : initscripts)



> #kallsyms is used in kernel 2.6 instead of ksyms
> #should the logs off kallsyms be written to /var/log/ksyms.$i or to
> /var/log/kallsyms.$i or maybe even both
> #to keep compatibility with programs that read these files?! 

Supporting multiple kernels is a very nobel thing to do indeed. However,
I am not sure whether or not maintaining such scripts when they have
inline if-then-else constructs like this will be easy.

My proposal would be to create kernel-dependant parts of the scripts in
folders like

/etc/initscripts/kernel/2.4/
/etc/initscripts/kernel/2.6/
/etc/initscripts/kernel/2.5/

and then make calls to the scripts using

KERNEL_BRANCH=`/bin/uname -r | /bin/cut -c -3`
/etc/initscripts/$KERNEL_BRANCH/script_to_do_this.sh
/etc/initscripts/$KERNEL_BRANCH/script_to_do_that.sh

A check for the directory
/etc/initscripts/$KERNEL_BRANCH/ could tell the user whether or not the
kernel is support, and if not could ask the user to try starting the
system using initscript for a different kernel, or the nearest kernel
initscripts available.




-- 
Philip Van Hoof, Software Developer @ Cronos
home: me at freax dot org
work: Philip dot VanHoof at cronos dot be
http://www.freax.be, http://www.freax.eu.org




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]