On Wednesday, November 06, 2013 19:18:31 UTC Baldwin, John wrote:
On Wednesday, November 06, 2013 10:22:44 am Teske, Devin wrote:
On Nov 6, 2013, at 1:18 AM, Lars Engels wrote:
> Am 05.11.2013 18:06, schrieb Kurt Lidl:
>
>> Well, I'd probably be in support of this change - it sure beats having
>> to interrupt the normal boot sequence and typing:
>> unload
>> load /boot/kernel.old/kernel
>> load /boot/kernel.old/opensolaris.ko
>> load /boot/kernel.old/zfs.ko
>> boot
>
> To load an older kernel I always just type
>
> boot kernel.old
>
>
> Doesn't that unload the currently loaded kernel automatically?
Actually... it does.
Thanks for pointing that out (forgot about that).
The only thing that it doesn't do which I wish it did was fixup
module_path. Right now if you break into the loader prompt and
do 'boot foo', you end up with module_path containing
"/boot/kernel;/boot/modules;/boot/foo". What I would like is to
be able to use 'boot foo' and get a proper module_path.
Yeah - I found this out the hard way when playing with incompatible
versions of zfs.ko. I suppose the "boot kernel.old" method works
if "kernel.old" is "close enough" to "kernel", as you'll get the
kernel.old/kernel file, and kernel/zfs.ko kernel/opensolaris.ko modules
loaded that way.
-Kurt
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
