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

Re: [issue1140] installkernel POSTFIX directive


From: Stefan Johannesdal <stefan.johannesdal@xxxxxxxxx>
Date: Sun, 21 Sep 2008 20:59:50 +0200

Matthew Dillon wrote:
    The problem I have is that having three different directives is, well,
    it is rather confusing.  I want to simplify it even more.

I have an idea. Please tell me if this is way off base.

    Why don't we just create a postfix out of the kernel name by default?
    So if you 'make installkernel KERNCONF=BLAH' you will get a
    /boot/kernel.BLAH and /boot/modules.BLAH ?

    So, for example, a GENERIC kernel would be installed as
    /boot/kernel.GENERIC and /boot/modules.GENERIC.

    We would then have a loader variable which defaults to 'GENERIC' in
    loader.conf, telling the loader which kernel to boot.

How does that sound?

-Matt
Install a kernel:
make installkernel KERNCONF=MYCONF

Install a second kernel, for example a SMP one:
make installkernel KERNCONF=MYSMPCONF KERNPOSTFIX=.smp

Install a kernel and modules somewhere else than /boot (like a VKERNEL):
make -DNO_MODULES installkernel KERNCONF=VKERNEL DESTKERNDIR=/var/vkernel/boot


I put the examples here to show that it does not really get that confusing. At least I don't think so and it gives all the options one might want.
On the other hand I like the idea of making it even more simple. If KERNPOSTFIX is not defined by the user we could set it to .${KERNCONF} and we get the behaviour suggested above.


--

Mvh - Stefan -




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