Kris Kennaway writes: > > loader to ignore loader.con) was that "unload" didn't help, it > > showed the kernel and modules were unloaded, but subsequent > > > > load <kernel> > > boot > > > > or > > > > boot <kernel> > > > > loaded the the modules again, and I had to "disable-module" for > > every individual module, about twelve times. Is that normal > > behavior, or was there a pilot error somewhere? > > I think it's expected behaviour. My fingers know what to do to stop > this, but my brain can't remember it right now :-)
unload load /boot/kernel/kernel boot does it for me. M -- Mark Murray iumop ap!sdn w,I idlaH _______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
