From owner-freebsd-hackers Sun May 19 13:31:23 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA18575 for hackers-outgoing; Sun, 19 May 1996 13:31:23 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA18565 for ; Sun, 19 May 1996 13:31:18 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id NAA00580; Sun, 19 May 1996 13:30:22 -0700 (PDT) To: Toshihiro Kanda cc: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch), hackers@FreeBSD.org Subject: Re: Does /stand/sysinstall overwrite existing system? In-reply-to: Your message of "Thu, 16 May 1996 21:39:29 +0900." <199605161239.VAA05852@xxx.fct.kgc.co.jp> Date: Sun, 19 May 1996 13:30:22 -0700 Message-ID: <578.832537822@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > I see, thank you. What I really wanted to do is capturing the > sysinstall screen images. (My goal is publishing "Install guide" WWW > pages with these graphics.) I could do this by xv(l), kterm(1) and > vga font came with pcemu(1); please see Well, if you're willing to document the -current sysinstall instead (or edit the screen-shots that look different, most menus are the same), that version has a command-line switch called `-fake' which, if specified, causes all the system modifying commands to be skipped. It basically just puts sysinstall into simulation mode (with lots of debugging printfs going to the sysinstall.debug file) for someone trying to test its control flow without blowing the underlying system away. :-) Jordan