On 21 Jan 1999, Jacques Gelinas writes:
> On Thu, 21 Jan 1999, Jonathan Marsden wrote:
> THe problem comes from the call to "linuxconf --setmod" in the upgrade
> process. ...
> The solution to this problem will be to process the --setmod and
> --unsetmod options early at startup, before loading the module. This
> will cure the problem.
Great! I'm just glad we found it!
Jonathan
--
Jonathan Marsden | Internet: [EMAIL PROTECTED] | Making electronic
1849 N. Wabash Ave.| Phone: +1 (909) 794 1151 | communications work
Redlands, CA 92374 | FAX: +1 (909) 794 3016 | reliably for Christian
USA | http://www.xc.org/jonathan | missions worldwide
---
You are currently subscribed to linuxconf as: [[email protected]]
To unsubscribe, forward this message to [EMAIL PROTECTED]
