Printable View
I'd really like ot work out some hardware monitoring capability, but i2c is holding me up. I can compile a kernel, but seems like there are a lot of special considerations for knoppix's kernel. If there's someone who's got a handle on alterning knoppix's kernel, please make one that has i2c modules that will support most x86 architectures. I know I can't be the only one who wants this....
If you are running KNOPPIX install to HD, building custom kernel is pretty easy. If you mean a CD based KNOPPIX, it would mean a remastering that IMO is pretty cumbersome(every time Klaus comes out a new CD, the fork needs to follow, pain to maintain).
Since I use the poorman's install method, I adopt a 'middle of the road' approach as the following :
1. put the ISO file on the HD
2. put my custom kernel tree side by side on a ext2 loopback file under the same directory when the ISO goes
3. extra the boot.img(thus the miniroot.gz) and made modification to the initrc as well as copying the necessary modules to it
4. boot using my own kernel and at the end of initrc, mount my kernel tree to /lib/modules
In this way, I can keep up with the packages in KNOPPIX using my own kernel for as long as I want and I can switch kernel easily.
Of course it sticks to the machine but since the kernel tree is not too large, I believe about 15M compressed, I can put in on a CF(just use one that comes with my digital camera that is useless for that purpose) and I can still carry it around, together with KNOPPIX.
As for alternative knoppix kernel, my limited experience said that there is no such a thing. A kernel in linux means vmlinuz + ALL files under /lib/modules/`uname -r`(which got burnt into the CD) as a slight change in one of the function address exported by the kernel would make those modules unusable and how these address is in the kernel depends on what compilation option one choose when compiling it and what compiler used as well. So a standard linux kernel is actually 30M+(uncompressed) unless for special one where no module is used(like those special purpose router on a floppy stuff).
If Klaus can change his arrangement a bit by seperate out the kernel tree from the rest and use a similar approach as mine, it would be easier to 'inject' a custom kernel to KNOPPIX CD as all I need is to build another clooped kernel tree image and use knoppix-customize to replace that in the ISO.
One of the install alternatives lets you compile the modules outside your kernel source tree (i.e. you don't need to recompile your kernel, you only need its sources) and then install them in the right place. This is how ALSA/nvidia's binary drivers/etc work.
Maybe scripts a la FabianX could do this....
Until now, I still don't know how these binary only module works. I have tried to use the config file of KNOPPIX using supposely the same source tree but the modules are not compatible. I tried to diff the System.map and they are all different.Quote:
Originally Posted by arkaine23