Thank you. That was it. Booted from
/boot/cvsup/kernel, loaded modules from
/boot/kernel/*. Now, if I can just figure out
"read-conf" and friends in loader.
It seems I have to manually:
loader> unload
loader> set kernel=cvsup
loader> set kernelname=/boot/cvsup/kernel
loader> set module_path=/boot/cvsup
loader> boot
I want to have two different kernels - one I know
works (older -current) and the latest cvsup of
-current.
Then, I would like to:
loader> "some-command-to-load-alternate-configuration"
I suppose that's read-conf, but that doesn't seem to
like me :(
I have: /boot/cvsup.conf as:
unload
kernel=cvsup
kernelname=/boot/cvsup/kernel
module_path=/boot/cvsup
then I use:
loader> read-conf cvsup.conf
but the changes don't take effect. Oh well, maybe
some more experimentation later...
Thanks,
Chuck McCrobie
--- Kenneth Culver <[EMAIL PROTECTED]> wrote:
> What exactly were you running? I use linux emulation
> on -CURRENT right now
> for mozilla and a few other packages, and havn't had
> any panics... you
> might have your kernel modules out of sync with your
> kernel.
>
> Ken
>
> On Mon, 13 Jan 2003, Chuck McCrobie wrote:
>
> > Two panics produced when using Linux emulation on
> a
> > machine CVSUP'ed two hours ago. Both very easy to
> > produce. Am I the only one running Linux
> emulation on
> > -current? Or is something wacked-ifed with this
> > machine?
> >
> > Thanks,
> >
> > Chuck McCrobie
> > [EMAIL PROTECTED]
> >
__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
