From tim@X2296 Thu Oct 10 20:44:19 1996 Received: from X2296 (ppp1677.on.sympatico.ca [206.172.249.141]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA11831 for ; Thu, 10 Oct 1996 20:43:59 -0700 (PDT) Received: (from tim@localhost) by X2296 (8.7.6/8.7.3) id WAA00521; Wed, 27 Dec 1995 22:30:16 -0500 (EST) Message-Id: <199512280330.WAA00521@X2296> Date: Wed, 27 Dec 1995 22:30:16 -0500 (EST) From: keohrednaV.miT@X2296 Reply-To: ac199@freenet.hamilton.on.ca To: FreeBSD-gnats-submit@freebsd.org Subject: sysinstall is broken and SIG11's X-Send-Pr-Version: 3.2 >Number: 1757 >Category: misc >Synopsis: sysinstall repeatably generates a sig11 >Confidential: no >Severity: critical >Priority: low >Responsible: freebsd-bugs >State: closed >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Oct 10 20:50:01 PDT 1996 >Closed-Date: Tue Oct 22 09:59:04 PDT 1996 >Last-Modified: Tue Oct 22 09:59:37 PDT 1996 >Originator: Tim Vanderhoek >Release: FreeBSD 2.2-961006-SNAP i386 >Organization: -- The Organization of people wondering what would happen if I piped /dev/zero into this section for a couple of seconds? >Environment: FreeBSD 2.2-961006-SNAP boot disk. >Description: I have been granted the capability to consistently cause sysinstall to generate ugly-looking (as opposed to sexy) sig11's. It happens only when certain values are given when doing the network configuration, hence the low priority. >How-To-Repeat: 1. (*) Boot from boot disk. 2. Select "Set Options" option from main menu. 3. Choose to set the "Media". 4. Choose ftp media. 5. Choose something. 6. Choose pp0. If you have the urge, maybe you can get away with some other choice? 7. Enter a hostname. 8. TAB over (oops! Is that a Windows term?) everything else and select "Ok". 9. Read the message "Missing Name Server" and select "Ok". 10. Read baud rate question, and select "Ok". You may (probably?) enter a substitute baud rate, if you so desire. 11. Read ip address question, and select "Ok". You may (probably?) enter a substitute ip address, if you are in such a manner motivated. 12. Read the message telling you to establish a connection, and disobey it. You could (probably?) establish a connection if you were so inclined, but it's hardly even worth it. 13. Choose "Media type". 14. Intuit the fact from the previous instruction that you are back at setting-options menu. 15. Choose "FTP". 16. Read the message concerning skipping the reconfiguration of netopts. 17. Understand that we want to reconfigure netopts, so you should select "No". 18. Select "pp0". If you are drawn to such an action, you might possibly be able to get away with selecting some other deal. 19. Laugh heartily as sysinstall turns inwards in a roaring mass of flames, stuttering messages such as "I'm dead! I'm Dead!". HAHAHAHA!! 20. Decide that this guy is pretty stupid, since flames don't have much mass... (*) Necessary? Maybe? Maybe not? >Fix: Improve `dialog' and `libdialog' and then rewrite `sysinstall' as a bunch of shell scripts, or something along those lines. Optionally, warn people that reconfiguring netopts can cause a crash. >Release-Note: >Audit-Trail: From: J Wunsch To: ac199@freenet.hamilton.on.ca Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: misc/1757: sysinstall is broken and SIG11's Date: Fri, 11 Oct 1996 09:53:42 +0200 (MET DST) As keohrednaV.miT@X2296 wrote: > 9. Read the message "Missing Name Server" and select "Ok". Don't do this. Fill in a nameserver value. This was a known bug in sysinstall that has been fixed since. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) State-Changed-From-To: open->closed State-Changed-By: phk State-Changed-When: Tue Oct 22 09:59:04 PDT 1996 State-Changed-Why: Jordan has nailed this one I presume. >Unformatted: