DragonFly BSD
DragonFly bugs List (threaded) for 2010-09
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: booting kernel.old uses /boot/modules, not modules.old

From: Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxx>
Date: Wed, 1 Sep 2010 01:03:04 -0700 (PDT)

:go to
:  ${DESTDIR}/boot/kernel.${DESTLABEL} and
:  ${DESTDIR}/boot/modules.${DESTLABEL},
:respectively.  I believe that the idea was to be able to specify this
:${DESTLABEL} in the boot loader, for example,
:  OK boot ${DESTLABEL}		# or maybe .${DESTLABEL}
:and $kernel and $module_path are set up to point to those locations.
:I'm not sure how to do this in Forth, though.
:/boot/<directory> is fine as well, but it could be useful if we have
:some make variables for installkernel target to point to where old
:kernel/modules should go or where new kernel/modules should be installed.

    I managed to the whole thing in one day, including ripping out the
    4th loader and putting in a saner C-based menu system.

    Not only can we now boot from directories/{kernel+modules}, but
    I got directories/loader.conf localization working so it is possible
    to have different root mounts, and thus possible to boot 32 or 64 bits
    (though of course root, bins, usr bins, etc have to be different),
    as well as keeping around backup kernels+modules and such.

					Matthew Dillon 

[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]