From owner-freebsd-sysinstall@FreeBSD.ORG Sun Jan 23 18:59:14 2011 Return-Path: Delivered-To: freebsd-sysinstall@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DC4D51065674; Sun, 23 Jan 2011 18:59:14 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 225168FC1E; Sun, 23 Jan 2011 18:59:13 +0000 (UTC) Received: by wyf19 with SMTP id 19so3446770wyf.13 for ; Sun, 23 Jan 2011 10:59:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=QHynQHNBWbY1/0b2kY4NQJOw4t9ktI2ZpY0IqDgDE3c=; b=L6zhfsibN4mEyNUHNSEA6jR71tBlLXbOmgGewPb+Lxb7Ouo7VmZlc0p2lu3CpVCc2g Zp+PfkXIYQQtLZ4jY3p2HWSqDeEnhJ+wDZFHggk4PPL1jmxmAePaE5rWqVilJ2AU3WSt m+qWzfJPrJU6smIh6fa5idjKBAxRJaFJVX7u4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=dCDX/r6gDcFbPtUdYRfuNH/rBTcwdowX+OZq6auh5ywAAyObjNi0aZJ8sHMAwUQxBn JEix+a5b//nEz199VmvT3dXx06drBIyY4umar2BYI4yzpQpjksyGQK91ZcmadN2RvQDS GSITbcHlXrXdgPIoSCzhTeo0GqVSGsJwMK55A= MIME-Version: 1.0 Received: by 10.216.30.137 with SMTP id k9mr2791549wea.31.1295809151699; Sun, 23 Jan 2011 10:59:11 -0800 (PST) Sender: yanegomi@gmail.com Received: by 10.216.254.226 with HTTP; Sun, 23 Jan 2011 10:59:11 -0800 (PST) In-Reply-To: <4D28EB32.9090807@freebsd.org> References: <4D28EB32.9090807@freebsd.org> Date: Sun, 23 Jan 2011 10:59:11 -0800 X-Google-Sender-Auth: 9S6oE1V9rd_zhuqe3D2xTDE39R8 Message-ID: From: Garrett Cooper To: Nathan Whitehorn Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-sysinstall@freebsd.org, freebsd-arch@freebsd.org Subject: Re: BSDInstall ISO images X-BeenThere: freebsd-sysinstall@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Sysinstall Work List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jan 2011 18:59:15 -0000 On Sat, Jan 8, 2011 at 2:54 PM, Nathan Whitehorn wrote: > I've spent some time integrating bsdinstall into startup of install CDs, > mostly related to building useful live-CD-based installers. An i386 image > can be found here (other architectures may follow, as my very slow DSL line > permits): > > http://people.freebsd.org/~nwhitehorn/bsdinstall-i386-20110108.iso.bz2 > > The source for this can be found at: > > svn://svn.freebsd.org/base/user/nwhitehorn/bsdinstall > > The bits related to live CD usage are the testsystem.sh and rc.local files. > Instead of running sysinstall as an init replacement, I have written a small > rc.local script that gives the user the option to either start the > installer, open a single-user-mode style shell, or to continue to boot to a > multi-user live CD. Also, instead of the md root used by sysinstall, this > just boots from the CD directly. This prevents the need for sysinstall's > media selection, since the distribution files are in the mounted root file > system. > > I would appreciate any comments or test results. Not sure if it matters anymore, but here are my comments: NOTE: this was using http://people.freebsd.org/~nwhitehorn/bsdinstall-i386-20110118.iso.bz2 . 1. The i386 image (apparently) isn't compiled with ATACAM, etc support so opening /dev/cd0 always fails with ENODEV. 2. There's a lot of noise at bootup related to missing files. Putting in a dummy /etc/fstab, adding hostid_enable="NO", and setting hostname="" to a dummy value in rc.conf will help weed out some noise. 3. The initial dialog beeped when I first pressed the right key on my keyboard. Maybe hw.syscons.bell=0 would help? 4. Splitting up the Keyboard Menu into regions and providing human readable names would help. Partition Editor (I used Manual for the first try): 1. It would be helpful if the cursor was at the end of the textbox so that I didn't have to position the cursor at the end or press the delete key. 2. K is a bogus suffix for kilo-; k is correct. 3. Having a mountpoint for a bsdlabel partition doesn't make sense and is confusing. 4. Backing out of the Partition Manager and going back to the previous dialogs is impossible. 5. Noting that the values (freebsd-ufs, etc) map back to gpart driven values would be helpful. I exited the install and tried again on the command line. Couldn't conjure up the right gpart commands (manpage sucks for what I was looking for -- creating a new partition), I went back into the partedit command that was in /usr/libexec/ and entered in data manually . Committed my changes which threw me back into the prompt and then hit ^d to get back into the installer proper. The first run around failed for some odd reason (claimed it couldn't create boot/kernel.gz, or whatever, so there might be some error checking missing with mount, mkdir, etc). Chose restart, walked through the process again and chose manual, made sure the slice was properly configured for / and swap was setup, then continued. This time the install went through properly. Progress bar: I think you're on the right track by simplifying the install, but it could be polished to say: kernel world distribution (in what context is distribution? Is it configuration files, etc from `make distribution' ?) Configuring Network (etc) Seems like this could have been done earlier on to shrink the CD size down a bit. Add Users (YAY! something that finally works) - Prompts seem ok. - Login class - getting too specific IMO; this should be done after the first boot. - Home directory - /usr/home was the traditional home directory root for BSD I thought. - Home directory permissions - as an aside, what are the default? - Use password-based authentication - what other options are there other than not having a password or using a non-master.passwd backend like LDAP, etc? - Lock out account after creation - I would remove this; again, it seems like something that an admin can do after first boot. In general: Some of the dialogs are a bit small (like the DHCP status dialog). Enlarging them might help. Hopefully this feedback is helpful. Thanks! -Garrett