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: YONETANI Tomokazu <qhwt+dfly@xxxxxxxxxx>
Date: Wed, 1 Sep 2010 07:31:06 +0900

On Tue, Aug 31, 2010 at 09:23:04AM -0700, Matthew Dillon wrote:
>     Hmm.  I've been wanting to go to a /boot/<directory>/{kernel + modules}
>     setup for a while, I'm glad you brought this up.  I will mess around a
>     bit today and see if I can implement the model I want.  It will be a
>     nice break from the kernel work.

We have DESTLABEL variable (see build(7)); with which, If specified, things
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.



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