From nobody Wed Jul 28 17:30:44 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 2620D127FDA2 for ; Wed, 28 Jul 2021 17:31:03 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-oo1-f44.google.com (mail-oo1-f44.google.com [209.85.161.44]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4GZggB430Xz3rDT; Wed, 28 Jul 2021 17:31:02 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-oo1-f44.google.com with SMTP id n1-20020a4ac7010000b0290262f3c22a63so845953ooq.9; Wed, 28 Jul 2021 10:31:02 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=IOHk+Ty0cvy+oiJ73rcBaRAc9ilh/DRxFrWQNEopjOI=; b=ctJArdc4NN5bc1V8+UU3jTL+Rq6zSgfmKMFQ2aOeUVHES6UfVJhnlFDKsSlMA8/3M0 Ro+UdQ8NFkw4ANwFpoC7gxRQgsZJgaeYOwb5ZsWYy9q4RxREsIEPU5yQIu3KMSZVPz93 Koc/18cJxv+DFi4dxNknASI5Pnvp/AAZ/pJLVfNbjlbqTb6R01WP5LOfCukQHmLHtv99 iqHA5iqlOFJEDIxJKkqolsgbUZJqu8uRLiOcATFEgES3sYhSXA2V3lXpK2LkO8VB5C8L 4wfgcQuk1PN43ZKWcq20unlxnODfy8wgaeXGJbfv+K1KoRGx6bMIAzfG19W5BZK4jMg2 S1mQ== X-Gm-Message-State: AOAM5305ovKo1xZpN/Wm78phEN3M/iL+KtcOKjMFPBRaVw/TMERl6w/u JroZ9brTshk6OoWiHyTId3uZ42Ezyj1QcHB78viNdFbKq6Q= X-Google-Smtp-Source: ABdhPJw3O1QXZz8VJ8dZasTPG5NTfDnjOQiHLrWezeTx4w9SOJTgP7DcRnaI4MGDdwEPAAfSGF+ozqs3pZA0x4nwaGE= X-Received: by 2002:a4a:e1f8:: with SMTP id u24mr444329ood.61.1627493455743; Wed, 28 Jul 2021 10:30:55 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <20210728172650.GI1648@FreeBSD.org> <20210728172830.GJ1648@FreeBSD.org> In-Reply-To: <20210728172830.GJ1648@FreeBSD.org> From: Alan Somers Date: Wed, 28 Jul 2021 11:30:44 -0600 Message-ID: Subject: Re: Building multiple kernels with "make release" To: Glen Barber Cc: FreeBSD CURRENT Content-Type: multipart/alternative; boundary="0000000000004dcfae05c83259bb" X-Rspamd-Queue-Id: 4GZggB430Xz3rDT X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-Spam: Yes X-ThisMailContainsUnwantedMimeParts: Y --0000000000004dcfae05c83259bb Content-Type: text/plain; charset="UTF-8" On Wed, Jul 28, 2021 at 11:28 AM Glen Barber wrote: > On Wed, Jul 28, 2021 at 05:26:50PM +0000, Glen Barber wrote: > > On Wed, Jul 28, 2021 at 11:11:48AM -0600, Alan Somers wrote: > > > Is it possible to build multiple different kernels and include them > all in > > > a release image? release.conf says so. But from experiment, what I > see is > > > that: > > > > > > * release.sh does pass both kernels in the KERNCONF variable to "make > > > buildkernel" > > > * "make buildkernel" dutifully builds both > > > * BUT, "make installkernel" only installs the first kernel and ignores > the > > > rest > > > * Only the first kernel ends up in the final image > > > * It's not really clear where an alternate kernel should go, anyway. > > > Probably someplace like /boot/kernel.debug , but release.conf doesn't > > > provide a way to specify that. > > > > > > So is the "multiple kernels in release.conf" feature unfinished? If > so, > > > does anybody have a good idea about the best way to finish it? > > > > > > > https://github.com/freebsd/freebsd-src/blob/7045b1603bdf054145dd958a4acc17b410fb62a0/release/release.conf.sample#L32 > > > > > > > Last I was aware, based on a patch sent to me privately, I believe, it > > should work. > > > > Let me take a look. > > > > Oh, wait. Are you using 'make release' or release/release.sh? > > Glen > I'm using release.sh. I thought that was just a wrapper for "make release". --0000000000004dcfae05c83259bb--