Date: Mon, 6 Aug 2018 05:07:03 +0800 (+08) From: Paul Goyette <p...@whooppee.com> Message-ID: <pine.neb.4.64.1808060459190.6...@speedy.whooppee.com>
| Or we could just leave things alone, and tolerate the "hack" that is | currently being used. Or there could just be a new 1 bit/syscall const data struct that says whether the original (as compiled originally) syscall entry was sys_nomodule or something different. If the bit is set, put sys_nomodule back, otherwise sys_nosys (those are the only possible values, right). makesyscalls.sh could easily make this new big vector, which would only be used as part of unloading a syscall module, so need not be particularly effecient (avoid big/little endian issues by making it an array of u_char if that matters, for example). kre