From owner-cvs-all Mon Jan 7 13:14:53 2002 Delivered-To: cvs-all@freebsd.org Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by hub.freebsd.org (Postfix) with ESMTP id 3C05537B417 for ; Mon, 7 Jan 2002 13:14:35 -0800 (PST) Received: (qmail 10823 invoked from network); 7 Jan 2002 21:14:34 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail6.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 7 Jan 2002 21:14:34 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200201072020.g07KK7965561@bmah.dyndns.org> Date: Mon, 07 Jan 2002 13:14:04 -0800 (PST) From: John Baldwin To: "Bruce A. Mah" Subject: Re: cvs commit: src/release Makefile Cc: cvs-all@FreeBSD.org, cvs-committers@FreeBSD.org Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 07-Jan-02 Bruce A. Mah wrote: > If memory serves me right, John Baldwin wrote: >> jhb 2002/01/06 23:42:41 PST >> >> Modified files: (Branch: RELENG_4) >> release Makefile >> Log: >> MFC: Rev. 1.640 and 1.644: split the mfsroot out of boot.flp kernel and >> don't use write_mfs_in_kernel anymore. Also, switch to using a stock >> GENERIC kernel for booting off the CD on Alpha and on x86 with cdboot. >> On x86 INTRO_USERCONFIG isn't enabled for a CD that boots from cdboot >> however. It still works fine for a CD that boots from boot.flp like we >> currently do. > > Do you plan to frob src/release/{alpha,i386}/mkisoimages.sh too (to > update the -b and -c options to mkisofs)? They don't need any frobbing right now. Since cdboot doesn't run INTRO_USERCONFIG (we could fix that by compiling the 'intro' keyword into the kernel if VISUAL_USERCONFIG is specified, I already create a kernel.conf that contains 'intro', it just doesn't work) it's not suitable yet. Also, the idea for our RC's are to distribute both a cdboot and boot.flp ISO, so we can deterine how wide-spread support is for cdboot. If it's very wide, we might ship a cdboot ISO by default. If it's not supported by most of the systems out there, we might just ship a boot.flp ISO by default. If it's more of an even split, we might want to ship 2 ISO's. The only changes are the options to mkisofs, and both ISO's have the exact same contents, so it's not that much effort to generate 2 ISO's. Now if someone is going to ship CD's, they will probably want to pick one or the other. > Bruce. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message