a custom fault signal handler does :-)
Cheers,
Gilad
--
Gilad Ben-Yossef
Chief Coffee Drinker
Codefidence Ltd.
The code is free, your time isn't.(TM)
Web:http://codefidence.com
Email: [EMAIL PROTECTED]
Office: +972-8-9316883 ext. 201
Fax:+972-8-9316885
Mobile: +972-52-8260388
Q
Tim Bird wrote:
Gilad Ben-Yossef wrote:
Tim Bird wrote:
I agree. When you say have the application call modprobe directly,
I'm not sure I understand what you mean.
I simply meant that you can fork and exec modprobe itself (or use
system() but that
would require a working
Tim Bird wrote:
Gilad Ben-Yossef wrote:
Well, seeing as both modprobe and a minimal shell are part of busybox
which is included in over 90%+ of Linux based embedded systems and that
the script is trivial, not to mention that you can just have the
application call modprobe directly, just
them in a an in kernel
initramfs if you want to keep them attached to the kernel binary for
ease of maintenance) and simply call a script that calls modprobe when
it's OK to load them?
Sounds a hell of lot simpler to me...
Gilad
--
Gilad Ben-Yossef
Chief Coffee Drinker
Codefidence Ltd
