Date: Wed, 21 Apr 2004 19:09:52 +0200 From: Roman Neuhauser <neuhauser@chello.cz> To: markm@FreeBSD.ORG Cc: Kris Kennaway <kris@obsecurity.org> Subject: Re: panic: random.ko Message-ID: <20040421170952.GC2088@isis.wad.cz> In-Reply-To: <200404211103.i3LB3aIn033981@grimreaper.grondar.org> References: <20040421082505.GA75715@xor.obsecurity.org> <200404211103.i3LB3aIn033981@grimreaper.grondar.org>
next in thread | previous in thread | raw e-mail | index | archive | help
# markm@FreeBSD.ORG / 2004-04-21 12:03:36 +0100:
> 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.
Of course I run unload as the first step. It wrote it unloaded the
modules, and the started loading them again booting the new kernel.
--
If you cc me or remove the list(s) completely I'll most likely ignore
your message. see http://www.eyrie.org./~eagle/faqs/questions.html
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040421170952.GC2088>