> Actually, IMO, even on 2.4, loosely replacing certain or all > sys_call_table entries are highly discouraged. The reason is > similar...you don't know whether they are currently referenced or not, > right? Since all other code expects it to be read-only anyway once its setup (if I'm right), concurrency shouldn't be a problem? Joel -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ