Changing functions/code on running target

Well, if the code is in the kernel, and if it is not a module, then you can not avoid a reboot, thereby loosing all state. If it *is* a module, it should be possible to compile it seperate from the kernel and unload/reload it in a running system. However, you said above that "Some kernel modules cannot be reloaded". Care to explain why?

IMHO the ideal setup for quick development turnaround times is an NFSroot system: Keep the root file system on the development host and let the target mount it via NFS. That way, you can rebuild any files on the development host and just load them on the target. We do that all the time.

Rob

-- Robert Kaiser email: rkaiser AT sysgo DOT com SYSGO AG

We are using the Intel Ethernet driver module ixp425_eth.c, which complains about "locked resources" or so.

We use a commercial Linux distribution (not sure if I'm allowed to name it), which officially doesn't support NFS root file systems. Maybe there is a simple way of making this work?

-- Daniel

Check Documentation/nfs-root.txt in the kernel source directory.

Hmm, that could be a bug in the driver. Anyway, if you build an NFSroot system, you don't want to unload the NIC driver as that is your link to the root file system. Typically, you would link it into the kernel statically.

There is an embedded Linux distribution available that comes with a number of preconfigured configurations, NFSroot being one of them. (Hint: see my .sig)

As another poster has suggested: read Documentation/nfs-root.txt

Good Luck

Rob

-- Robert Kaiser email: rkaiser AT sysgo DOT com SYSGO AG