From owner-cvs-user  Sat Oct  5 03:44:26 1996
Return-Path: owner-cvs-user
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id DAA07806
          for cvs-user-outgoing; Sat, 5 Oct 1996 03:44:26 -0700 (PDT)
Received: (from jkh@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id DAA07780;
          Sat, 5 Oct 1996 03:44:11 -0700 (PDT)
Date: Sat, 5 Oct 1996 03:44:11 -0700 (PDT)
From: "Jordan K. Hubbard" <jkh>
Message-Id: <199610051044.DAA07780@freefall.freebsd.org>
To: CVS-committers, cvs-all, cvs-user, cvs-sys
Subject: cvs commit:  src/sys/conf newvers.sh src/sys/i386/conf options.i386 src/sys/i386/i386 locore.s machdep.c userconfig.c src/release dumpnlist.c Makefile src/release/sysinstall Makefile install.c uc_main.c dumpnlist.c
Sender: owner-cvs-user@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

jkh         96/10/05 03:44:10

  Modified:    release   Makefile
               release/sysinstall  Makefile install.c uc_main.c
               sys/conf  newvers.sh
               sys/i386/conf  options.i386
               sys/i386/i386  locore.s machdep.c userconfig.c
  Added:       release   dumpnlist.c
  Removed:     release/sysinstall  dumpnlist.c
  Log:
  Multiple changes stacked as one commit since they all depend on one another.
  
  First, change sysinstall and the Makefile rules to not build the kernel
  nlist directly into sysinstall now.  Instead, spit it out as an ascii
  file in /stand and parse it from sysinstall later.  This solves the chicken-n-
  egg problem of building sysinstall into the fsimage before BOOTMFS is built
  and can have its symbols extracted.  Now we generate the symbol file in
  release.8.
  
  Second, add Poul-Henning's USERCONFIG_BOOT changes.  These have two
  effects:
  
  	1. Userconfig is always entered, rather than only after a -c
  	   (don't scream yet, it's not as bad as it sounds).
  
  	2. Userconfig reads a message string which can optionally be
  	   written just past the boot blocks.  This string "preloads"
  	   the userconfig input buffer and is parsed as user input.
  	   If the first command is not "USERCONFIG", userconfig will
  	   treat this as an implied "quit" (which is why you don't need
  	   to scream - you never even know you went through userconfig
  	   and back out again if you don't specifically ask for it),
  	   otherwise it will read and execute the following commands
  	   until a "quit" is seen or the end is reached, in which case
  	   the normal userconfig command prompt will then be presented.
  
    How to create your own startup sequences, using any boot.flp image
  from the next snap forward (not yet, but soon):
  
  	% dd of=/dev/rfd0 seek=1 bs=512 count=1 conv=sync <<WAKKA_WAKKA_DOO
  USERCONFIG
  irq ed0 10
  iomem ed0 0xcc000
  disable ed1
  quit
  WAKKA_WAKKA_DOO
  
  Third, add an intro screen to UserConfig so that users aren't just thrown
  into this strange screen if userconfig is auto-launched.  The default
  boot.flp startup sequence is now, in fact, this:
  
  	USERCONFIG
  	intro
  	visual
  
  (Since visual never returns, we don't need a following "quit").
  
  Submitted-By: phk & jkh
  
  Revision  Changes    Path
  1.243     +27 -17    src/release/Makefile
  1.44      +2 -7      src/release/sysinstall/Makefile
  1.129     +3 -5      src/release/sysinstall/install.c
  1.7       +42 -14    src/release/sysinstall/uc_main.c
  1.25      +2 -2      src/sys/conf/newvers.sh
  1.21      +2 -1      src/sys/i386/conf/options.i386
  1.74      +11 -1     src/sys/i386/i386/locore.s
  1.207     +5 -1      src/sys/i386/i386/machdep.c
  1.53      +65 -4     src/sys/i386/i386/userconfig.c